You are not logged in.
- Topics: Active | Unanswered
#1 2024-06-08 13:08:14
- tomsk
- Member
- Registered: 2016-12-17
- Posts: 183
[SOLVED] Cannot update system anymore (invalid or corrupted package)
For every package I get error like this:
╰─ sudo pacman -Sy archlinux-keyring ─╯
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
warpdotdev is up to date
warning: archlinux-keyring-20240520-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) archlinux-keyring-20240520-1
Total Download Size: 1.17 MiB
Total Installed Size: 1.66 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
archlinux-keyring-20240520-1-any 1193.9 KiB 19.4 MiB/s 00:00 [####################################################################################] 100%
(1/1) checking keys in keyring [####################################################################################] 100%
(1/1) checking package integrity [####################################################################################] 100%
error: archlinux-keyring: signature from "Christian Hesse <eworm@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/archlinux-keyring-20240520-1-any.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 (PGP signature))
Errors occurred, no packages were upgraded.I tried:
─ ~ 1 ✘ 14:18:31 ─╮
╰─ find /var/cache/pacman/pkg/ -iname "*.part" -exec rm {} \; ╰─ rm /var/lib/pacman/db.lck ─╯
rm: cannot remove '/var/lib/pacman/db.lck': No such file or directory╰─ sudo pacman-key --list-sigs Master ─╯
pub rsa4096 2024-05-29 [SC]
DF3BE4D835CEB5B5389E180330556917D4618290
uid [ultimate] Pacman Keyring Master Key <pacman@localhost>
sig 3 30556917D4618290 2024-05-29 [self-signature]I dont know what to do next. Same for pacman -Syu
Last edited by tomsk (2024-06-08 14:45:23)
I use several linux distros like: Archlinux, Ubuntu, Fedora, Linux Mint
Offline
#2 2024-06-08 13:41:16
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 12,244
- Website
Re: [SOLVED] Cannot update system anymore (invalid or corrupted package)
If that's the full output for `pacman-key --list-sigs Master` then your pacman keyring is very incomplete.
Start with https://wiki.archlinux.org/title/Pacman … aster_keys then try re-installing archlinux-keyring again. Post the outputs you get if you still have problems.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
#3 2024-06-08 14:27:15
- tomsk
- Member
- Registered: 2016-12-17
- Posts: 183
Re: [SOLVED] Cannot update system anymore (invalid or corrupted package)
I got this:
╰─ sudo pacman-key --populate ─╯
[sudo] password for tomsk:
==> Appending keys from archlinux.gpg...
gpg: public key of ultimately trusted key 9458794D5B6DA21B not found
==> Locally signing trusted keys in keyring...
==> ERROR: 69E6471E3AE065297529832E6BA0F5A2037F4F41 could not be locally signed.
==> ERROR: D8AFDDA07A5B6EDFA7D8CCDAD6D055F927843F1C could not be locally signed.
==> ERROR: 3572FA2A1B067F22C58AF155F8B821B42A6FDCD7 could not be locally signed.
==> ERROR: 91FFE0700E80619CEB73235CA88E23E377514E00 could not be locally signed.I use several linux distros like: Archlinux, Ubuntu, Fedora, Linux Mint
Offline
#4 2024-06-08 14:33:59
- Scimmia
- Fellow
- Registered: 2012-09-01
- Posts: 11,895
Re: [SOLVED] Cannot update system anymore (invalid or corrupted package)
When dealing with a corrupted keyring, https://wiki.archlinux.org/title/Pacman … l_the_keys is the best course of action.
Offline
#5 2024-06-08 14:40:48
- tomsk
- Member
- Registered: 2016-12-17
- Posts: 183
Re: [SOLVED] Cannot update system anymore (invalid or corrupted package)
Thanks, it helps
╰─ sudo rm -rf /etc/pacman.d/gnupg ─╯
[sudo] password for tomsk:
╭─ ~ ✔ 16:36:28 ─╮
╰─ sudo pacman-key --init ─╯
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/2DD2B5C722AF3B85999E407EA1DA7A2AF2A796A0.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
╭─ ~ ✔ 16:36:38 ─╮
╰─ sudo pacman-key --populate ─╯
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signed 5 keys.
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
-> Disabled 45 keys.
==> Updating trust database...
gpg: Note: third-party key signatures using the SHA1 algorithm are rejected
gpg: (use option "--allow-weak-key-signatures" to override)
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 5 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 5 signed: 100 trust: 0-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2 valid: 75 signed: 23 trust: 75-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2024-06-29looks alright now
I use several linux distros like: Archlinux, Ubuntu, Fedora, Linux Mint
Offline