Hi Paul,
Paul Gevers <elbrus@debian.org> (2025-05-28):
> On 27-05-2025 15:59, Cyril Brulebois wrote:
> > I'm still ambivalent about this, and I still don't want to push in
> > either direction. I'll just mention that reviewing, merging, and
> > also adjusting… is all done as far as I'm concerned.
> >
> > The remaining question is whether that's for trixie or forky.
>
> I'm assuming that if we were to accept this, we'd enlarge the key
> package set. Let's not do that this late in the cycle.
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
but I'd be very fine with *not* enlarging the key package set, and
having no specific “protection” against autoremovals for those two
prospective new desktop environments.
If desktop tasks were indeed injected manually in the past, I suppose
it would be sufficient not to inject the new ones into the DB during
this cycle, and delay that until forky development opens?
If that's more complicated and/or generally just too late, that's also
fine with me. (Here I'm merely trying to understand the key packages
picture a little better, not trying to push harder.)
Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature