Re: Paul Gevers 2018-07-29 <fec99c86-6963-b1b0-6984-34e49d8df...@debian.org> > Looking at the error log, the changelog and your updated lintian > override, it seems that this library requires all reverse dependencies > to be rebuild. But because you don't follow traditional Debian library > practices of doing transitions, the Debian archive doesn't know this. > Luckily the sqlsmith autopkgtest caught this.
Looking at debian/libpqxx6.symbols, I notice the first line is libpqxx-4.0.so libpqxx-4.0v5 #MINVER# which implies you aren't tracking symbols at all for the more recent .so files. dpkg-gensymbols throws warnings about that at build time, please don't ignore these. dpkg-gensymbols: warning: new libraries appeared in the symbols file: libpqxx-6.2.so dpkg-gensymbols: warning: some libraries disappeared in the symbols file: libpqxx-4.0.so dpkg-gensymbols: warning: debian/libpqxx6/DEBIAN/symbols doesn't match completely debian/libpqxx6.symbols --- debian/libpqxx6.symbols (libpqxx6_6.1_amd64) +++ dpkg-gensymbolsCgj2o9 2018-07-29 12:52:58.522401056 +0000 @@ -1,867 +1,654 @@ $ cat debian/libpqxx6.lintian-overrides ## I see no need for creating new bianry package each time minor version is ## updated and prefer not to see this warning libpqxx6 binary: package-name-doesnt-match-sonames libpqxx-6.2 This might be ok if there's no actual breakage between versions. In that case, you need to provide compat symlinks to the .so file (or better change SONAME to libpqxx6.so), but without symbol tracking, we don't know. Christoph
signature.asc
Description: PGP signature
