-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Glibc 2.34 from alma 9 #80
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 ( For recipe/meta.yaml:
Documentation on acceptable licenses can be found here. |
This is the output of the
i.e. exactly two packages aren't available in the expected location w.r.t. x86_64. I've checked the other subfolders on the vault, and indeed the Edit: opened a thread on the alma discourse |
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.
Did you move the current main to an alma8 branch?
It'll be easy to create a new |
doesn't exist anymore, see https://git.almalinux.org/rpms/nss_nis/commit/d654f8c5a2a721ea5d38c26b1d12d71eda3bcfbb (there's also no c9s branch)
I went ahead and made a v2.28 branch. I will sync it with main if any other PRs get made there before this is merged. |
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.
We need to add one extra feature to the build to weigh it down relative to v2.28.
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.
LGTM!
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.
What happened to libnss_nis.so
?
Also I see aarch64-conda-linux-gnu/sysroot/usr/lib64/libnss_hesiod.so is a symlink with no target
See the commit message for 6d8749d. I couldn't find anything related to that anymore (see also here).
Looks like we need |
Edit: this comment was wrong; the |
OK, the "symlink with no target" warnings are all gone now. While I don't know what determines the separation between
|
Shall we remove |
That seems fine. I don't even know why we had them in the first place. Is there someone to ask about that? |
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/meta.yaml:
For recipe/meta.yaml:
Documentation on acceptable licenses can be found here. |
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 ( For recipe/meta.yaml:
Documentation on acceptable licenses can be found here. |
Fixed in this PR; opened #83 that backports relevant commits to v2.28 |
Thanks |
Builds on #79 and predecessors, so review those first.