Packaging system and non-Debian packages [was: Re: lm_sensors]
On Thu, Feb 06, 2003 at 08:01:25PM -0700, Hugo Graumann wrote:
> * On Fri, Feb 07, 2003 at 12:00:17AM +0100, mess-mate (messmate@tiscali.fr) wrote:
> > Sorry, this error messages appaers on the install of this i2c package :
> > dpkg: dependency problems prevent configuration of i2c-2.4.20:
> > i2c-2.4.20 depends on kernel-image-2.4.20; however:
> > Package kernel-image-2.4.20 is not installed.
> > dpkg: error processing i2c-2.4.20 (--install):
> > dependency problems - leaving unconfigured
> > Errors were encountered while processing:
> > i2c-2.4.20
> > ?? This kernel is installed ! Compiled and installed by myself.
> > (with the old method)
> > What has I do other ?
> > mess-mate
>
> If by old method you mean "make bzimage" etc, then I bet that is
> why the package wont install. Looks like the i2c package wants to
> see a 2.4.20 kernel installed as a Debian package before it is
> satisfied. So even though you have a running 2.4.20 kernel, the
> Debian package system doesn't know about it. I guess one fix
> would be to make a kernel the Debian way with make-kpkg and
> then install that kernel package (this is sort of implied in step 0).
> After this you have a 2.4.20 kernel and the packaging system knows about
> it as well so the dependencies will be correct.
It would be useful to know how to do this in the more general case,
where there isn't a convenient command like make-kpkg.
My particular case is X 4.2.0, which I downloaded the source of and
compiled for slink, then for woody when I upgraded. But of course
woody's packaging system doesn't realise it's there and keeps wanting
to pull in bits of the woody X.
No doubt the "Debian way" to fix this would be to get the X 4.2.1
source package from testing and build that. But I'm on dialup, and the
idea of re-downloading 100Mb or so compares poorly with that of
editing a few files to achieve the same result.
Pigeon
Reply to: