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

Package updates needed #5

Open
EvilNuff opened this issue Oct 7, 2021 · 3 comments
Open

Package updates needed #5

EvilNuff opened this issue Oct 7, 2021 · 3 comments

Comments

@EvilNuff
Copy link

EvilNuff commented Oct 7, 2021

msys2 had a change in packagers and therefore key updates. The latest mamedev tools do not include these key updates. See here:
https://www.msys2.org/news/#2020-06-29-new-packagers

The fix is to update the keyring which requires pacman-key from the dev tools and this does not appear to be included in the mamedev build.

@p1pkin
Copy link
Member

p1pkin commented Oct 7, 2021

are you sure issue is real ? for me "pacman -Syu" still works no problems, no any additional actions was made, it just works.

@EvilNuff
Copy link
Author

EvilNuff commented Oct 7, 2021

It is real for me, unless of course I am experiencing a user error. Fresh version on a clean install causes the same signature errors in the linked post.
Edit: I am wiping and trying again FYI.
Edit2: After wiping and reinstalling from scratch I still get the same error. Following the instructions here: https://github.com/mamedev/buildtools
When I try to update the build tools I get a number of errors such as this:
error: mingw-w64-x86_64-xz: signature from "David Macek david.macek.0@gmail.com" is unknown trust
:: File /var/cache/pacman/pkg/mingw-w64-x86_64-xz-5.2.5-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]

This indicates to me (in my admittedly limited understanding of msys2) that the version in the latest mamedev version does not have the correct keys. This is what is causing the unknown trust errors.

So yes, I feel pretty confident that this is a real issue.

@p1pkin
Copy link
Member

p1pkin commented Oct 7, 2021

I've tried clean install, and at 1st launch pacman showed some warning/error messages, however it seems worked OK and at 2nd and furthers runs pacman works as usual...

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

2 participants