Re: mips64el/mipsel and testing migration
On Sat, Feb 04, 2023 at 09:59:23AM -0500, Roberto C. Sánchez wrote:
>...
> If that is the case, then I am puzzled how intelrdfpmath would have
> migrated to testing without being able to build on mips64el/mipsel
intelrdfpmath having never been built on mips* is not an RC bug or
testing migration blocker for intelrdfpmath since there are no old
binaries of intelrdfpmath in unstable.[1]
> and
> it makes me think that I might need to be concerned that libmongocrypt
> might not migrate in time.
libmongocrypt is currently in testing, so the 12th is not a hard
deadline here.
> If that is not the case, and the excuses are spurious because the lack
> of availability on mips64el/mipsel won't prevent testing migration, that
> would be good to know as well.
>...
libmongocrypt does have old binaries on mips* in unstable,
which blocks testing migration of libmongocrypt.
There are 3 options for handling this:
1. Is there a way to build libmongocrypt without intelrdfpmath?
2. Fixing intelrdfpmath on mips*
3. "reportbug ftp.debian.org" could be used to request removal of the
old mipsel/mips64el binaries of libmongocrypt, but that requires first
making the build dependency in mongo-c-driver exclude architectures
where libmongocrypt is no longer available.
If !pkg.mongo-c-driver.no-libmongocrypt is still a usable configuration,
then [!mipsel !mips64el] could be used there.
I will look whether 2. is feasible. intelrdfpmath does build on not
explicitely supported architectures like s390x, and MIPS might be a
victim of explicit support code that is now half-broken.
> Regards,
>
> -Roberto
cu
Adrian
[1] https://release.debian.org/testing/rc_policy.txt
Packages must autobuild without failure on all architectures on
which they are supported. Packages must be supported on as many
architectures as is reasonably possible. Packages are assumed to
be supported on all architectures for which they have previously
built successfully. Prior builds for unsupported architectures
must be removed from the archive (contact -release or ftpmaster
if this is the case).
Reply to: