abarbarian Posted February 4, 2022 Posted February 4, 2022 A few days ago I tried to do an Arch update and got this, (217/217) checking keys in keyring [######################] 100% downloading required keys... :: Import PGP key C132293954BBE4AD, "Sergej Pupykin <spupykin@archlinux.org>"? [Y/n] y :: Import PGP key E85B8683EB48BC95, "Daniel Bermond <dbermond@archlinux.org>"? [Y/n] y (217/217) checking package integrity [######################] 100% error: libjxl: key "80247D99EABD3A4D1E3A1836E85B8683EB48BC95" is unknown :: Import PGP key 80247D99EABD3A4D1E3A1836E85B8683EB48BC95? [Y/n] n :: File /var/cache/pacman/pkg/libjxl-0.6.1-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] y error: mujs: key "80247D99EABD3A4D1E3A1836E85B8683EB48BC95" is unknown :: Import PGP key 80247D99EABD3A4D1E3A1836E85B8683EB48BC95? [Y/n] n :: File /var/cache/pacman/pkg/mujs-1.2.0-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] y error: failed to commit transaction (invalid or corrupted package) Errors occurred, no packages were upgraded. Today I tried again and got this, (253/253) checking keys in keyring [######################] 100% (253/253) checking package integrity [######################] 100% error: libjxl: signature from "Daniel Bermond <dbermond@archlinux.org>" is marginal trust :: File /var/cache/pacman/pkg/libjxl-0.6.1-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] y error: mujs: signature from "Daniel Bermond <dbermond@archlinux.org>" is marginal trust :: File /var/cache/pacman/pkg/mujs-1.2.0-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] y error: failed to commit transaction (invalid or corrupted package) Errors occurred, no packages were upgraded. I can not find any information on this on the net. Bit stumped ?????????????????????????? Quote
raymac46 Posted February 4, 2022 Posted February 4, 2022 (edited) Maybe try deleting the file from cache? I just tried an update on my old Toshiba netbook and all went well. https://wiki.archlinux.org/title/Pacman/Package_signing Edited February 4, 2022 by raymac46 Quote
abarbarian Posted February 5, 2022 Author Posted February 5, 2022 15 hours ago, raymac46 said: Maybe try deleting the file from cache? I just tried an update on my old Toshiba netbook and all went well. https://wiki.archlinux.org/title/Pacman/Package_signing Hmm I'll give that a try. Thanks. Quote
Chihiro Posted February 5, 2022 Posted February 5, 2022 Had the same problem today. Resolved it by running : # pacman-key --refresh-keys Hope this could help. 1 Quote
securitybreach Posted February 5, 2022 Posted February 5, 2022 Sorry, I was away yesterday. I ran into the same thing on my main laptop and you basically just have to refresh your keys: sudo pacman-key --init sudo pacman-key --populate Archlinux sudo pacman-key --refresh-keys 1 Quote
abarbarian Posted February 6, 2022 Author Posted February 6, 2022 That # pacman-key --refresh-keys sorted things out, it took quite q while to run though. Now I just have to deal with the "sudoers.pacnew" 1 Quote
securitybreach Posted February 7, 2022 Posted February 7, 2022 5 hours ago, abarbarian said: That # pacman-key --refresh-keys sorted things out, it took quite q while to run though. Now I just have to deal with the "sudoers.pacnew" Good deal. I think a couple of developers changed their keys and it just had to be updated. Quote
wa4chq Posted February 17, 2022 Posted February 17, 2022 sudo pacman --refresh-with-slackware No, seriously abarbarian, glad you got it all sorted out! 1 Quote
securitybreach Posted February 17, 2022 Posted February 17, 2022 7 minutes ago, wa4chq said: sudo pacman --refresh-with-slackware But then you lose packages and package signing..... 1 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.