Bug#950711: marked as done (apache2: autopkgtest use hardcoded libgcc_s.so.1 path)
Your message dated Wed, 05 Feb 2020 12:49:29 +0000
with message-id <E1izK7V-0000Hl-EP@fasolo.debian.org>
and subject line Bug#950711: fixed in apache2 2.4.41-3
has caused the Debian Bug report #950711,
regarding apache2: autopkgtest use hardcoded libgcc_s.so.1 path
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 owner@bugs.debian.org
immediately.)
--
950711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950711
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: apache2
Version: 2.4.41-2
Severity: serious
apache2 autopkgtest hard codes the patch to libgcc_s.so.1 in
debian/tests/chroot:
| LIBGCC_S_PATH=/lib/$(dpkg-architecture -qDEB_HOST_MULTIARCH)/libgcc_s.so.1
Starting with libgcc1 >= 10, aka libgcc-s1, the file has been moved to
/usr/lib/$(DEB_HOST_MULTIARCH)/libgcc_s.so.1, causing the autopkgtest to
fail. Here is the full log to the failure:
https://ci.debian.net/data/autopkgtest/testing/amd64/a/apache2/4201876/log.gz
If you really need to know the path of this library, I suggest to use
the following code, with a dependency on gcc:
| gcc --print-file-name=libgcc_s.so.1
-- 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
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.41-3
We believe that the bug you reported is fixed in the latest version of
apache2, 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 950711@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Xavier Guimard <yadd@debian.org> (supplier of updated apache2 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 ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 05 Feb 2020 13:18:04 +0100
Source: apache2
Architecture: source
Version: 2.4.41-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Apache Maintainers <debian-apache@lists.debian.org>
Changed-By: Xavier Guimard <yadd@debian.org>
Closes: 950711
Changes:
apache2 (2.4.41-3) unstable; urgency=medium
.
* Don't use hardcoded libgcc_s.so.1 path in autopkgtest files. Thanks to
Aurelien Jarno (Closes: #950711)
Checksums-Sha1:
329b87839bc9b41e2bb75b9c9b5ebdfc3a20c14d 3493 apache2_2.4.41-3.dsc
a9621b88fc9db2287160002b69a260261adfb05c 1016060 apache2_2.4.41-3.debian.tar.xz
Checksums-Sha256:
5e6bf2860ea7f3034ba8c2c42d2439735b2ebea9a8539c09240c5008121d60f8 3493 apache2_2.4.41-3.dsc
23699b7a7f62320a64726b2765baa8222e3f384e33cb767c07d2fb28425fb589 1016060 apache2_2.4.41-3.debian.tar.xz
Files:
71ee9b7a0dabc2e126d3d7edb682313b 3493 httpd optional apache2_2.4.41-3.dsc
146e65c2f2d1480dd9286e5e1d784081 1016060 httpd optional apache2_2.4.41-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl46tLsACgkQ9tdMp8mZ
7umXag//dXfbGSVEecOb7Pl6oW55b0tCTBvfFVdU5wg9pJI4xjhlfon5xTYNxsd7
zTlxiRT8G63Jec6F6OopXWcedRiwK0KrxGAvuWX9UB2+bjeGoxoV7ks643Gy114I
uv1EpYi4fUXNKi6G8h+3eyiaKnJuOmqB5iLob4Ujuj0sfxEc51auKVCm0jC7lUXf
9lQDDRWiaElo7B8QWEqRAtgTFfGgGr0af0L8JKp3VsFlIt9O7v0suLqPb2frtjV9
BfIkP0DbdKCyM8LYOQhF6tOSjTx5i7sTsVqNYDmihT2K6gWaeUSTlb44e/2jVDpU
IGAt5T2GBGttJgArBTcdVgRIbPs7V+iQbVTcbO2CJUTaCEzQdX9ts1lHeHilmFdm
dX3J+AvontGMD4n8pu+an9+TmWprFV2iMzrPNkK2MdbLGmylSVtrcU0Ss1JTwqwg
4RKIl4tuQRwzSjvSozqvRzNApk58hdZ2OxQNryOXq4gHsnsi988rJgbvziszowAJ
eYPKwlLii35U+EH4atxe8WR4h5XnSkBZXH9fcwBVDZVta26CGRl/tMsEpE9e6cTD
g4YO878+jd4/9DKrZ2cie20uQCGVEMHgt5eva1ef2HefxyMGJ+PWmPTXUQJ7A1oV
ru9tIG/vU3XNfdrmD5GYSuCfO1qbn8YtkfFCDME2tW1+8T1Thz0=
=SsLy
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: