On Tue 2016-03-22 12:49:10 -0400, Didier 'OdyX' Raboud wrote: > I've noticed that gpgv.exe fails its CI test (debian/tests/gpgv-win32) in > version 1.4.20-4 (-3 and previous work fine):
interesting, there was no change between -3 and -4 other than re-adding the gpgv-udeb for constrained armel devices at tbm's request (see #814027). I suspect this means that the toolchain changed in some significant way between these releases. > (This is after adding WINEDEBUG=err+all as prefix to the latest line): > > err:menubuilder:init_xdg error looking up the desktop directory > err:module:import_dll Library zlib1.dll (which is needed by > L"Z:\\usr\\share\\win32\\gpgv.exe") not found > err:module:LdrInitializeThunk Main exe initialization for > L"Z:\\usr\\share\\win32\\gpgv.exe" failed, status c0000135 > > It seems gpgv-win32 is dynamically linked against zlib1.dll, where it should > probably be statically linked. This appears to be a problem in the dependency > chain. hm, right. I'm actually working on moving gpgv.exe over to the gnupg2 packaging, so that we can get support for elliptic curve signatures as well. I'll definitely test to ensure that it's properly statically linked when i produce it from that source. > (By the way, the CI seems to have never run successfully in the last months: > https://ci.debian.net/packages/g/gnupg/unstable/amd64/ …) this appears to be because of uninstallable dependencies; the tests can really only run on i386 systems or multiarch systems, right? is wine32 available in amd64? I don't see any other architectures available at https://ci.debian.net/packages/g/gnupg/unstable/, and i'm assuming that the amd64 ci tester isn't multiarch. or am i misinterpreting something? --dkg
signature.asc
Description: PGP signature