[gentoo-commits] proj/devmanual:master commit in: keywording/

[Sam James]

commit: a4d5e702ddea5f01980e667d6673decdcc8a68e9
Author: Sam James  gentoo  org>
AuthorDate: Tue Mar  1 09:49:54 2022 +
Commit: Sam James  gentoo  org>
CommitDate: Wed Mar 16 14:51:50 2022 +
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  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.
 
 
 
+
+Keeping track of pending stabilizations
+
+
+
+Maintainers need some method or system to organize and start pending
+stabilizations once they become due.
+
+
+
+There are several tools available that can help with this:
+
+
+
+  
+Use imlate from app-portage/gentoolkit
+  
+  
+Use packages.gentoo.org's maintainer pages (which have a Stabilization
+tab)
+  
+  
+Use pkgcheck's StableRequest check, e.g.
+  grep -ri "larry@" */*/metadata.xml -l | cut -d'/' -f1-2 | xargs 
pkgcheck scan -k StableRequest
+  
+
+
+
+
+
 
 Simultaneous stabilization on all architectures
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Matt Turner]

commit: 43a02db3cad737ea1ae574e63caa47a615a0bf20
Author: Matt Turner  gentoo  org>
AuthorDate: Fri Mar 11 23:41:50 2022 +
Commit: Matt Turner  gentoo  org>
CommitDate: Mon Mar 14 17:06:38 2022 +
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  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, not 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.
   
-
-  
-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.
-  
 
 
 
-Exotic architectures (like hppa, ia64, ppc*, sparc)
+Exotic architectures (like hppa, ppc*, sparc)
 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).
 
 
 
-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 (alpha, ia64, mips, riscv,
+s390) do not maintain a stable keyword, so packages are not to be marked
+stable for one of these architectures.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Sam James]

commit: 876646b9ee6fa84f3ed8d225e7ba3442d2da338d
Author: Sam James  gentoo  org>
AuthorDate: Mon Jan 24 04:20:59 2022 +
Commit: Sam James  gentoo  org>
CommitDate: Thu Mar 10 23:33:17 2022 +
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  gentoo.org>
Closes: https://github.com/gentoo/devmanual/pull/270
Signed-off-by: Sam James  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 repoman or pkgdev  instead please 
commit with
 git commit message.
 
 
+
+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
+package.use.mask 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.
+
+
 
 When committing, make sure that you reference any bugs in the commit message.
 See  for how

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Sam James]

commit: 17ea5e4be826a1155ddc62ce4dbbccb7d26eba15
Author: Sam James  gentoo  org>
AuthorDate: Sat Jan 22 23:24:54 2022 +
Commit: Sam James  gentoo  org>
CommitDate: Fri Feb 18 18:19:34 2022 +
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  gentoo.org>
Closes: https://github.com/gentoo/devmanual/pull/267
Signed-off-by: Sam James  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.
 Stabilization rules
 
 
+
+These are rules for stabilizing packages by yourself on a particular
+architecture, not for filing bugs to request arch teams to handle it.
+
+
 
   
  amd64, x86: If you are the maintainer of a package and own

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Sam James]

commit: 5ef0611901e3ef14e6473c960418985f6b6f7c61
Author: Sam James  gentoo  org>
AuthorDate: Wed Jan 12 04:36:03 2022 +
Commit: Sam James  gentoo  org>
CommitDate: Sat Jan 22 21:34:56 2022 +
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  gentoo.org>
Closes: https://github.com/gentoo/devmanual/pull/262
Signed-off-by: Sam James  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 not have a 
dependency upon hard masked
 packages.
 
 
+
+It is good practice to file a bug for ebuilds listed in package.mask 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.
+
+
 
 The only time it is acceptable for a user to see the Possibly a DEPEND
 problem error message is if they have manually changed visibility levels 
for

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Sam James]

commit: d3dbd7ea0bd09daf0c9daf790d50952244b62b0a
Author: Sam James  gentoo  org>
AuthorDate: Wed Jan 12 04:31:49 2022 +
Commit: Sam James  gentoo  org>
CommitDate: Sat Jan 22 21:34:55 2022 +
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  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.
 
 
 
-Do not commit straight to arch ("stable").
+Do not commit straight to arch ("stable"). If it is necessary
+to do so, when using repoman, use
+repoman commit --straight-to-stable and not --force as
+this disables other QA checks.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Sam James]

commit: e61cbdca52edcc1ff6bac20577722793703997ce
Author: Sam James  gentoo  org>
AuthorDate: Wed Jan 12 04:26:44 2022 +
Commit: Sam James  gentoo  org>
CommitDate: Sat Jan 22 21:34:54 2022 +
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  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.
 Moving from ~arch to arch
 
 
+
+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.
+
+
+
+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.
+
+
+
+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.
+
+
 
 Stabilization, i.e., moving an ebuild from ~arch ("testing") to
 arch ("stable"), is done by the relevant architecture teams. If you have

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 6b5ff53adca1ad2fe5b3f9b2bb35245fd507ffab
Author: Joonas Niilola  gentoo  org>
AuthorDate: Sun Oct 10 10:09:26 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Oct 13 13:40:35 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=6b5ff53a

keywording: add ekeyword ~all command example

Signed-off-by: Joonas Niilola  gentoo.org>
Signed-off-by: Ulrich Müller  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 not commit straight to arch ("stable").
 
 
 When upgrading, drop all existing keywords from arch to ~arch
-("testing"), and leave any existing ~arch keywords intact. This must be
-done even if you think you're just making a trivial fix  there have
-been several examples of the stable tree getting broken this way.
+("testing"), and leave any existing ~arch keywords intact. It's easiest
+and safest to use ekeyword ~all my-new-version.ebuild from the 
+app-portage/gentoolkit package. This must be done even if you think
+you're just making a trivial fix  there have been several examples of the
+stable tree getting broken this way.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 42652857e3b5592b2001f13b041e66c341007ebe
Author: Joonas Niilola  gentoo  org>
AuthorDate: Sun Oct 10 10:03:33 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Oct 13 13:40:35 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=42652857

keywording: wrap text at 80 chars

Signed-off-by: Joonas Niilola  gentoo.org>
Signed-off-by: Ulrich Müller  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 @@
 
 
 
-Terminology: The term 'package' refers to an entire directory, for 
example
-app-editors/vim  it does not refer to a specific version. 
The terms
-'ebuild' or 'package version' are used when this meaning is intended. This
-distinction is important.
+Terminology: The term 'package' refers to an entire directory, for
+example app-editors/vim  it does not refer to a specific
+version. The terms 'ebuild' or 'package version' are used when this meaning is
+intended. This distinction is important.
 
 
 
@@ -41,8 +41,8 @@ The different levels of keyword are:
 arch (x86, ppc-macos) ("stable")
   
   
-Both the package version and the ebuild are widely tested, known to 
work
-and not have any serious issues on the indicated platform.
+Both the package version and the ebuild are widely tested, known to
+work and not have any serious issues on the indicated platform.
   
   
 ~arch (~x86, ~ppc-macos) ("testing")
@@ -72,9 +72,10 @@ The different levels of keyword are:
 
 
 
-The -* 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 ppc and x86 might use:
+The -* 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 ppc and x86 might
+use:
 
 
 
@@ -103,23 +104,23 @@ do not specify a KEYWORDS variable.
 
 
 
-An ebuild must not depend upon any package that is of a lower keyword 
level
-than itself. For example, if foo-1.2 depends upon bar-1.2, and
-bar-1.2 is ~x86, then foo-1.2 must not be marked 
stable on
-x86 unless bar-1.2 is also stabilised.
+An ebuild must not depend upon any package that is of a lower keyword
+level than itself. For example, if foo-1.2 depends upon bar-1.2,
+and bar-1.2 is ~x86, then foo-1.2 must not be 
marked
+stable on x86 unless bar-1.2 is also stabilised.
 
 
 
-You may assume that if a user accepts ~arch for a given arch then they 
also
-accept arch.
+You may assume that if a user accepts ~arch for a given arch then they
+also accept arch.
 
 
 
-For optional dependencies, all possible dependencies must satisfy the 
above.
-Note that certain USE flags can be forcibly disabled on a per-profile 
basis
- talk to the arch teams if you require this. For either-or dependencies, 
at
-least one of the options must be of equal or better visibility than the
-package in question.
+For optional dependencies, all possible dependencies must satisfy the
+above. Note that certain USE flags can be forcibly disabled on a
+per-profile basis  talk to the arch teams if you require this. For
+either-or dependencies, at least one of the options must be of equal or
+better visibility than the package in question.
 
 
 
@@ -139,10 +140,10 @@ packages.
 
 
 The only time it is acceptable for a user to see the Possibly a DEPEND
-problem error message is if they have manually changed visibility levels 
for a
-package (for example, through /etc/portage/) and have missed a 
dependency.
-You should never commit a change which could cause this error to appear on a
-user system.
+problem error message is if they have manually changed visibility levels 
for
+a package (for example, through /etc/portage/) and have missed a
+dependency. You should never commit a change which could cause this error to
+appear on a user system.
 
 
 
@@ -162,12 +163,12 @@ a keywording bug instead for non-amd64/x86.
 
 
 Do not assume that your package works on all architectures. Do 
not
-assume that user submitted ebuilds will have correct KEYWORDS  
chances are
-they just copied from somewhere else. Do not assume that upstream's
-'supported architectures' list is correct. Do not 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 vim script which only worked on
-x86).
+assume that user submitted ebuilds will have correct KEYWORDS 
+chances are they just copied from somewhere else. Do not assume that
+upstream's 'supported architectures' list is correct. Do not assume that
+because your code is written in Perl / Python / Java / whatever that it will 
run
+on 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: ee137375b92144471e3ed389b23550c4b8068a72
Author: Florian Schmaus  gentoo  org>
AuthorDate: Fri Jul 16 08:54:37 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Fri Jul 16 09:11:09 2021 +
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  gentoo.org>
Signed-off-by: Ulrich Müller  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  when you are filing the stabilization bug  please
-add the keyword ALLARCHES in addition to STABLEREQ and CC the
-arches that you would like to stabilize.
+add the keyword ALLARCHES and CC the arches that you would like to
+stabilize.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 81b5355bb0af54e378abefb5915aa21357f5a809
Author: Sam James  gentoo  org>
AuthorDate: Sat Apr 10 01:18:07 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Sat Jul  3 16:18:07 2021 +
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  gentoo.org>
Signed-off-by: Ulrich Müller  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 - sanity-check, so please fix this if it 
occurs  or ask for
 help to do so.
 
 
+
+In addition, if you are changing the package list of a bug after it has been
+processed,  i.e. after NATTkA has CCed arches  you should un-CC all
+arches so that NATTkA CCs the new correct set of arches.
+
+
 
 Note that sometimes NATTkA may do nothing if it has concluded the 
package
 list is complete. You may wish to run nattka sanity-check BUG where

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 147d70669db90455ee801244c75383651b9ce2da
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 09:01:41 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:13 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=147d7066

keywording: convert 'Stabilization rules' into a list

Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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.
 Stabilization rules
 
 
-
-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
-https://wiki.gentoo.org/wiki/Project:AMD64/32-bit_Chroot_Guide;>
-specialized environment on amd64.
-
+
+  
+ 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
+ https://wiki.gentoo.org/wiki/Project:AMD64/32-bit_Chroot_Guide;>
+ specialized environment on amd64.
+  
 
-
-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.
-
+  
+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.
+  
 
-
-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.
-
+  
+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.
+  
+
 
 
 Exotic architectures (like hppa, ia64, ppc*, sparc)

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 5415582aaa5845c3b71501f92ad8e547bd1c0c30
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 08:58:33 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:13 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5415582a

keywording: expound on NATTkA importance and HOWTO

Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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.
 
 
+
+It is strongly
+https://archives.gentoo.org/gentoo-dev/message/cd62f6be924f6a0f76b68a07d33b256a;>
+recommended that NATTkA 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.
+
+
+
+NATTkA will set the sanity-check field on Bugzilla to either
+- or + 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 - sanity-check, so please fix this if it occurs  or ask for
+help to do so.
+
+
+
+Note that sometimes NATTkA may do nothing if it has concluded the 
package
+list is complete. You may wish to run nattka sanity-check BUG where
+BUG is the bug number you're having an issue with in order to debug the
+issue to receive verbose output.
+
+
+
+You may wish to read NATTkA's
+https://github.com/mgorny/nattka#filing-keywordingstabilization-bugs;>
+documentation for help on package list syntax or other information about
+the tool. The documentation details syntax which can be used, such as *
+to represent 'all previously stable arches', or '^' to copy the arches from the
+line(s) above.
+
+
 
 For an ebuild to move to stable, the following guidelines must be met
 (see https://www.gentoo.org/glep/glep-0040.html;>GLEP 40

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 48cd0bf726e676abf333e186c7632e5eb8323390
Author: Sam James  gentoo  org>
AuthorDate: Mon Mar 29 22:27:05 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:15 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=48cd0bf7

keywording: s/archs/arches/

Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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:
 
 
 The -* 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 ppc and x86 might use:
 
 
@@ -82,9 +82,9 @@ KEYWORDS="-* ppc x86"
 
 
 
-This is different in implication from "ppc x86"  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 "ppc x86"  the former implies
+that it will not work on other arches, whereas the latter implies that it has
+not been tested.
 
 
 
@@ -166,12 +166,12 @@ assume that user submitted ebuilds will have correct 
KEYWORDS  chanc
 they just copied from somewhere else. Do not assume that upstream's
 'supported architectures' list is correct. Do not 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 vim script which only worked on
+arches (there is at least one case of a vim script which only worked on
 x86).
 
 
 
-Note that most (non-amd64/x86) archs expect you to be on the
+Note that most (non-amd64/x86) 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 mips, 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.
 NATTkA will set the sanity-check field on Bugzilla to either
 - or + 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 - sanity-check, so please fix this if it occurs  or ask for
 help to do so.
@@ -292,8 +292,8 @@ You may wish to read NATTkA's
 https://github.com/mgorny/nattka#filing-keywordingstabilization-bugs;>
 documentation for help on package list syntax or other information about
 the tool. The documentation details syntax which can be used, such as *
-to represent 'all previously stable arches', or '^' to copy the arches from the
-line(s) above.
+to represent "all previously stable arches", or ^ to copy the arches
+from the line(s) above.
 
 
 
@@ -447,7 +447,7 @@ any given keyword level on any profile. The aim here is:
 
 
 
-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.
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 5df4e789f27b792b785620802cb6376c2f675b83
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 08:48:28 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:12 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5df4e789

keywording: add nuance about first-time ALLARCHES stabilisations

Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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.
 
 
+
+Note that first-time ALLARCHES stabilizations are done "as normal" 
+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 ALLARCHES in
+bugs, but instead let NATTkA set it automatically based on metadata.xml.
+
+
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 34957441bbcce538d388c262ec53b34d0d8ddcc5
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 05:25:39 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:10 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=34957441

keywording: minor grammar/phrasing changes

Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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 vim script 
which only worked on
 
 
 
-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 mips, for 
example,
-there are multiple ABIs and byte orders to consider  a package working on 
your
-o32 box may not work on o64 or n32). Contact the 
individual arch
-teams for details.
+Note that most (non-amd64/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 mips, for example, there are multiple ABIs and byte orders to
+consider  a package working on your o32 box may not work on
+o64 or n32). Contact the individual arch teams for details.
 
 
 
-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 alpha, ia64,
+s390, sparc, hppa, ppc*) 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.
 
 
 
@@ -253,8 +253,8 @@ teams to the CC list. They can do it manually, or they can 
fill the package
 list field, add the CC-ARCHES keyword, and let
 https://dev.gentoo.org/~mgorny/doc/nattka/;>NATTkA
 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.
 
 
 
@@ -290,7 +290,7 @@ for further details):
 
 For security fixes, the "reasonable amount of time" guideline may be relaxed.
 See the https://www.gentoo.org/support/security/vulnerability-treatment-policy.html;>
-Vulnerability Treatment Policy
+Vulnerability Treatment Policy.
 
 
 
@@ -303,9 +303,9 @@ Vulnerability Treatment Policy
 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 x86 using a
 https://wiki.gentoo.org/wiki/Project:AMD64/32-bit_Chroot_Guide;>
-specialized environment on amd64.
+specialized environment on amd64.
 
 
 
@@ -321,15 +321,15 @@ the team can keep an eye out for possible keywording 
mistakes.
 
 
 
-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 hppa, ia64, ppc*, sparc)
+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).
 
 
 
-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 mips, riscv) do not maintain a stable
+keyword, so packages are not to be marked stable for one of these 
architectures.
 
 
 
@@ -341,7 +341,7 @@ 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
+Python, ...), then you may request that your package be stabilized on all 
arches
 at once. To do this  when you are filing the stabilization bug  please
 add the keyword ALLARCHES in addition to STABLEREQ and CC the
 arches that you would like to stabilize.

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 596cd2dec06268d8e03971ee41e58b8b974e43ac
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 09:06:08 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:14 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=596cd2de

keywording: add arm/arm64 policy for keywording/stablization

Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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.
  specialized environment on amd64.
   
 
+  
+arm, arm64: These teams have a strict policy on passing
+testsuites. You must run test suites for packages with e.g.
+FEATURES=test 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.
+  
+
   
 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

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: aca4e12789394f7e2b6af34ef3f3dc68d79065d5
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 08:45:25 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:11 2021 +
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  gentoo.org>
Signed-off-by: Ulrich Müller  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 not use the * or ~* special keywords 
in ebuilds.
 
 Usually, "live" ebuilds
 (see )
-do not specify a KEYWORDS variable, or assign the empty string to it.
+do not specify a KEYWORDS variable.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 0b9aa967db85539baad1903c8c681a963e1765ec
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 09:12:19 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:14 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=0b9aa967

keywording: add QA policy link for dropped keywords

Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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 KEYWORDS which are causing
 problems and CC the relevant architectures on the bug  you must file
-a new bug to the architecture in question regarding this if no bug is already
-available.
+a https://projects.gentoo.org/qa/policy-guide/keywords.html#pg0401;>
+new bug to the architecture in question regarding this if no bug is
+already available.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: acfc48b80657c6221e1a4000ec046c65cd72fcc6
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 05:18:18 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:09 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=acfc48b8

keywording: call ~arch ("testing") and arch ("stable")

Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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:
 
 
   
-arch (x86, ppc-macos)
+arch (x86, ppc-macos) ("stable")
   
   
 Both the package version and the ebuild are widely tested, known to 
work
 and not have any serious issues on the indicated platform.
   
   
-~arch (~x86, ~ppc-macos)
+~arch (~x86, ~ppc-macos) ("testing")
   
   
 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 arch.
   
   
-No keyword
+No keyword ("unkeyworded")
   
   
 If a package has no keyword for a given arch, it means it is not known
@@ -153,7 +153,7 @@ user system.
 
 
 
-New packages should be marked as ~arch only upon
+New packages should be marked as ~arch ("testing") only upon
 architectures for which the committing developer has tested.
 
 
@@ -185,7 +185,7 @@ keyworded.
 
 
 
-Do not commit straight to arch.
+Do not commit straight to arch ("stable").
 
 
 
@@ -196,10 +196,10 @@ Do not commit straight to arch.
 
 
 
-When upgrading, drop all existing keywords from arch to ~arch, 
and leave
-any existing ~arch keywords intact. This must be done even if you 
think
-you're just making a trivial fix  there have been several examples of the
-stable tree getting broken this way.
+When upgrading, drop all existing keywords from arch to ~arch
+("testing"), and leave any existing ~arch keywords intact. This must be
+done even if you think you're just making a trivial fix  there have
+been several examples of the stable tree getting broken this way.
 
 
 
@@ -237,10 +237,11 @@ to do this.
 
 
 
-Stabilization, i.e., moving an ebuild from ~arch to arch, 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 
-the arch teams are happy for help, so long as they know what is going on.
+Stabilization, i.e., moving an ebuild from ~arch ("testing") to
+arch ("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  the arch teams are happy for help, so long as they
+know what is going on.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 1f5f72e47dde3fae29ed9cd96ada00902cc9a395
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 05:26:58 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:10 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=1f5f72e4

keywording: make clear automatically CCing arches is preferred

Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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 CC-ARCHES keyword, and let
 https://dev.gentoo.org/~mgorny/doc/nattka/;>NATTkA
-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.
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 0da552c23c04072e728dd83ffe3a34903b64f481
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 08:44:46 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Apr  7 17:35:11 2021 +
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  gentoo.org>
Signed-off-by: Ulrich Müller  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.
 
 
 New packages should be marked as ~arch ("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  better yet  ask them to file
+a keywording bug instead for non-amd64/x86.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: fb5642b982abe07a3a215e39ca315ae2b5553e68
Author: Sam James  gentoo  org>
AuthorDate: Sun Mar 21 04:35:28 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Tue Mar 30 16:00:53 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=fb5642b9

keywording: mention pkgdev as an alternative to repoman

Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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.
 
 
 If there are no new dependencies, do not remove keywords if your commit fails
-with repoman  please try a full git pull and if you still have
-problems, then commit with repoman -I and file a bug to the broken
-architecture, noting it in your git commit message.
+with repoman or pkgdev  instead please commit with
+repoman -I and file a bug to the broken architecture, noting it in your
+git commit message.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 3fbb9af3ba7e5e617dca6559108d757d587e07b2
Author: Joonas Niilola  gentoo  org>
AuthorDate: Thu Mar 11 12:59:47 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Thu Mar 11 13:11:38 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=3fbb9af3

keywording: use  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  gentoo.org>
Signed-off-by: Ulrich Müller  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.
 
 
 If your package is architecture-independent, you should add the
-stabilize-allarches tag to metadata.xml. This allows consistency
+stabilize-allarches/ tag to metadata.xml. This allows 
consistency
 in future stabilizations and saves arch teams considerable work.
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/, general-concepts/virtuals/, ebuild-writing/using-eclasses/, ...

[Ulrich Müller]

commit: 2a5a27dcf9a014fcf8fe6f04420ec26ed3c9085a
Author: Sam James  gentoo  org>
AuthorDate: Mon Feb 15 07:49:16 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Feb 17 09:29:46 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=2a5a27dc

*/*: Use modern example of a prefix arch/keyword

Gentoo/OpenBSD and Gentoo/FreeBSD are gone, but
we still have Prefix which has some arches
like ~x64-macos, so let's use that to keep
the same level of variety.

Closes: https://github.com/gentoo/devmanual/pull/190
Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  gentoo.org>

 ebuild-writing/using-eclasses/text.xml | 2 +-
 ebuild-writing/variables/text.xml  | 4 ++--
 general-concepts/virtuals/text.xml | 2 +-
 keywording/text.xml| 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/ebuild-writing/using-eclasses/text.xml 
b/ebuild-writing/using-eclasses/text.xml
index 9d5f64c..943e92d 100644
--- a/ebuild-writing/using-eclasses/text.xml
+++ b/ebuild-writing/using-eclasses/text.xml
@@ -45,7 +45,7 @@ SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="alpha ~amd64 ~x86 ~x86-fbsd"
+KEYWORDS="alpha ~amd64 ~x86 ~x64-macos"
 
 RDEPEND="sys-libs/ncurses:0=
=sys-libs/readline:0="

diff --git a/ebuild-writing/variables/text.xml 
b/ebuild-writing/variables/text.xml
index 058f466..b6cebb3 100644
--- a/ebuild-writing/variables/text.xml
+++ b/ebuild-writing/variables/text.xml
@@ -503,8 +503,8 @@ You need not assign the IUSE variable in your ebuild if it 
is empty.
 
 
 
-Arch USE flags (sparc, mips, x86-fbsd and so on) should 
not be
-listed.
+Arch USE flags (sparc, mips, x64-macos and so on) should
+not be listed.
 
 
 

diff --git a/general-concepts/virtuals/text.xml 
b/general-concepts/virtuals/text.xml
index 6ac5832..377933f 100644
--- a/general-concepts/virtuals/text.xml
+++ b/general-concepts/virtuals/text.xml
@@ -28,7 +28,7 @@ EAPI=7
 
 DESCRIPTION="Virtual for C++ tr1 type_traits"
 SLOT="0"
-KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 ~s390 sparc x86 ~x86-fbsd"
+KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 ~s390 sparc x86 ~x64-macos"
 
 RDEPEND="|| ( =sys-devel/gcc-4.1 dev-libs/boost )"
 

diff --git a/keywording/text.xml b/keywording/text.xml
index 391f2d6..1c5f71d 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -14,7 +14,7 @@ distinction is important.
 
 Most ebuilds specify a KEYWORDS variable. This variable is used to
 indicate the suitability and stability of both the package and the ebuild on
-each given arch (sparc, ppc, x86-obsd, ...).
+each given arch (sparc, ppc, x64-macos, ...).
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: dfae932454e5f59ac7985c0fe6475de5dca7a656
Author: Sam James  gentoo  org>
AuthorDate: Sun Feb 14 20:12:04 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Feb 17 09:20:24 2021 +
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  gentoo.org>
Signed-off-by: Ulrich Müller  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
 
 
 
-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.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 6d1fffbccb1675783eb758ba1b2ba60e7e976ed4
Author: Sam James  gentoo  org>
AuthorDate: Mon Feb 15 07:03:28 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Feb 17 09:29:44 2021 +
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  gentoo.org>
Signed-off-by: Sam James  gentoo.org>
Signed-off-by: Ulrich Müller  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
 
 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
+https://wiki.gentoo.org/wiki/Project:AMD64/32-bit_Chroot_Guide;>
+specialized environment on amd64.
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: de435d26ee4d040969db12d59ff103e8b7cd75a6
Author: Sam James  gentoo  org>
AuthorDate: Sun Feb 14 20:18:37 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Feb 17 09:29:45 2021 +
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  gentoo.org>
Signed-off-by: Ulrich Müller  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 ALLARCHES in addition to 
STABLEREQ and CC the
 arches that you would like to stabilize.
 
 
+
+If your package is architecture-independent, you should add the
+stabilize-allarches tag to metadata.xml. This allows consistency
+in future stabilizations and saves arch teams considerable work.
+
+
 
 The arch teams, when encountering the ALLARCHES keyword, should perform
 their usual set of tests on a single convenient architecture. Then, if

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 2ad7f77460baef02015ca41032bc86896c9a3a1f
Author: Sam James  gentoo  org>
AuthorDate: Sun Feb 14 20:14:58 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Wed Feb 17 09:29:44 2021 +
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  gentoo.org>
Signed-off-by: Ulrich Müller  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.
 
 
 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  when you are filing the stabilization bug  please
 add the keyword ALLARCHES in addition to STABLEREQ and CC the
 arches that you would like to stabilize.

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 5914e1444dccfb9229bd5f7973070dc825a621c8
Author: Ulrich Müller  gentoo  org>
AuthorDate: Mon Feb 15 07:20:25 2021 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Mon Feb 15 07:20:25 2021 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5914e144

keywording: Fix coding style

Fixes: 9c2e6f500a276b974bc2e2bd476d8423f113dbb2
Signed-off-by: Ulrich Müller  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.
 
 
 Simultaneous stabilization on all architectures
-  
-
-  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  when
-  you are filing the stabilization bug  please add the keyword
-  ALLARCHES in addition to STABLEREQ and CC the
-  arches that you would like to stabilize.
-
-
-
-  The arch teams, when encountering the ALLARCHES 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.
-
-  
+
+
+
+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  when you are filing the stabilization bug  please
+add the keyword ALLARCHES in addition to STABLEREQ and CC the
+arches that you would like to stabilize.
+
+
+
+The arch teams, when encountering the ALLARCHES 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.
+
+
+
 
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 3cbde132b6b28dcaf4ae591c567b6828e4fc7688
Author: Alexey Sokolov  google  com>
AuthorDate: Fri Jun 26 14:03:30 2020 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Sun Jul 12 18:31:43 2020 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=3cbde132

keywording: Mention NATTkA

Signed-off-by: Alexey Sokolov  google.com>
Signed-off-by: Ulrich Müller  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.
 
 
 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 CC-ARCHES keyword, and let
+https://dev.gentoo.org/~mgorny/doc/nattka/;>NATTkA
+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.
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 0549711de12b5fac535118c49a2df8c2b7b966f1
Author: Ulrich Müller  gentoo  org>
AuthorDate: Sat May  2 19:35:27 2020 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Sat May  2 19:35:27 2020 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=0549711d

keywording: SuperH is gone.

Signed-off-by: Ulrich Müller  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.
 
 
 
-   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.
 
 
-
 
 Do not commit straight to arch.
 

[gentoo-commits] proj/devmanual:master commit in: keywording/, ebuild-maintenance/stabilization/, ebuild-maintenance/

[Ulrich Müller]

commit: 449da7f72272a7f3c4b5c5a2761151fc553d7338
Author: Ulrich Müller  gentoo  org>
AuthorDate: Thu Jan 23 16:54:18 2020 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Sat Jan 25 05:53:21 2020 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=449da7f7

keywording: Include sections about stabilization.

Remove the ebuild-maintenance/stabilization section (which resulted
from the split of ebuild-maintenance/maintenance-tasks), and include
it in keywording. Delete duplicate and outdated information.

Closes: https://bugs.gentoo.org/648316
Signed-off-by: Ulrich Müller  gentoo.org>

 ebuild-maintenance/stabilization/text.xml | 119 --
 ebuild-maintenance/text.xml   |   1 -
 keywording/text.xml   |  83 +
 3 files changed, 69 insertions(+), 134 deletions(-)

diff --git a/ebuild-maintenance/stabilization/text.xml 
b/ebuild-maintenance/stabilization/text.xml
deleted file mode 100644
index b67c2b5..000
--- a/ebuild-maintenance/stabilization/text.xml
+++ /dev/null
@@ -1,119 +0,0 @@
-
-
-
-Stabilizing and Upgrading Ebuilds
-
-
-Stabilizing ebuilds
-
-
-
-Only architecture maintainers for a given architecture should mark packages as
-stable on that architecture. The maintainer of the package should always be
-contacted just in case there are reasons not to do so. The exception to this
-is if you are part of an architecture team, in which case you may mark the
-package stable for that architecture. If you are not part of an architecture
-team, you should consult the guidelines below; if the architecture you are
-looking for is not listed then please consult the relevant lead.
-
-
-
-You should never stabilize packages on architectures for which you
-cannot test and instead you should file a bug to the relevant architecture
-team, such as sp...@gentoo.org asking them to stabilize the ebuild.
-Alternatively, you may be able to find Gentoo developers on IRC who could help
-you with your request.
-
-
-
-It is best to not use arch-maintain...@gentoo.org, adding architecture
-teams onto a bug's CC list individually instead. 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.
-
-
-
-
-
-
-Stabilization rules
-
-
-
-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.
-
-
-
-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.
-
-
-
-Exotic architectures (like alpha, ia64, sparc, hppa, ppc*) are short
-on manpower, so it's best if you avoid opening stabilization bugs for
-them unless it is absolutely necessary (eg, a reverse dependency for
-your package). More about keywording policies can be found in the
-keywording section.
-
-
-
-Some architectures (like m68k, mips, s390, sh) do not maintain a
-stable keyword. So there is no use in marking a package stable for one
-of these architectures.
-
-
-
-
-
-
-Upgrading ebuilds
-
-
-
-New ebuilds should rarely go in with "arch" keywords and even if they do
-not, the package must be tested on any architectures listed in the
-KEYWORDS variable of the new ebuild.
-
-
-
-Exceptions to the no "arch" rule are major bug fixes, or
-security fixes. If the previous version of the ebuild
-contains KEYWORDS which you cannot test for, you should
-downgrade them: turn any "arch" keyword to "~arch". If you
-think that your package may not work at all even on "~arch"
-then it is best to leave the keyword out and request testing from the
-relevant team: if you are to do this, you must file a bug to the team
-in question.
-
-
-
-If a new version introduces new dependencies which are not available
-on some architectures, then you should file a bug or ask on IRC before
-you upgrade the package. If you really need to get the ebuild added in
-a hurry, for example, for a security fix, then you should drop
-any KEYWORDS which are causing problems and CC the relevant
-architectures on the bug  you should file a new bug to the
-architecture in question regarding this if no bug is already
-available.
-
-
-
-If there are no new dependencies, do not remove keywords if your
-commit fails with repoman  please try a full git pull and if
-you still have problems, then commit with repoman -I and file a
-bug to the broken architecture, noting it in your git commit message.
-
-
-
-When committing, make sure that you reference any bugs in the
-commit message. Failing to do so is considered
-to be in very poor taste and may result in disciplinary action.
-
-
-
-
-
-

diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index 6c8d562..3576fbc 100644
--- 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: b696fdc696574cd1fec19ff572c951c464fe10be
Author: Tom Wijsman  gentoo  org>
AuthorDate: Tue May 13 00:52:15 2014 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Sat Jan 25 05:53:46 2020 +
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  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
 Stabilization rules
 
 
+
+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.
+
+
 
 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

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 39f82639c14734efb1a8638952e17984b38a0023
Author: Ulrich Müller  gentoo  org>
AuthorDate: Thu Jan 23 13:10:50 2020 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Thu Jan 23 13:10:50 2020 +
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  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.
 
 
 
-Moving a package from ~arch to arch is done only by the relevant 
arch teams.
+Moving an ebuild from ~arch to arch 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  the arch teams are happy for help, so 
long as
 they know what is going on. Please note that x86 is now no longer an 
exception
@@ -232,25 +232,26 @@ for further details.
 
 
 
-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:
 
 
 
   
-The package has spent a reasonable amount of time in ~arch 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 ~arch 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.
   
   
-The package must not have any non-arch dependencies.
+The ebuild must not have any non-arch dependencies.
   
   
-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.
   
   
-The package must be widely tested.
+The package version must be widely tested.
   
   
 If the package is a library, it should be known not to break any package 
which

[gentoo-commits] proj/devmanual:master commit in: keywording/, archs/alpha/, appendices/contributing/, archs/amd64/, ...

[Ulrich Müller]

commit: c57839caf2608ddda43a6ee5c3b9474784218134
Author: Ulrich Müller  gentoo  org>
AuthorDate: Fri Jan 10 09:44:44 2020 +
Commit: Ulrich Müller  gentoo  org>
CommitDate: Fri Jan 10 09:44:44 2020 +
URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=c57839ca

Update redirected links.

Signed-off-by: Ulrich Müller  gentoo.org>

 appendices/contributing/text.xml| 2 +-
 archs/alpha/text.xml| 4 ++--
 archs/amd64/text.xml| 2 +-
 archs/ppc/text.xml  | 2 +-
 ebuild-writing/common-mistakes/text.xml | 2 +-
 keywording/text.xml | 2 +-
 6 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/appendices/contributing/text.xml b/appendices/contributing/text.xml
index d17205a..d7e7003 100644
--- a/appendices/contributing/text.xml
+++ b/appendices/contributing/text.xml
@@ -45,7 +45,7 @@ For current Gentoo developers, access is at
 Non-developers can clone the repository by typing
 git clone git://anongit.gentoo.org/proj/devmanual.git.
 The sources are also hosted on
-https://github.com/gentoo/devmanual.gentoo.org;>GitHub
+https://github.com/gentoo/devmanual;>GitHub
 for those who prefer to submit patches using pull requests.
 
 

diff --git a/archs/alpha/text.xml b/archs/alpha/text.xml
index c52e080..e294166 100644
--- a/archs/alpha/text.xml
+++ b/archs/alpha/text.xml
@@ -142,10 +142,10 @@ The Alpha team can be contacted:
 https://wiki.gentoo.org/wiki/Project:Alpha;>Gentoo Linux Alpha 
Development Project
   
   
-https://www.gentoo.org/doc/en/gentoo-alpha-faq.xml;>Gentoo/Alpha FAQ
+https://wiki.gentoo.org/wiki/Alpha/FAQ;>Gentoo/Alpha FAQ
   
   
-https://www.gentoo.org/proj/en/base/alpha/doc/alpha-porting-guide.xml;>Alpha
 Porting Guide
+https://wiki.gentoo.org/wiki/Project:Alpha/Porting_guide;>Alpha 
Porting Guide
   
   
 https://forums.gentoo.org/viewforum-f-32.html;>Gentoo on 
Alternative Architectures Forum

diff --git a/archs/amd64/text.xml b/archs/amd64/text.xml
index 4e9919a..73264df 100644
--- a/archs/amd64/text.xml
+++ b/archs/amd64/text.xml
@@ -582,7 +582,7 @@ segmentation faults or strange behaviour. GCC 4.0 refuses 
to compile such code.
 https://wiki.gentoo.org/wiki/Project:AMD64;>Gentoo/AMD64 
Project
   
   
-https://www.gentoo.org/doc/en/gentoo-amd64-faq.xml;>Gentoo/Linux AMD64 
FAQ
+https://wiki.gentoo.org/wiki/AMD64/FAQ;>Gentoo/Linux AMD64 
FAQ
   
   
 https://forums.gentoo.org/viewforum-f-46.html;>Gentoo on AMD64 
Forum

diff --git a/archs/ppc/text.xml b/archs/ppc/text.xml
index 837a526..fc449bf 100644
--- a/archs/ppc/text.xml
+++ b/archs/ppc/text.xml
@@ -93,7 +93,7 @@ The PowerPC team can be reached by:
 
 
   
-https://www.gentoo.org/doc/en/gentoo-ppc-faq.xml;>Gentoo PPC 
FAQ
+https://wiki.gentoo.org/wiki/PPC/FAQ;>Gentoo PPC FAQ
   
   
 https://forums.gentoo.org/viewforum-f-24.html;>Gentoo PPC 
Forums

diff --git a/ebuild-writing/common-mistakes/text.xml 
b/ebuild-writing/common-mistakes/text.xml
index 9cd998c..a133037 100644
--- a/ebuild-writing/common-mistakes/text.xml
+++ b/ebuild-writing/common-mistakes/text.xml
@@ -157,7 +157,7 @@ GCC can turn any specific warning into an error. A specific 
-Werror flag would b
 
 Removing "-Werror" from configure.ac can cause breakage in very rare
 cases where the configure phase relies on the exit code. See
-https://sourceforge.net/tracker/?func=detailaid=2959749group_id=204462atid=989708;>
+https://sourceforge.net/p/open-vm-tools/tracker/81/;>
 app-emulation/open-vm-tools bug. But even then we remove it from
 the resulting Makefile.
 

diff --git a/keywording/text.xml b/keywording/text.xml
index d3c5ea4..2b25a0e 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -260,7 +260,7 @@ For a package to move to stable, the following guidelines 
must be met:
 
 
 For security fixes, the "reasonable amount of time" guideline may be relaxed.
-See the https://www.gentoo.org/security/en/vulnerability-policy.xml;>
+See the https://www.gentoo.org/support/security/vulnerability-treatment-policy.html;>
 Vulnerability Treatment Policy
 
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Göktürk Yüksek]

commit: cd0550900d2461ceef2ad82da9371309a49131be
Author: Mikle Kolyada  gentoo  org>
AuthorDate: Thu Jul 19 22:46:11 2018 +
Commit: Göktürk Yüksek  gentoo  org>
CommitDate: Mon Aug 27 15:23:54 2018 +
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 KEYWORDS entry might look like:
 
 
 
-KEYWORDS="x86 sparc ~mips ~ppc ~ppc-macos -ia64"
+KEYWORDS="-ia64 ~mips ~ppc sparc x86 ~ppc-macos"
 
 
 
@@ -82,15 +82,15 @@ The different levels of keyword are:
 
 The -* 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 x86 and ppc might use:
+which is only supported upstream on ppc and x86 might use:
 
 
 
-KEYWORDS="-* x86 ppc"
+KEYWORDS="-* ppc x86"
 
 
 
-This is different in implication from "x86 ppc"  the former 
implies that
+This is different in implication from "ppc x86"  the former 
implies that
 it will not work on other archs, whereas the latter implies that it has not 
been
 tested.
 

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Ulrich Müller]

commit: 1362d6608c323241ad1a4d0313046e99407ef352
Author: Ulrich Müller ulm AT gentoo DOT org
AuthorDate: Thu May 21 16:37:11 2015 +
Commit: Ulrich Müller ulm AT gentoo DOT org
CommitDate: Mon Jun  1 18:55:39 2015 +
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 cKEYWORDS/c variable. This variable is used to
+Most ebuilds specify a cKEYWORDS/c variable. This variable is used to
 indicate the suitability and stability of both the package and the ebuild on
 each given arch (csparc/c, cppc/c, cx86-obsd/c, ...).
 /p
@@ -99,6 +99,12 @@ tested.
 Do bnot/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 cKEYWORDS/c variable, or assign the empty string to it.
+/note
+
 section
 titleEqual Visibility Requirement/title
 body

[gentoo-commits] proj/devmanual:master commit in: keywording/

[Markos Chandras]

commit: 9c2e6f500a276b974bc2e2bd476d8423f113dbb2
Author: Michael Orlitzky mjo AT gentoo DOT org
AuthorDate: Thu Mar 12 13:29:40 2015 +
Commit: Markos Chandras hwoarang AT gentoo DOT org
CommitDate: Sat Mar 14 09:18:46 2015 +
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 thisd /when
+  you are filing the stabilization bugd /please add the keyword
+  cALLARCHES/c in addition to cSTABLEREQ/c and CC the
+  arches that you would like to stabilize.
+/p
+
+p
+  The arch teams, when encountering the cALLARCHES/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
 titleRemoving Package Versions/title
 body