Re: up2date - package update dependency

On 1/26/2007 2:43 AM, Aries Star wrote:
> We have servers which have not been updated with patches for quite some 
> time (since year 2005). The latest package usually have the following 
> dependancy:
> 
> "Before applying this update, make sure all previously released errata
> relevant to your system have been applied."

What I didn't mention in my other posting is *why* you need to do this. 
  One of the key reasons is that package foo may have a requirement for 
say package bar.  When you up2date, it will update bar only if bar isn't 
at the version specificied in the dependency.  If the version is okay 
but is missing some critical security fixes, it won't be updated 
automatically.

One other key reason to update all of the previously released errata is 
that the testing for the latest updates is only done against the current 
versions of the packages.  It's totally impractical for Red Hat (or 
anybody else) to test the latest update of the package you're interested 
in against all previous permutations of patches on your system.  They 
simply bring the systems up to date and then test against that set.

This is why you should not attempt to pick and choose which updates to 
apply - even if you think the update may not be relevant to you, you 
should apply them all.  Exceptions may apply to those who really know 
what they're doing...

	.../Ed

-- 
Ed Wilts, RHCE, Mounds View, MN, USA
mailto:[email protected]

--
Taroon-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/taroon-list