Hi everyone, Systemd (with the resolvconf USE flag) now supports an interface for programs to call resolvconf and have them managed by systemd-resolved. It feels as though this would be a candidate for a virtual/resolvconf package that uses either openresolv or systemd-239[resolvconf]? The current packages with a hard dependency on openresolv are the following: net-misc/netctl net-misc/networkmanager net-vpn/openconnect net-vpn/vpnc The first step would be to get the virtual in place, then convert over the above packages to make use of it. This bug is designed as a tracker to do those things. I don't know who it makes best sense to look after the virtual, but I figured perhaps Alon who looks after openresolv at the moment? (Note: there is a bug in the current resolvconf support see [1]) [1] https://github.com/systemd/systemd/issues/9423
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b53a8ddd0bbdf1848a35f60a89c66de5014e125d commit b53a8ddd0bbdf1848a35f60a89c66de5014e125d Author: Alon Bar-Lev <alonbl@gentoo.org> AuthorDate: 2018-08-24 17:32:05 +0000 Commit: Alon Bar-Lev <alonbl@gentoo.org> CommitDate: 2018-08-24 17:32:05 +0000 virtual/resolvconf: initial add Bug: https://bugs.gentoo.org/show_bug.cgi?id=659220 Package-Manager: Portage-2.3.40, Repoman-2.3.9 virtual/resolvconf/metadata.xml | 7 +++++++ virtual/resolvconf/resolvconf-1.ebuild | 12 ++++++++++++ 2 files changed, 19 insertions(+)
Awesome, thanks Alon! 5:)
I just noticed that NetworkManager was updated, but still depended explicitly on openresolv, so I've opened bugs that block this one, for the packages that do that. I also noticed that virtual/resolvconf doesn't yet list >=sys-apps/systemd-239-r1[resolvconf]. As of version 239-r1, the bug I identified has been fixed, and I've been using it without problem since then. @alon, would you be able to add the >=sys-apps/systemd-239-r1[resolvconf] dependency as a second option to fulfill the dependency please? If it's second then it won't affect anyone's current installation, but there's a chance that future installs will have systemd already satisfied, and the flag in most packages is the same, which is the only way I can see people could unknowingly end up using the systemd implementation. I think that's probably a reasonable way of slowly getting the option out there without forcing it on anyone, but happy to defer to different opinions. 5:) Thanks very much! 5:)
(In reply to Mike Auty from comment #3) > @alon, would you be able to add the >=sys-apps/systemd-239-r1[resolvconf] > dependency as a second option to fulfill the dependency please? Hi, You can do this yourself, no reason to wait for me. Thanks.
Thanks, I just didn't want to tread on your feet. All done as of commit b93b8cc8621. 5:)
Now that systemd-239 has been stabilized without all the blockers being fixed, what is the recommended workaround? (I have a merge conflict between openresolv and systemd.)
The easiest solution would be to set USE="-resolvconf" for sys-apps/systemd. Otherwise you'd need to figure out which package depends on net-dns/openresolv (there's only 3 left, and I'll be fixing vpnc soon) and sign up to the ticket for that package. The authors should be aware, but you can always mention that it's now stable and therefore more users are likely to encounter the issue. Hope that's of some help?
All blockers have be resolved.
