Hi Benjamin, Andreas Tille, on 2025-03-15: > Am Thu, Mar 13, 2025 at 12:19:47PM -0400 schrieb Benjamin Redelings: > > It looks like the bali-phy v4.0 packages are not migrating to testing > > because the armel and armhf builds are failing. It looks like there is a > > segfault somewhere. I think these are 32-bit ARM instances, so it looks > > like the code works on 64-bit ARM, but not 32-bit. > > You might rather like to answer the question whether you consider it > worth porting it to 32bit arm. Otherwise we tend to exclude those > hardware if they create trouble in whatever way. I took the liberty to open #1101890 to request removal of the package for arm 32-bit architectures. Newer reportbug versions include some logic to add relevant porters in the loop, in case package removal requests are architecture specific. This is pretty new to me and am not sure how this will work, but it may happen that you will get help from arm porters if they deem preferable to fix the build failure rather than letting ftpmaser proceed to package removal. As explained in the bug, given the current timing and the fact that the operation is reversible, I expressed preference for a package removal, but don't hesitate to ping the bug if you do wish some help with the porting effort instead, or in addition, of removal from 32-bit arm. Thanks for your work this far on bali-phy development and its packaging! I hope it will make it to upcoming Debian trixie! Have a nice day, :) -- .''`. Étienne Mollier <emollier@debian.org> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/2, please excuse my verbosity `- on air: Genesis - Dancing with the Moonlit Knight
Attachment:
signature.asc
Description: PGP signature