Bug 564401 - --version option doesn't work in publican
Summary: --version option doesn't work in publican
Keywords:
Status: CLOSED DUPLICATE of bug 533081
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 1.6
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-12 16:29 UTC by Deon Ballard
Modified: 2010-11-24 04:19 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-15 00:25:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Deon Ballard 2010-02-12 16:29:46 UTC
[dlackey@dlackey schema]$ publican --version
Unknown option: version


Usage:
    publican <global options>

    publican <action> <options>

    Global Options

        --help      Display help message
        --man               Display Full man page
        --help_actions      Display a list of valid actions
        --version   Display the version of Publican

    Run: 'publican <action> --help' for details on action usage

    Valid actions are:

        build         Transform XML to other formats (pdf, html, html-single)
        clean         Remove all temporary files and directories
        clean_ids     Run clean ids for source XML
        cleanset      Remove local copies remote set books
        create        Create a new Book|Set|Article|brand
        create_brand  Create a new Brand
        help_config   Display help text for the configuration file
        installbrand  Install a brand to the supplied location
        old2new       Create a publican.cfg file for an old Book|Article|Set Makefile
        package       Package a language for shipping
        printtree     Print a tree of the xi:includes
        update_po     Update the PO files
        update_pot    Update the POT files

Comment 1 Jeff Fearn 🐞 2010-02-15 00:25:44 UTC

*** This bug has been marked as a duplicate of bug 533081 ***


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