On Sat, Apr 26, 2025 at 10:10:07AM +0200, Paul Gevers wrote:

On Fri, 18 Apr 2025 20:34:25 +0200 Sven Joachim <svenjoac@gmx.de> 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 package is not listed in debian/control it bypassed any sanity checks.

Can you elaborate? This sounds like a bug in dak as I would expect it to reject uploads with binaries that are not listed in debian/control.

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.

However I see there is also a dependency on debian/control from override_dh_auto_configure. Looking at the .dsc it looks like I forgot
to run `debian/rules maint` for 1.4.28-1 so debian/control may have been regenerated during the build.

The equivalent of this dependency has been there since the start of git
history over 20 years ago, before I took over as maintainer, but it is
clearly a bad idea. I'll remove it.

Cheers,
Olly

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)