Troubleshooting
SSH: Permission denied (publickey)
Section titled “SSH: Permission denied (publickey)”Symptom: ssh aur@aur.archlinux.org returns Permission denied.
Causes:
- The public key is not on your AUR account. Add it under My Account > SSH Public Key on https://aur.archlinux.org.
- SSH offers another key. Offer this one alone:
ssh -F /dev/null -o IdentitiesOnly=yes -o IdentityAgent=none -i ~/.ssh/aur_ed25519 aur@aur.archlinux.org - The key file is readable by others. Fix it with
chmod 600 ~/.ssh/aur_ed25519.
SSH: Host key verification failed
Section titled “SSH: Host key verification failed”Symptom: ./aurtomator.sh setup verify prints Host key verification failed. under SSH: cannot connect to aur.archlinux.org.
Cause: no known hosts file holds a key of aur.archlinux.org. The check runs ssh with -F /dev/null and BatchMode=yes, so it reads ~/.ssh/known_hosts, ~/.ssh/known_hosts2, /etc/ssh/ssh_known_hosts and /etc/ssh/ssh_known_hosts2 alone and accepts no new host key.
Fix: run the command of step 3 once. Compare the fingerprint that ssh shows with those under “Submitting Packages” on the home page of https://aur.archlinux.org, and answer yes only when they match.
GPG: No secret key / unusable secret key
Section titled “GPG: No secret key / unusable secret key”Symptom: gpg --sign fails with “No secret key” or “Unusable secret key”.
Causes:
- The key ID is wrong.
gpg --list-secret-keys --keyid-format longlists your keys. - The subkey expired.
gpg --quick-set-expire <master-key-fingerprint> 1y <subkey-fingerprint>extends it, and./aurtomator.sh setup gpg secretssets the secret again, since CI holds the earlier copy. - The key is in another keyring, such as one of another
GNUPGHOME.
gh: not logged in / authentication failed
Section titled “gh: not logged in / authentication failed”Symptom: gh auth status fails, or gh secret set returns 403.
Fixes:
- Run
gh auth login. - Check with
gh auth statusthat the token has thereposcope. A fine-grained token needs write access to “Secrets” of the repository.
Without gh, set the secrets in the web UI, see Manual setup.
Secrets not set / workflow fails with missing secret
Section titled “Secrets not set / workflow fails with missing secret”Symptom: the publish job fails in Setup AUR SSH with The secret AUR_SSH_KEY is empty, or with an SSH key error.
Fixes:
- Settings > Secrets and variables > Actions of your repository lists
AUR_SSH_KEY,AUR_GIT_NAME,AUR_GIT_EMAILand, with GPG,GPG_SIGNING_KEY. ./aurtomator.sh setup secretssets them again.- The job
check-updatesof.github/workflows/check-updates.ymlpasses each secret by name, as The calling workflows shows.secrets: inheritpasses none, see Required.
Invalid workflow file: a nested job requests more permissions
Section titled “Invalid workflow file: a nested job requests more permissions”Symptom: a run of a calling workflow fails before any job starts, with Invalid workflow file and a line of this form:
The nested job '<job>' is requesting '<permissions>', but is only allowed '<permissions>'Cause: the calling job grants less than a job of the called workflow requests, and a called workflow cannot raise the permissions.
Fix: give each job of the calling workflow the permissions of The calling workflows: contents: write and issues: write for check-updates, actions: read and issues: write for notify, and contents: read in validate.yml.
check-update.sh fails: “Strategy not found”
Section titled “check-update.sh fails: “Strategy not found””Symptom: Strategy not found or not executable: and the path of strategies/<strategy>.sh in aurtomator.
Fixes:
./aurtomator.sh validate-pkg my-packagelists the strategies of the pinned release whenstrategynames none of them.- A strategy of a newer release of aurtomator needs the pin of that release, see The calling workflows.
update-pkg.sh fails: “No PKGBUILD found”
Section titled “update-pkg.sh fails: “No PKGBUILD found””Symptom: the clone succeeds, and the script reports No PKGBUILD found in AUR repo.
Cause: the package does not exist on the AUR yet. aurtomator updates existing packages, so push the first PKGBUILD by hand.
updpkgsums fails
Section titled “updpkgsums fails”Symptom: Required command not found: updpkgsums, or updpkgsums failed and no push.
Causes:
updpkgsumsis missing:sudo pacman -S --needed pacman-contribinstalls it.- A download fails that the URL check does not cover: a source that is no
httporhttpsURL, or a server that answers aHEADrequest and refuses the download. A URL that does not resolve after the bump stops the update earlier, withSource URL validation failed, aborting.