Bug 1707570 - Obsolete pix < 1.8.2-2
Summary: Obsolete pix < 1.8.2-2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-obsolete-packages
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-07 19:35 UTC by Leszek Matok
Modified: 2019-05-23 17:48 UTC (History)
3 users (show)

Fixed In Version: fedora-obsolete-packages-30-43
Clone Of:
Environment:
Last Closed: 2019-05-23 17:48:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Leszek Matok 2019-05-07 19:35:10 UTC
dnf system-upgrade spits:
 Problem 1: package pix-1.8.2-1.fc29.x86_64 requires libexiv2.so.26()(64bit), but none of the providers can be installed
  - exiv2-libs-0.26-12.fc29.x86_64 does not belong to a distupgrade repository
  - problem with installed package pix-1.8.2-1.fc29.x86_64

Which prevents F29->F30 upgrade.

Comment 1 Leszek Matok 2019-05-11 15:26:52 UTC
I've noticed new fedora-obsolete-packages fixing other upgrade errors I've seen, so I guess these belong there as well?

Comment 2 Fedora Update System 2019-05-21 11:48:24 UTC
fedora-obsolete-packages-30-43 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-2213140151

Comment 3 Fedora Update System 2019-05-22 01:44:13 UTC
fedora-obsolete-packages-30-43 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2213140151

Comment 4 Fedora Update System 2019-05-23 17:48:50 UTC
fedora-obsolete-packages-30-43 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.


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