<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">This reminds me that there is one more thing which drives the convoluted process I described earlier\u2026<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Automation. Deployment solutions which use yum to build new hosts are often the place where one notices the problem. They would need to determine that they
should install both the base-version and efix RPMS and <i>in that order. </i>IIRC, there were no RPM dependencies connecting the efix RPMs to their base-version equivalents, so there was nothing to signal YUM that installing the efix requires that the base-version
be installed first. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">(Our particular case is worse than just this though, since we prohibit installing two versions/releases for the same (non-kernel) package name. But that\u2019s not
the case for everyone.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-Paul<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> gpfsug-discuss-bounces@spectrumscale.org <gpfsug-discuss-bounces@spectrumscale.org>
<b>On Behalf Of </b>IBM Spectrum Scale<br>
<b>Sent:</b> Wednesday, January 15, 2020 16:00<br>
<b>To:</b> gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>
<b>Cc:</b> gpfsug-discuss-bounces@spectrumscale.org<br>
<b>Subject:</b> Re: [gpfsug-discuss] How to install efix with yum ?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:9.0pt;font-family:"Verdana",sans-serif;color:#CC0000">This message was sent by an external party.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p><span style="font-size:10.0pt">>> </span><span style="font-family:"Calibri",sans-serif">I don't see any yum options which match rpm's '--force' option.
</span><br>
<span style="font-size:10.0pt">Actually, you do not need to use --force option since efix RPMs have incremental efix number in rpm name.</span><br>
<br>
<span style="font-size:10.0pt">Efix package provides update RPMs to be installed on top of corresponding PTF GA version. When you install 5.0.4.1 efix9, if 5.0.4.1 is already installed on your system, "yum update" should work.
</span><br>
<br>
<span style="font-size:10.0pt">Regards, The Spectrum Scale (GPFS) team<br>
<br>
------------------------------------------------------------------------------------------------------------------<br>
If you feel that your question can benefit other users of Spectrum Scale (GPFS), then please post it to the public IBM developerWroks Forum at
<a href="https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479">
https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479</a>.
<br>
<br>
If your query concerns a potential software error in Spectrum Scale (GPFS) and you have an IBM software maintenance contract please contact 1-800-237-5511 in the United States or your local IBM Service Center in other countries.
<br>
<br>
The forum is informally monitored as time permits and should not be used for priority messages to the Spectrum Scale (GPFS) team.</span><br>
<br>
<img border="0" width="16" height="16" style="width:.1666in;height:.1666in" id="_x0000_i1025" src="cid:image001.gif@01D5CBCA.2A732840" alt="Inactive hide details for Jonathan Buzzard ---01/15/2020 02:09:33 PM---On 15/01/2020 18:30, Sanchez, Paul wrote: > Yum generall"><span style="font-size:10.0pt;color:#424282">Jonathan
Buzzard ---01/15/2020 02:09:33 PM---On 15/01/2020 18:30, Sanchez, Paul wrote: > Yum generally only wants there to be single version of a</span><br>
<br>
<span style="font-size:10.0pt;color:#5F5F5F">From: </span><span style="font-size:10.0pt">Jonathan Buzzard <<a href="mailto:jonathan.buzzard@strath.ac.uk">jonathan.buzzard@strath.ac.uk</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">To: </span><span style="font-size:10.0pt">"<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a>" <<a href="mailto:gpfsug-discuss@spectrumscale.org">gpfsug-discuss@spectrumscale.org</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Date: </span><span style="font-size:10.0pt">01/15/2020 02:09 PM</span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Subject: </span><span style="font-size:10.0pt">[EXTERNAL] Re: [gpfsug-discuss] How to install efix with yum ?</span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Sent by: </span><span style="font-size:10.0pt"><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">gpfsug-discuss-bounces@spectrumscale.org</a></span><o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<tt><span style="font-size:10.0pt">On 15/01/2020 18:30, Sanchez, Paul wrote:</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>> Yum generally only wants there to be single version of any package (it </tt>
<br>
<tt>> is trying to eliminate conflicting provides/depends so that all of the </tt>
<br>
<tt>> packaging requirements are satisfied). So this alien packaging practice </tt>
<br>
<tt>> of installing an efix version of a package over the top of the base </tt><br>
<tt>> version is not compatible with yum.</tt><br>
<br>
<tt>I would at this juncture note that IBM should be appending the efix </tt><br>
<tt>number to the RPM so that for example</tt><br>
<br>
<tt> gpfs.base-5.0.4-1 becomes gpfs.base-5.0.4-1efix9</tt><br>
<br>
<tt>which would firstly make the problem go away, and second would allow one </tt>
<br>
<tt>to know which version of GPFS you happen to have installed on a node </tt><br>
<tt>without doing some sort of voodoo.</tt><br>
<br>
<tt>> </tt><br>
<tt>> The real issue for draconian sysadmins like us (whose systems must use </tt>
<br>
<tt>> and obey yum) is that there are files (*liblum.so) which are provided by </tt>
<br>
<tt>> the non-efix RPMS, but are not owned by the packages according to the </tt>
<br>
<tt>> RPM database since they\u2019re purposefully installed outside of RPM\u2019s </tt><br>
<tt>> tracking mechanism.</tt><br>
<tt>></tt><br>
<br>
<tt>It worse than that because if you install the RPM directly yum/dnf then </tt>
<br>
<tt>start bitching about the RPM database being modified outside of </tt><br>
<tt>themselves and all sorts of useful information gets lost when you purge </tt>
<br>
<tt>the package installation history to make the error go away.</tt><br>
<br>
<tt>> We work around this by repackaging the three affected RPMS to include </tt>
<br>
<tt>> the orphaned files from the original RPMs (and eliminating the related </tt>
<br>
<tt>> but problematic checks from the RPMs\u2019 scripts) so that our efix RPMs </tt><br>
<tt>> have been \u201cun-efix-ified\u201d and will install as expected when using \u2018yum </tt>
<br>
<tt>> upgrade\u2019. To my knowledge no one\u2019s published a way to do this, so we </tt>
<br>
<tt>> all just have to figure this out and run rpmrebuild for ourselves.</tt><br>
<tt>></tt><br>
<br>
<tt>IBM should be hanging their heads in shame if the replacement RPM is </tt><br>
<tt>missing files.</tt><br>
<br>
<tt>JAB.</tt><br>
<br>
<tt>-- </tt><br>
<tt>Jonathan A. Buzzard Tel: +44141-5483420</tt><br>
<tt>HPC System Administrator, ARCHIE-WeSt.</tt><br>
<tt>University of Strathclyde, John Anderson Building, Glasgow. G4 0NG</tt><br>
<tt>_______________________________________________</tt><br>
<tt>gpfsug-discuss mailing list</tt><br>
<tt>gpfsug-discuss at spectrumscale.org</tt><br>
<tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a> </tt><br>
<br>
</span><br>
<br>
<o:p></o:p></p>
</div>
</div>
</body>
</html>