Bug 151541 - Repeated man pages
Summary: Repeated man pages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: man-pages
Version: 3.0
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Ivana Varekova
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-19 01:14 UTC by Binand Sethumadhavan
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-08-30 08:12:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Binand Sethumadhavan 2005-03-19 01:14:48 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

Description of problem:
A number of man pages are repeated in /usr/share/man/en/man?/ and /usr/share/man/man?/ directories. The don't even look exactly identical (even though the text of the manpage as displayed by man(1) looks the same):

[root@server man]# ls -l ./en/man2/getdomainname.2.gz ./man2/getdomainname.2.gz
-rw-r--r--    1 root     root         1190 Jun 10  2001 ./en/man2/getdomainname.2.gz
-rw-r--r--    1 root     root         1188 Oct  5 08:16 ./man2/getdomainname.2.gz

Just an annoyance, especially when you do something like man -a.

Version-Release number of selected component (if applicable):
1.60-4.2

How reproducible:
Always

Steps to Reproduce:
man -a time - you will see two time(2) man pages. man 2 time does not exhibit this problem.

Additional info:

RHEL 3 U4, up2dated completely.

Comment 1 Ivana Varekova 2005-08-30 08:12:52 UTC
Thank you for your notice. There are reasons why these man pages should be in
/usr/share/man/en/man?/ and /usr/share/man/man?/ directories and there are
reasons why they should not be there. I think upstream (mtk-manpages)
should resolved on this problem. Nowdays upstream version contains these man
pages in both directories. 


Note You need to log in before you can comment on or make changes to this bug.