Bug#951508: A patch file

2020-09-15 Thread Aaron Zauner (azet)
Hi, 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

Bug#951508: A patch file

2020-09-15 Thread Lucas Nussbaum
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

Bug#951508: A patch file

2020-02-17 Thread Aaron Zauner
Thanks for the information, interesting. These paths are auto generated during setup and installation as far as i know, so either we're breaking something in the build process within the package or as you point out it's an issue with the package building system. I'll look into it once i have a bit

Bug#951508: A patch file

2020-02-17 Thread Tamar Klein
I did try with "apt source lmod" on the same system, in order to check you suggestion. So yes, it is the same version as debian's package, we're currently using the packages from: http://snapshot.debian.org/archive/debian/20200217T030244Z/ (We started upgrading the system this morning, so the dat

Bug#951508: A patch file

2020-02-17 Thread Aaron Zauner
It might be related to the version. Keep in mind that the version packaged for Debian is quite old. Did you try with the same version? On Mon 17. Feb 2020 at 19:39, Tamar Klein wrote: > Hi > > Thanks for your suggestion. > > When downloading the source package and building it locally, the paths

Bug#951508: A patch file

2020-02-17 Thread Tamar Klein
Hi Thanks for your suggestion. When downloading the source package and building it locally, the paths seems to be correct. So I guess that the problem is either debian packagers used the same version for powerpc and x86 or was doing cross-site compilation without passing the correct parameters. I

Bug#951508: A patch file

2020-02-17 Thread Aaron Zauner
Hi Tamar This is something you need to bring up with the upstream maintainer of lmod. Replacing hard coded paths for one architecture with another will just break it for most users except for you. I suggest opening a GitHub PR with reference to this Debian bug report and an explanation what doesn

Bug#951508: A patch file

2020-02-17 Thread Tamar Klein
attached the patch file diff -aur /usr/share/lmod/6.6/libexec/addto ./libexec/addto --- /usr/share/lmod/6.6/libexec/addto 2018-12-02 19:06:51.0 +0200 +++ ./libexec/addto 2020-02-17 17:59:06.628796908 +0200 @@ -52,7 +52,7 @@ sys_lua_path = package.path end -local sys_lua_cpath = "/usr