Adam Borowski writes: > On Sat, Jan 06, 2018 at 07:17:14PM +0100, Marco d'Itri wrote: >> On Jan 06, Simon Richter <s...@debian.org> wrote: >> >> > As it is now, we have a lot of people who are maintaining their own >> > packages outside of Debian. Can we get enough support to reintegrate >> > both the people and the code? >> I will ignore for the time being the reasons why these packages are >> outside of Debian, and focus on the obvious prerequisite. >> As it is now, and as Simon is patiently trying to explain, sysvinit in >> Debian is basically unmaintained because no Debian developer cares >> enough about it. > > Ian Jackson and Benda Xu are nobodies? > (Somehow Ian mistakenly versioned an upload as NMU.)
I think Marco wants to suggest that they don't seem to actively maintain sysvinit and therefore the package is in practice unmaintained. > I can't think of any pressing issue (#872039 has bogus severity), the > package is mature, and any recent breakage happened due to systemd > changes. No maintainer has replied for almost half a year (when the bug was filed)... sysvinit probably only stays in testing because systemd depends on sysv-rc for compatability with LSB init scripts... > This is not to say all is fine -- the package really could take some extra > work, but it is functional. And the remaining packages of the sysvinit ecosystem are unmaintained too, for example insserv (#834284) and startpar (#834283). Or systemd-shim if you want to consider desktop systems too. Ansgar