Bug#1064810: transition: mpi-defaults
On 15/08/2024 11:42, Sebastian Ramacher wrote: On 2024-07-13 10:54:19 +0100, Alastair McKinstry wrote: On 12/07/2024 22:56, Sebastian Ramacher wrote: On 2024-07-08 11:40:37 +0100, Alastair McKinstry wrote: On 08/07/2024 11:34, Sebastian Ramacher wrote: Hi Alastair On 2024-07-07 19:20:01 +0200, Sebastian Ramacher wrote: Control: tags -1 confirmed On 2024-02-26 06:40:41 +, Alastair McKinstry wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: mpi-defau...@packages.debian.org, debian-scie...@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. 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. I still see lots of packages in that tracker without a bug report. Some of those need bugs because they build-dep on openmpi-dev directly (instead of mpi-default-dev), and so they either need to switch to mpi-default-dev, or they need to be removed from 32-bit arches. I have filed the missing bugs for examl ffindex murasaki phyml tree-puzzle sopt relion mfem. This transition has been dragging for too long. Let's try to close it up. Cheers, Emilio
Bug#1064810: transition: mpi-defaults
I'm copying the following email to the bug. On Fri, 18 Oct 2024 at 21:09, Adrian Bunk wrote: > > On Mon, Oct 14, 2024 at 02:25:40PM +0100, Alastair McKinstry wrote: > >... > > Ok this is uploaded and through britney, though I need to bring git up to > > date on salsa. > >... > > Various packages (e.g. combblas, superlu-dist, trilinos) are linked with > the libmpi_cxx that was removed in openmpi 5. > > A rebuild seems to fix it. > > The clean solution would be renaming the library package > (e.g. libopenmpi40), and then a transition to rebuild all > reverse dependencies. > > > Thanks > > > > Alastair > > cu > Adrian >
Bug#1064810: transition: mpi-defaults
The upload of openmpi 5 removed libmpi_cxx.so. So all packages linked against libmpi_cxx.so need to be rebuilt.
Bug#1064810: transition: mpi-defaults
On 2024-10-14 14:25:40 +0100, Alastair McKinstry wrote: > > On 2024-10-07 10:44:52 +0100, Alastair McKinstry wrote: > > > > > > > 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
Bug#1064810: transition: mpi-defaults
On 2024-07-13 10:54:19 +0100, Alastair McKinstry wrote: > > On 12/07/2024 22:56, Sebastian Ramacher wrote: > > On 2024-07-08 11:40:37 +0100, Alastair McKinstry wrote: > > > On 08/07/2024 11:34, Sebastian Ramacher wrote: > > > > Hi Alastair > > > > > > > > On 2024-07-07 19:20:01 +0200, Sebastian Ramacher wrote: > > > > > Control: tags -1 confirmed > > > > > > > > > > On 2024-02-26 06:40:41 +, Alastair McKinstry wrote: > > > > > > Package: release.debian.org > > > > > > Severity: normal > > > > > > User: release.debian@packages.debian.org > > > > > > Usertags: transition > > > > > > X-Debbugs-Cc: mpi-defau...@packages.debian.org, > > > > > > debian-scie...@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. > > > > > 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
Bug#1064810: transition: mpi-defaults
On 12/07/2024 22:56, Sebastian Ramacher wrote: On 2024-07-08 11:40:37 +0100, Alastair McKinstry wrote: On 08/07/2024 11:34, Sebastian Ramacher wrote: Hi Alastair On 2024-07-07 19:20:01 +0200, Sebastian Ramacher wrote: Control: tags -1 confirmed On 2024-02-26 06:40:41 +, Alastair McKinstry wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: mpi-defau...@packages.debian.org, debian-scie...@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. 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
Bug#1064810: transition: mpi-defaults
On 2024-07-08 11:40:37 +0100, Alastair McKinstry wrote: > > On 08/07/2024 11:34, Sebastian Ramacher wrote: > > Hi Alastair > > > > On 2024-07-07 19:20:01 +0200, Sebastian Ramacher wrote: > > > Control: tags -1 confirmed > > > > > > On 2024-02-26 06:40:41 +, Alastair McKinstry wrote: > > > > Package: release.debian.org > > > > Severity: normal > > > > User: release.debian@packages.debian.org > > > > Usertags: transition > > > > X-Debbugs-Cc: mpi-defau...@packages.debian.org, > > > > debian-scie...@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. > > > 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
Bug#1064810: transition: mpi-defaults
On 08/07/2024 11:34, Sebastian Ramacher wrote: Hi Alastair On 2024-07-07 19:20:01 +0200, Sebastian Ramacher wrote: Control: tags -1 confirmed On 2024-02-26 06:40:41 +, Alastair McKinstry wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: mpi-defau...@packages.debian.org, debian-scie...@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. 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.
Bug#1064810: transition: mpi-defaults
Hi Alastair On 2024-07-07 19:20:01 +0200, Sebastian Ramacher wrote: > Control: tags -1 confirmed > > On 2024-02-26 06:40:41 +, Alastair McKinstry wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > X-Debbugs-Cc: mpi-defau...@packages.debian.org, > > debian-scie...@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. > > 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
Bug#1064810: transition: mpi-defaults
Control: tags -1 confirmed On 2024-02-26 06:40:41 +, Alastair McKinstry wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: mpi-defau...@packages.debian.org, > debian-scie...@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. Let's go ahead with this change. Please switch the 32 bit architectures to mpich. Cheers > 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 = [ ]; > -- Sebastian Ramacher
Bug#1064810: transition: mpi-defaults
On 05/05/2024 16:59, Sebastiaan Couwenberg wrote: On 2/26/24 7:40 AM, Alastair McKinstry wrote: 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 mpich: https://qa.debian.org/excuses.php?package=mpich Testing migration of openmpi is likewise blocked by autopkgtest failures on i386 of several rdeps: 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: mckins...@debian.org, im: @alastair:mckinstry.ie
Bug#1064810: transition: mpi-defaults
On 2024-05-05 17:59:40 +0200, Sebastiaan Couwenberg wrote: > On 2/26/24 7:40 AM, Alastair McKinstry wrote: > > 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 > mpich: > > https://qa.debian.org/excuses.php?package=mpich > > Testing migration of openmpi is likewise blocked by autopkgtest failures on > i386 of several rdeps: > > 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
Bug#1064810: transition: mpi-defaults
On 2/26/24 7:40 AM, Alastair McKinstry wrote: 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 mpich: https://qa.debian.org/excuses.php?package=mpich Testing migration of openmpi is likewise blocked by autopkgtest failures on i386 of several rdeps: 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? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1064810: transition: mpi-defaults
On 26/02/2024 12:03, Drew Parsons wrote: On 2024-02-26 07:40, Alastair McKinstry wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: mpi-defau...@packages.debian.org, debian-scie...@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";; 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: mckins...@debian.org, im: @alastair:mckinstry.ie
Bug#1064810: transition: mpi-defaults
On 2024-02-26 07:40, Alastair McKinstry wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: mpi-defau...@packages.debian.org, debian-scie...@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";; 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
Bug#1064810: transition: mpi-defaults
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: mpi-defau...@packages.debian.org, debian-scie...@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 = [ ];
