there is a new release candidate.
Abort the testing of the 1.38-rc2 and start again with 1.38-rc3. Sorry about that.
This one brings an intentional change in behavior, w.r.t. the order in which IPv6 addresses are configured. That can affect source address selection for IPv6, but the new behavior is deemed preferable.
I worry, there is a bug in this release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1066#note_1233210
A revert of the patch currently fails to build: https://bodhi.fedoraproject.org/updates/FEDORA-2022-2edc1195fd#comment-2381650 . Will investigate tomorrow.
Sorry for any inconvenience.
@jakub, it seams, this breaks build with LTO. Here: https://koji.fedoraproject.org/koji/taskinfo?taskID=81973808
checking if gcc supports flag -fno-strict-aliasing in envvar CFLAGS... yes checking if gcc supports flag -flto -flto-partition=none in envvar CFLAGS... no configure: error: Link Time Optimization -flto is not supported. error: Bad exit status from /var/tmp/rpm-tmp.Uwjyx0 (%build) Bad exit status from /var/tmp/rpm-tmp.Uwjyx0 (%build)
@adamwill it is probably related to the changes how NetworkManager configures systemd-resolved. Is it possible to add some printf debugging statements before the failure? In particular
resolvectl ; nmcli device ; ip addr ; ip route.
Btw, yesterday we also released 1.28.0 which is now in rawhide (package "1.28.0-1"). That might have exactly the same problem. Does it?
Thank you for having extensive CI tests! That is awesome!!