Bug 726848 - [abrt] fedpkg-0.5.9.2-1.fc15: fedpkg:670:retire:TypeError: push() takes exactly 1 argument (0 given)
Summary: [abrt] fedpkg-0.5.9.2-1.fc15: fedpkg:670:retire:TypeError: push() takes exact...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-packager
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1fc8e3edaf7b49ff65a0e1bd243...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-29 22:50 UTC by Orion Poplawski
Modified: 2013-01-10 06:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-22 23:25:53 UTC
Type: ---


Attachments (Terms of Use)

Description Orion Poplawski 2011-07-29 22:50:10 UTC
abrt version: 2.0.3
architecture:   i686
cmdline:        
comment:        fedpkg retire -p 'a  message'
component:      fedora-packager
executable:     /usr/bin/fedpkg
kernel:         2.6.38.8-35.fc15.i686.PAE
os_release:     Fedora release 15 (Lovelock)
package:        fedpkg-0.5.9.2-1.fc15
reason:         fedpkg:670:retire:TypeError: push() takes exactly 1 argument (0 given)
time:           Fri Jul 29 16:47:22 2011
uid:            1744
username:       orion

backtrace:
:fedpkg:670:retire:TypeError: push() takes exactly 1 argument (0 given)
:
:Traceback (most recent call last):
:  File "/usr/bin/fedpkg", line 1495, in <module>
:    args.command(args)
:  File "/usr/bin/fedpkg", line 670, in retire
:    push()
:TypeError: push() takes exactly 1 argument (0 given)
:
:Local variables in innermost frame:
:args: Namespace(command=<function retire at 0x844d56c>, dist=None, msg='Upstream is essentially dead - gui stuck on qt3 and buggy', path='/export/home/orion/fedora/pdfedit', push=True, q=False, user=None, v=False)

Comment 1 Jesse Keating 2011-08-02 18:50:56 UTC
This is already fixed upstream in the re-write and split out.  I'll be building a package from that soon.

Comment 2 Orion Poplawski 2011-11-22 23:25:53 UTC
I'm going to assume this is fixed.  Don't retire a lot of packages... :)


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