It could be. I've noticed a similar thing recently. If I do not use wildcards, the exclusion of packages does not always work as expected.

I've found it seems to be xerces that's the root prob.
If I always refuse to update it, the others always go ok.
Unfortunately, tried to remove xerces so I don't have to keep un-selecting it on auto-updates, turns out it insists that Open Office (amongst others) is a dependency.
grrrr
Anybody got a perm fix eg like asking the developers to fix it. please please...
I'd have though by now they'd have done so.

I did a F7 install on my box a couple of days ago (upgrade from FC6 failed - another story), and now have OOo 2.2.0 installed as part of the "Workstation and Productivity" install option. Package xerces-j2 is back. In F7, OOo still depends upon xerces-j2. No related yum update issues yet - I'll post here if anything comes up.

xerces is a dependency for the Fedora version of OOo, but not the official OOo packages. Since I am using the official OOo packages, I did not have any problems uninstalling xerces.

Hello:

Yes, I found a solution: use smart-package-manager to do the update - it's smart enough to know that xml-commons-resolver11-1.3.03-10jpp would replace xml-commons-resolver-1.1-1jpp.12, without trying to remove other dependent packages (OOorg, etc.) with it. See http://forum.fedoraforum.org/forum/s...d.php?t=161024 Post #13.

Regards,
V

EDIT: Smart-Package-Manager: http://labix.org/smart

Thanks, guys.
I'll uninstall the Fedora OO packages dependent upon xerces-j2, install the official packages, then delete xerces-j2. I know this resolver11 problem is going to strike again one day...

Hlinger, the package you use looks promising - I'll check it out.

Edit...

Well, I thought I had the exclude thing sorted, but evolution update has appeared again! Do /etc/yum.conf exclude statements *really* work?

I also note that Nautilus sees yum.conf as type "Cisco VPN Settings". Other .conf files in /etc are "plain text document" files, which is what is expected. Any ideas on this?...

Hello:

Yes, /etc/yum.conf exclude statements work for me - but it's best to use them as "globs", i.e., exclude=evolution* . That way, the packages you mark as "exclude" from updates are less likely to get dragged in as dependencies of other packages (but IIRC yum should really not allow excluded packages to be updated, period).... As far as Nautilus: Maybe any *.conf file is listed as mime-type "Cisco VPN Settings". You could try opening /etc/yum.conf (as root) with text editor (e.g., gedit), then "Save as..." type=plain text document. It is possible that yum is overlooking the /etc/yum.conf file if it is an invalid type, but then you would see no message "Excluding Packages in global exclude list" when you process a transaction:You can easily test this with "yum info updates", and see if the "excludes" are being read in (i.e., that message will be output). If they are being read in, then /etc/yum.conf is OK. Note that I am also using the yum-priorities plug-in to protect my key repos from being trumped by other "3rd-party" repos.

Regards,
V