• Bug#1105965: Remove mips64el from testing

    From Sebastian Ramacher@21:1/5 to Sebastian Ramacher on Sun May 18 13:00:01 2025
    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: [email protected], [email protected]

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sebastian Ramacher@21:1/5 to Sebastian Ramacher on Sun May 18 15:20:01 2025
    Control: clone -1 -2
    Control: severity -2 normal
    Control: reassign -2 cdimage.debian.org
    Control: retitle -2 cdimage.debian.org: stop building images for mips64el

    On 2025-05-18 12:50:44 +0200, Sebastian Ramacher wrote:
    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: [email protected], [email protected]

    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.

    Also cloning the bug image generation. Please stop builing images for
    mips64el.

    Cheers
    --
    Sebastian Ramacher

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Philipp Kern@21:1/5 to Philipp Kern on Sun May 18 19:50:01 2025
    Hi,

    On 5/18/25 4:14 PM, Philipp Kern wrote:
    On 5/18/25 12:50 PM, Sebastian Ramacher wrote:
    1. is now implemented and deployed. I am cloning the bug for the archive >>> and buildd sides.

    As for wanna-build itself:

    wanna-build=> select * from distribution_architectures where distribution like 'trixie%' and architecture = 'mips64el';
    distribution | architecture | vancouvered | archive
    ------------------+--------------+-------------+-----------------
    trixie | mips64el | f | debian
    trixie-backports | mips64el | f | debian
    trixie-security | mips64el | f | debian-security
    (3 rows)
    wanna-build=> begin;
    BEGIN
    wanna-build=*> delete from packages where distribution like 'trixie%' and architecture = 'mips64el';
    DELETE 37801
    wanna-build=*> delete from distribution_architectures where distribution like 'trixie%' and architecture = 'mips64el';
    DELETE 3
    wanna-build=*> commit;
    COMMIT

    This should stop the triggers from doing any work on those tuples.
    buildds themselves are still missing.

    Removed trixie* from mipsel-osuosl-0{3,4,5}'s config. Did not restart
    buildd as builds were in progress. Could not reach the conova ones.

    Kind regards
    Philipp Kern

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam D. Barratt@21:1/5 to Philipp Kern on Mon May 19 18:40:02 2025
    On Sun, 2025-05-18 at 19:43 +0200, Philipp Kern wrote:
    Removed trixie* from mipsel-osuosl-0{3,4,5}'s config. Did not restart
    buildd as builds were in progress. Could not reach the conova ones.

    I updated setup-all-dchroots in Puppet to stop trying to generate
    mips64el trixie chroots. (They fail to generate, because there are no
    mips64el packages in testing any more.)

    Regards,

    Adam

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)