public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Dummer <martin.dummer@gmx.net>
To: gentoo-dev@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>,
	gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Subject: Re: [gentoo-dev] New acct-* package policy
Date: Mon, 6 Jan 2020 01:36:53 +0100	[thread overview]
Message-ID: <a4625acb-b270-f328-795d-ecde7415d74b@gmx.net> (raw)
In-Reply-To: <0f3118f45820a27cf66a58d14144eb62b60733a4.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 904 bytes --]

Am 21.12.19 um 18:32 schrieb Michał Górny:
> Please commit and push uid-gid.txt [3] change to data/api.git *before*
> your packages.  This makes sure that any potential collisions are caught
> as merge conflicts before they hit users.  The CI also catches UID/GID
> collisions.


One remark from a "proxy-maintainer" view:

A proxy-maintainer (like me) cannot commit or add github pull requests for 

https://gitweb.gentoo.org/data/api.git/tree/files/uid-gid.tx

and therefore cannot allocate a valid UID/GID for valid new ebuilds in
pull requests.

So for proxy-maintained packages which need acct-user/acct-group ebuilds
this must be

- either done like before - announcement on the gentoo-dev ML, then
committed by ???

- or done by a member of the proxy-maintainers group.


Maybe you find the time to refine that exception in the documentation.


Bye

Martin




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-01-06  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-21 17:32 [gentoo-dev] New acct-* package policy Michał Górny
2020-01-06  0:36 ` Martin Dummer [this message]
2020-01-06  0:41   ` Ralph Seichter
2020-01-06  0:46   ` Aaron Bauman
2020-01-06  7:39   ` Joonas Niilola

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a4625acb-b270-f328-795d-ecde7415d74b@gmx.net \
    --to=martin.dummer@gmx.net \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox