Bug 901614 - [abrt] fedup-0.7.2-1.fc17: callback.py:142:procConflictPo:NameError: global name 'po' is not defined
Summary: [abrt] fedup-0.7.2-1.fc17: callback.py:142:procConflictPo:NameError: global n...
Keywords:
Status: CLOSED DUPLICATE of bug 895576
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a710eb89a0d83fdf0df58e82775...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-18 16:25 UTC by Aaron Gee
Modified: 2013-01-23 16:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-23 16:20:06 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (1.52 KB, text/plain)
2013-01-18 16:25 UTC, Aaron Gee 		no flags Details
File: core_backtrace (930 bytes, text/plain)
2013-01-18 16:25 UTC, Aaron Gee 		no flags Details
File: environ (3.31 KB, text/plain)
2013-01-18 16:25 UTC, Aaron Gee 		no flags Details
File: smolt_data (4.08 KB, text/plain)
2013-01-18 16:25 UTC, Aaron Gee 		no flags Details
View All

Description Aaron Gee 2013-01-18 16:25:38 UTC 
Description of problem:
Upgradeing from Fedora 17 with non standard file system setup with fedup causes the process to hang.

File System;

/home <-- ACHI RAID1 partition
/ <-- Software Raid 0 partition


Version-Release number of selected component:
fedup-0.7.2-1.fc17

Additional info:
cmdline:        /usr/bin/python /usr/bin/fedup-cli --network 18 --debuglog fedupdebug.loh
dso_list:       yum-3.4.3-30.fc17.noarch
executable:     /usr/bin/fedup-cli
kernel:         3.3.4-5.fc17.x86_64
uid:            0

Truncated backtrace:
callback.py:142:procConflictPo:NameError: global name 'po' is not defined

Traceback (most recent call last):
  File "/usr/bin/fedup-cli", line 330, in <module>
    main(args)
  File "/usr/bin/fedup-cli", line 275, in main
    pkgs = download_packages(f)
  File "/usr/bin/fedup-cli", line 57, in download_packages
    updates = f.build_update_transaction(callback=output.DepsolveCallback(f))
  File "/usr/lib/python2.7/site-packages/fedup/download.py", line 185, in build_update_transaction
    (rv, msgs) = self.buildTransaction(unfinished_transactions_check=False)
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1124, in buildTransaction
    (rescode, restring) = self.resolveDeps()
  File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 897, in resolveDeps
    (checkdep, errormsgs) = self._processConflict(*conflict)
  File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 759, in _processConflict
    self._dscb_procConflict(po, niceformatneed)
  File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 745, in _dscb_procConflict
    self.dsCallback.procConflictPo(po, niceformatneed)
  File "/usr/lib/python2.7/site-packages/fedup/callback.py", line 142, in procConflictPo
    self.log.debug('CONFLICT: %s → %s', po, formatted_conflict)
NameError: global name 'po' is not defined

Local variables in innermost frame:
self: <fedup.textoutput.DepsolveCallback object at 0x7f9a29c2a1d0>
formatted_conflict: 'sysvinit-tools < 2.88-8'
name: <YumAvailablePackageSqlite : util-linux-2.22.1-2.4.fc18.x86_64 (0x4216410)>

Potential duplicate: bug 895576
Comment 1 Aaron Gee 2013-01-18 16:25:41 UTC 
Created attachment 682515 [details]
File: backtrace
Comment 2 Aaron Gee 2013-01-18 16:25:44 UTC 
Created attachment 682516 [details]
File: core_backtrace
Comment 3 Aaron Gee 2013-01-18 16:25:46 UTC 
Created attachment 682517 [details]
File: environ
Comment 4 Aaron Gee 2013-01-18 16:25:48 UTC 
Created attachment 682518 [details]
File: smolt_data
Comment 5 Josh Cogliati 2013-01-22 20:22:11 UTC 
These are the lines that cause the bug.

I am guessing that either "name" should be "po", or "po" should be "name"
    def procConflictPo(self, name, formatted_conflict):
        self.log.debug('CONFLICT: %s → %s', po, formatted_conflict)
Comment 6 Josh Cogliati 2013-01-22 20:32:03 UTC 
Duplicate of Bug 895576
Comment 7 Will Woods 2013-01-23 16:20:06 UTC 
I thought ABRT was supposed to detect duplicate bugs. Alas.

*** This bug has been marked as a duplicate of bug 895576 ***
Note You need to log in before you can comment on or make changes to this bug.