Your message dated Sat, 5 Aug 2017 11:57:55 +0200
with message-id <30951167-2ac4-c148-f946-62d91c6b3...@debian.org>
and subject line systemd unable to boot when snoopy is enabled
has caused the Debian Bug report #784682,
regarding systemd unable to boot when snoopy is enabled
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
784682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-17
I just came across an issue with journald being unable to start up when
snoopy is enabled that prevents a Jessie/systemd installation to boot up
which i reported to upstream at
https://bugs.freedesktop.org/show_bug.cgi?id=90364 .
This is to let you know about the issue. Maybe we need to stick a
warning label somewhere. ;-)
best regards,
Stefan
--- End Message ---
--- Begin Message ---
I don't see the point of fixing wheezy right now,
specially because an eventual fix will need to go
in wheezy-bpo-sloppy anyway.
I pushed snoopt 2.3.1 in jessie-bpo.
G.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
