<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:25:16 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-16242] Self-built lustre-client-dkms requires /usr/bin/python2</title>
                <link>https://jira.whamcloud.com/browse/LU-16242</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;RHEL 9 and its derivatives are no longer distributed with python 2. Two scripts specify python2 as their interpreter:&lt;br/&gt;
contrib/scripts/gerrit_checkpatch.py&lt;br/&gt;
lustre/scripts/zfsobj2fid&lt;br/&gt;
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.&lt;br/&gt;
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. &lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
#!/usr/bin/env python2
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;becomes:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
#!/usr/bin/env python3
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;When I looked for previous issues related to this, it appeared that &apos;python&apos; was changed to &apos;python2&apos; for debian builds. I didn&apos;t test these scripts with python3.&lt;/p&gt;</description>
                <environment></environment>
        <key id="72817">LU-16242</key>
            <summary>Self-built lustre-client-dkms requires /usr/bin/python2</summary>
                <type id="9" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/undefined.png">Question/Request</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="3">Duplicate</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="jstroik">Jesse Stroik</reporter>
                        <labels>
                    </labels>
                <created>Mon, 17 Oct 2022 16:18:31 +0000</created>
                <updated>Tue, 1 Aug 2023 00:21:06 +0000</updated>
                            <resolved>Tue, 1 Aug 2023 00:21:06 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="349883" author="jstroik" created="Mon, 17 Oct 2022 16:29:50 +0000"  >&lt;p&gt;RHEL 9 and its derivatives are no longer distributed with python 2. Two scripts specify python2 as their interpreter:&lt;/p&gt;

&lt;p&gt;contrib/scripts/gerrit_checkpatch.py&lt;/p&gt;

&lt;p&gt;lustre/scripts/zfsobj2fid&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&#160;&lt;/p&gt;

&lt;p&gt;#!/usr/bin/env python2&lt;/p&gt;

&lt;p&gt;becomes:&lt;/p&gt;

&lt;p&gt;#!/usr/bin/env python3&lt;/p&gt;

&lt;p&gt;When I looked for previous issues related to this, it appeared that &apos;python&apos; was changed to &apos;python2&apos; for debian builds. I didn&apos;t test these scripts with python3.&lt;/p&gt;</comment>
                            <comment id="349889" author="adilger" created="Mon, 17 Oct 2022 17:00:28 +0000"  >&lt;p&gt;Hi Jesse, could you please push a patch for changing these tools to use python3. Have you actually tried running them after changing the python version?  I&apos;m not much of a python person myself, but know that they may need minor updates to work with the new version. &lt;/p&gt;</comment>
                            <comment id="349900" author="simmonsja" created="Mon, 17 Oct 2022 17:41:27 +0000"  >&lt;p&gt;Yes please push the patches. I would be great to drop python2.&lt;/p&gt;</comment>
                            <comment id="349902" author="jstroik" created="Mon, 17 Oct 2022 18:16:39 +0000"  >&lt;p&gt;I have &lt;b&gt;not&lt;/b&gt; tested these scripts.&lt;/p&gt;

&lt;p&gt;pylint suggests minor changes are needed lustre/scripts/zfsobj2fid.&#160; It looks like someone might have already updated this script and added pout.decode() call that I would have missed. It&apos;s in the &lt;a href=&quot;https://github.com/LLNL/lustre-tools-llnl/commit/184e95f601d6e4d84b1fcb335ff26bf363ebf948&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;LLNL lustre-tools repo&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The other script, contrib/scripts/gerrit_checkpatch.py, looks more involved. I&apos;m not a python programmer so I don&apos;t think I&apos;d be a good choice to cobble together changes to that &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.whamcloud.com/images/icons/emoticons/wink.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="380812" author="adilger" created="Tue, 1 Aug 2023 00:20:59 +0000"  >&lt;p&gt;This was fixed on master via patch &lt;a href=&quot;https://review.whamcloud.com/50241&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/50241&lt;/a&gt; &quot;&lt;tt&gt;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-16626&quot; title=&quot;Don&amp;#39;t use or check for python2 for lustre-zfs-dkms rpm&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-16626&quot;&gt;&lt;del&gt;LU-16626&lt;/del&gt;&lt;/a&gt; build: remove python2 dependencies&lt;/tt&gt;&quot;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="74974">LU-16626</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="70396">LU-15874</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10030" key="com.atlassian.jira.plugin.system.customfieldtypes:labels">
                        <customfieldname>Epic/Theme</customfieldname>
                        <customfieldvalues>
                                        <label>build</label>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i03307:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>