[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kernel-package Help



On Mon, Aug 23, 2004 at 02:59:17PM +0900, Horms wrote:
> On Sun, Aug 22, 2004 at 11:43:10PM -0500, Manoj Srivastava wrote:
> > On Mon, 23 Aug 2004 13:03:56 +0900, Horms  <horms@debian.org> said: 
> > 
> > > This is to get around the problem where these packages are rejected
> > > as their version, 2.4.26-6 is less than the version currently in
> > > debian provided by kernel-image-1-i386-2.4.27, that is version
> > > 2.4.27-X. This will allow 2.4.26-6 to be uploaded.
> > 
> > 	I guess I haven't been following along too closely.  The idea
> >  behind kernel image naming used to be that version 2.4.26 was a
> >  different package from version 2.4.27, and thus was independent;
> >  uploading 2.4.27 would in no way impact 2.4.26 uploads.  Has this
> >  been somehow changed?
> > 
> > > However, when I try to built packages thus, the build fails with the
> > > error.
> > 
> > > dpkg-gencontrol: error: package kernel-image-2.4-386 not in control
> > 
> > 	Right. The kernel image name was related to the kernel
> >  version, so that each kernel image package would own the
> >  corresponding /lib/modules/$version dir. The kernel-image name is
> >  really kernel-image-$version$extraversion,  and it owns
> >  /lib/modules/$version$extraversion.
> > 
> > > Does anyone have any suggestions on how to resolve either this error
> > > or the upload problem?
> > 
> > 	Epochs have been created to work around versioning snafus.
> 
> Hi Manoj,
> 
> thanks for your quick response. However, I don't think that using
> an epoch will reslove the problem.

Hi Manoj,

I discussed this a problem with Joshua Kwan and Sven Luther on
#debian-kernel, and on closer examination the problem I was seeing
appears to have been caused by the post-install script and not
kpkg.

-- 
Horms



Reply to: