[Touch-packages] [Bug 1892798] Re: eliminating resolvconf/openresolv dependencies

2020-08-25 Thread Jason A. Donenfeld
> wireguard package => please feed DNS data direct to systemd-resolved
using either dbus or the cli.

Absolutely not. We're not going to add vendor-specific hacks for broken
distros that are unable to include the standard interface for this kind
of thing, resolvconf(8). This is a pretty clear case of downstream being
broken.

> Unfortunately systemd's resolved's resolvctl is not compatible with
Debian's/Ubuntu's historical resolvconf.

First of all, we're not talking about systemd's resolvectl. We're
talking about systemd's resolvconf compatibility symlink which provides
the same interface as openresolv or the debian resolvconf monster.

With that clarified, if you still think there's a problem due to
Debian's resolvconf using an interface prefix list, I think you're
incorrect there too. Firstly, openresolv doesn't act that way, and
things work fine. Secondly, systems that have moved to systemd-resolved
(that is, Ubuntu itself) have in the process _broken_ resolvconf anyway.
Replacing broken resolvconf with one that is less broken -- even if it
doesn't do priority interface prefixes -- is still a marked improvement.
And thirdly, every script I've seen that uses resolvconf actually
continues to work fine with systemd's compatibility symlink of
resolvconf; if any you see don't, why not fix them?

So, in other words, I don't think you've presented a very compelling
argument at all. I can't see any correct technical reasoning in what you
wrote. It seems like adding the resolvconf compatibility symlink is a
marked improvement over the current broken status quo.

** Summary changed:

- eliminating resolvconf/openresolv dependencies
+ systemd package missing resolvconf(8) compatibility symlink, and a Provides: 
resolvconf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1892798

Title:
  systemd package missing resolvconf(8) compatibility symlink, and a
  Provides: resolvconf

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1892798] Re: eliminating resolvconf/openresolv dependencies

2020-08-25 Thread Dimitri John Ledkov
wireguard package => please feed DNS data direct to systemd-resolved
using either dbus or the cli.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1892798

Title:
  eliminating resolvconf/openresolv dependencies

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1892798] Re: eliminating resolvconf/openresolv dependencies

2020-08-25 Thread Dimitri John Ledkov
In ubuntu everything should feed DNS information direct into resolved whenever 
possible.
We are working on improving it, for example in groovy isc-dhcp-client & 
ifupdown started to do that too.

Unfortunately systemd's resolved's resolvctl is not compatible with
Debian's/Ubuntu's historical resolvconf.

Specifically Debian/Ubuntu has a lot of $interface.$suffix where $suffix
is arbitrary, such syntax is widely used and not supported by systemd.

So for the time being it is not possible to switch /sbin/resolvconf to
be the one provided by systemd.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1892798

Title:
  eliminating resolvconf/openresolv dependencies

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1892798] Re: eliminating resolvconf/openresolv dependencies

2020-08-25 Thread Jason A. Donenfeld
Thanks for bringing this to my attention. I believe your assessment is
correct. Do you know which Ubuntu first started using resolved? How far
back do we need to make changes?

There are two facets of this:

1) The Ubuntu systemd package should install the resolvconf
compatibility symlink. I have no idea why this isn't already the case,
and that seems like a bug that should be remedied ASAP. resolvconf(8) is
the standard interface for programs to interact with DNS, which is why
systemd provides it. Not providing it is super confusing.

2) The Recommends in the wireguard package should be adjusted.

I believe apw@ can handle (2). Somebody on the systemd team should
handle (1).

** Changed in: wireguard (Ubuntu)
   Status: New => Confirmed

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1892798

Title:
  eliminating resolvconf/openresolv dependencies

Status in systemd package in Ubuntu:
  Confirmed
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp