Msys2-packages: [BUG] Failure to Update

Created on 4 Jul 2020 · 17Comments · Source: msys2/MSYS2-packages

Azure and AppVeyor builds started doing this just a few hours ago.

:: Synchronizing package databases...
downloading mingw32.db...
downloading mingw32.db.sig...
error: mingw32: key "(REDACTED)" is unknown
error: mingw32: signature from "David Macek <(REDACTED)>" is unknown trust
error: failed to update mingw32 (invalid or corrupted database (PGP signature))
:: Import PGP key (REDACTED) "David Macek <(REDACTED)>", created: 2018-01-14? [Y/n] 
downloading mingw64.db...
downloading mingw64.db.sig...
error: mingw64: signature from "David Macek <(REDACTED)>" is unknown trust
error: failed to update mingw64 (invalid or corrupted database (PGP signature))
downloading msys.db...
downloading msys.db.sig...
error: msys: signature from "David Macek <(REDACTED)>" is unknown trust
error: failed to update msys (invalid or corrupted database (PGP signature))
error: failed to synchronize all databases
##[error]Cmd.exe exited with code '1'.
Finishing: Update MSYS2

Source

RobertBColton

Most helpful comment

This instruction may help https://www.msys2.org/news/#2020-06-29-new-packagers.

Biswa96 on 26 Jul 2020

👍5

All 17 comments

Same here.

DDoSolitary on 4 Jul 2020

same here

adonaimartins on 4 Jul 2020

same here as well

drencorxeen on 4 Jul 2020

We've reverted some things. Can anyone try again?

lazka on 4 Jul 2020

Some packages were updated one minute ago now those are downgrading. No signature issue in my case.

Biswa96 on 4 Jul 2020

Some packages were updated one minute ago now those are downgrading. No signature issue in my case.

that's expected

lazka on 4 Jul 2020

@lazka OK, it is working now again. The signature issue reported here has disappeared.
Would you mind posting a link here to what was reverted (what fixed it)?

c72578 on 4 Jul 2020

The pacman database files (http://repo.msys2.org/msys/x86_64/msys.db and others).

elieux on 6 Jul 2020

First of all, many thanks for this useful software.

I also have a problem updating.

I closed all msys2 und stopped the sshd service.
on the Windows Server 2016.
When I use msys2-x86_64-20200629.exe for msys2 installation, I cannot start a shell
C:\msys64\usr\bin\bash at cmd.exe shell gave a message like
bash shared_info::initialize: size of shared memory region changed from xxx to xxx
Sorry for not keeping the exact message.
I repeated the process twice with the same result.
Installing with older version msys2-x86_64-20190524.exe works fine.
However, pacman -Sy msys2-runtimerenders the Msys2 unfunctional again.
I am currently happy with the msys2-x86_64-20190524.exe installation.

cgille on 7 Jul 2020

Just attempted pacman -Su and hit this snag. Found this thread and was still unable to find actions I can take to recover.

Is there a simple set of actions to take advantage of the reverted elements? Do I need to reinstall a particular version then update?

marawuti on 26 Jul 2020

This instruction may help https://www.msys2.org/news/#2020-06-29-new-packagers.

Biswa96 on 26 Jul 2020

👍5

Thank you

On Sun, Jul 26, 2020 at 9:21 AM Biswapriyo Nath notifications@github.com
wrote:

This instruction may help
https://www.msys2.org/news/#2020-06-29-new-packagers.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/msys2/MSYS2-packages/issues/2033#issuecomment-664008650,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW7CY75OGSJLFKXXSQJCJ3R5RJ2DANCNFSM4OQDUPTA
.

marawuti on 26 Jul 2020

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

I noticed that these are not present in the i686 directory. I am running on a 32-bit OS, and never got these updates through normal pacman -Syuu. Should they have been in i686 as well as x86_64, even though they are -any? I installed manually as per the instructions in the link, and that worked, but wants to downgrade msys2-keyring back to -r9...

jeremyd2019 on 26 Jul 2020

I noticed that these are not present in the i686 directory.

See https://www.msys2.org/news/#2020-05-17-32-bit-msys2-no-longer-actively-supported

lazka on 26 Jul 2020

👎1

Oh dear. I have a tablet with a 32-bit UEFI and cannot boot a 64-bit Windows despite having a 64-bit capable processor.

jeremyd2019 on 26 Jul 2020

signature issues happens again?

>pacman -Sy --noconfirm 
error: mingw32: signature from "David Macek <[email protected]>" is marginal trust
error: mingw64: signature from "David Macek <[email protected]>" is marginal trust
error: msys: signature from "David Macek <[email protected]>" is marginal trust
:: Synchronizing package databases...
downloading mingw32.db...
downloading mingw32.db.sig...
error: mingw32: signature from "David Macek <[email protected]>" is marginal trust
error: failed to update mingw32 (invalid or corrupted database (PGP signature))
downloading mingw64.db...
downloading mingw64.db.sig...
error: mingw64: signature from "David Macek <[email protected]>" is marginal trust
error: failed to update mingw64 (invalid or corrupted database (PGP signature))
downloading msys.db...
downloading msys.db.sig...
error: msys: signature from "David Macek <[email protected]>" is marginal trust
error: failed to update msys (invalid or corrupted database (PGP signature))
error: failed to synchronize any databases
error: failed to init transaction (invalid or corrupted database (PGP signature))