Bug#872039: [Pkg-sysvinit-devel] Bug#872039: why the severity?

2018-06-25 Thread Thomas Goirand
On 06/25/2018 03:10 AM, Cameron Norman wrote: >> > On the other hand, only a very small minority are still using > sysvinit on >> > Debian, so this I think it's ok to have the severity set to serious. >> >> According to my last data, 14% of unstable users; less on stable as those >> tend to be

Bug#872039: why the severity?

2018-06-24 Thread Cameron Norman
On Fri, 12 Jan 2018 03:56:42 +0100 Adam Borowski wrote: > On Wed, Jan 10, 2018 at 08:38:39PM +0100, John Paul Adrian Glaubitz wrote: > > > Please tell me why this would be serious: any filesystem from this millenium > > > can handle unclean shutdown fine -- especially if there's a sync before > >

Bug#872039: why the severity?

2018-01-11 Thread Adam Borowski
On Wed, Jan 10, 2018 at 08:38:39PM +0100, John Paul Adrian Glaubitz wrote: > > Please tell me why this would be serious: any filesystem from this millenium > > can handle unclean shutdown fine -- especially if there's a sync before > > reboot/poweroff. > > That's hardly an argument. There is

Bug#872039: why the severity?

2018-01-10 Thread John Paul Adrian Glaubitz
> Please tell me why this would be serious: any filesystem from this millenium > can handle unclean shutdown fine -- especially if there's a sync before > reboot/poweroff. That's hardly an argument. There is still very much the possibility that this bug causes data-loss, so the severity is

Bug#872039: why the severity?

2017-12-26 Thread Adam Borowski
> Reason for Severity=serious: This leaves /var (or other > filesystems) in an unclean state, so could possibly lead to > data loss! Please tell me why this would be serious: any filesystem from this millenium can handle unclean shutdown fine -- especially if there's a sync before