Package: systemd; Maintainer for systemd is Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>; Source for systemd is src:systemd (PTS, buildd, popcon).
Reported by: Michael Stapelberg <stapelberg@debian.org>
Date: Mon, 24 Sep 2012 11:09:02 UTC
Severity: important
Tags: patch
Found in version systemd/44-4
Fixed in version systemd/44-5
Done: Michael Biebl <biebl@debian.org>
Bug is archived. No further changes may be made.
View this report as an mbox folder, status mbox, maintainer mbox
Report forwarded
to debian-bugs-dist@lists.debian.org, Tollef Fog Heen <tfheen@debian.org>:
Bug#688635; Package systemd.
(Mon, 24 Sep 2012 11:09:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Stapelberg <stapelberg@debian.org>:
New Bug report received and forwarded. Copy sent to Tollef Fog Heen <tfheen@debian.org>.
(Mon, 24 Sep 2012 11:09:04 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
Package: systemd
Version: 44-4
Severity: important
Hi,
I noticed that libvirt virtual machines are placed in the user’s session
by default, so I installed a proper libvirtd.service:
$ cat <<EOF >/etc/systemd/system/libvirtd.service
# NB we don't use socket activation. When libvirtd starts it will
# spawn any virtual machines registered for autostart. We want this
# to occur on every boot, regardless of whether any client connects
# to a socket. Thus socket activation doesn't have any benefit
[Unit]
Description=Virtualization daemon
After=udev.target
After=avahi.target
After=dbus.target
Before=libvirt-guests.service
[Service]
KillMode=process
ExecStart=/usr/sbin/libvirtd
ExecReload=/bin/kill -HUP $MAINPID
# Override the maximum number of opened files
#LimitNOFILE=2048
[Install]
WantedBy=multi-user.target
EOF
$ systemctl stop libvirt-bin.service
$ systemctl stop libvirt-guests.service
$ killall libvirtd
$ systemctl mask libvirt-bin.service
$ systemctl mask libvirt-guests.service
$ systemctl daemon-reload
$ systemctl enable libvirtd.service
$ systemctl start libvirtd.service
Now, when I create a VM, it will be placed in the cgroup of
libvirtd.service, as expected:
$ systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
Active: active (running) since Mon, 24 Sep 2012 12:25:14 +0200; 1s ago
Main PID: 24130 (libvirtd)
CGroup: name=systemd:/system/libvirtd.service
└ 24130 /usr/sbin/libvirtd
$ virsh -c qemu:///system create /etc/libvirt/qemu/test2.xml
Domain test2 created from /etc/libvirt/qemu/test2.xml
$ systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
Active: active (running) since Mon, 24 Sep 2012 12:25:14 +0200; 33s ago
Main PID: 24130 (libvirtd)
CGroup: name=systemd:/system/libvirtd.service
├ 24130 /usr/sbin/libvirtd
└ 24253 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -...
However, when I and start libvirtd.service, the VMs are killed because
systemd cleans up the cgroups on start:
$ systemctl stop libvirtd.service
$ systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
Active: inactive (dead) since Mon, 24 Sep 2012 12:26:54 +0200; 700ms ago
Process: 24326 ExecStart=/usr/sbin/libvirtd (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/libvirtd.service
└ 24456 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -...
$ ps auxf | grep 24456
root 24492 20 0 0.0 0.0 | \_ grep 24456
121 24456 20 0 2.0 0.1 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -uuid 7ed8b939-8e56-3083-c63a-8b7a6ba15182 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/test2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
$ systemctl start libvirtd.service
$ ps auxf | grep 24456
root 24610 20 0 0.0 0.0 | \_ grep 24456
See also https://bugzilla.redhat.com/show_bug.cgi?id=805942. From the
Fedora packaging, I extracted their patch for it and applied it to our
package (find it attached). With that patch, the problem does no longer
occur:
$ systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
Active: active (running) since Mon, 24 Sep 2012 12:27:03 +0200; 11min ago
Main PID: 24502 (libvirtd)
CGroup: name=systemd:/system/libvirtd.service
└ 24502 /usr/sbin/libvirtd
$ virsh -c qemu:///system create /etc/libvirt/qemu/test2.xml
Domain test2 created from /etc/libvirt/qemu/test2.xml
$ systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
Active: active (running) since Mon, 24 Sep 2012 12:27:03 +0200; 11min ago
Main PID: 24502 (libvirtd)
CGroup: name=systemd:/system/libvirtd.service
├ 19256 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -...
└ 24502 /usr/sbin/libvirtd
$ systemctl stop libvirtd.service
$ systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
Active: inactive (dead) since Mon, 24 Sep 2012 12:38:17 +0200; 916ms ago
Main PID: 24502 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/libvirtd.service
└ 19256 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -...
$ systemctl status libvirtd.service
libvirtd.service - Virtualization daemon
Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
Active: active (running) since Mon, 24 Sep 2012 12:38:21 +0200; 2s ago
Main PID: 19293 (libvirtd)
CGroup: name=systemd:/system/libvirtd.service
├ 19256 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -...
└ 19293 /usr/sbin/libvirtd
I have been running systemd with this patch for over a month now and
could not find any negative side-effects. I suggest we apply the patch
and get a freeze exception.
I’ve set the severity to important because running into this issue is
very unpleasant on production systems and might lead to severe data
loss.
Thanks!
[F17-disable-killing-on-entering-START_PRE-START.patch (text/x-diff, attachment)]
[Message part 3 (text/plain, inline)]
-- Best regards, Michael
Information forwarded
to debian-bugs-dist@lists.debian.org, Tollef Fog Heen <tfheen@debian.org>:
Bug#688635; Package systemd.
(Sat, 13 Oct 2012 21:51:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Guido Günther <agx@sigxcpu.org>:
Extra info received and forwarded to list. Copy sent to Tollef Fog Heen <tfheen@debian.org>.
(Sat, 13 Oct 2012 21:51:03 GMT) (full text, mbox, link).
Message #10 received at 688635@bugs.debian.org (full text, mbox, reply):
On Mon, Sep 24, 2012 at 12:51:39PM +0200, Michael Stapelberg wrote:
> Package: systemd
> Version: 44-4
> Severity: important
>
>
> Hi,
>
> I noticed that libvirt virtual machines are placed in the user’s session
> by default, so I installed a proper libvirtd.service:
>
> $ cat <<EOF >/etc/systemd/system/libvirtd.service
> # NB we don't use socket activation. When libvirtd starts it will
> # spawn any virtual machines registered for autostart. We want this
> # to occur on every boot, regardless of whether any client connects
> # to a socket. Thus socket activation doesn't have any benefit
>
> [Unit]
> Description=Virtualization daemon
> After=udev.target
> After=avahi.target
> After=dbus.target
> Before=libvirt-guests.service
>
> [Service]
> KillMode=process
> ExecStart=/usr/sbin/libvirtd
> ExecReload=/bin/kill -HUP $MAINPID
> # Override the maximum number of opened files
> #LimitNOFILE=2048
>
> [Install]
> WantedBy=multi-user.target
> EOF
>
> $ systemctl stop libvirt-bin.service
> $ systemctl stop libvirt-guests.service
> $ killall libvirtd
> $ systemctl mask libvirt-bin.service
> $ systemctl mask libvirt-guests.service
> $ systemctl daemon-reload
> $ systemctl enable libvirtd.service
> $ systemctl start libvirtd.service
>
> Now, when I create a VM, it will be placed in the cgroup of
> libvirtd.service, as expected:
>
> $ systemctl status libvirtd.service
> libvirtd.service - Virtualization daemon
> Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
> Active: active (running) since Mon, 24 Sep 2012 12:25:14 +0200; 1s ago
> Main PID: 24130 (libvirtd)
> CGroup: name=systemd:/system/libvirtd.service
> └ 24130 /usr/sbin/libvirtd
>
> $ virsh -c qemu:///system create /etc/libvirt/qemu/test2.xml
> Domain test2 created from /etc/libvirt/qemu/test2.xml
>
> $ systemctl status libvirtd.service
> libvirtd.service - Virtualization daemon
> Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
> Active: active (running) since Mon, 24 Sep 2012 12:25:14 +0200; 33s ago
> Main PID: 24130 (libvirtd)
> CGroup: name=systemd:/system/libvirtd.service
> ├ 24130 /usr/sbin/libvirtd
> └ 24253 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -...
>
> However, when I and start libvirtd.service, the VMs are killed because
> systemd cleans up the cgroups on start:
>
> $ systemctl stop libvirtd.service
> $ systemctl status libvirtd.service
> libvirtd.service - Virtualization daemon
> Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
> Active: inactive (dead) since Mon, 24 Sep 2012 12:26:54 +0200; 700ms ago
> Process: 24326 ExecStart=/usr/sbin/libvirtd (code=exited, status=0/SUCCESS)
> CGroup: name=systemd:/system/libvirtd.service
> └ 24456 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -...
>
> $ ps auxf | grep 24456
> root 24492 20 0 0.0 0.0 | \_ grep 24456
> 121 24456 20 0 2.0 0.1 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -uuid 7ed8b939-8e56-3083-c63a-8b7a6ba15182 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/test2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3
> $ systemctl start libvirtd.service
> $ ps auxf | grep 24456
> root 24610 20 0 0.0 0.0 | \_ grep 24456
>
> See also https://bugzilla.redhat.com/show_bug.cgi?id=805942. From the
> Fedora packaging, I extracted their patch for it and applied it to our
> package (find it attached). With that patch, the problem does no longer
> occur:
>
> $ systemctl status libvirtd.service
> libvirtd.service - Virtualization daemon
> Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
> Active: active (running) since Mon, 24 Sep 2012 12:27:03 +0200; 11min ago
> Main PID: 24502 (libvirtd)
> CGroup: name=systemd:/system/libvirtd.service
> └ 24502 /usr/sbin/libvirtd
>
> $ virsh -c qemu:///system create /etc/libvirt/qemu/test2.xml
> Domain test2 created from /etc/libvirt/qemu/test2.xml
>
> $ systemctl status libvirtd.service
> libvirtd.service - Virtualization daemon
> Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
> Active: active (running) since Mon, 24 Sep 2012 12:27:03 +0200; 11min ago
> Main PID: 24502 (libvirtd)
> CGroup: name=systemd:/system/libvirtd.service
> ├ 19256 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -...
> └ 24502 /usr/sbin/libvirtd
>
> $ systemctl stop libvirtd.service
> $ systemctl status libvirtd.service
> libvirtd.service - Virtualization daemon
> Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
> Active: inactive (dead) since Mon, 24 Sep 2012 12:38:17 +0200; 916ms ago
> Main PID: 24502 (code=exited, status=0/SUCCESS)
> CGroup: name=systemd:/system/libvirtd.service
> └ 19256 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -...
>
> $ systemctl status libvirtd.service
> libvirtd.service - Virtualization daemon
> Loaded: loaded (/etc/systemd/system/libvirtd.service; enabled)
> Active: active (running) since Mon, 24 Sep 2012 12:38:21 +0200; 2s ago
> Main PID: 19293 (libvirtd)
> CGroup: name=systemd:/system/libvirtd.service
> ├ 19256 /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 256 -smp 1,sockets=1,cores=1,threads=1 -name test2 -...
> └ 19293 /usr/sbin/libvirtd
>
>
> I have been running systemd with this patch for over a month now and
> could not find any negative side-effects. I suggest we apply the patch
> and get a freeze exception.
>
> I’ve set the severity to important because running into this issue is
> very unpleasant on production systems and might lead to severe data
> loss.
>
> Thanks!
>
> Description: disable killing on entering START_PRE, START
> The killing worked fine with the added "control" sub-cgroup, but that
> brought other problems:
> https://bugzilla.redhat.com/show_bug.cgi?id=816842
> The "control" sub-cgroup had to be removed. In order not to reintroduce
> https://bugzilla.redhat.com/show_bug.cgi?id=805942, comment out the
> killing for F17 GA. Hopefully we'll get a proper fix later.
>
> Almost a revert of commit 8f53a7b8ea9ba505f8fefe4df4aaa5a8aab1e2eb
> "service: brutally slaughter processes that are running in the cgroup
> when we enter START_PRE and START"
> Author: Michal Schmidt <mschmidt@redhat.com>
> Origin: vendor
> Bug: https://bugzilla.redhat.com/show_bug.cgi?id=816842
> Forwarded: not-needed
> Reviewed-by: Michael Stapelberg <stapelberg@debian.org>
> Last-Update: 2012-09-24
> ---
> This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
> Index: systemd-44/src/service.c
> ===================================================================
> --- systemd-44.orig/src/service.c 2012-03-12 21:49:16.000000000 +0100
> +++ systemd-44/src/service.c 2012-09-24 12:30:27.238541632 +0200
> @@ -2094,7 +2094,8 @@
> /* We want to ensure that nobody leaks processes from
> * START_PRE here, so let's go on a killing spree, People
> * should not spawn long running processes from START_PRE. */
> - cgroup_bonding_kill_list(UNIT(s)->cgroup_bondings, SIGKILL, true, NULL);
> + // F17, bz816842, bz805942
> + //cgroup_bonding_kill_list(UNIT(s)->cgroup_bondings, SIGKILL, true, NULL);
>
> if (s->type == SERVICE_FORKING) {
> s->control_command_id = SERVICE_EXEC_START;
> @@ -2168,7 +2169,8 @@
>
> /* Before we start anything, let's clear up what might
> * be left from previous runs. */
> - cgroup_bonding_kill_list(UNIT(s)->cgroup_bondings, SIGKILL, true, NULL);
> + // F17, bz816842, bz805942
> + //cgroup_bonding_kill_list(UNIT(s)->cgroup_bondings, SIGKILL, true, NULL);
>
> s->control_command_id = SERVICE_EXEC_START_PRE;
>
It seems this is the fix that went into upstream git to resolve this:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=ecedd90fcdf647f9a7b56b4934b65e30b2979b04
Would be great to have this fixed since newer libvirtd ship service
files by default an so currently all VMs get killed during package
upgrade which doesn't happen with sysvinit.
Cheers,
-- Guido
>
>
> --
> Best regards,
> Michael
Information forwarded
to debian-bugs-dist@lists.debian.org, Tollef Fog Heen <tfheen@debian.org>:
Bug#688635; Package systemd.
(Sat, 13 Oct 2012 22:51:07 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Stapelberg <stapelberg@debian.org>:
Extra info received and forwarded to list. Copy sent to Tollef Fog Heen <tfheen@debian.org>.
(Sat, 13 Oct 2012 22:51:08 GMT) (full text, mbox, link).
Message #15 received at 688635@bugs.debian.org (full text, mbox, reply):
Hi Guido, Guido Günther <agx@sigxcpu.org> writes: > It seems this is the fix that went into upstream git to resolve this: > > http://cgit.freedesktop.org/systemd/systemd/commit/?id=ecedd90fcdf647f9a7b56b4934b65e30b2979b04 As far as I understand the corresponding Fedora bugreport[1], the commit you referred to was reverted because it triggered additional problems. I have pulled the patch I attached to my original message out of Fedora’s systemd packaging git repository. This patch is what worked for them and what worked for me (for months). I strongly recommend to use that and NOT the commit you referenced. Thanks for the heads-up about libvirt, I see that libvirt 0.10.2-4 in experimental is indeed shipping service files: http://packages.debian.org/experimental/amd64/libvirt-bin/filelist The file contains KillMode=process, so with the patch from my original message, it should work. -- Best regards, Michael
Information forwarded
to debian-bugs-dist@lists.debian.org, Tollef Fog Heen <tfheen@debian.org>:
Bug#688635; Package systemd.
(Sat, 13 Oct 2012 22:57:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Michael Stapelberg <stapelberg@debian.org>:
Extra info received and forwarded to list. Copy sent to Tollef Fog Heen <tfheen@debian.org>.
(Sat, 13 Oct 2012 22:57:03 GMT) (full text, mbox, link).
Message #20 received at 688635@bugs.debian.org (full text, mbox, reply):
Hi Guido, Michael Stapelberg <stapelberg@debian.org> writes: > As far as I understand the corresponding Fedora bugreport[1], the commit With [1] being https://bugzilla.redhat.com/show_bug.cgi?id=805942#c28 — sorry for forgetting. (This reference is also wrong in the patchfile) -- Best regards, Michael
Added tag(s) patch.
Request was from Michael Stapelberg <stapelberg@debian.org>
to control@bugs.debian.org.
(Sun, 14 Oct 2012 10:39:05 GMT) (full text, mbox, link).
Reply sent
to Michael Biebl <biebl@debian.org>:
You have taken responsibility.
(Thu, 25 Oct 2012 20:51:18 GMT) (full text, mbox, link).
Notification sent
to Michael Stapelberg <stapelberg@debian.org>:
Bug acknowledged by developer.
(Thu, 25 Oct 2012 20:51:18 GMT) (full text, mbox, link).
Message #27 received at 688635-close@bugs.debian.org (full text, mbox, reply):
Source: systemd
Source-Version: 44-5
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 688635@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <biebl@debian.org> (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 25 Oct 2012 21:41:23 +0200
Source: systemd
Binary: systemd systemd-sysv libpam-systemd systemd-gui libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev
Architecture: source amd64
Version: 44-5
Distribution: unstable
Urgency: low
Maintainer: Tollef Fog Heen <tfheen@debian.org>
Changed-By: Michael Biebl <biebl@debian.org>
Description:
libpam-systemd - system and service manager - PAM module
libsystemd-daemon-dev - systemd utility library - development files
libsystemd-daemon0 - systemd utility library
libsystemd-id128-0 - systemd 128 bit ID utility library
libsystemd-id128-dev - systemd 128 bit ID utility library - development files
libsystemd-journal-dev - systemd journal utility library - development files
libsystemd-journal0 - systemd journal utility library
libsystemd-login-dev - systemd login utility library - development files
libsystemd-login0 - systemd login utility library
systemd - system and service manager
systemd-gui - system and service manager - GUI
systemd-sysv - system and service manager - SysV links
Closes: 624599 650382 668344 686115 688635 690916
Changes:
systemd (44-5) unstable; urgency=low
.
* Team upload.
.
[ Tollef Fog Heen ]
* disable killing on entering START_PRE, START, thanks to Michael
Stapelberg for patch. This avoids killing VMs run through libvirt
when restarting libvirtd. Closes: #688635.
* Avoid reloading services when shutting down, since that won't work and
makes no sense. Thanks to Michael Stapelberg for the patch.
Closes: #624599.
* Try to determine which init scripts support the reload action
heuristically. Closes: #686115, #650382.
.
[ Michael Biebl ]
* Update Vcs-* fields, the Git repository is hosted on alioth now. Set the
default branch to "debian".
* Avoid reload and (re)start requests during early boot which can lead to
deadlocks. Closes: #624599
* Make systemd-cgroup work even if not all cgroup mounts are available on
startup. Closes: #690916
* Fix typos in the systemd.path and systemd.unit man page. Closes: #668344
* Add watch file to track new upstream releases.
Checksums-Sha1:
a2934df2b077f3dc09eb55424d867549b03b4724 2882 systemd_44-5.dsc
66303b45b773b49f5aac668f34584e3ae6608ac4 26277 systemd_44-5.debian.tar.gz
b32a530bb3d5dfbdb7936de839dff1c9336fa13f 1445478 systemd_44-5_amd64.deb
f0ae2ee1dc4147b75224fe4a1811870fe70e5410 14026 systemd-sysv_44-5_amd64.deb
fcd6bee8733ec6965abbbb1a7bb8af57a96e11fe 31476 libpam-systemd_44-5_amd64.deb
b0899be717965874ec6049ceff25682b78781238 65896 systemd-gui_44-5_amd64.deb
bcda472ef70290c8ccecc968e2c86137aed41578 28218 libsystemd-login0_44-5_amd64.deb
cce8cdea872aecf214db4284f96fb225c92bedbf 10766 libsystemd-login-dev_44-5_amd64.deb
123f052fb906a7bdda291efcba573ead3e42f40d 13802 libsystemd-daemon0_44-5_amd64.deb
699117f66298737eabc7a6c7d9ead9d8773b0d52 13244 libsystemd-daemon-dev_44-5_amd64.deb
730bf11b0a8a6e3a5339ea77fe7970a1516689c6 41360 libsystemd-journal0_44-5_amd64.deb
c9f4c37c61a63df800beb9ddd4a6f790db62599e 10372 libsystemd-journal-dev_44-5_amd64.deb
ed1288c5e58ecb201f017681d4c758c46788bea6 19916 libsystemd-id128-0_44-5_amd64.deb
d1ec2234116fe08cf84ffb0985ebb233e73ea755 9740 libsystemd-id128-dev_44-5_amd64.deb
Checksums-Sha256:
a4af9bb9407313339b51717242f7f010761933c32767a03e7e4ac99d48b12e63 2882 systemd_44-5.dsc
3c0a6fc22cd9656e3bb039b4e12f95899e2702567ebf9da6294c9bb3e83a9b57 26277 systemd_44-5.debian.tar.gz
21da64797703fe3de4eacaf092e1b69e96d44c94932599903b93d9e665fa4ca2 1445478 systemd_44-5_amd64.deb
37014d5338b1a19b17b877fc9d436d6f30ad3d9692aae08b2485142ff8b7747f 14026 systemd-sysv_44-5_amd64.deb
282b29ee4d6015e3f2d0a4e56b99fc763600c7aeed143073a4206cc79a55e625 31476 libpam-systemd_44-5_amd64.deb
1975c1c2b63e181285697fedd0a5e90ebcc580ecf11506123c27a1df6e236a2e 65896 systemd-gui_44-5_amd64.deb
8215c858b6235e0ca81d1f2ab1788d4d415f9438dc7148c97f196b293ca7a012 28218 libsystemd-login0_44-5_amd64.deb
c3bb0db8c22fde5fe198368ab15801bd9ef1da2ab2b92f87fa0071325bbe83d6 10766 libsystemd-login-dev_44-5_amd64.deb
864de664fcd06e531fad0cf6f3da2538eeb6771ea1299f30ee3aa15599f17453 13802 libsystemd-daemon0_44-5_amd64.deb
8ad7b09dbbeef7b9c452d7407afb406c6254f2996aa910f0fc8f262b241c4407 13244 libsystemd-daemon-dev_44-5_amd64.deb
8bb0408bba9efee4202fb0fdb2e981335604cc57522f34275ef014987e231e45 41360 libsystemd-journal0_44-5_amd64.deb
cf6cde74256219132152a81b29938125a82f90523ad434df12fa85cafbb72304 10372 libsystemd-journal-dev_44-5_amd64.deb
39c04d5d87708657d1ef16e324b187e7b4a361aec214ee69e2b0d52e2554228b 19916 libsystemd-id128-0_44-5_amd64.deb
05c16ce7940f1521d2623f727a353ec38bb2cd2e90471f9c6167db3ef47aba76 9740 libsystemd-id128-dev_44-5_amd64.deb
Files:
8565480f819ad09a0ff049a7d3e5ef43 2882 admin extra systemd_44-5.dsc
81b74e50b9075bfc72474e1f7c4040b3 26277 admin extra systemd_44-5.debian.tar.gz
7b26f209e32b22cfda1138cec2bd98eb 1445478 admin extra systemd_44-5_amd64.deb
07aeec9fede157c732660e44806441a1 14026 admin extra systemd-sysv_44-5_amd64.deb
3b516bf70a1ae2d88d34e3ab4790a1fc 31476 admin extra libpam-systemd_44-5_amd64.deb
99c4618858e3deed96e3ceff9e190da6 65896 admin extra systemd-gui_44-5_amd64.deb
7b5f196e2e370aa2b682d25a831bb1b3 28218 libs extra libsystemd-login0_44-5_amd64.deb
658e68371286a6fde6eabcf9a933a0b5 10766 libdevel extra libsystemd-login-dev_44-5_amd64.deb
31b043a971ae61ffcbf4d97ae6d895bf 13802 libs extra libsystemd-daemon0_44-5_amd64.deb
4801c1b269bb6fd8fc09f22afe1d0987 13244 libdevel extra libsystemd-daemon-dev_44-5_amd64.deb
138c438ff63df661aecd3e9ece076407 41360 libs extra libsystemd-journal0_44-5_amd64.deb
6bf3cc427487c04f4c994c314d25c4f4 10372 libdevel extra libsystemd-journal-dev_44-5_amd64.deb
23fb0148f3544f8988f78836713df09d 19916 libs extra libsystemd-id128-0_44-5_amd64.deb
c23cf694cbd5c977d637decf5e980eba 9740 libdevel extra libsystemd-id128-dev_44-5_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQiZzPAAoJEGrh3w1gjyLcY6YP+gJVs/l2vKdqESnqNjTg+1y/
SIJfF3PABF2Jo5/0xyS+mtRVkp5mF//8FP1r96rJtk7mvclAOvdmYS/26lZg214x
qfkgwN5p+QnuFWpdlwt9ijfK5DoBMunFB9bOtQJjUoOrAfGiE36wgesfClXD5yJ+
anT7P7Pcfas9ZVXa10PV6evmXBTLXt7v+/NYVL+TI0sTXY8yhzCUqD08wg0wIsFq
kflFYqtbr20xbancXClRmC8HwF75kCK+I6qzbU6rJUHRDoW1Xp0LkCO9S1UlaJj9
YVsuw6gCpym9sp4Q5j7z6JNFK/AN3FvPbPnAvA/L10ESJwtEo5S+vMmq5C7B4f9G
1nh05aKDIHre/AO50lPG8fQF8M5+appNEb6ccZ72sgzYO6Dh8LgfxZZtuVC2P9jb
r2DCPaALEqwT87QLNsV8VC1VjX2QZuwiOwHeJhnYjc5PWU0NpMPwFxFALgbCz/v2
p2nvGeZp3whhhYAx+91yNrAAeAvv4OF0M1wvXhsf0KIkqAWsXuTSmaPvxHDS02SG
t3A/yBime0XrU0G5DmEsfqGa0iRgNBd7GBYFgbndB9+CCIBAqDK4kUupEFiSdCU3
1q0kzgvIt0XOGnOkrUoxK65S+vwVtVMib8DY1E7u3wYMuCeLnngg7MV8AZJjz5t0
1XZjarS5VXMthQszuwhM
=0dyv
-----END PGP SIGNATURE-----
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Tue, 11 Dec 2012 07:30:11 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.