Added more notes about bodhi and critpath.

This commit is contained in:
Adam Saleh 2021-06-04 11:34:56 +02:00
parent 010fdb0050
commit d4474a2baf

View file

@ -28,8 +28,25 @@ Bodhi already has concept that maps to releases and components,
we should be able to create auxiliary table that will pair these with additional metadata, we should be able to create auxiliary table that will pair these with additional metadata,
mostyl the critical-path flag, that previously had to be queried from PDC. mostyl the critical-path flag, that previously had to be queried from PDC.
Pagure-dist-git PDC actually isn't the source-of-truth for packages on critical path.
--------------- The source of truth, according to https://fedoraproject.org/wiki/Critical_path_package is
in https://pagure.io/fedora-comps/tree/main when you search for groups with critical-path-*
prefix. For example: https://pagure.io/fedora-comps/blob/main/f/comps-f35.xml.in#_622
The data is available through dnf, but generating it can be really slow, PDC is then used as
a sort of a pre-computed cache.
To update it, we used to use https://docs.pagure.org/releng/sop_update_critpath.html
but now we have https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/pdc_update_critpath.py
Only place we actually use the information during the fedora release is in Bodhi,
to have stricter requirements on `critpath` package updates in Bodhi:
https://github.com/fedora-infra/bodhi/blob/master/bodhi/server/util.py#L192
Pagure-dist-git
---------------
Pagure-dist-git would take over responsibilities for Pagure-dist-git would take over responsibilities for