Re: [linux-audio-user] CCRMA and yum

Quoting Fernando Lopez-Lezcano <nando@email-addr-hidden>:

> On Thu, 2006-02-16 at 16:47 -0800, thewade wrote:
>> Quoting Fernando Lopez-Lezcano <nando@email-addr-hidden>:
>> [MUNCH]
>> >> > I still don't understand completely. Do you have xine-lib installed
>> >> > already?
>> >>
>> >> I have the livna xine-lib installed (so I can watch DVD's using xine):
>> >> xine-lib-1.1.1-0.lvn.3.4
>> >>
>> >>
>> >> > Or is that what is triggering the problem when you try to
>> >> > install it?
>> >>
>> >> That is where I am confused. I just run "yum update" and it dies on
>> >> libavcodec and faad2.
>> >
>> > I'm confused as well. I'm not used to yum so I don't really know how to
>> > troubleshoot this. I can't make up my mind on which side is breaking
>> > things.
>> >
>> > Try removing the Planet CCRMA urls from the yum configuration file, and
>> > then doing a "yum update".
>>
>> I relocated my /etc/yum.repos.d/planetCCRMA.repo file and ran yum -y
>> update and a few things updated but nothing having to do with faad
>> ffmpeg. Everything worked fine. Then I moved the file back and ran
>> update again and I got the fault with libavcodec and faad2 again.
>> I will attach the whole of the yum execution below.
>> Thanks again for helping me out on this.
>> -thewade
>>
>> yum -y update
>> Setting up Update Process
>> Setting up repositories
>> planetccrma 100% |=========================| 951 B 00:00
>> os 100% |=========================| 951 B 00:00
>> planetcore 100% |=========================| 951 B 00:00
>> planetedge 100% |=========================| 951 B 00:00
>> updates 100% |=========================| 951 B 00:00
>> Reading repository metadata in from local files
>> primary.xml.gz 100% |=========================| 110 kB 00:00
>> planetccrm: ################################################## 400/400
>> Added 3 new packages, deleted 0 old in 1.22 seconds
>> Resolving Dependencies
>> --> Populating transaction set with selected packages. Please wait.
>> ---> Package pam.i386 0:0.79-9.6.2.rhfc4.ccrma set to be updated
>> ---> Package alsa-lib.i386 0:1.0.10-3.2.rhfc4.ccrma set to be updated
>> ---> Package pam-devel.i386 0:0.79-9.6.2.rhfc4.ccrma set to be updated
>> ---> Package wxGTK-common.i386 0:2.4.2-12.1.rhfc4.ccrma set to be updated
>> ---> Package imlib2.i386 0:1.2.0-8.fc4.rhfc4.ccrma set to be updated
>> ---> Package wxGTK2.i386 0:2.4.2-12.1.rhfc4.ccrma set to be updated
>> ---> Package libid3tag.i386 0:0.15.1b-3.rhfc4.ccrma set to be updated
>
>> ---> Package faad2.i386 0:2.0-1.rhfc4.ccrma set to be updated
>> ---> Package ffmpeg.i386 0:0.4.9-0.1.20050427.rhfc4.ccrma set to be updated
>
> These two are probably the culprit, conflicting versions between livna
> and Planet CCRMA.
>
> I wonder what would happen if you exclude them from the update.
> Something else will probably not be able to be updated. You could use
> the "--exclude" keyword in yum, I guess.
>
>> ---> Package kino.i386 0:0.7.6-1.rhfc4.ccrma set to be updated
>> ---> Package alsa-lib-devel.i386 0:1.0.10-3.2.rhfc4.ccrma set to be updated
>> ---> Package audacity.i386 0:1.2.4b-1.rhfc4.ccrma set to be updated
>> ---> Package a52dec.i386 0:0.7.4-1.rhfc4.ccrma set to be updated
>> ---> Package libmad.i386 0:0.15.1b-3.rhfc4.ccrma set to be updated
>> ---> Package alsa-utils.i386 0:1.0.10-1.rhfc4.ccrma set to be updated
>> ---> Package vcdimager.i386 0:0.7.23-2.rhfc4.ccrma set to be updated
>> ---> Package libsndfile.i386 0:1.0.11-1.rhfc4.ccrma set to be updated
>> ---> Package libquicktime.i586 0:0.9.7-1.rhfc4.ccrma set to be updated
>> --> Running transaction check
>> --> Processing Dependency: libavcodec.so.51 for package: xine-lib
>> --> Processing Dependency: libpostproc.so.0 for package: ffmpeg
>> --> Processing Dependency: alsa-driver for package: alsa-lib
>> --> Processing Dependency: faad2 = 0:2.0-0.lvn.5.4 for package: xmms-faad2
>> --> Restarting Dependency Resolution with new changes.
>> --> Populating transaction set with selected packages. Please wait.
>
>> ---> Package libpostproc.i386 0:0.4.9-0.1.20050427.rhfc4.ccrma set to
>> be updated
>
> The one above may also be a source of problems...
>
>> ---> Package alsa-driver.i686 0:1.0.10-1.rhfc4.ccrma set to be updated
>> --> Running transaction check
>> --> Processing Dependency: libavcodec.so.51 for package: xine-lib
>> --> Processing Dependency: kernel-module-alsa = 1.0.10-1.rhfc4.ccrma
>> for package: alsa-driver
>> --> Processing Dependency: faad2 = 0:2.0-0.lvn.5.4 for package: xmms-faad2
>
> Looks like xxms-faad2 is driving the update of faad2?
>
>> --> Restarting Dependency Resolution with new changes.
>> --> Populating transaction set with selected packages. Please wait.
>> ---> Package kernel-module-alsa-2.6.14-0.10.rrt.rhfc4.ccrma.i686
>> 0:1.0.10-1.rhfc4.ccrma set to be updated
>> --> Running transaction check
>> --> Processing Dependency: libavcodec.so.51 for package: xine-lib
>> --> Processing Dependency: kernel-2.6.14-0.10.rrt.rhfc4.ccrma-i686 for
>> package: kernel-module-alsa-2.6.14-0.10.rrt.rhfc4.ccrma
>> --> Processing Dependency: faad2 = 0:2.0-0.lvn.5.4 for package: xmms-faad2
>> --> Processing Dependency: kernel = 2.6.14-0.10.rrt.rhfc4.ccrma for
>> package: kernel-module-alsa-2.6.14-0.10.rrt.rhfc4.ccrma
>> --> Restarting Dependency Resolution with new changes.
>> --> Populating transaction set with selected packages. Please wait.
>> ---> Package kernel.i686 0:2.6.14-0.10.rrt.rhfc4.ccrma set to be installed
>> --> Running transaction check
>> --> Processing Dependency: libavcodec.so.51 for package: xine-lib
>> --> Processing Dependency: faad2 = 0:2.0-0.lvn.5.4 for package: xmms-faad2
>> --> Finished Dependency Resolution
>> Error: Missing Dependency: libavcodec.so.51 is needed by package xine-lib
>> Error: Missing Dependency: faad2 = 0:2.0-0.lvn.5.4 is needed by package
>> xmms-faad2
>
> You could try yum with --exclude ffmpeg --exclude faad2 to see what
> happens.

Well, that update worked!
So just so I know what is going on:
(1)Livna's versions of ffmpeg and faad2 are newer then ccrma's, but for
some reason yum thinks ccrma's are newer...? Or are ccrma's files newer
and livna can only handle an exact version number...?
(2)Do you think this will this affect pd-Gem at all?

Thanks again for all the help! I am excited to try this new kernel out,
but now I must rebuild nDisWrapper (which doesn't work for me yet
anyway) and ati-fglrx (which hasn't visibly improved video performance
for me yet).

I will now add "options realtime gid=xxx" (right? Oh, I'll figure it
out... you've already helped me enough!)

Thanks again!
-thewade
Received on Sat Feb 18 04:15:07 2006