On 1/20/26 22:45, Jorge Merlino wrote:
On Fri, 12 Dec 2025 18:29:41 -0300 Jorge Merlino
<[email protected]> wrote:
Hi folks,
Can any of you review this pull request? It has been waiting for a while.
Kindly asking again if anyone can review this PR.
Hi!
I still don't see why do we spend resources on this.
Having more than one resolver on the system is, a very least,
a niche config, it's a very rare configuration to have. On
such a special configuration, sure it's possible to run
systemctl disable unbound-recolvconf
once and be done with this issue.
Again, for a such a rare config, it might be that resolvconf
is diverted for something else which actually works, unlike
a somewhat dumb resolvconf emulation by systemd-resolved, -
and in that case, this Conflicts: will do more harm than good.
My point is that we don't really know when this configuration
is actually useful (it is definitely not useful for vast majority
of installs), so we can't really know how to deal with it.
For a very similar case but with a MUCH more significant outcome,
how about fixing this one instead --
resolvconf[PID]: Failed to resolve interface "NetworkManager": \
No such device
This happens when NetworkManager is managing network, and systemd-resolved
is used as local caching resolver. This is actually a very common
configuration and very valid one.
Thanks,
/mjt
