Package Details: mingw-w64-tools 10.0.0-1

Git Clone URL: https://aur.archlinux.org/mingw-w64-tools.git (read-only, click to copy)
Package Base: mingw-w64-tools
Description: MinGW-w64 utilities
Upstream URL: http://mingw-w64.sourceforge.net
Keywords: mingw mingw-w64
Licenses: GPL3, LGPL2
Submitter: rubenvb
Maintainer: xantares
Last Packager: xantares
Votes: 18
Popularity: 1.37
First Submitted: 2011-11-15 18:00 (UTC)
Last Updated: 2022-05-04 18:18 (UTC)

Latest Comments

XkE5NBr2 commented on 2022-07-22 22:16 (UTC) (edited on 2022-07-22 22:32 (UTC) by XkE5NBr2)

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

Ciaran commented on 2022-05-06 16:27 (UTC)

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

xantares commented on 2022-03-04 07:59 (UTC) (edited on 2022-03-04 08:01 (UTC) by xantares)

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 ?

blakerateliff commented on 2022-03-04 01:57 (UTC) (edited on 2022-03-04 02:00 (UTC) by blakerateliff)

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

Building mingw-w64-tools...

==> Making package: mingw-w64-tools 9.0.0-1 (Thu 03 Mar 2022 07:46:11 PM CST)

==> Checking runtime dependencies...

==> Checking buildtime dependencies...

==> Retrieving sources...

-> Found mingw-w64-v9.0.0.tar.bz2

-> Found mingw-w64-v9.0.0.tar.bz2.sig

==> 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 ... FAILED (unknown public key 93BDB53CD4EBC740)

==> ERROR: One or more PGP signatures could not be verified!

Failed to build mingw-w64-tools

xantares commented on 2022-02-27 09:36 (UTC)

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

Kandelborg commented on 2022-02-25 11:47 (UTC)

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

xantares commented on 2022-02-18 09:55 (UTC) (edited on 2022-02-18 09:56 (UTC) by xantares)

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

Kandelborg commented on 2022-02-18 06:39 (UTC) (edited on 2022-02-18 06:58 (UTC) by Kandelborg)

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.

krs commented on 2022-02-06 19:44 (UTC) (edited on 2022-02-06 19:45 (UTC) by krs)

I had to append "/download" to the url in the sources line to make it download the actual files instead of what I assume was an html document. I'm using yay if that makes any difference but it didn't seem to make any difference by using makepkg directly.

djmattyg007 commented on 2022-02-05 05:33 (UTC)

When I build this package, makepkg outputs a warning saying it contains a reference to $srcdir.

xantares commented on 2021-10-26 10:59 (UTC)

the key is fine, you may have a problem with your gnupg

Adrian.Carver commented on 2021-10-21 14:37 (UTC) (edited on 2021-10-21 14:38 (UTC) by Adrian.Carver)

Is it possible to solve the problem with the key?

gpg --recv-key CAF5641F74F7DFBA88AE205693BDB53CD4EBC740

gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat trust hashing ipc clock lookup extprog

gpg: DBG: [not enabled in the source] start

gpg: DBG: chan_3 <- # Home: /home/adrian/.gnupg

gpg: DBG: chan_3 <- # Config: /home/adrian/.gnupg/dirmngr.conf

gpg: DBG: chan_3 <- OK Dirmngr 2.2.29 at your service

gpg: DBG: connection to the dirmngr established

gpg: DBG: chan_3 -> GETINFO version

gpg: DBG: chan_3 <- D 2.2.29

gpg: DBG: chan_3 <- OK

gpg: DBG: chan_3 -> KS_GET -- 0xCAF5641F74F7DFBA88AE205693BDB53CD4EBC740

gpg: DBG: chan_3 <- ERR 167772380 Нет имени <Dirmngr>

gpg: сбой при получении с сервера ключей: Нет имени

gpg: DBG: chan_3 -> BYE

gpg: DBG: [not enabled in the source] stop

gpg: keydb: handles=0 locks=0 parse=0 get=0

gpg: build=0 update=0 insert=0 delete=0

gpg: reset=0 found=0 not=0 cache=0 not=0

gpg: kid_not_found_cache: count=0 peak=0 flushes=0

gpg: sig_cache: total=0 cached=0 good=0 bad=0

gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0

          outmix=0 getlvl1=0/0 getlvl2=0/0

gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0

gpg: secmem usage: 0/32768 bytes in 0 blocks

Paradox625 commented on 2021-10-18 05:50 (UTC)

if you get "one or more pgp signatures could not be verified" then you need to import the keys:

CAF5641F74F7DFBA88AE205693BDB53CD4EBC740

short answer:

gpg --recv-key CAF5641F74F7DFBA88AE205693BDB53CD4EBC740

xantares commented on 2021-06-25 19:22 (UTC) (edited on 2021-06-25 19:24 (UTC) by xantares)

gnupg is broken currently, choose another keyserver in your gpg.conf

https://bugs.archlinux.org/task/71078?project=1&string=gnupg

Deep6 commented on 2021-06-25 17:30 (UTC)

This package's PGP key is broken:

:: PGP keys need importing: -> CAF5641F74F7DFBA88AE205693BDB53CD4EBC740, required by: mingw-w64-tools ==> Import? [Y/n] Y :: Importing keys with gpg... gpg: keyserver receive failed: No name problem importing keys

Ranguvar commented on 2021-06-12 07:00 (UTC)

Moo-Crumpus, that key isn't broken and can be imported

Version 9.0.0 builds fine

Moo-Crumpus commented on 2021-05-05 11:18 (UTC) (edited on 2021-05-05 11:21 (UTC) by Moo-Crumpus)

can't compile, the PGP key is broken and will not be imported. gpg: Key 93BDB53CD4EBC740

ESI commented on 2019-11-11 06:22 (UTC) (edited on 2019-11-11 07:23 (UTC) by ESI)

Hello.

I got sha256sum error when I making latest mingw-w64-tools package. So I guess mingw-w64-v7.0.0.tar.bz2 has been changed.

According to https://sourceforge.net/projects/mingw-w64/files/mingw-w64/mingw-w64-release/

mingw-w64-v7.0.0.tar.bz2

SHA1SUM: 25940043c4541e3e59608dead9b6f75b5596d606
MD5SUM: 7cd9b09be0b2c658ce200c4c43b59b27
and the page said "Modified 5 hours ago"

And, Here is the error and some check-sums.

$ git clone https://aur.archlinux.org/mingw-w64-tools.git
$ cd mingw-w64-tools
$ makepkg -si
==> Making package: mingw-w64-tools 7.0.0-1 (Mon 11 Nov 2019 02:30:39 PM JST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading mingw-w64-v7.0.0.tar.bz2...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 18014  100 18014    0     0  13284      0  0:00:01  0:00:01 --:--:-- 13274
100 18001  100 18001    0     0  10676      0  0:00:01  0:00:01 --:--:-- 10676
100 18076  100 18076    0     0   9533      0  0:00:01  0:00:01 --:--:--  9533
100   389  100   389    0     0    126      0  0:00:03  0:00:03 --:--:--   428
100 8858k  100 8858k    0     0  1187k      0  0:00:07  0:00:07 --:--:-- 2070k
  -> Downloading mingw-w64-v7.0.0.tar.bz2.sig...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 18021  100 18021    0     0  13672      0  0:00:01  0:00:01 --:--:-- 13683
100 18008  100 18008    0     0  12069      0  0:00:01  0:00:01 --:--:-- 12069
100 18084  100 18084    0     0  10893      0  0:00:01  0:00:01 --:--:--     0
100   397  100   397    0     0    140      0  0:00:02  0:00:02 --:--:--  1464
100   148  100   148    0     0     41      0  0:00:03  0:00:03 --:--:--  4933
==> Validating source files with sha256sums...
    mingw-w64-v7.0.0.tar.bz2 ... FAILED
    mingw-w64-v7.0.0.tar.bz2.sig ... Skipped
==> ERROR: One or more files did not pass the validity check!


$ sha1sum mingw-w64-v7.0.0.tar.bz2
25940043c4541e3e59608dead9b6f75b5596d606  mingw-w64-v7.0.0.tar.bz2

$ md5sum mingw-w64-v7.0.0.tar.bz2
7cd9b09be0b2c658ce200c4c43b59b27  mingw-w64-v7.0.0.tar.bz2

$ sha256sum mingw-w64-v7.0.0.tar.bz2
aa20dfff3596f08a7f427aab74315a6cb80c2b086b4a107ed35af02f9496b628  mingw-w64-v7.0.0.tar.bz2

$ cat PKGBUILD | grep sha256sums
sha256sums=('f5c9a04e1a6c02c9ef2ec19b3906ec4613606d1b5450d34bbd3c4d94ac696b3b'

Also I found some "6.0.0" remains in PKGBUILD.

rubenvb commented on 2017-06-04 08:54 (UTC)

I uploaded a patch adding // fallthrough comments, which put GCC at ease: https://sourceforge.net/p/mingw-w64/bugs/616/ I also sent it to the mingw-w64-public mailing list.

Schala commented on 2017-06-04 02:20 (UTC)

fixed

xantares commented on 2017-06-03 13:17 (UTC) (edited on 2017-06-03 13:30 (UTC) by xantares)

hi, it doesn't build with gcc 7: src/mingw-w64-v5.0.2/mingw-w64-tools/gendef/src/gendef.c:1034:15: error: this statement may fall through [-Werror=implicit-fallthrough=] case c_4: sz++; I opened https://sourceforge.net/p/mingw-w64/bugs/616/ maybe werror could be disabled for now ? xan.

Schala commented on 2015-03-25 17:55 (UTC)

No idea, ask Fedora

xantares commented on 2015-03-16 10:03 (UTC)

hi, why aren't the patch upstreamed ? xan.

Schala commented on 2014-07-10 02:22 (UTC)

added i686-w64-mingw32-widl and x86_64-w64-mingw32-widl binaries, with Fedora patches

rubenvb commented on 2014-07-06 10:01 (UTC)

I orphaned this as per request. Feel free to bump the version numbers :-)