| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0006-Use-bash-for-test-script-portablitity.patch | Use bash for test script portablitity | Kevin Murray <spam@kdmurray.id.au> | no | 2016-11-14 | ||
| 0008-Address-embedded-zlib.patch | Do not build zlibWrapper examples against embedded code copies. | Sascha Steinbiss <satta@debian.org> | no | |||
| 0013-skip-memory-greedy-tests.patch | Skip memory heavy tests causing FTBFS on mips(el) and hurd buildds | Alex Mestiashvili <mestia@debian.org> | no | |||
| 0014-Reproducible-build.patch | Make the build reproducible | Chris Lamb <lamby@debian.org> | no | 2018-05-04 | ||
| 0015-Skip-dev-random-tests-on-hurd.patch | Skip test failing on GNU/Hurd when writing on /dev/zero or /dev/random. On different GNU/Hurd installations writing to either one or another would fail. Currently writing to /dev/random results in the message "Computer bought the farm" and exit status 1 See also: https://github.com/facebook/zstd/issues/1116 |
Alex Mestiashvili <mestia@debian.org> | no | |||
| 0017-alpha-fbfs-st_mtime.patch | Fix ftbfs on alpha, see #962676 | Helmut Grohne <helmut@subdivi.de> | no | |||
| 0018-kfreebsd-ftbfs-utime-now.patch | Fix the build on kFreeBSD - no UTIME_NOW. | Peter Pentchev <roam@ringlet.net> | no | 2023-02-13 | ||
| 0019-upstream-fix-cli-tests.patch | fix cli-tests issues | Danielle Rozenblit <drozenblit@fb.com> | no | upstream; https://github.com/facebook/zstd/commit/7da1c6ddbfe61ad2f9bc9c3a2205567a76be24f5 | 2023-03-08 | |
| 0020-upstream-fix-block-splitter.patch | Fix rare corruption bug affecting the block splitter The block splitter confuses sequences with literal length == 65536 that use a repeat offset code. It interprets this as literal length == 0 when deciding the meaning of the repeat offset, and corrupts the repeat offset history. This is benign, merely causing suboptimal compression performance, if the confused history is flushed before the end of the block, e.g. if there are 3 consecutive non-repeat code sequences after the mistake. It also is only triggered if the block splitter decided to split the block. . All that to say: This is a rare bug, and requires quite a few conditions to trigger. However, the good news is that if you have a way to validate that the decompressed data is correct, e.g. you've enabled zstd's checksum or have a checksum elsewhere, the original data is very likely recoverable. So if you were affected by this bug please reach out. . The fix is to remind the block splitter that the literal length is actually 64K. The test case is a bit tricky to set up, but I've managed to reproduce the issue. |
Nick Terrell <terrelln@meta.com> | no | upstream, https://github.com/facebook/zstd/commit/395a2c54621d36b4eaf17b4111353243f91a1d90 | 2023-02-22 | |
| 0021-tests-newline.patch | Fix splitting test output into newlines | Peter Pentchev <roam@ringlet.net> | yes | 2023-03-18 | ||
| 0022-tests-timeout.patch | Raise the timeout for test commands to 10 minutes Some of the tests, e.g. the window-resize one, may take a long time on busy builder hosts. |
Peter Pentchev <roam@ringlet.net> | no | debian | 2023-03-18 |