On 1/27/19 6:13 AM, Hagar wrote:
On 27/1/19 7:01 pm, stefan-husmann@t-online.de wrote:
Hello,
Can someone please have a look on what happens on server side?
I want to update gtkhtml4 in AUR adding a long proposed (in the comments) patch.
This fails with
fatal: unable to access 'https://aur.archlinux.org/gtkhtml4.git/': The requested URL returned error: 403
I maybe do not see the obvious, but I can update my other packages without problems, but not thi one, which I newly adopted.
Best Regards
Stefan Its not well documented - but edit the .git/config file an change the url from https to ssh:
look at the aur page for the package for the exact url.
I hit this problem just last week.
It is pretty well documented. - We repeatedly document the use of ssh cloning everywhere in the wiki page describing the submission process, and make no mention of using https:// - When logged into the AUR and viewing a package that you maintain, it lists two clone urls: https:// and ssh:// -- and right after the https:// link it specifies in parentheses, "read-only". Read-only means you cannot write to it. - When viewing a package that you do not maintain or when not even logged into the AUR, only the https:// clone url is referenced, and it still states "read-only". - Other websites which support pushing over https:// will require you to type in your username and password every time you do, which is unfriendly and I don't understand why anyone would ever want to do so in the first place if they could just use ssh. -- Eli Schwartz Bug Wrangler and Trusted User