yum 2.1.13 in updates-testing

[Phil Schaffner]

On Sat, 2005-02-05 at 16:24 +0100, Michael Schwendt wrote:
> On Sat, 5 Feb 2005 09:34:52 -0500, Jeff Spaleta wrote:
> 
> > On Sat, 05 Feb 2005 09:20:06 -0500, Phil Schaffner
> > <P.R.Schaffner at ieee.org> wrote:
> > <snip>
> > >   Update: synaptic.i386 0:0.55.3-2 - extras
> > <snip>
> > > Transaction Check Error:   package apt-0.5.15cnc6-53.4.rhfc3.at (which is newer than apt-0.5.15cnc6-12.r362) is already installed
> > <snip>
> > 
> > Check the requirements of the synaptic yum wants to update
> > check the provides of the apt you currently have installed.
> > you have apt from atrpms installed...  you dont have atrpms in the yum
> > repository information that you loaded....
> > 
> > Looks like a packaging conflict from using multiple repositories to
> > me.  I don't see how this qualifies as a yum problem considering that
> > yum isn't going to downgrade packages as a matter of design.
> 
> synaptic requires libapt-pkg-libc6.3-6.so.0, which is only provided by
> apt-0.5.15cnc6-12.r362 in Phil's configured set of repositories.  yum
> decides to take that one, but then realises that a higher version of apt
> is installed already and does not come from the enabled repositories.
> That's not a conflict, but an inconsistent repository configuration.

Deliberately disabled 3rd party repos to test new yum and new Extras
repo.  Seems yum should ideally notice the conflict in apt versions
earlier in the process, before asking the user to confirm the upgrade
(or should I say downgrade?).  I get the same failure with ATrpms,
FreshRPMS, Dag, NR, NewRPMS, locally-built and Macromedia (my usual
[excessive?] set of 3rd party repos) added to the mix.  Only way to
avoid the conflict/error seems to be to remove Extras - in which case,
result is "No Packages marked for Update/Obsoletion".

Looks like Extras does not play nicely with ATrpms, FreshRPMS, ... any
more than Fedora.US did - or vice versa.  Perhaps the situation will
improve now that Extras is on the Red Hat server.  Otherwise, will just
stick with the "compatible" set of repos plus home-built where required.

Phil