On Fri, 2019-04-26 at 09:26 +, Holger Levsen wrote:
> I'm not really impressed by this fix either, cause it will also cause
> breakage in xx months when the next stable arrives...
Admittedly I haven't read the code in too much detail, but conceptually
I'd expect the following:
- either d-s-s
On Fri, Apr 26, 2019 at 03:31:42PM +0200, Christoph Anton Mitterer wrote:
> Oh and btw: it still does fail on upgrade for systems which have the
> old base-files and the old d-s-s, namely when apt upgrades base-files
> before.
I think I would prefer a new bug for this. Also suggestions how to fix
Oh and btw: it still does fail on upgrade for systems which have the
old base-files and the old d-s-s, namely when apt upgrades base-files
before.
Cheers,
Chris.
Thanks for keeping this open.
Packages should really not contain "time-bombs" like this.
On Fri, 26 Apr 2019, Holger Levsen wrote:
> control: severity -1 normal
> control: retitle -1 debian-security-support needs to be adapted to each new
> Debian release
> thanks
>
> On Fri, Apr 26, 2019 at
control: severity -1 normal
control: retitle -1 debian-security-support needs to be adapted to each new
Debian release
thanks
On Fri, Apr 26, 2019 at 12:34:44AM +0200, Christoph Anton Mitterer wrote:
> As if I wouldn't have written it before... o.O
talk is cheap, show me the code ;)
> Now all
Control: reopen -1
As if I wouldn't have written it before... o.O
Now all that was done is changing the value from 9 to 10 and it will
break again in xx months when the next-stable arrives an no one will
remember by then that this must be adapted...
Can't you just set a Conflicts/Breaks against
6 matches
Mail list logo
