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

Issue with FPM packaging, Lmod and the ModuleRC easyblock #836

Open
michaelmayer2 opened this issue Nov 1, 2022 · 0 comments
Open

Issue with FPM packaging, Lmod and the ModuleRC easyblock #836

michaelmayer2 opened this issue Nov 1, 2022 · 0 comments

Comments

@michaelmayer2
Copy link

Step to reproduce:

Build Java-11.eb using EasyBuild 4.6.2 with the --package option on a RHEL based system (e.g. CentOS 7) with Lmod 8.7.7 installed

Expected Result:

Build succeeds and RPM is successfully created

Actual Result:

  1. The software is correctly deployed and module_version("Java/11.0.16", "11") added to .modulerc.lua in modules/all/Java/. Informational message from the build logs Found Lmod v8.7.7 >= v7.7.38, so will generate .modulerc.lua in Lua syntax.
  2. Packaging step fails with
"Invalid package configuration: Cannot package the path './opt/apps/easybuild/modules/all/Java/11.lua', does it exist?"

which is correct - 11.lua does not exist while .modulerc.lua does.

Additional details

We probably could patch EasyBuild to package the .modulerc.lua instead of the 11.lua when a recent Lmod is detected, but then we will not cover a case where Java/11.0.16 can be reached by two aliases, Java/11 AND Java/11.0, respectively. Implementing a custom post install and remove script however also could be a bit too extreme for this purpose either.

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

No branches or pull requests

1 participant