Bug#1103529: xapian-core: libxapian unexpectedly changed soname and package name

2025-05-01 Thread Olly Betts
On Sat, Apr 26, 2025 at 09:20:53PM +0100, Olly Betts wrote: > On Sat, Apr 26, 2025 at 10:10:07AM +0200, Paul Gevers wrote: > > Is debian/control maybe generated during the build? That is not allowed [1]. > > It's generated, but by a `maint` target run before making the source > package. > > Howev

Bug#1103529: xapian-core: libxapian unexpectedly changed soname and package name

2025-04-26 Thread Olly Betts
On Sat, Apr 26, 2025 at 10:10:07AM +0200, Paul Gevers wrote: > On Fri, 18 Apr 2025 20:34:25 +0200 Sven Joachim wrote: > > In the latest upload of xapian-core, libxapian changed its soname from > > 30 to 29 and a new binary package libxapian29 appeared out of nowhere. > > If this were intended, the

Bug#1103529: xapian-core: libxapian unexpectedly changed soname and package name

2025-04-26 Thread Paul Gevers
Hi Sven, On Fri, 18 Apr 2025 20:34:25 +0200 Sven Joachim wrote: In the latest upload of xapian-core, libxapian changed its soname from 30 to 29 and a new binary package libxapian29 appeared out of nowhere. If this were intended, the package would have needed to go threw NEW, but since the packa

Bug#1103529: xapian-core: libxapian unexpectedly changed soname and package name

2025-04-18 Thread Sven Joachim
Source: xapian-core Version: 1.4.28-1 Severity: serious In the latest upload of xapian-core, libxapian changed its soname from 30 to 29 and a new binary package libxapian29 appeared out of nowhere. If this were intended, the package would have needed to go threw NEW, but since the package is not l