Package: autopkgtest Version: 5.22 Severity: minor X-Debbugs-Cc: ja...@oneway.dev
Hi, Severity: minor because this is probably an exotic corner case. I'm filing this anyway becuse it is probably easily fixed. I'm on the adduser team. Adduser is part of the minimal install and is therefore installed in every environment that autopkgtest is run in. In current experimental, adduser has migrated /etc/adduser.conf to being an dpkg-conffile. Before that, adduser.conf was kind of "managed" in postinst. adduser.conf suddenly becoming a dpkg-conffile causes dpkg to emit a conffile prompt in every case of adduser <= 3.123 being updated to adduse >= 3.125. This also happens when the newly built adduser.deb gets installed during autopkgtest. The autopkgtest run stalls in this case and needs manual intervention to continue. Is this autopkgtest's intended behavior? If not, would passing --force-confnew to dpkg solve this issue? This most probably only happens iff: - the package in test is already part of the base install AND - the package in test has recently changed a maintainer-managed configuration file to being a dpkg-conffile. Since this is probably exotic, I'm holding off uploading a new version of adduser to unstable until Friday Aug 5 to give you a chance to reproduce this behavior. Let me know when I can upload earlier please. I am setting Jason Franklin, my team colleague who investgated this in depth, as Cc so that he can give additional information that I might have forgotten. Greetings Marc
