Bug#769747: Technical committee acting in gross violation of the Debian constitution

Sjoerd Simons sjoerd at luon.net
Tue Nov 18 07:28:01 GMT 2014


On Tue, 2014-11-18 at 06:29 +0100, Martin Pitt wrote:
> Hello all,
> 
> Josselin Mouette [2014-11-17 19:38 +0100]:
> > This decision has been made in gross violation of constitution §6.3.6,
> > being summoned to override a maintainer’s choice while the solution was
> > still under discussion.
> > 
> > I urge the systemd maintainers not to take it into account.
> 
> TBH, I think this was blown way out of proportion. I already switched
> the dependencies around yesterday in git. It's a rather harmless
> change after all -- a no-op for any existing system, regardless of
> whether they have systemd-sysv or sysvinit installed. And on upgrades,
> libpam-systemd is *not* meant to be the package that decides which
> init system you end up with IMHO -- that should be the job of a
> meta-package like "init" or other means (and there's still a pending
> discussion whether and how to upgrade existing wheezy machines to
> systemd).
> 
> If other systemd maintainers want to keep discussing this dependency
> issue, please do (but it seems we are just losing them in dangerous
> quantities!), but I see absolutely no point in this personally.

Yeah, the switch is entirely fine, thanks for doing the change. At worst
it's inelegant to have to do this in order to trick the dependency
systems into doing the right thing, maybe we manage to find a nicer
solution for jessie+1. 

However I don't really the path that lead to the vote and the overruling
(as i really don't think such drastic measures were needed), but that's
a completely different discussion that clearly needs to be held
seperately from discussing any specific technial outcome including this
one.
-- 
Sjoerd Simons <sjoerd at luon.net>




More information about the Pkg-systemd-maintainers mailing list