GNU bug report logs -
#33499
file-5.33 doesn't detect berkeley-db files correctly
Previous Next
Reported by: Julien Lepiller <julien <at> lepiller.eu>
Date: Sun, 25 Nov 2018 12:12:01 UTC
Severity: normal
Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Wed, 04 Aug 2021 23:37:42 -0400
with message-id <87czqsmuih.fsf <at> gmail.com>
and subject line Re: bug#33499: file-5.33 doesn't detect berkeley-db files correctly
has caused the debbugs.gnu.org bug report #33499,
regarding file-5.33 doesn't detect berkeley-db files correctly
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
33499: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=33499
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Hi,
our file on core-updates (soon to be master), fails to detect
berkeley-db files correctly. I've sent a bug report upstream about this
issue here: https://bugs.astron.com/view.php?id=54
This issue seems to be only present on file-5.33, and is solved in more
recent versions. I haven't fixed the issue on core-updates because it's
a rebuild-the-world change, and I don't think we can push those anymore
at this stage in core-updates.
This issue affects diffoscope, where a test fails because it doesn't
detect the correct file type. You can reproduce the issue with:
file /path/to/diffoscope/source/tests/data/test1.db
which returns `, created: Thu Jan 1 00:38:24 1970` instead of `Berkeley
DB (Btree, version 9, native byte-order)`.
For now, I've disabled the test in diffoscope, so we can build it.
Other packages might be affected by this bug.
[Message part 3 (message/rfc822, inline)]
Julien Lepiller <julien <at> lepiller.eu> writes:
> Hi,
>
> our file on core-updates (soon to be master), fails to detect
> berkeley-db files correctly. I've sent a bug report upstream about this
> issue here: https://bugs.astron.com/view.php?id=54
>
> This issue seems to be only present on file-5.33, and is solved in more
> recent versions. I haven't fixed the issue on core-updates because it's
> a rebuild-the-world change, and I don't think we can push those anymore
> at this stage in core-updates.
We now have 5.38 on master. Closing.
Thanks,
Maxim
This bug report was last modified 3 years and 350 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.