https://bugzilla.redhat.com/show_bug.cgi?id=531870
Description of problem: 389-console no loner provides any usage options, help, or man pages. There used to be some command line options like -a to specify what admin url to connect to. Version-Release number of selected component (if applicable): [mgregg@tiny ~]$ rpm -qa 389-console 389-console-1.1.3-3.fc11.noarch How reproducible: always Steps to Reproduce: 1. 389-console --help or 1. man 389-console or 1. info 389-console
batch update to FUTURE milestone
set default ticket origin to Community
Added initial screened field value.
attachment 0001-Ticket-97-389-console-should-provide-man-page.patch
Very nice. Thanks, Mark!
git merge ticket97 Updating c8d5cc5..23e0e74 Fast-forward 389-console.8 | 78 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 389-console.spec | 5 ++++- build.xml | 10 ++++++++-- 3 files changed, 90 insertions(+), 3 deletions(-) create mode 100644 389-console.8
git push origin master c8d5cc5..23e0e74 master -> master
commit 23e0e74c245604e69f2153c48028fde3aee2103a Author: Mark Reynolds mreynolds@redhat.com Date: Tue Aug 26 10:34:25 2014 -0400
git patch file (idm-console-framework master) 0001-Ticket-97-389-console-should-provide-usage-options-h.patch
ack - you'll also need a change to the 389-console shell script.
Replying to [comment:13 rmeggins]:
I see. I thought the shell script in the source tree is obsolete and deprecated. I'm changing it. Thanks!
Let me confirm one thing... If we build with "buildnoscript", 389-console is generated, e.g., having the options specified in the spec file? If we build without "buildnoscript", the 389-console shell script is used?
Replying to [comment:14 nhosoi]:
Replying to [comment:13 rmeggins]: ack - you'll also need a change to the 389-console shell script. I see. I thought the shell script in the source tree is obsolete and deprecated.
I see. I thought the shell script in the source tree is obsolete and deprecated.
It is. I think it uses some special java script build magic in the 389-console.spec file.
I'm changing it. Thanks!
I don't think there is a need to change that.
I'm not sure. It's been a long time since I looked at that stuff. I think the 389-console script is generated "magically" in the 389-console.spec file.
Metadata Update from @rmeggins: - Issue assigned to mreynolds - Issue set to the milestone: 389-admin,console 1.1.36
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/97
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.