Hi, On Fri, Jul 04, 2014 at 09:08:21AM +0000, Gerrit Pape wrote: > This package hooks into /etc/inittab, does systemd not automatically > manage services from inittab? Isn't it systemd having release critical
For clarity: daemontools-run does *not* include a file in /etc/init.d/ which systemd might use, instead it adds this line to /etc/inittab: SV:123456:respawn:/usr/bin/svscanboot systemd's source doesn't even include the word "inittab" and I wouldn't expect it to. I don't think that it's systemd's fault. > I looked into latest policy, but did not find anything about systemd > support. I'm surprised that this is now a release critical bug, and the > package marked for removal. What's the justification? With the current stable (wheezy) this package works for most users. I assume that the next stable release, Jessie, will use systemd by default: https://lists.debian.org/debian-ctte/2014/02/msg00405.html So upon release, when this bug is not fixed yet, the package becomes useless for most users. "makes the package in question unusable" hence I choose "grave" as severity. I was actually tempted to mark it "critical". "makes … the whole system … break". Because that's what happens for me. Upon reboot, there's no working DNS resolution (nameserver 127.0.0.1, using djbdns). But I assume that this setup is not very common. Now I'm wondering about a few things: * Can I only choose a release-critical severity for bugs affecting the current stable but not the next stable? * Is there documentation clearly describing this? * If I want to use djb's dnscache, is it the correct way to install daemontools and daemontools-run, or is there any better way? My knowledge of Debian's policies is limited, so if you believe that my reasoning above is flawed, please point me to the relevant sections of the docs. Cheers Joern -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
