atrpms, gcc, libtool and what did i do wrong?

[Robert P. J. Day]

  as a followup to the recent flurry of posts regarding third-party
yum repos, here's the situation i'm in right now -- perhaps someone
can explain what i should have done differently.

  on one FC4 box, i had added a number of third-party repos, including
axel thimm's base and updates repos.  because of that, when i did a
"yum update" recently, one of the updates i got was for libtool from
axel's updates repo:

  # rpm -q libtool
  libtool-1.5.18-2.99_11.rhfc4.at

the problem with this libtool update is that it has a dependency
*specifically* of gcc-4.0.0.  at this point, i can no longer do a
regular yum update since the fedora updates-released repo has an
updated gcc-4.0.1-fc4 *and* an updated libtool-1.5.16...

  at this point, yum won't update gcc since the current libtool
(axel's) *absolutely* requires the current gcc-4.0.0, and yum won't
update libtool since it must figure that the current version
(1.5.18...) is newer than fedora's 1.5.16.

  in short, having updated libtool from axel's repo has pretty much
screwed me in terms of doing an unassisted update at this point.
thoughts?

rday

p.s.  the update on a more generic, stock FC4 box works fine since
the version of libtool on *that* system is the regular FC version,
hence yum is happy to update it along with gcc and a bunch of others.