Your message dated Sat, 10 Feb 2024 13:11:20 +0000
with message-id <e1ryn8a-002yas...@coccia.debian.org>
and subject line Released with 12.5
has caused the Debian Bug report #1059846,
regarding bookworm-pu: package isl/0.25-1.1
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.)
--
1059846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian....@packages.debian.org
Usertags: pu
X-Debbugs-Cc: i...@packages.debian.org
Control: affects -1 + src:isl
[ Reason ]
The isl package detects the CPU on which it is built and enables the
corresponding GCC optimization. Depending on the buildd on which it is
built, this can lead to a baseline ABI violation. This is the case for
the package in bookworm for at least amd64 and i386.
[ Impact ]
Users of older hardware are not able to use the library, which affects
GCC when used with graphite optimizations enabled.
[ Tests ]
None
[ Risks ]
The change is trivial, and just removes the -march=haswell or similar in
the GCC invocation. Therefore the risk is minimal.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
The fix is to pass the --without-gcc-arch option to the configure script
to disable the CPU detection.
[ Other info ]
Given the change is trivial, I have already uploaded the package.
--- End Message ---
--- Begin Message ---
Version: 12.5
The upload requested in this bug has been released as part of 12.5.
--- End Message ---
