| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Delete-config.sub-and-config.guess.patch | Delete config.sub and config.guess dh_autoreconf will provide these back. If this patch does not apply when rebasing, you can simply delete the files again. |
Ian Jackson <ian.jackson@citrix.com> | no | 2018-09-19 | ||
| 0002-Delete-configure-output.patch | Delete configure output These autogenerated files are not useful in Debian; dh_autoreconf will regenerate them. If this patch does not apply when rebasing, you can simply delete the files again. |
Ian Jackson <ian.jackson@citrix.com> | no | 2018-09-19 | ||
| 0003-Display-Debian-package-version-in-hypervisor-log.patch | Display Debian package version in hypervisor log During hypervisor boot, disable the banner and nicely display the xen version as well as the Maintainer address from debian/control. For this to work the DEB_VERSION and DEB_MAINTAINER variables needs to be set by debian/rules. Original patch by Bastian Blank <waldi@debian.org> Modified by Hans van Kranenburg <hans@knorrie.org> Maximilian Engelhardt <maxi@daemonizer.de> |
Bastian Blank <waldi@debian.org> | no | 2014-07-05 | ||
| prefix-abiname/config-prefix.diff | config-prefix.diff | Bastian Blank <waldi@debian.org> | no | 2014-07-05 | ||
| 0005-Do-not-ship-COPYING-into-usr-include.patch | Do not ship COPYING into /usr/include This is not wanted in Debian. COPYING ends up in /usr/share/doc/xen-*copyright. |
Bastian Blank <waldi@debian.org> | no | 2014-07-05 | ||
| misc/tools-pygrub-remove-static-solaris-support | Remove static solaris support from pygrub | Bastian Blank <waldi@debian.org> | no | 2014-07-05 | ||
| 0007-Do-not-build-the-instruction-emulator.patch | Do not build the instruction emulator | Ian Jackson <ian.jackson@citrix.com> | no | 2018-09-20 | ||
| 0008-tools-libfsimage-prefix.diff.patch | tools-libfsimage-prefix.diff \o/ |
Hans van Kranenburg <hans@knorrie.org> | no | 2020-05-25 | ||
| 0009-autoconf-Provide-libexec_libdir_suffix.patch | autoconf: Provide libexec_libdir_suffix This is going to be used to put libfsimage.so into a path containing the multiarch triplet. |
Ian Jackson <ian.jackson@citrix.com> | no | 2018-10-03 | ||
| 0010-.gitignore-Add-configure-output-which-we-always-dele.patch | .gitignore: Add configure output which we always delete and regenerate | Ian Jackson <ian.jackson@citrix.com> | no | 2018-10-05 | ||
| 0011-config-Tools.mk.in-Respect-caller-s-CONFIG_PV_SHIM.patch | config/Tools.mk.in: Respect caller's CONFIG_PV_SHIM This makes it easier to disable the shim build. (In Debian we need to build the shim separately because it needs different compiler flags). [ Hans: adjust from tools/firmware/Makefile to config/Tools.mk.in to follow changes that happened in 8845155c83 ("pvshim: make PV shim build selectable from configure") ] |
Ian Jackson <iwj@barriere.debian.org> | no | 2018-10-12 | ||
| 0012-shim-Provide-separate-install-shim-target.patch | shim: Provide separate install-shim target When building on a 32-bit userland, the user wants to build 32-bit tools and a 64-bit hypervisor. This involves setting XEN_TARGET_ARCH to different values for the tools build and the hypervisor build. So the user must invoke the tools build and the hypervisor build separately. However, although the shim is done by the tools/firmware Makefile, its bitness needs to be the same as the hypervisor, not the same as the tools. When run with XEN_TARGET_ARCH=x86_32, it it skipped, which is wrong. So the user must invoke the shim build separately. This can be done with make -C tools/firmware/xen-dir XEN_TARGET_ARCH=x86_64 However, tools/firmware/xen-dir has no `install' target. The installation of all `firmware' is done in tools/firmware/Makefile. It might be possible to fix this, but it is not trivial. For example, the definitions of INST_DIR and DEBG_DIR would need to be copied, as would an appropriate $(INSTALL_DIR) call. For now, provide an `install-shim' target in tools/firmware/Makefile. This has to be called from `install' of course. We can't make it a dependency of `install' because it might be run before `all' has completed. We could make it depend on a `shim' target but such a target is nearly impossible to write because everything is done by the inflexible subdir-$@ machinery. The overally result of this patch is that existing make invocations work as before. But additionally, the user can say make -C tools/firmware install-shim XEN_TARGET_ARCH=x86_64 to install the shim. The user must have built it already. Unlike the build rune, this install-rune is properly conditional so it is OK to call on ARM. What a mess. |
Ian Jackson <iwj@barriere.debian.org> | no | 2018-10-12 | ||
| 0013-docs-man-xen-vbd-interface.7-Provide-properly-format.patch | docs/man/xen-vbd-interface.7: Provide properly-formatted NAME section This manpage was omitted from docs/man: Provide properly-formatted NAME sections because I was previously building with markdown not installed. |
Ian Jackson <ian.jackson@citrix.com> | no | 2018-10-12 | ||
| 0014-t-h-L-vif-common.sh-disable-handle_iptable.patch | t/h/L/vif-common.sh: disable handle_iptable Also see Debian bug #894013. The current attempt at providing anti-spoofing rules results in a situation that does not have any effect. Also note that forwarding bridged traffic to iptables is not enabled by default, and that for openvswitch users it does not make any sense. So, stop cluttering the live iptables ruleset. This functionality seems to be introduced before 2004 and since then it has never got some additional love. It would be nice to have a proper discussion upstream about how Xen could provide some anti mac/ip spoofing in the dom0. It does not seem to be a trivial thing to do, since it requires having quite some knowledge about what the domU is allowed to do or not (e.g. a domU can be a router...). |
Hans van Kranenburg <hans@knorrie.org> | no | 2019-01-04 | ||
| 0015-sysconfig.xencommons.in-Strip-and-debianize.patch | sysconfig.xencommons.in: Strip and debianize Strip all options that are for stuff we don't ship, which is 1) xenstored as stubdom and 2) the new options for oom score and open file descriptor limit, which would not have any effect, because we're shipping different init scripts... :| It seems useful to give the user the option to revert to xenstored instead of the default oxenstored if they really want. |
Hans van Kranenburg <hans@knorrie.org> | no | 2019-02-09 | ||
| 0016-hotplug-common-Do-not-adjust-LD_LIBRARY_PATH.patch | hotplug-common: Do not adjust LD_LIBRARY_PATH This is in the upstream script because on non-Debian systems, the default install locations in /usr/local/lib might not be on the linker path, and as a result the hotplug scripts would break. A reason we might need it in Debian is our multiple version coinstallation scheme. However, the hotplug scripts all call the utilities via the wrappers, and the binaries are configured to load from the right place anyway. This setting is an annoyance because it requires libdir, which is an arch-specific path but comes from a file we want to put in xen-utils-common, an arch:all package. So drop this setting. |
Ian Jackson <ian.jackson@citrix.com> | no | 2019-02-21 | ||
| 0017-pygrub-Set-sys.path.patch | pygrub: Set sys.path We install libfsimage in a non-standard path for Reasons. (See debian/rules.) This patch was originally part of `tools-pygrub-prefix.diff' (eg commit 51657319be54) and included changes to the Makefile to change the installation arrangements (we do that part in the rules now since that is a lot less prone to conflicts when we update) and to shared library rpath (which is now done in a separate patch). (Commit message rewritten by Ian Jackson.) squash! pygrub: Set sys.path and rpath |
Bastian Blank <waldi@debian.org> | no | 2014-07-05 | ||
| 0018-pygrub-Specify-rpath-LIBEXEC_LIB-when-building-fsima.patch | pygrub: Specify -rpath LIBEXEC_LIB when building fsimage.so If LIBEXEC_LIB is not on the default linker search path, the python fsimage.so module fails to find libfsimage.so. Add the relevant directory to the rpath explicitly. (This situation occurs in the Debian package, where --with-libexec-libdir is used to put each Xen version's libraries and utilities in their own directory, to allow them to be coinstalled.) |
Ian Jackson <ian.jackson@citrix.com> | no | 2019-02-22 | ||
| 0019-tools-xl-bash-completion-also-complete-xen.patch | tools/xl/bash-completion: also complete 'xen' We have the `xen` alias for xl in Debian, since in the past it was a command that could execute either xl or xm. Now, it always does xl, so, complete the same stuff for it as we have for xl. [git-debrebase split: mixed commit: upstream part] |
Hans van Kranenburg <hans@knorrie.org> | no | 2019-02-10 | ||
| 0020-tools-don-t-build-ship-xenmon.patch | tools: don't build/ship xenmon This is something that hasn't been touched (except for making it Python 3 compatible, which failed) since 2007. Don't build or ship it. -# xenmon File "/usr/sbin/xenmon", line 680 stop_cmd = "/usr/bin/pkill -INT -z global xenbaked" TabError: inconsistent use of tabs and spaces in indentation |
Hans van Kranenburg <hans@knorrie.org> | no | 2020-09-05 | ||
| 0021-docs-set-date-to-SOURCE_DATE_EPOCH-if-available.patch | docs: set date to SOURCE_DATE_EPOCH if available Use the solution described in [1] to replace the call to the 'date' command with a version that uses SOURCE_DATE_EPOCH if available. This is needed for reproducible builds. [1] https://reproducible-builds.org/docs/source-date-epoch/ [Hans van Kranenburg] expect that it gets in. Otherwise, we don't wait and already have it here because I want to have the reproducible build work completed. |
Maximilian Engelhardt <maxi@daemonizer.de> | no | 2020-12-18 | ||
| 0022-give-meaningful-error-message-if-qemu-device-model-i.patch | give meaningful error message if qemu device model is unavailable There's no sense to switch to qemu-xen-traditional device model if that one is not enabled in the first place. This way we'll have a chance later to print a message suggesting to install the missing qemu package if we *actually* need qemu for the device model. |
Michael Tokarev <mjt@tls.msk.ru> | no | 2022-04-24 | ||
| 0023-xen-arch-x86-make-objdump-output-user-locale-agnosti.patch | xen/arch/x86: make objdump output user locale agnostic The objdump output is fed to grep, so make sure it doesn't change with different user locales and break the grep parsing. This problem was identified while updating xen in Debian and the fix is needed for generating reproducible builds in varying environments. |
Maximilian Engelhardt <maxi@daemonizer.de> | no | 2021-12-10 | ||
| 0024-tools-xenstore-xenstored_control.c-correctly-print-t.patch | tools/xenstore/xenstored_control.c: correctly print time_t On 32 bit systems with 64 bit time_t (hello, Y2038 problem), the following error occurs otherwise: | xenstored_control.c: In function 'lu_reject_reason': | xenstored_control.c:646:70: error: format '%ld' expects argument of type 'long int', but argument 5 has type 'time_t' {aka 'long long int'} [-Werror=format=] (cherry picked from commit b33a5c5929bce66302fbfd680ac5b4091886079e) |
Alexander Kanavin <alex@linutronix.de> | no | 2023-04-19 |