--===============1385445510727265420== Content-Type: multipart/alternative; boundary="000000000000de894d05adfcf955" --000000000000de894d05adfcf955 Content-Type: text/plain; charset="UTF-8" On Saturday, August 29, 2020, John M. Harris Jr wrote: > On Monday, August 10, 2020 9:52:42 AM MST Michael Catanzaro wrote: > > On Tue, Aug 4, 2020 at 9:08 am, Michael Catanzaro > > wrote: > > > > > Zbigniew, do you agree that we should remove the script if and only > > > if it is generated by NetworkManager? Otherwise, the change is only > > > partially-implemented for users upgrading from F32 and earlier. > > > > > > We agreed to go with this approach. /etc/resolv.conf will be moved to > > /etc/resolv.conf.orig-with-nm on upgrade to F33 if the 'Generated by > > NetworkManager' comment is present. If you've gone to the trouble to > > prevent NetworkManager from managing this file, it's likely you've also > > removed the comment. If not, you can either remove the comment before > > upgrade, or recover your previous configuration from the > > /etc/resolv.conf.orig-with-nm backup file after upgrade, and hopefully > > have only a small blip in your upgrade experience. This will make the > > upgrade work properly for the 99% of users who don't mess with the > > defaults and should not be too difficult for those who do. > > That comment being there doesn't mean that is still the case. I haven't > removed that comment, I just fixed the file. It would be best to just not > mess > with this file on upgrade, and, instead, change the behavior of new > installs. > This wouldn't break anything, and would have all newly installed systems > with > the configuration you seem to want. > > There's no reason to break peoples' systems here, we can easily plan for > this. > I also don't know where you're getting this estimate of 99% of users not > changing this file. People expect to get the new features on upgrades without having to reinstall. There is no reason to upgrades differently - if you have customized configuration you should be reading the changes before doing an upgrade. > -- > John M. Harris, Jr. > > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-leave@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 > --000000000000de894d05adfcf955 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Saturday, August 29, 2020, John M. Harris Jr <johnmh@splentity.com> wrote:
On Monday, August 10, 2020 9:52:42 AM MST Michael Catan= zaro wrote:
> On Tue, Aug 4, 2020 at 9:08 am, Michael Catanzaro
> <mcatanzaro@gnome.org&g= t; wrote:
>
> > Zbigniew, do you agree that we should remove the script if and on= ly
> > if it is generated by NetworkManager? Otherwise, the change is on= ly
> > partially-implemented for users upgrading from F32 and earlier. >
>
> We agreed to go with this approach. /etc/resolv.conf will be moved to =
> /etc/resolv.conf.orig-with-nm on upgrade to F33 if the 'Generated = by
> NetworkManager' comment is present. If you've gone to the trou= ble to
> prevent NetworkManager from managing this file, it's likely you= 9;ve also
> removed the comment. If not, you can either remove the comment before =
> upgrade, or recover your previous configuration from the
> /etc/resolv.conf.orig-with-nm backup file after upgrade, and hopefully=
> have only a small blip in your upgrade experience. This will make the =
> upgrade work properly for the 99% of users who don't mess with the=
> defaults and should not be too difficult for those who do.

That comment being there doesn't mean that is still the case. I haven&#= 39;t
removed that comment, I just fixed the file. It would be best to just not m= ess
with this file on upgrade, and, instead, change the behavior of new install= s.
This wouldn't break anything, and would have all newly installed system= s with
the configuration you seem to want.

There's no reason to break peoples' systems here, we can easily pla= n for this.
I also don't know where you're getting this estimate of 99% of user= s not
changing this file.

People expect to get th= e new features on upgrades without having to reinstall.=C2=A0
There is no reason to upgrades differently - if you have custom= ized configuration you should be reading the changes before doing an upgrad= e.
=C2=A0
--
John M. Harris, Jr.

_______________________________________________
devel mailing list -- deve= l@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.or= g/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list= _guidelines
List Archives: https://lists.fedoraproject.<= wbr>org/archives/list/devel@lists.fedoraproject.org
--000000000000de894d05adfcf955-- --===============1385445510727265420== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGV2ZWwgbWFp bGluZyBsaXN0IC0tIGRldmVsQGxpc3RzLmZlZG9yYXByb2plY3Qub3JnClRvIHVuc3Vic2NyaWJl IHNlbmQgYW4gZW1haWwgdG8gZGV2ZWwtbGVhdmVAbGlzdHMuZmVkb3JhcHJvamVjdC5vcmcKRmVk b3JhIENvZGUgb2YgQ29uZHVjdDogaHR0cHM6Ly9kb2NzLmZlZG9yYXByb2plY3Qub3JnL2VuLVVT L3Byb2plY3QvY29kZS1vZi1jb25kdWN0LwpMaXN0IEd1aWRlbGluZXM6IGh0dHBzOi8vZmVkb3Jh cHJvamVjdC5vcmcvd2lraS9NYWlsaW5nX2xpc3RfZ3VpZGVsaW5lcwpMaXN0IEFyY2hpdmVzOiBo dHRwczovL2xpc3RzLmZlZG9yYXByb2plY3Qub3JnL2FyY2hpdmVzL2xpc3QvZGV2ZWxAbGlzdHMu ZmVkb3JhcHJvamVjdC5vcmcK --===============1385445510727265420==--