On Mon, Oct 15, 2018 at 12:21:16AM +0000, Dmitry Bogatov wrote: > > [2018-10-13 13:20] Niko Tyni <nt...@debian.org> > > The libgdbm6 transition broke autopkgtest checks of src:perl and > > libmarc-charset-perl. > > > > It looks like some GDBM databases which were working with the older > > gdbm are not readable any more with the new one. > > After a bit more research I deduced, that libmarc-charset-perl, as > present in sid, was build with gdbm-1.8.3. gdbm-1.9 is incompatible with > 1.8.3, so it is pure luck, that thigs worked with gdbm-1.14. > > 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)
This sounds really sad. So even the gdbm we have in our current stable release is too old to be supported anymore! Any packaged databases are easily rebuilt, but what about local user databases? I think breaking compat with those is horrible, and I don't even see a way to recover their contents after they've upgraded gdbm. $ gdbmtool stretch.gdbm recover gdbmtool: argv:1.1-8: cannot open database stretch.gdbm: Malformed database file header -- Niko Tyni nt...@debian.org
