On Sun, Jun 29, 2008 at 18:31:35 -0700, stan <goedigi89__e(a)cox.net&gt; wrote: You don't need to do that any more. Yum will skip the broken packages. (I don't think skip_broken is the default, so you probably want to add that option to /etc/yum.conf .) Things should be much better now. (THe change happened during the F9 rawhide period.) Only some file conflicts which are detected after the packages to be updated are selected, cause all updates to fail.

Luis Orlindo Tedeschi wrote: It is trivial to do the following. (as root) yum list updates > updates Edit updates to leave only the packages. Put #! /bin/bash at the top. Replace the version of the package with *, and add yum -y update in front of each package. In vim, recording a macro to do this takes less than a minute. Save the file. Change the mode on updates to executable chmod +x updates ./updates This is a little inefficient as it runs yum on individual packages that have been pulled in for dependencies already, but it will update everything except the invalid package. When I was using rawhide I automated this with scripts and python programs (well, more sophisticated than this). There are almost always dependency errors in rawhide, so you would never get any updates if you didn't do something like this.

On Sun, 2008-06-29 at 18:14 -0500, Luis Orlindo Tedeschi wrote: 1) This has been reported several times. Apparently an update is in the process of being pushed to the mirrors, so be patient. 2) Please don't hijack threads. You sent your message by replying to a completely unrelated one and changing the subject. This is called hijacking and is extremely annoying because it messes up the order of list messages in many common mail clients. It's trivial to send a new message without doing this, so please take note. poc