linux-image-debug

[Colin Watson]

On Mon, Mar 02, 2009 at 07:16:05PM -0700, Tim Gardner wrote:
> I need an archive wizard. While attempting to restore the construction  
> of linux-image-debug-{generic,server} in Jaunty, I discovered that these  
> debug packages are already being built, but only on the buildd's (which  
> is a good thing because they are ginormous). In the attached snippet  
> from debian/rules.d/2-binary-arch.mk, I'm a bit confused about the code  
> starting after the "Hokay" comment. I assume renaming the package to  
> *.ddeb serves some special purpose?

ddebs are indeed somewhat complicated magic.
https://blueprints.launchpad.net/ubuntu/+spec/apt-get-debug-symbols and
https://wiki.ubuntu.com/DebuggingProgramCrash are worthwhile background
reading here.

Briefly, ddebs go into a separate archive rather than bloating the main
one with debugging symbols; there are special tools to deal with that
separate archive in convenient ways.

> What effect does removing the package name from debian/files have?

debian/files is the list of files to be uploaded; it is read by
dpkg-genchanges.

Ideally, the ddebs *would* actually be in debian/files (either by
seddery or by use of dpkg-distaddfile). However, the Launchpad archive
doesn't yet support ddebs, and so there is a hacked-up system on the
buildds to process these (I haven't checked, but assume that it just
looks in the parent of the build directory for files called .ddeb or
something like that).

> Where do the .ddeb packages ultimately end up?

  http://ddebs.ubuntu.com/pool/main/l/linux/

(This is really Martin Pitt's area; if you have further questions he
would be your man.)

Cheers,

-- 
Colin Watson                                       [cjwatson at ubuntu.com]