From Fedora Project Wiki
(→‎Implementation: drop command for pre-F22)
(5 intermediate revisions by 5 users not shown)
Line 36: Line 36:
You can list the packages in these groups with the following command, replacing 'critical-path-base' with the name of the group you're interested in:
You can list the packages in these groups with the following command, replacing 'critical-path-base' with the name of the group you're interested in:


<pre>yum groupinfo critical-path-base</pre>
<pre>dnf group info critical-path-base</pre>


For more information on {{filename|comps.xml}} see [[how to use and edit comps.xml for package groups]].
For more information on {{filename|comps.xml}} see [[how to use and edit comps.xml for package groups]].


= Maintainer Responsibilities =
= Where can I find the ''critical path''? =
 
{{admon/important|FIXME|This section needs to be updated.}}
 
If a package is added to the critical path list as a result of normal package dependency the package maintainer will be notified through direct email and the extra processes they have to go through.  (IS THIS TRUE)
 
If they do not wish to maintain the packages with these extra processes then they have to orphan the package.  A new maintainer will need to be found.


= Tester Responsibilities =
The critical path package list for all releases is stored in [https://pdc.fedoraproject.org/ PDC].


The [[QA]] team <!--[proven testers group dormant]:https://admin.fedoraproject.org/accounts/group/view/proventesters ''proventesters'' FAS group]--> is responsible for ensuring minimal disruption to the critical actions listed above.  If you would like to <!--[proven testers group dormant]:join ''proventesters'', check out [[Proven_tester]] where you will also find instructions on the testing process.--> help out with testing critical path packages, please read the [[QA:Updates_Testing]] page and the [[QA:Update_feedback_guidelines]].
The most recent lists of critical path packages are available at:
 
= Where can I find the ''critical path''? =


The critical path package list is stored in the packagedb for both [[Releases/Rawhide|rawhide]] and [[Releases/Branched|branched]].
* [https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=master&active=true&critical_path=true&type=rpm Rawhide]
* [https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=f{{FedoraVersionNumber|next}}&active=true&critical_path=true&type=rpm {{FedoraVersion|long|next}} (if branched)]
* [https://pdc.fedoraproject.org/rest_api/v1/component-branches/?name=f{{FedoraVersionNumber}}&active=true&critical_path=true&type=rpm {{FedoraVersion|long}}]


The most recent list of critical path packages are available at:
Read API documentation [https://pdc.fedoraproject.org/rest_api/v1/component-branches/ here].


* [https://admin.fedoraproject.org/pkgdb/lists/critpath?tg_format=plain&collctn_list=f{{FedoraVersion||next}} Branched] (aka {{FedoraVersion|long|next}})
* [https://admin.fedoraproject.org/pkgdb/lists/critpath?tg_format=plain&collctn_list=devel Rawhide] (aka {{FedoraVersion|long|next2}})
<!--
<!--
SAMPLE USAGE of the Parser Function #time -- See http://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23time
SAMPLE USAGE of the Parser Function #time -- See http://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23time

Revision as of 13:28, 3 January 2021

For information on the proposal, see Critical Path Packages Proposal.

A critical path package is a specially managed package in Fedora that provides some essential or core functionality. Updates for critical path packages must undergo additional verification before they can be distributed to the community at large.

Background

Previously, documented policy treated every package the same. While good for uniformity, in reality certain packages require extra attention and care when updating and testing. These packages have potential to break the critical path of use of our Fedora distribution. As part of a Fedora Activity Day, several contributors proposed a critical set of actions that must not be broken. The packages required to sustain these actions make up the critical path.

Actions

Packages within the critical path are required to perform the most fundamental actions on a system. Those actions include:

  • graphical network install
  • post-install booting
  • decrypt encrypted filesystems
  • graphics
  • login
  • networking
  • get updates
  • minimal buildroot
  • compose new trees
  • compose live

Implementation

A set of groups are defined in the comps.xml file to include packages required for the critical use cases listed above. Since package dependencies change regularly, the comps.xml groups are then used to dynamically generate the list of packages.

The critical path package groups in comps.xml are listed below: 

@core
@critical-path-base
@critical-path-gnome
@critical-path-apps
@critical-path-kde
@critical-path-lxde
@critical-path-xfce

You can list the packages in these groups with the following command, replacing 'critical-path-base' with the name of the group you're interested in: 

dnf group info critical-path-base

For more information on comps.xml see how to use and edit comps.xml for package groups.

Where can I find the critical path?

The critical path package list for all releases is stored in PDC.

The most recent lists of critical path packages are available at:

Read API documentation here.


Retrieved from "https://fedoraproject.org/w/index.php?title=Critical_path_package&oldid=599546"