Installation failed: pacman failed Ruby 2.7.1 32 bit

[kumarneeraj89]

This issue has been reproduce while installing ruby 2.7 for 32 bit system.

---

| __ \ | | |_ | | | | | | |_
| |) | | | _ _ | | _ __ | | __ | | | ___ _ __ ) |
| _ / | | | ' | | | | | | | ' / __| / _` | | |/ _ \ '/ /
| | \ \ || | |) | || || || | | __ \ || (| | | | _/ | / /
|| __,|_./ __, ||| ||/__,||_|__||||
/ | _
|/ | _ __ | | o __ | _ _
| () | |^| | | |(|()^/_>

1 - MSYS2 base installation
2 - MSYS2 system update (optional)
3 - MSYS2 and MINGW development toolchain

Which components shall be installed? If unsure press ENTER [1,3] 1

sh -lc true
MSYS2 seems to be properly installed

1 - MSYS2 base installation
2 - MSYS2 system update (optional)
3 - MSYS2 and MINGW development toolchain

Which components shall be installed? If unsure press ENTER [] 2

sh -lc true
MSYS2 seems to be properly installed
Remove catgets to avoid conflicts while update ...
pacman -Rdd catgets libcatgets --noconfirm
error: mingw32: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: mingw64: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: msys: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: target not found: catgets
error: target not found: libcatgets
MSYS2 system update (optional) part 1 ...

pacman -Syu --needed --noconfirm
error: mingw32: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: mingw64: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: msys: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

:: Synchronizing package databases...
mingw32 569.9 KiB 247K/s 00:02 [#########################] 100%
mingw32.sig 438.0 B 428K/s 00:00 [#########################] 100%
error: mingw32: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: failed to update mingw32 (invalid or corrupted database (PGP signature))
mingw64 571.4 KiB 388K/s 00:01 [#########################] 100%
mingw64.sig 438.0 B 0.00B/s 00:00 [#########################] 100%
error: mingw64: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: failed to update mingw64 (invalid or corrupted database (PGP signature))
msys 184.2 KiB 200K/s 00:01 [#########################] 100%
msys.sig 438.0 B 428K/s 00:00 [#########################] 100%
error: msys: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: failed to update msys (invalid or corrupted database (PGP signature))
error: failed to synchronize all databases
### MSYS2 system update (optional) failed
Installation failed: pacman failed

1 - MSYS2 base installation
2 - MSYS2 system update (optional)
3 - MSYS2 and MINGW development toolchain

Which components shall be installed? If unsure press ENTER []

[MSP-Greg]

I believe a work-around is:

Download the following two files and place them in a folder without a space in the path, (like C:\temp) :

https://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
https://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig

then run:

ridk exec pacman -Udd <full path to the xz file>

If using c:\temp:

ridk exec pacman -Udd C:/temp/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz

EDIT: 32 bit Ruby or 32 bit system? The above files may be wrong for a 32 bit system. I don't know if the 32 bit systems are supported?

32 bit system is:

https://repo.msys2.org/msys/i686/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
https://repo.msys2.org/msys/i686/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig

[kumarneeraj89]

Yes its for 32 bit Windows operating system (Window 7 sp1),,

I tried above steps but I am still getting below errors;

C:\Temp>ridk exec pacman -Udd C:/temp/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
error: mingw32: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: mingw64: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: msys: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely

error: database 'mingw32' is not valid (invalid or corrupted database (PGP signature)
)
error: database 'mingw64' is not valid (invalid or corrupted database (PGP signature)
)
error: database 'msys' is not valid (invalid or corrupted database (PGP signature))
loading packages...
error: failed to prepare transaction (invalid or corrupted database)

C:\Temp>

[sroller]

You might have run into the problem which occured after a change of the guard of the msys2 maintainers. It's explained here:
https://www.msys2.org/news/#2020-06-29-new-packagers

I include the text from the webpage in case the URL will go out of service at some point:

We have prepared the following steps to verify and install the new keyring manually after which you should be able to use pacman -Syu again:

$ curl -O http://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
$ curl -O http://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig

$ pacman-key --verify msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig
==> Checking msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig... (detached)
gpg: Signature made Mon Jun 29 07:36:14 2020 CEST
gpg: using DSA key AD351C50AE085775EB59333B5F92EFC1A47D45A1
gpg: Good signature from "Alexey Pavlov (Alexpux) [email protected]" [full]

# pacman -U msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
If you can't even import the key and the above command fails like this:

error: msys: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
:: Import PGP key 4A6129F4E4B84AE46ED7F635628F528CF3053E04? [Y/n]
[...]
error: database 'msys' is not valid (invalid or corrupted database (PGP signature))
loading packages...
error: failed to prepare transaction (invalid or corrupted database)
... you have to convince pacman to not care about those databases for a while, for example like this:

# pacman -U --config <(echo) msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
If you still see signature errors, resetting your pacman key store might help:

# rm -r /etc/pacman.d/gnupg/
# pacman-key --init
# pacman-key --populate msys2