[Pkg-xen-devel] Are we there yet?
ralph at debianbase.de
Fri Feb 24 12:39:08 UTC 2006
Am Freitag, 24. Februar 2006 06:28 schrieb Guido Trotter:
> On Thu, Feb 23, 2006 at 08:23:20PM +0100, Ralph Passgang wrote:
> > hmmm, I am not sure what is still open and not fixed, but I guess the
> > most stuff is in shapre for a release now.
> I have test packages built with the last svn on
> http://debian.quaqua.net/quaqua pkg-xen/
> Anyway before uploading we need to fix the xenstore library positioning
> issue! Then I think we're pretty much done!
> > but what about the dh-kpatches problem? We still have a patch that
> > doesn't change the extraversion.
> is it really necessary? I noticed that mine doesn't too! (I don't know why,
> I didn't use upstream's makefile to build it, but just manually did a
> ./mkbuildtree and applied patches/linux-2.6.12/ patches) And since I
> compile with --arch=xen I already get package names called
> linux-xen0-22.214.171.124tst000_000_i386.deb (the tst000 is mine)...
not really sure what happens if you "just" use mkbuildtree. But I am hoping
that upstream fixes the patch generation anyways, I would like to use this
function for patch generation.
of course it's not a critical problem that the extraversion is missing in
the .config, but of course I can life with it the way it is (it's exactly how
my package handled it).
But you should add "--append_to_version .6-xen" to the make-kpkg options to
have a kernel that reports "126.96.36.199-xen" with the uname comand.
What version does a uname reports on your xen-kernel?
> Anyway if we want we can even direct people to the patch and tell them to
> apply it with zcat patch | patch -p1, and be done! ;)
of course, that's the other posibiltiy. because we use a vanilla kernel and
not a debianized one this would be okay, wouldn't it?
Hmmm, but is it really better? not sure... I don't want to decice that :)
> Pkg-xen-devel mailing list
> Pkg-xen-devel at lists.alioth.debian.org
More information about the Pkg-xen-devel