Control: clone -1 -2 -3
Control: reassign -2 ftp.debian.org
Control: retitle -2 ftp.debian.org: remove mipsel64el from testing
Control: severity -2 normal
Control: reassign -3 buildd.debian.org
Control: retitle -3 buildd.debian.org: stop building mipsel64el for testing
Control: severity -3 normal
Control: block -1 by -2 -3

Let's try this again.

On 2025-05-18 12:41:08 +0200, Sebastian Ramacher wrote:
> Control: clone -1 -2 ftp.debian.org
> Control: retitle -2 ftp.debian.org: remove mipsel64el from testing
> Control: severity -2 normal
> Control: clone -1 -3 buildd.debian.org
> Control: retitle -3 buildd.debian.org: stop building mipsel64el for testing
> Control: severity -3 normal
> Control: block -1 by -2 -3
> 
> On 2025-05-18 10:54:32 +0200, Sebastian Ramacher wrote:
> > Package: release.debian.org
> > Severity: serious
> > X-Debbugs-CC: sramac...@debian.org, debian-m...@lists.debian.org
> > 
> > On 2025-05-18 08:26:30 +0000, Paul Gevers wrote:
> > > mips64el and riscv64
> > > ====================
> > > 
> > > The Release Team has decided to drop mips64el as a release architecture
> > 
> > Let use this bug to coordinate the removal of mips64el from testing. As
> > last time:
> > 
> > 1. Get britney to ignore mips64el
> > 2. Stop building for mips64el/{testing,unstable,experimental}
> > 3. Remove mips64el/{testing,unstable,experimental} from the archive
> > 
> > I am implementing 1. and will later clone this bug to the appropriate
> > teams to implement 2. and 3.
> 
> 1. is now implemented and deployed. I am cloning the bug for the archive
> and buildd sides.
> 
> Cheers
> 
> PS: For the removal from unstable and experimental, it make sense to
> wait for a reply from the mips64el porter whether they want to move it
> to ports or not.
> -- 
> Sebastian Ramacher
> 

-- 
Sebastian Ramacher

Reply via email to