#171 Identify minimal set of critical path KDE Plasma stack packages
Closed: Fixed by siosm. Opened by ngompa.

@adamwill discovered yesterday that we practically have a non-existent critical path package set for KDE Plasma. The critical path package set in the composition groups are used to determine when OpenQA will run the full battery of tests on an update submitted in Bodhi.

Currently, sddm and qt5-qtwayland are there, but we definitely should have more than that.

Let's figure out what minimal set of packages make sense for this from our stack and get this set up.


Metadata Update from @ngompa:
- Issue tagged with: meeting

Well, not just that - being 'critical path' also means a package is subject to stricter requirements in Bodhi for being pushed stable.

For Kinoite, we currently use https://pagure.io/workstation-ostree-config/blob/main/f/kde-desktop-pkgs.yaml plus https://pagure.io/workstation-ostree-config/blob/main/f/fedora-kinoite.yaml filtered from the comps with https://pagure.io/workstation-ostree-config/blob/main/f/comps-sync-exclude-list.yml#_170.

Removing meeting tag. I don't think this is controversial. We just need someone to suggest a list of package and to make a PR to update the comps files.

Metadata Update from @siosm:
- Issue untagged with: meeting

Metadata Update from @siosm:
- Issue tagged with: need-work

This really needs doing. I just found that the default background for newly-generated F35 KDE live images is broken, but because no KDE packages are in critpath, the update that caused this was not tested and gated.

If nobody contributes to this soon I am just going to make up a definition myself and put it in comps.

OK, I did that: https://pagure.io/fedora-comps/pull-request/764

Comments and corrections welcome.

Thanks for doing this.

Metadata Update from @siosm:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata