Debian Bug report logs - #758902
systemd: Please make ^C interrupt systemd-fsck

version graph

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: Alberto Fuentes <pajaro@gmail.com>

Date: Fri, 22 Aug 2014 17:12:02 UTC

Severity: wishlist

Tags: fixed-upstream

Merged with 772425

Found in versions 215, systemd/208-6

Fixed in versions systemd/219-3, systemd/220-2

Done: Martin Pitt <mpitt@debian.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, pajaro@gmail.com, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Fri, 22 Aug 2014 17:12:07 GMT) (full text, mbox, link).


Acknowledgement sent to Alberto Fuentes <pajaro@gmail.com>:
New Bug report received and forwarded. Copy sent to pajaro@gmail.com, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Fri, 22 Aug 2014 17:12:07 GMT) (full text, mbox, link).


Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Alberto Fuentes <pajaro@gmail.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: systemd: Please make ^C interrupt systemd-fsck
Date: Fri, 22 Aug 2014 19:09:56 +0200
[Message part 1 (text/plain, inline)]
Package: systemd
Version: 208-6
Severity: important

Please consider adding ctrl + C or whatever other means to cancel fsck during
startup...

By default, the ext partitions are checked for errors after 30 reboots. If the
disk is big, it can take 1+ hours without any other option than to wait.

This is a regression after migration to systemd, since it used to work this way

Thanks for considering



-- Package-specific info:

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  acl                  2.2.52-1
ii  adduser              3.113+nmu3
ii  initscripts          2.88dsf-53.3
ii  libacl1              2.2.52-1
ii  libaudit1            1:2.3.7-1
ii  libblkid1            2.20.1-5.8
ii  libc6                2.19-9
ii  libcap2              1:2.24-4
ii  libcap2-bin          1:2.24-4
ii  libcryptsetup4       2:1.6.4-4
ii  libdbus-1-3          1.8.6-1
ii  libgcrypt11          1.5.4-2
ii  libkmod2             18-1
ii  liblzma5             5.1.1alpha+20120614-2
ii  libpam0g             1.1.8-3
ii  libselinux1          2.3-1
ii  libsystemd-daemon0   208-6
ii  libsystemd-journal0  208-6
ii  libsystemd-login0    208-6
ii  libudev1             208-6
ii  libwrap0             7.6.q-25
ii  sysv-rc              2.88dsf-53.3
ii  udev                 208-6
ii  util-linux           2.20.1-5.8

Versions of packages systemd recommends:
ii  libpam-systemd  208-6

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- debconf-show failed
[systemd-delta.txt (text/plain, attachment)]
[systemd-analyze-dump.txt (text/plain, attachment)]
[dsh-enabled.txt (text/plain, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Fri, 22 Aug 2014 18:12:07 GMT) (full text, mbox, link).


Acknowledgement sent to Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Fri, 22 Aug 2014 18:12:07 GMT) (full text, mbox, link).


Message #10 received at 758902@bugs.debian.org (full text, mbox, reply):

From: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
To: Alberto Fuentes <pajaro@gmail.com>, 758902@bugs.debian.org
Subject: Re: Bug#758902: systemd: Please make ^C interrupt systemd-fsck
Date: Fri, 22 Aug 2014 19:37:22 +0200
On Fri, Aug 22, 2014 at 07:09:56PM +0200, Alberto Fuentes wrote:
> Package: systemd
> Version: 208-6
> Severity: important
> 
> Please consider adding ctrl + C or whatever other means to cancel fsck during
> startup...
http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n562

Zbyszek



Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Fri, 22 Aug 2014 19:09:08 GMT) (full text, mbox, link).


Acknowledgement sent to alberto fuentes <pajaro@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Fri, 22 Aug 2014 19:09:08 GMT) (full text, mbox, link).


Message #15 received at 758902@bugs.debian.org (full text, mbox, reply):

From: alberto fuentes <pajaro@gmail.com>
To: 758902@bugs.debian.org
Subject: Re: Bug#758902: systemd: Please make ^C interrupt systemd-fsck
Date: Fri, 22 Aug 2014 21:06:41 +0200
> http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n562

This bug has already bitten me 3 times. It stops the show for the time
it takes to do the fsck

I guess the workaround is to disable the automatic check of ext and
remember to do it manually from time to time or risk data corruption

I understand theres some reason that makes this bug hard to fix
(probably a safe way to stop a fsck in the middle or something) but
there is a very easy to implement (by upstream at least) workaround.
Wait 3 secs before launching the fsck to allow you to break it before
it starts. Right now not even a reboot will help.

Is there a way to make them aware of this easy workaround that would
take them as much at 15 min to implement? :)

Thanks for considering



Severity set to 'wishlist' from 'important' Request was from Michael Biebl <biebl@debian.org> to control@bugs.debian.org. (Fri, 22 Aug 2014 23:30:04 GMT) (full text, mbox, link).


Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Sat, 23 Aug 2014 13:18:05 GMT) (full text, mbox, link).


Acknowledgement sent to alberto fuentes <pajaro@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Sat, 23 Aug 2014 13:18:05 GMT) (full text, mbox, link).


Message #22 received at 758902@bugs.debian.org (full text, mbox, reply):

From: alberto fuentes <pajaro@gmail.com>
To: 758902@bugs.debian.org
Cc: Michael Biebl <biebl@debian.org>
Subject: wishlist?
Date: Sat, 23 Aug 2014 15:15:24 +0200
would you kindly explain the downgrade of severity of the bug?

I would not expect a migration of this kind without bumps, but it took
3 years in 2002 to add this feature ( #150295 ) and this seems like a
regresion to me 10+ years later

Thanks in advance



Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Sun, 28 Sep 2014 15:45:04 GMT) (full text, mbox, link).


Acknowledgement sent to Samuel Thibault <sthibault@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Sun, 28 Sep 2014 15:45:04 GMT) (full text, mbox, link).


Message #27 received at 758902@bugs.debian.org (full text, mbox, reply):

From: Samuel Thibault <sthibault@debian.org>
To: alberto fuentes <pajaro@gmail.com>, 758902@bugs.debian.org
Cc: Michael Biebl <biebl@debian.org>
Subject: Re: Bug#758902: wishlist?
Date: Sun, 28 Sep 2014 17:41:34 +0200
Hello,

alberto fuentes, le Sat 23 Aug 2014 15:15:24 +0200, a écrit :
> would you kindly explain the downgrade of severity of the bug?
> 
> I would not expect a migration of this kind without bumps, but it took
> 3 years in 2002 to add this feature ( #150295 ) and this seems like a
> regresion to me 10+ years later

I can only concur here, I have just been hit by it.  This is a showstopper in
quite a few cases.  Sometimes I *do need* to get my system to boot timely to get
some information or start a presentation, etc., not after the periodic fsck.

That was the whole point of the allow_cancellation option in e2fsck, which
now does not work any more. So this is not a wishlist, but a regression. It's
actually breaking another package.

Samuel



Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Wed, 05 Nov 2014 05:12:04 GMT) (full text, mbox, link).


Acknowledgement sent to Tim Vaughan <tgvaughan@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Wed, 05 Nov 2014 05:12:04 GMT) (full text, mbox, link).


Message #32 received at 758902@bugs.debian.org (full text, mbox, reply):

From: Tim Vaughan <tgvaughan@gmail.com>
To: 758902@bugs.debian.org
Subject: Re: Bug#758902: wishlist?
Date: Wed, 5 Nov 2014 18:09:47 +1300
I don't generally like adding "me too"s, but in this case I can't
resist.  Today I went to give a public presentation using my
up-to-date Debian Jessie laptop.  I booted the system with just
minutes before the talk was due to start, only to find that this was
the magical 30th boot where fsck is forced.  Without any way to abort
the check, which takes ~10min on my HDD, I had no choice but to run
from room to room begging for another laptop.

While I understand the necessity of regular fscks, occasionally one
needs to boot a system _now_: having an option to delay the check is
certainly more than "wishlist" severity in these situations!

Cheers,
Tim



Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Wed, 05 Nov 2014 11:06:04 GMT) (full text, mbox, link).


Acknowledgement sent to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Wed, 05 Nov 2014 11:06:04 GMT) (full text, mbox, link).


Message #37 received at 758902@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>
To: Tim Vaughan <tgvaughan@gmail.com>, 758902@bugs.debian.org
Subject: Re: Bug#758902: wishlist?
Date: Wed, 05 Nov 2014 12:03:22 +0100
[Message part 1 (text/plain, inline)]
Am 05.11.2014 um 06:09 schrieb Tim Vaughan:
> I don't generally like adding "me too"s, but in this case I can't
> resist.  Today I went to give a public presentation using my
> up-to-date Debian Jessie laptop.  I booted the system with just
> minutes before the talk was due to start, only to find that this was
> the magical 30th boot where fsck is forced.  Without any way to abort
> the check, which takes ~10min on my HDD, I had no choice but to run
> from room to room begging for another laptop.
> 
> While I understand the necessity of regular fscks, occasionally one
> needs to boot a system _now_: having an option to delay the check is
> certainly more than "wishlist" severity in these situations!

It's a feature request and has the same severity as the original bug
report against sysvinit.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Marked as found in versions 215. Request was from Michael Biebl <email@michaelbiebl.de> to 772425-submit@bugs.debian.org. (Sat, 06 Dec 2014 20:21:08 GMT) (full text, mbox, link).


Merged 758902 772425 Request was from Michael Biebl <email@michaelbiebl.de> to 772425-submit@bugs.debian.org. (Sat, 06 Dec 2014 20:21:10 GMT) (full text, mbox, link).


Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Tue, 23 Dec 2014 02:33:14 GMT) (full text, mbox, link).


Acknowledgement sent to Stefan Monnier <monnier@iro.umontreal.ca>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Tue, 23 Dec 2014 02:33:14 GMT) (full text, mbox, link).


Message #46 received at 758902@bugs.debian.org (full text, mbox, reply):

From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Cc: Alberto Fuentes <pajaro@gmail.com>, 758902@bugs.debian.org
Subject: Re: Bug#758902: systemd: Please make ^C interrupt systemd-fsck
Date: Mon, 22 Dec 2014 21:30:38 -0500
> http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n562

This points to line-number 562 in a long TODO list.  Of course, the item
at that line number is unrelated to this bug-report (tho I presume it
was related back when this reply was sent).

I think this is a very nasty regression that will hit relatively few
people but will really piss them off.

But I don't think we should focus exclusively on fsck: C-c should be
usable also to interrupt a "waiting for device to appear" or "waiting
for the network to come up".  So, basically, I think that any thingy
which takes more than N second to complete should be interruptible via
C-c (potentially with a prompt to confirm that the user really intended
to interrupt this operation).

In my experience, systemd has introduced various different *new* ways in
which the boot can get stuck in some long-running "operation" (which
might just be waiting for a timeout).  If we don't want to alienate
users, we should raise the severity of this bug (and broaden its scope).


        Stefan



Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Tue, 23 Dec 2014 12:21:04 GMT) (full text, mbox, link).


Acknowledgement sent to alberto fuentes <pajaro@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Tue, 23 Dec 2014 12:21:04 GMT) (full text, mbox, link).


Message #51 received at 758902@bugs.debian.org (full text, mbox, reply):

From: alberto fuentes <pajaro@gmail.com>
To: 758902@bugs.debian.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Bug#758902: systemd: Please make ^C interrupt systemd-fsck
Date: Tue, 23 Dec 2014 13:19:08 +0100
[Message part 1 (text/plain, inline)]
On Mon, 22 Dec 2014 21:30:38 -0500 Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> > http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n562
>
> This points to line-number 562 in a long TODO list. Of course, the item
> at that line number is unrelated to this bug-report (tho I presume it
> was related back when this reply was sent).

This is the original line:

|* There's currently no way to cancel fsck (used to be possible via C-c or c on the console)|

Its line 659 now

http://cgit.freedesktop.org/systemd/systemd/tree/TODO?id=HEAD#n659


> I think this is a very nasty regression that will hit relatively few
> people but will really piss them off.

Not sure why you think they will be few people affected. I think almost
everybody is going to be hit by this at least once... probably more than
once. Computers have hard drives attached. They are checked at
semi-random intervals. If the hard drives is relatively large, it can
take from 20min to more than 1h to check.

I was biten by this once a month until one time I had to do a
presentation and the computer refused to bootup without checking the
disks, then decided to write the bug and disable checking on the disks
risking corruption
 
> In my experience, systemd has introduced various different *new* ways in
> which the boot can get stuck in some long-running "operation" (which
> might just be waiting for a timeout). If we don't want to alienate
> users, we should raise the severity of this bug (and broaden its scope).

While I agree and something generic and well implemented should be put
in place, i would be well off with a hack to interrupt it.

It would take less than 15 min to implement it to the systemd people to
avoid this 10+ years regresion. Calling a pre-script,or pre-service or
however systemd works

 "echo 'press ctrl - C to interrupt'; sleep 3;systemd-f*ck"

I dont know the details of how it would go in systemd but I dont think
this hack cant be put in place with the mighty systemd, can it?

The major problem is that the computer refuses to bootup without doing
the preventive check. Not even a reboot because you missed the ctrl - c
screen will help and you are forced to wait like is 1999

At the very least I would add 'patience is a virtue' or 'go outside and
play!' under the check. There is no reason not to joke about it :P

Happy holidays
[Message part 2 (text/html, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Tue, 23 Dec 2014 19:06:04 GMT) (full text, mbox, link).


Acknowledgement sent to Brian Potkin <claremont102@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Tue, 23 Dec 2014 19:06:04 GMT) (full text, mbox, link).


Message #56 received at 758902@bugs.debian.org (full text, mbox, reply):

From: Brian Potkin <claremont102@gmail.com>
To: alberto fuentes <pajaro@gmail.com>, 758902@bugs.debian.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Bug#758902: systemd: Please make ^C interrupt systemd-fsck
Date: Tue, 23 Dec 2014 19:02:52 +0000
On Tue 23 Dec 2014 at 13:19:08 +0100, alberto fuentes wrote:

> On Mon, 22 Dec 2014 21:30:38 -0500 Stefan Monnier
> <monnier@iro.umontreal.ca> wrote:
> 
> > I think this is a very nasty regression that will hit relatively few
> > people but will really piss them off.
> 
> Not sure why you think they will be few people affected. I think almost
> everybody is going to be hit by this at least once... probably more than
> once. Computers have hard drives attached. They are checked at
> semi-random intervals. If the hard drives is relatively large, it can
> take from 20min to more than 1h to check.

File systems created with mk2fs on fresh Wheezy and Jessie installs have
mount-count and time based file checking disabled. That's quite a few
people who are never liable to experience a surprise fsck.

> I was biten by this once a month until one time I had to do a
> presentation and the computer refused to bootup without checking the
> disks, then decided to write the bug and disable checking on the disks
> risking corruption

Disabling perodic checking (which upstream doesn't regard as conferring
any particular benefit) eliminates the surprise factor. Without elements
of surprise and inconvenience to combat there is no need to overstrive
for a solution. A fsck can always be run by a user as part of regular
maintenance.

Wishlist is about right for this bug; there isn't a lower severity
level.

> > In my experience, systemd has introduced various different *new* ways in
> > which the boot can get stuck in some long-running "operation" (which
> > might just be waiting for a timeout). If we don't want to alienate
> > users, we should raise the severity of this bug (and broaden its scope).
> 
> While I agree and something generic and well implemented should be put
> in place, i would be well off with a hack to interrupt it.
> 
> It would take less than 15 min to implement it to the systemd people to
> avoid this 10+ years regresion. Calling a pre-script,or pre-service or
> however systemd works
> 
>  "echo 'press ctrl - C to interrupt'; sleep 3;systemd-f*ck"
> 
> I dont know the details of how it would go in systemd but I dont think
> this hack cant be put in place with the mighty systemd, can it?

Changes to ways of working are not unknown as software develops. It
could take much less than 15 minutes for a user to implement a solution
which took the changes into account.

> The major problem is that the computer refuses to bootup without doing
> the preventive check. Not even a reboot because you missed the ctrl - c
> screen will help and you are forced to wait like is 1999

The first statement is misleading; new Wheezy and Jessie users would
disagree with it. They also realise that the consequences of enabling
mount-count or time based file checking falls on them, not someone else.

Regards,

Brian.




Information forwarded to debian-bugs-dist@lists.debian.org, Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>:
Bug#758902; Package systemd. (Tue, 23 Dec 2014 20:33:24 GMT) (full text, mbox, link).


Acknowledgement sent to alberto fuentes <pajaro@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>. (Tue, 23 Dec 2014 20:33:24 GMT) (full text, mbox, link).


Message #61 received at 758902@bugs.debian.org (full text, mbox, reply):

From: alberto fuentes <pajaro@gmail.com>
To: Brian Potkin <claremont102@gmail.com>
Cc: 758902@bugs.debian.org
Subject: Re: Bug#758902: systemd: Please make ^C interrupt systemd-fsck
Date: Tue, 23 Dec 2014 21:28:46 +0100
On Tue, Dec 23, 2014 at 8:02 PM, Brian Potkin <claremont102@gmail.com> wrote:
> File systems created with mk2fs on fresh Wheezy and Jessie installs have
> mount-count and time based file checking disabled. That's quite a few
> people who are never liable to experience a surprise fsck.

My hunch tells me that there are more fs pre-wheezy than post-wheezy
out there, considering Wheezy was only released ~1.5 years ago

> Disabling perodic checking (which upstream doesn't regard as conferring
> any particular benefit) eliminates the surprise factor. Without elements
> of surprise and inconvenience to combat there is no need to overstrive
> for a solution. A fsck can always be run by a user as part of regular
> maintenance.

Well, I just learned this. It's good to know that upstream think is
safe and good to know that the default was changed as well. I wish the
defaults of my partitions had changed on the upgrade as well


> Wishlist is about right for this bug; there isn't a lower severity
> level.

hehe.

At least is mentioned once in this bug that the *recommended upgrade
path* for your ext fs includes to disable the automatic check on the
fs, and so prevent this bug from happening in the future

[...]
> The first statement is misleading; new Wheezy and Jessie users would
> disagree with it. They also realise that the consequences of enabling
> mount-count or time based file checking falls on them, not someone else.

If it is indeed misleading let me rephrase it.

The system refuses to bootup until the check is done to anybody that
has a partition formated with defaults values provided by debian
before ~1.5 years.

For example, if you are installing wheezy, but you are using a /home
partition from a previous installation, you are still affected by this
bug


IMOH, It's a really bad attitude to not take into account most of the
user base of your installations, especially in transitions like the
systemd one, where there's already plenty of bad blood

I love debian very much, and so this is nothing i can't deal with...
but I understand people which are at the edge


Cheers



Message sent on to Alberto Fuentes <pajaro@gmail.com>:
Bug#758902. (Wed, 18 Feb 2015 16:27:19 GMT) (full text, mbox, link).


Message #64 received at 758902-submitter@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>
To: 775093-submitter@bugs.debian.org, 758902-submitter@bugs.debian.org
Subject: Re: Bug#775093: systemd-fsck: no progress reporting
Date: Wed, 18 Feb 2015 17:26:45 +0100
[Message part 1 (text/plain, inline)]
Control: tag 775093 fixed-upstream
Control: tag 758902 fixed-upstream

Support for this just landed upstream. fsckd now aggregates the status
of all running fsck process, sends it both to the terminal (for
servers) and plymouth (for desktops), and allows you to Control-C the
checks in both modes.

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
[signature.asc (application/pgp-signature, inline)]

Added tag(s) fixed-upstream. Request was from Martin Pitt <mpitt@debian.org> to 758902-submitter@bugs.debian.org. (Wed, 18 Feb 2015 16:27:20 GMT) (full text, mbox, link).


Reply sent to Martin Pitt <mpitt@debian.org>:
You have taken responsibility. (Mon, 23 Feb 2015 09:39:08 GMT) (full text, mbox, link).


Notification sent to Alberto Fuentes <pajaro@gmail.com>:
Bug acknowledged by developer. (Mon, 23 Feb 2015 09:39:09 GMT) (full text, mbox, link).


Message #71 received at 758902-close@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>
To: 758902-close@bugs.debian.org
Subject: Bug#758902: fixed in systemd 219-3
Date: Mon, 23 Feb 2015 09:34:59 +0000
Source: systemd
Source-Version: 219-3

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 758902@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt <mpitt@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@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 23 Feb 2015 09:52:12 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-dev libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg
Architecture: source amd64
Version: 219-3
Distribution: experimental
Urgency: medium
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Martin Pitt <mpitt@debian.org>
Description:
 gir1.2-gudev-1.0 - libgudev-1.0 introspection data
 libgudev-1.0-0 - GObject-based wrapper library for libudev
 libgudev-1.0-dev - libgudev-1.0 development files
 libpam-systemd - system and service manager - PAM module
 libsystemd-daemon-dev - systemd utility library (transitional package)
 libsystemd-dev - systemd utility library - development files
 libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package)
 libsystemd-journal-dev - systemd journal utility library (transitional package)
 libsystemd-login-dev - systemd login utility library (transitional package)
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 python3-systemd - Python 3 bindings for systemd
 systemd    - system and service manager
 systemd-dbg - system and service manager (debug symbols)
 systemd-sysv - system and service manager - SysV links
 udev       - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 758902 775093 778700 778970
Changes:
 systemd (219-3) experimental; urgency=medium
 .
   * sysv-generator: fix wrong "Overwriting existing symlink" warnings.
     (Closes: #778700)
   * Add systemd-fsckd multiplexer and feed its output to plymouth. This
     provides an aggregate progress report of running file system checks and
     also allows cancelling them with ^C, in both text mode and Plymouth.
     (Closes: #775093, #758902; LP: #1316796)
   * Revert "journald: allow restarting journald without losing stream
     connections". This was a new feature in 219, but currently causes boot
     failures due to logind and other services not starting up properly.
     (Closes: #778970; LP: #1423811)
   * Add "boot-smoke" autopkgtest: Test 20 successful reboots in a row, and
     that there are no connection timeouts or stalled jobs. This reproduces the
     above regression.
   * debian/tests/localed-locale: Set up locale and keyboard default files on a
     minimal unconfigured testbed.
   * Add missing python3 test dependency to cmdline-upstart-boot and
     display-managers autopkgtests.
   * debian/tests/boot-and-services: Skip AppArmor test if AppArmor is not
     enabled.
   * debian/tests/boot-and-services: Reboot also if lightdm was just installed
     but isn't running yet.
Checksums-Sha1:
 c634d9c817cfb37563a55b69713d054331fb9fcd 3838 systemd_219-3.dsc
 b411a791fa0ffc22f2f364e4acffde740cdf53a2 151180 systemd_219-3.debian.tar.xz
 55d71ddc4014f31773f5ba834e16f683d831a8ef 3385786 systemd_219-3_amd64.deb
 e99ddc55fdec03e2f1aae66869dbbf4a401bab2d 38126 systemd-sysv_219-3_amd64.deb
 9973ca832334226a12a95fd44baf258eafeb1dd1 137680 libpam-systemd_219-3_amd64.deb
 2212a343aec088c4c3113c59894f7dcb8a281432 98364 libsystemd0_219-3_amd64.deb
 57b6f26e53f6f2d9dc273581ecd132bc2ae08bef 99922 libsystemd-dev_219-3_amd64.deb
 49d8086a55e8a909604d510e34332dd977c314e4 33744 libsystemd-login-dev_219-3_amd64.deb
 b073436f533cdfde7e535494d2bbf6c086a9fba9 33758 libsystemd-daemon-dev_219-3_amd64.deb
 f199f39d1c67dfbc4f403bc9900c2554b9658785 33734 libsystemd-journal-dev_219-3_amd64.deb
 7f23a3e62b9be1563cd2a97b7f2f07e6a6f6c689 33734 libsystemd-id128-dev_219-3_amd64.deb
 9df400ace4d4a8398c96ec2b0ae03fc1f972a12c 946172 udev_219-3_amd64.deb
 cc5fb0daabda00e92867b1df8e94f819aa40d42f 66512 libudev1_219-3_amd64.deb
 5fc6836a151fd9f5674b20fba3414cdf3d76bb0a 22958 libudev-dev_219-3_amd64.deb
 428ab8387aaf97b1c0e546a68996f5420e9d33a1 230226 udev-udeb_219-3_amd64.udeb
 24fed6752f3df19e90786414b1d84161765d3127 32178 libudev1-udeb_219-3_amd64.udeb
 1d863e3170ba3b371f6f4b91552232549479fc67 44052 libgudev-1.0-0_219-3_amd64.deb
 b5cf780afe75866a2acbeafbe2adf4d78ca50516 2830 gir1.2-gudev-1.0_219-3_amd64.deb
 61e5a6d3caa68d6215162cf2b8deb991f5df60ac 24492 libgudev-1.0-dev_219-3_amd64.deb
 2d34737d308e8b03371a95afe78c3b06854496f6 63958 python3-systemd_219-3_amd64.deb
 3a988d96662ad8b6ce3af9abdbf1bf59a03c168c 22030038 systemd-dbg_219-3_amd64.deb
Checksums-Sha256:
 da9ae6003537e30f9f50d06582ebf084427d8dcc3aff1a44938fd1388957d34c 3838 systemd_219-3.dsc
 51020ef102824d56e530f2b491da20e0e012db48501c18540f3a69cf472669a1 151180 systemd_219-3.debian.tar.xz
 a2b0fbd7ae2b61056ae13ef6c833ce9aaba494d45cfa3a4e3a4fdd08ee8fb4d0 3385786 systemd_219-3_amd64.deb
 7fe08cf85a47b7c07304ddb455207b6e7482b4534b1615952eb1d0762e184857 38126 systemd-sysv_219-3_amd64.deb
 029586feb863953c7a33b8b036ed4a8fc2dfaedb9dfb0c551a266efaf6ea0d75 137680 libpam-systemd_219-3_amd64.deb
 232857b5ecb41ea8a85f267b21c786cc5b8443aabbf5a2d128c574f79ad2b77d 98364 libsystemd0_219-3_amd64.deb
 b88cfd87605a68ddd6763e2d7e3c65cb0ca3607b9d0ea83ad4f79f2920c5c726 99922 libsystemd-dev_219-3_amd64.deb
 dd02efd86d3b9bd800d19d4cde90663fb173d16cbbe09f6e54d21fbb848b5976 33744 libsystemd-login-dev_219-3_amd64.deb
 426812b71f5ddd88e9145330a3d84304b8db4e525053ef1b02be79457baa0184 33758 libsystemd-daemon-dev_219-3_amd64.deb
 76d5d1d400a8e09f8f9dc2b8acf078615c33ea0c9049ef3c0ece14be18cb09ce 33734 libsystemd-journal-dev_219-3_amd64.deb
 080fbdf5a57561ac007278ec2d278d1c21eb39d988ce399d7bfa28e6bef73c61 33734 libsystemd-id128-dev_219-3_amd64.deb
 c926d27b6e49321b4265805a612b94a26c6734a3a4ddf18634a8b764ab082a69 946172 udev_219-3_amd64.deb
 b90477a56c9f9e2d1284261f1ce68fd6eb8d5afea2de287634dc7c2e3065af5f 66512 libudev1_219-3_amd64.deb
 03e5c01b6c2f23368a153d01ecbb47442bfddf0927b9431942cb67b5d95e925d 22958 libudev-dev_219-3_amd64.deb
 e809952be3ab17a003de05d47ebacdef40b26cd0294400312b808d79da4fc580 230226 udev-udeb_219-3_amd64.udeb
 c19759f626bf9d8cfdf83ac0577360e41cde17fe372d0ba779742d007cc63455 32178 libudev1-udeb_219-3_amd64.udeb
 ee0ff6e3ed42ce8ef13cfe44ea66cf7bbd223d8c48179cbb36dba6b9af0e969d 44052 libgudev-1.0-0_219-3_amd64.deb
 6975812aeb57c248d506f434fd7941afeed08f8f11ab8b945afdd3226cbb4caa 2830 gir1.2-gudev-1.0_219-3_amd64.deb
 e167ea7cb1400642a827672df8982a6859b5049bbe5ba1e4d629fbb73ce8537b 24492 libgudev-1.0-dev_219-3_amd64.deb
 24f09a7aee8c03095a1af75388c7fa40f01a70ce226e42f15d797219b2a30933 63958 python3-systemd_219-3_amd64.deb
 f0e9cad617a4abd73190c32a6142b27278b87d140e222c440f4c5151fe4d958f 22030038 systemd-dbg_219-3_amd64.deb
Files:
 9d4353e89feaea0817c79e36ec1d2737 3838 admin optional systemd_219-3.dsc
 22810ae983efc6979b0cdc50e3acdc66 151180 admin optional systemd_219-3.debian.tar.xz
 c6ea94c0ad977b507b53a80eff16d370 3385786 admin optional systemd_219-3_amd64.deb
 2901f6ed9031bc73425048223ea81ac0 38126 admin extra systemd-sysv_219-3_amd64.deb
 3da0d1509f63f700dd91d7fc9ffb4683 137680 admin optional libpam-systemd_219-3_amd64.deb
 02c683be9326704c1e887b3ae2f8250a 98364 libs optional libsystemd0_219-3_amd64.deb
 fd97aba99ba5e56a90c6858ff515bdb9 99922 libdevel optional libsystemd-dev_219-3_amd64.deb
 30a140fdaaae000062833482c446119a 33744 oldlibs extra libsystemd-login-dev_219-3_amd64.deb
 a32038f812ca8c7242d38eb142235a16 33758 oldlibs extra libsystemd-daemon-dev_219-3_amd64.deb
 24c61e5fdbac9c3816986efb383239bf 33734 oldlibs extra libsystemd-journal-dev_219-3_amd64.deb
 59478299805801b495741c26983e2f9f 33734 oldlibs extra libsystemd-id128-dev_219-3_amd64.deb
 7153d5a49d680ed22c7cc768aa7f6add 946172 admin important udev_219-3_amd64.deb
 cb20cae5f5443346181138d19816d463 66512 libs important libudev1_219-3_amd64.deb
 92b03d839865f83ce05c76c8d5a54946 22958 libdevel optional libudev-dev_219-3_amd64.deb
 3b86c90eb9b672969ab54fbb05e52484 230226 debian-installer optional udev-udeb_219-3_amd64.udeb
 006fc07b0bad6efb7c43f579800f01c1 32178 debian-installer optional libudev1-udeb_219-3_amd64.udeb
 4b8cc740036576ac23d72fdc3bdf84d9 44052 libs optional libgudev-1.0-0_219-3_amd64.deb
 7a3bc94725a945159ff4643cee47b432 2830 introspection optional gir1.2-gudev-1.0_219-3_amd64.deb
 8363cedf4d86c0fd9c7a824a9b396af7 24492 libdevel optional libgudev-1.0-dev_219-3_amd64.deb
 bc65128c3929e4ac69316b5392a76f4e 63958 python optional python3-systemd_219-3_amd64.deb
 f44b5c0e557b45ad08525b7a683dbfce 22030038 debug extra systemd-dbg_219-3_amd64.deb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJU6vGiAAoJENFO8V2v4RNHS1sQAId6qnVd1WdbJSkLzC0wuc5q
Cwi7LcuWTBZBIrJLL/xWwMdMVAgI/Go43iHiw++Gsj5T3NXVk7KgLRUYV0DsnZH6
p3ckzFQDUOZ0gGU++axrV6sVX5rID7pb9brofUVG0TKcwpczBn8MRklraDmQDyks
0ELtbIzUFc6sRrcDJkZuojU0PVlZOhs+eCWFO1oPb3839MNqiiHUv183ZG6enRK1
0BjcU6l67Housszb5dOaPaebIgOgSzpv2XWnKkN7wzY0ZjlKDR66vzJHt93nC3Xs
RuWpGoHoQMcRJ9QrWsQbH5j1Gj/GQj5UmFj7kpgp1x8FnMnajpVi10jG6O8ld7ea
X6ewgHo4+rmEb8s7EfPriConCyoSEkOKlunGlBXQr8Sera7Oqrv9GoS2hw/g+gno
ddJeCC2Bnygvig4Kwz1JBkxXQc2j4xVSXlyMIDXwnjQhDO5KRzuDjhJ5HNEiHxhw
ACrWb6NiN7suz2kgoWZ3+Z/dJMe8LtMWExKvLM0BZLDZ9gu+33CDO0oU6eW1V4MI
EGVaoXeeYJwAws9+TS8TFjzljaVRPssNCrL6VlzW05TpP7tOYo81m50rlR+p69tw
tZe02CmClPPFFJDaAVd9DTSIFe3I7W5ENo7AZB8/V4zWoMOG9h/2ujFa1xHnd9aw
gT3mSRewpXpdW3jX1ILP
=iZ4C
-----END PGP SIGNATURE-----




Reply sent to Martin Pitt <mpitt@debian.org>:
You have taken responsibility. (Mon, 23 Feb 2015 09:39:10 GMT) (full text, mbox, link).


Notification sent to Eduardo Nogueira <eng442@ymail.com>:
Bug acknowledged by developer. (Mon, 23 Feb 2015 09:39:10 GMT) (full text, mbox, link).


Reply sent to Martin Pitt <mpitt@debian.org>:
You have taken responsibility. (Fri, 29 May 2015 17:39:12 GMT) (full text, mbox, link).


Notification sent to Alberto Fuentes <pajaro@gmail.com>:
Bug acknowledged by developer. (Fri, 29 May 2015 17:39:12 GMT) (full text, mbox, link).


Message #80 received at 758902-close@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>
To: 758902-close@bugs.debian.org
Subject: Bug#758902: fixed in systemd 220-2
Date: Fri, 29 May 2015 17:37:08 +0000
Source: systemd
Source-Version: 220-2

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 758902@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt <mpitt@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@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 29 May 2015 18:54:09 +0200
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libnss-myhostname libnss-mymachines libsystemd0 libsystemd-dev libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-dev libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb python3-systemd systemd-dbg
Architecture: source amd64
Version: 220-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Changed-By: Martin Pitt <mpitt@debian.org>
Description:
 libnss-myhostname - nss module providing fallback resolution for the current hostname
 libnss-mymachines - nss module to resolve hostnames for local container instances
 libpam-systemd - system and service manager - PAM module
 libsystemd-daemon-dev - systemd utility library (transitional package)
 libsystemd-dev - systemd utility library - development files
 libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package)
 libsystemd-journal-dev - systemd journal utility library (transitional package)
 libsystemd-login-dev - systemd login utility library (transitional package)
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 python3-systemd - Python 3 bindings for systemd
 systemd    - system and service manager
 systemd-dbg - system and service manager (debug symbols)
 systemd-sysv - system and service manager - SysV links
 udev       - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 739676 740372 742048 748668 751707 755722 757367 758902 759320 759489 759515 760514 760616 762101 762343 762700 762953 764613 765577 766413 766429 766938 767267 768644 769186 771122 771397 771423 771498 771652 771739 771980 772182 772700 773302 773528 773533 774012 774335 775067 775093 775331 775404 775889 775903 776166 776170 776546 777115 777601 777613 778499 778654 778656 778700 778970 779169 779710 779902 780263 780650 781604 782265 782522 784720 784858
Changes:
 systemd (220-2) unstable; urgency=low
 .
   * 220-1 was meant to go to experimental, but was accidentally uploaded to
     unstable. This was planned for next week anyway, just not on a Friday;
     we don't revert, but keep an RC bug open for a few days to get broader
     testing. Reupload 220-1 with its changelog actually pointing to unstable
     and with all versions in the .changes.
 .
 systemd (220-1) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * New upstream release:
     - Ship sdio.ids and ids-update.pl in upstream tarball. (Closes: #780650)
     - Drop non-working "journalctl /dev/sda" example from manpage
       (Closes: #781604)
     - man systemd.network: Explain UseDomains a bit more (not used by
       default). (Closes: #766413)
     - Ignore comments in /etc/hostname (LP: #766413)
     - Drop all backported patches and port the others to new upstream release.
   * Cherry-pick patch to fix udevd --daemon assertion regression.
   * Cherry-pick patch to fix udevd worker hang.
   * systemd.install: systemd.pc moved back into /usr/share/pkgconfig/.
   * libsystemd0.symbols: Add new symbols from this release.
   * Drop debian/extra/60-keyboard.hwdb for now. Upstream has a newer version,
     and it's not nearly as often updated any more as it used to be.
   * debian/rules: Remove shipped audit_type-to-name.h and
     keyboard-keys-from-name.gperf and regenerate them during build (bug in
     upstream 220 tarball).
   * autopkgtest: Ship/use mock fsck from debian/tests, as it's missing in the
     220 tarball.
   * Add libnss-mymachines binary package. (Closes: #784858)
   * Add libnss-myhostname binary package, taking over from the very old and
     unmaintained standalone source package as per its maintainer's request.
     (Closes: #760514)
   * Drop buildsys-Don-t-default-to-gold-as-the-linker.patch and set LD in
     debian/rules on sparc only. This can be dropped entirely once we build
     GUdev from a separate source.
   * bootchart autopkgtest: Skip test if /proc/schedstat does not exist, i. e.
     the kernel is missing CONFIG_SCHEDSTAT. Bootchart requires this.
   * systemd-fsckd autopkgtest: On Debian plymouth-start stays running, adjust
     was_running() for that.
   * systemd-fsckd autopkgtest: In test_systemd_fsck_with_plymouth_failure(),
     fix plymouthd status check to work under both Debian and Ubuntu.
   * Replace almost all of Fix-paths-in-man-pages.patch with upstreamed
     patches. (The reminder is planned to get fixed upstream as well.)
   * Remove our update-rc.d patches, replace them with upstream patches for
     /lib/systemd/systemd-sysv-install abstraction, and provide one for
     update-rc.d. Also implement "is-enabled" command by directly checking for
     the presence of rcS or rc5 symlinks. (Closes: #760616)
   * Fix path_is_mount_point for files (regression in 220).
   * debian/control: Drop obsolete XS-Testsuite:, dpkg adds it automatically.
   * Use Ubuntu's default NTP server for timesyncd when building on Ubuntu.
 .
   [ Michael Biebl ]
   * Remove /var/run and /var/lock migration code from debian-fixup. The /run
     migration was completed in wheezy so this is no longer necessary.
   * Drop our versioned Depends on initscripts. This was initially added for
     the /run migration and later to ensure we have a mountnfs hook which
     doesn't cause a deadlock under systemd. The /run migration was completed
     in wheezy and jessie ships a fixed mountnfs hook. In addition we now use
     the ignore-dependencies job mode in our lsb init-functions hook, so it's
     safe to drop this dependency.
   * Stop building gudev packages. Upstream has moved the gudev code into a
     separate repository which is now managed on gnome.org. The gudev packages
     will be built from src:libgudev from now on. See also
     http://lists.freedesktop.org/archives/systemd-devel/2015-May/032070.html
 .
 systemd (219-10) experimental; urgency=medium
 .
   * Fix assertion crash with empty Exec*= paths. (LP: #1454173)
   * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch
     and Avoid-reloading-services-when-shutting-down.patch: This was fixed more
     robustly in invoke-rc.d and service now, see #777113.
   * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down.
   * Fix "tentative" state of devices which are not in /dev (mostly in
     containers), and avoid overzealous cleanup unmounting of mounts from them.
     (LP: #1444402)
   * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls.
   * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long
     obsolete, CD ejection with the hardware button works properly without it.
   * Re-enable-journal-forwarding-to-syslog.patch: Update patch description,
     journal.conf.d/ exists now.
   * journal: Gracefully handle failure to bind to audit socket, which is known
     to fail in namespaces (containers) with current kernels. Also
     conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ.
     (LP: #1457054)
   * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping
     of unit names, reduces the delta, and will make it easier to get a common
     solution for integrating ifup.d/ scripts with networkd.
   * When booting with "quiet", run the initramfs' udevd with "notice" log
     level. (LP: #1432171)
   * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in
     a container. This makes lxc-stop work for systemd containers.
     (LP: #1457321)
   * write_net_rules: Escape '{' and '}' characters as well, to make this work
     with busybox grep. Thanks Faidon Liambotis! (Closes: #765577)
 .
 systemd (219-9) experimental; urgency=medium
 .
   * 75-persistent-net-generator.rules: Fix rules for ibmveth (it's a driver,
     not a subsystem). (LP: #1437375)
   * debian/tests/unit-config: Add tests for systemctl enable/disable on a
     SysV-only unit. Reproduces LP #1447807.
   * Fix systemctl enable for SysV scripts without a native unit. We must not
     try and enable the nonexisting unit then. (LP: #1447807)
   * Drop Add-env-variable-for-machine-ID-path.patch. systemd should always
     be installed via the essential "init" in buildd schroots now.
   * debian/README.source: Update git-buildpackage commands for the renames in
     0.6.24.
   * Make apparmor run before networking, to ensure that profiles apply to
     e. g. dhclient (LP: #1438249):
     - Rename networking.service.d/network-pre.conf to systemd.conf, and add
       After=apparmor.service.
     - ifup@.service: Add After=apparmor.service.
     - Add Breaks: on apparmor << 2.9.2-1, which dropped its dependency to
       $remote_fs.
   * Drop login-don-t-overmount-run-user-UID-on-upgrades.patch and
     login-don-t-overmount-run-user-UID-on-upgrades.patch, these were only
     needed for upgrades from wheezy to jessie.
   * systemd.{pre,post}inst: Clean up obsolete (pre-wheezy/jessie) upgrade
     fixes.
   * systemd-fsckd autopkgtest: Stop assuming that
     /etc/default/grub.d/90-autopkgtest.cfg exists.
   * systemd-fsckd autopkgtest: Add missing plymouth test dependency.
   * Drop core-mount-ensure-that-we-parse-proc-self-mountinfo.patch, and bump
     util-linux dependency to the version which enables
     --enable-libmount-force-mountinfo.
 .
 systemd (219-8) experimental; urgency=medium
 .
   [ Michael Biebl ]
   * Skip filesystem check if already done by the initramfs. (Closes: #782522)
   * Drop hard-coded versioned dependency on libapparmor1. Bump the
     Build-Depends on libapparmor-dev instead. This ensures a proper versioned
     dependency via Build-Depends-Package.
   * Revert "Make apparmor run before networking". This causes dependency
     cycles while apparmor still depends on $remote_fs.
   * Cleanup hwclock-save.service symlinks when upgrading from the jessie
     version.
 .
   [ Martin Pitt ]
   * cryptsetup: Implement offset and skip options. (Closes: #751707,
     LP: #953875)
   * logind autopkgtest: Add test for suspending on lid switch close.
     This reproduces LP #1444166 (lid switch not working in the first few
     minutes after boot).
   * Reduce the initial suspend supression time from 3 minutes to 30 seconds,
     and make it configurable. (LP: #1444166)
   * Fix double free crash in "systemctl enable" when calling update-rc.d and
     the latter fails. (Closes: #764613, LP: #1426588)
   * hwdb: Fix wireless switch on Dell Latitude (LP: #1441849)
   * Fix assertion crash when reading a service file with missing ' and
     trailing space. (LP: #1447243)
   * ifup@.service: Set IgnoreOnIsolate, so that "systemctl default" does not
     shut down network interfaces. (Closes: #762953, LP: #1449380).
     Add PartOf=network.target, so that stopping network.target also stops
     network interfaces (so that isolating emergency.target and similar work as
     before).
   * Revert upstream commit 743970d which immediately SIGKILLs units during
     shutdown. This leads to problems like bash not being able to write its
     history, mosh not saving its state, and similar failed cleanup actions.
     (Closes: #784720, LP: #1448259)
   * Drop the reversion of "journald: allow restarting journald without losing
     stream connections", and replace with proper upstream fix for
     sd_pid_notify_with_fds(). (See Debian #778970, LP #1423811; LP: #1437896)
 .
 systemd (219-7) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * Make systemd-sysv's dependency to systemd unversioned. The package just
     contains 6 symlinks and thus isn't sensitive at all against version
     mismatches. This avoids running into circular dependencies when testing
     local debs.
   * Revert "udev: Drop hwdb-update dependency" and replace with upstream patch
     which moves it to systemd-udev-trigger.service.
   * display-managers autopkgtest: Properly wait until all jobs are finished.
   * display-managers autopkgtest: Reset failed units between tests, to avoid
     running into restart limits and for better test isolation.
   * Enable timesyncd in virtual machines. (Closes: #762343)
 .
   [ Adam Conrad ]
   * debian/systemd.{triggers,postinst}: Trigger a systemctl daemon-reload
     when init scripts are installed or removed (Closes: #766429)
 .
   [ Didier Roche ]
   * Squash all fsckd patches in one (as fsckd and such will be removed
     soon upstream), containing various fixes from upstream git and refactor
     the connection flow to upstream's suggestion. Modify the man pages to match
     those modifications as well. Amongst others, this suppresses "Couldn't
     connect to plymouth" errors if plymouth is not running.
     (Closes: #782265, LP: #1429171)
   * Keep plymouth localized messages in a separate patch for easier updates in
     the future and refresh to latest upstream.
   * display-managers autopkgtest: Use ExecStart=sleep instead of the actual
     lightdm binary, to avoid errors from lightdm startup. Drop the now
     unnecessary "needs-recommends" to speed up the test.
 .
 systemd (219-6) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * Import patches from v219-stable branch (up to 85a6fab).
   * boot-and-services autopkgtest: Add missing python3 test dependency.
   * Make apparmor run before networking, to ensure that profiles apply to
     e. g. dhclient (LP: #1438249):
     - Rename networking.service.d/network-pre.conf to systemd.conf, and add
       After=apparmor.service.
     - ifup@.service: Add After=apparmor.service.
   * udev: Drop hwdb-update dependency, which got introduced by the above
     v219-stable branch. This causes udev and plymouth to start too late and
     isn't really needed in Debian yet as we don't support stateless systems
     yet and handle hwdb.bin updates through dpkg triggers. (LP: #1439301)
 .
   [ Didier Roche ]
   * Fix mount point detection on overlayfs and similar file systems without
     name_to_handle_at() and st_dev support. (LP: #1411140)
 .
   [ Christian Seiler ]
   * Make the journald to syslog forwarding more robust by increasing the
     maximum datagram queue length from 10 to 512. (Closes: #762700)
 .
   [ Marco d'Itri ]
   * Avoid writing duplicate entries in 70-persistent-net.rules by double
     checking if the new udev rule has already been written for the given
     interface. This happens if multiple add events are generated before the
     write_net_rules script returns and udevd renames the interface.
     (Closes: #765577)
 .
 systemd (219-5) experimental; urgency=medium
 .
   [ Didier Roche ]
   * Add "systemd-fsckd" autopkgtest. (LP: #1427312)
   * cmdline-upstart-boot autopkgtest: Update to Ubuntu's upstart-sysv split
     (test gets skipped on Debian while upstart-sysv does not yet exist there).
   * Cherry-pick a couple of upstream commits for adding transient state,
     fixing a race where mounts become available before the device being
     available.
   * Ensure PrivateTmp doesn't require tmpfs through tmp.mount, but rather adds
     an After relationship. (Closes: #779902)
 .
   [ Martin Pitt ]
   * journald: Suppress expected cases of "Failed to set file attributes"
     errors. (LP: #1427899)
   * Add systemd-sysv.postinst: Update grub on first installation, so that the
     alternative init system boot entries get updated.
   * debian/tests: Call /tmp/autopkgtest-reboot, to work with autopkgtest >=
     3.11.1.
   * Check for correct architecture identifiers for SuperH. (Closes: #779710)
   * Fix tmpfiles.d to only apply the first match again (regression in 219).
     (LP: #1428540)
   * /lib/lsb/init-functions.d/40-systemd: Don't ignore systemd unit
     dependencies in "degraded" mode. (LP: #1429734)
 .
   [ Michael Biebl ]
   * debian/udev.init: Recognize '!' flag with static device lists, to work
     with kmod 20. (Closes: #780263)
 .
   [ Craig Magina ]
   * rules-ubuntu/71-power-switch-proliant.rules: Add support for HP ProLiant
     m400 Server Cartridge soft powerdown on Linux 3.16. (LP: #1428811)
 .
   [ Scott Wakeling ]
   * Rework package description to be more accurate. (Closes: #740372)
 .
 systemd (219-4) experimental; urgency=medium
 .
   * tmpfiles: Avoid creating duplicate ACL entries. Add postinst code to clean
     them up on upgrade. (Closes: #778656)
   * bootchart: Fix path to default init. (LP: #1423867)
   * Add "bootchart" autopkgtest, to spot regressions like the above.
   * autopkgtests: Factorize out "assert.sh" utility functions, and use them in
     the tests for useful failure messages.
   * Downgrade requirement for timedated, hostnamed, localed-locale, and
     logind autopkgtests from machine to container isolation.
   * boot-and-services and display-manager autopkgtest: Add systemd-sysv as
     proper test dependency instead of apt-get installing it. This works now
     also under Ubuntu 15.04.
   * boot-and-services autopkgtest: Check cleanup of temporary files during
     boot. Reproduces #779169.
   * Clean up /tmp/ directory again. (Closes: #779169, LP: #1424992)
 .
 systemd (219-3) experimental; urgency=medium
 .
   * sysv-generator: fix wrong "Overwriting existing symlink" warnings.
     (Closes: #778700)
   * Add systemd-fsckd multiplexer and feed its output to plymouth. This
     provides an aggregate progress report of running file system checks and
     also allows cancelling them with ^C, in both text mode and Plymouth.
     (Closes: #775093, #758902; LP: #1316796)
   * Revert "journald: allow restarting journald without losing stream
     connections". This was a new feature in 219, but currently causes boot
     failures due to logind and other services not starting up properly.
     (Closes: #778970; LP: #1423811)
   * Add "boot-smoke" autopkgtest: Test 20 successful reboots in a row, and
     that there are no connection timeouts or stalled jobs. This reproduces the
     above regression.
   * debian/tests/localed-locale: Set up locale and keyboard default files on a
     minimal unconfigured testbed.
   * Add missing python3 test dependency to cmdline-upstart-boot and
     display-managers autopkgtests.
   * debian/tests/boot-and-services: Skip AppArmor test if AppArmor is not
     enabled.
   * debian/tests/boot-and-services: Reboot also if lightdm was just installed
     but isn't running yet.
 .
 systemd (219-2) experimental; urgency=medium
 .
   * Fix UTF-16 to UTF-8 conversion on big-endian machines. (Closes: #778654)
   * Disable new new test-sigbus, it fails on some buildds due to too old
     kernels. (part of #778654)
   * debian/README.Debian, debian/systemd.postinst: Drop setfacl call for
     /var/log/journal, this is now done automatically by tmpfiles.d/systemd.conf.
   * Drop "acl" dependency, not necessary any more with the above.
   * debian/tests/boot-and-services: Move to using /var/lib/machines/,
     /var/lib/containers is deprecated.
 .
 systemd (219-1) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * New upstream release:
     - Fix spelling mistake in systemd.unit(5). (Closes: #773302)
     - Fix timeouts with D-Bus, leading to SIGFPE. (Closes: #774012)
     - Fix load/save of multiple rfkill states. (Closes: #759489)
     - Non-persistant journal (/run/log/journal) is now readable by group adm.
       (Closes: #771980)
     - Read netdev user mount option to correctly order network mounts after
       network.target. (Closes: #769186)
     - Fix 60-keyboard.hwdb documentation and whitespace handling.
       (Closes: #757367)
     - Fix ThinkPad X1 Carbon 20BT trackpad buttons (LP: #1414930)
     - Drop all backported patches and port the others to new upstream release.
   * Bump libblkid-dev build dependency as per upstream configure.ac.
   * debian/systemd.install: Add new language-fallback-map file.
   * debian/udev.install: Add new systemd-hwdb tool.
   * debian/libsystemd0.symbols: Add new symbols from this release.
   * tmpfiles.d/systemd.conf: Drop "wheel" ACL (that group does not exist in
     Debian) to make the ACL for "adm" actually work.
   * debian/rules: Explicitly disable importd for now; it should still mature a
     bit. Explicitly enable hwdb support.
   * /lib/lsb/init-functions.d/40-systemd: Call systemctl is-system-running
     with --quiet. (LP: #1421058)
   * debian/systemd.postrm: Clean getty@tty1.service and remote-fs.target
     enablement symlinks on purge. (Closes: #778499)
   * Move all Debian specific units in the systemd package into
     debian/extra/units/ and simplify debian/systemd.install.
   * Enable timesyncd by default. Add a config drop-in to not start if ntp,
     openntpd, or chrony is installed. (Closes: #755722)
   * debian/systemd.links: Drop obsolete hwclockfirst.service mask link, this
     was dropped in wheezy's util-linux already.
   * debian/udev.postinst: Call systemd-hwdb instead of udevadm hwdb.
 .
   [ Michael Biebl ]
   * Stop removing firstboot man pages. They are now installed conditionally.
 .
 systemd (218-10) experimental; urgency=medium
 .
   * Pull latest keymaps from upstream git. (LP: #1334968, #1409721)
   * rules: Fix by-path of mmc RPMB partitions and don't blkid them. Avoids
     kernel buffer I/O errors and timeouts. (LP: #1333140)
   * Clean up stale mounts when ejecting CD drives with the hardware eject
     button. (LP: #1168742)
   * Document systemctl --failed option. (Closes: #767267)
   * Quiesce confusing and irrelevant "failed to reset devices.list" warning.
     (LP: #1413193)
   * When booting with systemd-bootchart, default to run systemd rather than
     /sbin/init (which might not be systemd). (LP: #1417059)
   * boot-and-services autopkgtest: Add CgroupsTest to check cgroup
     creation/cleanup behaviour. This reproduces #777601 and verifies the fix
     for it.
 .
 systemd (218-9) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * debian/tests/logind: With dropped systemd-logind-launch we don't have a
     visible /sys/fs/cgroup/systemd/ any more under cgmanager. So adjust the
     test to check /proc/self/cgroup instead.
   * Add unit-config autopkgtest to check systemd unit/sysv init enabling and
     disabling via systemctl. This also reproduces #777613.
   * systemctl: Always install/enable/disable native units, even if there is a
     corresponding SysV script and we call update-rc.d; while the latter
     handles WantedBy=, it does not handle Alias=. (Closes: #777613)
   * cgroup: Don't trim cgroup trees created by someone else, just the ones
     that systemd itself created. This avoids cleaning up empty cgroups from
     e.g. LXC. (Closes: #777601)
   * Don't parse /etc/mtab for current mounts, but /proc/self/mountinfo. If the
     former is a file, it's most likely outdated on boot, leading to race
     conditions and unmounts during boot. (LP: #1419623)
 .
   [ Michael Biebl ]
   * Explicitly disable the features we don't want to build for those with
     autodetection. This ensures reliable build results in dirty build
     environments.
   * Disable AppArmor support in the udeb build.
   * core: Don't fail to run services in --user instances if $HOME is missing.
     (Closes: #759320)
 .
   [ Didier Roche ]
   * default-display-manager-generator: Avoid unnecessary /dev/null symlink and
     warning if there is no display-manager.service unit.
 .
 systemd (218-8) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * boot-and-services autopkgtest: Ensure that there are no failed units,
     except possibly systemd-modules-load.service (as that notoriously fails
     with cruft in /etc/modules).
   * Revert "input" system group creation in systemd.postinst from 218-7. It's
     already done in udev.postinst.
   * ifup@.service: Revert checking for existance of ifupdown config for that
     interface, net.agent already does that.
   * Drop Also-redirect-to-update-rc.d-when-not-using-.service.patch; not
     necessary any more with the current version (mangle_names() already takes
     care of this).
   * Merge into Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch:
     - Do-not-order-rcS.d-services-after-local-fs.target-if.patch, as it
       partially reverts the above, and is just fixing it.
     - Map-rcS.d-init-script-dependencies-to-their-systemd-.patch as it's just
       adding some missing functionality for the same purpose.
   * Merge Run-update-rc.d-defaults-before-update-rc.d-enable-d.patch into
     Make-systemctl-enable-disable-call-update-rc.d-for-s.patch as the former
     is fixing the latter and is not an independent change.
   * Drop Launch-logind-via-a-shell-wrapper.patch and systemd-logind-launch
     wrapper. The only remaining thing that we need from it is to create
     /run/systemd/, move that into the D-BUS service file directly.
   * /lib/lsb/init-functions.d/40-systemd: Avoid deadlocks during bootup and
     shutdown. DHCP/ifupdown and similar hooks which call "/etc/init.d/foo
     reload" can easily cause deadlocks, since the synchronous wait plus
     systemd's normal behaviour of transactionally processing all dependencies
     first easily causes dependency loops. Thus during boot/shutdown operate
     only on the unit and not on its dependencies, just like SysV behaves.
     (Closes: #777115, LP: #1417010)
   * Only start logind if dbus is installed. This fixes the noisy startup
     failure in environments without dbus, such as LXC containers or servers.
     (part of #772700)
   * Add getty-static.service unit which starts getty@.service on tty 2 to 6 if
     dbus is not installed, and hence logind cannot auto-start them on demand.
     (Closes: #772700)
 .
   [ Michael Biebl ]
   * Update insserv-generator and map $x-display-manager to
     display-manager.service, following the recent change in sysv-generator.
     This avoids creating references to a no longer existing
     x-display-manager.target unit.
 .
 systemd (218-7) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * Don't attempt to mount the same swap partition twice through different
     device node aliases. (Closes: #772182, LP: #1399595)
   * logind: handle closing sessions over daemon restarts. (Closes: #759515,
     LP: #1415104)
   * logind: Fix sd_eviocrevoke ioctl call, to make forced input device release
     after log out actually work.
   * debian/rules: Drop obsolete --disable-multi-seat-x and
     --with-firmware-path configure options.
   * debian/udev.README.Debian: Trim the parts which are obsolete, wrong, or
     described in manpages. Only keep the Debian specific bits.
     (Part of #776546)
   * Actually install udev's README.Debian when building for Debian.
     (Closes: #776546)
   * Create system group "input" which was introduced in 215. (LP: #1414409)
   * ifup@.service: Don't fail if the interface is not configured in
     /etc/network/interfaces at all. (LP: #1414426)
 .
   [ Michael Biebl ]
   * Update Vcs-Browser URL to use cgit and https.
   * Map $x-display-manager LSB facility to display-manager.service instead of
     making it a target. Using a target had the downside that multiple display
     managers could hook into it at the same time which could lead to several
     failed start attempts for the non-default display manager.
 .
 systemd (218-6) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * initramfs hook: Install 61-persistant-storage-android.rules if it exists.
   * Generate POT file during package build, for translators.
   * Pull latest keymaps from upstream git.
   * Order ifup@.service and networking.service after network-pre.target.
     (Closes: #766938)
   * Tone down "Network interface NamePolicy= disabled on kernel commandline,
     ignoring" info message to debug, as we expect this while we disable
     net.ifnames by default. (Closes: #762101, LP: #1411992)
 .
   [ Michael Biebl ]
   * Ship bash-completion for udevadm. (Closes: #776166)
   * Drop rc-local generator in favor of statically enabling rc-local.service,
     and drop halt-local.service which is unnecessary on Debian.
     (Closes: #776170)
   * Drop the obsolete libsystemd-* libraries, there are no reverse
     dependencies left.
 .
 systemd (218-5) experimental; urgency=medium
 .
   * Drop logger.agent. It hasn't been called from any udev rule for a long
     time, and looks obsolete.
   * debian/rules: Configure with --disable-firstboot to replace some manual
     file removals.
   * debian/rules: Remove manual file installation, move them to
     debian/*.install. Move all Debian specific installed files to
     debian/extra/.
   * Merge some changes from the Ubuntu package to reduce the delta; these only
     apply when building on/for Ubuntu:
     - Add 40-hyperv-hotadd.rules: Workaround for LP: #1233466.
     - Add 61-persistant-storage-android.rules to create persistent symlinks
       for partitions with PARTNAME. By Ricardo Salveti.
     - Add 71-power-switch-proliant.rules for supporting the power switches of
       ProLiant Server Cartridges. By Dann Frazier.
     - Add 78-graphics-card.rules: Mark KMS capable graphics devices as
       PRIMARY_DEVICE_FOR_DISPLAY so that we can wait for those in plymouth.
       By Scott James Remnant.
     - Don't install the Debian *.agent scripts. Instead, have Ubuntu's
       80-networking.rules directly pull in ifup@.service, which is much easier
       and more efficient.
   * Make EPERM/EACCESS when applying OOM adjustment for forked processes
     non-fatal. This happens in user namespaces like unprivileged LXC
     containers.
   * Fix assertion failure due to /dev/urandom being unmounted when shutting
     down unprivileged containers. Thanks Stéphane Graber.
   * Enable EFI support. This mostly auto-mounts /sys/firmware/efi/efivars, but
     also provides a generator for auto-detecting the root and the /boot/efi
     partition if they aren't in /etc/fstab. (Closes: #773533)
 .
 systemd (218-4) experimental; urgency=medium
 .
   [ Michael Biebl ]
   * sysv-generator: handle Provides: for non-virtual facility names.
     (Closes: #774335)
   * Fix systemd-remount-fs.service to not fail on remounting /usr if /usr
     isn't mounted yet. This happens with initramfs-tools < 0.118 which we
     might not get into Jessie any more. (Closes: #742048)
 .
   [ Martin Pitt ]
   * fstab-generator: Handle mountall's non-standard "nobootwait" and
     "optional" options. ("bootwait" is already the systemd default behaviour,
     and "showthrough" is irrelevant here, so both can be ignored).
   * Add autopkgtest for one-time boot with upstart when systemd-sysv is
     installed. This test only works under Ubuntu which has a split out
     upstart-bin package, and will be skipped under Debian.
   * debian/ifup@.service: Check if ifup succeeds by calling ifquery, to
     work around ifup not failing on invalid interfaces (see #773539)
   * debian/ifup@.service: Set proper service type (oneshot).
   * sysv-generator: Handle .sh suffixes when translating Provides:.
     (Closes: #775889)
   * sysv-generator: Make real units overwrite symlinks generated by Provides:
     from other units. Fixes failures due to presence of backup or old init.d
     scripts. (Closes: #775404)
   * Fix journal forwarding to syslog in containers without CAP_SYS_ADMIN.
     (Closes: #775067)
   * Re-enable AppArmor support, now that libapparmor1 moved to /lib. Add
     versioned dependency as long as this is still only in experimental.
     (Closes: #775331)
   * Add some missing dpkg and ucf temp files to the "hidden file" filter, to
     e. g. avoid creating units for them through the sysv-generator.
     (Closes: #775903)
   * Silence useless warning about /etc/localtime not being a symlink. This is
     deliberate in Debian with /usr (possibly) being on a separate partition.
     (LP: #1409594)
 .
   [ Christian Kastner ]
   * Use common-session-noninteractive in systemd-user's PAM config, instead of
     common-session. The latter can include PAM modules like libpam-mount which
     expect to be called just once and/or interactively, which already happens
     for login, ssh, or the display-manager. Add pam_systemd.so explicitly, as
     it's not included in -noninteractive, but is always required (and
     idempotent). There is no net change on systemd which don't use manually
     installed PAM modules. (Closes: #739676)
 .
   [ Michael Biebl ]
   * Make sure we run debian-fixup.service after /var has been mounted if /var
     is on a separate partition. Otherwise we might end up creating the
     /var/lock and /var/run symlink in the underlying root filesystem.
     (Closes: #768644)
 .
 systemd (218-3) experimental; urgency=medium
 .
   * build-logind autopkgtest: Re-enforce that sd_login_monitor_new() succeeds,
     and restrict this test to isolation-container. (Reproduces LP #1400203)
   * Bring back patch to make sd_login_monitor_new() work under other init
     systems where /sys/fs/cgroup/systemd/machine does not exist.
     (LP: #1400203)
   * build-login autopkgtest: Build against libsystemd, not libsystemd-login
     any more.
   * Add debian/extra/systemd-vconsole-setup.service dependency shim for
     the console-setup init script, to avoid breaking dependencies of
     third-party packages. Install it for Ubuntu only for now, as in Debian
     plymouth's unit got adjusted. (LP: #1392970, Debian #755194)
   * Mark systemd{,-sysv} as M-A: foreign (thanks lintian).
   * Quiesce maintainer-script-calls-systemctl lintian warning.
   * Quiesce possibly-insecure-handling-of-tmp-files lintian warning, it's
     wrong there (we are handling tmpfiles.d/ files which are not in a temp
     dir).
   * Use dh_installinit's --noscript instead of --no-start for the upstart
     jobs without sysvinit scripts (thanks lintian).
   * Put systemd.pc into arch specific pkgconfig dir, as it contains the arch
     specific libdir value.
   * Don't enable audit by default. It causes flooding of dmesg and syslog,
     suppressing actually important messages. (Closes: #773528)
   * Cherrypick various bug fixes in loopback device setup and netlink socket
     communication. Fixes massive CPU usage due to tight retry loops in user
     LXC containers.
 .
 systemd (218-2) experimental; urgency=medium
 .
   * boot-and-services AppArmor autopkgtest: Stop checking the dmesg log; it is
     racy as sometimes message bursts are suppressed.
   * Fix crash in timedatectl with Etc/UTC.
   * Prefer-etc-X11-default-display-manager-if-present.patch: Drop wrong
     copy&paste'd comment, fix log strings. Thanks Adam D. Barratt.
   * boot-and-services: Robustify Nspawn tests, and show systemd-nspawn output
     on failure.
   * Disable tests which fail on buildds, presumably due to too old kernels,
     misconfigured /etc/hosts, and similar problems. Make failures of the test
     suite fatal now.
 .
 systemd (218-1) experimental; urgency=medium
 .
   * New upstream release. Drop all cherry-picked patches and port the Debian
     specific ones.
     - Create /etc/machine-id on boot if missing. (LP: #1387090)
   * Add new libmount-dev build dependency.
   * Configure with --enable-split-usr.
   * Merge some permanent Ubuntu changes, using dpkg-vendor:
     - Don't symlink udev doc directories.
     - Add epoch to gudev packages; Ubuntu packaged the standalone gudev before
       it got merged into udev.
     - Add Apport hooks for udev and systemd.
   * udev-fallback-graphics upstart job: Guard the modprobe with || true to
     avoid a failure when vesafb is compiled in. (LP: #1367241)
 .
 systemd (217-4) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * Reinstate a debian/extra/rules/50-firmware.rules which immediately tells
     the kernel that userspace firmware loading failed. Otherwise it tries for a
     minute to call the userspace helper (if CONFIG_FW_LOADER_USER_HELPER is
     enabled) in vain, which causes long delays with devices which have a range
     of possible firmware versions. (LP: #1398458)
   * debian/systemd.postinst: Don't always restart journald, as this currently
     can't be done without losing the current journal and breaking attached
     processes. So only restart it from upgrades < 215-3 (where the socket
     location got moved) as an one-time upgrade path from wheezy.
     (Closes: #771122)
   * Revert "Modify insserv generator to mask sysvinit-only display managers".
     This is still under dispute, a bit risky, and might get a different
     implementation. Also, nodm really needs to be fixed properly, working
     around it is both too risky and also too hard to get right.
 .
   [ Didier Roche ]
   * Add display managers autopkgtests.
   * Reset display-manager symlink to match /e/X/d-d-m even if
     display-manager.service was removed. Adapt the autopkgtests for it.
     (LP: #1400680)
 .
 systemd (217-3) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * systemd.bug-script: Really capture stderr of systemd-delta.
     (Closes: #771498)
   * boot-and-services autopkgtest: Give test apparmor job some time to
     actually finish.
 .
   [ Didier Roche ]
   * updated debian/patches/insserv.conf-generator.patch:
     - if /etc/X11/default-display-manager doesn't match a systemd unit
       (or doesn't exist), be less agressive about what to mask: we let
       all sysvinit-only display-manager units enabled to fallback to previous
       behavior and let them starting. (Closes: #771739)
 .
 systemd (217-2) experimental; urgency=medium
 .
   * Re-enable journal forwarding to syslog, until Debian's sysloggers
     can/do all read from the journal directly.
   * Fix hostnamectl exit code on success.
   * Fix "diff failed with error code 1" spew with systemd-delta.
     (Closes: #771397)
   * Re-enable systemd-resolved. This wasn't meant to break the entire
     networkd, just disable the new NSS module. Remove that one manually
     instead. (Closes: #771423, LP: #1397361)
   * Import v217-stable patches (up to commit bfb4c47 from 2014-11-07).
   * Disable AppArmor again. This first requires moving libapparmor to /lib
     (see #771667). (Closes: #771652)
   * systemd.bug-script: Capture stderr of systemd-{delta,analyze}.
     (Closes: #771498)
 .
 systemd (217-1) experimental; urgency=medium
 .
   [ Martin Pitt ]
   * New upstream release. Drop all cherry-picked patches and port the Debian
     specific ones.
   * Disable systemd-resolved for now. It still needs to mature, and
     integration into Debian should be discussed first.
   * Bump util-linux dependency to >= 2.25 as per NEWS.
   * Drop installation of 50-firmware.rules, not shipped upstream any more.
     Firmware loading is now exclusively done by the kernel.
   * Drop installation of readahead related services and code, readahead got
     dropped in this version.
   * Ship new networkctl CLI tool.
   * debian/libsystemd0.symbols: Add new symbols from this release.
   * debian/rules: Call dpkg-gensymbols with -c4 to immediately spot
     changed/missing symbols during build.
   * boot-and-services autopkgtest: Test AppArmor confined units (LP #1396270)
   * Create new "systemd-journal-remote" system group, for
     systemd-tmpfiles-setup.service.
 .
   [ Marc Deslauriers ]
   * Build-depend on libapparmor-dev to enable AppArmor support. (LP: #1396270)
 .
   [ Didier Roche ]
   * Handle display-manager transitions: (Closes: #748668)
     - Add a generator to ensure /etc/X11/default-display-manager is controlling
       which display-manager is started.
     - Modify insserv generator to mask of sysvinit-only dms with insserv
       $x-display-manager tag if they don't match
       /etc/X11/default-display-manager. This avoids starting multiple dms at
       boot.
   * Cherry-pick Shared-add-readlink_value.patch as using that function in the
     generator.
Checksums-Sha1:
 909957db005ea555556c50db6d0372221c1a1ac9 3663 systemd_220-2.dsc
 2fb8f59bcc36ed4e08b164dd5b294c33193ff50a 152796 systemd_220-2.debian.tar.xz
 f2ff8d77b1eeb3e1c9d712c65f82ef2f37466f24 61608 libnss-myhostname_220-2_amd64.deb
 aa8b8eb41f3937c0269f9caf53d2212936e1dbf4 141790 libnss-mymachines_220-2_amd64.deb
 085af5c621baddda750c7f6986473a607a643f26 145860 libpam-systemd_220-2_amd64.deb
 a0618b52148dfa912f42bf2ff14538184ff4d71c 40822 libsystemd-daemon-dev_220-2_amd64.deb
 1c10dcc758f47f6aea49d736882a87617785fc9e 107154 libsystemd-dev_220-2_amd64.deb
 efb00887f72ebadc8c0bc69629089261321b2527 40794 libsystemd-id128-dev_220-2_amd64.deb
 78e04031540f95235c46b46074bce149f6bd9438 40796 libsystemd-journal-dev_220-2_amd64.deb
 551061fa257ecd65e86aff70d1a5e3bdd0c6a1fb 40810 libsystemd-login-dev_220-2_amd64.deb
 76ecc68d7efb599db3f9377aa3ca452810400ceb 107052 libsystemd0_220-2_amd64.deb
 3af711c2025727b91b22a8a12a96b429ca3b49fe 23154 libudev-dev_220-2_amd64.deb
 a904f0db34674afb3b84001d0b00a1262965a3c7 46166 libudev1-udeb_220-2_amd64.udeb
 b639308bb946baf0502e55b4f0ecdf224107670a 87918 libudev1_220-2_amd64.deb
 cc6ac7935514cb7972e9bf48844c8a800e8e2fe1 73182 python3-systemd_220-2_amd64.deb
 191edf5c0776d4f714dc85872b08cc9532b878f5 23652474 systemd-dbg_220-2_amd64.deb
 41675e14ff7cb715363e579f031d7ff194ad3504 45462 systemd-sysv_220-2_amd64.deb
 d24d189d7d361d7b6df62d7cd3e4ca43c64b7aae 3537860 systemd_220-2_amd64.deb
 0ce1d304789e31f3863c56c014147d7b96ebeb45 251614 udev-udeb_220-2_amd64.udeb
 e7fa514cbc25f351e4688a3de472421fe78332ba 987564 udev_220-2_amd64.deb
Checksums-Sha256:
 a9284e74f0d5afaecf20f8a4fb550464f98ec2b8ebd0af635a64f9ce895cca52 3663 systemd_220-2.dsc
 3127dfcf07e0fd6255191d0186f196498ba1b29bf14e0bd43f9eb941d00c1841 152796 systemd_220-2.debian.tar.xz
 76c206e61cd266fac0a10664e8b64132366894892666483ab5b84e15096ba9a9 61608 libnss-myhostname_220-2_amd64.deb
 68cde8de77aeac670e18cedca26ebdb5d876e5c81b19b8433ba531ccba54f2ac 141790 libnss-mymachines_220-2_amd64.deb
 3daf39e4d54d9eeddb19ed41ba6be1ec0aa374ac87b99c1863de09c907918c81 145860 libpam-systemd_220-2_amd64.deb
 7d5b8dcbd283932f3fbfcaba7567b1d5c131bf4045a795a879c5a43eece041a8 40822 libsystemd-daemon-dev_220-2_amd64.deb
 ed0aa3c580f3afe30c9db54f9e245bf43e34c57c8245798b4e07a520adb39cde 107154 libsystemd-dev_220-2_amd64.deb
 3affe60bb1aaeefbf545b98807600377bfd5e612ab2d682fdbc5f7d26f397ec5 40794 libsystemd-id128-dev_220-2_amd64.deb
 a0e2c71073d22309b822007b8a2f92e46d2efd3130fb09f719ea7ee9e0c36135 40796 libsystemd-journal-dev_220-2_amd64.deb
 4fdd861f1565fb4c26d20486b03ccb5257593cc2be2b86ae5ff4a0732513cbb3 40810 libsystemd-login-dev_220-2_amd64.deb
 1757845e0f7b43da40ecbd31a800d6b9354149aafe7fa2260d9187dd4e7dc920 107052 libsystemd0_220-2_amd64.deb
 5ba4ea7df4c3f89ac135612a6a5b3c2f44c30f154cead9b39ca9540ba2c05c16 23154 libudev-dev_220-2_amd64.deb
 2ec0455ca441cb793be3984d2975f758fe12ef90809901d899e3d8415958a155 46166 libudev1-udeb_220-2_amd64.udeb
 4c8eab44339f140b090d6e7ddc4a2f3a4a4f78ee2ea922f09033fff253ea7b9c 87918 libudev1_220-2_amd64.deb
 f80cf67b3e2b4852823af40697099fdd525fcc85297ac95ef6f0670f5e91538f 73182 python3-systemd_220-2_amd64.deb
 0fdf7a891a32de4ee06b7fa7c5a58188a2b42db9f7f8346d77559479d280d581 23652474 systemd-dbg_220-2_amd64.deb
 79d490687c530e3b9009835846d1d741ba9da6f75858d185f5efc67074b832bd 45462 systemd-sysv_220-2_amd64.deb
 676e8487762c9b4ad657e7c5f7118e87fee29374f164d8fbdb99a8bc7f6880be 3537860 systemd_220-2_amd64.deb
 d2204d9b1edb56aad7f84dd36b1146ae9c5312f76bc4e89d0b6fd730b9b261c6 251614 udev-udeb_220-2_amd64.udeb
 90fa4336967f4d0b264ba3ebb464c36ead05ca97406364157ce7e41195f729b3 987564 udev_220-2_amd64.deb
Files:
 7c1e311d396cd31c0dde1525c431b3b5 3663 admin optional systemd_220-2.dsc
 bbcede8b9de84534da196a91575cec58 152796 admin optional systemd_220-2.debian.tar.xz
 28624de9ddca9cb7ca55de5cd43f9d65 61608 admin extra libnss-myhostname_220-2_amd64.deb
 9e2d7966fc0463b87375e9cfdc34cdfc 141790 admin extra libnss-mymachines_220-2_amd64.deb
 ec5125f048695d05e89fb994557a57b5 145860 admin optional libpam-systemd_220-2_amd64.deb
 0fa11c900580611c8c732962d8b6a38c 40822 oldlibs extra libsystemd-daemon-dev_220-2_amd64.deb
 94d3b986cc2e89bca616a9dd4b3a47ee 107154 libdevel optional libsystemd-dev_220-2_amd64.deb
 ee67cdc0a1389cc1119d0a0a2429efb3 40794 oldlibs extra libsystemd-id128-dev_220-2_amd64.deb
 ea7f03dea1654a859aac7f6e5f452a55 40796 oldlibs extra libsystemd-journal-dev_220-2_amd64.deb
 9baac90f07531922ecaf6dea5422c461 40810 oldlibs extra libsystemd-login-dev_220-2_amd64.deb
 1b6c294b1e2b202a6c2dc34c46a80abe 107052 libs optional libsystemd0_220-2_amd64.deb
 5ddfac648567a463cf80d275279a3a8d 23154 libdevel optional libudev-dev_220-2_amd64.deb
 75259f52a62569935eacb7036b3267ea 46166 debian-installer optional libudev1-udeb_220-2_amd64.udeb
 32008d44962a1991ad98fe0cef90b2f1 87918 libs important libudev1_220-2_amd64.deb
 66cec86f4be50f17a9a502d5365292d9 73182 python optional python3-systemd_220-2_amd64.deb
 38228c3d87093fde2318fd5e20a99c11 23652474 debug extra systemd-dbg_220-2_amd64.deb
 a1de72b3db102b174ec26e3138bc4847 45462 admin extra systemd-sysv_220-2_amd64.deb
 4a5da82b6054a77182847d74e501d59d 3537860 admin optional systemd_220-2_amd64.deb
 dddd33204350f3a813febe4032c9324a 251614 debian-installer optional udev-udeb_220-2_amd64.udeb
 238037960f0329cb1db3a85a73c122c4 987564 admin important udev_220-2_amd64.deb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVaJ43AAoJENFO8V2v4RNHPIQQAI6vNHdANMR9vPUSIWp0VTpE
lNu9hPNFoX9qoj27G0abS37m6ftT93fMno7bq0vgT6FpzFrxXic7YWem59fr+4CN
NaK1Et21K0ACEhpe/Va1Gx9sapls2qLxQ16/ztwlKLdSJfUgIvZmDHPqVmMr7uko
1nBRqat2ujiJku5bgDrJ3Sux/1gC+I91lwquTe7ZrQ8M0ay7rlhrOAyQlZP+MKkl
N94r+FiAMVBGGWZt8IsTzsdcUKz2EcPnorTiAb4vYZfPS0CD0lNolh2MLTOrjUxu
iNNskcEytl4QFh9ck6BTWU69btlTDXrAInKV49J0BJ59br6o3A6/fDFCGIgqPYi/
hMtYSjkZHG+yhOUAIJfdS6J4FcS1cDnrlZtiYMLDcqOJlwq6wTEnvKkQg7H7zlQM
QJldoop5AQKzldeJRv70SEIdrfmU2IRXOFbgxbK0Wxpu02iJYqkBoEaw+jKmgoCm
CK9Q6azTK1e+hqzkmXBYvvOETOGMf6DjEfaQz6Y1gd32u6K5RmhXcAPMFnQLokCD
T9bE2+AmHBg0RJBAxsaPFlKyIP460HqsMMjNDxs5hpXILXDFQJi2AY/cBRjdNPI5
SnG7q7AICb/Z23vzQj6ioVPzNn+QNpjXCWevoYoyyLVJosU7yJhMgzBM+siqkat5
LkTSKAzMU/uEgYEBt09x
=IGlm
-----END PGP SIGNATURE-----




Reply sent to Martin Pitt <mpitt@debian.org>:
You have taken responsibility. (Fri, 29 May 2015 17:39:13 GMT) (full text, mbox, link).


Notification sent to Eduardo Nogueira <eng442@ymail.com>:
Bug acknowledged by developer. (Fri, 29 May 2015 17:39:13 GMT) (full text, mbox, link).


Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Sat, 27 Jun 2015 07:25:04 GMT) (full text, mbox, link).


Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Fri Jan 5 06:05:49 2018; Machine Name: beach

Debian Bug tracking system

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.