| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| Correct-parameter-name-when-documenting-psplash-pipe-in-t.patch | Correct parameter name when documenting --psplash-pipe in the man page | Simon McVittie <smcv@debian.org> | yes | 2021-02-03 | ||
| Expand-documentation-of-psplash-pipe-to-specify-what-is-r.patch | Expand documentation of --psplash-pipe to specify what is reported | Simon McVittie <smcv@debian.org> | yes | 2021-02-03 | ||
| TransRead-kill-subprocesses.patch | TransRead: kill subprocesses Kill and wait for subprocesses when destroying TransRead objects. This gets rid of the following warning (observed when running self-tests): /usr/lib64/python3.9/subprocess.py:1048: ResourceWarning: subprocess 140912 is still running _warn("subprocess %s is still running" % self.pid, |
Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | no | upstream, 3.7, commit:d17e2eaea318444c7370298739da3c5a3969cc6d | 2021-03-10 | |
| Do-not-use-subprocess-pipe.patch | Do not use subprocess pipe We use the 'subprocess' module for running external processes, and in few places we create sub-processes with the 'stderr=subprocess.PIPE' argument. Howerver, we never read from the pipe, which means that it may get filled and block the external program. This is dangerous and may lead to deadlock situations. This patch fixes the issue by removing the argument. If we do not read sub-process's 'stderr', it is OK for it to inherit it from the main program, so the error message will just go to bmaptool's standare error stream. |
Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | no | upstream, 3.7, commit:d77f3e9a6e496ba8d460f27bfef02aec45181b78 | 2021-03-10 | |
| TransRead-hide-useless-message.patch | TransRead: hide useless message The previous patch (stop using 'subprocess.PIPE') addes a side-effect - now we see 'tar' the following tar message: This patch gets rid of them. |
Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | no | upstream, 3.7, commit:f41e5529471ff94fc84280338a0e13e4862daa63 | 2021-03-10 | |
| tests-fix-test_bmap_helpers-on-non-ZFS.patch | tests: fix test_bmap_helpers on non-ZFS One test failed when running with on a system that does not have ZFS. |
Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | no | upstream, 3.7, commit:3a84ba28364c5686b6b1ce0742a4b70d8f8b37c3 | 2021-03-11 | |
| tests-Use-unittest.mock-from-Python-standard-library-if-p.patch | tests: Use unittest.mock from Python standard library if possible This avoids an unnecessary external dependency when using Python >= 3.3. |
Simon McVittie <smcv@debian.org> | yes | 2021-10-28 | ||
| tests-Try-to-use-TemporaryDirectory-from-Python-standard-.patch | tests: Try to use TemporaryDirectory from Python standard library This avoids an unnecessary external dependency with Python >= 3.2. |
Simon McVittie <smcv@debian.org> | yes | 2021-10-28 | ||
| tests-Pass-c-k-options-to-zstd-too.patch | tests: Pass -c -k options to zstd, too Otherwise we get interactive prompts during testing, like this: zstd: /*stdin*\: unexpected end of file zstd: /*stdin*\: unexpected end of file zstd: /*stdin*\: unexpected end of file zstd: /*stdin*\: unexpected end of file zstd: .../.pybuild/cpython3_3.9/build/4Khole_idts5mgb.img.zst already exists; overwrite (y/n) ? |
Simon McVittie <smcv@debian.org> | yes | 2021-10-28 | ||
| tests-Fix-import-pattern-for-mock-objects.patch | tests: Fix import pattern for mock objects The legacy mock module contains a mock.mock submodule, but unittest.mock does not contain a redundant unittest.mock.mock. This bug was masked by the transparent fallback to the legacy mock module. The actual test only uses mock.patch(), so we can simplify by just importing the one member that we need. |
Simon McVittie <smcv@debian.org> | yes | 2021-10-28 |