From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 75F9A158004 for ; Tue, 18 Jul 2023 08:59:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 02D47E08F9; Tue, 18 Jul 2023 08:59:45 +0000 (UTC) Received: from mail-yw1-x1131.google.com (mail-yw1-x1131.google.com [IPv6:2607:f8b0:4864:20::1131]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C7690E08E2 for ; Tue, 18 Jul 2023 08:59:44 +0000 (UTC) Received: by mail-yw1-x1131.google.com with SMTP id 00721157ae682-579dd20b1c8so52627077b3.1 for ; Tue, 18 Jul 2023 01:59:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689670784; x=1692262784; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=zAp/h0mHggIiY/dO14rVniJN7qLou4Ao/6H4OaYa5JM=; b=YhwUZCdAdVPoxx/IHGBplHtdNj5WxaEhyiE6oPT94khkouqDN5ypBQd7T88byfM6pY Pd2R88MS7/i/SYLY7CU5LAJdUd3RdWgXASmT6HNWtyj/g+JszoB6Umu4N8iEUmRNh8KB MLU80kJiVjKdiclL+qRSRFqEiEQ5EppIt/ntxK9q76JNyzVJIf4IebjQ2sxNA/0w0cNk nj19uvUf1LIBFDjnZwbMCxaoM058lk6IsL8HzJis0xEVffZnreLrTuJeMfCRekZyGusS JisFpMda7OevevYJf/wVtZNQCjEk8chjgpTXaIPeSETUFnLWcBTQabkUk4OEG22fsfLo VTew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689670784; x=1692262784; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=zAp/h0mHggIiY/dO14rVniJN7qLou4Ao/6H4OaYa5JM=; b=CZ9kdy+bTVJTZ8HFT1OPZvHLIqBekkeB0TmTdqQ66XDJUsMXizErF85VB2k5NrgCip e/5WQnkWFk5aB6r31fgt3QGBXc3aflS4irvs6ak6fhWvCv6b/26QbCboxSpGzQqOzhUu PZJaatuSaUGlx43IEFMoYoTTPwfCprB18nmvwN1tIsyzA+uVTWI0J6m6riFqNB+2gJd+ Y4QosxqLUfPl7id+pNZFoWj5Xd/P2AVA+M+uU1WJBFFiL++ujvnUNeytsyvZ2DduX6yA J1Ydy6EdrLRCpZ6b74UFd3qcsxoIOqTn+mISsJgN18scDz2I4MqnUPfYGyW9UeWnHumo bYQA== X-Gm-Message-State: ABy/qLbRjhzOiI9SrbnvaznIkGKaaQvqHrUlbwIJuhZP5atHtX5eyATk qwHzAkxCNUfgCsqYExZ4r3oC+HtEayG4XU/GZLDyxwco X-Google-Smtp-Source: APBJJlFQJez1JdxzgOmCig82vWLoc8HaJPOqihgnfh++5R/5aJ4oKUUUyv/tSHa3xuf/HPYYA0joYyf0Nmr6C3NrsSs= X-Received: by 2002:a81:924c:0:b0:579:e606:6ce2 with SMTP id j73-20020a81924c000000b00579e6066ce2mr14031072ywg.40.1689670784131; Tue, 18 Jul 2023 01:59:44 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <9626e2f9-5f57-e061-b3ba-1c1fa95cb868@gentoo.org> <87sf9m9ta5.fsf@gentoo.org> <01b3b14c8a4fdc3df001bdd28eccce60726d68e1.camel@gentoo.org> In-Reply-To: From: =?UTF-8?B?0JfRg9GA0LDQsSDQmtCy0LDRh9Cw0LTQt9C1?= Date: Tue, 18 Jul 2023 11:59:33 +0300 Message-ID: Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Last rites: obsolete acct-* packages To: gentoo-dev@lists.gentoo.org Content-Type: multipart/alternative; boundary="000000000000e026620600bf22ba" X-Archives-Salt: 65610dad-8505-475d-9d50-1e220b60e2e4 X-Archives-Hash: 2c34ddb238f3234772f8b914ccb9bc49 --000000000000e026620600bf22ba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Well, this configuration is reasonable, I am for the change On Tue, 18 Jul 2023 at 11:55 Florian Schmaus wrote: > On 18/07/2023 10.42, =D0=97=D1=83=D1=80=D0=B0=D0=B1 =D0=9A=D0=B2=D0=B0=D1= =87=D0=B0=D0=B4=D0=B7=D0=B5 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. > > Nobody is proposing that the uid-gid.txt entry is removed. Ideally, it > would be marked as 'historical', together with the date it went historica= l. > > > > 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? > > If a UID/GID is in use, then acct-*.eclass will find the next suitable > ID (unless, e.g. ACCT_USER_ENFORCE_ID is set, we is usually not the case)= . > > - Flow > --000000000000e026620600bf22ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Well, this configuration is reasonable, I am for the chan= ge

On Tue, 18 Jul 2023 at 11:55 Florian Schmaus <flow@gentoo.org> wrote:
= On 18/07/2023 10.42, =D0=97=D1=83=D1=80=D0=B0=D0=B1 =D0=9A=D0=B2=D0=B0=D1= =87=D0=B0=D0=B4=D0=B7=D0=B5 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.<= br>
Nobody is proposing that the uid-gid.txt entry is removed. Ideally, it
would be marked as 'historical', together with the date it went his= torical.


> 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 bee= n
> updated for some time. What if they still have acct-user/foo, when >= ; acct-user/bar with the same UID is installed?

If a UID/GID is in use, then acct-*.eclass will find the next suitable
ID (unless, e.g. ACCT_USER_ENFORCE_ID is set, we is usually not the case).<= br>
- Flow
--000000000000e026620600bf22ba--