Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#9356 - pacman man page is broken at x86_64
Attached to Project:
Pacman
Opened by Petr Slansky (psl) - Sunday, 27 January 2008, 12:17 GMT
Last edited by Dan McGee (toofishes) - Monday, 04 February 2008, 15:45 GMT
Opened by Petr Slansky (psl) - Sunday, 27 January 2008, 12:17 GMT
Last edited by Dan McGee (toofishes) - Monday, 04 February 2008, 15:45 GMT
|
DetailsSummary and Info:
I cannot read pacman man page at x86_64 system Steps to Reproduce: $ pacman -Q pacman pacman 3.1.1-1 $ man pacman No manual entry for pacman $ man -k pacman pacman [] (8) - package manager utility pacman.conf [] (5) - pacman package manager configuration file $ ls -l /usr/share/man/man8/pacman.8.gz -rw-r--r-- 1 root root 5175 2008-01-20 21:36 /usr/share/man/man8/pacman.8.gz |
Closed by Dan McGee (toofishes)
Monday, 04 February 2008, 15:45 GMT
Reason for closing: Not a bug
Additional comments about closing: Should be OK now with any future releases and the man package being updated.
Monday, 04 February 2008, 15:45 GMT
Reason for closing: Not a bug
Additional comments about closing: Should be OK now with any future releases and the man package being updated.
man 1.6f-1
bug 8839.The problem is that /etc/profile sets a wrong MANPATH. It will be fixed when bash/filesystem are moved from testing.
Try : unset MANPATH
x86:
/usr/man
x86_64:
/usr/share/man/
Is this correct? I noticed a message that Arch moves man pages from /usr/man to /usr/share/man to be closer to LFS specification. But I don't understand why the same package in x86 and x86_64 differ.