On 3/5/2011 1:35 πμ, Steve Jenkins wrote:
I actually didn't have it in either - I was under the (apparently false) impression that just putting the exclude in yum.conf would apply to any repo. It's in the CentOS-Base.repo file in [base] and [updates] now, tho. Thank you. :)
I also have servers with compiled Postfix (2.8.1 and 2.8.2), thanks to your blog Steve, and I also recently upgraded all of them to CentOS 5.6.
I only have an exclude for postfix* in yum.conf and all upgrades (with "yum update") went without problems. My Postfix was not replaced by the distribution's package.
In one server where I had forgotten the exclude in yum.conf, I saw Postfix was in the results of yum check-update, but then I added it and re-run yum check-update, and Postfix was no more included in the offered updates.
So, from my point of view, an exclude at the bottom of yum.conf does the job! :-)
Perhaps you used "yum upgrade"? This could possibly have more radical effects to installable packages? Yet, from the man page:
"Upgrade: Is the same as the update command with the --obsoletes flag set... " "--obsoletes: This option only has affect for an update, it enables yum΄s obsoletes processing logic." "If the main obsoletes configure option is true (default) or the --obsoletes flag is present yum will include package obsoletes in its calculations..."...it seems that (since obsoletes configure option is by default true) upgrade = update, so there should not be a difference.
In any case, I used "yum update" in all cases. Nick
smime.p7s
Description: S/MIME Cryptographic Signature
