this was done a while back. 

You can now open up the aeolus-image man page via:

man aeolus-image

Observed that still man aeolus-image gives the same output

[root@nec-em24-3 ~]# man aeolus-image
No manual entry for aeolus-image

on 
rpm -qa | grep aeolus
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-daemons-0.13.8-1.el6cf.noarch
rubygem-aeolus-cli-0.7.1-1.el6cf.noarch
aeolus-conductor-doc-0.13.8-1.el6cf.noarch
aeolus-all-0.13.8-1.el6cf.noarch
aeolus-conductor-0.13.8-1.el6cf.noarch
aeolus-configure-2.8.6-1.el6cf.noarch

setting it back to assigned.

A couple of potentially interesting observations:

Note that on fedora, `man aeolus-image` displays the man page for aeolus-image-list. There is no separate man source for aeolus-image.

On rhel, `man aeolus-image-list` works fine.

Not sure what magic fedora uses to determine that man should display the aeolus-image-list man page when you invoke `man aeolus-image`, but that is what appears to be missing on RHEL.

Looks like this is due to fedora using man-db and rhel using plain old man. The text of ./man/aeolus-image-list.1 uses aeolus-image for the program name, man page subject, etc. So that's what's getting indexed in /var/cache/man/index.db on fedora.

reviewing it now, just checking that it installs properly everywhere.

patch works for me. pushed to
8555dbe master
cbd054e 1.1

setting component to rubygem-aeolus-cli since that's where the executable in question lives.

aeolus-image has now a man page entry.

# man aeolus-image
aeolus-image(1)                  USER COMMANDS                 aeolus-image(1)

NAME
       aeolus-image - command line tool for managing images and related resources on the aeolus suite of tools

SYNOPSIS
       aeolus image [list|build|push|import|status] [-h]

DESCRIPTION
       aeolus-image  is a tool that allows users to manage images and related resources in their aeolus installation.  Such resources consist
       of:

       aeolus-image consists of 5 subcommands: list, build, push, import and status.

       Each command can also be called directly via ’aeolus-image’ or via ’aeolus-image-{subcommand}’

       For more information on each subcommand, you may run any of the following:
           man aeolus-{command}-{subcommand}
           aeolus-image {subcommand} --help
           aeolus-image-{subcommand} --help
           aeolus --help

OPTIONS
       -h, --help
              Get usage information for this tool and subcommands

FILES
       aeolus reads its configuration from ~/.aeolus-cli

       ~/.aeolus-cli
              This contains the URL and credentials for your admin user in aeolus-conductor.  If setup differs from default one, those should
              be changed accordingly. Conductor URL should be as follows https://<host_where_conductor_runs>/conductor/api

AUTHORS
       Martyn Taylor (mtaylor), Jason Guiditta (jguiditta)

SEE ALSO
       aeolus-image-build(1), aeolus-image-push(1), aeolus-image-list(1), aeolus-image-import(1), aeolus-image-status(1)

version 0.4                    December 20, 2011               aeolus-image(1)





verified:
rpm -qa | grep aeolus
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.7.2-1.el6cf.noarch
aeolus-conductor-doc-0.13.14-1.el6cf.noarch
aeolus-configure-2.8.7-1.el6cf.noarch
aeolus-all-0.13.14-1.el6cf.noarch
aeolus-conductor-0.13.14-1.el6cf.noarch
aeolus-conductor-daemons-0.13.14-1.el6cf.noarch

good to go

aeolus-all-0.13.24-1.el6cf.noarch
aeolus-conductor-0.13.24-1.el6cf.noarch
aeolus-conductor-daemons-0.13.24-1.el6cf.noarch
aeolus-conductor-doc-0.13.24-1.el6cf.noarch
aeolus-configure-2.8.11-1.el6cf.noarch
rubygem-aeolus-cli-0.7.7-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch

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/RHEA-2012-1516.html