Your message dated Sun, 2 Nov 2025 14:56:55 +0100
with message-id <[email protected]>
and subject line mips64el/armel have been removed from wanna-build
has caused the Debian Bug report #1113680,
regarding buildd.debian.org: stop building armel on forky and unstable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1113680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1113680
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: wishlist
X-Debbugs-Cc: [email protected]
User: [email protected]
Usertags: armel
The release notes for trixie announced that it would be the last release
for armel.
Now that forky is open, would it be possible to start removing armel
from the lists of architectures that "matter"? For example, this could
allow packages whose buildability regresses on armel (usually due to
lack of atomic ops) to migrate to testing, without needing ftp team
intervention to clean up their old binaries.
In my case this request was prompted by looking at src:dxvk, which was
buildable on armel in trixie but has regressed in experimental
("undefined reference to `__atomic_fetch_sub_8'"), and at this stage of
armel's life cycle it doesn't seem useful to spend time on fixing that.
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Hi,
We stopped ingesting mips64el and armel for forky, sid, and experimental
into wanna-build now and removed them from the buildds. This should
resolve these bugs.
Kind regards and thanks
Philipp Kern
--- End Message ---
