Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-16242

Self-built lustre-client-dkms requires /usr/bin/python2

Details

    • Question/Request
    • Resolution: Duplicate
    • Minor
    • None
    • None
    • None
    • 9223372036854775807

    Description

      RHEL 9 and its derivatives are no longer distributed with python 2. Two scripts specify python2 as their interpreter:
      contrib/scripts/gerrit_checkpatch.py
      lustre/scripts/zfsobj2fid
      I did attempt to create the distribution with tests and i/o kit disabled, but the lustre-client-dkms RPM still required /usr/bin/python2.
      I modified the interpreter to python3 for those scripts and tested. The RPM will no longer requires /usr/bin/python2 and can then be installed on rocky9.

      #!/usr/bin/env python2
      

      becomes:

      #!/usr/bin/env python3
      

      When I looked for previous issues related to this, it appeared that 'python' was changed to 'python2' for debian builds. I didn't test these scripts with python3.

      Attachments

        Issue Links

          Activity

            [LU-16242] Self-built lustre-client-dkms requires /usr/bin/python2
            adilger Andreas Dilger made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-16626 [ LU-16626 ]
            adilger Andreas Dilger made changes -
            Description New: RHEL 9 and its derivatives are no longer distributed with python 2. Two scripts specify python2 as their interpreter:
            contrib/scripts/gerrit_checkpatch.py
            lustre/scripts/zfsobj2fid
            I did attempt to create the distribution with tests and i/o kit disabled, but the lustre-client-dkms RPM still required /usr/bin/python2.
            I modified the interpreter to python3 for those scripts and tested. The RPM will no longer requires /usr/bin/python2 and can then be installed on rocky9.
            {code}
            #!/usr/bin/env python2
            {code}
            becomes:
            {code}
            #!/usr/bin/env python3
            {code}
            When I looked for previous issues related to this, it appeared that 'python' was changed to 'python2' for debian builds. I didn't test these scripts with python3.
            adilger Andreas Dilger made changes -
            Link New: This issue is related to LU-15874 [ LU-15874 ]
            jstroik Jesse Stroik created issue -

            People

              wc-triage WC Triage
              jstroik Jesse Stroik
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: