Discussion:
Bug#1064810: transition: mpi-defaults
Add Reply
Alastair McKinstry
2024-02-26 06:50:01 UTC
Reply
Permalink
Package: release.debian.org
Severity: normal
User: ***@packages.debian.org
Usertags: transition
X-Debbugs-Cc: mpi-***@packages.debian.org, debian-***@lists.debian.org
Control: affects -1 + src:mpi-defaults

OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.

notes = "https://lists.debian.org/debian-release/2023/11/msg00379.html";

Ben file:

title = "mpi-defaults";
is_affected = .build-depends ~ /mpi-default-dev/;
is_good = .depends ~ /libmpich.*/;
is_bad = .depends ~ /libopenmpi.*/;
architectures = [ "armhf","armel","i386" ];
ignored = [ ];
Drew Parsons
2024-02-26 12:10:02 UTC
Reply
Permalink
Post by Alastair McKinstry
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:mpi-defaults
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
notes =
"https://lists.debian.org/debian-release/2023/11/msg00379.html";
Be mindful that Ubuntu is about to freeze for their noble LTS release.
We're (or I'm) still updating some Debian packages with the hope to get
the new versions (and new packages) into noble. Since it's an LTS
release, our packages will still be supporting their users in, say, 3 or
4 years time.

Would it be reasonable to pause the 32-bit mpich transition until after
they've frozen noble?
Or alternatively, can this mpich transition be completed in time to make
it into their freeze (only days left).

Drew
Alastair McKinstry
2024-02-26 12:30:01 UTC
Reply
Permalink
Post by Drew Parsons
Post by Alastair McKinstry
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:mpi-defaults
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
notes = "https://lists.debian.org/debian-release/2023/11/msg00379.html";
Be mindful that Ubuntu is about to freeze for their noble LTS release.
We're (or I'm) still updating some Debian packages with the hope to
get the new versions (and new packages) into noble. Since it's an LTS
release, our packages will still be supporting their users in, say, 3
or 4 years time.
Would it be reasonable to pause the 32-bit mpich transition until
after they've frozen noble?
Or alternatively, can this mpich transition be completed in time to
make it into their freeze (only days left).
Drew
Hi

I think we can get mpich 4.2.0 into noble. I've been doing a full
rebuild of mpich repds and mpich4.2 is not a transition (as feared);
I'll do an upload later today. This is independent of mpi-defaults.
I'm test-building mpich on armhf and hopefully will have a test
completed today/tomorrow.

Regards

Alastair


Alastair
--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
e: ***@debian.org, im: @alastair:mckinstry.ie
Sebastian Ramacher
2024-05-05 16:40:02 UTC
Reply
Permalink
Post by Alastair McKinstry
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
This transition is blocking many of the remaining packages rebuilt for
64-bit time_t.
The autopkgtest for slurm-wlm on i386 is blocking testing migration of
https://qa.debian.org/excuses.php?package=mpich
Testing migration of openmpi is likewise blocked by autopkgtest failures on
https://qa.debian.org/excuses.php?package=openmpi
I'm starting to think that it'd be better to drop support for 32bit
architectures from all these rdeps so they can just use openmpi everywhere
and not have i386 autopkgtest failures able to block testing migration.
openmpi should migrate with the next britney run.

After that we can look into starting the transition to change
mpi-defaults on 32 bit architctures. That is currently

https://release.debian.org/transitions/html/mpi-defaults.html

This will also require changes to hdf5. Have they been prepared
somewhere?

Cheers
--
Sebastian Ramacher
Alastair McKinstry
2024-05-06 06:00:02 UTC
Reply
Permalink
Post by Alastair McKinstry
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
This transition is blocking many of the remaining packages rebuilt for
64-bit time_t.
The autopkgtest for slurm-wlm on i386 is blocking testing migration of
 https://qa.debian.org/excuses.php?package=mpich
Testing migration of openmpi is likewise blocked by autopkgtest
 https://qa.debian.org/excuses.php?package=openmpi
I'm starting to think that it'd be better to drop support for 32bit
architectures from all these rdeps so they can just use openmpi
everywhere and not have i386 autopkgtest failures able to block
testing migration.
Should we advocate this to the maintainer of these packages or is
there something else we can do to improve this situation?
Dropping 32-bit support for so many packages is a bit more radical than
I had considered, but I'd go with it.

Regards

Alastair
Kind Regards,
Bas
--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
e: ***@debian.org, im: @alastair:mckinstry.ie
Sebastian Ramacher
2024-07-07 17:30:01 UTC
Reply
Permalink
Control: tags -1 confirmed
Post by Alastair McKinstry
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:mpi-defaults
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
Let's go ahead with this change. Please switch the 32 bit architectures
to mpich.

Cheers
Post by Alastair McKinstry
notes = "https://lists.debian.org/debian-release/2023/11/msg00379.html";
title = "mpi-defaults";
is_affected = .build-depends ~ /mpi-default-dev/;
is_good = .depends ~ /libmpich.*/;
is_bad = .depends ~ /libopenmpi.*/;
architectures = [ "armhf","armel","i386" ];
ignored = [ ];
--
Sebastian Ramacher
Sebastian Ramacher
2024-07-08 10:40:01 UTC
Reply
Permalink
Hi Alastair
Post by Sebastian Ramacher
Control: tags -1 confirmed
Post by Alastair McKinstry
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:mpi-defaults
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
Let's go ahead with this change. Please switch the 32 bit architectures
to mpich.
Thanks for the upload of mpi-defaults. A fix for #1028172 is needed
though to continue with this transition. I would appreciate if you could
take a look at that bug.

Cheers
--
Sebastian Ramacher
Alastair McKinstry
2024-07-08 11:00:01 UTC
Reply
Permalink
Post by Sebastian Ramacher
Hi Alastair
Post by Sebastian Ramacher
Control: tags -1 confirmed
Post by Alastair McKinstry
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:mpi-defaults
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
Let's go ahead with this change. Please switch the 32 bit architectures
to mpich.
Thanks for the upload of mpi-defaults. A fix for #1028172 is needed
though to continue with this transition. I would appreciate if you could
take a look at that bug.
Thanks for highlighting it. I'm preparing a fix now.
Sebastian Ramacher
2024-07-12 22:10:01 UTC
Reply
Permalink
Post by Alastair McKinstry
Post by Sebastian Ramacher
Hi Alastair
Post by Sebastian Ramacher
Control: tags -1 confirmed
Post by Alastair McKinstry
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:mpi-defaults
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
Let's go ahead with this change. Please switch the 32 bit architectures
to mpich.
Thanks for the upload of mpi-defaults. A fix for #1028172 is needed
though to continue with this transition. I would appreciate if you could
take a look at that bug.
Thanks for highlighting it. I'm preparing a fix now.
Most of the binNMUs are now scheduled. Not that
https://release.debian.org/transitions/html/mpi-defaults.html still
lists quite a lot of packages. Some FTBFS, but others also depend on
both mpi-defaults and openmpi and build with openmpi. I would appreciate
if you could take a look at those packages and file bugs where
appropriate.

Cheers
--
Sebastian Ramacher
Alastair McKinstry
2024-07-13 10:00:01 UTC
Reply
Permalink
Post by Sebastian Ramacher
Post by Alastair McKinstry
Post by Sebastian Ramacher
Hi Alastair
Post by Sebastian Ramacher
Control: tags -1 confirmed
Post by Alastair McKinstry
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:mpi-defaults
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
Let's go ahead with this change. Please switch the 32 bit architectures
to mpich.
Thanks for the upload of mpi-defaults. A fix for #1028172 is needed
though to continue with this transition. I would appreciate if you could
take a look at that bug.
Thanks for highlighting it. I'm preparing a fix now.
Most of the binNMUs are now scheduled. Not that
https://release.debian.org/transitions/html/mpi-defaults.html still
lists quite a lot of packages. Some FTBFS, but others also depend on
both mpi-defaults and openmpi and build with openmpi. I would appreciate
if you could take a look at those packages and file bugs where
appropriate.
Cheers
Will do.  Thanks

Alastair
Sebastian Ramacher
2024-08-15 09:50:01 UTC
Reply
Permalink
Post by Alastair McKinstry
Post by Sebastian Ramacher
Post by Alastair McKinstry
Post by Sebastian Ramacher
Hi Alastair
Post by Sebastian Ramacher
Control: tags -1 confirmed
Post by Alastair McKinstry
Package: release.debian.org
Severity: normal
Usertags: transition
Control: affects -1 + src:mpi-defaults
OpenMPI 5.0 drops 32-bit support, so we need to move those archs to MPICH.
Let's go ahead with this change. Please switch the 32 bit architectures
to mpich.
Thanks for the upload of mpi-defaults. A fix for #1028172 is needed
though to continue with this transition. I would appreciate if you could
take a look at that bug.
Thanks for highlighting it. I'm preparing a fix now.
Most of the binNMUs are now scheduled. Not that
https://release.debian.org/transitions/html/mpi-defaults.html still
lists quite a lot of packages. Some FTBFS, but others also depend on
both mpi-defaults and openmpi and build with openmpi. I would appreciate
if you could take a look at those packages and file bugs where
appropriate.
Cheers
Will do.  Thanks
Let's also start the openmpi 32 bit removal transition. The tracker is
https://release.debian.org/transitions/html/openmpi-rm32.html.

Same request as above: please check the packages that are marked as bad
on the tracker and file bugs to change to mpich or drop the 32 bit
binaries as appropriate.

Cheers
--
Sebastian Ramacher
Sebastian Ramacher
2024-10-15 19:40:02 UTC
Reply
Permalink
Post by Sebastian Ramacher
Let's also start the openmpi 32 bit removal transition. The tracker is
https://release.debian.org/transitions/html/openmpi-rm32.html.
Same request as above: please check the packages that are marked as bad
on the tracker and file bugs to change to mpich or drop the 32 bit
binaries as appropriate.
Cheers
Note that mpich got caught up in the gcc 14 transition and FTBFS (#1057292)
I'm working on this as I write, (there is a patch from Adrian Bunk that
fails to install for me, but I have it working now and am testing on amd64).
Thanks, this upload now made its way into testing.
Are there any news regarding the upload of openmpi removing 32 bit
support?
Cheers
I need to do more bug submissions on the transition but mpich is present,
and I can upload openmpi 5
(there is a bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078212
that I will close on uploading 5.0.5). I will do so when the Release Team
agrees.
ACK, from our side this is good to go.
Cheers
Ok this is uploaded and through britney, though I need to bring git up to
date on salsa.
I'll be submitting bugs on the remaining packages.
openmpi failed to build on Architecture: all. Could you please take a
look?

Cheers
--
Sebastian Ramacher
Loading...