Red Hat Bugzilla – Bug 461775
man needs lzma, but not getting installed
Last modified: 2008-09-25 12:18:28 EDT
Description of problem: man yum fails on default install because lzma isn't installed.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Do default install of F10a, been unchecking dial up and office and java
2. man yum
# man yum
Formatting page, please wait...
sh: /usr/bin/lzma: No such file or directory
Error executing formatting or display command.
System command (cd /usr/share/man && (echo ".pl 1100i"; /usr/bin/gunzip -c '/usr/share/man/man8/yum.8.gz'; echo ".\\\""; echo ".pl \n(nlu+10") | /usr/bin/gtbl | /usr/bin/nroff -c -mandoc 2>/dev/null | /usr/bin/lzma > /var/cache/man/cat8/yum.8.lzma) exited with status 32512.
Show man page
yum install lzma
Installed: lzma.i386 0:4.32.7-1.fc10
Dependency Installed: lzma-libs.i386 0:4.32.7-1.fc10
man yum works great!
jlaska perhaps a bug requesting that `man` adds a %requires lzma to it's spec file might be in order
Hello, please could you attach here your /etc/man.config file?
The problem should be you either change /etc/man.config setting or you have an environment variable PAGER set to /usr/bin/lzma.
So please put here printenv | grep PAGER too.
*** Bug 461842 has been marked as a duplicate of this bug. ***
Sorry about the duplicate.
About your questions regarding man.config and PAGER, PAGER is not set. man.config is unchanged from as it is in the rpm (man-1.6f-9.fc10.i386), never the less I'll attach it for you.
Created attachment 316546 [details]
Checking the attached man.config you will see it specifies lzma, which explains why man needs lzma now, maybe the upstream defaults have changed?
Anyways the fix is to either change the default config as it installed with a fresh install, or to add a "Requires: /usr/bin/lzma" to the package.
Note I verified that this man.config is unchanged from the one in the rpm using rpm --verify
Thanks. Fixed in man-1.6f-10.fc10.i386
*** Bug 463324 has been marked as a duplicate of this bug. ***
*** Bug 463941 has been marked as a duplicate of this bug. ***