[PlanetCCRMA] Building Alsa RPMs...

Mark Knecht markknecht@attbi.com
Fri Jan 24 17:25:02 2003

OK, a small problem. On 


step 3, I build the first RPM using the rpm -bb command. Then before I
install it I decide to look at ../RPMS/i386 and find that nothing is
there. I look around and find the RPM just got placed in i686. 

The command

rpm -Uvh ../RPMS/i386/alsa-driver*0.9.0-44.i386.rpm 

isn't going to work.

I think something is wrong with the architecture part of this thing.

I didn't get an answer to this question earlier. At the step where I do
apt-get install kernel-source, I stated that I got duplications

[root@Godzilla root]# apt-get install kernel-source
Reading Package Lists... Done
Collecting File Provides... Done
Building Dependency Tree... Done
Package kernel-source is a virtual package provided by:
  kernel-source#2.4.19-1.ll@i386 2.4.19-1.ll
  kernel-source#2.4.19-1.ll@i386 2.4.19-1.ll
  kernel-source#2.4.18-18.7.x@i386 2.4.18-18.7.x
  kernel-source#2.4.18-18.7.x@i386 2.4.18-18.7.x
  kernel-source#2.4.18-3@i386 2.4.18-3
  kernel-source#2.4.18-3@i386 2.4.18-3
You should explicitly select one to install.
E: Package kernel-source has no installation candidate
[root@Godzilla root]#

This doesn't look right to me. Why are there two @i386 entries for each?

Anyway, why is the rpm in the i686 directory? What am I doing wrong?


On Sat, 2003-01-25 at 00:12, Fernando Pablo Lopez-Lezcano wrote:
> > > _After_ you have built all of them, yes, you can install them with one
> > > command. But for building each of the pieces you have to have the
> > > previous one installed. 
> > > 
> > 
> > Sorry, I'm stuck on the word 'installed'.
> > 
> > I 'installed' the 0.9.0-44  RPM that you made and provided via the
> > Planet a few days ago. However, it appears that these instructions ask
> > me to 'install' it a second time:
> Awh, the "obvious" things. You should change the version number of the
> rpms you are building so that they do not conflict with the ones that
> are already installed. You do that by changing the "release" tag in each
> spec file (to, for example, "44.1") and then rebuilding / reinstalling.
> Each time you want to build a "new" version up the release number. 
> OR: you could rpm -e --nodeps all the relevant packages and reinstall,
> but on the first try I would modify the version number so that it does
> not have the same number as the planet ccrma rpms. 
> -- Fernando
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma