Msys2-packages: Invalid signature, corrupt database
oscar@w10x64-vm-sky MINGW64 ~
$ pacman -Suy
:: Synchronizing package databases...
mingw32 468.8 KiB 652 KiB/s 00:01 [#####################] 100%
mingw32.sig 119.0 B 0.00 B/s 00:00 [#####################] 100%
mingw64 471.4 KiB 3.27 MiB/s 00:00 [#####################] 100%
mingw64.sig 119.0 B 0.00 B/s 00:00 [#####################] 100%
msys 189.8 KiB 0.00 B/s 00:00 [#####################] 100%
msys.sig 438.0 B 0.00 B/s 00:00 [#####################] 100%
error: msys: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
:: Import PGP key 4A6129F4E4B84AE46ED7F635628F528CF3053E04? [Y/n]
error: msys: signature from "David Macek <[email protected]>" is unknown trust
error: failed to update msys (invalid or corrupted database (PGP signature))
error: failed to synchronize all databases
oscar@w10x64-vm-sky MINGW64 ~
$ pacman -Suy
error: msys: signature from "David Macek <[email protected]>" is unknown trust
:: Synchronizing package databases...
mingw32 is up to date
mingw64 is up to date
msys 189.8 KiB 450 KiB/s 00:00 [#####################] 100%
msys.sig 438.0 B 0.00 B/s 00:00 [#####################] 100%
error: msys: signature from "David Macek <[email protected]>" is unknown trust
error: failed to update msys (invalid or corrupted database (PGP signature))
error: failed to synchronize all databases
oscar@w10x64-vm-sky MINGW64 ~
$
oscarfv
All 24 comments
In the Arch forum it was suggested that pacman-key --refresh-keys is a possible solution for this. Didn't work.
oscarfv
on 25 Jul 2020
I think I have a similar issue, which I outlined here: https://github.com/msys2/MINGW-packages/issues/6717.
maxnelso
on 25 Jul 2020
See https://www.msys2.org/news/#2020-06-29-new-packagers
lazka
on 25 Jul 2020
See https://www.msys2.org/news/#2020-06-29-new-packagers
That worked for me, thank you @lazka. Also thanks to you and @elieux for becoming packagers!
I'm not closing this issue to give this change more visibility. Feel free to close it when you decide that it is not useful anymore.
oscarfv
on 25 Jul 2020
If i follow the guide from the homepage, the keyring verification fails
see: https://ci.appveyor.com/project/lovetox/gajim/builds/34604241/job/6b9d0ab7m4925v56
lovetox
on 11 Aug 2020
@lovetox see https://github.com/msys2/msys2.github.io/commit/49cb77c59824e07acaac1b4a8e03a9df45296bc0. Looks like pacman-key argument handling has changed some versions ago.
lazka
on 11 Aug 2020
Correct. The version shipped with appveyor takes just one argument, the signature:
https://github.com/mamedev/mame/blob/master/.appveyor.yml
belegdol
on 11 Aug 2020
I was originally having this problem, but while I was writing this post, it got fixed, so I just post this for reference.
I updated via pacman -Syu yesterday, all was fine.
Today I get this error, and I found this bug, and I'm trying to follow the steps:
$ pacman -Syu
error: msys: signature from "David Macek <[email protected]>" is invalid
:: Synchronizing package databases...
mingw32 is up to date
mingw64 is up to date
msys 205.6 KiB 461 KiB/s 00:00 [#####################] 100%
msys.sig 438.0 B 0.00 B/s 00:00 [#####################] 100%
error: msys: signature from "David Macek <[email protected]>" is invalid
error: failed to update msys (invalid or corrupted database (PGP signature))
error: failed to synchronize all databases
$ curl -O http://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 61344 100 61344 0 0 103k 0 --:--:-- --:--:-- --:--:-- 103k
$ curl -O http://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 119 100 119 0 0 319 0 --:--:-- --:--:-- --:--:-- 319
$ 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, 2020 7:36:14 AM 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
error: msys: signature from "David Macek <[email protected]>" is invalid
error: database 'msys' is not valid (invalid or corrupted database (PGP signature))
loading packages...
warning: msys2-keyring-r21.b39fb11-1 is up to date -- reinstalling
error: failed to prepare transaction (invalid or corrupted database)
$ pacman -U --config <(echo) msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz
loading packages...
warning: msys2-keyring-r21.b39fb11-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) msys2-keyring-r21.b39fb11-1
Total Installed Size: 0.05 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 msys2-keyring [###################################] 100%
==> Appending keys from msys2.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signing key 6E8FEAFF9644F54EED90EEA0790AE56A1D3CFDDC...
-> Locally signing key D55E7A6D7CE9BA1587C0ACACF40D263ECA25678A...
-> Locally signing key 123D4D51A1793859C2BE916BBBE514E53E0D0813...
-> Locally signing key B91BCF3303284BF90CC043CA9F418C233E652008...
-> Locally signing key 9DD0D4217D75A33B896159E6DA7EF2ABAEEA755C...
-> Locally signing key 69985C5EB351011C78DF7F6D755B8182ACD22879...
==> Importing owner trust values...
==> Disabling revoked keys in keyring...
-> Disabling key B19514FB53EB3668471B296E794DCF97F93FC717...
==> Updating trust database...
gpg: next trustdb check due at 2021-06-19
Previously, at this point, I restarted the MSYS2 terminal, and then ran pacman -Syu, which failed again for me - but this time I did not restart the terminal after last command, instead I just proceeded directly:
$ pacman -Syu
error: msys: signature from "David Macek <[email protected]>" is invalid
:: Synchronizing package databases...
mingw32 is up to date
mingw64 is up to date
msys 205.6 KiB 467 KiB/s 00:00 [###################################] 100%
msys.sig 438.0 B 0.00 B/s 00:00 [###################################] 100%
:: Starting core system upgrade...
warning: terminate other MSYS2 programs before proceeding
resolving dependencies...
looking for conflicting packages...
Packages (3) filesystem-2020.02-7 msys2-runtime-3.1.6-2 msys2-runtime-devel-3.1.6-2
Total Download Size: 8.12 MiB
Total Installed Size: 46.40 MiB
Net Upgrade Size: -0.02 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
filesystem-2020.02-7-x86_64 31.3 KiB 245 KiB/s 00:00 [###################################] 100%
msys2-runtime-3.1.6-2-x86_64 2.7 MiB 742 KiB/s 00:04 [###################################] 100%
msys2-runtime-devel-3.1.6-2-x86_64 5.4 MiB 657 KiB/s 00:08 [###################################] 100%
(3/3) checking keys in keyring [###################################] 100%
(3/3) checking package integrity [###################################] 100%
(3/3) loading package files [###################################] 100%
(3/3) checking for file conflicts [###################################] 100%
(3/3) checking available disk space [###################################] 100%
:: Processing package changes...
(1/3) upgrading filesystem [###################################] 100%
(2/3) upgrading msys2-runtime [###################################] 100%
(3/3) upgrading msys2-runtime-devel [###################################] 100%
:: To complete this update all MSYS2 processes including this terminal will be closed. Confirm to proceed [Y/n] y
Restarted MSYS2 terminal here - and now pacman -Syu is fine:
$ pacman -Syu
:: Synchronizing package databases...
mingw32 is up to date
mingw64 is up to date
msys is up to date
:: Starting core system upgrade...
there is nothing to do
:: Starting full system upgrade...
there is nothing to do
sdbbs
on 14 Aug 2020
error: mingw32: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
:: Import PGP key 4A6129F4E4B84AE46ED7F635628F528CF3053E04? [Y/n]
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely
error: mingw64: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
:: Import PGP key 4A6129F4E4B84AE46ED7F635628F528CF3053E04? [Y/n]
error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely
error: msys: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" is unknown
:: Import PGP key 4A6129F4E4B84AE46ED7F635628F528CF3053E04? [Y/n]
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))
Install MSYS2 and MINGW development toolchain failed
Installation failed: pacman failed
I tried all of the option that you have suggested over here but none of it doesnt work for me
Kinfe123
on 7 Sep 2020
- See the news https://www.msys2.org/news/#2020-06-29-new-packagers
- Try
pacman-key --init; pacman-key --populate - If possible, try newer version of msys2-installer.
Biswa96
on 7 Sep 2020
please help me with this i just reinstalled msys2 just for it to worsen
im using x86 version because i have to
Cooliokid956
on 16 Sep 2020
i686 msys2 installer was deprecatee since 22-05-2020, news link. You can use x86_64 installer if you've x86_64 OS. Also you can access mingw32 packages there.
Biswa96
on 16 Sep 2020
I tried to follow the 2020-06-29-new-packagers guide and got the signature of Alexey Pavlov. Still, the message error: key "4A6129F4E4B84AE46ED7F635628F528CF3053E04" could not be looked up remotely remained.
I'm on an older installation and want to update the packages.
The statement pacman -U --config <(echo) msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz helped, however, the doc says convince pacman to not care about those databases for a while. Will I eventually uninstall this?
What's the issue with the remote availability of 4A6129F4E4B84AE46ED7F635628F528CF3053E04?
bardware
on 17 Sep 2020
I have the same issue as @bardware, except if I try to run the pacman -U --config <(echo) msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz line, I get:
error: config file /dev/fd/63 could not be read: Not a directory
And I can't progress further? Any tips on what I can do to fix this? My /dev/fd is not a directory.
eddieparker
on 8 Oct 2020
I followed the steps by sdbbs and it works fine.
mcuee
on 30 Oct 2020
after I followed all these steps and did an update I get lots of
2 [main] make (9752) shared_info::initialize: size of shared memory region changed from 49080 to 51128
2 [main] make (10632) shared_info::initialize: size of shared memory region changed from 49080 to 51128
1 [main] cp (1924) shared_info::initialize: size of shared memory region changed from 49080 to 51128
no idea if this is because of the steps or something else. Should I open a new issue? This is really annoying :(
DominusExult
on 30 Oct 2020
restarting windows should help (or close all msys2 processes, but restarting is easier)
lazka
on 30 Oct 2020
Thanks, I just did and indeed that fixed it. Sorry for the noise
DominusExult
on 30 Oct 2020
See https://www.msys2.org/news/#2020-06-29-new-packagers
This useless link is mentioned in all tickets related to that failure with msys2 update (it doesn't work for me, not sure what I need to run, and I don't want to read that long poem). I've used msys2 for many years, have never had any problems, and this update with key is a huge failure imo. No clear answer what to run to make and update/upgrade. This should have been handled properly instead of breaking things for everybody.
After running all possible commands mentioned all over the place, I still cannot update and get this error from running pacman -Syuu:
(8/8) checking package integrity [########################################################################################################] 100%
0 [main] pacman (18360) shared_info::initialize: size of shared memory region changed from 40888 to 49080 [--------------------------------------------------------------------------------------------------------] 0%
0 [main] pacman (11244) shared_info::initialize: size of shared memory region changed from 40888 to 49080 [###################-------------------------------------------------------------------------------------] 19%
1 [main] pacman (15672) shared_info::initialize: size of shared memory region changed from 40888 to 49080 [####################------------------------------------------------------------------------------------] 20%
0 [main] pacman (31588) shared_info::initialize: size of shared memory region changed from 40888 to 49080 [#################################################-------------------------------------------------------] 48%
0 [main] pacman (27008) shared_info::initialize: size of shared memory region changed from 40888 to 49080 [####################################################----------------------------------------------------] 50%
0 [main] pacman (21016) shared_info::initialize: size of shared memory region changed from 40888 to 49080 [#######################################################-------------------------------------------------] 53%
(8/8) loading package files [########################################################################################################] 100%
error: could not open file /var/cache/pacman/pkg/bash-5.1.004-1-x86_64.pkg.tar.zst: Child process exited with status 127
error: could not open file /var/cache/pacman/pkg/filesystem-2021.01-1-x86_64.pkg.tar.zst: Child process exited with status 127
error: could not open file /var/cache/pacman/pkg/mintty-1~3.4.4-1-x86_64.pkg.tar.zst: Child process exited with status 127
error: could not open file /var/cache/pacman/pkg/libzstd-1.4.8-1-x86_64.pkg.tar.zst: Child process exited with status 127
error: could not open file /var/cache/pacman/pkg/zstd-1.4.8-1-x86_64.pkg.tar.zst: Child process exited with status 127
error: could not open file /var/cache/pacman/pkg/pacman-5.2.2-9-x86_64.pkg.tar.zst: Child process exited with status 127
error: failed to commit transaction (cannot open package file)
Errors occurred, no packages were upgraded.
pps83rbx
on 21 Jan 2021
@pps83rbx
The following steps worked for me when updating an older msys2 version:
- install the new keys ( https://www.msys2.org/news/#2020-06-29-new-packagers)
- taskkill /fi "MODULES eq msys-2.0.dll" + exit the terminal (https://github.com/msys2/MSYS2-packages/issues/1966)
- install zstd and pacman manually ( https://github.com/msys2/MSYS2-packages/issues/1967)
pacman --noconfirm -U "http://repo.msys2.org/msys/x86_64/libzstd-1.4.4-2-x86_64.pkg.tar.xz"
pacman --noconfirm -U "http://repo.msys2.org/msys/x86_64/zstd-1.4.4-2-x86_64.pkg.tar.xz"
pacman --noconfirm -U "http://repo.msys2.org/msys/x86_64/pacman-5.2.1-6-x86_64.pkg.tar.xz" - taskkill /fi "MODULES eq msys-2.0.dll" + exit the terminal
- update pacman separately first (https://www.msys2.org/news/#2020-05-31-update-may-fail-with-could-not-open-file)
pacman --noconfirm -Sydd pacman - taskkill /fi "MODULES eq msys-2.0.dll" + exit the terminal
- Core update (in case any core packages are outdated)
pacman --noconfirm -Syuu - taskkill /fi "MODULES eq msys-2.0.dll" + exit the terminal
- Normal update
pacman --noconfirm -Syuu - taskkill /fi "MODULES eq msys-2.0.dll"
dmn-star
on 28 Jan 2021
@dmn-star Perhaps something what you did would work for me also.
I fixed it a bit differently. I didn't want to completely reinstall msys from scratch (to keep my local changes/settings), so to unbreak it I had to manually copy pacman and dll's from a clear msys install, this made it work on my old install where I was finally able to update everything and now it's ok.
pps83rbx
on 28 Jan 2021
@pps83rbx, your issue is not the one this ticket is about. Step 3 from @dmn-star would fix it.
I'm not quite sure if core packages using Zstd is intended though, let me check.
elieux
on 14 Feb 2021
this update with key is a huge failure imo. No clear answer what to run to make and update/upgrade. This should have been handled properly instead of breaking things for everybody.
Regarding keys, hypothetically speaking, we could've improved the upgrade path for irregularly updated installations, but it'd create complications for everyone. Given MSYS2 is a rolling release distro, I don't think it's unheard of to not support these installations 100 percent.
elieux
on 14 Feb 2021
I'm not quite sure if core packages using Zstd is intended though, let me check.
Yes, it was intentional. I've created a "news" entry describing this including the fix for older installations (copied from @dmn-star).
elieux
on 14 Feb 2021
Related issues
jlinse
路
4Comments
Arnold1
路
8Comments
transtone
路
8Comments
neolib
路
7Comments
hiroakit
路
5Comments
Most helpful comment
See https://www.msys2.org/news/#2020-06-29-new-packagers