From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: keywording/maintenance/, keywording/
Date: Mon, 15 Sep 2025 08:43:03 +0000 (UTC) [thread overview]
Message-ID: <1757925739.6c3308be9ca79098e8653b3602b5832520e82a8d.ulm@gentoo> (raw)
commit: 6c3308be9ca79098e8653b3602b5832520e82a8d
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 6 07:31:08 2025 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Sep 15 08:42:19 2025 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=6c3308be
keywording/maintenance: add section for destabilizing an arch
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/maintenance/text.xml | 54 +++++++++++++++++++++++++++++++++++++++++
keywording/text.xml | 1 +
2 files changed, 55 insertions(+)
diff --git a/keywording/maintenance/text.xml b/keywording/maintenance/text.xml
new file mode 100644
index 0000000..228f070
--- /dev/null
+++ b/keywording/maintenance/text.xml
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<devbook self="keywording/maintenance/">
+<chapter>
+<title>Arch and profile maintenance</title>
+
+<section>
+<title>Moving an arch from arch to ~arch</title>
+<body>
+
+<p>
+When demoting an entire architecture from stable (<c>arch</c>) to testing
+(<c>~arch</c>), perform the following:
+</p>
+
+<ol>
+ <li>
+ Prepare and publish a Gentoo news item announcing the architecture
+ destabilization, following the process described in
+ <uri link="::general-concepts/news/"/> (per
+ <uri link="https://www.gentoo.org/glep/glep-0042.html">GLEP 42</uri>).
+ </li>
+ <li>
+ Update the profile to accept both stable and testing keywords by setting
+ <c>ACCEPT_KEYWORDS="${ARCH} ~${ARCH}"</c> in the appropriate
+ <c>profiles/arch/${ARCH}/...</c> file(s).
+ </li>
+ <li>
+ Remove the architecture from all open stabilization bugs using the script
+ at
+ <uri>https://gitweb.gentoo.org/proj/pkgcore/pkgcore.git/tree/examples/destable_arch_bugs.py</uri>.
+ </li>
+ <li>
+ Convert all ebuild keywords for the architecture to testing:
+ <c>qkeyword --all "${ARCH}" | cut -f1 -d" " | xargs -n 250 qatom
+ -F "%{CATEGORY}/%{PN}/%{PF}.ebuild" | xargs ekeyword "~${ARCH}"</c>
+ (<c>qkeyword</c> and <c>qatom</c> are tools from
+ <c>app-portage/portage-utils</c>, while <c>ekeyword</c> is provided by
+ <c>app-portage/gentoolkit</c>).
+ </li>
+ <li>
+ Update any eclasses that define shared <c>KEYWORDS</c> variables. Currently,
+ this includes <c>acct-group.eclass</c> and <c>acct-user.eclass</c>.
+ </li>
+ <li>
+ Update the architecture status in the template files within the
+ <uri link="https://gitweb.gentoo.org/fork/bugzilla.git/">bugzilla</uri>
+ repository as needed.
+ </li>
+</ol>
+
+</body>
+</section>
+</chapter>
+</devbook>
diff --git a/keywording/text.xml b/keywording/text.xml
index 490b3fb..6ed75c6 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -18,4 +18,5 @@ Refer to the subpages for details on policy, procedures, and maintenance.
<include href="concepts/"/>
<include href="workflow/"/>
+<include href="maintenance/"/>
</devbook>
reply other threads:[~2025-09-15 8:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1757925739.6c3308be9ca79098e8653b3602b5832520e82a8d.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.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