[Pkg-xen-devel] Entirely new Xen packaging

[Hans van Kranenburg]

On 10/05/2018 08:04 PM, Ian Jackson wrote:
> I have now finished totally rewriting the Xen package in Debian, from
> scratch.  Amazingly as soon as I got a package which was lintian-clean
> and would install, it worked first time !

\:D/ Congrats!

> I have generated 18 patches to go upstream which I have sent to
> xen-devel.  There are two more, xenstore ABI patches, which need a bit
> of tidying up.
> 
> 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!

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

The comments about why things are in a certain place (like, in rules)
are really helpful.

> I do not know if it builds other than on amd64.  I hope so, because I
> have stripped out a lot of cruft.  If there are build failures we will
> have to fix them.
> 
> Debian FTP Masters writes ("xen_4.11.1~pre.20180911.5acdd26fdc+dfsg-1~exp1_multi.changes ACCEPTED into experimental, experimental"):
>>  xen (4.11.1~pre.20180911.5acdd26fdc+dfsg-1~exp1) experimental; urgency=medium
>>  .
>>    * Update to new upstream version 4.11.1~pre.20180911.5acdd26fdc+dfsg.
>>    * Remove stubdom/grub.patches/00cvs from the upstream source because it's
>>      not DFSG compliant. (license-problem-gfdl-invariants)
>>    * Override statically-linked-binary lintian error about
>>      usr/lib/xen-4.11/boot/xen-shim
> 
> I accidentally dropped these changes from my fisrt upload to sid.  I
> noticed when I tried to push to salsa/master and discovered my branch
> wasn't ff.  Hooray for git.
> 
> So I have fixed that by rebasing onto the dfsg upstreamk tag and
> followed it up with a 2nd upload.  So please don't be alarmed by noise
> from the archive.

Ah, that's probably because I started working on that during the UK
visit, while you started working on this. :)

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.

o/
Hans