Package: environment-modules
Version: 4.1.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm completely locked out of my modules.

   * What led up to the situation?
   Upgrade from 3.2.10-10 (probably) to 4.1.0-1 when pulling in buster.
   However, I don't think it is upgrade-dependent.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   I tried to list my modules with "module avail"

   * What was the outcome of this action?
   No output at all. No module is found.

   * What outcome did you expect instead?
   A list of at least the default modules provided by the package

I tried to track the bug. The script /usr/lib/modulecmd.tcl is setting 
MODULESHOME to /usr and tries to read /usr/init/.modulespath and 
usr/init/modulerc in several places. However, these files are installed 
to /usr/share/modules/init.

Checking the upstream-repository, it seems that PREFIX somehow does not
match the installation directory.

Thanks and best regards,
emanuel



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'stable'), (500, 
'oldstable'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages environment-modules depends on:
ii  debhelper  11.1.3
ii  libc6      2.26-4
ii  libtcl8.6  8.6.8+dfsg-2
ii  tcl        8.6.0+9
ii  tcl8.6     8.6.8+dfsg-2

environment-modules recommends no packages.

environment-modules suggests no packages.

-- no debconf information

Reply via email to