Bug#1072375: sysvinit: please implement restarting init using triggers

2024-06-14 Thread Aurelien Jarno
Hi Mark, On 2024-06-13 10:26, Mark Hindley wrote: > Aurelien, > > On Sun, Jun 09, 2024 at 08:51:34PM +0100, Mark Hindley wrote: > > Until that happens, does that mean that sysvinit will be restarted twice, > > once by > > libc6 postinst and once by the libc-upgrade trigger? > > For the record,

Bug#1072375: sysvinit: please implement restarting init using triggers

2024-06-13 Thread Mark Hindley
Aurelien, On Sun, Jun 09, 2024 at 08:51:34PM +0100, Mark Hindley wrote: > Until that happens, does that mean that sysvinit will be restarted twice, > once by > libc6 postinst and once by the libc-upgrade trigger? For the record, this appears to be the case: $ dpkg-reconfigure libc6 logs in

Bug#1072375: sysvinit: please implement restarting init using triggers

2024-06-09 Thread Mark Hindley
Control: tags -1 patch Aurelien, Thanks for this. I have a proposed patch for this (see attached). I have also taken the opportunity to rework and cleanup the sysvinit-core postinst. Any comments are welcome. On Sat, Jun 01, 2024 at 11:38:04PM +0200, Aurelien Jarno wrote: > At some point this

Bug#1072375: sysvinit: please implement restarting init using triggers

2024-06-01 Thread Aurelien Jarno
Source: sysvinit Version: 3.09-1 Severity: important Dear maintainer, To avoid issues like #1071462, please implement restarting init by declaring an interest on the "libc-upgrade" trigger, introduced in glibc 2.38-12. At some point this will allow us to drop the corresponding part of the libc6