If a package hard codes the UID or GID when adding a user or group to
the system and that UID/GID already exists, we should abort rather than
changing the UID/GID.
---
eclass/user.eclass | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/eclass/user.eclass b/eclass/user.ecla
On Mon, May 27, 2019 at 11:45 AM William Hubbs wrote:
>
> If a package hard codes the UID or GID when adding a user or group to
> the system and that UID/GID already exists, we should abort rather than
> changing the UID/GID.
These functions have behaved this way for a long time.
What problem ar
On Mon, 2019-05-27 at 10:45 -0500, William Hubbs wrote:
> If a package hard codes the UID or GID when adding a user or group to
> the system and that UID/GID already exists, we should abort rather than
> changing the UID/GID.
I think the major usage of this argument is not to enforce a specific
UI
On Mon, May 27, 2019 at 08:44:09PM -0400, Mike Gilbert wrote:
> On Mon, May 27, 2019 at 11:45 AM William Hubbs wrote:
> >
> > If a package hard codes the UID or GID when adding a user or group to
> > the system and that UID/GID already exists, we should abort rather than
> > changing the UID/GID.
On Tue, May 28, 2019 at 1:41 AM Robin H. Johnson wrote:
>
> On Mon, May 27, 2019 at 08:44:09PM -0400, Mike Gilbert wrote:
> > On Mon, May 27, 2019 at 11:45 AM William Hubbs wrote:
> > >
> > > If a package hard codes the UID or GID when adding a user or group to
> > > the system and that UID/GID a
