Hi, On 2025-09-01 07:49, Sebastian Ramacher wrote: > Control: clone -1 -2 -3 > Control: reassign -2 ftp.debian.org > Control: retitle -2 ftp.debian.org: remove armel from forky and unstable > Control: reassign -3 buildd.debian.org > Control: retitle -3 buildd.debian.org: stop building armel on forky and > unstable > > On 2025-08-22 13:25:33 +0200, Sebastian Ramacher wrote: > > On 2025-08-13 17:40:26 +0200, Paul Gevers wrote: > > > Hi, > > > > > > On 13-08-2025 16:28, Simon McVittie wrote: > > > > Now that forky is open, would it be possible to start removing armel > > > > from the lists of architectures that "matter"? > > > > > > > > > We're intending to remove armel from testing soon. I seem to recall there > > > was a reason why we might want to keep it longer during the cycle, but I > > > can't recollect the reason and I can't seem to find it in my inbox (might > > > have been on IRC or IRL. If nobody can reproduce the reason, we'll > > > probably > > > act within a couple of days/weeks. It already came up on IRC this week. > > > > I intend to merge > > https://salsa.debian.org/release-team/britney2/-/tree/armel-removal by > > the end of August and will then ask FTP to remove armel from forky. > > This is now done. Cloning and reassigning to also remove armel from > forky and stop building packages for it. Unless there are any plans by > the armel porters to move armel to ports, please do the same for > unstable.
This is now done on the wanna-build side for forky. For unstable, similarly to mips64el, let's wait for at least for an ack from the ftp masters side. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B [email protected] http://aurel32.net
