[2019-03-05 17:44] Sergey Poznyakoff <g...@gnu.org.ua>
> Hello,
>
> Investigation of the attached file has shown that it has been created
> by gdbm 1.8.3 compiled without large file support (sizeof(off_t) == 4).
> In contrast, gdbm 1.18.1 was compiled with large file support enabled,
> which naturally lead to the observed behavior. Recompile it with the
> --disable-largefile flag and it will be able to read the file.
Thank you, Sergey. Does incompatibility goes other way too, that version
without LFS support is incapable of reading file, created with LFS
version?
I consider providing statically-linked, LFS-disabled version of
gdbm_{load,dump,tool}, so user with database, created on stretch could
do `gdbm_dump old.gdbm | gdbm_load new.gdbm'. Opinions?
Oh, we may need to ask release team, for we are too close to hard-freeze.
--
Note, that I send and fetch email in batch, once every 24 hours.
If matter is urgent, try https://t.me/kaction
--
