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

Bug#942217: marked as done (nmu: libapache2-mod-security2_2.9.3-1)

Your message dated Sat, 10 Sep 2022 19:49:53 +0100
with message-id <ea10923c91011658f9871a7178eb25f48fd7927c.camel@adam-barratt.org.uk>
and subject line Re: Bug#942217: nmu: libapache2-mod-security2_2.9.3-1
has caused the Debian Bug report #942217,
regarding nmu: libapache2-mod-security2_2.9.3-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 owner@bugs.debian.org
immediately.)


-- 
942217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942217
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

nmu libapache2-mod-security2_2.9.3-1 . amd64 . buster . -m "Build with libapr-1.6.5"

Looks like my build environment wasn't up to date when I built this.
The amd64 package is linked with an older version of libapr1 than the
one in Buster.
Sorry for the mess.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On Tue, 2019-10-15 at 13:48 +0200, Julien Cristau wrote:
> On Tue, Oct 15, 2019 at 13:15:22 +0200, Alberto Gonzalez Iniesta
> wrote:
> 
> > On Sat, Oct 12, 2019 at 05:01:38PM +0200, Alberto Gonzalez Iniesta
> > wrote:
> > > On Sat, Oct 12, 2019 at 03:57:14PM +0100, Adam D. Barratt wrote:
> > > > Control: tags -1 + moreinfo
> > > > 
> > > > On Sat, 2019-10-12 at 15:16 +0200, Alberto Gonzalez Iniesta
> > > > wrote:
> > > > > nmu libapache2-mod-security2_2.9.3-1 . amd64 . buster . -m
> > > > > "Build
> > > > > with libapr-1.6.5"
> > > > > 
> > > > > Looks like my build environment wasn't up to date when I
> > > > > built this.
> > > > > The amd64 package is linked with an older version of libapr1
> > > > > than the
> > > > > one in Buster.
> > > > > Sorry for the mess.
> > > > 
> > > > What practical issues does this cause?
> > > > 
> > > 
> > > It's probably just a warning, reported here:
> > > https://github.com/SpiderLabs/ModSecurity/issues/2139
> > > 
> > 
> > Upstream commented on the issue:
> > https://github.com/SpiderLabs/ModSecurity/issues/2139#issuecomment-541590904
> > 
> That doesn't make sense.  Shared library ABI changes are handled by
> shlibs/symbols updates when compatible, and SONAME bumps when
> incompatible.  Version checks beyond that are actively harmful.
> 

This apparently never went any further.

As the final point release for buster has now happened, I'm going to
close this bug.

Regards,

Adam

--- End Message ---
Reply to: