Use bzip2 compression for linux-image-* debs

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

it seems it's already done. At least for Jaunty and Karmic:

file /boot/vmlinuz-2.6.30-8-generic
/boot/vmlinuz-2.6.30-8-generic: Linux kernel x86 boot executable bzImage, version 2.6.30-8-generic (buildd@vernad, RO-rootFS, root_dev 0x801, swap_dev 0x3, Normal VGA
andres@mostro:~$ file /boot/vmlinuz-2.6.28-11-generic
/boot/vmlinuz-2.6.28-11-generic: Linux kernel x86 boot executable bzImage, version 2.6.28-11-generic (buildd@palme, RO-rootFS, root_dev 0x6801, swap_dev 0x3, Normal VGA

not for hardy

file /boot/vmlinuz-2.6.24-22-generic
/boot/vmlinuz-2.6.24-22-generic: Linux kernel x86 boot executable RO-rootFS, root_dev 0x801, swap_dev 0x1, Normal VGA

On Tue, Jun 09, 2009 at 05:56:26PM -0000, Andres Mujica wrote:
> it seems it's already done. At least for Jaunty and Karmic:
>
> file /boot/vmlinuz-2.6.30-8-generic
> /boot/vmlinuz-2.6.30-8-generic: Linux kernel x86 boot executable bzImage, version 2.6.30-8-generic (buildd@vernad, RO-rootFS, root_dev 0x801, swap_dev 0x3, Normal VGA
> andres@mostro:~$ file /boot/vmlinuz-2.6.28-11-generic
> /boot/vmlinuz-2.6.28-11-generic: Linux kernel x86 boot executable bzImage, version 2.6.28-11-generic (buildd@palme, RO-rootFS, root_dev 0x6801, swap_dev 0x3, Normal VGA

Andres, that's for the kernel image itself, not for the .deb. I'm
talking about the feature whereby you can select a different compression
method for the data.tar part of the .deb. Furthermore, contrary to
popular belief, the "bz" in "bzImage" does *not* denote bzip2
compression; it simply indicates a "big" variant of the older zImage
format that's loaded into high memory.

That said, my original request does appear to have been implemented a
while ago, so this bug can remain closed despite the incorrect closure
reason:

  $ ar t /mirror/ubuntu/pool/main/l/linux/linux-image-2.6.30-8-generic_2.6.30-8.9_i386.deb
  debian-binary
  control.tar.gz
  data.tar.bz2

thks for the heads up Colin!