mips64el in trixie: [was: Bug#1093200: Some packages consistently FTBFS with EFAULT (Bad address) on most mips64el buildds]
Paul Gevers <[email protected]> Sun, 16 Feb 2025 21:14:24 +0100
| Newsgroups | gmane.linux.debian.devel.kernel,gmane.linux.debian.ports.mips |
|---|---|
| Message-ID | <[email protected]> |
Dear mips64el porters, This is a warning from a Release Team member regarding the state of mips64el in Debian. Unless Sergei considers himself a mips64el porter, I haven't seen activity of the mips64el porters on bug 1093200 and similar bugs where the porters were asked for help and thus cc-ed. Because of the seriousness of the problem, that's a very bad sign for the port. I also like to hear your view on the topic of the Debian hosts, like it was raised in bug 1050872. I understand that there are difficulties upgrading existing hardware to bookworm (and later) kernels. Some hosts apparently are currently not upgradable. I also heard that newer hardware is incompatible with the ABI used in Debian. How do you see a future for mips64el in Debian? Paul
OpenPGP_signature.asc
(application/pgp-signature, 495 B)
-----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmeyRyAFAwAAAAAACgkQnFyZ6wW9dQrM rwgApp2sd8jHVXaX4Z7DlXAHXDRyTVBs0ZiHKdkFd5J0PL7hlbrHrw6bMNrA8Rp556O+3dWCRZ0b L4pBJ++H3iV4E7F5fn84xGKqpWwwNglRaqrxd7zaGhe5GQAtrtO1Plqrp3TrBM8cX8W7dqZ4CpDH qA9BGyClMDKXlEEtDpk81W8Q1k+eeJ9pFftHVFsRwXgBwEHXqdEWL/7qeWLDTkZKdrDLFpnCsWsl eeXch8QJLONZMoVxJMnl2YJ+AuTYXejBISFTVPTdBsUkrMMEEL8WqXAi1tznALA+bHOYhXtJQZ7z 3DWT65VaZby/qmvOPhlhJOkzHxZWBrMvwx7SUMXnEQ== =Vxt8 -----END PGP SIGNATURE-----