Your message dated Fri, 23 Dec 2016 01:40:27 -0500
with message-id <20161223064027.ijwcgnucvwtkzioz@gambit>
and subject line Fixed in 1.6.1-2
has caused the Debian Bug report #832933,
regarding dnscrypt-proxy: dnscrypt-proxy.socket should not be After
network.target
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.)
--
832933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832933
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dnscrypt-proxy
Version: 1.6.1-1
Severity: important
Tags: patch
A dnscrypt-proxy user suffering from intermittent boot failures on
Ubuntu 16.04 recently asked for advice[0] on the systemd mailing list.
The issue turned out to be dnscrypt-proxy.socket declaring itself to be
After=network.target, leading to a circular dependency (because socket
units are scheduled in early boot). The cycle is:
Jul 29 11:33:06 blablabla systemd[1]: basic.target: Found ordering cycle
on basic.target/start
Jul 29 11:33:06 blablabla systemd[1]: basic.target: Found dependency on
sockets.target/start
Jul 29 11:33:06 blablabla systemd[1]: basic.target: Found dependency on
dnscrypt-proxy.socket/start
Jul 29 11:33:06 blablabla systemd[1]: basic.target: Found dependency on
network.target/start
Jul 29 11:33:06 blablabla systemd[1]: basic.target: Found dependency on
NetworkManager.service/start
Jul 29 11:33:06 blablabla systemd[1]: basic.target: Found dependency on
dbus.service/start
Jul 29 11:33:06 blablabla systemd[1]: basic.target: Found dependency on
basic.target/start
Jul 29 11:33:06 blablabla systemd[1]: basic.target: Breaking ordering
cycle by deleting job sockets.target/start
This was corrected upstream in 1.6.1 [1][2], but the Debian/Ubuntu
package has its own systemd units in the debian/ directory, possibly
derived from the ones shipped in 1.6.0. Please apply the Debian
customizations via drop-ins (see systemd.unit(5)) or by patching the
units like you'd do for any other change to the upstream source code, or
re-sync the ones in debian/ with those supplied by upstream.
[0]
https://lists.freedesktop.org/archives/systemd-devel/2016-July/037238.html
[1]
https://github.com/jedisct1/dnscrypt-proxy/commit/f20d71fb863b6d1f4588b6b175efa9f2fd331d90
[2]
https://github.com/jedisct1/dnscrypt-proxy/commit/cdc497bb7cbb13f6dd4ad2b49ce8eeda83ea984d
--
Simon McVittie
Collabora Ltd. <http://www.collabora.com/>
--- End Message ---
--- Begin Message ---
Version: 1.6.1-2
These bugs were fixed in 1.6.1-2, which didn't actually make it to unstable.
--
Eric Dorland <[email protected]>
43CF 1228 F726 FD5B 474C E962 C256 FBD5 0022 1E93
--- End Message ---
