Your message dated Fri, 5 Dec 2014 07:27:35 +0100
with message-id <[email protected]>
and subject line Re: Bug#770504: systemd: log all members of cyclic
dependencies (loops)
has caused the Debian Bug report #770504,
regarding systemd: log all members of cyclic dependencies (loops) even with
quiet on cmdline
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 [email protected]
immediately.)
--
770504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770504
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-6
Severity: wishlist
(Bug carefully titled to include both "cycl" and "loop" since those are the
searches I've been using to find related bugs :-)
Looking at <https://bugs.debian.org/768548>, which involved a cyclic
dependency: systemd logs that there was a loop, and which arbitrary point
it tried to use to break it. However, it does not log (an example of) the
whole path around the loop before it started trying to break it.
It would be great if it could.
See also
http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2014-November/004764.html
where I tried to look for a general solution to cyclic dependencies
between "rcS things" that need networking, and "rc2 things" that provide
or want to come before networking, without having this as a prerequisite.
S
--- End Message ---
--- Begin Message ---
Version: 217-2
Zbigniew Jędrzejewski-Szmek [2014-11-22 0:53 +0100]:
> C.f. http://cgit.freedesktop.org/systemd/systemd/commit/?id=14fe721b5f6d
This is part of the v217-stable patch series which is applied in
experimental now, so marking as fixed in experimental.
But still exists in unstable's/testing's 215 version, but < important
bugs don't qualify for jessie any more as per freeze policy. If
someone wants to convince the release team, by all means go ahead, of
course -- I'm happy to cherry-pick it into unstable.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--- End Message ---
