Error failed to synchronize all databases invalid or corrupted database pgp signature

Arch Linux

You are not logged in.

#1 2015-09-14 19:03:41

[SOLVED] invalid or corrupted database (PGP signature)

Since yesterday (roughly 20 hours ago), I have tried a couple of times to pacman -Syu my system and keep getting the following:

I figured it might be something internet related so I gave it some time, but after so many hours, I am started to wonder if there might be another issue at play.

Here is my pacman.conf . it is pretty much default though.

I did search the forums here and found an old 2013 thread that didn’t really help. Searching google lead to a few pages saying thing like removing the pacman/sync directory which hasn’t helped in my case.

pacman -Syy returns exactly the same as -Syu

Oh and I found posts saying to run something like pacman-mirrors -u. These were old posts though and my system does not even have a pacman-mirrors command so I didn’t see any help there.

Can someone shed some help on what could be happening?

Last edited by dewmsolo (2015-09-17 15:53:05)

#2 2015-09-14 21:09:48

Re: [SOLVED] invalid or corrupted database (PGP signature)

The pacman.conf is indeed default and not interesting. What’s your mirror?

#3 2015-09-14 22:46:05

Re: [SOLVED] invalid or corrupted database (PGP signature)

I edited the original question and added my /etc/pacman/mirrorlist

#4 2015-09-15 06:48:07

Re: [SOLVED] invalid or corrupted database (PGP signature)

Have you tried resetting the pacman keyring and then refreshing all the keys?

Also, from where did you get the signature for the database? I mean, none of the mirrors in your /etc/pacman/mirrorlist has a signed database and pacman shouldn’t download non exiting files.

— When you have eliminated the impossible, whatever remains, however improbable, must be the truth — Spock | Sherlock Holmes

#5 2015-09-15 12:24:30

Re: [SOLVED] invalid or corrupted database (PGP signature)

Have you tried resetting the pacman keyring and then refreshing all the keys?

Also, from where did you get the signature for the database? I mean, none of the mirrors in your /etc/pacman/mirrorlist has a signed database and pacman shouldn’t download non exiting files.

The —init returned with no output and the —populate archlinux returned:

After running those commands, I still receive the exact same output from pacman -Syu.

As for the signature for the database. just off the top of my head I can’t really tell other than when I setup this install I follow the Wiki’s installation guide and I had actually followed the mirror configuration and had used reflector.

#6 2015-09-15 12:48:45

Re: [SOLVED] invalid or corrupted database (PGP signature)

Ok, let’s do some sanity checks. first of all, can you post the output of the following commands?

Secondly, try changing the line «SigLevel = Required DatabaseOptional» to «SigLevel = PackageRequired» in your pacman.conf. Then remove the signature files

and try again to upgrade the system.

— When you have eliminated the impossible, whatever remains, however improbable, must be the truth — Spock | Sherlock Holmes

#7 2015-09-15 12:54:56

Re: [SOLVED] invalid or corrupted database (PGP signature)

I just had a fellow around who solved the same issue by passing `-Syyu` (with two `y`). Not sure if applicable here, and why this solves the issue.

Last edited by ayekat (2015-09-15 12:55:20)

#8 2015-09-15 13:37:48

Re: [SOLVED] invalid or corrupted database (PGP signature)

Ok, let’s do some sanity checks. first of all, can you post the output of the following commands?

Secondly, try changing the line «SigLevel = Required DatabaseOptional» to «SigLevel = PackageRequired» in your pacman.conf. Then remove the signature files

and try again to upgrade the system.

Most certainly. here goes
uname -a

pacman -Qi pacman gpgme

I then changed the pacman.conf as you said and ran pacman -Syyuv and received the same output.

Removing the sigs and trying to upgrade still yields the same.

#9 2015-09-15 15:14:28

Re: [SOLVED] invalid or corrupted database (PGP signature)

I noted that pacman reports that each database file and each sig file has the same size of 1396.0 bytes, and that the download speed is always 0.00B/s. can you open a database file in a text editor (let’s say /var/lib/pacman/extra.db) and check it’s content? Does it contain binary (unreadable) data or plain text?

Cany you try to use a different mirror? Also, what happens if you try to download the database files manually from that mirror?

Last edited by mauritiusdadd (2015-09-15 15:15:13)

— When you have eliminated the impossible, whatever remains, however improbable, must be the truth — Spock | Sherlock Holmes

#10 2015-09-15 16:33:14

Re: [SOLVED] invalid or corrupted database (PGP signature)

I noted that pacman reports that each database file and each sig file has the same size of 1396.0 bytes, and that the download speed is always 0.00B/s. can you open a database file in a text editor (let’s say /var/lib/pacman/extra.db) and check it’s content? Does it contain binary (unreadable) data or plain text?

Cany you try to use a different mirror? Also, what happens if you try to download the database files manually from that mirror?

Well a cat core.db returns:

Executing your curl command and the echo commad afterward returns at 0.

But the core.db is now a binary file.

I’m wondering if I shouldn’t change my mirrorlist with a fresh one. My current one is from February so 6

#11 2015-09-15 16:58:49

Re: [SOLVED] invalid or corrupted database (PGP signature)

Yes, please use another mirror.
But I still don’t get it — no problems here at all, curl via IPv4 and v6 always fetches the correct file, no weird HTML at all.
Did you notice any DNS problems, besides pacman usage? What’s your /etc/resolv.conf?

#12 2015-09-15 18:17:41

Re: [SOLVED] invalid or corrupted database (PGP signature)

Yes, please use another mirror.
But I still don’t get it — no problems here at all, curl via IPv4 and v6 always fetches the correct file, no weird HTML at all.
Did you notice any DNS problems, besides pacman usage? What’s your /etc/resolv.conf?

Which points to my router and my router points to the addresses of my ISP’s nameservers.

I have had no other issues of any kind with the internet lately. My other linux installs (other stations) all work and update fine.

I will start a new mirrorlist from scratch when I’m done work. I’ll post later tonight if that helps.

#13 2015-09-16 00:59:40

Re: [SOLVED] invalid or corrupted database (PGP signature)

It seems like there was a problem with one of the canadian mirrors. I had to run pacman -Syy after changing my mirrors to fix the issue.

But you did that already so idk what else to suggest, but some other people had a similar issue — https://www.reddit.com/r/archlinux/comm … g_upgrade/

Last edited by Dren (2015-09-16 01:03:16)

#14 2015-09-16 01:42:42

Re: [SOLVED] invalid or corrupted database (PGP signature)

Ok. so. tell you what.

I get home, do some stuff and finally sit down at my computer and get right away onto refreshing my mirrorlist.

Right away you guys should pick on my worst mistake. not trying a pacman -Syyuv or such to see if the problem was still there.

So get a new mirrorlist following the pacman mirrors instructions from the wiki. I took only the canadian ones.

Backup my current mirrorlist

Create a new one and insert what I got online

run a pacman -Syyuv

Successful in everyway with a few packages out of date so I do the updates and everything is peachy.

Being a curious and wanting to see this through, I decided to investigate and do a diff of my old mirrorlist and the new one. Except for one, out of 7 or 8, only one freaking mirror is different and it’s the 5th of the list which shouldn’t even ever get used by pacman unless the prior 4 screw up.

. Save the new mirrorlist and put the old back in place. EVERYTHING WORKS. 4 or 5 hours ago it wasn’t working. for the past 3 days it wasn’t working

In the end I deleted my old mirrorlist and put the new one in its place since it had one newer mirror in there. Not that it should make much of a difference being the 5th ot 6th.

At this point I am really puzzled. The only thing that comes to mind is downloading the core.db with curl earlier. Then again, before posting here at all one of the links I had found suggested deleting the /var/lib/pacman/sync directory. So even if my core.db was corrupted, I should have gotten a fresh one. Unless my core.db got corrupted at the time of the problem with the canadian mirror that Dren suggested and that I did my deletion of sync before it got fixed and ended up in the same boat because of that same problem with the *at the time* unfixed mirror.

Maybe someonelse has another theory?

The issue is fixed, but for the sake of listening to your theories and maybe finding the real cause I will not mark it solved right away. Since we don’t really know the cause I’d like to give us until tomorrow to keep the conversation going and I’ll close/solve it then.

Last edited by dewmsolo (2015-09-16 01:43:57)

#15 2015-09-16 05:32:37

Re: [SOLVED] invalid or corrupted database (PGP signature)

I don’t know what actually happened, but checking the mirrors status, it seems that the mirror archlinux.dropswitch.net was in a semi-broken state just when your problem started. The strange thing is that your problem persisted even when the mirror was back online (I tried every mirror from your original mirrorlist and all of them worked just fine for me). More strange is the fact that pacman wasn’t able to download the database file while curl was and, pacman uses libcurl so there should be no difference

Last edited by mauritiusdadd (2015-09-16 05:33:04)

— When you have eliminated the impossible, whatever remains, however improbable, must be the truth — Spock | Sherlock Holmes

Источник

Arch Linux

You are not logged in.

#1 2012-06-06 03:16:23

[Solved] invalid or corrupted database (PGP signature)

When I try to run pacman -Syu, I get this error:

I have invoke the command pacman-key —init and pacman-key —populate archlinux as per instructed in the front page. Due to this problem, I am unable to upgrade any package, not until I set the SigLevel to Never. Here’s my pacman.conf if it’ll be any help.

Thanks in advance.

Last edited by teddypick3r (2012-06-13 21:30:09)

#2 2012-06-06 08:38:25

Re: [Solved] invalid or corrupted database (PGP signature)

Try commenting SigLevel = Optional TrustAll and uncommenting the SigLevel = PackageRequired for the individual repositories. Maybe changing the global SigLevel = PackageRequired also works, but I haven’t tried.
Look in pacman.conf.*new* (not sure about filename, it is created after the recent update) for an example like pacman said.

#3 2012-06-06 08:40:55

Re: [Solved] invalid or corrupted database (PGP signature)

Database signing hasn’t been implemented yet. Simply adding «DatabaseOptional» to your SigLevel line should take care of it.

#4 2012-06-06 09:22:28

Re: [Solved] invalid or corrupted database (PGP signature)

Hi, thanks for the replies.

I tried commenting out the global SigLevel, and also the suggestion of adding DatabaseOptional to my SigLevel, apparently both of them doesn’t solve my problem.

I try deleting the pacman.d/gnupg folder and re-init the pacman-key, the error still persists. any other idea?

#5 2012-06-06 12:35:49

Re: [Solved] invalid or corrupted database (PGP signature)

It would be strange that you still get pgp signature error when you’ve put «SigLevel = Never». Try doing a full database sync again (pacman -Syy).

#6 2012-06-06 13:34:53

Re: [Solved] invalid or corrupted database (PGP signature)

ah, maybe I didn’t explain myself well, sorry for that. What I mean is that the only way I can upgrade my system is by setting SigLevel to Never. I would love to implement package signing too.
What I’ve done is

1) add DatabaseOptional to SigLevel
2) deleted the pacman.d/gnupg and re-invoke pacman-key —init & pacman-key —populate archlinux

but the error still persists whenever I try to implement package signing.

#7 2012-06-06 15:32:48

Re: [Solved] invalid or corrupted database (PGP signature)

show us your pacman.conf

There’s no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

#8 2012-06-06 15:53:22

Re: [Solved] invalid or corrupted database (PGP signature)

show us your pacman.conf

that would be in the first post

#9 2012-06-06 16:34:09

Re: [Solved] invalid or corrupted database (PGP signature)

show us your pacman.conf

that would be in the first post

what version of pacman are you running. One option would be to simply set siglevel to never and update pacman to the latest. Then merge the pacman.conf file with the pacman.conf.pacnew. Then re-run pacman-key —init and pacman-key —populate archlinux

The new version of pacman has signing enabled by default and has siglevel=PackageRequired on all the official repositories. You can still set globally if you want to later.

There’s no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

#10 2012-06-06 17:24:21

Re: [Solved] invalid or corrupted database (PGP signature)

Same problem here.

1) upgraded pacman
2) replaced pacman-conf with pacman.conf.new
3) tried everything from above

For some tasks, the CLI is quicker. That’s not elitism nor arrogance, that’s just a fact of life.

#11 2012-06-06 19:01:00

Re: [Solved] invalid or corrupted database (PGP signature)

Same problem here.

1) upgraded pacman
2) replaced pacman-conf with pacman.conf.new
3) tried everything from above

Vi0L0 is a user, not an Arch dev. To get his key, see his forum signature: https://bbs.archlinux.org/profile.php?id=26754

Edit: The address mentioned in his profile seems down, use http://pgp.mit.edu:11371/pks/lookup?op= … 2d653c3094

Last edited by karol (2012-06-07 00:01:16)

#12 2012-06-07 03:07:03

Re: [Solved] invalid or corrupted database (PGP signature)

show us your pacman.conf

that would be in the first post

what version of pacman are you running. One option would be to simply set siglevel to never and update pacman to the latest. Then merge the pacman.conf file with the pacman.conf.pacnew. Then re-run pacman-key —init and pacman-key —populate archlinux

The new version of pacman has signing enabled by default and has siglevel=PackageRequired on all the official repositories. You can still set globally if you want to later.

I’m using the latest pacman 4.0.3-2. I did merge the pacman.conf.pacnew with the old one. I try re-run pacman-key -init and pacman-key —populate archlinux for quite a few times already yet the error persists.

#13 2012-06-07 19:41:32

Re: [Solved] invalid or corrupted database (PGP signature)

I was having the same problem.

I tried all the steps above but the only thing that helped me was changing mirrors.

I just started commenting them out in mirrorlist and finally it started working.

-ed+
But i should add, the only time it will perform package operations now I’m getting a 550 error:

Last edited by bioe007 (2012-06-07 19:50:44)

#14 2012-06-08 04:56:58

Re: [Solved] invalid or corrupted database (PGP signature)

I did try changing the mirror, yet the problem still persists. is the mirror affect the error? because I thought package signing is implemented on package level..

Last edited by teddypick3r (2012-06-08 05:03:59)

#15 2012-06-10 18:21:36

Re: [Solved] invalid or corrupted database (PGP signature)

I had the same issue too. I managed to fix it by ]running the command found under the header «Master Keys» of the pacman-key page: https://wiki.archlinux.org/index.php/Pacman-key

#16 2012-06-10 22:48:17

Re: [Solved] invalid or corrupted database (PGP signature)

the command found under the header «Master Keys» of the pacman-key page: https://wiki.archlinux.org/index.php/Pacman-key

#17 2012-06-11 02:18:03

Re: [Solved] invalid or corrupted database (PGP signature)

I had the same issue too. I managed to fix it by ]running the command found under the header «Master Keys» of the pacman-key page: https://wiki.archlinux.org/index.php/Pacman-key

I tried, but doesn’t solve the problem for me

#18 2012-06-13 09:56:09

Re: [Solved] invalid or corrupted database (PGP signature)

I had the same problem. It’s fixed now, but I don’t know what worked exactly.
What I did was replace my pacman.conf with one from colleague who did not have this problem. Global SigLevel was commented and repos have had their level set to PackageRequired in his conf file.
After running

with database update in the end

it started working. I have no idea what fixed it, but if you’re out of options you might want to reproduce it the way I did.

The weird thing is running the three commands by themselves was not fixing the issue a couple of days back.

#19 2012-06-13 17:18:05

Re: [Solved] invalid or corrupted database (PGP signature)

I had the same issue too. I managed to fix it by ]running the command found under the header «Master Keys» of the pacman-key page: https://wiki.archlinux.org/index.php/Pacman-key

I tried, but doesn’t solve the problem for me

I think the problem You are getting are caused by your custom XferCommand.
It seems pacman will always try to fetch the sig file for the db, even if key signing has not been enabled (BUG?). If your Xfer script leaves something behind when a file on the server is not found, that file will be used as a sig file. It will obviously not be a valid key file.
If you use something like curl in your script, it will create a HTML file when the file on the server is not found.

Check the files in /var/lib/pacman/sync. You shouldnt have any .db.sig files here.
You probably have .db.sig files here containing HTML code.

Make sure your Xfer script do not create .db.sig files.
Also make sure the script exits with a fault code when the file can not be found on the server.

The cake is a lie

#20 2012-06-13 21:29:50

Re: [Solved] invalid or corrupted database (PGP signature)

I had the same issue too. I managed to fix it by ]running the command found under the header «Master Keys» of the pacman-key page: https://wiki.archlinux.org/index.php/Pacman-key

I tried, but doesn’t solve the problem for me

I think the problem You are getting are caused by your custom XferCommand.
It seems pacman will always try to fetch the sig file for the db, even if key signing has not been enabled (BUG?). If your Xfer script leaves something behind when a file on the server is not found, that file will be used as a sig file. It will obviously not be a valid key file.
If you use something like curl in your script, it will create a HTML file when the file on the server is not found.

Check the files in /var/lib/pacman/sync. You shouldnt have any .db.sig files here.
You probably have .db.sig files here containing HTML code.

Make sure your Xfer script do not create .db.sig files.
Also make sure the script exits with a fault code when the file can not be found on the server.

Ah, at last. Thanks for your suggestion. Seems like the custom XferCommand is really the culprit after all. After I commenting it out, the package signing works flawlessly. Marked the thread as solved. Thanks again.

Источник

Googling the error, it redirects here. After doing rm -r /etc/pacman.d/gnupg/ && pacman-key --init && pacman-key --populate msys2 && pacman-key --refresh-keys, looks like some gpg keys has erros:

gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: key 280056C915DFC20C marked as ultimately trusted
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/6505491C7A061E293231E6B2280056C915DFC20C.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Appending keys from msys2.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signed 6 keys.
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
  -> Disabled 2 keys.
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   6  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:   6  signed:   5  trust: 0-, 0q, 0n, 6m, 0f, 0u
gpg: depth: 2  valid:   5  signed:   0  trust: 5-, 0q, 0n, 0m, 0f, 0u
gpg: error retrieving 'alexey.pawlow@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key F40D263ECA25678A: "Alexey Pavlov (Alexpux) <alexey.pawlow@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: error retrieving 'david.macek.0@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key 790AE56A1D3CFDDC: "David Macek (MSYS2 master key) <david.macek.0@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: error retrieving 'martellmalone@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key DA7EF2ABAEEA755C: "Martell Malone (martell) <martellmalone@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: error retrieving 'mingw.android@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key BBE514E53E0D0813: "Ray Donnelly (MSYS2 Developer - master key) <mingw.android@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: error retrieving 'reiter.christoph@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key 755B8182ACD22879: "Christoph Reiter (MSYS2 master key) <reiter.christoph@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: error retrieving 'icquinteiro@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key 9F418C233E652008: "Ignacio Casal Quinteiro <icquinteiro@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: error retrieving 'alexpux@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key 5F92EFC1A47D45A1: "Alexey Pavlov (Alexpux) <alexpux@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: error retrieving 'david.macek.0@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key 974C8BE49078F532: "David Macek <david.macek.0@gmail.com>" 3 new signatures
gpg: key 974C8BE49078F532: "David Macek <david.macek.0@gmail.com>" 1 signature cleaned
gpg: Total number processed: 1
gpg:         new signatures: 3
gpg:     signatures cleaned: 1
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   6  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:   6  signed:   6  trust: 0-, 0q, 0n, 6m, 0f, 0u
gpg: depth: 2  valid:   6  signed:   0  trust: 6-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2022-11-18
gpg: error retrieving 'martellmalone@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key D595C9AB2C51581E: "Martell Malone (MSYS2 Developer) <martellmalone@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: error retrieving 'reiter.christoph@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key FA11531AA0AA7F57: "Christoph Reiter (MSYS2 development key) <reiter.christoph@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: error retrieving 'me@martellmalone.com' via WKD: No name
gpg: error reading key: No name
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key 794DCF97F93FC717: "Martell Malone (martell) <me@martellmalone.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: error retrieving 'mingw.android@gmail.com' via WKD: No data
gpg: error reading key: No data
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: key 4DF3B7664CA56930: "Ray Donnelly (MSYS2 Developer) <mingw.android@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

The error still persists:

error: mingw-w64-x86_64-libvorbis: signature from "David Macek <david.macek.0@gmail.com>" is unknown trust
:: File /var/cache/pacman/pkg/mingw-w64-x86_64-libvorbis-1.3.7-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: mingw-w64-x86_64-ffms2: signature from "David Macek <david.macek.0@gmail.com>" is unknown trust
:: File /var/cache/pacman/pkg/mingw-w64-x86_64-ffms2-2.40-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

Maybe 3 or 4 years ago, I’ve posted a workaround here to a different MSYS error preventing me to upgrade the system.

The exact same workaround works with this one:

• Edit /etc/pacman.conf add SigLevel = Never and save.
• Run the command rm -r /etc/pacman.d/gnupg/ && pacman-key --init && pacman-key --populate msys2
• Try pacman -Suy again, it should work without any further issues.
• When all set and done, remove SigLevel = Never from /etc/pacman.conf and save.

Now everything should be working.

pacman -Suy
:: Synchronizing package databases...
 mingw32 is up to date
 mingw64 is up to date
 ucrt64 is up to date
 clang32 is up to date
 clang64 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

Hope it helps.

Только зарегистрированные и авторизованные пользователи могут оставлять комментарии.