On Fri, Apr 12, 2024 at 06:00:41PM -0700, Adam Williamson wrote:
This should have been an announced Change. This is a significant change with wide impact.
I've filed a bug, proposed it as a blocker, and filed a FESCo ticket asking FESCo to designate the bug as a blocker.
https://bugzilla.redhat.com/show_bug.cgi?id=2274830 https://pagure.io/fesco/issue/3196
I admit I was also initially surprised. But, this actually has been going through the Change process for a while:
F33: https://fedoraproject.org/wiki/Changes/NetworkManager_keyfile_instead_of_ifc... F36: https://fedoraproject.org/wiki/Changes/NoIfcfgFiles F39: https://fedoraproject.org/wiki/Changes/MigrateIfcfgToKeyfile
That last one actually says:
The upstream NetworkManager project has recently declared the ifcfg plugin as deprecated. This means that the code will only receive bug fixes, and will not get new functionality such as supporting new properties.
With this change, existing profiles in ifcfg format will be automatically migrated to the native keyfile format via a migration service shipped with the NetworkManager-initscripts-ifcfg-rh package. In Fedora, we plan to drop the plugin by Fedora Linux 41.
(Emphasis on the last line.)
The words "the network-scripts subpackage is deprecated and will be removed" do not seem to have appeared in the release notes, and in retrospect that probably should have been stronger.
"Gone in 40" _does_ technically fit into the letter of "drop by 41"... but maybe not the spirit?
I think a "drop in 41" change (and a clear item in the F40 release notes!) is probably the best way to clear the air -- but I don't think the maintainers stepped around the process here.