Instead of tracking git upstream directly, the upstream branch now
contains the contents of the orig tarball available at
http://www.freedesktop.org/software/systemd/

This is necessary to properly deal with files like units/syslog.target,
which would not be deleted when merging otherwise.

This is a followup commit for e89ec25a

Instead of installing and removing tmp.mount later via debian/rules,
don't install it in the first place. This is a followup commit for
d151046c

closes #634472

This bug was introduced in aa57b6c5

We need to initialize the DBusError struct before it is used/freed.

from Ubuntu’s patches/pam-check-runtime-dir-user.patch:

From: Martin Pitt <martinpitt@gnome.org>
Date: Wed, 13 Nov 2013 13:02:28 +0100
Subject: [PATCH] pam: Check $XDG_RUNTIME_DIR owner

http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html requires
that $XDG_RUNTIME_DIR "MUST be owned by the user, and he MUST be the only one
having read and write access to it.".

Don't set an existing $XDG_RUNTIME_DIR in the PAM module if it isn't owned by
the session user. Otherwise su sessions get a runtime dir from a different user
which leads to either permission errors or scribbling over the other user's
files.

Bug-Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=753882
Bug-Ubuntu: https://launchpad.net/bugs/1197395

closes: #739679

(Following Ben Hutching’s recommendation.)

closes #725422

closes #739113

from /etc/default/rcS and /etc/default/tmpfs, i.e. enable tmp.mount

Closes: #738687

fix systemctl enable/disable/… error message “Failed to issue method call: No such file or directory”

For real. This commit was accidentally reverted when merging
upstream-fixes into the debian branch *shakes fist at gitpkg*.

Closes: #738843

see #738799

closes #738723

This removes the closes: on the bootstrap bug, because that issue is not
actually resolved with the current patch.

http://bugs.debian.org/738316

This fixes the error message "Unknown or unsupported cgroup attribute
CPUShares".

Usually the network is stopped before filesystems are umounted.
Ordering network filesystems before remote-fs.target means that their
unmounting will be performed earlier, and can terminate sucessfully.

https://bugs.freedesktop.org/show_bug.cgi?id=70002

Unit names were mangled in function enable_unit only when dbus was
used. This patch adds mangling also when the dbus is not in use.

This makes it possible to say e.g.:
   systemctl --root=/path enable cups
without spelling cups.service out in full.

Patch by Daniel Schepler

http://bugs.debian.org/738316

This fixes the error message "Unknown or unsupported cgroup attribute
CPUShares".

Usually the network is stopped before filesystems are umounted.
Ordering network filesystems before remote-fs.target means that their
unmounting will be performed earlier, and can terminate sucessfully.

https://bugs.freedesktop.org/show_bug.cgi?id=70002

No such file or directory”

The bug affected only non-native services, i.e. LSB SysV init scripts,
with isc-dhcp-server.service being an example for this commit message.

The bug was introduced with commit
fdcb1bce. The issue is that
enable_unit() would not return even though the SysV init script was
disabled by enable_sysv_units(). enable_unit() then tried to
disable a native systemd unit called isc-dhcp-server.service, even
though there is no such native unit. This is what caused the “no such
file or directory” error message.

Closes: #734809