Bug 215450

Summary: Reference invalid variable in depSolver.py
Product: Red Hat Enterprise Linux 4 Reporter: Matthew Booth <mbooth>
Component: up2dateAssignee: Clifford Perry <cperry>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Brandon Perkins <bperkins>
Severity: high Docs Contact:
Priority: medium    
Version: 4.4CC: cperry
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-22 16:31:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
Patch fixing invalid variable reference in depSolver.py none

Description Matthew Booth 2006-11-14 01:48:13 UTC
Description of problem:
I don't have a reproducer for this, and I don't have access to the machine I hit
it on. The problem manifested itself as a python backtrace in the code handling
obsoletes dependency resolution. I hit updating both seamonkey and wireshark
from RHEL4 U2 (ish) to RHEL4 U4 + updates. I don't have the original backtrace
either, but I did get the customer to mail the patch to me. I have done similar
updates before without hitting this problem, so there's probably something
unusual about this particular setup. I couldn't tell you what it is, though.

The code in question is very obviously bogus as it references a variable which
isn't in scope. Note that very similar code is also obviously broken at other
points in depSolver.py, but I didn't hit that and didn't fix it.

I've put severity to high because it's a total show stopper when you hit it.

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

Comment 1 Matthew Booth 2006-11-14 01:48:13 UTC
Created attachment 141126 [details]
Patch fixing invalid variable reference in depSolver.py

Comment 3 Red Hat Bugzilla 2007-04-12 01:43:07 UTC
User bnackash@redhat.com's account has been closed