On Mon, Oct 15, 2018 at 12:21:16AM +0000, Dmitry Bogatov wrote: > I am sorry to say it, but probably binNMU or sourceful upload would be > required for all packages, that bundle gdbm databases, generated by > (gdbm << 1.9)
It looks like the incompatibility goes the other way too: the stretch gdbm (1.8) can't read the new databases in my tests. So to properly support partial upgrades on the Perl side I think we need to - update perl to build-depend on libgdbm-dev (>= 1.18-2) and Break older versions of libmarc-charset-perl (and any other perl packages bundling GDBM or NDBM databases) - update libmarc-charset-perl (and any other perl packages bundling GDBM or NDBM databases) to build-depend and depend on the newer perl I assume other language bindings like python-gdbm will need something similar. As the command-not-found database lives in /var/cache, it will probably need some maintscript logic to remove the incompatible version and regenerate it. Local databases on user systems still need a solution. -- Niko Tyni nt...@debian.org