Bug 852762 - cdrdao - Inconsistency between man page and help
Summary: cdrdao - Inconsistency between man page and help
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cdrdao
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Frantisek Kluknavsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-29 14:05 UTC by Filip Holec
Modified: 2016-04-18 10:21 UTC (History)
3 users (show)

Fixed In Version: cdrdao-1.2.3-16.fc18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-01 15:04:36 UTC


Attachments (Terms of Use)

Description Filip Holec 2012-08-29 14:05:19 UTC
Description of problem:
Several commands are mentioned in help but not in man:
* toc-info
* toc-size
* discid
* drive-info
* scanbus

Version-Release number of selected component (if applicable):
cdrdao-1.2.3-14.fc18.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Check man page
2. Check --help option
  
Actual results:
Inconsistent man page/help

Expected results:
Consistent man page/help

Additional info:

Comment 1 Fedora Update System 2012-10-08 14:31:49 UTC
cdrdao-1.2.3-16.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/cdrdao-1.2.3-16.fc18

Comment 2 Fedora Update System 2012-10-08 23:53:35 UTC
Package cdrdao-1.2.3-16.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cdrdao-1.2.3-16.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-15660/cdrdao-1.2.3-16.fc18
then log in and leave karma (feedback).

Comment 3 Fedora Admin XMLRPC Client 2012-10-16 11:19:11 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.


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