Bug 1007605 - libpopt sensitivity to $POSIXLY_CORRECT nukes smbstatus option processing
Summary: libpopt sensitivity to $POSIXLY_CORRECT nukes smbstatus option processing
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Guenther Deschner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-12 22:54 UTC by Frank Ch. Eigler
Modified: 2016-07-19 10:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 10:22:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank Ch. Eigler 2013-09-12 22:54:28 UTC
As of rawhide samba 4.1rc (and far back as rhel5's samba 3),
compare & contrast:

% env -u POSIXLY_CORRECT   smbstatus --help
% env    POSIXLY_CORRECT=1 smbstatus --help

The latter ignores the --help option.  This is due to libpopt being
sensitive to that environment variable, (popt.c:195 as of popt 1.13).

Please consider explicitly unsetting the environment variable before
calling into libpopt.  Or fix (if there is a problem; dunno) the
smbstatus long-options to be sufficiently saintly to work even with
$POSIXLY_CORRECT.

Comment 1 Jaroslav Reznik 2015-03-03 15:03:23 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 2 Fedora End Of Life 2016-07-19 10:22:09 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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