Todd Zullinger writes:
The relevant parts of the diff from -1 to -2 are:
%posttrans resolved
+[ $1 -eq 1 ] || exit 0
+# Initial installation
+
And that's why an update to 11-1.fc35 ran the rest of the script.
- if ! test -e /etc/resolv.conf && ! test -L
/etc/resolv.conf; then
- ln -sv ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf || :
+ if ! test -e /etc/resolv.conf; then
+ ln -sv ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
elif test -d /run/systemd/system/ &&
! mountpoint /etc/resolv.conf &>/dev/null; then
- ln -fsv ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
|| :
+ ln -fsv ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
fi
Note the elif part. If the symlink exists, it's going to get reset if
systemd is installed.
So, if you don't have systemd-resolved currently installed, and then install
it, the existing symlink is going to get reset, one way or another. Which
might be fine, you're taking an explicit, manual action.
It skips the code which touches /etc/resolv.conf except on
initial install of systemd-resolved, at least, which would
have prevented this issue for most folks in this thread, I
believe.
Now it does.