[PlanetCCRMA] Alsa driver not updateable

[ken]

Fernando
The source and the debug repositories were not enabled. Should I enable the 
debug repository?
Ken

On Sunday 24 September 2006 22:38, Fernando Lopez-Lezcano wrote:
> On Sun, 2006-09-24 at 22:11 -0400, ken wrote:
> > I checked the planet web page and verified that I had done them.
> >
> > The last thing that happened was strange. Why does it say no match for
> > argument: planetccrma-core?
> >
> > bash-3.1$ su
> > Password:
> > [root@localhost ken]# yum install planetccrma-core
> > Setting up Install Process
> > Setting up repositories
> > core                                                                
> > [1/3] updates                                                            
> >  [2/3] extras                                                            
> >   [3/3] Reading repository metadata in from local files
> > Parsing package install arguments
> > No Match for argument: planetccrma-core
> > Nothing to do
> > [root@localhost ken]#
>
> Weird, it would seem that you don't have the planetccrma repositories
> enabled in yum, check /etc/yum.repo.d/*...
>
> -- Fernando
>
> > On Wednesday 20 September 2006 21:19, Fernando Lopez-Lezcano wrote:
> > > On Wed, 2006-09-20 at 19:17 -0400, ken wrote:
> > > > Does this answer your question about the fc5 kernel and alsa driver
> > > > installation.
> > > >
> > > > [root@localhost ken]# rpm -e alsa-driver-1.0.9-0.1.rc1.rhfc3.ccrma
> > > > error: Failed dependencies:
> > > >         alsa-driver = 1.0.9-0.1.rc1.rhfc3.ccrma is needed by
> > > > (installed) planetccrma-core-2005.03.22-1.rhfc3.ccrma.i686
> > > >
> > > > However the first line of the kernel startup log says:
> > > > Linux version 2.6.17-1.2174_FC5
> > > > (brewbuilder@hs20-bc2-3.build.redhat.com) (gcc version 4.1.1 20060525
> > > > (Red Hat 4.1.1-1)) #1 Tue Aug 8 15:30:55 EDT 2006 What do I do next?
> > >
> > > You are booting the latest Fedora Core kernel (no harm in that).
> > >
> > > Have you followed the instructions on installing the planetcore
> > > components on fc5? That's not going to happen magically after you
> > > upgrade. Go to the web page and see what needs to be done for
> > > installing fc5 - yum update, yum configuration, etc, etc.
> > >
> > > You may hit a problem when trying to install the kernel (yum may refuse
> > > to install the kernel because you have a newer one, damn yum...).
> > >
> > > After installing the newer yum and configuring for the Planet CCRMA
> > > repositoies you could try:
> > >
> > >   yum install planetccrma-core
> > >
> > > -- Fernando
> > >
> > > > On Wednesday 20 September 2006 13:50, Fernando Lopez-Lezcano wrote:
> > > > > On Wed, 2006-09-20 at 11:18 -0400, ken wrote:
> > > > > > Which command should I use to remove the alsa packages? I still
> > > > > > have synaptic on my system and when I tried to use it to remove
> > > > > > the alsa-driver it threatened to remove a whole lot of other
> > > > > > things?
> > > > >
> > > > > Just try "rpm -e package_name".
> > > > > Do you have the new fc5 versions of the kernel and alsa installed?
> > > > >
> > > > > It appears you have not done that as you still have the fc3
> > > > > versions of alsa-lib, alsa-tools, etc, etc (I think you will not be
> > > > > able to erase the kernel-module-alsa packages until you install the
> > > > > newer kernel and alsa packages).
> > > > >
> > > > > -- Fernando
> > > > >
> > > > > > On Tuesday 19 September 2006 13:10, Fernando Lopez-Lezcano wrote:
> > > > > > > On Mon, 2006-09-18 at 22:33 -0400, ken wrote:
> > > > > > > > I see the following list:
> > > > > > >
> > > > > > > Wow, a lot of stuff left over...
> > > > > > >
> > > > > > > > amsynth-1.0.0-3.rhfc3.ccrma
> > > > > > > > libid3tag-0.15.1b-3.rhfc3.ccrma
> > > > > > > > xmms-jack-0.13-2.rhfc3.ccrma
> > > > > > > > alsa-driver-1.0.9-0.1.rc1.rhfc3.ccrma
> > > > > > > > jamin-0.95.0-1.rhfc3.ccrma
> > > > > > > > clthreads-1.0.2-1.rhfc3.ccrma
> > > > > > > > libfluidsynth-1.0.5-1.rhfc3.ccrma
> > > > > > > > alsa-tools-1.0.9-0.1.rc1.rhfc3.ccrma
> > > > > > > > gtkmm-1.2.10-1.rhfc3.ccrma
> > > > > > > > jackeq-0.4.0-1.rhfc3.ccrma
> > > > > > > > clalsadrv-1.0.1-1.rhfc3.ccrma
> > > > > > > > aeolus-0.3.1-1.rhfc3.ccrma
> > > > > > > > muse-0.7.1-1.rhfc3.ccrma
> > > > > > > > gtkmm2-2.2.12-1.rhfc3.ccrma
> > > > > > > > jackmix-0.0.3-1.rhfc3.ccrma
> > > > > > > > kernel-module-alsa-2.6.10-2.1.ll.rhfc3.ccrma-1.0.7-1.cvs.rhfc
> > > > > > > >3.cc rma libmad-0.15.1b-3.rhfc3.ccrma
> > > > > > > > tse3-0.2.7-1.rhfc3.ccrma
> > > > > > > > ladcca-0.4.0-2.rhfc3.ccrma
> > > > > > > > swami-0.9.2-2.rhfc3.ccrma
> > > > > > > > gamix-1.99.p14-2.rhfc3.ccrma
> > > > > > > > jaaa-0.1.2-1.rhfc3.ccrma
> > > > > > > > libsigc++10-1.0.4-1.rhfc3.ccrma
> > > > > > > > kernel-module-alsa-2.6.10-2.1.ll.rhfc3.ccrma-1.0.8-3.rhfc3.cc
> > > > > > > >rma alsa-firmware-1.0.8-1.rhfc3.ccrma
> > > > > > > > planetccrma-core-2005.03.22-1.rhfc3.ccrma
> > > > > > > > ec-fonts-mftraced-1.0.7-1.rhfc3.ccrma
> > > > > > > > clxclient-1.0.1-1.rhfc3.ccrma
> > > > > > > > alsa-oss-1.0.9-0.1.rc1.rhfc3.ccrma
> > > > > > > > noteedit-2.7.4-1.rhfc3.ccrma
> > > > > > > > rtirq-20050415-1.rhfc3.ccrma
> > > > > > > > seq24-0.6.3-1.rhfc3.ccrma
> > > > > > > > ams-1.8.7-2.rhfc3.ccrma
> > > > > > > > kernel-module-alsa-2.6.10-0.4.rdt.rhfc3.ccrma-1.0.8-3.rhfc3.c
> > > > > > > >crma ardour-0.99-1.rhfc3.ccrma
> > > > > > > > kernel-module-alsa-2.6.10-2.1.ll.rhfc3.ccrma-1.0.9-0.1.rc1.rh
> > > > > > > >fc3. ccrm a fox-1.2.11-1.rhfc3.ccrma
> > > > > > > > rtload-0.0.2-1.rhfc3.ccrma
> > > > > > > > kmidimon-0.3-1.rhfc3.ccrma
> > > > > > >
> > > > > > > A good start would be to remove the kernel-module-alsa-*
> > > > > > > packages, those are leftover from the older kernels (which
> > > > > > > appear to have been removed by the upgrade process - which is
> > > > > > > not very smart, of course).
> > > > > > >
> > > > > > > Maybe that will enable you to get more things upgraded by a
> > > > > > > "yum upgrade".
> > > > > > >
> > > > > > > With apt-get I would have suggested starting with a "apt-get
> > > > > > > check" but I don't know what the equivalent command with yum
> > > > > > > would be (apt-get check checks the consistency of dependencies
> > > > > > > and reports any problems).
> > > > > > >
> > > > > > > -- Fernando
> > > > > > >
> > > > > > > > On Sunday 17 September 2006 23:32, Fernando Lopez-Lezcano 
wrote:
> > > > > > > > > On Sun, 2006-09-17 at 20:58 -0400, ken wrote:
> > > > > > > > > > I have upgraded from FC3 to FC5 and like some others have
> > > > > > > > > > not had the ALSA drivers updated. The yum program or the
> > > > > > > > > > software update program tells me I need
> > > > > > > > > > 1.0.9-0.1.rc1.rhfc3.ccrma. Where do I find this and how
> > > > > > > > > > can an FC3 package co-exist with my system which is now
> > > > > > > > > > FC5?
> > > > > > > > >
> > > > > > > > > That's probably because you still have some package
> > > > > > > > > installed that requires that particular version of alsa. Do
> > > > > > > > > this:
> > > > > > > > >
> > > > > > > > >   rpm -q -a |grep rhfc3
> > > > > > > > >
> > > > > > > > > to see a list of "old" packages that should not be
> > > > > > > > > installed in fc5... What do you see?
> > >
> > > _______________________________________________
> > > PlanetCCRMA mailing list
> > > PlanetCCRMA@ccrma.stanford.edu
> > > http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> >
> > _______________________________________________
> > PlanetCCRMA mailing list
> > PlanetCCRMA@ccrma.stanford.edu
> > http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma