-
-
Notifications
You must be signed in to change notification settings - Fork 27
6.34.06 (for non- osx-x86_64 archs) #298
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
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
Hi! This is the friendly automated conda-forge-linting service. I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict. Please ping the 'conda-forge/core' team (using the |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
@conda-forge-admin, please rerender |
1 similar comment
|
@conda-forge-admin, please rerender |
|
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping The following suggestions might help debug any issues:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16433442552. Examine the logs at this URL for more detail. |
|
@conda-forge-admin, please rerender |
|
Build failures are on which looks suspiciously the same as seen in Homebrew/homebrew-core#217574 and root-project/root#18429 . This looks like a nightmare admittedly. Wonder if it makes sense to skip straight to 6.34.08 / 12 -- if we can't get 06 built for everything. |
|
@vepadulano -- I have more progress here. osx arm builds, and most of the linux builds should succeed. |
|
@conda-forge-admin, please rerender |
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16477268108. Examine the logs at this URL for more detail. |
|
@conda-forge-admin, please rerender |
|
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16477928123. Examine the logs at this URL for more detail. |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
@conda-forge-admin, please rerender |
|
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipe/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16485459210. Examine the logs at this URL for more detail. |
|
@conda-forge-admin, please rerender |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16485730579. Examine the logs at this URL for more detail. |
matthewfeickert
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heck yeah! 🚀 Great to see things passing @kratsg. As this is also bumping to a new ROOT version, can you update the PR title and body to summarize the great work here?
|
Hi @kratsg , Let me express my gratitude for this PR and for all the work connected to it 🚀! I am digesting all the changes, I have to admit that I couldn't have imagined the core of the problem was with connected to something happening at a global level across all conda-forge. |
No problem! I had to skip osx-64 for now, but I'm hoping that's caught in the fix of 6-34-08 which needs to come next (osx-arm64 works fine however...). It would be great to at least have this in and then fix with a new build number after (or go straight to 6-34-08). |
|
for @h-vetinari's benefit, I was asked by @vepadulano offline to rebase this into two separate commits (one for actual changes, one for render). |
|
Was removed by conda-forge#298 and then it was not reverted when moving to a more recent 6.34 patch release.
Was removed by conda-forge#298 and then it was not reverted when moving to a more recent 6.34 patch release.

Checklist
0(if the version changed)conda-smithy(Use the phrase@conda-forge-admin, please rerenderin a comment in this PR for automated rerendering)This builds off of #288 by @vepadulano . Honestly ended up coming down to just having the re-renders of various dependent libs to make this all work. Particularly, both
llvmdevandclangdevgot a bit unlucky in release theroot_63406variant withlibxml==2.14before conda-forge globally bumped that back down to 2.13. A bit of a nasty race condition that ended up delaying getting this working.For this to work, we need to re-render dependencies using
libxml < 2.14rather than the original pin (for some reason not getting picked up automatically?):