Learn more about these different git repos.
Other Git URLs
If ~/.config/copr doesn't exist, don't fail with python jargon errors.
Instead, provide an interactive way to set up the file. Point the user to the API page. Then the user can press enter once they have copied the information onto their clipboard at which point copr-cli will run $EDITOR ~/.config/copr so the user can paste the information and begin working.
$EDITOR ~/.config/copr
Thank you for the report, and idea.
copr-cli build asdfadfa/asdfaf asdfa.src.rpm ================= WARNING: ======================= File '~/.config/copr' is missing or incorrect. See documentation: man copr-cli. Any operation requiring credentials will fail! ================================================== Hint: There is no config file: /root/.config/copr Error: Operation requires api authentication
This is not "python jargon error" at least, but better wording could be implemented ... more concrete ideas?
I would be against "interactive" automation (too much hassle for low gain, security, etc.). But I'm definitely for better help text that can be copy-pasted...
If in doubt a simple link to the token page would help.
As for python jargon I got a few python error messages when I launched. I can't seem to replicate it now by moving the copr cli config file out of the way.
Edited by mistake by @praiskup, sorry.
The thing is we are not sure what Copr user wants to work with. Perhaps we can put there something like "If you want to work with Fedora Copr, go to https://copr.fedorainfracloud.org/api/".
Also, in the next release we'll have a GSSAPI support, so it will be enough to run fkinit (and no ~/.config/copr will be needed).
fkinit
If there's a python traceback, please fill a separate issue. This shouldn't happen, I fully agree here.
Ah well if it's changing soon then there's no need to change the current setup.
On Mon, Mar 21, 2022, 9:14 PM Pavel Raiskup pagure@pagure.io wrote:
praiskup added a new comment to an issue you are following: `` If in doubt a simple link to the token page would help. The thing is we are not sure what Copr user wants to work with. Perhaps we can put there something like "If you want to work with Fedora Copr, go to https://copr.fedorainfracloud.org/api/". Also, in the next release we'll have a GSSAPI support, so it will be enough to run fkinit (and no ~/.config/copr will be needed). As for python jargon I got a few python error messages when I launched. I can't seem to replicate it now by moving the copr cli config file out of the way. If there's a python traceback, please fill a separate issue. This shouldn't happen, I fully agree here. `` To reply, visit the link below or just reply to this email https://pagure.io/copr/copr/issue/2126
praiskup added a new comment to an issue you are following: ``
``
To reply, visit the link below or just reply to this email https://pagure.io/copr/copr/issue/2126
Metadata Update from @praiskup: - Issue tagged with: RFE
This issue has been migrated to GitHub: https://github.com/fedora-copr/copr/issues/2126
Metadata Update from @nikromen: - Issue close_status updated to: MIGRATED - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.