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.
Cheers, Julien