On Fri, Sep 6, 2024 at 9:16 AM Simon McVittie <s...@debian.org> wrote: > 0. Adapt some packages to stop depending on gjs or gnome-shell on armel: > […] > 1. Wait for release team ack > 2. Upload gjs/experimental and packages from (0.) to unstable > 3. Adapt meta-gnome3 so gnome-core and gnome are only built on > architectures that have a working gjs > 4. Remove only these armel *binaries* (as NBS), leaving the rest of their > source packages intact: > - gdm3 (from src:gdm3) > - gnome-core (from src:meta-gnome3) > - gnome (from src:meta-gnome3) > 5. Remove all binaries of these source packages from armel: > - eos-sdk > - foliate > - gjs > - gnome-characters > - gnome-maps > - gnome-shell > - gnome-shell-extension-desktop-icons-ng > - gnome-shell-extension-gsconnect > - gnome-shell-extension-manager > - gnome-shell-mailnag > - gnome-shell-pomodoro > - gnome-sound-recorder > - gnome-sushi > - gnome-weather > - gpaste > - polari > 6. Release team will need to force through the transition by ignoring the > "all task packages are installable" check on armel, because > task-gnome-desktop will now be uninstallable on armel
I believe we have finished steps 0, 1, and 3. Step 4 is mostly done: gdm3's removal is only requested not done yet. Can I proceed with uploading the new gjs to unstable to finish step 2? I also created https://salsa.debian.org/installer-team/tasksel/-/merge_requests/32 but maybe that's unnecessary since task-gnome-desktop is currently arch: all. Thank you, Jeremy Bícha
