On 2015-01-29 21:25, Andreas Beckmann wrote: > just to make notation clear > > /etc/sudoers is a *configuration file*, i.e. rules of preserving user > changes apply > > since wheezy it is also a *conffile* i.e. shipped with the package at > /etc/sudoers and managed by dpkg, not to be touched by maintainer scripts > > before it was managed by maintainer scripts
True. But as you observed in your initial report, the same bug can be triggered in a clean jessie environment, where the configuration file / conffile distinction is not a factor. As you reported: on a fresh jessie host, install sudo, and switch to sudo-ldap (or vice versa). The bug will present itself. > the tricky part is to get a smooth upgrade patch from the pre-conffile > stage to a conffile > > * with preserving user chnages > * without asking useles questions > > I think the real bug is still that pre-conffile handling is applied to a > conffile by listing the wheezy md5sum The way I see the problem, a solution for the pure-jessie case will also be a solution for the wheezy case. > if dpkg installs a conffile for the first time there are three > possibilities: > > * the file does not exist - trivial: install and record it > * the file exists and is the same as being installed - record it > * the file exists but is different: ask And the patch I proposed works with all these cases. But that is all beside the point, because the conffile is not being installed for the first time. The problem manifests itself during a switch, so we have a pre-existing conffile. Regards, Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
