Hi, On 28-05-2025 21:30, Cyril Brulebois wrote:
To be honest I've tried to answer questions as best as I could when I
got asked whether dropping this or that package from the key package
set would be OK, but I've never wondered how it is built. A quick look
at https://udd.debian.org/cgi-bin/key_packages.yaml.cgi suggests all
desktop tasks are there:
kibi@tokyo:~$ awk '/^- reason: task-.*desktop / { print $3}' key_packages.yaml|sort -u
task-cinnamon-desktop
task-cyrillic-desktop
task-gnome-desktop
task-gnome-flashback-desktop
task-kde-desktop
task-lxde-desktop
task-lxqt-desktop
task-mate-desktop
task-xfce-desktop
(8 choices currently offered by pkgsel calling tasksel, plus
Cyrillic support for some reason.)
I'm not immediately understanding how those get in there based on
skimming over https://release.debian.org/key-packages.html and
https://salsa.debian.org/qa/udd/-/blob/master/scripts/update-key-packages.pl
I think it's like this (pkgsel doesn't declare task-*desktop dependencies AFAICT): d-i -> debian-edu-install -> debian-edu-config -> education-tasks -> tasksel (and as tasksel comes from src:tasksel, all binaries from it are automatically key [1]).
I would *love* to avoid having all the desktops (and what they pull in) in the key package set, but I also don't want to do that while making your work harder without being aligned on what both sides expect from that. I think now is not a good moment to change the definition of the key package set. Graham and I have been discussing different definitions already, but that's for forky.
Paul [1] https://release.debian.org/key-packages.html
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature