kernel-image or linux-image?

Bug #16447 reported by Ante Karamatić
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
Medium
Ben Collins

Bug Description

Linux images on Ubuntu are called linux-images-_KVERS_. OK. That's fine. But,
kernel-package (make-kpkg) creates kernel-image-_KVERS_. If u apt install
linux-source and run make-kpkg it will create kernel-image-_KVERS_ couse in
/usr/src/linux-source-2.6.10/debian/control there is no linux-image, only
kernel-image.

If u go along with kernel-image, and build modules they will depend on
kernel-image-_KVERS_. OK. No problem. But sl-modem-daemon depends on
linux-image-2.6. So it will try to download linux-image-2.6.10-5. So now, i
should have kernel-image (kernel i would like to use) and linux-image from
Ubuntu (just to satisfy sl-modem-daemon package).

This would be avoided if make-kpkg would create linux-image package. So, if I
change debian/control in linux-source to create linux-image and build kernel,
make-kpkg would create linux-package-_KVERS_ package. Great. But, wait. Now
sl-modem-source would't compile (if I use make-kpkg modules) couse it depends on
kernel-image package.

In the end, I needed to change debian/control in linux-source (rename every
"kernel-" with "linux-") and in sl-modem-source (same rename).

There is no patch, couse I don't know how many packages are broken this way.

Debian calls his kernel images packages as kernel-image. There are to solutions.
One is to rename and change all kernel packages to be called as:

kenel-image
kernel-source
kernel-doc etc.

or, fix every debian/control which is borken. I don't know how many broken
packages there is. sl-modem-source and linux-source* are just tip od the
iceberg, I think.

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

As explained in the make-kpkg documentation you need to set
the env variable STEM to set linux- or kernel-

Revision history for this message
Ante Karamatić (ivoks) wrote :

I know for --stem, but wouldn't it be better if linux-source packages will
create linux-*, and not kernel-, packages by default? It's easy to change this
and makes sense. If Ubuntu has linux-images, why would it's tools create
kernel-images? I could provide patches for sources. They are trivial.

Revision history for this message
Ante Karamatić (ivoks) wrote :

It isn't resolved!

OK. Just try this:

apt-get install linux-source-2.6.10
cd /usr/src
tar xvfj linux-source-2.6.10*tar.bz2
cd linux-source-2.6.10
make-kpkg --stem linux kernel_image

You will get:

dpkg-gencontrol: error: package linux-image-2.6.10 not in control info

And that's right. There is no linux-* in debian/control, only kernel-*.

Revision history for this message
Ben Collins (ben-collins) wrote :

This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.

This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.

If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).

Thanks for your help.

Revision history for this message
Ben Collins (ben-collins) wrote :

Fairly sure this is addressed with newer kernel-package/kernel-wedge packages.

Revision history for this message
Anca Emanuel (anca-emanuel) wrote :

dpkg-gencontrol: error: package linux-image-2.6.36-rc4+ not in control info
make[2]: *** [debian/stamp/binary/linux-image-2.6.36-rc4+] Error 255
make[2]: Leaving directory `/home/username/linux-2.6'
make[1]: *** [debian/stamp/binary/pre-linux-image-2.6.36-rc4+] Error 2
make[1]: Leaving directory `/home/username/linux-2.6'
make: *** [kernel_image] Error 2

Revision history for this message
Daniel J Blueman (danielblueman) wrote :

I experience this also, and use this patch to workaround the '+' symbol introduced into the kernel version string due to git detecting source changes:

--- /usr/share/kernel-package/ruleset/kernel_version.mk.orig 2008-05-02 07:06:28.000000000 +0200
+++ /usr/share/kernel-package/ruleset/kernel_version.mk 2010-07-08 00:02:45.316669641 +0200
@@ -62,7 +62,7 @@
  @echo "$(strip $(EXTRAVERSION))"

 debian_LOCALVERSION:
- @echo $(if $(strip $(localver-full)),"$(strip $(localver-full))", "$(strip $(LOCALVERSION))")
+ @./scripts/setlocalversion

 debian_TOPDIR:
 # 2.6 kernels declared TOPDIR obsolete, so use srctree if it exists

Revision history for this message
sam tygier (samtygier) wrote :

@ daniel.

I filed a new bug for the issue with a modified git builds. Bug #650986

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.