[gentoo-dev] [PATCH v3 0/9] GLEP 72 (arches.desc) revival

[gentoo-dev] [PATCH v3 0/9] GLEP 72 (arches.desc) revival

[Michał Górny]

Hi,

Changes in v3:
- fixed commit message
- updated license

Michał Górny (9):
  glep-0072: Remove redundant 'broken' status
  glep-0072: Rename bad depgraph state to 'transitional'
  glep-0072: Use 'testing' for pure ~arch
  glep-0072: Remove weird third column from example
  glep-0072: Update initial values
  glep-0072: Combine and amend description of states
  glep-0072: Explicitly cover file not existing case
  glep-0072: Move 'overlays' to spec, and change behavior
  glep-0072: Update metadata

 glep-0072.rst | 126 +++++++++++++++++++++++---------------------------
 1 file changed, 57 insertions(+), 69 deletions(-)

-- 
2.26.0

[gentoo-dev] [PATCH v3 1/9] glep-0072: Remove redundant 'broken' status

[Michał Górny]

This is really no different from marking the profiles exp, and there
seems no value in having this controlled in two places.

Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 glep-0072.rst | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/glep-0072.rst b/glep-0072.rst
index 61f9c16..0a9914b 100644
--- a/glep-0072.rst
+++ b/glep-0072.rst
@@ -91,8 +91,7 @@ are ignored.  Every blank line is ignored. Otherwise the file consists of two
 whitespace-separated columns:
 
 - first column: architecture name (keyword)
-- second column: one of the four values ``stable``, ``testing``, ``unstable``,
-  ``broken``
+- second column: one of the three values ``stable``, ``testing``, ``unstable``
 
 Additional columns are ignored to allow for future revisions of this document.
 
@@ -146,11 +145,6 @@ as an error and aborts. Consistency is only tested for ``~arch``.
 Which profiles of the arch are tested is still controlled by profiles.desc
 (and ``-d`` / ``-e`` switches).
 
-broken
-~~~~~~
-Repoman is not testing any profiles of this architecture, irrespective
-of the settings in profiles.desc.
-
 Meaning of the values for other tools
 -------------------------------------
 
-- 
2.26.0

[gentoo-dev] [PATCH v3 2/9] glep-0072: Rename bad depgraph state to 'transitional'

[Michał Górny]

In Gentoo terms, 'testing' and 'unstable' are mostly synonymous,
so using the two names for different purposes is confusing.  Use
'transitional' instead.

Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 glep-0072.rst | 25 +++++++++++++------------
 1 file changed, 13 insertions(+), 12 deletions(-)

diff --git a/glep-0072.rst b/glep-0072.rst
index 0a9914b..1e906d2 100644
--- a/glep-0072.rst
+++ b/glep-0072.rst
@@ -56,7 +56,7 @@ a) An architecture loses its stable status (imagine c128), but
    about a broken stable dependency tree. If we do that, repoman does however
    also not check ~c128 consistency, meaning that the ~c128 dependency tree
    will soon be broken as well due to negligence.  Given arches.conf as
-   described below, one could set the architecture c128 to "testing" status
+   described below, one could set the architecture c128 to "transitional" status
    and keep stable profiles. This results in stable keywords being ignored,
    but consistency of the ~c128 dependency tree is still enforced.
 
@@ -66,7 +66,7 @@ b) An architecture prepares for becoming a stable architecture (think arm64).
    as the stable dependency tree is not complete yet, the profiles need to be
    set to dev/exp, and again this brings the danger of the ~arm64 dependency
    tree getting inadvertently broken. Again the combination of setting the
-   architecture to "testing" in arches.desc and profiles to stable helps.
+   architecture to "transitional" in arches.desc and profiles to stable helps.
 
 Finally, at the moment the "semi-official" algorithm to figure out if an
 architecture is stable in the colloquial sense (e.g., requires stabilization
@@ -91,7 +91,8 @@ are ignored.  Every blank line is ignored. Otherwise the file consists of two
 whitespace-separated columns:
 
 - first column: architecture name (keyword)
-- second column: one of the three values ``stable``, ``testing``, ``unstable``
+- second column: one of the three values ``stable``, ``transitional``,
+  ``unstable``
 
 Additional columns are ignored to allow for future revisions of this document.
 
@@ -99,16 +100,16 @@ An example arches.desc file might look as follows::
 
     # Example arches.desc file
     amd64   stable
-    x86     stable     # not for long
+    x86     stable        # not for long
 
-    mips    testing
-    m68k    unstable   outdated
+    sparc   transitional
+    m68k    unstable      outdated
 
 Initial value in the gentoo repository
 --------------------------------------
 
 On introduction, the setting will be ``stable`` for all stable architectures,
-``testing`` for all architectures where "inofficial" stable keywords are
+``transitional`` for all architectures where "inofficial" stable keywords are
 maintained and are present in the repository by the arch teams (sh, s390,
 ...), and ``unstable`` everywhere else.
 
@@ -125,8 +126,8 @@ by profiles.desc (and ``-d`` / ``-e`` switches).
 This is the current behaviour and shall be the default if nothing is specified
 for an architecture.
 
-testing
-~~~~~~~
+transitional
+~~~~~~~~~~~~
 When a profile of an architecture is tested, then repoman treats ``arch``
 in ebuilds as ``~arch``, and tests consistency only for ``~arch``.
 
@@ -134,8 +135,8 @@ Which profiles of the arch are tested is still controlled by profiles.desc
 (and ``-d`` / ``-e`` switches).
 
 A new switch for repoman may be provided to temporarily upgrade
-an architecture from ``testing`` to ``stable`` status (for architecture team
-work).
+an architecture from ``transitional`` to ``stable`` status (for architecture
+team work).
 
 unstable
 ~~~~~~~~
@@ -170,7 +171,7 @@ arches.desc present and old system
 Utilities ignore the unknown file.
 
 Repoman and other tools may emit surplus dependency errors when profiles are
-checked on arches that are ``testing`` (they check the consistency
+checked on arches that are ``transitional`` (they check the consistency
 of the stable tree alone, which may fail, since ``arch`` is supposed to be
 treated like ``~arch``). This affects only development work and can be fixed
 by updating repoman.
-- 
2.26.0

[gentoo-dev] [PATCH v3 3/9] glep-0072: Use 'testing' for pure ~arch

[Michał Górny]

'Testing' has generally nicer meaning than 'unstable'.

Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 glep-0072.rst | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/glep-0072.rst b/glep-0072.rst
index 1e906d2..5be7941 100644
--- a/glep-0072.rst
+++ b/glep-0072.rst
@@ -92,7 +92,7 @@ whitespace-separated columns:
 
 - first column: architecture name (keyword)
 - second column: one of the three values ``stable``, ``transitional``,
-  ``unstable``
+  ``testing``
 
 Additional columns are ignored to allow for future revisions of this document.
 
@@ -103,7 +103,7 @@ An example arches.desc file might look as follows::
     x86     stable        # not for long
 
     sparc   transitional
-    m68k    unstable      outdated
+    m68k    testing       outdated
 
 Initial value in the gentoo repository
 --------------------------------------
@@ -111,7 +111,7 @@ Initial value in the gentoo repository
 On introduction, the setting will be ``stable`` for all stable architectures,
 ``transitional`` for all architectures where "inofficial" stable keywords are
 maintained and are present in the repository by the arch teams (sh, s390,
-...), and ``unstable`` everywhere else.
+...), and ``testing`` everywhere else.
 
 Meaning of the values for repoman
 ---------------------------------
@@ -138,8 +138,8 @@ A new switch for repoman may be provided to temporarily upgrade
 an architecture from ``transitional`` to ``stable`` status (for architecture
 team work).
 
-unstable
-~~~~~~~~
+testing
+~~~~~~~
 When a profile of an architecture is tested, then repoman treats ``arch``
 as an error and aborts. Consistency is only tested for ``~arch``.
 
-- 
2.26.0

[gentoo-dev] [PATCH v3 4/9] glep-0072: Remove weird third column from example

[Michał Górny]

While it should technically be ignored, I don't think it's a good idea
to encourage developers using it for their own purposes.

Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 glep-0072.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/glep-0072.rst b/glep-0072.rst
index 5be7941..acc5da7 100644
--- a/glep-0072.rst
+++ b/glep-0072.rst
@@ -103,7 +103,7 @@ An example arches.desc file might look as follows::
     x86     stable        # not for long
 
     sparc   transitional
-    m68k    testing       outdated
+    m68k    testing
 
 Initial value in the gentoo repository
 --------------------------------------
-- 
2.26.0

[gentoo-dev] [PATCH v3 5/9] glep-0072: Update initial values

[Michał Górny]

I'm not aware of any profiles that should be set to 'degraded', so let's
focus on the immediate problem of stable/testing.  It will also probably
make sense to wait before we start using the third state.

Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 glep-0072.rst | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/glep-0072.rst b/glep-0072.rst
index acc5da7..33a9578 100644
--- a/glep-0072.rst
+++ b/glep-0072.rst
@@ -108,10 +108,9 @@ An example arches.desc file might look as follows::
 Initial value in the gentoo repository
 --------------------------------------
 
-On introduction, the setting will be ``stable`` for all stable architectures,
-``transitional`` for all architectures where "inofficial" stable keywords are
-maintained and are present in the repository by the arch teams (sh, s390,
-...), and ``testing`` everywhere else.
+On introduction, the setting will be ``stable`` for all architectures using
+stable keywords, and ``testing`` for those that do not (``alpha``, ``mips``,
+``riscv``, Prefix profiles at the moment).
 
 Meaning of the values for repoman
 ---------------------------------
-- 
2.26.0

[gentoo-dev] [PATCH v3 6/9] glep-0072: Combine and amend description of states

[Michał Górny]

Provide a combined description for every status that explains what it
means, how it's used by linting tools and how it affects stabilization
requests.

Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 glep-0072.rst | 46 +++++++++++++++++++---------------------------
 1 file changed, 19 insertions(+), 27 deletions(-)

diff --git a/glep-0072.rst b/glep-0072.rst
index 33a9578..d3afaef 100644
--- a/glep-0072.rst
+++ b/glep-0072.rst
@@ -112,49 +112,41 @@ On introduction, the setting will be ``stable`` for all architectures using
 stable keywords, and ``testing`` for those that do not (``alpha``, ``mips``,
 ``riscv``, Prefix profiles at the moment).
 
-Meaning of the values for repoman
----------------------------------
+Meaning of the values
+---------------------
 stable
 ~~~~~~
-When a profile of an architecture arch is tested, then repoman checks
-consistency of the dependency tree for ``arch`` and for ``~arch`` separately.
+Stable means that the architecture is actively maintaning stable keywords.
+When dependency graphs of packages with stable keywords are tested, they
+are tested separately for ``arch`` and ``~arch`` systems.
 
-Which profiles of the architecture are tested is still controlled
-by profiles.desc (and ``-d`` / ``-e`` switches).
+Stable architectures are listed first in keyword-relevant contexts (``eshowkw``,
+Bugzilla) and developers are expected to file stabilization requests on these
+arches.
 
 This is the current behaviour and shall be the default if nothing is specified
 for an architecture.
 
 transitional
 ~~~~~~~~~~~~
-When a profile of an architecture is tested, then repoman treats ``arch``
-in ebuilds as ``~arch``, and tests consistency only for ``~arch``.
+Transitional means that the architecture does not maintain a consistent stable
+dependency graph but uses stable keywords on some packages.  When dependency
+graphs of packages with stable keywords are tested, they are tested only
+for ``~arch`` systems, i.e. stable keywords are ignored.
 
-Which profiles of the arch are tested is still controlled by profiles.desc
-(and ``-d`` / ``-e`` switches).
+Transitional architectures are generally listed after stable architectures,
+possibly mixed with testing.  Developers are not expected to file stabilization
+requests.
 
-A new switch for repoman may be provided to temporarily upgrade
+A new switch for linting tools may be provided to temporarily upgrade
 an architecture from ``transitional`` to ``stable`` status (for architecture
 team work).
 
 testing
 ~~~~~~~
-When a profile of an architecture is tested, then repoman treats ``arch``
-as an error and aborts. Consistency is only tested for ``~arch``.
-
-Which profiles of the arch are tested is still controlled by profiles.desc
-(and ``-d`` / ``-e`` switches).
-
-Meaning of the values for other tools
--------------------------------------
-
-All architectures with the value ``stable`` are considered as stable
-architectures, in the sense that
-
-- they require stabilization requests on bugzilla, which are handled
-  by an arch team
-- they may, e.g., be listed first by tools such as eshowkw
-- and similar, to the discretion of tool authors
+Testing means that the architecture does not use stable keywords at all.
+Presence of such keywords is considered an error.  Consistency is tested
+only for ``~arch``.
 
 
 Backwards Compatibility
-- 
2.26.0

[gentoo-dev] [PATCH v3 7/9] glep-0072: Explicitly cover file not existing case

[Michał Górny]

Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 glep-0072.rst | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/glep-0072.rst b/glep-0072.rst
index d3afaef..9ad8b61 100644
--- a/glep-0072.rst
+++ b/glep-0072.rst
@@ -96,6 +96,8 @@ whitespace-separated columns:
 
 Additional columns are ignored to allow for future revisions of this document.
 
+If the file does not exist, it is treated as if it were empty.
+
 An example arches.desc file might look as follows::
 
     # Example arches.desc file
-- 
2.26.0

[gentoo-dev] [PATCH v3 8/9] glep-0072: Move 'overlays' to spec, and change behavior

[Michał Górny]

Change the handling of slave repositories to the usual notion of 'slave
overrides master'.

Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 glep-0072.rst | 22 ++++++++++++++--------
 1 file changed, 14 insertions(+), 8 deletions(-)

diff --git a/glep-0072.rst b/glep-0072.rst
index 9ad8b61..68b8e91 100644
--- a/glep-0072.rst
+++ b/glep-0072.rst
@@ -150,6 +150,20 @@ Testing means that the architecture does not use stable keywords at all.
 Presence of such keywords is considered an error.  Consistency is tested
 only for ``~arch``.
 
+arches.desc in slave repositories
+---------------------------------
+
+If ``arches.desc`` is present in several repositories, then each file affects
+packages in the repository in question.  If the file does not specify a value
+for given arch, the value from the master repository is used.  However, using
+it in multiple repositories is discouraged.
+
+Note that the stability status override affects only packages in the slave
+repository and their direct dependencies.  If an arch is set to ``testing``,
+then master repositories are still permitted to use stable keywords.  If it is
+set to ``stable``, then missing stable keywords in dependencies from the master
+repository will cause dependency graph inconsistency.
+
 
 Backwards Compatibility
 =======================
@@ -178,14 +192,6 @@ to determine a list of stable arches shall fall back to the current method
 of determining stable arches by scanning profiles.desc for stable profiles.
 
 
-arches.desc in overlays
-=======================
-
-If arches.desc is present in several repositories, then the strictest setting
-for an architecture wins. Using arches.desc outside the gentoo (or
-alternative) master repository however is discouraged.
-
-
 Copyright
 =========
 
-- 
2.26.0

[gentoo-dev] [PATCH v3 9/9] glep-0072: Update metadata

[Michał Górny]

Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 glep-0072.rst | 22 ++++++++--------------
 1 file changed, 8 insertions(+), 14 deletions(-)

diff --git a/glep-0072.rst b/glep-0072.rst
index 68b8e91..548ba95 100644
--- a/glep-0072.rst
+++ b/glep-0072.rst
@@ -1,23 +1,17 @@
 ---
 GLEP: 72
 Title: Architecture stability status file
-Author: Andreas K. Hüttel <dilfridge@gentoo.org>
+Author: Andreas K. Hüttel <dilfridge@gentoo.org>,
+        Michał Górny <mgorny@gentoo.org>
 Type: Standards Track
-Status: Deferred
+Status: Draft
 Version: 1
 Created: 2017-05-06
-Last-Modified: 2019-06-10
-Post-History: 2017-05-06
+Last-Modified: 2020-04-12
+Post-History: 2017-05-06, 2020-04-10
 Content-Type: text/x-rst
 ---
 
-Status
-======
-
-Marked as deferred by GLEP editor Ulrich Müller on 2019-06-10, due to
-inactivity.
-
-
 Abstract
 ========
 
@@ -195,6 +189,6 @@ of determining stable arches by scanning profiles.desc for stable profiles.
 Copyright
 =========
 
-This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
-Unported License.  To view a copy of this license, visit
-https://creativecommons.org/licenses/by-sa/3.0/.
+This work is licensed under the Creative Commons Attribution-ShareAlike 4.0
+International License. To view a copy of this license, visit
+https://creativecommons.org/licenses/by-sa/4.0/.
-- 
2.26.0

Re: [gentoo-dev] [PATCH v3 6/9] glep-0072: Combine and amend description of states

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 529 bytes --]

>>>>> On Mon, 13 Apr 2020, Michał Górny wrote:

> -When a profile of an architecture arch is tested, then repoman checks
> -consistency of the dependency tree for ``arch`` and for ``~arch`` separately.
> +Stable means that the architecture is actively maintaning stable keywords.
                                                  ^^^^^^^^^^
Typo. Sorry for not noticing earlier.

> +When dependency graphs of packages with stable keywords are tested, they
> +are tested separately for ``arch`` and ``~arch`` systems.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

Re: [gentoo-dev] [PATCH v3 6/9] glep-0072: Combine and amend description of states

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

On Mon, 2020-04-13 at 11:02 +0200, Ulrich Mueller wrote:
> > > > > > On Mon, 13 Apr 2020, Michał Górny wrote:
> > -When a profile of an architecture arch is tested, then repoman checks
> > -consistency of the dependency tree for ``arch`` and for ``~arch`` separately.
> > +Stable means that the architecture is actively maintaning stable keywords.
>                                                   ^^^^^^^^^^
> Typo. Sorry for not noticing earlier.
> 

Fixed locally.  I suppose there's no need to send v4 for that.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

Re: [gentoo-dev] [PATCH v3 6/9] glep-0072: Combine and amend description of states

[Andreas K. Hüttel]

[-- Attachment #1: Type: text/plain, Size: 667 bytes --]

> +Transitional architectures are generally listed after stable architectures,
> +possibly mixed with testing.  Developers are not expected to file
> stabilization +requests.

I'm still claiming that it would be more useful to have the stable requests 
for transitional arches, even if we explicitly state that they can't block 
anything. 

Otherwise these arches will never be able to get out of the transitional hole.

[Maybe someone who actually does slow-arch work should speak up. Anyone out 
there still reading g-dev?]

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, qa, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-dev] [PATCH v3 6/9] glep-0072: Combine and amend description of states

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

On Mon, 2020-04-13 at 21:39 +0300, Andreas K. Hüttel wrote:
> > +Transitional architectures are generally listed after stable architectures,
> > +possibly mixed with testing.  Developers are not expected to file
> > stabilization +requests.
> 
> I'm still claiming that it would be more useful to have the stable requests 
> for transitional arches, even if we explicitly state that they can't block 
> anything. 
> 
> Otherwise these arches will never be able to get out of the transitional hole.
> 
> [Maybe someone who actually does slow-arch work should speak up. Anyone out 
> there still reading g-dev?]
> 

I'm lost.  The original definition said that this state is for arches
that use stable only on subset of packages needed for stage building. 
Why would people file streqs for other packages then?

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

Re: [gentoo-dev] [PATCH v3 6/9] glep-0072: Combine and amend description of states

[Andreas K. Hüttel]

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

> > [Maybe someone who actually does slow-arch work should speak up. Anyone
> > out
> > there still reading g-dev?]
> 
> I'm lost.  The original definition said that this state is for arches
> that use stable only on subset of packages needed for stage building.
> Why would people file streqs for other packages then?

Shrug. I'm not going to fight here for anything. 

Just my experience after some arches lost stable status was that these arch 
people still wanted to get CC'ed in stabilization requests. If only to keep 
track.

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, qa, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-dev] [PATCH v3 6/9] glep-0072: Combine and amend description of states

[Rolf Eike Beer]

[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]

Am Montag, 13. April 2020, 20:49:45 CEST schrieb Andreas K. Hüttel:
> > > [Maybe someone who actually does slow-arch work should speak up. Anyone
> > > out
> > > there still reading g-dev?]
> > 
> > I'm lost.  The original definition said that this state is for arches
> > that use stable only on subset of packages needed for stage building.
> > Why would people file streqs for other packages then?
> 
> Shrug. I'm not going to fight here for anything.
> 
> Just my experience after some arches lost stable status was that these arch
> people still wanted to get CC'ed in stabilization requests. If only to keep
> track.

I would very much welcome if these arches would be CC'ed on anything that was 
previously stable for them, i.e. nattka '*'. I'm fighting the dependency tree 
on hppa and stable to get them back to stable with a managable set of 
packages. I had at least 2 packges over the weekend that lost their stable 
keywords in a "cleanup old versions" after a previous stable request where one 
of these arches was forgotten. Luckily this wasn't too late now, if this 
happens after a while it is a nightmare to fight that back.

And when we are at it, please don't forget these arches when doing ALLARCHES 
stabilization either. I hope that nattka will actually improve both 
situations.

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]