From Fedora Project Wiki
- ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->21 KB (3,130 words) - 16:21, 2 February 2023
- ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->16 KB (2,444 words) - 10:12, 31 May 2024
- ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->17 KB (2,562 words) - 16:42, 3 March 2022
- ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->17 KB (2,720 words) - 05:55, 20 May 2024
- ...er generating metadata in sqlite database format by default and simplified comps xml type in repodata. ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.17 KB (2,638 words) - 15:16, 10 April 2023
- ...er generating metadata in sqlite database format by default and simplified comps xml type in repodata. * Owner: Possibly others since it may touch -comps, systemd-boot, etc27 KB (3,633 words) - 19:04, 14 November 2023
- ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->28 KB (4,247 words) - 14:46, 17 April 2024
- ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. ** Modify comps accordingly14 KB (2,282 words) - 10:03, 8 October 2015
- Created 2 new groups in F12 comps.xml (critical-path-base and critical-path-gnome). Combining those two grou ...Jlaska directed curious contributors to the page describing how to propose comps.xml changes (see http://fedoraproject.org/wiki/PackageMaintainers/CompsXml)74 KB (9,055 words) - 08:57, 18 September 2016
- ...This page is no longer updated regularly. Talk to the [[SIGs/Python|Python SIG]] if you want to discuss it. }} ** See also: [[Changes/Update_comps_to_use_python3|Update comps to use python3]] ([[Releases/29 | Fedora 29]])19 KB (2,923 words) - 14:58, 6 May 2020
- | irc-support-sig || 3269 || yes || yes || yes | comps || 404 || no || no || no28 KB (3,359 words) - 20:44, 15 February 2017
- ...r with participants in the discussion including Yaakov on the grounds that comps were a consistent scheme. === Fedora SIG KDE Report Week 2008-02-12 ===42 KB (5,919 words) - 21:10, 20 September 2016
- ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. ...dhat-rpm-config PR #167], [https://pagure.io/fedora-comps/pull-request/704 comps PR #704]28 KB (4,394 words) - 21:18, 13 January 2022
- | style="color: #42427e" | and thanks to the great work of the Fonts Fonts SIG fonts support is getting much better in the recent releases with more fonts | style="color: #42427e" | comps50 KB (5,887 words) - 20:59, 17 September 2016
- | style="color: #488888" | | gst-mixer is in f11 repos and in comps | style="color: #4b904b" | | sig leaders I suppose87 KB (10,358 words) - 08:56, 18 September 2016