From Fedora Project Wiki

(drop unfilled or obsolete sections)
Line 39: Line 39:
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 =
{{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 [[QA]] team <!--[proven testers group dormant]: ''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]].
= Where can I find the ''critical path''? =
= Where can I find the ''critical path''? =

Revision as of 19:30, 7 November 2014

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.


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.


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


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:


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:

yum groupinfo 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 is stored in the packagedb for both rawhide and branched.

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