[PlanetCCRMA] dependancies
Julius Smith
jos@w3k.org
Mon Oct 27 11:46:34 2003
Hi Fernando,
Thanks for your reply (and welcome back!).
Below is what happens when I follow the instructions in the kernel install
page and then the change log. In both cases, I cannot seem to escape
dependency on the patched Red Hat kernel (2.4.20), which is too old for me
to use, even though I am trying to install the latest Plant CCRMA kernel
(2.4.22):
# apt-get -o RPM::Install-Options::=--oldpackage install planetccrma-core
Reading Package Lists... Done
Building Dependency Tree... Done
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
alsa-kernel-2.4.20-20.1.caps.rh90: Depends: kernel-version (=
2.4.20-20.1.caps.rh90)
Depends: kernel-version-arch (=
2.4.20-20.1.caps.rh90-i686)
planetccrma-core: Depends: kernel-version-arch (= 2.4.22-6.ll.rh90-i686)
Depends: alsa-kernel-arch-2.4.22-6.ll.rh90 (=
0.9.6-2.cvs.rh90-i686)
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or
specify a solution).
# apt-get -f install
Reading Package Lists... Done
Building Dependency Tree... Done
Correcting dependencies... Done
The following extra packages will be installed:
kernel#2.4.20-20.1.caps.rh90
The following NEW packages will be installed:
kernel#2.4.20-20.1.caps.rh90
0 packages upgraded, 1 newly installed, 0 removed and 20 not upgraded.
Need to get 0B/14.0MB of archives.
After unpacking 32.2MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Executing RPM (-ivh)...
Preparing... ########################################### [100%]
package kernel-2.4.21-1.ll.acpi (which is newer than
kernel-2.4.20-20.1.caps.rh90) is already installed
E: Sub-process /bin/rpm returned an error code (1)
[Next, I read the change log and learned that I could comment out the
"core" line in /etc/apt/sources.list to avoid updating the kernel. Trying
this, the behavior is as follows. It appears there must an explicit
dependency on a specific version of the alsa-kernel package at a higher
level (outside of the core packages).]
# apt-get update
Get:1 http://www-ccrma.stanford.edu redhat/9/en/i386 release [1769B]
Get:2 http://www-ccrma.stanford.edu redhat/all/en/i386 release [510B]
Fetched 2279B in 0s (9839B/s)
Hit http://www-ccrma.stanford.edu redhat/9/en/i386/os pkglist
Hit http://www-ccrma.stanford.edu redhat/9/en/i386/os release
Hit http://www-ccrma.stanford.edu redhat/9/en/i386/updates pkglist
Hit http://www-ccrma.stanford.edu redhat/9/en/i386/updates release
Hit http://www-ccrma.stanford.edu redhat/all/en/i386/planetccrma pkglist
Hit http://www-ccrma.stanford.edu redhat/all/en/i386/planetccrma release
Hit http://www-ccrma.stanford.edu redhat/9/en/i386/planetccrma pkglist
Hit http://www-ccrma.stanford.edu redhat/9/en/i386/planetccrma release
Reading Package Lists... Done
Building Dependency Tree... Done
# apt-get dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
You might want to run `apt-get -f install' to correct these.
The following packages have unmet dependencies:
alsa-kernel-2.4.20-20.1.caps.rh90: Depends: kernel-version (=
2.4.20-20.1.caps.rh90)
Depends: kernel-version-arch (=
2.4.20-20.1.caps.rh90-i686)
E: Unmet dependencies. Try using -f.
# apt-get -f install
Reading Package Lists... Done
Building Dependency Tree... Done
Correcting dependencies... failed.
The following packages have unmet dependencies:
alsa-kernel-2.4.20-20.1.caps.rh90: Depends: kernel-version (=
2.4.20-20.1.caps.rh90)
Depends: kernel-version-arch (=
2.4.20-20.1.caps.rh90-i686)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused
by held packages.
E: Unable to correct dependencies
Do you think it might work to temporarily install kernel 2.4.20 using the
--force option of RPM, followed by an installation of the Planet CCRMA
kernel (2.4.22)? Could anything get broken by forcing a kernel installation?
Thanks,
Julius
At 10:10 AM 10/27/2003 -0800, Fernando Pablo Lopez-Lezcano wrote:
> > I have a dependency snafu that perhaps someone can enlighten me about.
> >
> > (1) I have to run kernel#2.4.21 or later to get support for my networking
> > chip.
> > (2) I cannot install Planet CCRMA stuff because I don't have kernel#2.4.20.
> > (3) 'apt-get -f install' cannot fix the dependencies because kernel#2.4.20
> > will not install, because kernel#2.4.21 is recognized as being newer and
> > already installed.
> >
> > Does anyone know of a clean way out of this mess?
> >
> > I do not understand why kernel dependencies fail when the installed kernel
> > version is obviously later than the required version.
> >
> > Any advice appreciated.
>
>You have to use a command line option to apt-get to enable rpm to
>install kernels "older" than the latest one installed. Otherwise rpm
>complains and the kernel is not installed. Most probably this is the
>result of doing a "dist-upgrade" when you do not have the latest kernel
>installed.
>
>"Apt-get dist-upgrade" is not a good way to upgrade the kernel and alsa
>driver (and I have not found a good solution to this problem yet).
>Follow the instructions in the kernel install page (or in the changelog,
>search for the latest kernel "news"). The apt-get incantation outlined
>there will install the proper (latest) kernel. After that a
>"dist-upgrade" will work fine(*).
>
>-- Fernando
>
>(*) Why does it NOT work the first time? There are two kernels available
>to resolve the alsa dependencies (ie: alsa-lib that needs alsa-driver
>that need alsa-kernel that needs a matching kernel). Dist-upgrade picks
>up the first it finds. Regretfully that is the one for the RedHat kernel
>with capabilities enabled. Which is "older" than the latest Planet CCRMA
>kernel you already have installed. Apt does not know this, but rpm will
>not install an older package without a command line override. So apt
>tries to do the right thing, rpm barfs and the install fails. This only
>happens on things like kernels, where you can have more than one package
>of the same name ("kernel-*") installed.