Your message dated Fri, 07 Feb 2020 08:40:07 +0000
with message-id <e1izzbh-0003uz...@fasolo.debian.org>
and subject line Bug#948613: fixed in wcc 0.0.2+dfsg-4
has caused the Debian Bug report #948613,
regarding wcc: autopkgtests try to dlopen PIE executables
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
948613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wcc
Version: 0.0.2+dfsg-3
Severity: serious
Dear wcc maintainers,
The wcc autopkgtests try to dlopen some PIE executables (namely
/usr/bin/ssh). This has never been really supported, and this fails with
an error message in recent glibc versions. This cause the autopkgtest to
fail:
| autopkgtest [11:11:14]: test command1: ./debian/tests/wsh-ssl.wsh /usr/bin/ssh
| autopkgtest [11:11:14]: test command1: [-----------------------
| ERROR: dlopen() /usr/bin/ssh: cannot dynamically load position-independent
executable
| ERROR: dlopen() of patched file! //tmp/.wsh-1902/ssh: cannot dynamically load
position-independent executable
| WARNING: No binary loaded in memory. Try loadbin(). For help type
help("loadbin").
| lua_pcall() failed with ./debian/tests/wsh-ssl.wsh:6: attempt to call a nil
value (global 'MD5_Init'), for: ./debian/tests/wsh-ssl.wsh
| init
| ** libifying /usr/bin/ssh to //tmp/.wsh-1902/ssh (760616 bytes)
| -- input: my best friend is a little poney !
| -- md5 hexdump
| autopkgtest [11:11:15]: test command1: -----------------------]
| autopkgtest [11:11:15]: test command1: - - - - - - - - - - results - - - - -
- - - - -
| command1 FAIL non-zero exit status 42
(see https://ci.debian.net/data/autopkgtest/testing/amd64/w/wcc/3942223/log.gz)
You can see reason for disabling dlopening PIE binaries in this upstream
bug report:
https://sourceware.org/bugzilla/show_bug.cgi?id=24323
It is unclear to me what this change means for the wcc testsuite and for
the usability of the wcc package. Could you please explain me how is it
used?
Thanks,
Aurelien
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages wcc depends on:
ii libbinutils 2.33.1-6
ii libc6 2.29-7
ii libcapstone3 4.0.1+really+3.0.5-1+b1
ii libelf1 0.176-1.1
ii liblua5.3-0 5.3.3-1.1+b1
wcc recommends no packages.
Versions of packages wcc suggests:
pn lua <none>
--- End Message ---
--- Begin Message ---
Source: wcc
Source-Version: 0.0.2+dfsg-4
We believe that the bug you reported is fixed in the latest version of
wcc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Philippe Thierry <phi...@debian.org> (supplier of updated wcc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 06 Feb 2020 09:11:20 +0100
Source: wcc
Architecture: source
Version: 0.0.2+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools <team+pkg-secur...@tracker.debian.org>
Changed-By: Philippe Thierry <phi...@debian.org>
Closes: 948613 949601
Changes:
wcc (0.0.2+dfsg-4) unstable; urgency=medium
.
* Updated binutils usage, making libbfd linked staticaly (Closes: #949601)
* Removed wsh test on PIE exe (ssh) as PIE exe are not supported.
This is a wcc upstream constraint (Closes: #948613)
* Add Reproductible build patch, removing compile time info in binary.
* Corrected chunk position in wcc.c patch.
Checksums-Sha1:
3b3c4258a717d992b946214dc88e2e4455cd5074 2113 wcc_0.0.2+dfsg-4.dsc
6c9c0c6e4056d4f9159cf9f34b3e42b01c5247aa 15360 wcc_0.0.2+dfsg-4.debian.tar.xz
dc891e2526eb3b8ad95f9bdbbbbe397e1f4bb158 7062 wcc_0.0.2+dfsg-4_amd64.buildinfo
Checksums-Sha256:
7c6897e08b38e8019f0dbae05abd69d126e273f80d6b5845da08b99a0a468a51 2113
wcc_0.0.2+dfsg-4.dsc
e8f1221585738546de28aa81b9ec98c4d78a47ee92ec8334178abd94e1118ecb 15360
wcc_0.0.2+dfsg-4.debian.tar.xz
06255b61b676b611f7352ecdd83687991e86e007a79fa71e5b9d8dfd5bf3fea2 7062
wcc_0.0.2+dfsg-4_amd64.buildinfo
Files:
5d5724f9866083f0c74e71e3d908a54b 2113 utils optional wcc_0.0.2+dfsg-4.dsc
943a4e5e33442cc1793efc9823ad92dd 15360 utils optional
wcc_0.0.2+dfsg-4.debian.tar.xz
d93706b47da9d6a134e63d0755ba4fc8 7062 utils optional
wcc_0.0.2+dfsg-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/N321ye0S80G/xoyyJ1XEt+UX28FAl49GJYACgkQyJ1XEt+U
X2+uJQ//Ww98PL5VPBBLj+6tu1l9bK+VKgyW3mAbW/q4b3xJGQ2z7DmYVclsNqxn
ZgEOELzZzgiw7j4H6mGFmvCld769SPdOuvENLet9kLHYYIgmT+7KB9TS8ZaOt2tf
OTPmK3UCNaM8JL0Cu1b6HP3DEQimJSEbtJacX3jkPwPiKvH7LW27MvYkZZu/TVKB
I+rVFauAjt0eF+82SmfNaN7GmvsV5NQE/vN9RPUUIieFrOHAHS5QPF9Fm9O39U38
8qeJsNOyt6v5Zab/sIULJpAxfmtRK2mMOIeEhrUrisZ4X3iArjlzmGYH13mv/LUO
d/c3ZEDr1z24Ju/FFBmzscQuIILasLNRAextxc47i4+RawUGL0xmNqzX9hIJzIOP
5dZatYB4kjJWNBkgHUsmjeHS0QyUPgEYyfS9rw1yJqQ6VgD31EpKSiZZbIEnMdiA
UJZInCQiUARpxn3AONXEz1N4bFa99vKl2b5gkPZvNCd9wCPIiu++yMQg/rqSrjFo
otDmLkHeQbyYIulOq3BjYJG6fz/YMpNB+LRF+NoU77FFhtQHIkGcdiXpfrhNP8AH
MLYKx4Z2PHOHwAyP6NXziM6f53THLA0yIZjMV8BgUdn9pT+YdTWctLweSs3neIg7
qemfCvzPwBTLrbagdR+wX6uhaDinHEKkhQAEMiLw146Xi1RR5tE=
=gkZx
-----END PGP SIGNATURE-----
--- End Message ---
