Created attachment 331933 [details] Traceback from package-cleanup Description of problem: If the versionlock yum module is enabled, package-cleanup --dupes crashes with a huge traceback and the error "RuntimeError: maximum recursion depth exceeded" Version-Release number of selected component (if applicable): yum-versionlock-1.1.19-1.fc10.noarch yum-utils-1.1.19-1.fc10.noarch yum-3.2.21-2.fc10.noarch How reproducible: Always Steps to Reproduce: 1. Enable versionlock module 2. Run package-cleanup --dupes Actual results: Crash with traceback Expected results: List of dupes (or not as the case may be) Additional info: The traceback produced is attached
Created attachment 333634 [details] package-cleanup --leaves 2>&1 same here with --leaves on F-9
Workaround: yum erase yum-versionlock
What was in your versionlock.conf file for locklist?
I've since disabled, but at time of error (on older Fedora here), think it was these: 17:17]curtis@barleycorn/etc/yum/pluginconf.d$ grep . versionlock.*.rpmsave versionlock.conf.rpmsave:[main] versionlock.conf.rpmsave:enabled=1 versionlock.conf.rpmsave:locklist = /etc/yum/pluginconf.d/versionlock.list versionlock.list.rpmsave:postfix-2.3.3-2
[blewis@dominus tmp]$ cat /etc/yum/pluginconf.d/versionlock.* [main] enabled = 1 locklist = /etc/yum/pluginconf.d/versionlock.list # Uncomment this to lock out "upgrade via. obsoletes" etc. (slower) # follow_obsoletes = 1 amarok-1.4.10-1.fc10.i386 amarok-visualisation-1.4.10-1.fc10.i386
Benjamin, Can you make this happen, too?
I'm not sure what you mean. If you are referring to package-cleanup not working with versionlock enabled then yes I can. [Sorry for the delay in replying, I missed the bugzilla e-mail and forgot about this bug :(]
This is probably fixed by upstream commit: http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=5216a27d35d60e46f028b1fbba58acae5b9e79d2 can someone verify?
James, I confirm that applying the patch on F10's yum fixed this bug. Thanks.
*** Bug 516050 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is fixed in yum-3.2.24-2.fc10 which is in F10 updates.