Fedora 33 brough systemd-resolved by default; but in Fedora 35 this somehow got reverted.
I've proposed it as a blocker, but the main point of the thread is really to discuss the general case of whether such a thing is a blocker? I'm not thinking of a release criterion that applies to this case. It seems reasonable that approved+implemented features that subsequently break (accidentally or even intentionally when absent an approved change) should be blockers. Server edition is missing /etc/resolv.conf symlink (use systemd-resolved) https://bugzilla.redhat.com/show_bug.cgi?id=2032085 -- Chris Murphy _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
