Artix Linux Forum

Artix Linux => Package management => Topic started by: badsector on 10 August 2022, 04:09:39

Title: Updating with pacman involving bad file (sigs .. or)
Post by: badsector on 10 August 2022, 04:09:39

I ran into this update problem:

Code: [Select]
(195/195) checking package integrity                                        [##########################################] 100%
error: firefox: signature from "Artix Buildbot <[email protected]>" is invalid
:: File /var/cache/pacman/pkg/firefox-103.0.1-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: mxml: signature from "David Runge <[email protected]>" is marginal trust
:: File /var/cache/pacman/pkg/mxml-3.3.1-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: yoshimi: signature from "David Runge <[email protected]>" is marginal trust
:: File /var/cache/pacman/pkg/yoshimi-2.2.1-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

Not knowing any better I  -R emoved the offending packages and then completed the update. Following that I reinstalled the same offending packages of which the same version numbers that were unacceptable for the update installed without any problems.

I'm not sure this is the proper way to handle the situation...





Title: Re: Updating with pacman involving bad file (sigs .. or)
Post by: AndBenn on 10 August 2022, 06:50:18
You probably hadn't updated the last couple of weeks with -Syu.  And there were *-keyring with updates.  If you see new keyring packages, take those first.  These issues/errors are likely on the web somewhere too.

You didn't have to remove those packages.
Title: Re: Updating with pacman involving bad file (sigs .. or)
Post by: phoenix_king_rus on 10 August 2022, 07:49:38
Recently got into same problem. The solution was to add universe repo and update archlinux-keyring from there