| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| configure-use-pkg-config-with-newer-gpgme-and-gpg-error.patch | configure: use pkg-config with newer gpgme and gpg-error This tweaks autoconf logic in order to use pkg-config for gpgme and gpg-error when available. Recent versions of gpgme directly provide threaded support, and gpg-error started shipping a .pc file. Thus on recent distributions it is possible to directly use pkg-config for both. On older environments, the legacy logic is kept in place. |
Luca BRUNO <luca.bruno@coreos.com> | yes | 2022-11-24 | ||
| curl-Assert-that-curl_multi_assign-worked.patch | curl: Assert that curl_multi_assign worked ref https://github.com/ostreedev/ostree/issues/3299 This won't fix that issue, but *if* this assertion triggers it should give us a better idea of the possible codepaths where it is happening. |
Colin Walters <walters@verbum.org> | no | debian | upstream, 2024.8, commit:472d9d493a3e4a08415da4c337a7e831e0c5a5e2 | 2024-09-18 |
| curl-Make-socket-callback-during-cleanup-into-no-op.patch | curl: Make socket callback during cleanup into no-op Because curl_multi_cleanup may invoke callbacks, we effectively have some circular references going on here. See discussion in https://github.com/curl/curl/issues/14860 Basically what we do is the socket callback libcurl may invoke into a no-op when we detect we're finalizing. The data structures are owned by this object and not by the callbacks, and will be destroyed below. Note that e.g. g_hash_table_unref() may itself invoke callbacks, which is where some data is cleaned up. [smcv: Backport to 2022.7 by using gboolean instead of stdbool.h] |
Colin Walters <walters@verbum.org> | yes | debian upstream | upstream, 2024.8, commit:4d755a85225ea0a02d4580d088bb8a97138cb040 | 2024-09-18 |
| debian/Skip-test-pull-repeated-during-CI.patch | Skip test-pull-repeated during CI This test is expected to fail a small proportion of the time. During the build of ostree 2018.7-1 in Debian, it seems we were unlucky on s390x. Non-deterministic tests are also problematic for autopkgtest, where they can gate migration of our dependencies like GLib, so skip this test unless the caller has opted-in to non-deterministic tests. It would be appropriate to enable this test in environments where failures can easily be retried and are not disruptive to other packages. |
Simon McVittie <smcv@debian.org> | no | 2018-07-30 | ||
| debian/test-sysroot-Skip-on-s390x-by-default.patch | test-sysroot: Skip on s390x by default This test regularly fails on the buildds, but I cannot reproduce the failure on a porterbox. |
Simon McVittie <smcv@debian.org> | not-needed | debian upstream | 2022-12-06 |