openmpi-devel-default: The requested URL returned error: 403 Forbidden

[ryandesign (Ryan Carsten Schmidt)]

​https://build.macports.org/builders/jobs-mirror/builds/236277/steps/mirror/logs/stdio

--->  Fetching distfiles for openmpi-devel-default
--->  Attempting to fetch openmpi-v4.1.x-201905080241-5d4c9b4.tar.bz2 from https://distfiles.macports.org/openmpi-devel
--->  Attempting to fetch openmpi-v4.1.x-201905080241-5d4c9b4.tar.bz2 from https://www.open-mpi.org/nightly/v4.1.x
Error: Failed to mirror openmpi-devel-default: The requested URL returned error: 403 Forbidden

[jmroot (Joshua Root)]

Yeah, the distfile for all the openmpi-*-devel ports has been incorrect since [772b1936909dba5b0096c6862f189bcde67d4dab/macports-ports]. They need to be either updated to a snapshot that is actually newer than the non-devel version, or simply retired and marked as replaced by the corresponding non-devel subports.

[mascguy (Christopher Nielsen)]

Replying to jmroot:

Yeah, the distfile for all the openmpi-*-devel ports has been incorrect since [772b1936909dba5b0096c6862f189bcde67d4dab/macports-ports]. They need to be either updated to a snapshot that is actually newer than the non-devel version, or simply retired and marked as replaced by the corresponding non-devel subports.

I'll happily make either fix. In terms of usage, is there an easy way to see the usage stats across all of the *-devel subports? (Worst-case, I can visit the stats page for each, but I'm hoping there's a better way...)

[jmroot (Joshua Root)]

The web app doesn't have a way to query the stats for multiple ports at once AFAIK. I'm not sure "How many people are using openmpi-devel right now?" is the right question anyway. "How many people would use openmpi-devel if it was a current snapshot and not one from 2019?" is a more interesting question. Personally I would probably just retire them, since nobody has asked for them to be updated as far as I'm aware.

[mascguy (Christopher Nielsen)]

Replying to jmroot:

"How many people would use openmpi-devel if it was a current snapshot and not one from 2019?" is a more interesting question. Personally I would probably just retire them, since nobody has asked for them to be updated as far as I'm aware.

I'm fine with retiring them, as it would significantly reduce the number of subports.

Committers and maintainers, do you have any thoughts or objections, relative to removing the various openmpi-devel-* subports?

[mascguy (Christopher Nielsen)]

Slowly making progress on the changes to remove openmpi-devel-* subports. I'm being even more cautious than usual on this one though, given that it might require minor changes to the mpi-1.0 portgroup.

I'm not ready for any advice or feedback quite yet, as it'll be a good learning exercise to trace through the various logic and interactions. But just an FYI that it's being worked on.

Once I'm more confident in the changes, I'll solicit feedback from you folks. Stay tuned...

[mascguy (Christopher Nielsen)]

Josh, I'm guessing you can fix this in 5 minutes, so in the interest of getting this fixed ASAP... these are the changes I've made thus far. (Albeit without tracing through everything, so I'm not yet confident this is complete.)

But please let me know if I'm on the right track here:

​https://github.com/macports/macports-ports/compare/master...mascguy:mascguy-openmpi-remove-devel

[mascguy (Christopher Nielsen)]

PR created:

​https://github.com/macports/macports-ports/pull/9832

[Christopher Nielsen <mascguy@…>]

In b4794e01678e2f8d7215f23682ca01a8262cd82e/macports-ports (master):

openmpi: disable openmpi-devel-* subports

Fixes: #62068