You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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.
The text was updated successfully, but these errors were encountered:
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 installedExpected Result:
Build succeeds and RPM is successfully created
Actual Result:
module_version("Java/11.0.16", "11")
added to.modulerc.lua
inmodules/all/Java/
. Informational message from the build logsFound Lmod v8.7.7 >= v7.7.38, so will generate .modulerc.lua in Lua syntax
.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 the11.lua
when a recentLmod
is detected, but then we will not cover a case whereJava/11.0.16
can be reached by two aliases,Java/11
ANDJava/11.0
, respectively. Implementing a custom post install and remove script however also could be a bit too extreme for this purpose either.The text was updated successfully, but these errors were encountered: