On 09/02/2023 23:43, Michele Martone wrote:
On 20230209@17:50, Peter Green wrote:
Package: librsb
Version: 1.3.0.2+dfsg-1
Tags: bookworm, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: [email protected]
Usertags: edos-uninstallable
librsb build-depends on coccinelle which appears to have been removed
on armhf, presumablly because it fails to build with an out of memory
error. This leaves your package in violation of the rc policy.
In general in cases like this there are three possible ways forward,
in roughly descending order of preference.
1. Fix the package you depend on so that it once again builds on
all release architectures.
2. Modify your package to eliminate the build-dependency in question
on architectures where it is not available.
3. Decide it is not reasonable to support your package on armhf and
file a removal request with the ftp team.
I do not know enough about your individual package to say which are
feasible in your particular case.
The coccinelle-based patch was there only for gcc-11, which had a bug
in -O3 and generated buggy code.
So if one is sure to build with a different compiler thant gcc-11,
one can drop the coccinelle patch.
Otherwise one can remedy by using '-O3 -fno-tree-loop-vectorize'
instead of '-O3'.
Is it safe to assume gcc-11 is *not* being used?
It should be safe, but I would suggest adding a
build-dependency on gcc (>= 12) to make sure
the package is not inadvertently built in an out of
date environment.
