On 18/02/2020 08.45, Bastian Blank wrote:
On Tue, Jan 28, 2020 at 09:25:28PM +0100, Andreas Beckmann wrote:during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded...This is actually ucf vs conffile in different packages.
Great. grub-pc: ucf grub-cloud-amd64: conffile Can we make grub-cloud-amd64 Conflicts: grub-pc ?Then each can live in its own world handling /etc/default/grub differently. (Are there more grub-cloud-$ARCH?)
Or is there some need for them to be co-installable?(Switching from one to the other without purging the old one first will likely cause more prompting, but such a switch is highly unlikely.)
This conflict will break debian-cloud-images-packages, which depends on both grub-pc and grub-cloud-amd64. Is that really needed?
This is a violation of policy 10.7.3, see https://www.debian.org/doc/debian-policy/ch-files.html#behavior, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens."But this is about conffiles, not scripts.
???/etc/default/grub is a configuration file for both grub-pc and grub-cloud-amd64, and for grub-pc it is also a conffile.
Andreas