Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
1662655911.reschroot-1.6.13-2-g779349dc.replace-usage-of-egrep-and-which.patch | Replace usage of egrep and which Debian bug: https://bugs.debian.org/1019295 |
no | release/reschroot-1.6.13-2-g779349dc <https://codeberg.org/shelter/reschroot/commit/779349dc> | 2022-09-08 | ||
1539621689.revert.schroot-1.6.10-48-g2600bcab.revert-environment-preserve-empty-values.patch | Revert "environment: Preserve empty values" Upstream commit 2600b ("environment: Preserve empty values") causes the Debian build to fail in the test suite. Revert that change for the time being and investigate later. The failing test: test 2 Start 2: sbuild-chroot-chroot 2: Test command: /<<PKGBUILDDIR>>/debian/build/test/sbuild-chroot-chroot 2: Test timeout computed to be: 10000000 2: .........................Additional environment: CHROOT_BTRFS_SNAPSHOT_NAME= 2: F..........................................................................................Additional environment: CHROOT_LVM_SNAPSHOT_DEVICE= 2: Additional environment: CHROOT_LVM_SNAPSHOT_NAME= 2: F.................. 2: 2: 2: !!!FAILURES!!! 2: Test Results: 2: Run: 133 Failures: 2 Errors: 0 2: 2: 2: 1) test: test_chroot_btrfs_snapshot::test_setup_env (F) line: 412 ./test/test-sbuild-chroot.h 2: assertion failed 2: - Expression: extra.empty() 2: 2: 2: 2) test: test_chroot_lvm_snapshot::test_setup_env (F) line: 412 ./test/test-sbuild-chroot.h 2: assertion failed 2: - Expression: extra.empty() 2: 2: 2/8 Test #2: sbuild-chroot-chroot .............***Failed 0.05 sec |
Christoph Biedl <debian.axhn@manchmal.in-ulm.de> | not-needed | 2022-05-29 | ||
1448890714.schroot-1.7.2-72-gbf30a928.setup-d-20copyfiles-canonicalize-destination-path.patch | Setup.d: 20copyfiles: canonicalize destination path When parts of the destination path are symlinks, these symlinks are followed in the context of the host filesystem instead of the context of the chroot filesystem. This patch should fix it. |
no | release/schroot-1.7.2-72-gbf30a928 <https://codeberg.org/shelter/reschroot/commit/bf30a928> | 2015-11-30 | ||
1453505583.schroot-1.7.2-72-g11587fd8.etc-setup-d-20copyfiles-replace-dangling-symlink-during-cp.patch | Etc/setup.d/20copyfiles: Replace dangling symlink during cp. #1 Add --remove-destination to the cp calls in etc/setup.d/20copyfiles to fix problems with dangling symlinks. Error message from cp is: cp: not writing through dangling symlink ‘asymlinkfile’ This is useful since /etc/resolv.conf may be a dangling symlink ( which happens if resolvconf is installed in the schroot, or if the schroot uses systemd and /etc/resolv.conf points to the non-existant /run/systemd/resolve/resolv.conf ). Adding --remove-destination fixes this. (cp -f doesn't fix it.) |
no | release/schroot-1.7.2-72-g11587fd8 <https://codeberg.org/shelter/reschroot/commit/11587fd8> | 2016-01-22 | ||
1496783678.schroot-1.7.2-127-ga5e5d8d9.fix-bash-completion.patch | Fix bash completion | not-needed | debian | release/schroot-1.7.2-127-ga5e5d8d9 | 2017-06-06 | |
1530433671.schroot-1.7.2-129-g00c0a972.cmake-use-soelim-r-option.patch | Cmake: Use soelim -r option While non-portable, it's implemented as a no-op in BSD soelim, and is useful for reproducible builds. |
no | release/schroot-1.7.2-129-g00c0a972 | 2018-07-01 | ||
1487872945.schroot-1.7.2-137-g5c36362b.support-copyfiles-installation-into-non-existent-directories.patch | Support copyfiles installation into non-existent directories Trying to copy a file into a non-existent directory is currently fatal, and thus makes the whole schroot invocation fail. This means one cannot unconditionally add files if the chroot is possibly not going to have the containing directory. |
no | release/schroot-1.7.2-137-g5c36362b <https://codeberg.org/shelter/reschroot/commit/5c36362b> | 2017-02-23 | ||
1487872999.schroot-1.7.2-138-g5a611c49.support-copyfiles-source-destination-specifications.patch | Support copyfiles <source> <destination> specifications This makes it possible to store local files in the schroot configuration directory that will get installed on the chroot. For example a local policy-rc.d script. |
no | release/schroot-1.7.2-138-g5a611c49 <https://codeberg.org/shelter/reschroot/commit/5a611c49> | 2017-02-23 | ||
1662656169.reschroot-1.6.13-3-ga9e100e5.clean-up-mess-created-in-the-portuguese-translations.patch | Clean up mess created in the Portuguese translations Thanks Américo Monteiro <a_monteiro@gmx.com> for sorting things out. Debian bug: https://bugs.debian.org/965348 |
no | release/reschroot-1.6.13-3-ga9e100e5 <https://codeberg.org/shelter/reschroot/commit/a9e100e5> | 2022-09-08 | ||
1664011392.reschroot-1.6.13-4-g93017cff.update-french-translation.patch | Update French translation Thanks Martin Quinson <Martin.Quinson@ens-rennes.fr> Debian bug: https://bugs.debian.org/1020255 |
no | release/reschroot-1.6.13-4-g93017cff <https://codeberg.org/shelter/reschroot/commit/93017cff> | 2022-09-24 | ||
1658716738.reschroot-1.6.12-2-g2045008e.fix-variable-usage-in-copyfiles-copy-file-function.patch | Fix variable usage in copyfiles copy_file() function <https://codeberg.org/shelter/reschroot/commit/2045008e614229fffeca4b1a3f8915c8bb7bdebc> The function was using $file to refer to the source file of the copy, instead of $1. This happens to currently work because in shell the function has access to the global variables defined from the call site, but this makes it dependent on the global state and the call site semantics. If these variables change name then this specific code will stop working, which will be the case with the upcoming source and optional destination specification in copyfiles. |
no | release/reschroot-1.6.12-2-g2045008e | 2022-07-25 |