Skip to content

Conversation

@hehe7318
Copy link
Contributor

Description of changes

  • Describe what you're changing and why you're doing these changes.

Tests

  • Describe the automated and/or manual tests executed to validate the patch.
  • Describe the added/modified tests.

References

  • Link to impacted open issues.
  • Link to related PRs in other packages (i.e. cookbook, node).
  • Link to documentation useful to understand the changes.

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@hehe7318 hehe7318 added the 3.x label Jan 27, 2026
@hehe7318 hehe7318 requested review from a team as code owners January 27, 2026 14:43
cp -v DISCLAIMER #{node['cluster']['license_dir']}/slurm/DISCLAIMER
cp -v LICENSE.OpenSSL #{node['cluster']['license_dir']}/slurm/LICENSE.OpenSSL
cp -v README.rst #{node['cluster']['license_dir']}/slurm/README.rst
cp -v README.md #{node['cluster']['license_dir']}/slurm/README.md
Copy link
Contributor

@gmarciani gmarciani Jan 27, 2026

Choose a reason for hiding this comment

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

The goal here is to include license related files. If the README does not contain any additional info about licensing, then we can remove it rather than fixing it.

What we can do is in this PR is fixing to immediately unblock.
The check with legals if we need to include the readme for whatever reason.

- PMIx: 5.0.6 -> 5.0.10
- libjwt: 1.18.4 -> 2.1.2 (AL2 remains at 1.17.0 due to OpenSSL constraints)
- Temporarily hardcode GitHub URLs for testing (revert after S3 upload)
- Update SHA256 checksums for new versions
Add --without-gnutls to configure to work around autoconf bug in
libjwt 2.1.2 where HAVE_GNUTLS conditional is not properly defined
when GnuTLS is not found. We only use OpenSSL for crypto operations.
libjwt 2.1.2 has a bug in configure.ac where AM_CONDITIONAL([HAVE_GNUTLS], ...)
is not called when with_gnutls=check (default) and GnuTLS is not installed,
causing 'conditional HAVE_GNUTLS was never defined' error.

Changes:
- Revert libjwt from 2.1.2 to 1.18.4
- Revert URL from GitHub to S3
- Remove --without-gnutls workaround from configure command
- AL2 remains at 1.17.0 due to OpenSSL constraints
- PMIx 5.0.10 upgrade unchanged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants