| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Use-obs-build-in-locations-and-executable-names.patch | Use obs-build in locations and executable names instead of just build. | Héctor Orón Martínez <zumbi@debian.org> | not-needed | 2018-08-30 | ||
| 0002-HACK-make-glibc-build.patch | HACK: make glibc build | Héctor Orón Martínez <zumbi@debian.org> | not-needed | debian | 2018-08-30 | |
| 0003-dsc-keep-everything.patch | dsc: keep everything Debian package build dependencies allow for direct or indirect build cycles, when doing a full distribution build in OBS this means keeping the keep list gets very tedious very quickly. Adjust the default keep processing such that for Debian (dsc) builds everything is kept by default |
Héctor Orón Martínez <zumbi@debian.org> | yes | 2018-08-30 | ||
| 0004-build-recipe-dsc-don-t-rebuild-the-source-package.patch | build-recipe-dsc: don't rebuild the source package If we use build suffixes, rebuilding the source package will result in the build suffix being included into the source package, which we'd rather avoid. |
Andrej Shadura <andrew.shadura@collabora.co.uk> | yes | 2018-08-30 | ||
| 0005-Log-the-version-number-during-startup.patch | Log the version number during startup When testing OBS behaviour changes, it's useful to be able to look at a build log and see which code was running. |
Simon McVittie <smcv@collabora.com> | yes | 2018-11-12 | ||
| 0006-debootstrap-Print-the-exact-command-we-re-going-to-r.patch | debootstrap: Print the exact command we're going to run debootstrap is not a simple command, and there are some subtleties to the options we use, so we should log exactly what we did. The incantation with `$(printf ' %q' "$@")` is to log the contents of $@, correctly shell-quoted to avoid ambiguity (in case there are spaces in an argument). It should expand to something like running debootstrap: chroot /buildroot debootstrap --etc --etc... |
Simon McVittie <smcv@collabora.com> | yes | 2018-11-12 | ||
| 0007-deb-Show-version-of-each-package-that-we-preinstall.patch | deb: Show version of each package that we preinstall If packages fail to unpack or configure during the preinstall step, it's useful for the log to indicate precisely which packages were used. |
Simon McVittie <smcv@collabora.com> | yes | 2018-11-12 | ||
| 0008-build-recipe-dsc-List-contents-of-build-results.patch | build-recipe-dsc: List contents of build results Debian's sbuild dumps the metadata and contents of all build results into its own logs, which is often helpful when comparing build logs and package contents. Let's do the same. |
Simon McVittie <smcv@collabora.com> | yes | 2019-03-18 | ||
| 0009-build-recipe-dsc-Show-information-about-the-build-ch.patch | build-recipe-dsc: Show information about the build chroot This vaguely mimics what Debian's sbuild does, although the precise information given here is different. |
Simon McVittie <smcv@collabora.com> | yes | 2019-03-18 | ||
| 0010-Add-a-new-changelog-entry-for-debian-packages.patch | Add a new changelog entry for debian packages Rather then hacking up the current top changelog entry with a new version, add a generated entry at the top. Also do this in all cases a release tag has been set not just if the control file has the magic tag. As a further change, this uses the release tag directly rather then prefixing it with +, as that works in all cases e.g. 1-1+build1 is considered a higher version than 1-1ubuntu2+build1 by the Debian tools (+, unlike ~, isn't considered special). |
Sjoerd Simons <sjoerd.simons@collabora.co.uk> | no | 2017-02-23 | ||
| 0011-Use-Python-3-for-the-openstack-console.patch | Use Python 3 for the openstack console | Andrej Shadura <andrew.shadura@collabora.co.uk> | no | 2020-08-06 | ||
| 0012-Fallback-to-stable-if-lsb-reports-a-non-supported-di.patch | Fallback to stable if lsb reports a non-supported dist in debootstrap We have a issue that cause all package FTBFS in OBS when the base-files updated to a dist name that not supported in debootstrap. If lsb reported a non-supported dist, we fallback it to stable to avoid FTBFS in OBS. |
Andrew Lee (李健秋) <ajqlee@debian.org> | no | 2019-10-04 | ||
| 0013-Force-locale-to-C.UTF-8.patch | Force locale to C.UTF-8 Multiple packages have run into build failures on our OBS. On closer inspection, it was concluded to be issues with the locale settings. These issues were never seen on the Debian buildd infrastructure because there the locale setting LC_ALL=C.UTF-8 is in use. This change keeps us closer to what is used in Debian buildds. https://github.com/openSUSE/obs-build/pull/665 |
Emanuele Aina <emanuele.aina@collabora.com> | no | 2021-04-12 | ||
| 0014-Force-the-local-timezone-to-be-UTC.patch | Force the local timezone to be UTC To make the build environment a bit more reproducible, ensure the local timezone is set to UTC when building packages. |
Emanuele Aina <emanuele.aina@collabora.com> | no | 2021-04-12 | ||
| 0015-Unset-TERM-to-prevent-unexpectedly-colorized-output-.patch | Unset $TERM to prevent unexpectedly colorized output from breaking builds Our OBS workers run under a `screen` session, which gives them an actual `$TERM` variable. Some packages like `color.js` then enable colored output, which confuses some other packages like `node-grunt-legacy-log` which use it in their testsuite and do not expect colored output. To avoid that, unset `TERM`. |
Emanuele Aina <emanuele.aina@collabora.com> | no | 2021-04-12 | ||
| 0016-init_buildsystem-Move-hostname-ip-entry-to-the-end-o.patch | init_buildsystem: Move hostname ip entry to the end of /etc/hosts spymemcached package is FTBFS because a test expects a reverse lookup of 127.0.0.1 to return localhost, but current /etc/hosts configuration returns the hostname instead. Let's move this `hostname/ip` entry to the end of /etc/hosts so the reverse lookup of 127.0.0.1 returns localhost, which makes sense to be the default case usually. |
Ariel D'Alessandro <ariel.dalessandro@collabora.com> | no | debian | 2021-06-21 | |
| 0017-Consistently-use-deb_chroot-instead-of-chroot-where-.patch | Consistently use deb_chroot instead of chroot where it makes a difference | Andrej Shadura <andrew.shadura@collabora.co.uk> | no | 2022-11-10 | ||
| 0018-Escape-arguments-properly-to-avoid-leaking-spaces.patch | Escape arguments properly to avoid leaking spaces | Andrej Shadura <andrew.shadura@collabora.co.uk> | no | 2022-11-10 | ||
| 0019-Wrap-chroot-su-in-a-function-to-consistently-set-up-.patch | Wrap chroot + su in a function to consistently set up environment for builds Since "su -" cleans the environment, we need to tell it to keep variables we want to preserve. To make this easier, create a new wrapper su_deb_chroot that runs chroot and su and sets up the environment. Since DEBIAN_* variables are only needed when preparing the build chroot, don’t set them in su_deb_chroot. |
Andrej Shadura <andrew.shadura@collabora.co.uk> | no | 2022-11-10 |