New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
p5-*: add p5.32, remove p5.26 subports #10821
Conversation
Notifying maintainers: |
The build failure on mythweb.28 is expected. Depends on non-default variants. At some point, I will go over the myth* ports and update to a supported perl version (or declare some of the ports obsolete) among other maintenance. |
add p5.32, remove p5.26 subport See: #10821
add p5.32, remove p5.26 subport See: #10821
Add p5.32, remove p5.26 branches See: #10821
@mojca what do you want to do with this PR? Fix the conflicts and merge, or...? It seems that leaving this open for too long isn't very helpful as it will inevitably result in merge conflicts as soon as one of the packages is updated. |
I plan to (fix and) merge this. The problem is that there are some open / pending issues with efficiency on the buildbot side, usually resulting in the buildbot stuck building these ports for up to one week (truth to be told I'm not following exactly). From what I remember merging this has always caused one issue or another. But if there's no activity towards optimisations foreseen in the near future, maybe I'll just merge ... |
A lot of the portfiles seem to have |
Arghhhhh. Thanks for pointing this out. I'm fixing it now. |
Thanks. Since the problem affected p5.32-module-build, a lot of p5.32 ports failed to build. We should force build all affected p5.32 ports on those builders that have already processed the initial commits from this PR (10.7, 10.8, 10.14, 10.15, 11 x86_64, 11 arm64). Ideally we should list the p5.32 subports and not the p5 main ports to avoid unnecessary extra processing by the buildbot. |
I started new forced builds on 10.7, 10.8 and 11 arm64. These are the ones that have completely finished building the ports from that commit. I'll wait for the other workers to finish the job and then extract the summary and reschedule just the failed subports for 5.32. I guess I should add subports for 5.34 as well and then we could try to migrate directly to 5.34. |
Description
This update sometimes causes various issues related to our CI, so we want to monitor our services once we push the merge button.
Type(s)
Tested on
/
Verification
Have you
port lint
?sudo port test
?sudo port -vst install
?