Enable OVMF option. Has no side-effects and doesn't require compile-time or run-time dependencies until you add bios='ovmf' in a domU cfg.

Just to have it rendered as markdown in the gitlab web view.

Most of the patches are related to the prefix / abiname set.  Sort out
everything in sub directories, so it doesn't look completely like a big
pile of garbage.

Jump forward to commit 728fadb586 in stable-4.10, which contains the
first few XSA-254 fixes.

Add all missing changelog information about what has happened in the
previous set of commits.

In 8c378bc0

 I moved the grub config file that was wrongly placed
inside the hypervisor package, and assumed that it would be fixed in a
stable update, and that the orig tar would not change before that.
However, we don't know yet what will happen in stretch security.

So, don't assume the fix would happen in a specific version in stable.
For now, bump the cutoff point all the way up to 4.10 so we can lower it
again when the actual fix did happen in stretch.

The end goal is to be able to upgrade from stretch to buster without
this problem.  As long as the fix didn't happen in stable, and we have a
newer xen in unstable, the upgrade will hit the conflict.

Signed-off-by: Hans van Kranenburg <hans@knorrie.org>

First time someone does this the directory does not exist and you get an
ugly error. I copied this from the debian kernel genorig.py.

Note: currently my biggest annoyance with the placement of the orig file
in ../orig and the symlink to it is that if I run pbuilder, I will end
up with a symlink pointing nowhere in my pbuilder result location
instead of the actual orig, which makes including it into reprepro bork
of course.

For now, I'm making minimal changes to this. We can improve and change
it later. But this change prevents more lines in the README.source for
now.

Signed-off-by: Hans van Kranenburg <hans@knorrie.org>

Mark Pryor authored Jan 25, 2018 and Hans van Kranenburg committed Jan 26, 2018

xen-4.10 introduces a depends on libxentoolcore to the libxenstore3.0
package.  To keep the library support for the xenstore-utils minimal,
the libxentoolcore*.so* lib is added to the package, along with its
symbols into libxenstore3.0.symbols. This keeps d/control unchanged.

Signed-off-by: Mark Pryor <pryorm09@gmail.com>

Besides the libraries that are mentioned, a bunch of new ones have been
included over time. Just name them in a generic way in the libxen-dev
description.

Signed-off-by: Hans van Kranenburg <hans@knorrie.org>

There's a new library in Xen 4.10. It's xentoolcore, which centralizes
handling of open file descriptors for qemu.

Also see upstream b08da5859b,
"xentoolcore, _restrict_all: Introduce new library and implementation"

So:
- just apply the same patch magic for it as seen in other Makefiles
- include relevant things in libxen-dev

Signed-off-by: Hans van Kranenburg <hans@knorrie.org>

First part of dealing with the upstream changes...

- drop rerun-autogen.sh-stretch.patch, it's in the upstream code
- also include the new uninstall sections (regardless of the fact if
  it's used or not, let's keep things neat and tidy)

Signed-off-by: Hans van Kranenburg <hans@knorrie.org>

Let's try to see what happens when we throw the packaging code on top of
a 4.10 release!

Signed-off-by: Hans van Kranenburg <hans@knorrie.org>

Well, see the text inside. ;-)

The dot would be appended to the first line, ending in:
    [...]interface to XenStore.  .

After doing a full build, it seems there was still stuff not being
ignored correctly. This change should take care of that.

So after debian/rules orig, debian/rules debian/control-real and doing a
package build, there are no files in debian/ showing up as untracked
content. When cleaning out everything using git clean -dfx, there are no
files in debian/ which are listed when doing git status --ignored.

When using versions like 4.9.2~pre+1.32e364c4e7, I want to have an
archive made from commit 32e364c4e7. Same holds for 4.10~rc8+1.3e11e302a8

By picking up the repo provided to the script and kicking the git
archive process into that direction, we can at least do this now:

   ~/build/xen/debian-xen (master) 6-$ debian/bin/genorig.py ~/src/git/xen
   Generate tarball ../orig/xen_4.9.1.orig.tar.xz

...given that the newest changelog entry is e.g. 4.9.1-1

There's probably more things that can be improved in here, but let's
take one step at a time.

So, to reiterate... the orig tar will just be made from commit
32e364c4e7 in the upstream repo. And if we advance to a later point
before 4.9.3 is released, then it'll get 4.9.2~pre+2.<commitid> etc...

Update the packaging for Xen 4.9. I took these changes from the Xen 4.9
packaging in Ubuntu done by Stefan Bader. Thanks!

I'm not going to use Dgit, but rather track all changes in a more
granular way. Remove the obsolete headers.

I copied this one from the linux team. It combines the orig file with
the packaging, so we can start using quilt to refresh the patches.

The grub config snippet is not arch dependent, neither version
dependent, so it has to move into a 'common' package.

The packages with a version number in their name only have contents that
do not conflict with a previous or next version. Having this file in the
version dependent xen-hypervisor package currently prevents us from
being able to co-install the current and next version of Xen.

So, I can do this here for new packages in unstable but that will only
fix upgrades from xen 4.9 to 4.10. The same change still needs to go
into a stable update to solve the problem for upgrades from Stretch to
Buster.

Also see https://bugs.debian.org/852545

    When tracking the latest upstream versions in Debian unstable, I'd
like to keep the packages updated with latest available security patches
which are available when working on a new upload. So that means not
always working with an exact tagged upstream release.

There are two possible approaches when doing this:

1. Use the latest official release as orig tar and keep the rest of the
changes in debian patches. This is also what we would do for security
updates to stable.
2. Just follow the upstream stable branch lines (they will always fix
forward) and keep the latest changes in the orig tar.

I think option 2 makes the most sense for uploads to unstable when we're
nowhere near to a freeze yet. This results in version numbers like
4.9.2~pre+1.32e364c4e7-1, where the 1 is simply a helper because git
commit ids are not sortable. 4.9.1+1.32e364c4e7-1 would also be an
option, but since xen will report itself als 4.9.2-pre (e.g. in xen info
output), I prefer the ~pre one.

    When testing new versions that are in rc state upstream, we might
put them in the Debian experimental distribution, so that we can find
out what needs to be done to the packaging already, and so that we
provide the opportunity for Debian users to help testing the new release
on their hardware.

These versions will usually look like e.g. 4.10~rc8-1~exp1, but
incidentally they could also include a few newer corrections, in which
case we end up with a git revision again, like seen above, but then with
rcX instead of pre and now the second pattern choice, because upstream
doesn't let us know if there will be a next rc, or the actual release.
So, that would be something like 4.10~rc8+1.3e11e302a8-1~exp1

    This change allows both of these version patterns. While only the
major.minor version is used from it all, it's a nice sanity checker to
prevent eventual mistakes.

Allowed:
 * 4.9.2-1
 * 4.9.2~pre+1.32e364c4e7
 * 4.10~rc8-1~exp1
 * 4.10~rc8+1.3e11e302a8-1~exp1

Not allowed:
 * 4.10-1

This package uses some code from the linux-support package to generate
files. The way in which this done in the packaging is similar to how the
linux source package is managed.

debian/rules.defs defines a KERNELVERSION which requires you to have the
linux-support-$KERNELVERSION package installed.

For now, update it to 4.9.0-4, since that's the current latest in
Stretch. I'm working on the packaging on a stretch system.

After doing so...
    -$ make -f debian/rules debian/control-real
    [...]
      File "/usr/src/linux-support-4.9.0-4/lib/python/debian_linux/gencontrol.py", line 124, in do_main_recurse
          for featureset in self.config['base', ]['featuresets']:
    KeyError: 'featuresets'

Apparently the newer linux-support requires featuresets to be set. We
simply add it with only the option none, since we don't use it.

I'm preparing a 4.9 or 4.10 release, so no need to keep these.

But, fix the .gitignore while doing so. It was ignoring way too much
(e.g. tree/xen-utils-common) and not ignoring some of the generated
content (e.g. control.md5sum).

The orig tar that belongs to this debian version is created from this
commit in xen/stable-4.8:

    commit 9ba6783e47db71379c5120039b878f605bdf31f3
    Author: Andrew Cooper <andrew.cooper3@citrix.com>
    Date:   Thu Nov 16 11:55:47 2017 +0100

    x86/shadow: correct SH_LINEAR mapping detection in sh_guess_wrmap()