On Fri, 04 Apr 2025 at 12:08:04 -0400, Jeremy Bícha wrote:
Then file removal requests for armel for cjs, cinnamon, and
cinnamon-desktop-environment.
This is time-sensitive, due to the freeze starting soon and the old
binaries blocking migration of cjs. As a result I opened
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102392,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102393 and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102394 to get this
started.
If cinnamon-desktop-environment needs a removal bug for armel too (I
hadn't realised that cinnamon-desktop-environment.deb is
architecture-specific), then it should go at the beginning of the chain
and block #1102392.
On https://salsa.debian.org/gnome-team/meta-gnome3/-/blob/debian/latest/debian/control?ref_type=heads
I saw these archs:
Architecture: amd64 arm64 armhf i386 mips64el ppc64el riscv64 s390x loong64
But seems that build correctly new cjs also on ppc64 and sparc64 (but
I never used these archs), I suppose I should add also them, is it
correct?
The GNOME team has limited resources and several reasons why packages
end up with architecture-specific limitations (mozjs, Rust, GTK, working
Mesa), so we chose to make our metapackages "opt in" instead of "opt
out", and limited them to release architectures, plus -ports
architectures where a porter has told us that GNOME genuinely does work
on their architecture.
If you would prefer Cinnamon to be "opt-out", and the only reason for
Cinnamon to be architecture-specific is cjs, then there is a trick that
you could use: if you add
Build-Depends-Arch: cjs (>= 128)
then that source package will refuse to build any architecture-specific
.deb on architectures where cjs is not available, without you needing to
hard-code a list of specific architectures. And then you can ask the ftp
team to remove the obsolete binary packages (if any) from armel, with a
bug similar to #1102392.
smcv
