Bug 918909

Summary: update operation terminates immediately
Product: [Fedora] Fedora Reporter: Petr Pisar <ppisar>
Component: packagedb-cliAssignee: Pierre-YvesChibon <pingou>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: pingou
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-16 01:32:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Petr Pisar 2013-03-07 08:28:03 UTC
I cannot approve permission for an user, it terminates with Namespace() message immediately even without connect to the server:

$ pkgdb-cli --debug update --approve perl-CPANPLUS commit jplesnik devel
INFO:pkgdb:user      : None
INFO:pkgdb:package   : perl-CPANPLUS
INFO:pkgdb:acl       : commit
INFO:pkgdb:requester : jplesnik
INFO:pkgdb:branch    : devel
INFO:pkgdb:approve   : True
INFO:pkgdb:deny      : False
Namespace(action='commit', approve=True, branch='devel', debug=True, deny=False, func=<function do_update at 0x274dd70>, nocolor=False, package='perl-CPANPLUS', password=None, test=False, user='jplesnik', username=None, verbose=False)

$ echo $?
0

$ rpm -qf $(type -p pkgdb-cli)
packagedb-cli-1.4.1-1.fc18.noarch

Comment 1 Pierre-YvesChibon 2013-03-07 08:39:20 UTC
Yes sorry about that, it's basically the bug you're referring to in: https://bugzilla.redhat.com/show_bug.cgi?id=916581#c5

It's fixed in git but life got between the git repo and the spec file :)

Comment 2 Petr Pisar 2013-03-07 08:46:25 UTC
Thanks. The git tree works.

Comment 3 Pierre-YvesChibon 2013-03-07 08:50:06 UTC
I'm back-porting the fix as patch into the rpm, build are running :)

Comment 4 Fedora Update System 2013-03-07 09:02:18 UTC
packagedb-cli-1.4.1-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/packagedb-cli-1.4.1-2.fc17

Comment 5 Fedora Update System 2013-03-07 09:02:39 UTC
packagedb-cli-1.4.1-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/packagedb-cli-1.4.1-2.fc18

Comment 6 Fedora Update System 2013-03-07 09:03:00 UTC
packagedb-cli-1.4.1-2.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/packagedb-cli-1.4.1-2.el5

Comment 7 Fedora Update System 2013-03-07 09:03:26 UTC
packagedb-cli-1.4.1-2.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/packagedb-cli-1.4.1-2.el6

Comment 8 Fedora Update System 2013-03-07 23:59:57 UTC
Package packagedb-cli-1.4.1-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing packagedb-cli-1.4.1-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-3527/packagedb-cli-1.4.1-2.fc18
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2013-03-16 01:32:53 UTC
packagedb-cli-1.4.1-2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2013-03-16 01:41:48 UTC
packagedb-cli-1.4.1-2.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2013-04-04 16:38:39 UTC
packagedb-cli-1.4.1-2.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2013-04-04 16:44:55 UTC
packagedb-cli-1.4.1-2.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.