Colin Watson <firstname.lastname@example.org> writes: > I could arrange for the relevant grub2 postinst scripts to remove > /etc/default/grub.d/init-select.cfg entirely when appropriate conditions > apply. In addition to a self-defence argument, this is further > justified by the fact that grub2 now provides a similar facility of its > own as of 2.02~beta2-20: if other init daemons are installed, then > grub-mkconfig generates additional menu items for them (although there > are no arrangements to migrate the default choice from > /etc/default/init). This would still violate policy §10.7.3/10.7.4, > although it seems to be the favoured option of the debian-devel thread, > and it is the least bad option I can see so far. This seems like a tolerable approach for this particular situation. The question of what policy changes (if any) are needed seems harder to me, and for the moment I'll defer commenting on that, except to note that I agree with Tollef that policy change doesn't need be a blocker here.
Description: PGP signature