Re: Warning: Do NOT upgrade base-passwd in unstable!

2002-01-22 Thread Colin Watson
On Sun, Jan 20, 2002 at 08:52:55PM -0500, Michael P. Soulier wrote: > On 20/01/02 Colin Watson did speaketh: > > Well, quite, but the question you snipped was about why the maintainer > > didn't notice it. Although I occasionally test packages I build on, say, > > my workstation at work, I'll proba

Re: Warning: Do NOT upgrade base-passwd in unstable!

2002-01-20 Thread Michael P. Soulier
On 20/01/02 Colin Watson did speaketh: > On Sun, Jan 20, 2002 at 02:10:40PM -0500, Michael P. Soulier wrote: > > Well, quite, but the question you snipped was about why the maintainer > didn't notice it. Although I occasionally test packages I build on, say, > my workstation at work, I'll probabl

Re: Warning: Do NOT upgrade base-passwd in unstable!

2002-01-20 Thread Colin Watson
On Sun, Jan 20, 2002 at 02:10:40PM -0500, Michael P. Soulier wrote: > On 20/01/02 Colin Watson did speaketh: > > By default, most uids in the password file match their gids, aside from > > a couple of daemons, so I can imagine it being easy to miss. > > Only on personal systems. Well, quite, but

Re: Warning: Do NOT upgrade base-passwd in unstable!

2002-01-20 Thread Adam Majer
On Sun, Jan 20, 2002 at 02:10:40PM -0500, Michael P. Soulier wrote: > On 20/01/02 Colin Watson did speaketh: > > > On Sun, Jan 20, 2002 at 12:13:10PM -0600, Adam Majer wrote: > > > > By default, most uids in the password file match their gids, aside from > > a couple of daemons, so I can imagine

Re: Warning: Do NOT upgrade base-passwd in unstable!

2002-01-20 Thread Michael P. Soulier
On 20/01/02 Colin Watson did speaketh: > On Sun, Jan 20, 2002 at 12:13:10PM -0600, Adam Majer wrote: > > By default, most uids in the password file match their gids, aside from > a couple of daemons, so I can imagine it being easy to miss. Only on personal systems. I've found that most productio

Re: Warning: Do NOT upgrade base-passwd in unstable!

2002-01-20 Thread Colin Watson
On Sun, Jan 20, 2002 at 12:13:10PM -0600, Adam Majer wrote: > On Sun, Jan 20, 2002 at 09:57:15AM -0500, Kevin B. McCarty wrote: > > If you are running unstable, do NOT upgrade the base-passwd package!!! > > Version 3.2.2 has a critical bug which causes it to swap the UIDs and GIDs > > for users in

Re: Warning: Do NOT upgrade base-passwd in unstable!

2002-01-20 Thread Adam Majer
On Sun, Jan 20, 2002 at 09:57:15AM -0500, Kevin B. McCarty wrote: > If you are running unstable, do NOT upgrade the base-passwd package!!! > Version 3.2.2 has a critical bug which causes it to swap the UIDs and GIDs > for users in the /etc/passwd file. (See bug reports #130032 and 130085.) > > I

Re: Warning: Do NOT upgrade base-passwd in unstable!

2002-01-20 Thread Sean 'Shaleh' Perry
On 20-Jan-2002 Kevin B. McCarty wrote: > If you are running unstable, do NOT upgrade the base-passwd package!!! > Version 3.2.2 has a critical bug which causes it to swap the UIDs and GIDs > for users in the /etc/passwd file. (See bug reports #130032 and 130085.) > > I found this out the hard wa

Re: Warning: Do NOT upgrade base-passwd in unstable!

2002-01-20 Thread Jason Wood
On Sunday 20 January 2002 2:57 pm, Kevin B. McCarty wrote: > If you are running unstable, do NOT upgrade the base-passwd package!!! > Version 3.2.2 has a critical bug which causes it to swap the UIDs and GIDs > for users in the /etc/passwd file. (See bug reports #130032 and 130085.) Hehe, cheers.

Re: Warning: Do NOT upgrade base-passwd in unstable!

2002-01-20 Thread Paul 'Baloo' Johnson
On Sun, 20 Jan 2002, Kevin B. McCarty wrote: > I found this out the hard way. The simple fix if it's already happened to > you: copy the backup file "/etc/passwd.org" over top of the new file > "/etc/passwd". You should do this to shadow and group as well and readd any users that may have been a

Warning: Do NOT upgrade base-passwd in unstable!

2002-01-20 Thread Kevin B. McCarty
If you are running unstable, do NOT upgrade the base-passwd package!!! Version 3.2.2 has a critical bug which causes it to swap the UIDs and GIDs for users in the /etc/passwd file. (See bug reports #130032 and 130085.) I found this out the hard way. The simple fix if it's already happened to you