On 20 December 2016 at 23:13, Paul Wise <p...@debian.org> wrote: > Control: reopen -1 > > On Tue, 2016-12-20 at 19:55 -0300, Felipe Sateler wrote: > >> Unfortunately, I think the ship to fix this has sailed, as jessie was >> released a while ago already. I'm therefore closing this bug. > > There is still the possibility of fixing this in a jessie point release > so I think it should remain open unless you aren't going to bother. If > that is the case then the bug should be marked as wontfix and closed.
Did anyone else besides Michael verify if the proposed solution (add systemd-sysv to recommends) works and doesn't bring undesired effects? From my POV, this is a high risk change with fairly little payoff[1]. [1] https://qa.debian.org/popcon-graph.php?packages=systemd-sysv%2Csysvinit-core%2Csysvinit&show_installed=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 This shows a fairly constant path for sysvinit-core, and that systemd-sysv | sysvinit-core is already installed for about 75-80% of the the peak sysvinit installation usage. That means the transition is mostly done. -- Saludos, Felipe Sateler
