Skip to content
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

Merged
merged 14 commits into from
Oct 27, 2024
Merged

Glibc 2.34 from alma 9 #80

merged 14 commits into from
Oct 27, 2024

Conversation

h-vetinari
Copy link
Member

@h-vetinari h-vetinari commented Oct 22, 2024

Builds on #79 and predecessors, so review those first.

@conda-forge-admin
Copy link
Contributor

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 (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • License exception is not an SPDX exception.

Documentation on acceptable licenses can be found here.

@h-vetinari
Copy link
Member Author

h-vetinari commented Oct 22, 2024

This is the output of the update.py,

(builder) E:\conda-forge\linux-sysroot-feedstock\recipe>python update.py
WARNING:root:Could not download rpm for glibc-headers from https://repo.almalinux.org/vault/9.3/AppStream/aarch64/os/Packages/glibc-headers-2.34-83.el9_3.12.aarch64.rpm!
WARNING:root:Could not download rpm for glibc-headers from https://repo.almalinux.org/vault/9.3/AppStream/ppc64le/os/Packages/glibc-headers-2.34-83.el9_3.12.ppc64le.rpm!

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 glibc-headers seem to be missing completely for 9.3 on aarch/ppc, and this also matches the info on pkgs.org. No idea why that's the case. Interestingly it's fine for s390x.

Edit: opened a thread on the alma discourse
Edit2: it's intentional

@h-vetinari h-vetinari marked this pull request as ready for review October 23, 2024 23:24
Copy link
Member

@beckermr beckermr left a 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?

@h-vetinari
Copy link
Member Author

h-vetinari commented Oct 23, 2024

Did you move the current main to an alma8 branch?

It'll be easy to create a new v2.28 branch off the current commit on main (4bead36), irrespective of whether that's before/after merging this. I can do it if you'd like, but Isuru doesn't like non-maintainers doing branch ops, so I'm holding off.

@beckermr
Copy link
Member

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.

Copy link
Member

@beckermr beckermr left a 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.

Copy link
Member

@beckermr beckermr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Copy link
Member

@isuruf isuruf left a 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

@h-vetinari
Copy link
Member Author

What happened to libnss_nis.so?

See the commit message for 6d8749d. I couldn't find anything related to that anymore (see also here).

Also I see aarch64-conda-linux-gnu/sysroot/usr/lib64/libnss_hesiod.so is a symlink with no target

Looks like we need nss_hesiod instead...

@h-vetinari
Copy link
Member Author

h-vetinari commented Oct 24, 2024

Hm, nevermind, it was already there before my last commit, but it points to the wrong place:

?rwxrwxrwx 0/0          0 2024-10-24 22:09:17 aarch64-conda-linux-gnu/sysroot/usr/lib64/libnss_compat.so -> ../../lib64/libnss_compat.so.2 
?rwxrwxrwx 0/0          0 2024-10-24 22:09:17 aarch64-conda-linux-gnu/sysroot/usr/lib64/libnss_db.so -> ../../lib64/libnss_db.so.2 
?rwxrwxrwx 0/0          0 2024-10-24 22:09:17 aarch64-conda-linux-gnu/sysroot/usr/lib64/libnss_hesiod.so -> ../../lib64/libnss_hesiod.so.2 

Edit: this comment was wrong; the libnss_hesiod.so symlink was there, but libnss_hesiod.so.2 only gets installed from nss_hesiod.rpm.

@h-vetinari
Copy link
Member Author

OK, the "symlink with no target" warnings are all gone now. While I don't know what determines the separation between lib64 and usr/lib64, libnss_hesiod.so is now next to the other nss libraries:

                                              [...]
?rwxrwxr-x 0/0     904648 2024-10-24 22:45:50 x86_64-conda-linux-gnu/sysroot/lib64/libm.so.6 
?rwxrwxr-x 0/0     176840 2024-10-24 22:45:50 x86_64-conda-linux-gnu/sysroot/lib64/libmvec.so.1 
?rwxrwxr-x 0/0      45552 2024-10-24 22:45:50 x86_64-conda-linux-gnu/sysroot/lib64/libnss_compat.so.2 
?rwxrwxr-x 0/0      40872 2024-10-24 22:45:51 x86_64-conda-linux-gnu/sysroot/lib64/libnss_db.so.2 
?rwxrwxr-x 0/0      15344 2024-10-24 22:45:50 x86_64-conda-linux-gnu/sysroot/lib64/libnss_dns.so.2 
?rwxrwxr-x 0/0      15336 2024-10-24 22:45:50 x86_64-conda-linux-gnu/sysroot/lib64/libnss_files.so.2 
?rwxrwxr-x 0/0      28448 2024-10-24 22:45:51 x86_64-conda-linux-gnu/sysroot/lib64/libnss_hesiod.so.2 
?rwxrwxr-x 0/0      15480 2024-10-24 22:45:50 x86_64-conda-linux-gnu/sysroot/lib64/libpthread.so.0
                                              [...]

@h-vetinari h-vetinari requested a review from isuruf October 24, 2024 22:58
@isuruf
Copy link
Member

isuruf commented Oct 25, 2024

Shall we remove nss components from 2.28 and 2.34 both and deal with it when there's a use-case?

@beckermr
Copy link
Member

That seems fine. I don't even know why we had them in the first place. Is there someone to ask about that?

@beckermr
Copy link
Member

It appears from #32 that some of the nss stuff was added due to a bug in building the ROS distro packages from work by @wolfv. Maybe he recalls what happened there?

This reverts commit d9650a7, reversing
changes made to e13f355.
@conda-forge-admin
Copy link
Contributor

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 (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

  • license_file entry is missing, but is required.

For recipe/meta.yaml:

  • License exception is not an SPDX exception.

Documentation on acceptable licenses can be found here.

@conda-forge-admin
Copy link
Contributor

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 (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • License exception is not an SPDX exception.

Documentation on acceptable licenses can be found here.

@h-vetinari
Copy link
Member Author

Shall we remove nss components from 2.28 and 2.34 both and deal with it when there's a use-case?

Fixed in this PR; opened #83 that backports relevant commits to v2.28

@isuruf isuruf merged commit 2ebae6a into conda-forge:main Oct 27, 2024
7 checks passed
@isuruf
Copy link
Member

isuruf commented Oct 27, 2024

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants