RPM dependencies kicking my a**

[David Kramer]

Matthew Gillen wrote:
> David Kramer wrote:
>> David Kramer wrote:
>>
>>> What should I do?  For now, I'm disabling livna, and removing
>>> conflicting packages so the atrpms versions will get installed, but I
>>> don't have a good enough feel for the "culture and mythology" of each
>>> repo to know if that's a good idea or not.
>>>
>>> Thanks.
>> This eventually got me updated, but I would still like to hear if this
>> is SOP.
> 
> It's always something of a crap shoot when you use more than one non-official
> repo, especially when it comes to mplayer-related packages.

Yeah. When I was using SUSE, there was their own repository, and some
specific things I got from packman, which was well-designed to not
conflict.

I should probably ask yum to tell me the list of all packages in each
repo, then diff them, to see if there's anything in livna I need that's
not in atrpms.

> If you know exactly what you want from one repo (for example, you want Livna's
> nvidia/ati kernel drivers, but want all the video-codec stuff from the other
> repo), the best long term solution is to tell yum that by adding an
> "includepkgs" line to the livna.repo file ("includepkgs" specifies that only
> those packages listed should be considered for updates/install)

Excellent.  I missed that in the docs.  Thanks.

> By the way, if you want to remove Livna's version of something, "yum erase
> <packagename>" will remove a package and anything that depends on it.  Saves
> some time. :-)

Also good to know.  I had to use the evil "rpm -e --nodeps" to do what I
did.

Once I get MythTV working ot the extent it was before (somehow ivtv
broke during the ordeal last night), I'm gonna hafta do some package
switchovers to get as much as possible on one third-party repo.

Thanks again for the great info and support.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.