I got some information from a user on a more recent duplicate (bug
2063533). The problem seems to be that some users, when disabling the
stub-resolver, also create a symlink /etc/resolv.conf ->
/run/systemd/resolve/resolv.conf. This is not actually necessary because
systemd-resolved will make stub-resolv.conf a symlink to resolv.conf
when DNSStubListener=no.
Hence, the command
cp "${DPKG_ROOT}/etc/resolv.conf"
"${DPKG_ROOT}/run/systemd/resolve/stub-resolv.conf"
in systemd-resolved.postinst fails because the source and destination
are *both* symlinks to /run/systemd/resolve/resolv.conf.
** Also affects: systemd (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Noble)
Status: New => Triaged
** Changed in: systemd (Ubuntu Noble)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags added: foundations-todo systemd-sru-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047975
Title:
package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade:
installed systemd-resolved package post-installation script subprocess
returned error exit status 1 [cp: '/etc/resolv.conf' and
'/run/systemd/resolve/stub-resolv.conf' are the same file]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
