Updates continuously failing in loop

[8hssw]

spawn pacman -Su --config /tmp/tmp.ap5TWioH44
:: Starting full system upgrade...
:: Replace lib32-libva-mesa-driver with multilib/lib32-mesa? [Y/n] y
:: Replace lib32-mesa-vdpau with multilib/lib32-mesa? [Y/n] y
:: Replace libva-mesa-driver with extra/mesa? [Y/n] y
:: Replace mesa-vdpau with extra/mesa? [Y/n] y
resolving dependencies...
looking for conflicting packages...
warning: dependency cycle detected:
warning: systemd-libs will be installed before its libcap dependency
warning: dependency cycle detected:
warning: qt6-multimedia-ffmpeg will be installed before its qt6-multimedia dependency
warning: dependency cycle detected:
warning: lib32-libcap will be installed before its lib32-systemd dependency
warning: dependency cycle detected:
warning: rubygems will be installed before its ruby dependency

error: python-jaraco.collections: signature from "Daniel M. Capella <polyzen@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/python-jaraco.collections-5.0.1-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y

error: python-setuptools: signature from "Daniel M. Capella <polyzen@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/python-setuptools-1:75.2.0-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y

error: python-charset-normalizer: signature from "Daniel M. Capella <polyzen@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/python-charset-normalizer-3.4.0-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y

error: python-dulwich: signature from "Daniel M. Capella <polyzen@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/python-dulwich-0.22.6-1-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.

This laptop was off for a month (updating worked before) and now updates fail in a continuous loop.

I tried the following in the assistant:
clear caches
clear package cache
refresh keyrings
remove orphans
refresh mirrorlist

[SGS]

Use

upd

in terminal.

[8hssw]

Thanks for the reply. No difference I’m afraid.
I usually use “garuda-update” in the terminal which I assumed was the same?
Isn’t this a signature verification problem?

[SGS]

@8hssw

I assumed was the same?

Yes, I saw that you use it, but we would like the command to be posted so that those seeking help understand the process and learn automatically.

But others could recognize errors if the command is used incorrectly.

It’s an upstream problem that will probably be fixed soon.

https://archlinux.org/packages/extra/any/python-jaraco.collections/
Flagged out of date.

[8hssw]

OK, let me know if anything is needed from me. It always looks identical to my first post.
I’ll give upstream some time and try again later or tomorrow.
Vielen danke.

[filo]

@8hssw

python-jaraco.collections-5.0.1-1-any.pkg.tar.zst

But I think it should be 5.0.1-2
https://archlinux.org/packages/extra-staging/any/python-jaraco.collections/

Again, garuda-update, aka update, aka upd should help.

In case of further errors, you could consider this:

Issues with “signature is marginal trust”, "signature is unknown trust", or “invalid or corrupted package”

If you're getting an error similar to "Can’t update: signature from *** is marginal trust" or "invalid or corrupted package" you probably just need to update your package signing keys: sudo pacman -Sy archlinux-keyring chaotic-keyring sudo pacman -Syu If you have added any other repositories, e.g. BlackArch, then add their keyring to the list. Also make sure your system clock is correct! Of course, it's also possible that the package file actually is corrupt. Remove it from /var/cache/pacman…

Or try:

garuda-update remote fix

[8hssw]

“sudo pacman -Sy archlinux-keyring chaotic-keyring && sudo pacman -Syu”
fixed the problem, thanks.

I didn’t get a chance to try “garuda-update remote fix”

[dr460nf1r3]

For the record garuda-update would’ve updated the keyring before running the actual update. That’s why we suggest using it instead of pacman