On Wed, Jun 08, 2022 at 06:01:11PM +0200, Marc Haber wrote: > On Wed, Jun 08, 2022 at 10:11:48AM -0400, Jason Franklin wrote: > > Personally, I think we should simply install a default adduser.conf file > > and remove all of the debconf stuff from the post install script. > > That was like the gist of a short discussion I initiated in March, see > https://lists.debian.org/debian-boot/2022/03/msg00099.html
Aha! Wonderful. There is precedent for this idea. This thread also explains the context in which this debconf question had been useful (i.e., the installer). I had not been able to guess this. We would also be able to finally close this one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541620 > We just need to make sure to make a smooth transitoin, testing > installation and upgrades from a system with a locally changed > adduser.conf, a locally removed adduser.conf and adduser.conf unchanged > from the package. Local changes must be preserved. I had thought this would be gracefully handled by Dpkg, but maybe my understanding is not complete here. Simply changing the debian/install file to properly install the default /etc/adduser.conf file would work, I had thought (also removing all of the newly obsolete stuff in the maintscripts). The result would be that installing/upgrading adduser would prompt for whether or not you want to keep the local version or take the maintainer's version, etc. This prompt would depend on whether, for example, --force-confmiss or --force-conf{old,new} are passed to Dpkg, usually via apt. At least I thought that's how it would work. If we're on the same page here, should I put a patch together? -- Jason Franklin
