Bug 489208 - traceback on yum.misc.unique()
Summary: traceback on yum.misc.unique()
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-08 16:32 UTC by Jeroen van Meeuwen
Modified: 2014-01-21 23:08 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-03-08 16:49:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
snippet of log with traceback on yum.misc.unique() (1.17 KB, text/plain)
2009-03-08 16:32 UTC, Jeroen van Meeuwen
no flags Details

Description Jeroen van Meeuwen 2009-03-08 16:32:21 UTC
Created attachment 334442 [details]
snippet of log with traceback on yum.misc.unique()

Description of problem:

in branch yum-3_2_X, commit 12d9d60702a41a55bce19e01bb3151cfff0c31f0 [1] seems to have caused situations in which u is referenced before it is defined, causing a traceback[2] when using yum.misc.unique().

[1] http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=12d9d60702a41a55bce19e01bb3151cfff0c31f0

[2] http://www.kanarip.com/revisor/20090308/rawhide-i386-respin/log/revisor-rawhide-i386-respin.log (near the end, snippet attached)

Version-Release number of selected component (if applicable):

yum.noarch 0:3.2.21-12.fc11

How reproducible:

Run revisor in respin mode so that it calls yum.misc.unique()

Steps to Reproduce:
1. Create a transaction with a few packages (~2400)
2. Get all the requirements for these packages, similar to:

    reqs = []
    for txmbr in yumobj.tsInfo.getMembers():
        reqs.append(txmbr.po.requires)
    reqs = yum.misc.unique(reqs)

3. A traceback is the result

Comment 1 James Antill 2009-03-08 16:49:22 UTC
This should be fixed in commit: a0cd169628adcabc80575eb22447a9cf091e8251

.,..basically just s/del u/pass/

Comment 2 Jeroen van Meeuwen 2009-03-08 17:15:57 UTC
You're the best, thanks!


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