[Pkg-xen-devel] Entirely new Xen packaging [and 1 more messages]

[Ian Jackson]

Hans van Kranenburg writes ("Re: Entirely new Xen packaging"):
> On 10/05/2018 08:04 PM, Ian Jackson wrote:
> > There is still room for improvement but it is now clearly ready for
> > sharing so I uploaded it.  The result is now in dgit/dgit/sid, and
> > salsa/master.
> 
> This is an amazing amount of improvements, really nice!

Great, thanks for the kind words.

> I've spent last hour looking around, and did build packages for stretch.
> I'm going to install them probably tomorrow.

Any idea about the i386/armhf/arm64 builds ?  (I don't want to upload
anything else while this one sits in NEW.)

> I plan to work on this project on tuesday (2nd tuesday of the month!),
> finally processing my notes, updating TODO-list stuff and doing a few of
> them.

:-).  That's tomorrow.

I think you should push whatever improvements to salsa/master and we
can upload it when the current version is through NEW.

Hans van Kranenburg writes ("Re: Entirely new Xen packaging"):
> How does the new package play together with qemu in Debian? How far are
> we now away from being able to do buster-backports without qemu problems
> for whoever wants to use HVM with backports?

xen.git is supposed to be decoupled from the qemu version.  I see no
reason why it wouldn't work.  (In fact, don't tell anyone, but I
tested by upload with builds on stretch because the most convenient
test box was running stretch.)

> From the discussion last month at Citrix I understood that qemu could
> likely be changed to depend on one or more of the stable library
> packages instead of libxenmisc4.y (or, libxen-4.y, including all of it now).

I didn't test a qemu *build*.  But the qemu build-deps will be the
same because I didn't change the dev package.  The binary deps of the
resulting qemu will be different but the shlibdeps machinery will
handle it all.

> Also, does that mean there need to be more libxen<blaat>-dev packages,
> or not?

No, we want only one libxen-dev package.

I'm currently messing about with the libxenstore and libfsimage
patches to try to make them upstreamable.

Ian.

-- 
Ian Jackson <ijackson at chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.