sys-apps/file stopped to properly identify Berkeley DB files and produces broken output now, instead: $ base64 -d <<<'/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4C//AGddAABofp4g8deXsY+Yc/lSGqNM4rx3IcR+Hk9KWncQzdbUOf0E/1npFIxr7GkR3l5YQ5iqLMngItVRoSuhdetM9kxri/uo1zjKqghMYA7QrsTnXc05QOBkCzt+WFYDwOCtpLbhwSbEsgAAAKRC6IHNDzanAAGDAYBgAAAA5p/DscRn+wIAAAAABFla' | xz -d > Packages $ sha256sum Packages 3adf543a3c76f2a943c56e417ad0631e99eb126bc8d4d4953b627482e9250315 Packages $ file Packages # Debian, 5.33, all good Packages: Berkeley DB (Hash, version 9, native byte-order) $ file Packages # Gentoo, 5.33-r{0,3}, broken Packages: , created: Thu Jan 1 00:34:08 1970 Could it be one of our patches or are we missing a patch more? It did work in the past.
Yeah, Debian has https://sources.debian.org/patches/file/1:5.33-3/upstream.disable-erroneous-dbpf.patch/ to address the issue. Upstream fix is https://github.com/file/file/commit/4fb6a59df80d4974f8230bfce36e38e6de7d574f.
Nice! I can confirm that that patch fixes the issue. Since this is base-system: Any objections to adding the patch to -r4 myself?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6d0b89f14127625f091fe9edbec9ca41ac1accd2 commit 6d0b89f14127625f091fe9edbec9ca41ac1accd2 Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2018-07-24 08:55:05 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2018-07-24 08:58:02 +0000 sys-apps/file: Revbump to fix berkdb file magic Bumped straight to stable Closes: https://bugs.gentoo.org/661922 Package-Manager: Portage-2.3.43, Repoman-2.3.10 .../{file-5.33-r3.ebuild => file-5.33-r4.ebuild} | 5 ++-- .../file/files/file-5.33-berkdb_bogus_magic.patch | 33 ++++++++++++++++++++++ 2 files changed, 36 insertions(+), 2 deletions(-)
