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

Previous Next

Package: guix;

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.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 33499 in the body.
You can then email your comments to 33499 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#33499; Package guix. (Sun, 25 Nov 2018 12:12:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Julien Lepiller <julien <at> lepiller.eu>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Sun, 25 Nov 2018 12:12:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

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.




Reply sent to Maxim Cournoyer <maxim.cournoyer <at> gmail.com>:
You have taken responsibility. (Thu, 05 Aug 2021 03:38:02 GMT) Full text and rfc822 format available.

Notification sent to Julien Lepiller <julien <at> lepiller.eu>:
bug acknowledged by developer. (Thu, 05 Aug 2021 03:38:02 GMT) Full text and rfc822 format available.

Message #10 received at 33499-done <at> debbugs.gnu.org (full text, mbox):

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




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Thu, 02 Sep 2021 11:24:08 GMT) Full text and rfc822 format available.

This bug report was last modified 2 years and 230 days ago.

Previous Next


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