Bug 1986746 - vsctool.py has wrong interpreter '#!/usr/bin/python2'
Summary: vsctool.py has wrong interpreter '#!/usr/bin/python2'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: varnish
Version: rh-varnish6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
: 3.7
Assignee: Luboš Uhliarik
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-28 09:17 UTC by Branislav Náter
Modified: 2023-08-08 07:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-08 07:28:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Branislav Náter 2021-07-28 09:17:53 UTC
Description of problem:
Shebang test [1] caught this issue [2] in /opt/rh/rh-varnish6/root/usr/share/varnish/vsctool.py:

Shebang has been found in this file:
------------------------------------
/opt/rh/rh-varnish6/root/usr/share/varnish/vsctool.py
(Python script, UTF-8 Unicode text executable)
#!/usr/bin/python2
:: [ 12:25:01 ] :: [   FAIL   ] :: File '/opt/rh/rh-varnish6/root/usr/share/varnish/vsctool.py' has wrong interpreter '#!/usr/bin/python2' 

1. https://wiki.test.redhat.com/SoftwareCollections/GeneralTests#shebangcheck
2. https://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2021/07/56378/5637819/10391797/129579738/taskout.log

Version-Release number of selected component (if applicable):
rh-varnish6-varnish-6.0.8-2.el7


Steps to Reproduce:
1. by running test /CoreOS/scl-utils/Sanity/general-shebang-check

Actual results:
failing test

Expected results:
passing test (correct shebang)

Comment 5 RHEL Program Management 2023-08-08 07:28:34 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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