On Sun, 2 Jul 2017 03:15:36 +0200 Guillem Jover wrote:
> Hi!
>
> [...]
>
> Isn't the obviously correct and policy compliant approach to just
> Conflicts/Replaces (or Breaks/Replaces depending on the force you want
> to apply here) with the init-select package from one of the grub
> packages, and
Hi!
On Fri, 2017-06-23 at 12:22:34 +0100, Colin Watson wrote:
> The basic problem in init-select is of course the good old favourite of
> a conffile not behaving correctly when the package has been removed but
> not purged. This is probably worth fixing in unstable as follows, since
> init-select
Hi,
I've now filed a jessie-pu request (#866643) for init-select, with
... $(if [ -x /usr/lib/init-select/get-init ]; then
/usr/lib/init-select/get-init; fi)
Given that init-select has now been removed from sid, you don't
have to care too much about messing around with init-select.cfg,
you c
On Wed, May 31, 2017 at 01:42:34PM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'jessie'.
> It installed fine in 'jessie', then the upgrade to 'stretch' fails.
>
> >From the attached log (scroll to the bottom...):
>
> Setting up gru
Package: grub-coreboot
Version: 2.02~beta3-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + init-select
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch'
5 matches
Mail list logo
