"error: failed to commit transaction" error while updating eOS

[AlperAkca79]

When updating my system with the sudo pacman -Syu command, everything goes normally at first, but after all the latest updates are completed

error: libldap: signature from "Frederik Schwan <freswa@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/libldap-2.6.4-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]

it gives 30-40 similar error messages, I call them all ‘y’. At the end:

error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

It gives an error and the update fails. I searched a bit on the internet and tried several methods but none of them worked. How can I solve this?

[ricklinux]

I would update the mirrors and then try the update again.

Edit: You may also need to select another country for mirror list if it keeps failing.

[manuel]

Welcome to the forum!

Try: eos-update

[joekamprad]

and update keyring package first and do the full update after this
sudo pacman -Sy archlinux-keyring
yay

[joekamprad]

@manuel

Try: eos-update.

this will do it simpler

[AlperAkca79]

Thanks!

[AlperAkca79]

i tried it but it didn’t work.

[AlperAkca79]

I updated the mirrors and ran the full system update but it didn’t work. Now I will choose another country for the mirror list and try again.

[joekamprad]

whats the first mirror in your mirrorlist?

[manuel]

In line with what @joekamprad said, can you show the output of command

cat /etc/pacman.d/mirrorlist | eos-sendlog

and tell in which country you are running the machine?

[AlperAkca79]

Output of cat /etc/pacman.d/mirrorlist | eos-sendlog:

https://0x0.st/Hc7S.txt

I’m running my machine in Turkey.

[AlperAkca79]

I have only United States and Germany servers in the mirror list.

[joekamprad]

## Worldwide
Server = https://geo.mirror.pkgbuild.com/$repo/os/$arch

i would not put these…

[AlperAkca79]

I forgot to mention Worldwide. Sorry.

[joekamprad]

@joekamprad

sudo pacman -Sy archlinux-keyring

running bthis should renew all keys from archlinux if not it should gave errors on output

[AlperAkca79]

Its not gave errors. Take a look.

:: Synchronizing package databases...
 endeavouros is up to date
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
warning: archlinux-keyring-20230504-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)             Old Version  New Version  Net Change

core/archlinux-keyring  20230504-1   20230504-1     0,00 MiB

Total Installed Size:  1,61 MiB
Net Upgrade Size:      0,00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                        [--------------------------------------] 100%
(1/1) checking package integrity                                      [--------------------------------------] 100%
(1/1) loading package files                                           [--------------------------------------] 100%
(1/1) checking for file conflicts                                     [--------------------------------------] 100%
:: Processing package changes...
(1/1) reinstalling archlinux-keyring                                  [--------------------------------------] 100%
==> Appending keys from archlinux.gpg...
==> Updating trust database...
gpg: next trustdb check due at 2023-06-15
==> Updating trust database...
gpg: next trustdb check due at 2023-06-15
:: Running post-transaction hooks...
(1/3) Reloading system manager configuration...
(2/3) Arming ConditionNeedsUpdate...
(3/3) Checking which packages need to be rebuilt

[BONK]

[FAQ] 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 endeavouros-keyring sudo pacman -Syu 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/pkg/ so pacman will download it again. If no package file is explicitly mentioned then yo…

[AlperAkca79]

Thank you so much! It works.

[joekamprad]

somehow last resort
seems this can happen it was already on latest keyring package but looked like keys or signatures where not matching…