Red Hat Bugzilla – Bug 613622
Some manpages got removed from man-pages-fr
Last modified: 2012-04-18 23:26:24 EDT
Description of problem:
RPMdiff reported some removed man pages in man-pages-fr package. See
Looks like some of them should be included (e.g. lynx)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rpm -ql man-pages-fr | grep lynx
No man page
Man page was available in previous version
Hmm, seems like the files in mansupfr.tar.bz2 are not extracted.
However, since lynx also come with its own French translation,
I afraid including lynx will cause file conflict.
Does French translation in lynx package correct and accurate?
Actually I intent to include the mansupfr back, as there is still some logic to process the content.
Still need to make sure which man pages in it might trigger file conflicts.
This bug reveals that some man-pages in mansupfr are not included.
However, add back the mansupfr may trigger file conflict with packages that bring their own French translation, so I would suggest this bug to be fixed in 6.1.0.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
Is this fixed in Fedora?
My only concern is that this could possibly introduce some file conflict regressions.
bug #603627 need to consider for Regression.
Sebastien Aime has done the verified the man-pages-fr and I have excluded the man pages which do not pass the verification.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.