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 listed in debian/control it bypassed any sanity checks.
Please investigate why the soname suddenly went backwards, and make sure that a binary build does not build packages which are not listed in debian/control.
