On Tuesday, April 14, 2020 9:23:27 PM CEST Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/systemd-resolved > > == Summary == > > Enable systemd-resolved by default. ... We had serious headaches because racy systemd-resolved got enabled for some unknown reasons on copr builders before (and my host as well, for example). I filled bug [1] and then I was told that nobody tests/maintains systemd-resolved... why on earth I'd opt-in to use that. Can we fix the bug, so the generated resolv.conf pointing to local server does work _immediately_ inside mock, and isn't it port-triggered (or what it is :-))? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1710699 Pavel _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
