Curl doesn't know anything about ~/.config/copr, which supposed to be
used by copr-cli (and later by copr client libs). To use curl you should
provide credentials explicitly: curl --user login:token ... .
Preferable way is to use ``copr-cli build`` which utilize
~/.config/copr so you don't need to provide credentials each time.
On 09/13/2014 03:56 PM, Mark Reynolds wrote:
Using "http" instead of "curl" worked:
http --auth <login>:<password> POST
If there's a different preferred way to post srpm's I would be interested to hear
On 09/12/2014 06:29 PM, Mark Reynolds wrote:
> I'm trying to upload a srpm to copr by using:
> curl --data
> "error": "Login invalid/expired. Please visit
get or renew your API token.",
> "output": "notok"
> I did setup ~/.config/copr file correctly according to
> First I'm not sure if this is the best way to upload a srpm, second, the
> issue might be because my shell id is "mareynol" but my fedora/copr
> account is "mreynolds". I know this uid discrepancy caused issues with
> the fedora folks, where they had to do some kind of alias for mareynol
> -> mreynolds.
> Any help would be appreciated.