upgrading /etc/passwd (was Re: List of ... problems for 1.2)
-----BEGIN PGP SIGNED MESSAGE-----
> > However, I have a very very strange problem: When I update base-passwd
> > package using dpkg, *nothing happens*. Has anybody else seen this
> > behavioour?
> Can you expand on "nothing"?
> If you built the system fresh from the base disks, this package is up to
> date and dpkg will probably tell you so. Did you get any response from
# dpkg -i base-passwd_1.2.0-3.deb
(Reading database ... 7253 files and directories currently installed.)
Preparing to replace base-passwd 1.2.0-3 (using base-passwd_1.2.0-3.deb) ...
Unpacking replacement base-passwd ...
Setting up base-passwd (1.2.0-3) ...
And no questions about replacing /etc/passwd or not.
Ok, after this, I have just read the programmers' manual, and it says:
"When a package is upgraded dpkg will process the configuration files
during the configuration stage, shortly before it runs the package's
postinst script, etc. etc" i.e. I guess that it does not say anything
because I'm not really "upgrading" (from 1.2.0-3 to 1.2.0-3).
But IMHO this is counter-intuituve. A small warning would be very very
nice. I wonder what would happen if somebody upgrades base-passwd, say NO
when asked to replace current /etc/passwd and /etc/group, and later he/she
wants to add those new users in base-passwd (like "list") by installing it
again. I suspect he/she will not succeed by doing that, and it is a pity.
Maybe what I miss here is a dpkg option to be asked about replacing or not
conf files even if version number does not grow. Is there such an option?
I just would like to avoid tell people say "add the user/group
list by hand", when they find that list user does not exist.
(Of course, smartlist postinst need some more work on my side also).
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
Santiago Vila <email@example.com>
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com