Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Some Artix Buildbot packages contain invalid signatures (Read 729 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Some Artix Buildbot packages contain invalid signatures

Some packages built at the start of this month keep failing even if I remake pacman keyring, namely `samba seahorse smplayer spirv-headers`:

Code: [Select]
error: samba: signature from "Artix Buildbot <[email protected]>" is invalid
:: File /mnt/hdd/pacman_cache/samba-2:4.22.2-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: seahorse: signature from "Artix Buildbot <[email protected]>" is invalid
:: File /mnt/hdd/pacman_cache/seahorse-1:47.0.1-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: smplayer: signature from "Artix Buildbot <[email protected]>" is invalid
:: File /mnt/hdd/pacman_cache/smplayer-25.6.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: spirv-headers: signature from "Artix Buildbot <[email protected]>" is invalid
:: File /mnt/hdd/pacman_cache/spirv-headers-1:1.4.313.0-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

I rebuilt keyring multiple times, added these to IgnorePkg, occasionally tried to update them in case it was a fluke, all to no avail. Unfortunately, samba in particular needs to be updated as it fails to start otherwise.

Can you please look into this?

Edit: I even manually added the key to no avail.

Re: Some Artix Buildbot packages contain invalid signatures

Reply #1
Solved. I deleted the packages... oddly enough, I must have done that many times already, but this time it fixed the issue.