alflanagan
commented
8 years ago I've seen the same issue with python2-inotify and python2-jinja2. (Using version 4.3.2, installed from Fedora 24 repo). Here's the command-line install for python2-inotify:
sudo dnf install python2-inotify
[sudo] password for aflanagan:
Last metadata expiration check: 0:07:41 ago on Tue Oct 11 10:36:12 2016.
Dependencies resolved.
===============================================================================================================================================
Package Arch Version Repository Size
===============================================================================================================================================
Installing:
python2-inotify noarch 0.9.6-6.fc24 updates 56 k
replacing python-inotify.noarch 0.9.6-4.fc24
Transaction Summary
===============================================================================================================================================
Install 1 Package
Total download size: 56 k
Installed size: 264 k
Is this ok [y/N]: y
Downloading Packages:
python2-inotify-0.9.6-6.fc24.noarch.rpm 126 kB/s | 56 kB 00:00
-----------------------------------------------------------------------------------------------------------------------------------------------
Total 56 kB/s | 56 kB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Installing : python2-inotify-0.9.6-6.fc24.noarch 1/2
Obsoleting : python-inotify-0.9.6-4.fc24.noarch 2/2
Verifying : python2-inotify-0.9.6-6.fc24.noarch 1/2
Verifying : python-inotify-0.9.6-4.fc24.noarch 2/2
Installed:
python2-inotify.noarch 0.9.6-6.fc24 The obvious conclusion being that it's failing to handle obsoleted packages.
rluzynski
timlau
For the past few weeks, whenever I try to install updates with Yumex-DNF, I get an error like this:
This appears similar to issue #123. Adding an option to exempt a package from an update could still be useful -- however, in my case at least, the DNF commandline was able to handle the updates without errors or warnings, so I don't think removing the package from the update would have been the best solution. In this latest instance for me, it seems like issue was that the package
pygpgmewas renamed topython2-pygpgme.