Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
And others:
abrt 2.0.5 07/28/2011 REPORT-CLI(1)
abrt 2.0.4.32.g92a1 07/18/2011 REPORTER-BUZILLA(1)
abrt 2.0.4.32.g92a1 07/18/2011 REPORTER-KERNELOOPS(1)
abrt 2.0.4.32.g92a1 07/18/2011 REPORTER-MAILX(1)
abrt 2.0.4.32.g92a1 07/18/2011 REPORTER-PRINT(1)
abrt 2.0.4.32.g92a1 07/18/2011 REPORTER-UPLOAD(1)
Those from btparser & abrt don't have it at all and the date looks suspicious to me too:
24 May 2010 btparser(1)
28 May 2009 abrt.conf(5)
28 May 2009 abrt.conf(5)
28 May 2009 abrt(8)
28 May 2009 abrtd(8)
Used:
for page in $(rpmquery -al "*abrt" "*libreport*" btparser | grep man/ | sort); do man $page | tail -n1; done
(In reply to comment #2)
> And others:
>
> abrt 2.0.5 07/28/2011 REPORT-CLI(1)
> abrt 2.0.4.32.g92a1 07/18/2011 REPORTER-BUZILLA(1)
> abrt 2.0.4.32.g92a1 07/18/2011 REPORTER-KERNELOOPS(1)
> abrt 2.0.4.32.g92a1 07/18/2011 REPORTER-MAILX(1)
> abrt 2.0.4.32.g92a1 07/18/2011 REPORTER-PRINT(1)
> abrt 2.0.4.32.g92a1 07/18/2011 REPORTER-UPLOAD(1)
commit for libreport
commit cad632aa16e970a0340ab24c87adfad831b2f52b
Author: Nikola Pajkovsky <npajkovs>
Date: Thu Aug 4 15:04:21 2011 +0200
do not include generated man pages
Signed-off-by: Nikola Pajkovsky <npajkovs>
commit for abrt
commit 7ed6816b2b5ba935fb6c4737297356641d600786
Author: Nikola Pajkovsky <npajkovs>
Date: Thu Aug 4 15:11:24 2011 +0200
do not include generated man pages
Signed-off-by: Nikola Pajkovsky <npajkovs>
> Those from btparser & abrt don't have it at all and the date looks suspicious
> to me too:
>
> 24 May 2010 btparser(1)
Karel, do you have up to date your man?
> 28 May 2009 abrt.conf(5)
> 28 May 2009 abrt.conf(5)
> 28 May 2009 abrt(8)
> 28 May 2009 abrtd(8)
those are not rewritten or up to date
> Used:
>
> for page in $(rpmquery -al "*abrt" "*libreport*" btparser | grep man/ | sort);
> do man $page | tail -n1; done
commit 237e516fc738e40bc51a2088e1c7e3df983ed243
Author: Nikola Pajkovsky <npajkovs>
Date: Tue Oct 18 16:49:17 2011 +0200
rhbz#728190 - man pages contain suspicious version string
Signed-off-by: Nikola Pajkovsky <npajkovs>
(cherry picked from commit f261edf4b07aad8f175f8cc5cb755053994c2bba)
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.
http://rhn.redhat.com/errata/RHBA-2011-1598.html