search

mamedev / buildtools

MAME Build Tools
Creative Commons Zero v1.0 Universal
31 stars 12 forks source link

Package updates needed #5

Open EvilNuff opened 2 years ago

EvilNuff commented 2 years ago

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 commented 2 years ago

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

EvilNuff commented 2 years ago

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 commented 2 years ago

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