Bug#787205: Keep 220 in unstable for a while

[Martin Pitt]

Package: systemd
Version: 220-1
Severity: serious

Argh, I screwed up my sbuild command this morning, and

  systemd (220-1) experimental; urgency=medium

actually went to unstable:

  https://tracker.debian.org/news/687479

Now, we planned to land the experimental version in unstable around
next week anyway, so it's not too bad. I didn't plan to do that on a
Friday either; but at that point a revert is worse than just going
through with it.

There is nothing which is known to me to be a regression or broken.
But let's keep 220 in unstable for a few days longer than just 5 days.

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20150529/c20c2540/attachment.sig>