* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2013-02-16 0:03 Markos Chandras
0 siblings, 0 replies; 37+ messages in thread
From: Markos Chandras @ 2013-02-16 0:03 UTC (permalink / raw
To: gentoo-commits
commit: 77cc62ef56812a420b65cffa0e02d159b10733ad
Author: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 16 00:01:48 2013 +0000
Commit: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Sat Feb 16 00:02:34 2013 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=77cc62ef
keywording: ARM is not considered exotic or understaffed anymore
---
keywording/text.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index c5ba0f4..828fd63 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -178,7 +178,7 @@ teams for details.
</p>
<p>
- It's important to note that alternative arches (like alpha, arm, ia64, s390,
+ It's important to note that alternative arches (like alpha, ia64, s390,
sh, sparc, hppa, ppc*) are mainly undermanned arches, some of them are
slow, they have more basic problems and have a small userbase. Just file
bugs for these architectures when a package is going to be a dependency of a
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2015-03-14 9:20 Markos Chandras
0 siblings, 0 replies; 37+ messages in thread
From: Markos Chandras @ 2015-03-14 9:20 UTC (permalink / raw
To: gentoo-commits
commit: 9c2e6f500a276b974bc2e2bd476d8423f113dbb2
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 12 13:29:40 2015 +0000
Commit: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Sat Mar 14 09:18:46 2015 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=9c2e6f50
Document the new ALLARCHES process.
Per the latest council meeting, it is now possible to request a
stabilization on all arches at once (for architecture-independent
packages). This commit documents the new keyword and process on the
"Keywording" page.
Link: http://archives.gentoo.org/gentoo-dev/message/5d96b51ced1d1ed126951f117c828482
X-Gentoo-Bug: 543062
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=543062
keywording/text.xml | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index e22a76a..c386427 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -268,6 +268,32 @@ Vulnerability Treatment Policy</uri>
</body>
</section>
+<subsection>
+ <title>
+ Simultaneous stabilization on all architectures
+ </title>
+ <body>
+ <p>
+ If you maintain an architecture-independent package (data files,
+ icons, pure Perl,...) then you may request that your
+ package be stabilized on all arches at once. To do this<d />when
+ you are filing the stabilization bug<d />please add the keyword
+ <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
+ arches that you would like to stabilize.
+ </p>
+
+ <p>
+ The arch teams, when encountering the <c>ALLARCHES</c> keyword,
+ should perform their usual set of tests on a single convenient
+ architecture. Then, if everything works, stabilize not only the
+ arch that was used during testing, but also all of the other
+ arches in CC on the bug. Afterwards, the CC field can be cleared
+ and the bug closed if appropriate.
+ </p>
+ </body>
+</subsection>
+
+
<section>
<title>Removing Package Versions</title>
<body>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2015-06-17 12:05 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2015-06-17 12:05 UTC (permalink / raw
To: gentoo-commits
commit: 1362d6608c323241ad1a4d0313046e99407ef352
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Thu May 21 16:37:11 2015 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Jun 1 18:55:39 2015 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=1362d660
Live ebuilds need not specify KEYWORDS.
Bug 545488.
keywording/text.xml | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index c386427..e31e0a3 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -12,7 +12,7 @@ distinction is important.
</note>
<p>
-Every ebuild must specify a <c>KEYWORDS</c> variable. This variable is used to
+Most ebuilds specify a <c>KEYWORDS</c> variable. This variable is used to
indicate the suitability and stability of both the package and the ebuild on
each given arch (<c>sparc</c>, <c>ppc</c>, <c>x86-obsd</c>, ...).
</p>
@@ -99,6 +99,12 @@ tested.
Do <b>not</b> use the <c>*</c> or <c>~*</c> special keywords in ebuilds.
</p>
+<note>
+Usually, "live" ebuilds
+(see <uri link="::ebuild-writing/functions/src_unpack/cvs-sources"/>)
+do not specify a <c>KEYWORDS</c> variable, or assign the empty string to it.
+</note>
+
<section>
<title>Equal Visibility Requirement</title>
<body>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2018-08-27 15:24 Göktürk Yüksek
0 siblings, 0 replies; 37+ messages in thread
From: Göktürk Yüksek @ 2018-08-27 15:24 UTC (permalink / raw
To: gentoo-commits
commit: cd0550900d2461ceef2ad82da9371309a49131be
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 19 22:46:11 2018 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Mon Aug 27 15:23:54 2018 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=cd055090
keywording: sort keywords out
Closes: https://github.com/gentoo/devmanual.gentoo.org/pull/91
keywording/text.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 5ad2c75..1dfbc32 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -29,7 +29,7 @@ A sample <c>KEYWORDS</c> entry might look like:
</p>
<codesample lang="ebuild">
-KEYWORDS="x86 sparc ~mips ~ppc ~ppc-macos -ia64"
+KEYWORDS="-ia64 ~mips ~ppc sparc x86 ~ppc-macos"
</codesample>
<p>
@@ -82,15 +82,15 @@ The different levels of keyword are:
<p>
The <c>-*</c> keyword is special. It is used to indicate package versions which are
not worth trying to test on unlisted archs. For example, a binary-only package
-which is only supported upstream on <c>x86</c> and <c>ppc</c> might use:
+which is only supported upstream on <c>ppc</c> and <c>x86</c> might use:
</p>
<codesample lang="ebuild">
-KEYWORDS="-* x86 ppc"
+KEYWORDS="-* ppc x86"
</codesample>
<p>
-This is different in implication from <c>"x86 ppc"</c> <d /> the former implies that
+This is different in implication from <c>"ppc x86"</c> <d /> the former implies that
it will not work on other archs, whereas the latter implies that it has not been
tested.
</p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2020-01-23 13:50 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2020-01-23 13:50 UTC (permalink / raw
To: gentoo-commits
commit: 39f82639c14734efb1a8638952e17984b38a0023
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 23 13:10:50 2020 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Thu Jan 23 13:10:50 2020 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=39f82639
keywording: Follow the terminology defined at start of the section.
Closes: https://bugs.gentoo.org/567312
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 6b2d19c..4897186 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -221,7 +221,7 @@ This also applies to revision bumps, not just to upstream version changes.
<body>
<p>
-Moving a package from <c>~arch</c> to <c>arch</c> is done only by the relevant arch teams.
+Moving an ebuild from <c>~arch</c> to <c>arch</c> is done only by the relevant arch teams.
If you have access to non-x86 hardware but are not on the arch teams, you may wish
to make individual arrangements <d /> the arch teams are happy for help, so long as
they know what is going on. Please note that <c>x86</c> is now no longer an exception
@@ -232,25 +232,26 @@ for further details.
</p>
<p>
-For a package to move to stable, the following guidelines must be met:
+For an ebuild to move to stable, the following guidelines must be met:
</p>
<ul>
<li>
- The package has spent a reasonable amount of time in <c>~arch</c> first. Thirty
- days is the usual figure, although this is clearly only a guideline. For
- critical packages, a much longer duration is expected. For small packages
- which have only minor changes between versions, a shorter period is sometimes
- appropriate.
+ The ebuild has spent a reasonable amount of time in <c>~arch</c> first.
+ Thirty days is the usual figure, although this is clearly only a guideline.
+ For critical packages, a much longer duration is expected. For small
+ packages that have only minor changes between versions, a shorter period is
+ sometimes appropriate.
</li>
<li>
- The package must not have any non-<c>arch</c> dependencies.
+ The ebuild must not have any non-<c>arch</c> dependencies.
</li>
<li>
- The package must not have any severe outstanding bugs or issues.
+ The package version (and the ebuild) must not have any severe outstanding
+ bugs or issues.
</li>
<li>
- The package must be widely tested.
+ The package version must be widely tested.
</li>
<li>
If the package is a library, it should be known not to break any package which
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2020-01-25 6:02 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2020-01-25 6:02 UTC (permalink / raw
To: gentoo-commits
commit: b696fdc696574cd1fec19ff572c951c464fe10be
Author: Tom Wijsman <TomWij <AT> gentoo <DOT> org>
AuthorDate: Tue May 13 00:52:15 2014 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sat Jan 25 05:53:46 2020 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=b696fdc6
keywording: Add developer stabilization exception for AMD64/X86 arches.
References:
- "AMD64 keywording" thread by kingtaco on the gentoo-core mailing list (2007)
- app-emacs stabilization talk by kingtaco and ulm on IRC #gentoo-dev (2007)
- Gentoo Council agenda item: "amd64 arch team and big bug list" (2008/03/13)
Closes: https://bugs.gentoo.org/510198
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index 3942138..fd8f155 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -295,6 +295,13 @@ Vulnerability Treatment Policy</uri>
<title>Stabilization rules</title>
<body>
+<p>
+AMD64, X86: If you are the maintainer of a package that currently has open bugs
+for amd64 or x86 stabilization and own the respectively amd64 or x86 hardware,
+you can do your own testing and keywording of your packages; as long as it is
+not a core system set dependency.
+</p>
+
<p>
SPARC: You must have prior permission from the arch lead. Usually we expect
you to be on the sparc alias for QA reasons, although other arrangements
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2020-05-06 7:49 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2020-05-06 7:49 UTC (permalink / raw
To: gentoo-commits
commit: 0549711de12b5fac535118c49a2df8c2b7b966f1
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sat May 2 19:35:27 2020 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sat May 2 19:35:27 2020 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=0549711d
keywording: SuperH is gone.
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 92e71e2..2368cf3 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -177,14 +177,13 @@ teams for details.
</p>
<p>
- It's important to note that alternative arches (like alpha, ia64, s390,
- sh, sparc, hppa, ppc*) are mainly undermanned arches, some of them are
- slow, they have more basic problems and have a small userbase. Just file
- bugs for these architectures when a package is going to be a dependency of a
- package already keyworded.
+It's important to note that alternative arches (like alpha, ia64, s390, sparc,
+hppa, ppc*) are mainly undermanned arches, some of them are slow, they have
+more basic problems and have a small userbase. Just file bugs for these
+architectures when a package is going to be a dependency of a package already
+keyworded.
</p>
-
<p>
Do <b>not</b> commit straight to <c>arch</c>.
</p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2020-07-12 18:32 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2020-07-12 18:32 UTC (permalink / raw
To: gentoo-commits
commit: 3cbde132b6b28dcaf4ae591c567b6828e4fc7688
Author: Alexey Sokolov <sokolov <AT> google <DOT> com>
AuthorDate: Fri Jun 26 14:03:30 2020 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun Jul 12 18:31:43 2020 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=3cbde132
keywording: Mention NATTkA
Signed-off-by: Alexey Sokolov <sokolov <AT> google.com>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 2368cf3..b151e26 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -245,9 +245,13 @@ the arch teams are happy for help, so long as they know what is going on.
<p>
In order to request stabilization of an ebuild, file a bug to the package's
-maintainer (which may be yourself), and list all secondary maintainers
-in the bug's CC. When the maintainers consider the ebuild to be ready for
-stabilization, they will add the relevant architecture teams to the CC list.
+maintainer (which may be yourself) in the Stabilization component, and list
+all secondary maintainers in the bug's CC. When the maintainers consider the
+ebuild to be ready for stabilization, they will add the relevant architecture
+teams to the CC list. They can do it manually, or they can fill the package
+list field, add the <c>CC-ARCHES</c> keyword, and let
+<uri link="https://dev.gentoo.org/~mgorny/doc/nattka/">NATTkA</uri>
+automatically add arch teams to CC.
That way teams can remove themselves from the list when they are done, giving
a clear indication of which teams still have to stabilize a package.
</p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-02-15 7:21 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-02-15 7:21 UTC (permalink / raw
To: gentoo-commits
commit: 5914e1444dccfb9229bd5f7973070dc825a621c8
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 15 07:20:25 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Feb 15 07:20:25 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5914e144
keywording: Fix coding style
Fixes: 9c2e6f500a276b974bc2e2bd476d8423f113dbb2
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 38 +++++++++++++++++++-------------------
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index b151e26..bf924af 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -334,25 +334,25 @@ So packages are not to be marked stable for one of these architectures.
<subsection>
<title>Simultaneous stabilization on all architectures</title>
- <body>
- <p>
- If you maintain an architecture-independent package (data files,
- icons, pure Perl,...) then you may request that your
- package be stabilized on all arches at once. To do this <d/> when
- you are filing the stabilization bug <d/> please add the keyword
- <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
- arches that you would like to stabilize.
- </p>
-
- <p>
- The arch teams, when encountering the <c>ALLARCHES</c> keyword,
- should perform their usual set of tests on a single convenient
- architecture. Then, if everything works, stabilize not only the
- arch that was used during testing, but also all of the other
- arches in CC on the bug. Afterwards, the CC field can be cleared
- and the bug closed if appropriate.
- </p>
- </body>
+<body>
+
+<p>
+If you maintain an architecture-independent package (data files, icons, pure
+Perl, ...) then you may request that your package be stabilized on all arches
+at once. To do this <d/> when you are filing the stabilization bug <d/> please
+add the keyword <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
+arches that you would like to stabilize.
+</p>
+
+<p>
+The arch teams, when encountering the <c>ALLARCHES</c> keyword, should perform
+their usual set of tests on a single convenient architecture. Then, if
+everything works, stabilize not only the arch that was used during testing,
+but also all of the other arches in CC on the bug. Afterwards, the CC field can
+be cleared and the bug closed if appropriate.
+</p>
+
+</body>
</subsection>
</section>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-02-17 9:29 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-02-17 9:29 UTC (permalink / raw
To: gentoo-commits
commit: dfae932454e5f59ac7985c0fe6475de5dca7a656
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 14 20:12:04 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Feb 17 09:20:24 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=dfae9324
keywording: Clarify self-testing on amd64/x86
Some confusion occurred about whether this
was just for keywording or not, so I've
changed the phrasing.
I've also removed the requirement for a bug;
this isn't required in practice and adds
unnecessary overhead.
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index bf924af..0f2131b 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -299,10 +299,9 @@ Vulnerability Treatment Policy</uri>
<body>
<p>
-AMD64, X86: If you are the maintainer of a package that currently has open bugs
-for amd64 or x86 stabilization and own the respectively amd64 or x86 hardware,
-you can do your own testing and keywording of your packages; as long as it is
-not a core system set dependency.
+AMD64, X86: If you are the maintainer of a package and own the respective amd64
+or x86 hardware, you can do your own testing (stabilization and keywording) of
+your packages; as long as it is not a core system set dependency.
</p>
<p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-02-17 9:29 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-02-17 9:29 UTC (permalink / raw
To: gentoo-commits
commit: 2ad7f77460baef02015ca41032bc86896c9a3a1f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 14 20:14:58 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Feb 17 09:29:44 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=2ad7f774
keywording: Use "Pure Python" instead of "Pure Perl"
We prefer not to use ALLARCHES for Perl packages because
of how sensitive Perl can be to the underlying host.
While Perl is cross-platform, use of functions which
vary across hosts (e.g. unpack) is quite common.
Let's use Python as an example instead which is
endorsed [0] by Gentoo's Python Project.
[0] https://wiki.gentoo.org/wiki/Project:Python#ALLARCHES
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 790a582..9c88cf1 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -340,7 +340,7 @@ So packages are not to be marked stable for one of these architectures.
<p>
If you maintain an architecture-independent package (data files, icons, pure
-Perl, ...) then you may request that your package be stabilized on all arches
+Python, ...) then you may request that your package be stabilized on all arches
at once. To do this <d/> when you are filing the stabilization bug <d/> please
add the keyword <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
arches that you would like to stabilize.
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-02-17 9:29 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-02-17 9:29 UTC (permalink / raw
To: gentoo-commits
commit: de435d26ee4d040969db12d59ff103e8b7cd75a6
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 14 20:18:37 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Feb 17 09:29:45 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=de435d26
keywording: Encourage setting ALLARCHES metadata tag
Closes: https://github.com/gentoo/devmanual/pull/188
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index 9c88cf1..391f2d6 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -346,6 +346,12 @@ add the keyword <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
arches that you would like to stabilize.
</p>
+<p>
+If your package is architecture-independent, you should add the
+<c><stabilize-allarches></c> tag to metadata.xml. This allows consistency
+in future stabilizations and saves arch teams considerable work.
+</p>
+
<p>
The arch teams, when encountering the <c>ALLARCHES</c> keyword, should perform
their usual set of tests on a single convenient architecture. Then, if
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-02-17 9:29 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-02-17 9:29 UTC (permalink / raw
To: gentoo-commits
commit: 6d1fffbccb1675783eb758ba1b2ba60e7e976ed4
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 15 07:03:28 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Feb 17 09:29:44 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=6d1fffbc
keywording: Note that we can test x86 via amd64
Closes: https://github.com/gentoo/devmanual/pull/187
Suggested-by: Joonas Niilola <juippis <AT> gentoo.org>
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 0f2131b..790a582 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -301,7 +301,10 @@ Vulnerability Treatment Policy</uri>
<p>
AMD64, X86: If you are the maintainer of a package and own the respective amd64
or x86 hardware, you can do your own testing (stabilization and keywording) of
-your packages; as long as it is not a core system set dependency.
+your packages; as long as it is not a core system set dependency. Note that
+it is acceptable to test x86 using a
+<uri link="https://wiki.gentoo.org/wiki/Project:AMD64/32-bit_Chroot_Guide">
+specialized environment on amd64</uri>.
</p>
<p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-03-11 13:16 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-03-11 13:16 UTC (permalink / raw
To: gentoo-commits
commit: 3fbb9af3ba7e5e617dca6559108d757d587e07b2
Author: Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 11 12:59:47 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Thu Mar 11 13:11:38 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=3fbb9af3
keywording: use <stabilize-allarches/> as a real example
- Make it clear and copy-pasteable that this tag has no content inside.
Rest occurences in metadata/text.xml are descriptive text, not
straight examples.
Closes: https://github.com/gentoo/devmanual/pull/199
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 1c5f71d..93a5ae2 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -348,7 +348,7 @@ arches that you would like to stabilize.
<p>
If your package is architecture-independent, you should add the
-<c><stabilize-allarches></c> tag to metadata.xml. This allows consistency
+<c><stabilize-allarches/></c> tag to metadata.xml. This allows consistency
in future stabilizations and saves arch teams considerable work.
</p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-03-30 16:10 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-03-30 16:10 UTC (permalink / raw
To: gentoo-commits
commit: fb5642b982abe07a3a215e39ca315ae2b5553e68
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 04:35:28 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue Mar 30 16:00:53 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=fb5642b9
keywording: mention pkgdev as an alternative to repoman
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 93a5ae2..6d7c394 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -218,9 +218,9 @@ available.
<p>
If there are no new dependencies, do not remove keywords if your commit fails
-with repoman <d/> please try a full <c>git pull</c> and if you still have
-problems, then commit with <c>repoman -I</c> and file a bug to the broken
-architecture, noting it in your git commit message.
+with <c>repoman</c> or <c>pkgdev</c> <d/> instead please commit with
+<c>repoman -I</c> and file a bug to the broken architecture, noting it in your
+git commit message.
</p>
<important>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: 34957441bbcce538d388c262ec53b34d0d8ddcc5
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 05:25:39 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:10 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=34957441
keywording: minor grammar/phrasing changes
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 46 +++++++++++++++++++++++-----------------------
1 file changed, 23 insertions(+), 23 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 0f08c7e..fb490cc 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -168,20 +168,20 @@ archs (there is at least one case of a <c>vim</c> script which only worked on
</p>
<p>
-Note that most (non-x86) archs expect you to be on the arch team and bugzilla
-alias if you are committing packages with keywords for that arch, and may have
-additional requirements of which you should be aware (on <c>mips</c>, for example,
-there are multiple ABIs and byte orders to consider <d /> a package working on your
-<c>o32</c> box may not work on <c>o64</c> or <c>n32</c>). Contact the individual arch
-teams for details.
+Note that most (non-<c>amd64</c>/<c>x86</c>) archs expect you to be on the
+arch team and bugzilla alias if you are committing packages with keywords for
+that arch, and may have additional requirements of which you should be aware
+(on <c>mips</c>, for example, there are multiple ABIs and byte orders to
+consider <d/> a package working on your <c>o32</c> box may not work on
+<c>o64</c> or <c>n32</c>). Contact the individual arch teams for details.
</p>
<p>
-It's important to note that alternative arches (like alpha, ia64, s390, sparc,
-hppa, ppc*) are mainly undermanned arches, some of them are slow, they have
-more basic problems and have a small userbase. Just file bugs for these
-architectures when a package is going to be a dependency of a package already
-keyworded.
+It's important to note that alternative arches (like <c>alpha</c>, <c>ia64</c>,
+<c>s390</c>, <c>sparc</c>, <c>hppa</c>, <c>ppc*</c>) are mainly understaffed
+arches, some of them are slow, they have more basic problems and have a small
+userbase. Just file bugs for these architectures when a package is going to be
+a dependency of a package already keyworded.
</p>
<p>
@@ -253,8 +253,8 @@ teams to the CC list. They can do it manually, or they can fill the package
list field, add the <c>CC-ARCHES</c> keyword, and let
<uri link="https://dev.gentoo.org/~mgorny/doc/nattka/">NATTkA</uri>
automatically add arch teams to CC.
-That way teams can remove themselves from the list when they are done, giving
-a clear indication of which teams still have to stabilize a package.
+That way, teams can remove themselves from the list when they are done, giving
+a clear indication of which teams still remain to stabilize a package.
</p>
<p>
@@ -290,7 +290,7 @@ for further details):
<p>
For security fixes, the "reasonable amount of time" guideline may be relaxed.
See the <uri link="https://www.gentoo.org/support/security/vulnerability-treatment-policy.html">
-Vulnerability Treatment Policy</uri>
+Vulnerability Treatment Policy</uri>.
</p>
</body>
@@ -303,9 +303,9 @@ Vulnerability Treatment Policy</uri>
AMD64, X86: If you are the maintainer of a package and own the respective amd64
or x86 hardware, you can do your own testing (stabilization and keywording) of
your packages; as long as it is not a core system set dependency. Note that
-it is acceptable to test x86 using a
+it is acceptable to test <c>x86</c> using a
<uri link="https://wiki.gentoo.org/wiki/Project:AMD64/32-bit_Chroot_Guide">
-specialized environment on amd64</uri>.
+specialized environment</uri> on <c>amd64</c>.
</p>
<p>
@@ -321,15 +321,15 @@ the team can keep an eye out for possible keywording mistakes.
</p>
<p>
-Exotic architectures (like hppa, ia64, ppc*, sparc) are short on manpower,
-so it's best if you avoid opening bugs for stabilization of new packages
-for them, unless it is absolutely necessary (e.g., a reverse dependency
-for your package).
+Exotic architectures (like <c>hppa</c>, <c>ia64</c>, <c>ppc*</c>, <c>sparc</c>)
+are short on help, so it's best if you avoid opening bugs for stabilization
+of new packages for them, unless it is absolutely necessary (e.g., a reverse
+dependency for your package).
</p>
<p>
-Some architectures (like mips, riscv) do not maintain a stable keyword.
-So packages are not to be marked stable for one of these architectures.
+Some architectures (like <c>mips</c>, <c>riscv</c>) do not maintain a stable
+keyword, so packages are not to be marked stable for one of these architectures.
</p>
</body>
@@ -341,7 +341,7 @@ So packages are not to be marked stable for one of these architectures.
<p>
If you maintain an architecture-independent package (data files, icons, pure
-Python, ...) then you may request that your package be stabilized on all arches
+Python, ...), then you may request that your package be stabilized on all arches
at once. To do this <d/> when you are filing the stabilization bug <d/> please
add the keyword <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
arches that you would like to stabilize.
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: aca4e12789394f7e2b6af34ef3f3dc68d79065d5
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 08:45:25 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:11 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=aca4e127
keywording: note that setting KEYWORDS="" in a live ebuild is unnecessary
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 5602de1..f5f0911 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -94,7 +94,7 @@ Do <b>not</b> use the <c>*</c> or <c>~*</c> special keywords in ebuilds.
<note>
Usually, "live" ebuilds
(see <uri link="::ebuild-writing/functions/src_unpack/vcs-sources/"/>)
-do not specify a <c>KEYWORDS</c> variable, or assign the empty string to it.
+do not specify a <c>KEYWORDS</c> variable.
</note>
</body>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: 1f5f72e47dde3fae29ed9cd96ada00902cc9a395
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 05:26:58 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:10 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=1f5f72e4
keywording: make clear automatically CCing arches is preferred
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index fb490cc..ea28bed 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -249,10 +249,10 @@ In order to request stabilization of an ebuild, file a bug to the package's
maintainer (which may be yourself) in the Stabilization component, and list
all secondary maintainers in the bug's CC. When the maintainers consider the
ebuild to be ready for stabilization, they will add the relevant architecture
-teams to the CC list. They can do it manually, or they can fill the package
+teams to the CC list. They can fill the package
list field, add the <c>CC-ARCHES</c> keyword, and let
<uri link="https://dev.gentoo.org/~mgorny/doc/nattka/">NATTkA</uri>
-automatically add arch teams to CC.
+automatically add arch teams to CC (preferred), or do this manually.
That way, teams can remove themselves from the list when they are done, giving
a clear indication of which teams still remain to stabilize a package.
</p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: 5df4e789f27b792b785620802cb6376c2f675b83
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 08:48:28 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:12 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5df4e789
keywording: add nuance about first-time ALLARCHES stabilisations
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index f5f0911..9e7177e 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -364,6 +364,13 @@ but also all of the other arches in CC on the bug. Afterwards, the CC field can
be cleared and the bug closed if appropriate.
</p>
+<p>
+Note that first-time <c>ALLARCHES</c> stabilizations are done "as normal" <d/>
+i.e. all arch teams test individually as if it was not set. This nuance in the
+procedure is part of why developers should not manually set <c>ALLARCHES</c> in
+bugs, but instead let <c>NATTkA</c> set it automatically based on metadata.xml.
+</p>
+
</body>
</subsection>
</section>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: acfc48b80657c6221e1a4000ec046c65cd72fcc6
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 05:18:18 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:09 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=acfc48b8
keywording: call ~arch ("testing") and arch ("stable")
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 27 ++++++++++++++-------------
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 6d7c394..0f08c7e 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -38,14 +38,14 @@ The different levels of keyword are:
<dl>
<dt>
- <c>arch</c> (<c>x86</c>, <c>ppc-macos</c>)
+ <c>arch</c> (<c>x86</c>, <c>ppc-macos</c>) ("stable")
</dt>
<dd>
Both the package version <e>and</e> the ebuild are widely tested, known to work
and not have any serious issues on the indicated platform.
</dd>
<dt>
- <c>~arch</c> (<c>~x86</c>, <c>~ppc-macos</c>)
+ <c>~arch</c> (<c>~x86</c>, <c>~ppc-macos</c>) ("testing")
</dt>
<dd>
The package version and the ebuild are believed to work and do not have any
@@ -53,7 +53,7 @@ The different levels of keyword are:
is considered suitable for <c>arch</c>.
</dd>
<dt>
- No keyword
+ No keyword ("unkeyworded")
</dt>
<dd>
If a package has no keyword for a given arch, it means it is not known
@@ -153,7 +153,7 @@ user system</b>.
<body>
<important>
-New packages should be marked as <c>~arch</c> only upon
+New packages should be marked as <c>~arch</c> ("testing") only upon
architectures for which the committing developer has tested.
</important>
@@ -185,7 +185,7 @@ keyworded.
</p>
<p>
-Do <b>not</b> commit straight to <c>arch</c>.
+Do <b>not</b> commit straight to <c>arch</c> ("stable").
</p>
</body>
@@ -196,10 +196,10 @@ Do <b>not</b> commit straight to <c>arch</c>.
<body>
<p>
-When upgrading, drop all existing keywords from <c>arch</c> to <c>~arch</c>, and leave
-any existing <c>~arch</c> keywords intact. This must be done even if you <e>think</e>
-you're just making a trivial fix <d /> there have been several examples of the
-stable tree getting broken this way.
+When upgrading, drop all existing keywords from <c>arch</c> to <c>~arch</c>
+("testing"), and leave any existing <c>~arch</c> keywords intact. This must be
+done even if you <e>think</e> you're just making a trivial fix <d /> there have
+been several examples of the stable tree getting broken this way.
</p>
<p>
@@ -237,10 +237,11 @@ to do this.
<body>
<p>
-Stabilization, i.e., moving an ebuild from <c>~arch</c> to <c>arch</c>, is done
-by the relevant architecture teams. If you have access to exotic hardware but
-are not on the arch teams, you may wish to make individual arrangements <d/>
-the arch teams are happy for help, so long as they know what is going on.
+Stabilization, i.e., moving an ebuild from <c>~arch</c> ("testing") to
+<c>arch</c> ("stable"), is done by the relevant architecture teams. If you have
+access to exotic hardware but are not on the arch teams, you may wish to make
+individual arrangements <d/> the arch teams are happy for help, so long as they
+know what is going on.
</p>
<p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: 0da552c23c04072e728dd83ffe3a34903b64f481
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 08:44:46 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:11 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=0da552c2
keywording: non-developers should not add non amd64/x86 keywords in general
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index ea28bed..5602de1 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -154,7 +154,10 @@ user system</b>.
<important>
New packages should be marked as <c>~arch</c> ("testing") only upon
-architectures for which the committing developer has tested.
+architectures for which the committing developer has tested. If proxying
+commits for a non-developer, please ensure they have some relationship
+with the relevant arch teams, or <d/> better yet <d/> ask them to file
+a keywording bug instead for non-<c>amd64</c>/<c>x86</c>.
</important>
<p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: 596cd2dec06268d8e03971ee41e58b8b974e43ac
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 09:06:08 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:14 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=596cd2de
keywording: add arm/arm64 policy for keywording/stablization
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index 075f3c1..9b71791 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -348,6 +348,16 @@ Vulnerability Treatment Policy</uri>.
specialized environment</uri> on <c>amd64</c>.
</li>
+ <li>
+ <c>arm</c>, <c>arm64</c>: These teams have a strict policy on passing
+ testsuites. You <b>must</b> run test suites for packages with e.g.
+ <c>FEATURES=test</c> for Portage. Keywording or stabilizing packages which
+ fail these tests is avoided but acceptable if the test suite is fragile or
+ failures are known and reported. It is preferred to have to keyword or
+ stabilize more packages on these arches if needed for e.g. test dependencies
+ rather than masking or disabling tests here.
+ </li>
+
<li>
<c>sparc</c>: You must have prior permission from the arch lead. Usually we
expect you to be on the sparc alias for QA reasons, although other
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: 0b9aa967db85539baad1903c8c681a963e1765ec
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 09:12:19 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:14 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=0b9aa967
keywording: add QA policy link for dropped keywords
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 9b71791..89ab1ea 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -215,8 +215,9 @@ architectures, then you should file a bug or ask on IRC before you upgrade the
ebuild. If you really need to get the ebuild added in a hurry, for example,
for a security fix, then you should drop any <c>KEYWORDS</c> which are causing
problems and CC the relevant architectures on the bug <d/> you <b>must</b> file
-a new bug to the architecture in question regarding this if no bug is already
-available.
+a <uri link="https://projects.gentoo.org/qa/policy-guide/keywords.html#pg0401">
+new bug</uri> to the architecture in question regarding this if no bug is
+already available.
</p>
<p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: 147d70669db90455ee801244c75383651b9ce2da
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 09:01:41 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:13 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=147d7066
keywording: convert 'Stabilization rules' into a list
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 40 ++++++++++++++++++++++------------------
1 file changed, 22 insertions(+), 18 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index f57e18a..075f3c1 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -337,26 +337,30 @@ Vulnerability Treatment Policy</uri>.
<title>Stabilization rules</title>
<body>
-<p>
-AMD64, X86: If you are the maintainer of a package and own the respective amd64
-or x86 hardware, you can do your own testing (stabilization and keywording) of
-your packages; as long as it is not a core system set dependency. Note that
-it is acceptable to test <c>x86</c> using a
-<uri link="https://wiki.gentoo.org/wiki/Project:AMD64/32-bit_Chroot_Guide">
-specialized environment</uri> on <c>amd64</c>.
-</p>
+<ul>
+ <li>
+ <c>amd64</c>, <c>x86</c>: If you are the maintainer of a package and own
+ the respective <c>amd64</c> or <c>x86</c> hardware, you can do your own
+ testing (stabilization and keywording) of your packages; as long as it is
+ not a core system set dependency. Note that it is acceptable to test
+ <c>x86</c> using a
+ <uri link="https://wiki.gentoo.org/wiki/Project:AMD64/32-bit_Chroot_Guide">
+ specialized environment</uri> on <c>amd64</c>.
+ </li>
-<p>
-SPARC: You must have prior permission from the arch lead. Usually we expect
-you to be on the sparc alias for QA reasons, although other arrangements
-can be made if you will only be working with a small group of packages.
-</p>
+ <li>
+ <c>sparc</c>: You must have prior permission from the arch lead. Usually we
+ expect you to be on the sparc alias for QA reasons, although other
+ arrangements can be made if you will only be working with a small group of
+ packages.
+ </li>
-<p>
-ALPHA: Maintainers may keyword their own packages but are reminded to inform
-the Alpha team if they can help out with testing and keywording packages so
-the team can keep an eye out for possible keywording mistakes.
-</p>
+ <li>
+ <c>alpha</c>: Maintainers may keyword their own packages but are reminded to
+ inform the Alpha team if they can help out with testing and keywording
+ packages so the team can keep an eye out for possible keywording mistakes.
+ </li>
+</ul>
<p>
Exotic architectures (like <c>hppa</c>, <c>ia64</c>, <c>ppc*</c>, <c>sparc</c>)
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: 48cd0bf726e676abf333e186c7632e5eb8323390
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 29 22:27:05 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:15 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=48cd0bf7
keywording: s/archs/arches/
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 89ab1ea..aa01fcc 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -73,7 +73,7 @@ The different levels of keyword are:
<p>
The <c>-*</c> keyword is special. It is used to indicate package versions which are
-not worth trying to test on unlisted archs. For example, a binary-only package
+not worth trying to test on unlisted arches. For example, a binary-only package
which is only supported upstream on <c>ppc</c> and <c>x86</c> might use:
</p>
@@ -82,9 +82,9 @@ KEYWORDS="-* ppc x86"
</codesample>
<p>
-This is different in implication from <c>"ppc x86"</c> <d /> the former implies that
-it will not work on other archs, whereas the latter implies that it has not been
-tested.
+This is different in implication from <c>"ppc x86"</c> <d/> the former implies
+that it will not work on other arches, whereas the latter implies that it has
+not been tested.
</p>
<p>
@@ -166,12 +166,12 @@ assume that user submitted ebuilds will have correct <c>KEYWORDS</c> <d /> chanc
they just copied from somewhere else. Do <b>not</b> assume that upstream's
'supported architectures' list is correct. Do <b>not</b> assume that because your
code is written in Perl / Python / Java / whatever that it will run on other
-archs (there is at least one case of a <c>vim</c> script which only worked on
+arches (there is at least one case of a <c>vim</c> script which only worked on
<c>x86</c>).
</p>
<p>
-Note that most (non-<c>amd64</c>/<c>x86</c>) archs expect you to be on the
+Note that most (non-<c>amd64</c>/<c>x86</c>) arches expect you to be on the
arch team and bugzilla alias if you are committing packages with keywords for
that arch, and may have additional requirements of which you should be aware
(on <c>mips</c>, for example, there are multiple ABIs and byte orders to
@@ -274,7 +274,7 @@ Ask in #gentoo-dev or on the gentoo-dev mailing list if you need help.
<c>NATTkA</c> will set the <c>sanity-check</c> field on Bugzilla to either
<c>-</c> or <c>+</c> depending on whether the package list results in a
consistent dependency graph. You may need to add more packages or adjust the
-archs listed for each package based on the output the bot posts as a comment
+arches listed for each package based on the output the bot posts as a comment
on the bug. Please note that arch teams may not process or notice bugs with a
blank or <c>-</c> sanity-check, so please fix this if it occurs <d/> or ask for
help to do so.
@@ -292,8 +292,8 @@ You may wish to read NATTkA's
<uri link="https://github.com/mgorny/nattka#filing-keywordingstabilization-bugs">
documentation</uri> for help on package list syntax or other information about
the tool. The documentation details syntax which can be used, such as <c>*</c>
-to represent 'all previously stable arches', or '^' to copy the arches from the
-line(s) above.
+to represent "all previously stable arches", or <c>^</c> to copy the arches
+from the line(s) above.
</p>
<p>
@@ -447,7 +447,7 @@ any given keyword level on any profile. The aim here is:
</ul>
<p>
-If you would like a particular package version moved to stable on certain archs
+If you would like a particular package version moved to stable on certain arches
so that you can tidy up, file a bug.
</p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-04-07 17:35 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-04-07 17:35 UTC (permalink / raw
To: gentoo-commits
commit: 5415582aaa5845c3b71501f92ad8e547bd1c0c30
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 08:58:33 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:35:13 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5415582a
keywording: expound on NATTkA importance and HOWTO
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index 9e7177e..f57e18a 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -260,6 +260,41 @@ That way, teams can remove themselves from the list when they are done, giving
a clear indication of which teams still remain to stabilize a package.
</p>
+<p>
+It is <e>strongly</e>
+<uri link="https://archives.gentoo.org/gentoo-dev/message/cd62f6be924f6a0f76b68a07d33b256a">
+recommended</uri> that <c>NATTkA</c> be used to file keywording or
+stabilization bugs to ensure that arches are not accidentally forgot about;
+the automation removes an often error-prone step in the arch-testing process.
+Ask in #gentoo-dev or on the gentoo-dev mailing list if you need help.
+</p>
+
+<p>
+<c>NATTkA</c> will set the <c>sanity-check</c> field on Bugzilla to either
+<c>-</c> or <c>+</c> depending on whether the package list results in a
+consistent dependency graph. You may need to add more packages or adjust the
+archs listed for each package based on the output the bot posts as a comment
+on the bug. Please note that arch teams may not process or notice bugs with a
+blank or <c>-</c> sanity-check, so please fix this if it occurs <d/> or ask for
+help to do so.
+</p>
+
+<note>
+Note that sometimes NATTkA may do <e>nothing</e> if it has concluded the package
+list is complete. You may wish to run <c>nattka sanity-check BUG</c> where
+<c>BUG</c> is the bug number you're having an issue with in order to debug the
+issue to receive verbose output.
+</note>
+
+<p>
+You may wish to read NATTkA's
+<uri link="https://github.com/mgorny/nattka#filing-keywordingstabilization-bugs">
+documentation</uri> for help on package list syntax or other information about
+the tool. The documentation details syntax which can be used, such as <c>*</c>
+to represent 'all previously stable arches', or '^' to copy the arches from the
+line(s) above.
+</p>
+
<p>
For an ebuild to move to stable, the following guidelines must be met
(see <uri link="https://www.gentoo.org/glep/glep-0040.html">GLEP 40</uri>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-07-03 16:21 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-07-03 16:21 UTC (permalink / raw
To: gentoo-commits
commit: 81b5355bb0af54e378abefb5915aa21357f5a809
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 10 01:18:07 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sat Jul 3 16:18:07 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=81b5355b
keywording: mention un-CCing arches if making substantial changes to list
Closes: https://github.com/gentoo/devmanual/pull/218
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index aa01fcc..f548a68 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -280,6 +280,12 @@ blank or <c>-</c> sanity-check, so please fix this if it occurs <d/> or ask for
help to do so.
</p>
+<note>
+In addition, if you are changing the package list of a bug after it has been
+processed, <d/> i.e. after NATTkA has CCed arches <d/> you should un-CC all
+arches so that NATTkA CCs the new correct set of arches.
+</note>
+
<note>
Note that sometimes NATTkA may do <e>nothing</e> if it has concluded the package
list is complete. You may wish to run <c>nattka sanity-check BUG</c> where
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-07-16 9:11 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-07-16 9:11 UTC (permalink / raw
To: gentoo-commits
commit: ee137375b92144471e3ed389b23550c4b8068a72
Author: Florian Schmaus <flow <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 16 08:54:37 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri Jul 16 09:11:09 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=ee137375
keywording: remove mentioning of STABLEREQ bugs.g.o keywords
This keyword is no longer used, NATTkA does not need it, and is
redundant to the "Stabilization Request" component of the "Gentoo
Linux" product, under which stabilization requests are filled.
Signed-off-by: Florian Schmaus <flow <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index f548a68..159d746 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -402,8 +402,8 @@ keyword, so packages are not to be marked stable for one of these architectures.
If you maintain an architecture-independent package (data files, icons, pure
Python, ...), then you may request that your package be stabilized on all arches
at once. To do this <d/> when you are filing the stabilization bug <d/> please
-add the keyword <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
-arches that you would like to stabilize.
+add the keyword <c>ALLARCHES</c> and CC the arches that you would like to
+stabilize.
</p>
<p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-10-13 13:42 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-10-13 13:42 UTC (permalink / raw
To: gentoo-commits
commit: 6b5ff53adca1ad2fe5b3f9b2bb35245fd507ffab
Author: Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 10 10:09:26 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Oct 13 13:40:35 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=6b5ff53a
keywording: add ekeyword ~all command example
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 74bca5d..cc10166 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -201,9 +201,11 @@ Do <b>not</b> commit straight to <c>arch</c> ("stable").
<p>
When upgrading, drop all existing keywords from <c>arch</c> to <c>~arch</c>
-("testing"), and leave any existing <c>~arch</c> keywords intact. This must be
-done even if you <e>think</e> you're just making a trivial fix <d /> there have
-been several examples of the stable tree getting broken this way.
+("testing"), and leave any existing <c>~arch</c> keywords intact. It's easiest
+and safest to use <c>ekeyword ~all my-new-version.ebuild</c> from the <c>
+app-portage/gentoolkit</c> package. This must be done even if you <e>think</e>
+you're just making a trivial fix <d /> there have been several examples of the
+stable tree getting broken this way.
</p>
<p>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2021-10-13 13:42 Ulrich Müller
0 siblings, 0 replies; 37+ messages in thread
From: Ulrich Müller @ 2021-10-13 13:42 UTC (permalink / raw
To: gentoo-commits
commit: 42652857e3b5592b2001f13b041e66c341007ebe
Author: Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 10 10:03:33 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Oct 13 13:40:35 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=42652857
keywording: wrap text at 80 chars
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 71 +++++++++++++++++++++++++++--------------------------
1 file changed, 36 insertions(+), 35 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 159d746..74bca5d 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -5,10 +5,10 @@
<body>
<note>
-<e>Terminology</e>: The term 'package' refers to an entire directory, for example
-<c>app-editors/vim</c> <d /> it does <e>not</e> refer to a specific version. The terms
-'ebuild' or 'package version' are used when this meaning is intended. This
-distinction is important.
+<e>Terminology</e>: The term 'package' refers to an entire directory, for
+example <c>app-editors/vim</c> <d /> it does <e>not</e> refer to a specific
+version. The terms 'ebuild' or 'package version' are used when this meaning is
+intended. This distinction is important.
</note>
<p>
@@ -41,8 +41,8 @@ The different levels of keyword are:
<c>arch</c> (<c>x86</c>, <c>ppc-macos</c>) ("stable")
</dt>
<dd>
- Both the package version <e>and</e> the ebuild are widely tested, known to work
- and not have any serious issues on the indicated platform.
+ Both the package version <e>and</e> the ebuild are widely tested, known to
+ work and not have any serious issues on the indicated platform.
</dd>
<dt>
<c>~arch</c> (<c>~x86</c>, <c>~ppc-macos</c>) ("testing")
@@ -72,9 +72,10 @@ The different levels of keyword are:
</dl>
<p>
-The <c>-*</c> keyword is special. It is used to indicate package versions which are
-not worth trying to test on unlisted arches. For example, a binary-only package
-which is only supported upstream on <c>ppc</c> and <c>x86</c> might use:
+The <c>-*</c> keyword is special. It is used to indicate package versions which
+are not worth trying to test on unlisted arches. For example, a binary-only
+package which is only supported upstream on <c>ppc</c> and <c>x86</c> might
+use:
</p>
<codesample lang="ebuild">
@@ -103,23 +104,23 @@ do not specify a <c>KEYWORDS</c> variable.
<body>
<p>
-An ebuild <b>must not</b> depend upon any package that is of a lower keyword level
-than itself. For example, if <c>foo-1.2</c> depends upon <c>bar-1.2</c>, and
-<c>bar-1.2</c> is <c>~x86</c>, then <c>foo-1.2</c> must <b>not</b> be marked stable on
-<c>x86</c> unless <c>bar-1.2</c> is also stabilised.
+An ebuild <b>must not</b> depend upon any package that is of a lower keyword
+level than itself. For example, if <c>foo-1.2</c> depends upon <c>bar-1.2</c>,
+and <c>bar-1.2</c> is <c>~x86</c>, then <c>foo-1.2</c> must <b>not</b> be marked
+stable on <c>x86</c> unless <c>bar-1.2</c> is also stabilised.
</p>
<p>
-You may assume that if a user accepts <c>~arch</c> for a given arch then they also
-accept <c>arch</c>.
+You may assume that if a user accepts <c>~arch</c> for a given arch then they
+also accept <c>arch</c>.
</p>
<p>
-For optional dependencies, all <e>possible</e> dependencies must satisfy the above.
-Note that certain <c>USE</c> flags can be forcibly disabled on a per-profile basis
-<d /> talk to the arch teams if you require this. For either-or dependencies, <e>at
-least one</e> of the options must be of equal or better visibility than the
-package in question.
+For optional dependencies, all <e>possible</e> dependencies must satisfy the
+above. Note that certain <c>USE</c> flags can be forcibly disabled on a
+per-profile basis <d /> talk to the arch teams if you require this. For
+either-or dependencies, <e>at least one</e> of the options must be of equal or
+better visibility than the package in question.
</p>
</body>
@@ -139,10 +140,10 @@ packages.
<p>
The only time it is acceptable for a user to see the <c>Possibly a DEPEND
-problem</c> error message is if they have manually changed visibility levels for a
-package (for example, through <c>/etc/portage/</c>) and have missed a dependency.
-<b>You should never commit a change which could cause this error to appear on a
-user system</b>.
+problem</c> error message is if they have manually changed visibility levels for
+a package (for example, through <c>/etc/portage/</c>) and have missed a
+dependency. <b>You should never commit a change which could cause this error to
+appear on a user system</b>.
</p>
</body>
@@ -162,12 +163,12 @@ a keywording bug instead for non-<c>amd64</c>/<c>x86</c>.
<p>
Do <b>not</b> assume that your package works on all architectures. Do <b>not</b>
-assume that user submitted ebuilds will have correct <c>KEYWORDS</c> <d /> chances are
-they just copied from somewhere else. Do <b>not</b> assume that upstream's
-'supported architectures' list is correct. Do <b>not</b> assume that because your
-code is written in Perl / Python / Java / whatever that it will run on other
-arches (there is at least one case of a <c>vim</c> script which only worked on
-<c>x86</c>).
+assume that user submitted ebuilds will have correct <c>KEYWORDS</c> <d />
+chances are they just copied from somewhere else. Do <b>not</b> assume that
+upstream's 'supported architectures' list is correct. Do <b>not</b> assume that
+because your code is written in Perl / Python / Java / whatever that it will run
+on other arches (there is at least one case of a <c>vim</c> script which only
+worked on <c>x86</c>).
</p>
<p>
@@ -327,8 +328,8 @@ for further details):
The package version must be widely tested.
</li>
<li>
- If the package is a library, it should be known not to break any package which
- depends upon it.
+ If the package is a library, it should be known not to break any package
+ which depends upon it.
</li>
</ul>
@@ -443,9 +444,9 @@ any given keyword level on any profile. The aim here is:
<ul>
<li>
Never to force a downgrade. (Exception: occasionally you really do want to
- force a downgrade, for example if the newly committed <c>foo-1.3</c> turns out
- to be badly broken and that making everyone downgrade to <c>foo-1.2</c> is the
- better option. This is rare.)
+ force a downgrade, for example if the newly committed <c>foo-1.3</c> turns
+ out to be badly broken and that making everyone downgrade to <c>foo-1.2</c>
+ is the better option. This is rare.)
</li>
<li>
Do not break any existing dependencies.
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2022-01-22 21:35 Sam James
0 siblings, 0 replies; 37+ messages in thread
From: Sam James @ 2022-01-22 21:35 UTC (permalink / raw
To: gentoo-commits
commit: d3dbd7ea0bd09daf0c9daf790d50952244b62b0a
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 12 04:31:49 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 22 21:34:55 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=d3dbd7ea
keywording: add note about `repoman commit --straight-to-stable`
Somewhat regularly see --force being used with repoman commit rather
than --straigh-to-stable.
--straight-to-stable is preferable if it must be done because it
doesn't disable repoman's other QA checks.
Signed-off-by: Sam James <sam <AT> gentoo.org>
keywording/text.xml | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index ed6b6d1..1398ca7 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -189,7 +189,10 @@ a dependency of a package already keyworded.
</p>
<p>
-Do <b>not</b> commit straight to <c>arch</c> ("stable").
+Do <b>not</b> commit straight to <c>arch</c> ("stable"). If it is necessary
+to do so, when using <c>repoman</c>, use
+<c>repoman commit --straight-to-stable</c> and <b>not</b> <c>--force</c> as
+this disables other QA checks.
</p>
</body>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2022-01-22 21:35 Sam James
0 siblings, 0 replies; 37+ messages in thread
From: Sam James @ 2022-01-22 21:35 UTC (permalink / raw
To: gentoo-commits
commit: 5ef0611901e3ef14e6473c960418985f6b6f7c61
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 12 04:36:03 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 22 21:34:56 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5ef06119
keywording: mention filing bugs for package.mask entries
It's useful to have a bug filed for things masked for testing / due
to breakages so that feedback can be gathered in one place / the relevant
issue can be debugged.
We've sometimes had things p.masked indefinitely for "testing" when
it's not clear exactly what needs to be done left, or due to a "bug"
which with few details cannot be reproduced some time later.
Bug: https://bugs.gentoo.org/705394
Signed-off-by: Sam James <sam <AT> gentoo.org>
Closes: https://github.com/gentoo/devmanual/pull/262
Signed-off-by: Sam James <sam <AT> gentoo.org>
keywording/text.xml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index 1398ca7..732271f 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -138,6 +138,12 @@ which are not hard masked must <b>not</b> have a dependency upon hard masked
packages.
</p>
+<p>
+It is good practice to file a bug for ebuilds listed in <c>package.mask</c> to
+allow feedback to be gathered in one location and to reduce the chance of
+forgetting about it. Mention the bug number in the mask message.
+</p>
+
<p>
The only time it is acceptable for a user to see the <c>Possibly a DEPEND
problem</c> error message is if they have manually changed visibility levels for
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2022-01-22 21:35 Sam James
0 siblings, 0 replies; 37+ messages in thread
From: Sam James @ 2022-01-22 21:35 UTC (permalink / raw
To: gentoo-commits
commit: e61cbdca52edcc1ff6bac20577722793703997ce
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 12 04:26:44 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 22 21:34:54 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=e61cbdca
keywording: add explanatory text on maintainer obligations
Inspired partly by a discussion on a GitHub pull request [0].
[0] https://github.com/gentoo/gentoo/pull/23735
Signed-off-by: Sam James <sam <AT> gentoo.org>
keywording/text.xml | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index cc10166..ed6b6d1 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -243,6 +243,29 @@ to do this.
<title>Moving from <c>~arch</c> to <c>arch</c></title>
<body>
+<p>
+If a package has stable keywords, maintainers should regularly (subject to the
+rules below) file stabilization bugs for their packages, ideally approximately
+every 30 days after a new version is added. If a bug report for stabilization
+is filed by somebody else, the maintainer should respond with an
+acknowledgement ("ACK") if the ebuild is ready, and a negative
+acknowledgement ("NAK") if not.
+</p>
+
+<p>
+Previous stable keywords should not be dropped without good cause and it is
+courteous to ping members of the relevant arch team first. Maintainers must not
+drop stable keywords simply because they don't have access to a platform: this
+is what Gentoo's arch teams are here for.
+</p>
+
+<p>
+By convention, these bugs are assigned to package maintainers, but the only
+action expected from maintainers is to acknowledge or reject the
+stabilization rather than carry out additional testing on each required
+architecture themselves.
+</p>
+
<p>
Stabilization, i.e., moving an ebuild from <c>~arch</c> ("testing") to
<c>arch</c> ("stable"), is done by the relevant architecture teams. If you have
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2022-02-18 18:19 Sam James
0 siblings, 0 replies; 37+ messages in thread
From: Sam James @ 2022-02-18 18:19 UTC (permalink / raw
To: gentoo-commits
commit: 17ea5e4be826a1155ddc62ce4dbbccb7d26eba15
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 22 23:24:54 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Feb 18 18:19:34 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=17ea5e4b
keywording: note that stabilization rules are for actual testing
These rules are for maintainers wishing to stable if they have
access to hardware -- they do _not_ mean maintainers must
follow these rules just to file a bug and stabilise a package
via CCing arch teams (the usual route).
Closes: https://bugs.gentoo.org/546942
Signed-off-by: Sam James <sam <AT> gentoo.org>
Closes: https://github.com/gentoo/devmanual/pull/267
Signed-off-by: Sam James <sam <AT> gentoo.org>
keywording/text.xml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index 732271f..f794722 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -379,6 +379,11 @@ Vulnerability Treatment Policy</uri>.
<title>Stabilization rules</title>
<body>
+<p>
+These are rules for stabilizing packages <e>by yourself</e> on a particular
+architecture, <e>not</e> for filing bugs to request arch teams to handle it.
+</p>
+
<ul>
<li>
<c>amd64</c>, <c>x86</c>: If you are the maintainer of a package and own
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2022-03-10 23:33 Sam James
0 siblings, 0 replies; 37+ messages in thread
From: Sam James @ 2022-03-10 23:33 UTC (permalink / raw
To: gentoo-commits
commit: 876646b9ee6fa84f3ed8d225e7ba3442d2da338d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 24 04:20:59 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Mar 10 23:33:17 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=876646b9
keywording: it's preferred to rekeyword packages with new deps
It's preferred to rekeyword packages with their new dependencies in the
same bug rather than using `package.use.mask` as this means the new
code path(s) using the new dependencies get tested rather than just
the new package/dependency in isolation.
Also, no tooling exists for arch testers to automatically remove
the relevant mask(s) once keywording is done, so often we end up
with stale unnecessary masks remaining in tree.
Signed-off-by: Sam James <sam <AT> gentoo.org>
Closes: https://github.com/gentoo/devmanual/pull/270
Signed-off-by: Sam James <sam <AT> gentoo.org>
keywording/text.xml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index f794722..baffaaa 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -239,6 +239,16 @@ with <c>repoman</c> or <c>pkgdev</c> <d/> instead please commit with
git commit message.
</p>
+<p>
+Note that it is preferred to drop keywords on the package and request
+rekeywording of it together with its new dependencies within the same bug to
+allow the new code path(s) in your package to be tested. This won't happen if
+the new dependency is requested for keywording by itself and
+<c>package.use.mask</c> is used to mask the relevant new USE flag: only the
+new package dependency will be tested by arch testers. Also, the mask has to be
+manually removed during the testing process, which is cumbersome.
+</p>
+
<important>
When committing, make sure that you reference any bugs in the commit message.
See <uri link="::ebuild-maintenance/git/#Git Commit Message Format"/> for how
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2022-03-14 17:07 Matt Turner
0 siblings, 0 replies; 37+ messages in thread
From: Matt Turner @ 2022-03-14 17:07 UTC (permalink / raw
To: gentoo-commits
commit: 43a02db3cad737ea1ae574e63caa47a615a0bf20
Author: Matt Turner <mattst88 <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 11 23:41:50 2022 +0000
Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org>
CommitDate: Mon Mar 14 17:06:38 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=43a02db3
keywording: Update arch status and stabilization notes
Closes: https://github.com/gentoo/devmanual/pull/275
Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org>
keywording/text.xml | 13 ++++---------
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 30a7c73..74224a0 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -411,24 +411,19 @@ architecture, <e>not</e> for filing bugs to request arch teams to handle it.
arrangements can be made if you will only be working with a small group of
packages.
</li>
-
- <li>
- <c>alpha</c>: Maintainers may keyword their own packages but are reminded to
- inform the Alpha team if they can help out with testing and keywording
- packages so the team can keep an eye out for possible keywording mistakes.
- </li>
</ul>
<p>
-Exotic architectures (like <c>hppa</c>, <c>ia64</c>, <c>ppc*</c>, <c>sparc</c>)
+Exotic architectures (like <c>hppa</c>, <c>ppc*</c>, <c>sparc</c>)
are short on help, so it's best if you avoid opening bugs for stabilization
of new packages for them, unless it is absolutely necessary (e.g., a reverse
dependency for your package).
</p>
<p>
-Some architectures (like <c>mips</c>, <c>riscv</c>) do not maintain a stable
-keyword, so packages are not to be marked stable for one of these architectures.
+Some architectures (<c>alpha</c>, <c>ia64</c>, <c>mips</c>, <c>riscv</c>,
+<c>s390</c>) do not maintain a stable keyword, so packages are not to be marked
+stable for one of these architectures.
</p>
</body>
^ permalink raw reply related [flat|nested] 37+ messages in thread
* [gentoo-commits] proj/devmanual:master commit in: keywording/
@ 2022-03-16 14:52 Sam James
0 siblings, 0 replies; 37+ messages in thread
From: Sam James @ 2022-03-16 14:52 UTC (permalink / raw
To: gentoo-commits
commit: a4d5e702ddea5f01980e667d6673decdcc8a68e9
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 1 09:49:54 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Mar 16 14:51:50 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=a4d5e702
keywording: describe pending stabilization requests
Describe how maintainers should keep track of (and know when to file)
pending stabilization requests.
Signed-off-by: Sam James <sam <AT> gentoo.org>
keywording/text.xml | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/keywording/text.xml b/keywording/text.xml
index 74224a0..c5b5660 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -429,6 +429,36 @@ stable for one of these architectures.
</body>
</subsection>
+<subsection>
+<title>Keeping track of pending stabilizations</title>
+<body>
+
+<p>
+Maintainers need some method or system to organize and start pending
+stabilizations once they become due.
+</p>
+
+<p>
+There are several tools available that can help with this:
+</p>
+
+<ul>
+ <li>
+ Use <c>imlate</c> from app-portage/gentoolkit
+ </li>
+ <li>
+ Use packages.gentoo.org's maintainer pages (which have a Stabilization
+ tab)
+ </li>
+ <li>
+ Use <c>pkgcheck</c>'s <c>StableRequest</c> check, e.g.
+ <c>grep -ri "larry@" */*/metadata.xml -l | cut -d'/' -f1-2 | xargs pkgcheck scan -k StableRequest</c>
+ </li>
+</ul>
+
+</body>
+</subsection>
+
<subsection>
<title>Simultaneous stabilization on all architectures</title>
<body>
^ permalink raw reply related [flat|nested] 37+ messages in thread
end of thread, other threads:[~2022-03-16 14:52 UTC | newest]
Thread overview: 37+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-04-07 17:35 [gentoo-commits] proj/devmanual:master commit in: keywording/ Ulrich Müller
-- strict thread matches above, loose matches on Subject: below --
2022-03-16 14:52 Sam James
2022-03-14 17:07 Matt Turner
2022-03-10 23:33 Sam James
2022-02-18 18:19 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2021-10-13 13:42 Ulrich Müller
2021-10-13 13:42 Ulrich Müller
2021-07-16 9:11 Ulrich Müller
2021-07-03 16:21 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-11 13:16 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-15 7:21 Ulrich Müller
2020-07-12 18:32 Ulrich Müller
2020-05-06 7:49 Ulrich Müller
2020-01-25 6:02 Ulrich Müller
2020-01-23 13:50 Ulrich Müller
2018-08-27 15:24 Göktürk Yüksek
2015-06-17 12:05 Ulrich Müller
2015-03-14 9:20 Markos Chandras
2013-02-16 0:03 Markos Chandras
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox