Your message dated Thu, 1 Feb 2024 23:09:55 +0100
with message-id <828db802-fc9a-48b0-86e5-180134244...@debian.org>
and subject line fixed
has caused the Debian Bug report #1061370,
regarding libatomic1: 14-20240127-1 missing libat_test_and_set_1_i2
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.)
--
1061370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libatomic1
Version: 14-20240127-1
Severity: grave
Justification: breaks a lot of unrelated packages
Hello,
yesterday's cockpit armel build failed [1] on armel like this in the
./configure test for the PCP library:
| configure:6158: gcc -o conftest -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro
conftest.c -lssh >&5
| /usr/bin/ld: /lib/arm-linux-gnueabi/libatomic.so.1: undefined reference to
`libat_test_and_set_1_i2'
PCP hasn't changed since the previous build [2]; however, libatomic1 (via
gcc-14) did -- [2] built against libatomic1/gcc 13.2.0-9.
I spot-checked a few of the autopkgtest regressions on the PTS [3], and they
all failed on the exact same issue, e.g. [4].
Thanks!
Martin
[1]
https://buildd.debian.org/status/fetch.php?pkg=cockpit&arch=armel&ver=310-1&stamp=1706722995&raw=0
[2]
https://buildd.debian.org/status/fetch.php?pkg=cockpit&arch=armel&ver=309-1&stamp=1705590895&raw=0
[3] https://tracker.debian.org/pkg/gcc-14
[4] https://ci.debian.net/packages/3/389-ds-base/testing/armel/42559327/
--- End Message ---
--- Begin Message ---
Version: 14-20240201-2
fixed
--- End Message ---
