<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:03:10 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-44] e2fsprogs&apos; configure does not detect when there is no db.h available</title>
                <link>https://jira.whamcloud.com/browse/LU-44</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;If you don&apos;t have a db-devel package installed and therefore have a db.h available, configure detects it but does not error out:&lt;/p&gt;

&lt;p&gt;checking db.h usability... no&lt;br/&gt;
checking db.h presence... no&lt;br/&gt;
checking for db.h... no&lt;/p&gt;

&lt;p&gt;But db.h is required for lfsck.&lt;/p&gt;</description>
                <environment></environment>
        <key id="10268">LU-44</key>
            <summary>e2fsprogs&apos; configure does not detect when there is no db.h available</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</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="2">Won&apos;t Fix</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="brian">Brian Murrell</reporter>
                        <labels>
                    </labels>
                <created>Wed, 19 Jan 2011 10:04:33 +0000</created>
                <updated>Sun, 28 May 2017 06:34:45 +0000</updated>
                            <resolved>Sun, 28 May 2017 06:34:45 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>0</watches>
                                                                            <comments>
                            <comment id="10452" author="adilger" created="Thu, 20 Jan 2011 13:03:59 +0000"  >&lt;p&gt;The e2fsprogs-lfsck.patch file wasn&apos;t checking for db4.7 and db4.8 being installed, so that is one source of problems.&lt;/p&gt;

&lt;p&gt;However, the e2fsprogs.spec file does add &quot;BuildRequires: db-devel&quot; so that should be detected.  That said, it should also be possible to build without lfsck if --disable-lfsck is passed to configure.&lt;/p&gt;</comment>
                            <comment id="10453" author="brian" created="Thu, 20 Jan 2011 13:20:43 +0000"  >&lt;p&gt;I noticed that it stopped at 4.6 also.  I wonder if there is some way to deal with this other just adding more successive checks.  I thought about it for a few minutes and couldn&apos;t really come up with anything since we won&apos;t know if (for example) 4.9 will be next or if they go to 5.0, etc.&lt;/p&gt;

&lt;p&gt;I did notice that 4.1 to 4.6 are all copy&apos;n&apos;pastes of the same thing with just versions changing.  I wonder if we can at least either put those all in a loop or use a function, etc.&lt;/p&gt;

&lt;p&gt;Regardless, I really do think configure should bail if it&apos;s supposed to be building lfsck and can&apos;t find a usable db.h.&lt;/p&gt;</comment>
                            <comment id="197252" author="adilger" created="Sun, 28 May 2017 06:34:45 +0000"  >&lt;p&gt;The db4 libraries are no longer needed.&lt;/p&gt;</comment>
                    </comments>
                    <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_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzw0u7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>10216</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>