New to Garuda and Arch linux in general. Trying to update the system. Any guidance or help will be appreciated.
Run the command sudo pacman -Syyuu (which was suggested in another forum for this issue) I get the following:
Total Download Size: 0.01 MiB
Total Installed Size: 5337.80 MiB
Net Upgrade Size: 48.18 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
garuda-setup-assistant-r24.1ab4be6-1-any 10.3 KiB 0.00 B/s 00:00 [------------------------------------------------------] 99%
(478/478) checking keys in keyring [------------------------------------------------------] 100%
(478/478) checking package integrity [------------------------------------------------------] 100%
error: garuda-setup-assistant: signature from "Pedro Henrique Lara Campos <root@pedrohlc.com>" is invalid
:: File /var/cache/pacman/pkg/garuda-setup-assistant-r24.1ab4be6-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)
Errors occurred, no packages were upgraded.
2 Likes
What happens of you just delete the corrupted package?
And welcome btw
Cryles
6 February 2021 13:19
3
Package deleted and downloaded again but same Error
1 Like
Looks like an issue with the ChaoticAUR package database.... @pedrohlc ?
1 Like
Poida
6 February 2021 14:34
5
I just installed Garuda on a new system for the first time. Did experience the upgrade failure referenced here: https://forum.garudalinux.org/t/pacman-upgrade-failure-garuda-hooks-maximum-file-size-exceeded/3928
And I'm now getting this error too. It may have been a result of the rebuild mentioned in the above thread. I have cleared my package cache, and rebuilt the database as suggested. I am still receiving the same error as the OP.
1 Like
I rebuild the package, try again please
On my system it installs fine
4 Likes
Poida
6 February 2021 14:52
7
It is now working on my system. Whatever you did, you did it well. Thank-you
1 Like
TNE
6 February 2021 15:02
8
This has been a reoccurring issue, I had to ask a Chaotic-AUR to rebuild a few packages recently too, I wonder what's causing this
2 Likes
Phip
6 February 2021 15:11
9
there seems to be a few threads on this
petsam
6 February 2021 22:57
10
I assume it involves keyrings, but the repo maintainers should know better.
2 Likes
Essentially, the entry in the database does not match the package on disk.
This normally results in one of two things:
Signature does not match (“invalid or corrupted package”); file is same size or smaller than database entry;
File size does not match (“filesize exceeded”); file is larger than database entry filesize.
1 Like
Thank you, whatever you did worked. I only just now got to try updating again and it all worked.
2 Likes
TNE
7 February 2021 13:05
13
Yea, but that doesn't really answer WHY it's happening in the first place
3 Likes
Possibly a race condition on the builder (e.g. two repo-add
operations running at the same time)?
3 Likes
Hi, IDK if it's proper for me to just bump this thread. I can make a new post if needed, or if no one seems to respond here after a while. So, I'm having this exact problem myself on a fresh install. The only difference is the packages failing are signed by "Nico Jensch". I can post a terminal output if needed, I'm on a different pc atm, but it looks exactly like his just the authors are different. It's failing for Black Arch repo, Virtualbox, Wine, and a couple others that I dont remember off the top. Is there any fix for this? Or can someone let Nico know that his cert/keys whatever they're called are invalid/expired. Or something? Lol. TIA.
filo
31 May 2023 06:39
16
Yes, please, open a new topics, providing as much info as possible (terminal output).
2 Likes