control: tag -1 +moreinfo
[2018-10-13 13:20] Niko Tyni <nt...@debian.org> > For reference, the output with libgdbm5 1.14.1-6+b1 is > > % gdbm_dump debian/tests/data/jessie.gdbm > # GDBM dump file created by GDBM version 1.14.1. 03/01/2018 on Sat Oct 13 > 13:15:59 201 > 8 > #:version=1.0 > #:file=debian/tests/data/jessie.gdbm > #:uid=1000,user=niko,gid=1000,group=niko,mode=644 > # End of header > #:len=3 > Zm9v > #:len=9 > amVzc2llIE9L > #:count=1 > # End of data I compiled gdbm-1.14.1 from source to check `/usr/lib/libmarc-charset-perl/Table'. For me, exit code is non-zero. I belive that issue is with database, but older versions of gdbm_dump failed to properly report it. In addition, just checked bin:man-db database. It is fine. So I believe problem is not /too/ grave. But I agree, usability issue is at hand: something worked (no matter why), and now it no longer works. Let us debug. How those problematic databases are created?
