On Wed, 2014-11-19 at 13:51 +0100, Ansgar Burchardt wrote:
> Hi,
>
> I would like to see an end to open questions on systemd in Jessie.
>
> So, given that the GR is over and no technical proposals for not
> switching init systems on upgrade to Jessie have been made, is it
> possible to draw a con
On Fri, 2014-09-26 at 13:04 +0200, Carlos Alberto Lopez Perez wrote:
> On 11/09/14 14:36, Ben Hutchings wrote:
> > On Wed, 2014-09-10 at 21:36 +, Nick Phillips wrote:
> > [...]
> >> Debian has a good and hard-earned reputation for not messing up
> >> sysadmins' changes; upgrading to systemd - h
On Wed, 2014-07-02 at 20:39 +0200, Svante Signell wrote:
> On Wed, 2014-07-02 at 16:54 +0200, Emilio Pozuelo Monfort wrote:
> And this one is
> very important: systemd is default, not optional.
^^
On Wed, 2014-07-02 at 16:54 +0200, Emilio Pozuelo Monfort wrote:
> On 02/07/14 15:38, Thorsten Glaser wrote:
> > Jeroen Dekkers wrote:
> >> Wookey wrote:
> > But then, I did not upload them, and I do not oppose a name change.
> > Also, add the "Important: yes" header (and, obviously, remove the
>
On Thu, 2014-05-15 at 10:55 +0200, Gergely Nagy wrote:
> Thorsten Glaser writes:
> > Integration of some components at the cost of disabling the freedom
> > of users to choose a different free component that also does the job,
> > and at the cost of removing some users' use cases: no. That is not
On Fri, 2014-05-09 at 20:39 -0700, Josh Triplett wrote:
> Russ Allbery wrote:
> > ...
> > I think we need some sort of critical debconf prompt here for the jessie
> > release, similar to how we handled the change of /bin/sh to dash and how
> > we handled the switch to startpar. Probably in systemd
Package: systemd-sysv
Version: 204
Severity: serious
When upgrading an old system installing certain packages, like
network-manager and gdm3 systemd is installed changing the init system.
These packages depend on libpam-systemd, which depends on systemd-sysv |
systemd-shim. If systemd-shim is not
