Package: ostree / 2022.7-2+deb12u1

Metadata

Package Version Patches format
ostree 2022.7-2+deb12u1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
configure use pkg config with newer gpgme and gpg error.patch | (download)

configure.ac | 25 19 + 6 - 0 !
src/libostree/ostree-repo.c | 2 2 + 0 - 0 !
2 files changed, 21 insertions(+), 6 deletions(-)

 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.

curl Assert that curl_multi_assign worked.patch | (download)

src/libostree/ostree-fetcher-curl.c | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 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.

Signed-off-by: Colin Walters <walters@verbum.org>
curl Make socket callback during cleanup into no op.patch | (download)

src/libostree/ostree-fetcher-curl.c | 14 14 + 0 - 0 !
1 file changed, 14 insertions(+)

 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.

Signed-off-by: Colin Walters <walters@verbum.org>
debian/Skip test pull repeated during CI.patch | (download)

tests/test-pull-repeated.sh | 4 4 + 0 - 0 !
1 file changed, 4 insertions(+)

 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.

Signed-off-by: Simon McVittie <smcv@debian.org>

debian/test sysroot Skip on s390x by default.patch | (download)

tests/test-sysroot.js | 5 5 + 0 - 0 !
1 file changed, 5 insertions(+)

 test-sysroot: skip on s390x by default

This test regularly fails on the buildds, but I cannot reproduce the
failure on a porterbox.

Bug: https://github.com/ostreedev/ostree/issues/2527
Bug-Debian: https://bugs.debian.org/1025532