Bug#939904: Bug#930735: WireGuard: Add resolvconf as optional dependency

[Luca Boccassi]

On Mon, 09 Sep 2019 19:14:46 -0400 Daniel Kahn Gillmor
<dkg at fifthhorseman.net> wrote:
> Control: clone 930735 -1
> Control: reassign -1 src:systemd
> Control: severity -1 wishlist
> Control: blocks 930735 with -1
> Control: retitle -1 systemd should ship resolvconf symlink in some
package
> Control: affects -1 + wireguard-tools
> 
> Hi Willem--
> 
> Thanks for the followup.
> 
> It sounds to me like there is still no great suggestion on how to
make
> this work smoothly, or a clear consensus on what we should do to
ensure
> that the DNS = directive works for wg-quick :(
> 
> On Sat 2019-09-07 08:55:17 +0200, Willem van den Akker wrote:
> > If resolvectl is symlinked to resolvconf this also should work. But
the
> > symlinked is not on my system. Even with resolvectl available.
> 
> For most modern debian systems, this seems like the simplest
approach,
> but i don't think it's safe to assume it will work automatically yet.
> 
> Perhaps the systemd source package could ship a systemd-resolvconf
> binary package that (a) enables and runs the systemd-resolved service
> automatically, and (b) ships the symlink from /sbin/resolvconf to
> resolvectl, and (c) Provides: and Conflicts: with resolvconf itself
> (similar to how openresolv does).
> 
> I note that the systemd binary package already ships a resolvconf
> manpage as a symlink to the resolvectl manpage, but it puts it in
> section 1 of the manual, instead of section 8, so it doesn't manage
to
> conflict with resolvconf or openresolv.  that's a little bit weird
too :/
> 
> I'm cloning this wireguard bug report to the systemd source package
to
> see whether this suggestion is something they'd be willing to
consider.
> Debian systemd maintainers -- feel free to suggest an alternate
> resolution if you have one you'd prefer.
> 
> If systemd would do that, then i'd be willing to add a new control
line
> for wireguard-tools as something like this:
> 
>    Recommends: systemd-resolvconf | resolvconf
> 
> Does this seem like a plausible suggestion?  This sort of system
> integration across multiple potentially conflicting packages is a bit
of
> a pain point in Debian, and it's not clear how to make it work
sensibly
> and easily for everyone.

Hi,

systemd-resolved is now in experimental as a new package, and if there
are no huge breakages (it has provides/conflicts/replaces: resolvconf
and installs the symlinks) it will make it to unstable too at some
point soon. So the plan to add the Recommends you mentioned sounds good
to me.

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20220805/a4e3c902/attachment.sig>