GNU bug report logs - #33499
file-5.33 doesn't detect berkeley-db files correctly

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Julien Lepiller <julien <at> lepiller.eu>
Subject: bug#33499: closed (Re: bug#33499: file-5.33 doesn't detect
 berkeley-db files correctly)
Date: Thu, 05 Aug 2021 03:38:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#33499: file-5.33 doesn't detect berkeley-db files correctly

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 33499 <at> debbugs.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)]

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Julien Lepiller <julien <at> lepiller.eu>
Cc: 33499-done <at> debbugs.gnu.org
Subject: Re: bug#33499: file-5.33 doesn't detect berkeley-db files correctly
Date: Wed, 04 Aug 2021 23:37:42 -0400

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

[Message part 3 (message/rfc822, inline)]

From: Julien Lepiller <julien <at> lepiller.eu>
To: bug-guix <at> gnu.org
Subject: file-5.33 doesn't detect berkeley-db files correctly
Date: Sun, 25 Nov 2018 13:10:48 +0100

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.