Hello,
I have ssh set up and created and maintain this package.
Today I attempted to push a change to bump the package version and found that I am unable to push:
---
✔ ~/src/slack-desktop-wayland [master ↑·1|✔]
16:22 $ git push
aur@aur.archlinux.org: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
---
Also weirdly, I cannot clone it:
---
$ git clone ssh://aur@aur.archlinux.org/slack-desktop-wayland.git
Cloning into 'slack-desktop-wayland'...
aur@aur.archlinux.org: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
---
I have not changed anything on my end. I double and triple checked my SSH keys. I also double checked that I'm not on any VPN or tunnel.
Further, I can still use the ssh query interface, and I am still able to log in and it still shows me as the owner of this package:
---
✔ 16:23 $ ssh aur@aur.archlinux.org help
Commands:
adopt <name> Adopt a package base.
disown <name> Disown a package base.
flag <name> <comment> Flag a package base out-of-date.
git-receive-pack Internal command used with Git.
git-upload-pack Internal command used with Git.
help Show this help message and exit.
list-repos List all your repositories.
restore <name> Restore a deleted package base.
set-comaintainers <name> [...] Set package base co-maintainers.
set-keywords <name> [...] Change package base keywords.
unflag <name> Remove out-of-date flag from a package base.
unvote <name> Remove vote from a package base.
vote <name> Vote for a package base.
✔ ~/src/slack-desktop-wayland [master ↑·1|✔]
16:49 $ ssh aur@aur.archlinux.org list-repos
slack-desktop-wayland
---
I know that my ssh keys and setup are working because it used to function with the AUR and I continue to use it every hour of the day at work.
Any idea what is going wrong? Can you please help me fix this?
Also, I am away for a few days at the start of next week - could you please prevent any "orphaned package" requests while my access issues are fixed?
Regards,
Chris