Bug 470690 - global name 'os' is not defined in yum-complete-transaction
Summary: global name 'os' is not defined in yum-complete-transaction
Keywords:
Status: CLOSED DUPLICATE of bug 470458
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-08 22:11 UTC by Matěj Cepl
Modified: 2018-04-11 16:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-09 06:11:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matěj Cepl 2008-11-08 22:11:03 UTC
Description of problem:

[root@viklef i386]# yum-complete-transaction 
Loaded plugins: kernel-module, refresh-packagekit, versionlock
Excluding Packages in global exclude list
Finished
Reading version lock configuration
There are 1 outstanding transactions to complete. Finishing the most recent one
The remaining transaction had 4 elements left to run
Nothing in the unfinished transaction to cleanup.
Cleaning up completed transaction file
Traceback (most recent call last):
  File "/usr/sbin/yum-complete-transaction", line 208, in <module>
    util = YumCompleteTransaction()
  File "/usr/sbin/yum-complete-transaction", line 115, in __init__
    self.main()
  File "/usr/sbin/yum-complete-transaction", line 189, in main
    self.clean_up_ts_files(timestamp, self.conf.persistdir)
  File "/usr/sbin/yum-complete-transaction", line 123, in clean_up_ts_files
    if os.path.exists(f):
NameError: global name 'os' is not defined

Version-Release number of selected component (if applicable):
yum-utils-1.1.18-1.fc10.noarch

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Tim Lauridsen 2008-11-09 06:11:06 UTC

*** This bug has been marked as a duplicate of bug 470458 ***


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