Right, damn;). Guillem, do you generally think that using triggers (by manually adding activate to sysvinit*) is a good way how to solve this problem?
Ondřej On December 9, 2014 3:27:36 PM GMT+01:00, Guillem Jover <guil...@debian.org> wrote: >Hi! > >On Tue, 2014-12-09 at 14:56:56 +0100, Ondřej Surý wrote: >> On Tue, Dec 9, 2014, at 12:24, Gerrit Pape wrote: >> > On Mon, Nov 24, 2014 at 10:08:49PM +0000, Simon McVittie wrote: >> > > On 24/11/14 21:41, Gerrit Pape wrote: >> > > > Better than (2) would be to make the existence of /etc/inittab >still >> > > > essential for jessie, by moving the corresponding code from >> > > > sysvinit-core into the essential init package. What do you >think? >> > > >> > > If you go this route, I think initscripts might be a better home >for >> > >> > As I wrote above, I actually don't have the time to go any road at >all. >> > >> > The packages worked just fine until I learnt that support for the >> > inittab interface is dropped in jessie. I fixed the packages. Now >I >> > learnt that the existence of /etc/inittab is no longer essential, >next >> > thing breaking my packages - when switching jessie to sysvinit. >> >> I haven't noticed if this was mentioned before, but dpkg-trigger on >> /etc/inittab doesn't work? >> >> e.g. >> >> interest /etc/inittab > >It should not, because the file is not managed by dpkg, and no one >AFAIK is explicitly activating that file trigger. (And remember, >always consider if using the -noawait trigger variants is more >appropriate, as that makes the upgrade path way easier, and avoids >possible trigger cycles.) > >Thanks, >Guillem Cheers, -- Ondřej Surý <ond...@sury.org> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
