Comment 61 for bug 1787405

In preparation I did prepare the series for Disco/Cosmic:

For libvirt 4.6 compared to our series to 4.0:
- drop three being upstream in 4.4 and 4.6
  2b9690b62d01bb0b8555764e2365976b98fe4d47 v4.4.0
  21442874cf61ce61c7e0f8bcd616641f35adda2b v4.4.0
  d54e45b6edd7623e488a19e30bc4148a21fa8b03 v4.6.0
- old lp1787405-0006-conf-Move-VFIO-AP-validation-from-post-parse-to-QEMU.patch backport can now use the upstream versions of 208d6e6f5aafa102d04ce300c6338b0736bb52df and faab373b53e1a4eacf0d6f524eb47df243f21fac instead
- we can now use the upstram patch for f865d58028ccd568b6e7909608678584b12d3c90 as-is
- context updates for debian/patches/ubuntu/lp1787405-0003-qemu-add-vfio-ap-capability.patch
- also updated the Bionic branch as I realized patch 6 had actually two upstream patches as source (only meta data).

For qemu:
- patch debian/patches/ubuntu/lp1787405-0001-linux-headers-update.patch had some minor context updates
- patch ubuntu/lp1787405-0002-s390x-cpumodel-Set-up-CPU-model-for-AP-device-suppor.patch and ubuntu/lp1787405-0004-s390x-ap-base-Adjunct-Processor-AP-object-model.patch can now use the upstream version as-is
- some minor header updates for the Bionic branch

Both branches are built for Disco in the PPA we already used [1].

I'll wait another day for the libvirt upstreaming - there were a few reviews, but no formal ack's yet. I'll ping via IRC if nothing more is happening until tomorrow.

FYI: To add more fun to all the code-porting I just happened to realize that there is also a bunch of CVE fixes incoming (I don't know the content yet). But that might force us to bump these branches once more.

[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3520