[PlanetCCRMA] Re: conflict libasound installing ccrma on FC2

Fernando Lopez-Lezcano nando@ccrma.Stanford.EDU
Mon Apr 18 18:06:01 2005


On Mon, 2005-04-18 at 17:41, Axel Thimm wrote:
> On Mon, Apr 18, 2005 at 05:01:23PM -0700, Fernando Lopez-Lezcano wrote:
> > On Mon, 2005-04-18 at 15:13, Koen Maes wrote:
> > > When installing i ran into the following problem on my Fedora Core 2 :
> > >         file /usr/lib/libasound.so.2.0.0 from install of 
> > > alsa-lib-1.0.9-0.1.rc1.rhfc2.ccrma conflicts with file from package 
> > > libasound2-1.0.8-18.rhfc2.at
> > > 
> > > But querying for dependencies for  gives me  a huge list of packages 
> > > that are dependent...
> > > Any advice how to go from here without reinstalling everything
> > 
> > These are the atrpms packages that regretfully choose to rename packages
> > that come with fedora to a different name (and different from all other
> > repositories as well). 
> 
> It's the future! :)

But we are now, regretfully. 

> Seriously, I have had too many instances, where multiple different
> major versions of libraries were needed. It does pay of to have a
> standard to name the shared libraries' packages, and lately even
> fedora devels are open to such a thing (I think the latest discussion
> was on fedora-packaging).
> 
> There is a conflict in this policy: ATrpms is known to mix with many
> different repos and is in fact trying to coordinate
> compatibility. 

??

> This forward/backward compatibility idiom comes with
> the cost that upgrading away from it confuses apt and yum (but not
> smart!).

I'm not arguing the same thing over and over yet again. "alsa-lib" is a
core package, part of Fedora Core / RedHat. It should _NOT_ be renamed
by third party repositories, period. You are not going to help bring the
future by willfully creating incompatibilities now, with Fedora Core and
will all the other repositories that I know that package alsa-lib. 

> So it's a mixed lack-of-standards and depsolvers-inability issue.

Yes and no. The issue would not exist in the first place if you did not
insist on renaming them. 

> > Check what you have installed (just to see if you also have
> > libasound2-devel or whatever):
> >   rpm -q -a | grep libasound2
> > Then erase them (the hard way):
> >   rpm -e --nodeps libasound2 
> > Then let apt "fix" the resulting mess:
> >   apt-get -f install
> > 
> > That should bring in the Planet CCRMA pacakges that are needed (alsa-lib
> > and perhaps alsa-lib-devel)
> 
> That's a very old bug I had forgotten about:
> 
> http://bugzilla.atrpms.net/show_bug.cgi?id=166
> 
> Any chance your trip is over? ;)

The obsoletes recently made it to the "planetedge" packages (there was
another similar post not that long ago), they are not yet in
"planetcore" (ie: stable). 

-- Fernando