GitLab

Conflicts:
	debian/changelog
	debian/gbp.conf
	debian/patches/Always-probe-cpu-support-drivers.patch
	debian/patches/Load-sg-module-from-80-drivers.rules.patch
	debian/patches/series

LSB system facilities begin with a dollar sign '$'.

/lib/lsb/init-functions.d/40-systemd unconditionally uses "set +e; set
+u". This can change the behavior of init scripts that use "set -e"
and/or "set -u".

Change the systemd integration to not rely on "set +e" or "set +u" but
instead work correctly in all cases by catching all commands that might
fail.

Closes: #751472

- Use DefaultDependencies=no in ifup@.service so the service can be started
  as early as possible.
- Create the ifupdown runtime directory in ifup@.service as we can no longer
  rely on the networking service to do that for us.
- Don't stop ifup@.service on shutdown but let the networking service take
  care of stopping all hotplugged interfaces.
- Only start ifup@.service for interfaces configured as allow-hotplug.

If systemd is not the active PID 1 and the SysV compat tools are
provided by systemd-sysv, /sbin/telinit simply forwards the requests to
the native telinit implementation.
To make the upgrade from sysvinit to systemd less disruptive, the plan
is to make the transitional sysvinit package provide
/lib/sysvinit/telinit and /lib/sysvinit/init which then can be used as a
fallback in case of emergency.
Set the telinit path in systemd accordingly in preparation for that.

This makes them usable under sysvinit as PID 1 without requiring any
symlinks.

This avoids /sbin/init going missing when switching from systemd-sysv to
sysvinit. While at it, add a Replaces: upstart.

Closes: #751589

The runit-run package has been removed from the archive a long time ago.

since this breaks dist-upgrades from wheezy when switching from sysvinit
to systemd-sysv as default init. While downgrading the Pre-Depends in
sysvinit would have been an alternative, dropping the Conflicts and only
keeping the Replaces was deemed the lesser evil.

Closes: #748355

Closes: #746351

Closes: #747741

Closes: #748311

Patches backported from current upstream.

LP: #1313522

Fixes long shutdown times when using a systemd user session

Our debian/gbp.conf disables gbp-pq patch numbers, adjust README.source
accordingly.

See 6b3ad962

That patch is more general and will go away when we move to newer upstream
versions.

With the changes in 2d54bc37 this script
is no longer necessary.

The cgroup handling has been reworked in v205 and logind no longer
creates cgroup hierarchies on its own. That means that the standalone
logind is no longer functional without support from systemd (or an
equivalent cgroup manager).

Conflicts:
	debian/changelog

This pam config file is used by libpam-systemd/systemd-logind when
launching systemd user instances.

See 6b3ad962

Upstream renamed systemd-random-seed-load.service to
systemd-random.service.

since we don't want a hard dependency on kmod e.g. for container
installations.

as systemd-sysctl no longer reads /etc/sysctl.conf