• Bug#1105965: Remove mips64el from testing

    From Sebastian Ramacher@21:1/5 to Paul Gevers on Sun May 18 11:00:02 2025
    XPost: linux.debian.ports.mips, linux.debian.devel.release

    Package: release.debian.org
    Severity: serious
    X-Debbugs-CC: sramacher@debian.org, debian-mips@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.

    Cheers
    --
    Sebastian Ramacher

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Gevers@21:1/5 to All on Sun May 18 11:20:01 2025
    XPost: linux.debian.devel.release
    To: helmut@subdivi.de (Helmut Grohne)

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------Mmm0pnTlZrL5LVWACol0zeSU
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    SGkgYWxsLCBIZWxtdXQsDQoNCk9uIDE4LTA1LTIwMjUgMTA6NTQsIFNlYmFzdGlhbiBSYW1h Y2hlciB3cm90ZToNCj4gTGV0IHVzZSB0aGlzIGJ1ZyB0byBjb29yZGluYXRlIHRoZSByZW1v dmFsIG9mIG1pcHM2NGVsIGZyb20gdGVzdGluZy4gQXMNCj4gbGFzdCB0aW1lOg0KPiANCj4g MS4gR2V0IGJyaXRuZXkgdG8gaWdub3JlIG1pcHM2NGVsDQo+IDIuIFN0b3AgYnVpbGRpbmcg Zm9yIG1pcHM2NGVsL3t0ZXN0aW5nLHVuc3RhYmxlLGV4cGVyaW1lbnRhbH0NCj4gMy4gUmVt b3ZlIG1pcHM2NGVsL3t0ZXN0aW5nLHVuc3RhYmxlLGV4cGVyaW1lbnRhbH0gZnJvbSB0aGUg YXJjaGl2ZQ0KPiANCj4gSSBhbSBpbXBsZW1lbnRpbmcgMS4gYW5kIHdpbGwgbGF0ZXIgY2xv bmUgdGhpcyBidWcgdG8gdGhlIGFwcHJvcHJpYXRlDQo+IHRlYW1zIHRvIGltcGxlbWVudCAy LiBhbmQgMy4NCg0KDQpIZWxtdXQgdHJpZWQgdG8gZXhwbGFpbiB0byBtZSBpbiBIYW1idXJn IHdoeSANCnNyYzpjcm9zcy10b29sY2hhaW4tYmFzZS1taXBzZW4gaXMgaW4gdGhlIGtleSBw YWNrYWdlIHNldC4gSSBtdXN0IGFkbWl0IA0KSSBkaWRuJ3QgdW5kZXJzdGFuZCwgYnV0IHRo ZXJlJ3Mgc29tZXRoaW5nIHdpdGggcWVtdSBJSVJDLiBJdCBtaWdodCB0YWtlIA0KYSBiaXQg b2Ygd29yayB0byBmaXggdGhhdC4gSG9wZWZ1bGx5IHlvdSAoSGVsbXV0KSBhcmUgd2lsbGlu ZyB0byB0cnkgDQphZ2FpbiB0byBleHBsYWluIHRoZSBzaXR1YXRpb24/DQoNClBhdWwNCg0K


    --------------Mmm0pnTlZrL5LVWACol0zeSU--

    -----BEGIN PGP SIGNATURE-----

    wsC7BAABCABvBYJoKaQpCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u cy5zZXF1b2lhLXBncC5vcmeZYaOUQxkRRbYhf4b21/IQrrledV4x1bFRue7WcYOv vBYhBFi2bUhza+k7BS3mcpxcmesFvXUKAABuVwgAodNV2uHa8pjiRShLUVX+Bp2z jcyk5mkhDB/dYpmfza28RI8d1y4RtOcOTb6hKJ1DbJsOWKlP9f31tIIs4vIBtDSs UVJMuacp6VpZe2IndEX6QuQN48q1j4MK/S+eR1sTlZmM5ifeHYjP4MUgG2AIGY4b cbO0V0RYaREXbQrQf4gm2xT5E2qaGBZ9s8xngl2h5M2YpBK9Lj/jvn5a5uAjeP3k d4rwKsf5umpIQRovDOnghW6fd/PrABhBQHPuIMYY2N/8GyzHJdxm8ccDW1tULlOU 8TcPbVZGACgLrFknPfqLfd2zJS6Yo0atPq2VgW+WSQ9SoM9XlPR5AvKqRiGlOw==
    =3t0r
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sebastian Ramacher@21:1/5 to Sebastian Ramacher on Sun May 18 12:50:01 2025
    XPost: linux.debian.devel.release

    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: sramacher@debian.org, debian-mips@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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Philipp Kern@21:1/5 to Sebastian Ramacher on Sun May 18 16:20:01 2025
    XPost: linux.debian.devel.release

    Hi,

    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.

    Kind regards
    Philipp Kern

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