[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#994091: marked as done (nmu: aide_0.17.3-4)

Your message dated Mon, 13 Sep 2021 08:12:13 +0200
with message-id <YT7rvfS+n5EWQROU@ramacher.at>
and subject line Re: Bug#994091: nmu: aide_0.17.3-4
has caused the Debian Bug report #994091,
regarding nmu: aide_0.17.3-4
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.)


-- 
994091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994091
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

[this is my first binNMU request, I hope that I did everything right]

aide is statically linked. With the new glibc, NSS calls get somehow
still some dynamic linking, which causes a reproducible and
unconditional segfault one aide uses an NSS-releated call. A rebuild
fixes this issue. I am currently discussing this issue with upstream to
find out whether we can do things a bit better in the future.

Greetings
Marc


nmu aide_0.17.3-4 . ANY . unstable . -m "Rebuild against the new glibc"

--- End Message ---
--- Begin Message --- 
On 2021-09-12 00:11:36 +0200, Aurelien Jarno wrote:
> On 2021-09-11 21:52, Adrian Bunk wrote:
> > On Sat, Sep 11, 2021 at 03:59:12PM +0200, Marc Haber wrote:
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian.org@packages.debian.org
> > > Usertags: binnmu
> > > 
> > > [this is my first binNMU request, I hope that I did everything right]
> > 
> > [ I am not a member of the release team ]
> > 
> > > aide is statically linked. With the new glibc, NSS calls get somehow
> > > still some dynamic linking, which causes a reproducible and
> > > unconditional segfault one aide uses an NSS-releated call. A rebuild
> > > fixes this issue. I am currently discussing this issue with upstream to
> > > find out whether we can do things a bit better in the future.
> > 
> > AFAIR static glibc linking and NSS is known problematic.
> 
> Indeed, I confirm. Note that this will change with glibc 2.34 which has
> nss_files and nss_dns built-in.
> 
> > The dependencies should ensure that apt/dpkg only install a working set 
> > of packages. Dependencies like "libc6 (>> 2.32), libc6 (<< 2.33)" might
> > help, but I've added debian-glibc to Cc since I don't know for sure
> > whether this would be sufficient.
> 
> This is correct, there is no breakage between minor version, only
> between major version. Now, given that bookworm will very likely have
> glibc >= 2.34 (at least that the goal if we are able to solve all issues
> with each new upstream version), so I am not sure if it is worth
> implementing such a change.

ACK, but in case that glibc >= 2.34 doesn't happen for bookworm, this
should be implemented. For now, it would probably make sense for libc6
to have a Breaks on aide (<< 0.17.3-4+b3).

binNMUs scheduled.

Cheers

> 
> Regards,
> Aurelien
> 
> -- 
> Aurelien Jarno                          GPG: 4096R/1DDD8C9B
> aurelien@aurel32.net                 http://www.aurel32.net
> 

-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: