Hello list, Jeremy, Simon, First, thank you Jeremy for pushing towards better GNOME live images. In the past few days there has been a flood of messages with proposed changes [1].
Let's discuss this on the mailing list instead of on individual merge requests on Salsa. I'm happy to see these good MRs and nearly pressed the 'Merge' button, until I realised that the situation for the live images is slightly more complicated... The reason I hesitate is, that I have some questions in mind: 1) What is the proper location for the fix? 2) Which live images can/should be affected? 3) Who decides what goes in the live images? The Philosophy as mentioned in the manual [2] says 'Only unchanged packages from Debian "main" and "non-free-firmware"'. I've been bending this rule by using 'rebuild.sh' for reproducibility fixes (which don't alter the functionality of the packages), but how far should be bending go? A) The fix should be made closest to its source * This would benefit all users of such package * It will apply to sid (and then forky) * If it needs to be fixed for trixie or bookworm, it needs to go to 'trixie-proposed-updates' and 'bookworm-proposed-updates', not to backport, because the backports are not used when generating the live images. * Changes to 'XXX-proposed-updates' need to be OK-ed by the release managers * An example is the inclusion of 'xiterm+thai'. That is coming from the Recommends of 'task-thai-desktop'. As I understand now, that package is causing confusion for non-Thai users and might even not be used by Thai users anyway. B) The fix should be made just for the live images * This needs no uploads of modified packages, it is organised by 'rebuild.sh' * It applies to sid, forky, trixie and bookworm all in one go (or sub selections of this list when if-statements are added to the script) * This bends the rules and bypasses the release managers * If Debian is installed with a netinst image instead, users will still get the unmodified behaviour C) Both of A and B * For short term fixes, use B. And in parallel strategy A should be followed Note that although I've become a DD half a year ago, I'm a non-uploading DD, so I'll need help in getting the packages into the archive. With kind regards, Roland Clobus [1] https://salsa.debian.org/live-team/live-tasks/-/merge_requests/9 https://salsa.debian.org/live-team/live-tasks/-/merge_requests/10 https://salsa.debian.org/live-team/live-tasks/-/merge_requests/11 https://salsa.debian.org/live-team/live-tasks/-/merge_requests/12 https://salsa.debian.org/live-team/live-tasks/-/merge_requests/13 https://bugs.debian.org/1129069 https://bugs.debian.org/1125280 https://bugs.debian.org/1110661 [2] https://live-team.pages.debian.net/live-manual/html/live-manual/about-project.en.html#95
OpenPGP_signature.asc
Description: OpenPGP digital signature
