[Bug 1901526] Re: On upgrade tries to replace /etc/systemd/resolved.conf
Dan Streetman
1901526 at bugs.launchpad.net
Fri Nov 6 21:54:22 UTC 2020
when you say "tries to replace" do you mean this:
Configuration file '/etc/systemd/resolved.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** resolved.conf (Y/I/N/O/D/Z) [default=N] ?
that's what I see when upgrading with a modified conf file, and it's expected behavior. If that's what you are seeing, then there is no bug, just say "N" to keep your modified version, or say "Y" and then modify it again after upgrade is complete.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1901526
Title:
On upgrade tries to replace /etc/systemd/resolved.conf
Status in systemd package in Ubuntu:
Invalid
Bug description:
When upgrading from Ubuntu 20.04.1 to 20.10, the new package tries to
replace resolved.conf which would break custom DNS configuration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1901526/+subscriptions
More information about the foundations-bugs
mailing list