Thanks Dominique for writing CME and thanks Paul for the explanations, on my side I have added a --64 option to the `routine-update` script (from the same-named package) that adds a build-dependency on architecture-is-64-bits, and plan to do the same for little-endian architectures.
I wrote recently that I plan to restrict all the team-maintained r-cran-* packages to 64-bit, little-endian. I have delayed that because of worries of delaying migration of some packages with a mass upload, but... I would like to ask you "what about the architecture-independant packages"? They will be built on amd64 and be available for the excluded architectures. Is there a risk that a mixed dependency chain of architecture-specific and architecture-independant packages which are all already in Trixie but will disappear from some architectures in Sid will create a mess and therefore be not able to migrate? Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -