| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| cross.patch | no | |||||
| reproducible-build.patch | Make the documentation build reproducibly | Chris Lamb <lamby@debian.org> | no | 2020-09-24 | ||
| Add-support-for-more-compression-formats.patch | Add support for more compression formats | Aurelien Jarno <aurelien@aurel32.net> | no | upstream, https://github.com/codelibre-net/schroot/commit/22e04451800756b59f6e47b092ed952bc0dc995f | 2014-11-13 | |
| Add-SESSION_SOURCE-and-CHROOT_SESSION_SOURCE.patch | Add SESSION_SOURCE and CHROOT_SESSION_SOURCE | =?utf-8?q?Rapha=C3=ABl_Hertzog?= <hertzog@debian.org> | no | debian | upstream | 2015-08-16 |
| 10mount-Move-mount-directory-to-var-run.patch | 10mount: Move mount directory to /var/run Note that this patch merges multiple upstream commits. |
=?utf-8?q?Rapha=C3=ABl_Hertzog?= <hertzog@debian.org> | no | debian | upstream | 2015-08-16 |
| Support-union-mounts-with-overlay-as-in-Linux-4.0.patch | Support union mounts with overlay, as in Linux 4.0 | Felipe Sateler <ffsateler@debian.org> | yes | upstream | 2015-05-23 | |
| GCC5-fixes-on-regexes.patch | GCC5 fixes on regexes | =?utf-8?q?Rapha=C3=ABl_Hertzog?= <hertzog@debian.org> | yes | upstream | upstream | 2015-08-16 |
| schroot-mount-make-bind-mounts-private.patch | [PATCH] schroot-mount: Make bind mounts use private mount propagation When creating a bind mount, on a Linux system, mark the target as private. When creating a recursive bind mount, on a Linux system, mark the target as recursively private. This change fixes issues around shared mount points being bind mounted into a schroot and then when the schroot session is tore down, the mount point being unmounted in both the schroot and in the host environment. For example, if the schroot fstab file contains the following line: /home /home none rw,rbind 0 0 A user's home directory mounted at /home/$USER is unmounted in both the schroot and host when the schroot sessions is ended without this change. |
Tyler Hicks <tyhicks@canonical.com> | no | 2015-10-27 | ||
| schroot-mount-resolve-mount-destinations-while-chrooted.patch | [PATCH] schroot-mount: Resolve mount destinations while chrooted The schroot-mount binary was attempting to use realpath(3) from outside of the chroot to resolve mount destination paths inside of the chroot. It would then take the resolved path and prepend it with the path to the chroot in an attempt to enforce that symlink resolution will always end up inside of the chroot. One example of why this approach isn't sufficient is that when /<chroot>/dev/shm/ is the mount destination but it is a symlink to /run/shm and the host's /run/shm is a symlink to /dev/shm. The resolved path will end up being /<chroot>/dev/shm/ and, due to mount following symlinks, the host's /dev/shm will be mounted over. To fix the path resolution issue, this patch first resolves the path to the chroot base path, then forks and calls chroot(2) on that path, then resolves the path to the mount destination inside the chroot. Finally, the resolved chroot base path and the resolved mount destination path are combined to create the fully resolved path used for mounting. |
Tyler Hicks <tyhicks@canonical.com> | no | debian | 2015-07-28 | |
| fix-test-suite-with-usrmerge.patch | Fix test suite when /bin is a symlink to /usr/bin | Raphaël Hertzog <hertzog@debian.org> | no | 2017-01-09 | ||
| Unmount-everything-that-we-can-instead-of-giving-up.patch | [PATCH] Unmount everything that we can, instead of giving up at the first failure | Dima Kogan <dima@secretsauce.net> | no | 2016-07-02 | ||
| fix-killprocs.patch | Fix logic in 15killprocs The code that tried to identify processes running in a chroot was failing when the chroot path contained a symlink (/var/run) since the kernel reports a canonicalized name. . Thanks to Christoph Biedl <debian.axhn@manchmal.in-ulm.de> for the analysis. |
Raphaël Hertzog <hertzog@debian.org> | no | debian | 2017-01-09 | |
| fix-bash-completion.patch | Fix bash completion | Raphaël Hertzog <hertzog@debian.org> | yes | debian upstream | 2017-06-06 | |
| fix_typos_in_schroot_manpage.patch | schroot: [INTL:de] Updated German PO translation There's a typo (marked with »FIXME« in the po file). Date: Wed, 26 Nov 2014 15:26:13 +0000 From: Roger Leigh <rleigh@codelibre.net> Many thanks, much appreciated! I've committed this including the typo fix--thanks for pointing it out. =================================================================== |
Chris Leick <c.leick@vollbio.de> | no | debian | upstream | 2014-11-25 |
| update_czech_schroot_translation.patch | [l10n] Updated Czech translation of schroot in attachment there is updated Czech (cs.po) translation of schroot. =================================================================== |
Miroslav Kure <kurem@upcase.inf.upol.cz> | no | debian | upstream | 2014-11-29 |
| update_french_schroot_manpage_translation_2018.patch | =================================================================== | no | ||||
| update_german_schroot_manpage_translation_2018.patch | =================================================================== | no | ||||
| zfs-snapshot-support.patch | add support for a zfs-snapshot backend. =================================================================== |
Steve Langasek <vorlon@debian.org> | no | debian | 2020-01-04 | |
| binfmt-parent-dir.patch | schroot-setup: create parent directory for binfmt interpreter (#983087) Currently schroot-setu (/etc/setup.d/15binfmt) mounts foreign binfmt interpreter from host into the chroot. The problem is that the interpreter could be in a directory which is not present in the chroot being created. Ensure the parent directory exists before trying to bind-mount the interpreter. For qemu-based foreign chroots this whole thing isn't necessary with the introduction of the F binfmt-misc flag (fix_binary), but it wont hurt anyway. Also, the current method only works for binfmt-support package and not for other ways to register binfmt-misc interpreters, such as systemd way or direct/manual registration. diff --git a/etc/setup.d/15binfmt b/etc/setup.d/15binfmt index ad1776b2..ccd3776d 100644 |
Michael Tokarev <mjt@tls.msk.ru> | no | debian | 2021-02-28 | |
| 1660584747.reschroot-1.6.12-2-g6f7166a2.have-stricter-rules-on-chroot-names-cve-2022-2787.patch | Have stricter rules on chroot names [CVE-2022-2787] Commit 8c1c9370 ("sbuild::chroot_config: Replace is_valid_filename with is_valid_sessionname") introduced a very broad rule on the name of a chroot or session name. As it turned out, some of the allowed characters would break schroot's internal state, or would make the setup croak in various backends. This change limits the set of allowed characters to what seems to be safe: Letters and digits, and in all but the first place, the characters dot ('.'), dash ('-'), and underscore ('_'). Special thanks to Julian Gilbey <jdg@debian.org> for reporting the issue and providing additional insights about the severity. |
no | release/reschroot-1.6.12-2-g6f7166a2 | 2022-08-15 |