Arch Linux User Repository

Hi together,

I would like to maintain this package in the official repository in archlinux. Since this project (PKGBUILD) currently does not maintain a LICENSE file, it would be welcome, if the maintainer provide a 0BSD license in it. You can find more informations here: https://archlinux.org/news/providing-a-license-for-package-sources/

It would be also okay, if I get from all contributors a confirmation to switch to the 0-BSD License.

Thanks!

@XkE5NBr2

try using the port. for example gpg --keyserver hkps://keyserver.ubuntu.com:443 --recv-key 93BDB53CD4EBC740 works for me while gpg --keyserver hkps://keyserver.ubuntu.com --recv-key 93BDB53CD4EBC740 does not.

@Ciaran

gpg --keyserver hkps://pgp.surf.nl --recv-key 93BDB53CD4EBC740
gpg: keyserver receive failed: Server indicated a failure

I get these same results with all three key servers you've suggested. Please advise.

Update! Now the package builds!

The root cause here apparently is that GPG doesn't play nice with systemd-resolved. I needed to run a command, per this StackOverflow page: gpg: keyserver receive failed: Server indicated a failure .

rm /etc/resolv.conf
ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

This is because I'm using systemd-resolved and had nothing but comments in resolv.conf. Other users may need to take different corrective action.

For those with GPG key issues, try another keyserver as in https://superuser.com/questions/1485213/gpg-cant-import-key-new-key-but-contains-no-user-id-skipped/1485255#1485255:

--keyserver hkps://keyserver.ubuntu.com
--keyserver hkps://pgp.surf.nl
--keyserver hkp://pgp.rediris.es

Example:

gpg --keyserver hkps://pgp.surf.nl --recv-key 93BDB53CD4EBC740
gpg: key 93BDB53CD4EBC740: public key "JonY <jon_y@users.sourceforge.net>" imported
gpg: Total number processed: 1
gpg:               imported: 1

I think something is up with your gpg configuration, this key is valid until 2024:

$ gpg --recv-keys CAF5641F74F7DFBA88AE205693BDB53CD4EBC740 gpg: key 93BDB53CD4EBC740: public key "JonY jon_y@users.sourceforge.net" imported gpg: Total number processed: 1 gpg: imported: 1

$ gpg --list-keys ... pub dsa3072 2014-11-20 [SCA] [expires: 2024-11-10] CAF5641F74F7DFBA88AE205693BDB53CD4EBC740 uid [ unknown] JonY jon_y@users.sourceforge.net sub elg3072 2014-11-20 [E] [expires: 2024-11-10]

what package manager are you using ?

what is your gpg server ?

Package does not build due to the included gpg key being invalid/outdated:

Building mingw-w64-tools...

mingw-w64-v9.0.0.tar.bz2 ... FAILED (unknown public key 93BDB53CD4EBC740)

Could you post the modification done to your gpg configuration that is not blocked by your network ? it could be useful to the other users out there

"You can't claim that 'it works on your computer' because that's literally why we're here" - way to disregard my message.

But sure, dismiss my entire comment. I got it to work by trying 7 different keyservers, so if anyone has the gpg key problem, it's nonexistent as per the author and you better just figure it out.

Linux gaming? Sure, if package maintenance was done by people who cared.

This works on my side: you can see in this log that the key is properly fetched and that gpg verification succeeds:

:: Synchronizing package databases... core downloading... extra downloading... community downloading... :: Starting full system upgrade... there is nothing to do Cloning into 'mingw-w64-tools'... gpg: key 93BDB53CD4EBC740: public key "JonY jon_y@users.sourceforge.net" imported
gpg: Total number processed: 1
gpg: imported: 1
==> Making package: mingw-w64-tools 9.0.0-1 (Fri 18 Feb 2022 09:53:57 AM UTC) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading mingw-w64-v9.0.0.tar.bz2... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed
100 416 100 416 0 0 473 0 --:--:-- --:--:-- --:--:-- 473
100 432 100 432 0 0 388 0 0:00:01 0:00:01 --:--:-- 0
100 673 100 673 0 0 507 0 0:00:01 0:00:01 --:--:-- 507
100 399 100 399 0 0 145 0 0:00:02 0:00:02 --:--:-- 741
100 9314k 100 9314k 0 0 1996k 0 0:00:04 0:00:04 --:--:-- 5614k
-> Downloading mingw-w64-v9.0.0.tar.bz2.sig... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed
100 424 100 424 0 0 1043 0 --:--:-- --:--:-- --:--:-- 1041
100 440 100 440 0 0 687 0 --:--:-- --:--:-- --:--:-- 687
100 673 100 673 0 0 721 0 --:--:-- --:--:-- --:--:-- 721
100 399 100 399 0 0 190 0 0:00:02 0:00:02 --:--:-- 1170
100 148 100 148 0 0 59 0 0:00:02 0:00:02 --:--:-- 729
==> Validating source files with sha256sums... mingw-w64-v9.0.0.tar.bz2 ... Passed mingw-w64-v9.0.0.tar.bz2.sig ... Skipped
==> Verifying source file signatures with gpg... mingw-w64-v9.0.0.tar.bz2 ... Passed

GPG key has issues or is too new or something like that. I just did a 10-month old system upgrade with thousands of packages without problems, besides steam not working... I realize I need the lib32 packages, but now when I try to install Proton, mingw-w64-tools is the only package out of thousands of others (and a gpg keyserver update, and all that's needed there)

And this is the only problem I've had with GPG. There is definitely a problem. You can't claim that 'it works on your computer' because that's literally why we're here, please acknowledge the problem and try to fix it. Your key is not on all the keyservers or whatever else the problem might be, but it's not without problems, that's for sure.