Bug 1039978 - mysql_config nonzero return code on usage message
Summary: mysql_config nonzero return code on usage message
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mariadb
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Honza Horak
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On: 1039975
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-10 13:00 UTC by Karel Volný
Modified: 2014-01-21 12:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1039975
Environment:
Last Closed: 2014-01-21 12:36:16 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Karel Volný 2013-12-10 13:00:45 UTC
cloning to track failure in our test for the appropriate RHEL version

+++ This bug was initially created as a clone of Bug #1039975 +++

Description of problem:
Trying to run mysql_config without parameters, it returns nonzero exit code. But this is not an error, the application should return zero.

Version-Release number of selected component (if applicable):
mariadb-5.5.33a-1.fc19

How reproducible:
always

Steps to Reproduce:
1. mysql_config >/dev/null; echo $?

Actual results:
1

Expected results:
0

Additional info:
from the manpage:

"If you invoke mysql_config with no options, it displays a list of all options that it supports, and their values:"

so, invoking without parameters is correct usage ...

note also that it'd be nice to support the "--help" option, but that's more RFE material than a bug

Comment 2 Honza Horak 2013-12-12 15:57:33 UTC
Let's wait for upstream opinion.

Comment 3 Honza Horak 2014-01-07 16:08:55 UTC
Unless upstream accepts it soon, I'm moving it for RHEL-7.1.

Comment 4 Honza Horak 2014-01-21 12:36:16 UTC
Now it is quite late for such minor changes in RHEL-7, so deferring to upstream. If they accept that change, it will most probably get into RHEL-7 together with some security update/rebase.


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