Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 485578 - F10: package-cleanup --dupes crashes when versionlock module is enabled
Summary: F10: package-cleanup --dupes crashes when versionlock module is enabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: 10
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 516050 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-14 19:27 UTC by Benjamin Lewis
Modified: 2014-01-21 23:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-18 11:59:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Traceback from package-cleanup (deleted)
2009-02-14 19:27 UTC, Benjamin Lewis 		no flags Details
package-cleanup --leaves 2>&1 (deleted)
2009-03-01 03:47 UTC, Curtis Doty 		no flags Details
View All

Description Benjamin Lewis 2009-02-14 19:27:35 UTC 
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
Comment 1 Curtis Doty 2009-03-01 03:47:33 UTC 
Created attachment 333634 [details]
package-cleanup --leaves 2>&1

same here with --leaves on F-9
Comment 2 Curtis Doty 2009-03-01 03:49:33 UTC 
Workaround: yum erase yum-versionlock
Comment 3 seth vidal 2009-03-06 18:31:06 UTC 
What was in your versionlock.conf file for locklist?
Comment 4 Curtis Doty 2009-03-07 01:18:29 UTC 
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
Comment 5 Benjamin Lewis 2009-03-08 13:03:00 UTC 
[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
Comment 6 seth vidal 2009-03-09 18:41:51 UTC 
Benjamin,
 Can you make this happen, too?
Comment 7 Benjamin Lewis 2009-05-17 19:04:17 UTC 
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 :(]
Comment 8 James Antill 2009-06-22 05:53:14 UTC 
 This is probably fixed by upstream commit:

http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=5216a27d35d60e46f028b1fbba58acae5b9e79d2

can someone verify?
Comment 9 Michal Schmidt 2009-06-22 06:45:07 UTC 
James,
I confirm that applying the patch on F10's yum fixed this bug. Thanks.
Comment 10 seth vidal 2009-08-06 19:58:14 UTC 
*** Bug 516050 has been marked as a duplicate of this bug. ***
Comment 11 Bug Zapper 2009-11-18 09:51:38 UTC 
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
Comment 12 Michal Schmidt 2009-11-18 11:59:43 UTC 
This is fixed in yum-3.2.24-2.fc10 which is in F10 updates.
Note You need to log in before you can comment on or make changes to this bug.