<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 11, 2014 at 11:51 AM, Gary Buhrmaster <span dir="ltr"><<a href="mailto:gary.buhrmaster@gmail.com" target="_blank">gary.buhrmaster@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div>On Tue, Mar 11, 2014 at 4:20 PM, A Desai <<a href="mailto:ashu.desai@gmail.com">ashu.desai@gmail.com</a>> wrote:<br>
> I had a generic update question -<br>
</div>....<br>
<div>> * Is it okay to do a "yum update" on either one or both Linux systems? It's<br>
> been a while so the update show me 651 Mb worth of installation on the<br>
> backend. I didn't want an update on the Linux side to break my myth.<br>
<br>
</div>RHEL (as you know, which is why you are probably using it) is targeted<br>
for long term stability and works to avoid API changes that would break<br>
existing applications. Updates are usually non-impacting (as with all<br>
else, testing on your development systems is always recommended),<br>
although you should read the release notes if you are crossing a release<br>
(6.4 to 6.5, for example), as that is when RH would have changed<br>
something substantive (if they were forced to do so, usually forced<br>
by some upstream changes).<br>
<br>
That said, since RHEL6 never shipped with Qt4.8, you are either using<br>
a locally built/installed Qt, or using a 3rd party built Qt (repo). And<br>
those could have issues, since (clearly) RH cannot assure that there<br>
are not incompatible changes in their updates with other repos or<br>
local installations (depending on how you performed it), and could<br>
replace/update libraries without appropriate dependency checking.<br>
<br>
One thing to do is to do the "yum upgrade" and look at the repos from<br>
which the updates are coming. Look carefully at the list of updates,<br>
and from which repos they are coming from. The non-CentOS ones<br>
are more likely to cause issues.<br>
</blockquote><div><br></div><div>Thank you. I will take a note of the repos before I do anything. I guess my gut tells me that "if it ain't broken, don't fix it". On the other hand, I has been over a year since I did any sort of an update on the machines so I think I should...</div>
<div><br></div><div>Ash. </div></div></div></div>