Description of problem: With mpich2 package installed when one will try $ man man a response is 'No manual entry for man'. Eh? The same with any other manual page with a sole exception of a few located in /usr/share/man/mpich2/man1/. Closer check reveals that we have now in an environment MANPATH=/usr/share/man/mpich2 and that overrides whatever is in /etc/man_db.conf. A culprit is /etc/modulefiles/mpich2-x86_64 with prepend-path MANPATH /usr/share/man/mpich2 line in it. With MANPATH otherwise empty this has effects as above and we are screwed. Unsetting MANPATH restores most of sanity but then manpages in /usr/share/man/mpich2 become invisible. Setting MANPATH instead to '/usr/share/man/mpich2:' would work for everybody; only environment-modules are "smart" and are eating a trailing ':' fed to prepend-path and apparently they are hellbent on it. That behaviour is seriously buggy in itself as there are other examples when trailing colons in environment variables are semantically significant. TEXINPUTS, when set, comes to mind (and it requires '::'). BTW - if you will try prepend-path PATH /usr/lib64/mpich2/bin: then this colon is kept resulting in a harmless '::' in $PATH but there are other elements following that. OTOH for ':/usr/share/man/mpich2', which would work as a value of MANPATH too, this colon is lost as well. Version-Release number of selected component (if applicable): mpich2-1.4.1p1-2.fc17 environment-modules-3.2.9a-1.fc17 How reproducible: always
i have the same problem in f15 with the latest update.
(In reply to comment #1) > i have the same problem in f15 with the latest update. Here is a workaround until this get fixed one way or another. Create a file /etc/profile.d/z_fixmanpath.sh with the following lines in it: # fix a damage inflicted by environment-modules [ -n "$MANPATH" ] && MANPATH="${MANPATH%:}:" If you happen to use csh then create z_fixmanpath.csh which does the similar thing there. It should work although I did not check that an execution order will be right in all circumstances.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.