Your message dated Thu, 20 Mar 2025 23:04:52 +0100
with message-id <z9yrbpl22jbsx...@ramacher.at>
and subject line Re: Bug#1100954: unblock: glibc/2.41-6
has caused the Debian Bug report #1100954,
regarding unblock: glibc/2.41-6
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.)
--
1100954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: gl...@packages.debian.org
Control: affects -1 + src:glibc
User: release.debian....@packages.debian.org
Usertags: unblock
Dear release team,
glibc 2.41-6 is currently blocked from migrating to testing due to a
regression in the libinsane autopkgtest. After a long investigation (see
bug#1100805) it is actually a valgrind false positive specific to armhf.
Given the bad state of valgrind, especially on armhf following the
OpenMPI removal on 32-bit architecture, I don't expect a quick fix on
that side. Instead bug#1100939 asks to disable valgrind in libinsane
autopkgtest on armhf.
In the meantime, could you please allow glibc to migrate anyway? It is
basically ready besides that.
Regards
Aurelien
--- End Message ---
--- Begin Message ---
On 2025-03-20 22:55:20 +0100, Aurelien Jarno wrote:
> Package: release.debian.org
> Severity: normal
> X-Debbugs-Cc: gl...@packages.debian.org
> Control: affects -1 + src:glibc
> User: release.debian....@packages.debian.org
> Usertags: unblock
>
> Dear release team,
>
> glibc 2.41-6 is currently blocked from migrating to testing due to a
> regression in the libinsane autopkgtest. After a long investigation (see
> bug#1100805) it is actually a valgrind false positive specific to armhf.
>
> Given the bad state of valgrind, especially on armhf following the
> OpenMPI removal on 32-bit architecture, I don't expect a quick fix on
> that side. Instead bug#1100939 asks to disable valgrind in libinsane
> autopkgtest on armhf.
>
> In the meantime, could you please allow glibc to migrate anyway? It is
> basically ready besides that.
Thanks for providing an analysis of the libinsane autopkgtest
regression. Hint added.
Cheers
--
Sebastian Ramacher
--- End Message ---
