public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Last rites: obsolete acct-* packages
Date: Tue, 18 Jul 2023 11:05:12 +0200	[thread overview]
Message-ID: <ZLZVyDuhwMbFBNLA@gentoo.org> (raw)
In-Reply-To: <CADKhjbO3s-B4cGNA5135sZixNDNK1on=mB63x7MVQfKrqajWMg@mail.gmail.com>

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

On 18-07-2023 11:42:39 +0300, Зураб Квачадзе wrote:
> How do we handle this case, then.
> Imagine we have a leaf package acct-user/foo, which has a reserved UID of 123.
> It gets last rited and its entry is removed from uid-gid.txt. After a while
> appears a new package acct-user/bar, which takes the 123 UID. Then a user, say
> Bob, updates their system, which haven't been updated for some time. What if
> they still have acct-user/foo, when acct-user/bar with the same UID is
> installed? Should we even care about such cases?

IMO we should, thus 123 should not be removed from uid-gid.txt, and instead
be marked as reserved or something with a date.

Thanks,
Fabian

-- 
Fabian Groffen
Gentoo on a different level

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

  parent reply	other threads:[~2023-07-18  9:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 19:43 [gentoo-dev] Last rites: obsolete acct-* packages Florian Schmaus
2023-07-17 20:21 ` [gentoo-dev] Re: [gentoo-dev-announce] " Matt Turner
2023-07-17 20:27   ` Sam James
2023-07-17 21:07     ` Mike Gilbert
2023-07-18  6:39       ` Ulrich Mueller
2023-07-18  8:22         ` Pacho Ramos
2023-07-18  8:42           ` Зураб Квачадзе
2023-07-18  8:54             ` Florian Schmaus
2023-07-18  8:59               ` Зураб Квачадзе
2023-07-18  9:05             ` Fabian Groffen [this message]
2023-07-18  9:56       ` Sam James
2023-07-18 11:58         ` Florian Schmaus
2023-07-18 13:08           ` Sam James
2023-07-18 13:15             ` Sam James

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=ZLZVyDuhwMbFBNLA@gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

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

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