Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Failure to Update #2033

Closed
RobertBColton opened this issue Jul 3, 2020 · 18 comments
Closed

[BUG] Failure to Update #2033

RobertBColton opened this issue Jul 3, 2020 · 18 comments

Comments

@RobertBColton
Copy link

RobertBColton commented Jul 3, 2020

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
@DDoSolitary
Copy link

Same here.

@adonaimartins
Copy link

same here

@drencorxeen
Copy link

same here as well

@lazka
Copy link
Member

lazka commented Jul 4, 2020

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

@Biswa96
Copy link
Member

Biswa96 commented Jul 4, 2020

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

@lazka
Copy link
Member

lazka commented Jul 4, 2020

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

that's expected

@c72578
Copy link

c72578 commented Jul 4, 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)?

@elieux
Copy link
Member

elieux commented Jul 6, 2020

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

@cgille
Copy link

cgille commented Jul 7, 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.

@marawuti
Copy link

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?

@Biswa96
Copy link
Member

Biswa96 commented Jul 26, 2020

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

@marawuti
Copy link

marawuti commented Jul 26, 2020 via email

@jeremyd2019
Copy link
Member

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...

@lazka
Copy link
Member

lazka commented Jul 26, 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

@jeremyd2019
Copy link
Member

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.

@ukai
Copy link

ukai commented Jul 27, 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))

@lazka
Copy link
Member

lazka commented Jul 27, 2020

yes, see #2058

@Juan321654
Copy link

still happening

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests