On Mon, Apr 26, 2021 at 11:01:45PM +0200, Aurelien Jarno wrote:
Source: e2fsprogs
Version: 1.46.2-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://github.com/tytso/e2fsprogs/issues/65
e2fsprogs builds fine on armel/armhf when built on a machine with a
32-bit kernel. However it fails to build on a machine with a 64-bit
kernel due to alignments issues which are not trapped by the kernel:
A build log is available there:
https://tests.reproducible-builds.org/debian/logs/unstable/armhf/e2fsprogs_1.46.2-1.build2.log.gz
Hi, thanks for the bug report. I have a patch which should address
this problem. (See below).
I have a question for the Debian Release Team (cc'ed). Do you agree
this is considered "serious"? It will build from source on a system
with a arm-32 kernel. It is only when cross-compiling on armel or
armhf on a aarch64 platform that some regression tests
(j_recover_csum2_32bit, j_recover_csum2_64bit, and j_recover_fast_commit)
will fail, and it is this which causes dpkg-buildpackage when run on a
arm-32 chroot on a 64-bit arm system to fail.
So it is not completely clear to me that this qualifies as a FTBFS,
such that the release team would grant an migration into bullseye
given that we are currently in "frozen hard to get hot"[1]
[1] https://lists.debian.org/debian-devel-announce/2021/03/msg00006.html