Your message dated Mon, 26 Oct 2020 12:50:10 +0000
with message-id <e1kx1ww-0005cu...@fasolo.debian.org>
and subject line Bug#951508: fixed in lmod 6.6-0.4
has caused the Debian Bug report #951508,
regarding lmod: broken on all architectures except x86_64 (wrong search path)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
951508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lmod
Version: 6.6-0.3
Severity: important
Description:
Whe using lmod on powerpc system, it show the below errors:
/usr/bin/lua: /usr/share/lua/5.2/posix/init.lua:29: module 'posix.ctype' not
found:
no field package.preload['posix.ctype']
no file '/usr/local/share/lua/5.2/posix/ctype.lua'
no file '/usr/local/share/lua/5.2/posix/ctype/init.lua'
no file '/usr/local/lib/lua/5.2/posix/ctype.lua'
no file '/usr/local/lib/lua/5.2/posix/ctype/init.lua'
no file '/usr/share/lua/5.2/posix/ctype.lua'
no file '/usr/share/lua/5.2/posix/ctype/init.lua'
no file './posix/ctype.lua'
no file '/usr/local/lib/lua/5.2/posix/ctype.so'
no file '/usr/lib/x86_64-linux-gnu/lua/5.2/posix/ctype.so'
no file '/usr/lib/lua/5.2/posix/ctype.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './posix/ctype.so'
no file '/usr/local/lib/lua/5.2/posix.so'
no file '/usr/lib/x86_64-linux-gnu/lua/5.2/posix.so'
no file '/usr/lib/lua/5.2/posix.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './posix.so'
One of the search path is /usr/lib/x86_64-linux-gnu/lua/5.2/ instead of
/usr/lib/powerpc64le-linux-gnu/lua/5.2/, where the file can be found
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: ppc64el (ppc64le)
Kernel: Linux 4.14.158-power8-aufs-1 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en_GB:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lmod depends on:
ii lua-filesystem 1.6.3-1
ii lua-json 1.3.3-2
ii lua-posix 33.4.0-3
ii lua-term 0.07-0.1
ii lua5.2 5.2.4-1.1+b3
ii tcl 8.6.0+9
lmod recommends no packages.
lmod suggests no packages.
-- Configuration Files:
/etc/lmod/modulespath [Errno 116] Stale file handle: '/etc/lmod/modulespath'
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lmod
Source-Version: 6.6-0.4
Done: Lucas Nussbaum <lu...@debian.org>
We believe that the bug you reported is fixed in the latest version of
lmod, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lucas Nussbaum <lu...@debian.org> (supplier of updated lmod package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 26 Oct 2020 13:24:01 +0100
Source: lmod
Architecture: source
Version: 6.6-0.4
Distribution: unstable
Urgency: medium
Maintainer: Aaron Zauner <a...@azet.org>
Changed-By: Lucas Nussbaum <lu...@debian.org>
Closes: 951508
Changes:
lmod (6.6-0.4) unstable; urgency=medium
.
* Non-maintainer upload.
* Change Architecture: to any. Closes: #951508
This is required because lmod now gets LUA_PATH and LUA_CPATH at
compile time (to deal with users overriding those variables).
See https://github.com/TACC/Lmod/issues/112
There was an upstream report that this breaks Raspian, which was rejected,
so it is unlikely that upstream will return to the current behaviour.
See https://github.com/TACC/Lmod/issues/338
Thanks to Baptiste Jonglez for finding the relevant upstream bug reports.
Checksums-Sha1:
34ab743a691c1b1858fbd501c7e3d62adae3ac3c 1874 lmod_6.6-0.4.dsc
96924813708ca85eec0df65a8aea1d0c51bbad45 4892 lmod_6.6-0.4.debian.tar.xz
b7b73a5849ce49bb45690fc0d458f5aebaaf192e 5918 lmod_6.6-0.4_source.buildinfo
Checksums-Sha256:
99cc83812298af7abe76d1ee132341c11afb8e1f8643fe8f2f49e6d9a496566c 1874
lmod_6.6-0.4.dsc
9a5c450f26a5c16f0777b6d0a31f2013cc51d1d399e0579fbb71130aadd3cc1a 4892
lmod_6.6-0.4.debian.tar.xz
b5b035399cc7aba55085ab1bea1bb255c2908c171a5833062b685a073b30af25 5918
lmod_6.6-0.4_source.buildinfo
Files:
25a83a2b4f4e91e0950f276cb427ab54 1874 devel optional lmod_6.6-0.4.dsc
631ccfc49cd05157a2704b1ad045abb1 4892 devel optional lmod_6.6-0.4.debian.tar.xz
f08b46c02935c30564f804e2255bdb59 5918 devel optional
lmod_6.6-0.4_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE/t7ByzN7z1CfQ8IkORS1MvTfvpkFAl+WwdoACgkQORS1MvTf
vpntWg//Qr6INM/Kr2fe5wixeHHXCz1VL0RrVG32Vn4qwgOElvmXL7U1RBjXJVNP
Z776UYNMkolJh6gv9Ed9Q3tnfqw7wBM+eg7J/EigR9X25p88Bb5D23bkKeDrsENv
LMSJZP3ZEaMWEFrFNByxmRgO2FpbJ3v8CpDzUX8VFruJv3qi7L0eRPphhL2+vOdB
zfzr+r5c2Rh7QbzTRfuYs29Iqna+KSgv7K6GTAJ5EOsLC+HrAp3X09syXNEfeij4
G7rCIi4ZvPGvhQqxfkESHToKW5BMU+9BGHTAgsJeJeyOJgaLJkEYnWSEr7j9vydm
j2aMgKEm1pAe8Ut53V91z6qs6lRw2DDUSAqiFinIMtbuUyPRLKLMq5ai12CF0GgB
l5JlYyybYRgGIqmOEv9L2pn5EViM1XngcD31UmQyA9Hq20pcSzUnQq0Fw9J6DGiI
i9gIT4ysEaDzOSdG3KfeE05WIHTaIHIkmEdMkmJP7GTrqcJgEjaHZfzFSUwJnheQ
fILAKlGbP2cCg3nOS4/aVoyx5mbFoP6RMXRZaRZanPOokyT2a9tLu1QCAP5BLwfc
wNJgCXRtGk0rspJpasWQ7IbpWJBbki2yJZ558gnBCqLwJKdjRh8gmp2USBIY94Ha
emMZP5j6iL1tTcOPzwlVtpqgif+qwhWdbfDwXmbEXbYCItxQgt8=
=V9Qi
-----END PGP SIGNATURE-----
--- End Message ---
