Description of problem: I got a traceback from yum-complete-transaction: 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 195, 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 How reproducible: Don't know. Steps to Reproduce: 1.I just ran 'yum-complete-transaction' after interrupting an update. Actual results: Complete output attached.
Created attachment 322836 [details] yum-complete-transaction-traceback.txt
Looking more closely I see that yum-utils was one of the packages updated, so actually it was yum-utils-1.1.17-2.fc10 that gave the traceback.
was yum being updated, too, when your transaction died?
also try this yum-complete-transaction and tell me if it fixes it http://yum.baseurl.org/gitweb?p=yum-utils.git;a=blob;f=yum-complete-transaction.py;h=17ef3c8979a6493e62c3099768fc1a4b74a2f0da;hb=19a9ab41fc1f3eb2051287c870521edbae3f98a1 or at least changes the problem.
*** Bug 470612 has been marked as a duplicate of this bug. ***
*** Bug 470624 has been marked as a duplicate of this bug. ***
*** Bug 470690 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > also try this yum-complete-transaction > > and tell me if it fixes it > > http://yum.baseurl.org/gitweb?p=yum-utils.git;a=blob;f=yum-complete-transaction.py;h=17ef3c8979a6493e62c3099768fc1a4b74a2f0da;hb=19a9ab41fc1f3eb2051287c870521edbae3f98a1 > > or at least changes the problem. Hi, it did solve the issue for me. I had 9 'outstanding' transactions to complete (lot of them being from 2007) and everything is finally cleaned up after executing your modified yum-complete-transaction with --cleanup-only parameter (otherwise it was trying to reinstall 1200 packages). I wonder if it's not some leftovers of past preupgrade interrupted processes that are now taken into account because there was some fc7 in the packages it was checking.
I had the power go while updating tonight - the only "package/yum" related update being gnome-packagekit-0.3.9-8.fc10.i386. Like the reporter, I had the same traceback from yum-complete-transaction. Similarly, running the version from git "works" (sans command-line arguments) but leaves me wondering if my system is in a sane state... nic
your system should be. when in doubt - run: package-cleanup --problems and see what shows up.
I don't know if yum was being updated when the transaction failed. (In reply to comment #4) > also try this yum-complete-transaction > and tell me if it fixes it Yes, this fixes it.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 474406 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > also try this yum-complete-transaction > > and tell me if it fixes it > > http://yum.baseurl.org/gitweb?p=yum-utils.git;a=blob;f=yum-complete-transaction.py;h=17ef3c8979a6493e62c3099768fc1a4b74a2f0da;hb=19a9ab41fc1f3eb2051287c870521edbae3f98a1 > > or at least changes the problem. This fixes for me: [root@tlondon Download]# python yum-complete-transaction.py --cleanup-only Loaded plugins: fastestmirror, refresh-packagekit Loading mirror speeds from cached hostfile * rawhide: mirrors.kernel.org Cleaning up unfinished transaction journals Cleaning up 2008-12-03.06:22.00 [root@tlondon Download]#
*** Bug 475252 has been marked as a duplicate of this bug. ***
Also for me..
(In reply to comment #4) > also try this yum-complete-transaction > > and tell me if it fixes it > > http://yum.baseurl.org/gitweb?p=yum-utils.git;a=blob;f=yum-complete-transaction.py;h=17ef3c8979a6493e62c3099768fc1a4b74a2f0da;hb=19a9ab41fc1f3eb2051287c870521edbae3f98a1 > > or at least changes the problem. Fixes it for me here (I also saw the problem on updating a bunch, probably including yum-utils, and then on). Saw it on yum-utils-1.1.18-2.fc11.noarch, with python-2.6-1.fc11.x86_64
closing -> upstream
yum-utils-1.1.19-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/yum-utils-1.1.19-1.fc10
yum-utils-1.1.19-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/yum-utils-1.1.19-1.fc9
*** Bug 477075 has been marked as a duplicate of this bug. ***
yum-utils-1.1.19-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
yum-utils-1.1.19-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.