[opensuse-support] Command man in Tumbleweed does not work anymore /usr/lib -> /usr/libexec
I upgraded Tumbleweed and tried to use man. /usr/bin/man -> /etc/alternatives/man which points to /usr/lib/man-db/wrapper, which does not exists anymore. However /usr/libexec/man-db/wrapper does exist. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Freek de Kruijf
I upgraded Tumbleweed and tried to use man.
/usr/bin/man -> /etc/alternatives/man which points to /usr/lib/man-db/wrapper, which does not exists anymore. However /usr/libexec/man-db/wrapper does exist.
zypper -v in --force man then it will work -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Fri, 04 Sep 2020 15:26:19 +0200
Freek de Kruijf
I upgraded Tumbleweed and tried to use man.
/usr/bin/man -> /etc/alternatives/man which points to /usr/lib/man-db/wrapper, which does not exists anymore. However /usr/libexec/man-db/wrapper does exist.
I'm confused. I'd never heard of /usr/libexec/ before so I looked at https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html which indicates that it should be used for "internal binaries that are not intended to be executed directly by users or shell scripts". I don't pretend to understand why a binary executable would be stored under any path that starts /usr/lib... but even granted that it does, I *really* don't understand why invoking man should cause a binary in /usr/libexec/ to be executed? ??? -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (3)
-
Dave Howorth -
Freek de Kruijf -
Patrick Shanahan