Mainline builds

Andy Whitcroft apw at canonical.com
Tue Apr 6 09:20:56 UTC 2010


On Mon, Apr 05, 2010 at 10:03:33AM +0200, Geir Ove Myhr wrote:
> The mainline builds of 2.6.34-rc2 and -rc3 have failed. Does anybody
> know how to fix this?

Hrm, brokeness due to the new configuration checks.  I will get that
fixed up.

> Also, since around March 15 the mainline builds have a release name
> associated to it (lucid and karmic). Could somebody explain the
> significance of this or document it at
> https://wiki.ubuntu.com/KernelTeam/MainlineBuilds ?

These indicate which Ubuntu series the builds were made in, essentially
from which series the configuration was taken.  Previously the
configurations were very similar and there was little difference which
release they were built and no need to differentiate them.  However,
from Karmic to Lucid we have a number of very specifici configuration
requirements such as DEVTMPFS which mean that a kernel built with a
Karmic based configuration and the same kernel built with a Lucid based
configuration are considerably different.  Therefore it is sensible to
expose the build series in the built directory names.  This will also
allow us to build in multiple series where that is appropriate.

> And while mentioning the wiki page, it would be nice if it could
> explain in more detail what "Ubuntu kernel configuration files" means.
> My experience is that copying e.g.
> /boot/config-2.6.34-020634rc1-generic does not reproduce a mainline
> build if I build it myself (e.g. I will have to turn kernel debugging
> off in order to produce kernel-image*.deb < 30 MB instead of > 200
> MB). The wiki page https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
> suggests one needs to use the --overlay-dir option to make-kpkg with a
> current ubuntu-git tree.

All Ubuntu builds are built with debugging turned on, and that then
stripped at packaging time.  This allows one build to produce .ddeb and
.deb packages and saving time.

> Finally, I'm currently not able to build 2.6.34-rcX using the
> instructions at https://wiki.ubuntu.com/KernelTeam/GitKernelBuild, but
> I suppose that is related to the failing mainline builds, so leave
> that out for now.
> 
> I understand you guys are busy preparing for the Lucid release, but
> the missing mainline builds and difficult compile instructions make
> triaging and upstreaming Ubuntu bugs and testing patches from upstream
> much harder. For example, drm/i915 developers need more testing of the
> patch at http://bugs.freedesktop.org/show_bug.cgi?id=27187#c64 (LP:
> 541511) and I would have liked to prepare an Ubuntu package with that
> so that some of the Ubuntu users who have reported this problem could
> provide their test results without figuring out how to patch and build
> a kernel.

Entirely why we spend time producing these builds.  I hope to have these
fixed and building again correctly today.

-apw




More information about the kernel-team mailing list