Hi Ken et al, On 07 Jan, 2013, at 10:57, Kenneth Hoste wrote: > Just a heads up: just before the end of the year, environment modules v3.2.10 > was released, see below.
Indeed and it is a bit inconvenient we now have to wait for the different OS distros to pass the new version downstream. Do you know what are the reasonable expected timelines for different distros? (eg. RHEL) (yeah, we can always repackage it ourselves etc... btw. a hint: openbuildservice) > This version fixes an annoying bug that caused modulecmd to segfault > sometimes, especially when big changes in the environment are involved. I am well aware that it is not necessary to advertise easybuild to this mailing-list but, thanks to easybuild we were confident enough that the problem was not in the modulefiles but rather in the modules/TCL implementation. In fact this is not the last bug around: * We have spotted the "module unload" operation to be occasionally unreliable and failing to clean the environment as it should. For the same reason, "module purge" does not inspire too much trust either. I suggest when we try to reproduce module-related bugs, to always start with a new shell (eg. "bash" after login) and do the clean-up by exiting that. > So, upgrading to this version is highly recommended. Is there a chance to ride on easybuild's TCL to provide another version of modules or such? How are you guys managing this on your end? cheers, Fotis
