Bug 1683716 - glusterfind: revert shebangs to #!/usr/bin/python3
Summary: glusterfind: revert shebangs to #!/usr/bin/python3
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterfind
Version: 6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-27 16:00 UTC by Kaleb KEITHLEY
Modified: 2019-03-25 16:33 UTC (History)
3 users (show)

Fixed In Version: glusterfs-6.0
Clone Of:
Environment:
Last Closed: 2019-03-02 11:55:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22275 0 None Merged glusterfind: revert shebangs to #!/usr/bin/python3 2019-03-02 11:55:12 UTC

Description Kaleb KEITHLEY 2019-02-27 16:00:56 UTC
Description of problem:


Using #!/usr/bin/env python is illegal in Fedora and RHEL packaging.
(Debian and SUSE packaging will complain about it too but don't
enforce it like Fedora packaging does. Yet.)
    
We went through a giant exercise fixing these once already.
    
The python needs to be python2/python3 clean. There is a build
scriptlet (in the glusterfs.spec file) that converts the shebangs back to /usr/bin/python on rhel7 at rpm build time.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2019-02-27 16:07:49 UTC
REVIEW: https://review.gluster.org/22275 (glusterfind: revert shebangs to #!/usr/bin/python3) posted (#3) for review on release-6 by Kaleb KEITHLEY

Comment 2 Worker Ant 2019-03-02 11:55:14 UTC
REVIEW: https://review.gluster.org/22275 (glusterfind: revert shebangs to #!/usr/bin/python3) merged (#4) on release-6 by Shyamsundar Ranganathan

Comment 3 Shyamsundar 2019-03-25 16:33:26 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report.

glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/


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