Bug#832336: jessie-pu: package systemd/215-17+deb8u5

[Michael Biebl]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian.org at packages.debian.org
Usertags: pu

Dear release team,

for the upcoming jessie stable release, I'd like to update the systemd
package with the following fixes:

systemd (215-17+deb8u5) stable; urgency=medium

  * Use the right timeout for stop processes we fork. This ensures that
    services are properly killed after a given timeout. (Closes: #813702)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie&id=036d0949c

This patch has been cherry-picked from upstream. It was part of v217, so
has seen quite a bit of testing in unstable/stretch. Not aware of any
regressions caused by that change.

  * Re-enable fsck -l. This avoids that systemd-fsck runs fsck in parallel for
    file systems on the same disk. Parallel fsck can lead to suboptimal
    behaviour on rotational hard disks. This requires util-linux 2.25, so bump
    the dependency accordingly. (Closes: #824963)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie&id=aca6f1a0a

This patch has been cherry-picked from upstream. It was part of v217, so
has seen quite a bit of testing in unstable/stretch. Not aware of any
regressions caused by that change.


  * Don't reset log level to NOTICE if we get quiet on the kernel cmdline.
    (Closes: #828006)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie&id=c1bf59723

This patch has been cherry-picked from upstream. It was part of v219, so
has seen quite a bit of testing in unstable/stretch. Not aware of any
regressions caused by that change.


  * Fix prepare priority queue comparison function in sd-event.
    Otherwise a disabled event source can get swapped with an enabled one
    and cause a severe sd-event malfunction, breaking the event loop.
    (Closes: #789796)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie&id=3272c6b98


This patch has been cherry-picked from upstream. It was part of v227, so
has seen quite a bit of testing in unstable/stretch.
It's a rather annoying/important bug fix, because once systemd got in
this confused state, it was busy looping and could hog your CPU.

  * Update links to kernel.org cgroup documentation.
    The systemd.resource-control man page had references to /cgroups/ which
    moved to /cgroup-v1/. (Closes: #819970)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie&id=d5e94d3fb

This patch has been cherry-picked from upstream. It was part of v230.
Small documentation update with no regression potential.


  * Don't start console-getty.service when /dev/console is missing.
    Avoids repeated unsuccessful start attempts of agetty inside (docker)
    containers. (Closes: #829537)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie&id=51d6e161e

This patch has been cherry-picked from upstream. It was part of v220, so
has seen quite a bit of testing in unstable/stretch. Very low regression
potential.

  * getty-static.service: Only start if we have a working VC subsystem.
    Use ConditionPathExists=/dev/tty0, the same check as in getty at .service,
    to determine whether we have a functional VC subsystem and we should
    start any gettys. (Closes: #824779)

http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=jessie&id=95dc10016

getty-static.service is a Debian specific addition, so this change is
not an upstream cherry-pick. This fix hasn't been uploaded to unstable
yet, but is atm only committed to master and pending. So strictly
speaking it violates the stable upload policy.
The one-line fix seemed obvious enough though to include it in the
upcoming jessie release and not defer for another cycle.
If you have any concerns regarding this change, I'm happy to back it out
again. It's a small fix which mostly helps LXC containers, which don't
have a real VC subsystem but start some pseudo-ttys on tty1-tty4. So the
check for /dev/tty2 was wrong. We had a discussion with systemd upstream
who recommends to test for /dev/tty0 as indicator for a working VC
subsystem.

 -- Michael Biebl <biebl at debian.org>  Sun, 24 Jul 2016 11:58:28 +0200


The complete debdiff is attached as well.

Thanks for considering,
Michael

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: systemd_215-17+deb8u5.debdiff
Type: text/x-diff
Size: 22425 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160724/60b23da5/attachment-0001.diff>