Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-08-24 Thread Petter Reinholdtsen
[Petter Reinholdtsen] > You can follow the recipe for moving conffiles in > http://wiki.debian.org/DpkgConffileHandling >, and check if > the current file have one of the known MD5 sums (the ones from > untouched earlier installs), and move it away in the preinst and > back in the upgrade fail, or

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-07-30 Thread Petter Reinholdtsen
[Bdale Garbee] > This is a one-time-transition issue. If there's some clever thing > that could be done, for example in the preinst, to help the > packaging system not need to prompt on upgrades that cross this > transition, I'd be happy to do it. You can follow the recipe for moving conffiles in

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-09 Thread Jonathan Nieder
(-cc: debian-dpkg) Bdale Garbee wrote: >But, given my understanding of how things work and my > experiences "trying to be clever" handling the sudoers file in previous > releases of sudo, I currently believe the best option is to just leave > this alone and let users be potentially co

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-09 Thread Bdale Garbee
On Wed, 9 Feb 2011 03:25:23 -0600, Jonathan Nieder wrote: > Bdale, if nothing happens in that front soon, the simplest workaround > might be to teach sudo to use ucf. Not a dependency I like, but so it > goes. Would you be interested in a patch doing that? No. This is a one-time-transition i

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-09 Thread Jonathan Nieder
Sven Joachim wrote: > How about merging sudo-ldap into sudo? Some other possibilities to think about: - let sudo-ldap dlopen libldap and print a suitable message on failure (too slow?) - let sudo-ldap depend on and be coinstallable with ordinary sudo (using a diversion) - move respons

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-09 Thread Sven Joachim
On 2011-02-09 13:06 +0100, Jonathan Nieder wrote: > (-cc: debian-dpkg) Then please CC me. :-) > Sven Joachim wrote: >> On 2011-02-09 11:25 +0100, Jonathan Nieder wrote: > >>> Yes, sudoers is co-owned between sudo and sudo-ldap and needs to be >>> removed when both are purged. >>> >>> I think ucf

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-09 Thread Jonathan Nieder
(-cc: debian-dpkg) Sven Joachim wrote: > On 2011-02-09 11:25 +0100, Jonathan Nieder wrote: >> Yes, sudoers is co-owned between sudo and sudo-ldap and needs to be >> removed when both are purged. >> >> I think ucf can handle that. [...] > You still need to remove the file yourself on purge, ucf do

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-09 Thread Sven Joachim
On 2011-02-09 11:25 +0100, Jonathan Nieder wrote: > Sven Joachim wrote: > >> Before anyone delves into this, have a look at bug #605130 which is >> exactly the problem that was solved by making /etc/sudoers a conffile. > > Yes, sudoers is co-owned between sudo and sudo-ldap and needs to be > remov

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-09 Thread Jonathan Nieder
Sven Joachim wrote: > Before anyone delves into this, have a look at bug #605130 which is > exactly the problem that was solved by making /etc/sudoers a conffile. Yes, sudoers is co-owned between sudo and sudo-ldap and needs to be removed when both are purged. I think ucf can handle that. When

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-09 Thread Sven Joachim
On 2011-02-09 10:25 +0100, Jonathan Nieder wrote: > Raphael Hertzog wrote: > >> The point is precisely to deal with the case when the user has not made >> any change. And for this you would have to move /etc/sudoers aside in >> "preinst upgrade" if it matches the md5sum of an unmodified file. > >

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-09 Thread Jonathan Nieder
Raphael Hertzog wrote: > The point is precisely to deal with the case when the user has not made > any change. And for this you would have to move /etc/sudoers aside in > "preinst upgrade" if it matches the md5sum of an unmodified file. Thanks, Raphaël. The main problem with this solution is tha

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-08 Thread Raphael Hertzog
Hi, On Tue, 08 Feb 2011, Jonathan Nieder wrote: > Bdale Garbee wrote: > > The version of sudo in sid/experimental has switched to treating the > > sudoers file as a standard Debian "conffile" instead of the former > > ad-hoc approach to managing the file. That's already the case for the version i

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-08 Thread Jonathan Nieder
Bdale Garbee wrote: > The version of sudo in sid/experimental has switched to treating the > sudoers file as a standard Debian "conffile" instead of the former > ad-hoc approach to managing the file. > > Given that there's no way for the sudo package to know what changes you > might have made to t

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-08 Thread Bdale Garbee
On Tue, 8 Feb 2011 17:09:59 -0600, Jonathan Nieder wrote: > Package: sudo > Version: 1.7.4p4-6 > Justification: policy §10.7.3 > > Basic squeeze system, installed a few weeks ago. At installation > time, I gave no root password, so sudo was set up automatically. > Now I am upgrading to sid/exper

Bug#612532: sudo: prompts despite unmodified /etc/sudoers on upgrade

2011-02-08 Thread Jonathan Nieder
Package: sudo Version: 1.7.4p4-6 Justification: policy §10.7.3 Basic squeeze system, installed a few weeks ago. At installation time, I gave no root password, so sudo was set up automatically. Now I am upgrading to sid/experimental. | Preparing to replace sudo 1.7.4p4-2.squeeze.1 (using .../sud