Control: retitle -1 release.debian.org: status of mips64el for trixie
(Retitling because as far as I know, there is no longer a concern about
librsvg specifically)
On Fri, 11 Apr 2025 at 20:37:44 +0200, Sebastian Ramacher wrote:
On 2025-01-27 20:32:20 +0100, Emilio Pozuelo Monfort wrote:
On 23/01/2025 15:32, Simon McVittie wrote:
> The current version of librsvg is not migrating to testing because it
> FTBFS on mips64el. This appears to be caused by a kernel or hardware
> issue where otherwise-working code fails with EFAULT in a read() call
> on bookworm kernels (see #1093200): this is not librsvg-specific, and
> affects other Rust components, as well as git, Erlang and Go.
This particular issue is believed to have been fixed in bookworm since
6.1.129-1 ("mm/memory: Use exception ip to search exception tables")
thanks to work done by Sergei Golovan (not a mips64el porter) and Salvatore
Bonaccorso (not a mips64el porter as far as I know).
We are having serious concerns regarding the state of mips64el for
trixie. Beside this bug report (#1050872), other teams have raised
concerns as well.
While that specific bug did eventually get fixed, it seems concerning
that it had to be maintainers of affected packages who raised the alarm
about this, rather than the porting team noticing that there was a more
general problem. It also seems concerning that #1093200 was eventually
fixed by a maintainer of a different affected package rather than by the
mips64el porting team - it doesn't seem healthy for ports to be kept
alive by individual heroics from someone who doesn't even have the
relevant hardware.
smcv
