Red Hat Bugzilla – Bug 984305
fedup doesn't remove obsoleted packages
Last modified: 2013-12-06 16:02:58 EST
Description of problem
Fedup doesn't remove packages which were declared as obsolete (and so are not
included in the new fedora release). This leads to dependency conflicts in rpm
Version-Release number of selected component (if applicable)
Tried once, given the nature of the issue guessing "always".
Steps to Reproduce
1. on Fedora 18, install glusterfs-swift
2. update to Fedora 19 via fedup
3. run 'yum check'
yum check (which is btw run in every yum update) fails:
# yum check
Loaded plugins: etckeeper, langpacks, ps, refresh-packagekit, verify, versionlock
glusterfs-swift-3.3.1-15.fc18.noarch has installed conflicts openstack-swift: openstack-swift-1.8.0-2.fc19.noarch
glusterfs-swift-3.3.1-15.fc18.noarch has missing requires of glusterfs = ('0', '3.3.1', '15.fc18')
Error: check all
Package glusterfs-swift is not installed. Since it was removed in fedora 19,
fedup make sure this package is removed.
 from glusterfs changelog:
> * Mon Jul 8 2013 Kaleb S. KEITHLEY <kkeithle[at]redhat.com> - 3.4.0-0.9.beta4
> - add Obsolete: glusterfs-swift where we use openstack-swift
> - prerelease 3.4.0beta4 for oVirt/vdsm dependencies in Fedora19
For the fedup upgrade, I used fedup from fedora 18 but I filled this BZ for f19
to last longer since both fedora versions should contain the same fedup version
(checked via fedpkg).
# grep fedup yum.log
Feb 17 03:16:23 Installed: fedup-0.7.3-0.git20130128.fc17.noarch
May 15 23:58:19 Updated: fedup-0.7.3-4.fc18.noarch
# rpm -q fedup
Could you attach your fedup.log and upgrade.log?
Created attachment 783036 [details]
(In reply to Will Woods from comment #1)
> Could you attach your fedup.log and upgrade.log?
both files attached
note that fedup.log also contains entries from previous upgrade, I didn't edit it in any way
In my testing, fedup definitely removes obsoleted packages when the Obsoletes: entries are correct.
The problem was that your upgrade was installing glusterfs-3.4.0-0.8.beta4.fc19, which didn't have "Obsoletes: glusterfs-swift". So this was a packaging problem with glusterfs, not a fedup bug.
glusterfs has already fixed the packaging problem, so there's nothing else to do there.
(whoops, wrong resolution - sorry about that)