Bug#727708: call for votes on default Linux init system for jessie
Steve Langasek wrote:
> On Tue, Jan 28, 2014 at 09:23:11AM -0800, Keith Packard wrote:
> > Bdale Garbee <firstname.lastname@example.org> writes:
> > > Thus, I believe the only acceptable option for Q2 from among your set is
> > > "requiring a specific init is permitted even if it is not the default
> > > one". But I would prefer to vote a ballot that doesn't mention
> > > dependencies at all.
> > I agree with this; I don't think we should try to force developers into
> > significant work to satisfy an init system constraint as that may
> > prevent or delay important fixes and improvements from entering the
> > repository.
> > Of course, nothing would prevent someone else from fixing these kinds of
> > bugs and having those fixes get merged into the package, potentially
> > invoking §6.1.4 to have the tech-ctte resolve any conflict as needed.
> > However, I'd anticipate that most package developers would readily
> > accept fixes that made their packages work for more people.
> I'd like to believe this; however, the fact that bug #726763 is still open
> leads me to fear otherwise.
I don't see any counterexamples in 726763 to the statement that "nothing
would prevent someone else from fixing these kinds of bugs and having
those fixes get merged into the package", or to the statement that "most
package developers would readily accept fixes that made their packages
work for more people." Fixing 726763 just needs a "Depends" from the
GNOME packages to reflect their dependency on logind and the suspend
inhibit mechanism, which as stated in the bug log won't happen until the
resolution of 727708. Meanwhile, installing either systemd-sysv or
systemd-shim (or having systemd installed and booting with
init=/bin/systemd) fixes the issue reported in 726763.
- Josh Triplett