Hi, On Tue, 15 Sep 2020 12:32:34 +0200 "Aaron Zauner (azet)" <a...@azet.org> wrote: > If anyone wants to take over I'm more than fine with that. The amount of work > I have at the moment barely permits me from maintaining projects. It's most > sensible that someone actively using this project on Debian maintains it, as > is, I'm not using it much anymore and am not working in HPC at the moment. > The bug should definitely reported upstream. Upgrading the package should be > fairly simple though - the dependencies are already in place, as are simple > tests/git integration etc.: https://github.com/azet/lmod-deb
I had a look, and it seems to be an upstream "feature" that was introduced between lmod 6.2 and lmod 6.3. The root cause is that the configure script uses the build-time paths from lua, and then uses these paths at runtime. The upstream changelog for 6.3 states: > Lmod now uses the values of LUA_PATH and LUA_CPATH at configuration > time. This way Lmod is safe from user changes to these important Lua > values. The corresponding upstream change and discussion: https://github.com/TACC/Lmod/issues/112 This was already reported for ARM and closed: https://github.com/TACC/Lmod/issues/338 Overall, I think the simplest solution is to change the architecture to "any". Baptiste > > On 15.09.2020, at 09:33, Lucas Nussbaum <lu...@debian.org> wrote: > > > > retitle 951508 lmod: broken on all architectures except x86_64 (wrong > > search path) > > severity 951508 serious > > thanks > > > > Hi, > > > > We ran into the same bug on an arm64 system, so it looks like lmod is > > broken on all architectures except x86_64. I'm updating the bug title > > and the severity to reflect that. > > > > I'm attaching the diffoscope output that shows that the generated > > packages are indeed different on amd64 and arm64. > > > > A simple fix would be to turn this package into an Architecture:any > > package. But indeed, it should probably be reported (and fixed) upstream. > > > >> On 17/02/20 at 19:49 +0100, Aaron Zauner wrote: > >> Since I'm barely keeping this package updated I'd suggest that you use the > >> upstream Lmod project source with the dependencies that come with this > >> package, you'll get more bug fixes, Performance and features out of it in a > >> production environment. That's what we used to do on live HPC systems since > >> a lot of software needs to be built by hand outside of the distro packaging > >> anyway. > > > > Err, if this is the case, maybe you should mark this package as orphaned > > or RFA? I'm also Ccing people who uploaded NMUs for the package. Maybe > > someone is interested in taking over. > > > > Lucas > > <lmod-diffoscope.txt> -- Baptiste Jonglez Inria Grenoble - Rhône-Alpes <https://www.inria.fr/> R&D Engineer, Grid'5000 platform <https://www.grid5000.fr/> LIG lab <https://www.liglab.fr/>
signature.asc
Description: PGP signature
