nasty hack around broken yum archive dependancy blockages

[Sandy Pond]

On Mon, 2004-03-15 at 21:27 -0800, Tom Mitchell wrote:
> On Mon, Mar 15, 2004 at 09:42:14AM -0500, Thomas J. Baker wrote:
> > Reply-To: For testers of Fedora Core development releases <fedora-test-list at redhat.com>
> > 
> > On Mon, 2004-03-15 at 01:29, Michael Wiktowy wrote:
> > > > So just to be sure I understand. You take the list of updateable pkgs,
> > > > and you iterate over each one until you can't update anything completely
> > > > anymore. Is that right?
> > > >
> > > 
> > > Also, I couldn't figure out how to make yum stop
> > > "Gathering header information file(s) from server(s)"
> > > every single time it is run (to iterate through that list faster).
> ....
> > The way my rawhide mirror works (mirror of a mirror), it would be nice
> > if yum had a --update-what-you-can option. After a normal pass, it would
> > just --exclude 
> 
> In a pinch do a "up2date-nox --list" or a "yum list updates" and save the output
> to a file.  Then edit that in to a script that updates one or two or
> three packages at a time.  The packages that can be installed will
> be installed.  Then a new list can be generated and turned into a script.

The easiest way is to get familiar with "yum provides <file>" and "yum
list <pkg>".  Sometimes you'll want to exclude ("yum --exclude=<pkg>
update") a package from update, other times you'll want to remove the
offending package ("rpm -e <pkg>").  There's no easy logic to
automate.