On Sunday, August 30, 2020 8:36:46 AM MST Michael Catanzaro wrote: > On Sun, Aug 30, 2020 at 9:06 am, Michael Catanzaro > <mcatanz...@gnome.org> wrote: > > > I don't know what to do about this. Ideally we would figure out > > what's wrong and sneak a freeze exception into the beta release. If > > the file in 3. is not a symlink, then that would be what's wrong, but > > it ought to be a symlink. > > > I just did a test install. From the live environment, > post-installation, I see: > > $ pwd > /mnt/sysroot/etc > $ ls -l | grep resolv > -rw-r--r--. 1 root root 729 Aug 30 11:19 resolv.conf > > So the file is indeed not a symlink. That tells NetworkManager that the > file is to be managed by NetworkManager, not by systemd. > > So basically you discovered our change is totally broken. Thanks for > testing. I've reported > https://bugzilla.redhat.com/show_bug.cgi?id=1873856.
This is one of the reasons I've been warning you about this logic from the start. This heavy-handed change is going to be a nightmare if executed this way. A simple fix would be to leave existing systems alone, and only create that symlink on new installs. That would simplify the logic, and prevent breaking peoples' systems needlessly. All users would benefit this way. -- John M. Harris, Jr. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
