Bug 1845699 - dnf upgrade produced error messages about pdfarranger (rawhide)
Summary: dnf upgrade produced error messages about pdfarranger (rawhide)
Keywords:
Status: CLOSED DUPLICATE of bug 1841656
Alias: None
Product: Fedora
Classification: Fedora
Component: pdfarranger
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: David Auer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-09 20:30 UTC by George R. Goffe
Modified: 2020-06-10 09:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-10 09:07:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description George R. Goffe 2020-06-09 20:30:25 UTC
Description of problem:

Attempting to upgrade this system with "dnf upgrade". Received error messages prohibiting the upgrade.

Version-Release number of selected component (if applicable):

pdfarranger-1.5.3-1.fc33.noarch

How reproducible:
always

Steps to Reproduce:
1.dnf upgrade
2.
3.

Actual results:
see below

Expected results:
clean successful system upgrade

Additional info:

 Problem 1: cannot install the best update candidate for package pdfarranger-1.5.3-1.fc33.noarch
  - problem with installed package pdfarranger-1.5.3-1.fc33.noarch
  - nothing provides python3.9dist(pikepdf) >= 1.7 needed by pdfarranger-1.5.3-2.fc33.noarch

Comment 1 David Auer 2020-06-10 09:07:52 UTC
Hello and thanks for reporting!

Unfortunately this is an error up in the dependency chain and not really in pdfarranger. Lacking the time to dig into other packages at the moment, there is nothing I can do about this right now.

I'll close this as duplicate but feel free to comment / reopen if there is anything else.

The root cause is python-xmp-toolkit: https://bugzilla.redhat.com/show_bug.cgi?id=1793508
Which may actually be caused by a bug in exempi, I'm not sure at the moment: https://gitlab.freedesktop.org/libopenraw/exempi/-/issues/20

*** This bug has been marked as a duplicate of bug 1841656 ***


Note You need to log in before you can comment on or make changes to this bug.