On Sun, Aug 22, 2004 at 11:43:10PM -0500, Manoj Srivastava wrote: > On Mon, 23 Aug 2004 13:03:56 +0900, Horms <[EMAIL PROTECTED]> 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. To clarify the problem there are two source packages, kernel-image-1-i386-2.4.26 and kernel-image-1-i386-2.4.27, each of which provide a number of binary packages. Most of these packages have names of the form kernel-*-2.4.26-1-* and kernel-*-2.4.27-1-*. This works just fine. However, there are some packages of the form kernel-*-2.4-*, for example kernel-image-2.4-386. These latter packages are provided by both source packages, hence the problem. I think that the best way forward is for kernel-image-1-i386-2.4.26 to ommit the kernel-*-2.4-* packages and only provide the kernel-image-1-i386-2.4.26 packages. Leaving kernel-image-1-i386-2.4.27 to provide both the kernel-*-2.4-* and kernel-*-2.4.27-1-* packages. However I am not clear on how to get kpkg to allow me to do this. Would a better sulolution be to just force the kernel-image-1-i386-2.4.26 provided kernel-*-2.4-* packages into the archive somehow? If it helps, you can see a list of packages that are provided by kernel-image-1-i386-2.4.26 at the following URL. The ones that don't contain 2.4.26-1 in the name are the ones that are also provided by the corresponding 2.4.27 package and are the cause of concern. http://debian.vergenet.net/pending/kernel-image-2.4.26-i386-2.4.26/ Thanks -- Horms
