Your message dated Mon, 4 Oct 2021 11:24:50 +0200
with message-id <YVrIYg9DW5/8k...@ramacher.at>
and subject line Re: Bug#995072: nmu: tripwire_2.4.3.7-3
has caused the Debian Bug report #995072,
regarding nmu: tripwire_2.4.3.7-3
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.)
--
995072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: 994...@bugs.debian.org
tripwire now segfaults when it tries to read information about a file.
Rebuilding the package from source makes the problem go away. The
problem appeared to start after the libc6 update to 2.32.
I suspect this is because tripwire is statically linked, and there are
known issues with static linking with libc6 across version releases
because the internal API to nsswitch modules changes. This is
consistent with the pattern of segfaults, since it appears to happen
around the point where tripwire would try to resolve a numeric UID or
GID to a name. If this is correct, a binNMU against the latest libc6
should fix the problem.
I have tested this by rebuilding the source package with no changes
in a sid chroot and confirmed the resulting package works correctly.
nmu tripwire_2.4.3.7-3 . ANY . unstable . -m "Rebuild with libc6 2.32"
--- End Message ---
--- Begin Message ---
On 2021-09-25 10:33:04, Russ Allbery wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian....@packages.debian.org
> Usertags: binnmu
> X-Debbugs-Cc: 994...@bugs.debian.org
>
> tripwire now segfaults when it tries to read information about a file.
> Rebuilding the package from source makes the problem go away. The
> problem appeared to start after the libc6 update to 2.32.
>
> I suspect this is because tripwire is statically linked, and there are
> known issues with static linking with libc6 across version releases
> because the internal API to nsswitch modules changes. This is
> consistent with the pattern of segfaults, since it appears to happen
> around the point where tripwire would try to resolve a numeric UID or
> GID to a name. If this is correct, a binNMU against the latest libc6
> should fix the problem.
>
> I have tested this by rebuilding the source package with no changes
> in a sid chroot and confirmed the resulting package works correctly.
>
> nmu tripwire_2.4.3.7-3 . ANY . unstable . -m "Rebuild with libc6 2.32"
Scheduled. We really need a better way to track packages that statically
link glibc.
Cheers
--
Sebastian Ramacher
--- End Message ---
