From Fedora Project Wiki
mNo edit summary
(adding release notes tracker)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Removing network-scripts package =
= Removing network-scripts package =


{{Change_Proposal_Banner}}


== Summary ==
== Summary ==


<code>network-scripts</code> package will be removed in Fedora 41. By removing the package, we also remove support for legacy network scripts that have been deprecated since 2018.
<code>network-scripts</code> package will be removed in Fedora 41. By removing the package, we also remove support for legacy <code>ifup/ifdown</code> network scripts that have been deprecated since 2018.


== Owner ==
== Owner ==


* Name: [[User:jamacku| Jan Macku]]
* Name: [[User:jamacku| Jan Macku]], [[User:lnykryn| Lukáš Nykrýn]]
* Name: [[User:lnykryn| Lukáš Nykrýn]]


* Email: [mailto:jamacku@redhat.com jamacku@redhat.com]
* Email: [mailto:jamacku@redhat.com jamacku@redhat.com], [mailto:lnykryn@redhat.com lnykryn@redhat.com]
* Email: [mailto:lnykryn@redhat.com lnykryn@redhat.com]


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF41]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 23: Line 20:


<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
<!-- [[Category:SelfContainedChange]] -->
<!-- [[Category:SystemWideChange]] -->
[[Category:SystemWideChange]]


* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f41/ Fedora Linux 41]
* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f41/ Fedora Linux 41]
* Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
* Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
* [<will be assigned by the Wrangler> devel thread]
* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/4DDBIE5SBLV4DNBDT5GU5SL4ZYSPGGFR/ Announced]
* FESCo issue: <will be assigned by the Wrangler>
* [https://discussion.fedoraproject.org/t/f41-change-proposal-removing-network-scripts-package-system-wide/118553 Discussion thread]
* Tracker bug: <will be assigned by the Wrangler>
* FESCo issue: [https://pagure.io/fesco/issue/3221 #3221]
* Release notes tracker: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2293626 #2293626]
* Release notes tracker: [https://gitlab.com/fedora/docs/fedora-linux-documentation/release-notes/-/issues/98 #98]


== Detailed Description ==
== Detailed Description ==
Line 78: Line 76:


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
A good "how to test" should answer these four questions:
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


Networking should work as before the removal of <code>network-scripts</code> package.


== User Experience ==
== User Experience ==
Line 129: Line 113:


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are at https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/ -->
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are at https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.  
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.  

Latest revision as of 15:24, 2 October 2024

Removing network-scripts package

Summary

network-scripts package will be removed in Fedora 41. By removing the package, we also remove support for legacy ifup/ifdown network scripts that have been deprecated since 2018.

Owner

Current status

Detailed Description

network-scripts will be removed in Fedora 41. It provides legacy ifup/ifdown scripts as well as network.service.

The network-scripts were deprecated in 2018, and since then, upstream has provided only limited support.

The main reason for removing network-scripts is that ISC dhcp has not been maintained upstream since the end of 2022. There is plan to remove it upcoming Fedora release. Network scripts heavily depend on the DHCP client, and since Network Scripts are no longer developed, there is no chance of updating them to use an alternative client.

Feedback

Benefit to Fedora

We don't deliver software that has been deprecated for many years, unmaintained upstream, and for which we don't have resources to maintain downstream. Additionally, it simplifies networking tasks for users and administrators because NetworkManager will be used more uniformly across Fedora environments.

Scope

  • Proposal owners: Removing of network-scripts rpm package.
  • Other developers: Make sure that dependency on network-scripts package is removed (see #Dependencies).
  • Release engineering: N/A (not needed for this Change)
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Community Initiatives: N/A (not needed for this Change)

Upgrade/compatibility impact

ifup/ifdown command are no longer available. Use nmcli connection up/down or networkctl up/down instead.

Old ifcfg network configuration should still work thanks to NetworkManager-initscripts-ifcfg-rh package. No migration is needed, but it is recommended to migrate from ifcfg to keyfiles configuration.

You can use one of the following articles on how to migrate:

How To Test

Networking should work as before the removal of network-scripts package.

User Experience

Dependencies

RPM packages that depends in some form on network-scripts:

Note that this will also affect all users with local custom network-scripts that require functionality from network-scripts package.

Contingency Plan

  • Contingency mechanism: Since dhcp client is no longer maintained and is going to be deprecated in Fedora, there is currently no contingency mechanism.
  • Contingency deadline: beta freeze
  • Blocks release: No

Documentation

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/NetworkScriptsRemoval&oldid=721293"