Code indexing in gitaly is broken and leads to code not being visible to the user. We work on the issue with highest priority.

Skip to content

Dependency conflicts are not transitive

In order to specify module conflicts it's currently necessary to add the 'conflict' clause to the modulefiles of both packages. This can lead to bugs: today I noticed that anaconda is marked as conflicting with psi-python*, but not vice versa. This means that if anaconda is loaded before psi-python27 then no error is reported.

Is this something that pmodules should handle (by checking conflict lines of currently loaded packages during load operations), or is it just something to be aware of when writing module files?