Pacman -Syu fails to update, key is unknown

[mbehm]

Yes this is the same issue as #67 because just up and reinstalling everything from the scratch isn't a proper solution and since that one is closed nobody seems to care. Please provide a working solution to update past the key change without having to reinstall everything. Solution in https://www.msys2.org/news/#2020-06-29-new-packagers doesn't work.

[jeremyd2019]

touch empty
curl -LO https://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
pacman --config empty -U msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
pacman -Syyu

??

[mbehm]

Apparently you'll need to use the pacman -U --config <(echo) msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz even if adding the key doesn't fail, might want to update the documentation to say that.

[jeremyd2019]

Some people also reported the bash trick of <(echo) caused an error that /dev/fd/<number> was not found, perhaps because their install was so old that that directory wasn't created at install. Whatever the cause, an actual empty file might help in that case.

[humbleoh]

Could be caused by these changes in dirmngr https://dev.gnupg.org/rG47c4e3e00a7ef55f954c14b3c237496e54a853c1 https://github.com/msys2/msys2.github.io/issues/76

Updating the gnupg to the latest version should fix the issue.