Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

On Wed, Aug 16, 2017 at 06:58:32PM +0200, Philip Hands wrote: > Colin Watson writes: > > ... > > If you want to consider this bug closed at this point without a formal > > resolution, then I'm OK with saving you folks some time, ... > > I think that's fine, so I'm going to

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

On Sat, Jul 22, 2017 at 06:25:19AM +0200, Philip Hands wrote: > Just in case it's not already clear from the replies you have received > so far, there is a consensus amongst the members of the TC that you > should do as you suggest -- this was reflected in our recent meeting: > > >

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

Hi Colin, Just in case it's not already clear from the replies you have received so far, there is a consensus amongst the members of the TC that you should do as you suggest -- this was reflected in our recent meeting:

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

On Tue, Jun 27, 2017 at 11:31:57AM -0700, Josh Triplett wrote: > On Sun, 25 Jun 2017 23:37:13 +0100 Colin Watson wrote: > > I could arrange for the relevant grub2 postinst scripts to remove > > /etc/default/grub.d/init-select.cfg entirely when appropriate conditions > >

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

Control: block 866643 with -1 On Wed, 28 Jun 2017 22:34:41 +0300 Niko Tyni wrote: > On Sun, Jun 25, 2017 at 11:37:13PM +0100, Colin Watson wrote: > > > I could arrange for the relevant grub2 postinst scripts to remove > > /etc/default/grub.d/init-select.cfg entirely when

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

On Sun, Jun 25, 2017 at 11:37:13PM +0100, Colin Watson wrote: > 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

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

On Sun, 25 Jun 2017 23:37:13 +0100 Colin Watson wrote: > 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

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

Colin Watson 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

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

Hi, ]] Colin Watson > 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

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

On Sun, 25 Jun 2017 23:37:13 +0100 Colin Watson wrote > I could have NMUed init-select in both unstable and stretch with a > corrected conffile (and probably also with a corrected sysvinit init-select was not part of stretch, so an NMU would not be possible afaics. At least

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

Package: tech-ctte Preamble I would like to seek advice from the Technical Committee on the proper resolution of #863801. This is (for once) not a matter of irreconcilable disagreement among developers, but one where the only sensible technical resolutions I can see are in clear