Description of problem: I can't reassign my packages to my colleague. I tried to reassign them by: pkgdb-cli --user mmaslano unorphan --owner jplesnik name_of_package I used the same approach for giving her acl on my packages, but the old script didn't work either. Authentication stopped failing, when I removed the .fedora/.fedora-session and run twice: pkgdb-cli request --user mmaslano --cancel perl-pip watchcommits I don't think it should work like that. Also time ago worked script with parameters --user mmaslano --password my_password, which is not true anymore even if help insist on using password on commandline. Something is really wrong. Version-Release number of selected component (if applicable): packagedb-cli-1.5.0-1.fc19.noarch How reproducible: pkgdb-cli --user mmaslano --debug unorphan --owner jplesnik perl-pip INFO:pkgdb:user : mmaslano INFO:pkgdb:package : perl-pip INFO:pkgdb:branch : devel INFO:pkgdb:owner : jplesnik DEBUG:pkgdb:Packages: perl-pip INFO:pkgdb:Unorphaning package perl-pip on branch devel Error: Auth was requested but no way to perform auth was given. Please set username and password or session_id before calling this function with auth=True Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
For me it is broken for a user with a different username than my fedora username, but it works if the usernames match. But it might also be something else, why it works/does not work for the different users: $ LANG=C pkgdb-cli --debug orphan --retire mod_mono devel INFO:pkgdb:user : None INFO:pkgdb:package : mod_mono INFO:pkgdb:branch : devel INFO:pkgdb:all : False INFO:pkgdb:retire : True DEBUG:pkgdb:Orphan mod_mono in devel INFO:pkgdb:Orphaning package mod_mono on branch devel Error: Auth was requested but no way to perform auth was given. Please set username and password or session_id before calling this function with auth=True Would be nice to fix this soon, because fedpkg from testing already tries to call fedpkg-cli to retire packages.
Does pkgdb-cli prompt for username and password in this case and still refuse to authenticate you or does it never give you that chance? If the latter, pkgd-cli probably needs to catch the AuthError, prompt for (username: optional) and password and then try again with that. If the former, then it's a bug in python-fedora. I've heard of that sporadically but haven't been able to diagnose it first hand. We'll cross that bridge if that's what this is.
(In reply to Toshio Ernie Kuratomi from comment #2) > Does pkgdb-cli prompt for username and password in this case and still > refuse to authenticate you or does it never give you that chance? If the > latter, pkgd-cli probably needs to catch the AuthError, prompt for > (username: optional) and password and then try again with that. I do not get a password or username prompt when I try to run it as a different user. The output in comment:1 is all I get.
I agree, my user on computer is different than FAS name.
Created attachment 791436 [details] Fix a few bugs in get_client_authentified Well, I found a few bugs that might be this one. Could you try this patch and see if things work afterwards?
(In reply to Toshio Ernie Kuratomi from comment #5) > Created attachment 791436 [details] > Fix a few bugs in get_client_authentified > > Well, I found a few bugs that might be this one. Could you try this patch > and see if things work afterwards? Is there any authenticated feature that can be used to test this? There is no package I need to retire right now, but I could unretire and retire a package if there is no other way.
Giving the global --test switch should operate on the staging database instead of the production database. You can try that.
(In reply to Toshio Ernie Kuratomi from comment #7) > Giving the global --test switch should operate on the staging database > instead of the production database. You can try that. With the patch, it asks me for a password then, but I do not know which to use there.
You can check and set a different password at https://admin.stg.fedoraproject.org/accounts/ The FAS database in staging is periodically synced from production so initially it would be the same password as you use in production.
I was just able to retire a package in production, therefore the patch fixes this issue for me.
Thanks for the patch Toshio, I'll make a bugfix release and push an update with this change.
packagedb-cli-1.5.1-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/packagedb-cli-1.5.1-1.fc20
packagedb-cli-1.5.1-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/packagedb-cli-1.5.1-1.fc19
packagedb-cli-1.5.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/packagedb-cli-1.5.1-1.fc18
Package packagedb-cli-1.5.1-1.fc20: * should fix your issue, * was pushed to the Fedora 20 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.5.1-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-15872/packagedb-cli-1.5.1-1.fc20 then log in and leave karma (feedback).
packagedb-cli-1.6.0-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/packagedb-cli-1.6.0-1.el5
packagedb-cli-1.6.0-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/packagedb-cli-1.6.0-1.fc19
packagedb-cli-1.6.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/packagedb-cli-1.6.0-1.fc18
packagedb-cli-1.6.0-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/packagedb-cli-1.6.0-1.fc20
packagedb-cli-1.6.0-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/packagedb-cli-1.6.0-1.el6
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
packagedb-cli-1.6.0-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
packagedb-cli-1.6.0-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
packagedb-cli-1.6.0-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
packagedb-cli-1.6.0-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
packagedb-cli-1.6.0-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.