Your message dated Tue, 10 Dec 2019 16:06:10 +0000
with message-id <[email protected]>
and subject line Bug#847440: fixed in resolvconf 1.80
has caused the Debian Bug report #847440,
regarding resolvconf: run resolvconf service before any networking service
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.)


-- 
847440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: resolvconf
Version: 1.79.1
Severity: normal
Tags: patch
User: [email protected]
Usertags: origin-ubuntu zesty ubuntu-patch

Dear Maintainer,


When using other networking services (networkd, NetworkManager) instead of
networking, resolvconf doesn't run early enough to ensure it's watching for
DNS changes.  

In Ubuntu, the attached patch was applied to achieve the following:

Instead of encoding each networking service name in the service unit file use 
network-pre.target to ensure resolvconf runs before any other networking
software.


  * debian/resolvconf.service: resolvconf service must run before any of the
  possible network configuration services (ifupdown, networkd, NetworkManager)
  so use network-pre.target instead of service names. (LP: #1636912)


Thanks for considering the patch.


-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-51-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru resolvconf-1.79/debian/resolvconf.service resolvconf-1.79.1/debian/resolvconf.service
--- resolvconf-1.79/debian/resolvconf.service	2016-04-01 06:53:22.000000000 -0500
+++ resolvconf-1.79.1/debian/resolvconf.service	2016-12-08 03:23:14.000000000 -0600
@@ -2,7 +2,8 @@
 Description=Nameserver information manager
 Documentation=man:resolvconf(8)
 DefaultDependencies=no
-Before=networking.service
+Before=network-pre.target
+Wants=network-pre.target
 
 [Service]
 RemainAfterExit=yes

--- End Message ---
--- Begin Message ---
Source: resolvconf
Source-Version: 1.80

We believe that the bug you reported is fixed in the latest version of
resolvconf, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura <[email protected]> (supplier of updated resolvconf 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 [email protected])


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

Format: 1.8
Date: Tue, 10 Dec 2019 16:45:20 +0100
Source: resolvconf
Architecture: source
Version: 1.80
Distribution: unstable
Urgency: medium
Maintainer: resolvconf team <[email protected]>
Changed-By: Andrej Shadura <[email protected]>
Closes: 832394 847440 877695 905907
Launchpad-Bugs-Fixed: 924836 1610479 1636912 1638836 1713149 1817903 1825194
Changes:
 resolvconf (1.80) unstable; urgency=medium
 .
   [ Thomas Hood ]
   * Bump Standards-Version; no changes required
   * Fix postrm for Ubuntu (LP: 1593489)
   * Update README to reflect the removal of pdnsd from the archive
   * In unit file use network-pre.target (Closes: #847440
     and LP: #1636912). Thanks to Ryan Harper.
   * Add systemd predictable interface name patterns (Closes: #877695,
     #905907). Thanks to Kevin Otte for the patch in LP: #1610479.
 .
   [ Steve Langasek ]
   * Eliminate all references to /etc/resolvconf/run.  This should all be done
     directly in /run, there is no reason to support making any of this
     configurable with a symlink since we already have a versioned dependency
     on the version of initscripts that introduces the /run transition.
   * etc/resolvconf/resolv.conf.d/head: add comment about
     'systemd-resolve --status', since systemd-resolved is now in use in all
     but the most unusual configurations, and expert users should be given
     guidance where to find the actual nameservers for debugging purposes.
     LP: #1638836.
 .
   [ Martin Pitt ]
   * debian/postinst: Make /etc/resolv.conf a relative symlink so that it
     works when setting up chroots.
 .
   [ Dimitri John Ledkov ]
   * Drop ifupdown dependency.
   * Drop upstart system job.
   * Use readlink -m when checking the link's destination.
     (LP: #924836)
   * Dereference /etc/resolf.conf when creating runtime configuration when
     migrating to resolvconf managed /etc/resolv.conf. The contents of
     /etc/resolv.conf (rather than the symlink target information) is
     needed in /run/resolvconf/resolv.conf and
     /run/resolvconf/interface/original.resolvconf during migration until
     resolvconf updates the config next. (LP: #1713149)
   * Move resolvconf & resolved integration system units from src:systemd
     to src:resolvconf. Also use a different unit name, to avoid
     breaks/replaces.
   * debian/postrm: if resolved managed stub config is available, migrate
     to it upon resolvconf removal.
 .
   [ Dan Streetman ]
   * Filter out the edns0 option that systemd-resolved has recently added
     to its stub-resolv.conf. Using the stub conf with edns0 set with
     non-local DNS servers can break name resolution. (LP: #1817903)
 .
   [ Alfonso Sánchez-Beato ]
   * bin/resolvconf: use flock so resolvconf can be called in parallel
     safely (LP: #1825194).
 .
   [ Andrej Shadura ]
   * Add /usr/sbin and /usr/bin to PATH (Closes: #832394).
   * Update the team email address.
   * Wrap and sort.
   * Add myself as a co-maintainer.
   * Verify ifquery is available before running it (we no longer require
     ifupdown).
   * Remove id-length from gbp.conf so commit hashes are not prepended
     to the changelog entries.
   * Port debian/rules to the dh 12 short form.
   * d/copyright: Use https protocol in Format field.
   * d/changelog: Remove trailing whitespaces.
   * d/control: Set Vcs-* to salsa.debian.org.
 .
   [ Théophile Helleboid ]
   * Add vpn* to the interfaces-order list.
Checksums-Sha1:
 b1cedf9e2c4704a13472bc25d792dc86c61ee1b3 1483 resolvconf_1.80.dsc
 6662f84ad411c072cfadb39160eda53d6cef7de2 72856 resolvconf_1.80.tar.xz
Checksums-Sha256:
 3daf174a5bbed580e802264750f31f63f006f7fbd2797e1fa97f7cbc9c60bfcf 1483 
resolvconf_1.80.dsc
 edad207fffa6612b7f547dc75f165d170b3d4b5f50028d2984d60d1136f07eae 72856 
resolvconf_1.80.tar.xz
Files:
 c3311134a4e94737669a016158b830d2 1483 net optional resolvconf_1.80.dsc
 b5739955a4958a7aad18df6b6eb565b0 72856 net optional resolvconf_1.80.tar.xz

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl3vviEACgkQXkCM2RzY
OdLoxAgAk1+OZF8at5a5SWEYZrxLe3DUlkoKZLF9NFCGQlNTcIltz1zQyYi15V7e
WxFYiMeNXD6mVd7S8iXY28M6xKcA4r6rp4xts1SysqGMNF1rDFEtaZyPP/noCLcM
3V/A6E0TorBUYoma7vZHywMryutartYkRMQ/r64JQEs+sB2wWB+64E+drjjWxSBk
ibpkAAmz4V2auYXe2XVttXxbJrnS4mykQQtVLAxS32dfW6TGDogfpad9D9Qk85PR
pUVQaMTMy9VCq0+66v0K5sc6UzkefsYQZEdjb5+bMIEnQeGAN9qnXEb4YS8UY1Qw
N3VMpY4AUr5VT7yJRSr0/yiXfpMHog==
=ezPb
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to