Hi, With the introduction of default python 3 shebangs and the change in configure.ac to correct these to py2 if the build is being attempted on a machine that does not have py3, there are a couple of issues uncovered. Here is the plan to fix the same, suggestions welcome. Issues: - A configure job is run when creating the dist tarball, and this runs on non py3 platforms, hence changing the dist tarball to basically have py2 shebangs, as a result the release-new build job always outputs py files with the py2 shebang. See tarball in [1] - All regression hosts are currently py2 and so if we do not run the py shebang correction during configure (as we do not build and test from RPMS), we would be running with incorrect py3 shebangs (although this seems to work, see [2]. @kotresh can we understand why?) Plan to address the above is detailed in this bug [3]. The thought is, - Add a configure option "--enable-py-version-correction" to configure, that is disabled by default - All regression jobs will run with the above option, and hence this will correct the py shebangs in the regression machines. In the future as we run on both py2 and py3 machines, this will run with the right python shebangs on these machines. - The packaging jobs will now run the py version detection and shebang correction during actual build and packaging, Kaleb already has put up a patch for the same [2]. Thoughts? Shyam [1] Release tarball: https://build.gluster.org/job/release-new/69/ [2] Patch that defaults to py3 in regression and passes regressions: https://review.gluster.org/c/glusterfs/+/21266 [3] Infra bug to change regression jobs: https://bugzilla.redhat.com/show_bug.cgi?id=1633425 _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
