[Bugs] [Bug 1633425] New: Need regression jobs to build with python version detection

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1633425

            Bug ID: 1633425
           Summary: Need regression jobs to build with python version
                    detection
           Product: GlusterFS
           Version: mainline
         Component: project-infrastructure
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: srangana at redhat.com
                CC: bugs at gluster.org, gluster-infra at gluster.org



Description of problem:

The issue that we need to address is,
- Build with the right python version (or shebangs) in the regression jobs
- Build with the right python version for the various distributions

Currently, with the auto correction of python shebangs in configure, the dist
packages get bundled with python2 shebangs, whereas this decision needs to be
postponed to when packages are built for a distribution.

The above change is addressed with this commit:
https://review.gluster.org/c/glusterfs/+/21266

The above change now runs with py3 shebangs even on Cent7 regression machines
(idk why that works).

To get this corrected and to run with right python versions and to also enable
testing py2 backward compatability (as that is what we are claiming for our
python code), we need to get a configure option back into the configure.ac.

This new option will,
- Be off by default (so all shebangs remain py3)
- Should be turned on to detect and hence correct the py shebangs in the python
files

The regression jobs hence, should build with this new option enabled, and
possibly handle failures till the option is actually available (as Nigel
pointed out in a conversation).

This bug is to track the above request (i.e changing the regression jobs to
handle the new option).

I think we should call the option "--enable-py-version-correction" (if such
long options are permissible. Other nicer verbiage welcome.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.