From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Profile 23.0 testing with stages and binhost (part 1 of 2)
Date: Wed, 21 Feb 2024 00:56:30 +0100 [thread overview]
Message-ID: <1880766.CQOukoFCf9@pinacolada> (raw)
[-- Attachment #1: Type: text/plain, Size: 2197 bytes --]
Hi all,
for the following arches (and only these)
** GLIBC:
** alpha, arm, ia64, loong, m68k, ppc, ppc64, riscv, s390, sparc, x86
** MUSL:
** riscv
the 23.0 profiles are ready for testing, including stage downloads,
binary packages, and update instructions for existing installations.
IMPORTANT Draft update instructions IMPORTANT
https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_update_instructions
Stage downloads (temporarily, for all listed arches):
[preferably] https://distfiles.gentoo.org/experimental/x86/23.0_stages/
[direct/osu] https://gentoo.osuosl.org/experimental/x86/23.0_stages/
The changes can be seen here
https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_transition
and the timeline so far here
https://wiki.gentoo.org/wiki/Project:Toolchain/23.0_profile_timeline
Please try things out, and file bugs if you encounter problems.
In particular, also double-check the documentation - the update
path table was a lot of manual work, and it's not impossible that
C-C / C-V went wrong somwhere.
The update instructions also double as the news item that should be
published 2 weeks from now on these arches (unless there are
unexpected problems). I'll reply to this e-mail with a separate
mail containing the full text, for easier discussion.
Note 1: The next steps are, in 2 weeks:
* make 23.0 profiles the same stability level as 17.x profiles,
* degrade 17.x profiles all to exp (so the CI doesn't explode)
* publish news item
* replace stage downloads with 23.0 version (in situ)
Note 2: Musl is still missing out on *stable* arches, since this
requires musl-1.2.4 stable.
Note 3: The remaining arches follow when they are ready.
Why are they not ready?
* amd64: comes last :)
* arm64: bug #916381 still needs to be implemented
* hppa: slow hardware (one gcc build takes ~1 week)
* mips: slow qemu emulation (one gcc build takes ~1 day),
many variants and complex profile structure
* musl on stable arches: needs musl-1.2.4 stable
Cheers & have fun,
Andreas
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next reply other threads:[~2024-02-20 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 23:56 Andreas K. Huettel [this message]
2024-02-20 23:58 ` [gentoo-dev] Profile 23.0 news item (was: Re: Profile 23.0 testing with stages and binhost (part 1 of 2)) Andreas K. Huettel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1880766.CQOukoFCf9@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox