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.
Step to reproduce:
Build
Java-11.ebusing EasyBuild 4.6.2 with the--package optionon a RHEL based system (e.g. CentOS 7) with Lmod 8.7.7 installedExpected 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.luainmodules/all/Java/. Informational message from the build logsFound Lmod v8.7.7 >= v7.7.38, so will generate .modulerc.lua in Lua syntax. 2) Packaging step fails withwhich is correct -
11.luadoes not exist while.modulerc.luadoes.Additional details
We probably could patch EasyBuild to package the
.modulerc.luainstead of the11.luawhen a recentLmodis detected, but then we will not cover a case whereJava/11.0.16can be reached by two aliases,Java/11ANDJava/11.0, respectively. Implementing a custom post install and remove script however also could be a bit too extreme for this purpose either.