- ostree (2023.8-2+rpi1) trixie-staging; urgency=medium
++ostree (2024.8-1+rpi1) trixie-staging; urgency=medium
+
+ [changes brought forward from 2020.8-2+rpi1 by Peter Michael Green <plugwash@raspbian.org> at Tue, 15 Dec 2020 11:54:45 +0000]
+ * Disable testsuite.
+
- -- Raspbian forward porter <root@raspbian.org> Wed, 10 Jan 2024 04:32:00 +0000
++ -- Raspbian forward porter <root@raspbian.org> Thu, 03 Oct 2024 10:58:28 +0000
++
+ ostree (2024.8-1) unstable; urgency=medium
+
+ * New upstream release
+ * d/p/curl-Assert-that-curl_multi_assign-worked.patch,
+ d/p/curl-Make-socket-callback-during-cleanup-into-no-op.patch:
+ Drop patches that were included in the new upstream release
+
+ -- Simon McVittie <smcv@debian.org> Sat, 21 Sep 2024 18:49:10 +0100
+
+ ostree (2024.7-3) unstable; urgency=high
+
+ * d/p/curl-Assert-that-curl_multi_assign-worked.patch,
+ d/p/curl-Make-socket-callback-during-cleanup-into-no-op.patch:
+ Add patches from upstream to avoid libflatpak crash with curl 8.10.x
+ (Closes: #1082121)
+ * d/copyright: Remove obsolete stanzas
+ * Standards-Version: 4.7.0 (no changes required)
+ * Set high urgency since the version of libcurl that triggered the
+ regression has already migrated
+
+ -- Simon McVittie <smcv@debian.org> Thu, 19 Sep 2024 09:57:08 +0100
+
+ ostree (2024.7-2) unstable; urgency=medium
+
+ * d/control, d/rules: Disable gjs-based tests on armel.
+ It's looking as though mozjs128, and therefore the next gjs release,
+ will not support armel due to its lack of atomic instructions causing
+ relatively basic features to be disabled. (Helps: #1080521)
+
+ -- Simon McVittie <smcv@debian.org> Fri, 06 Sep 2024 18:16:11 +0100
+
+ ostree (2024.7-1) unstable; urgency=medium
+
+ * New upstream release
+ - debian/libostree-1-1.symbols: Update
+
+ -- Simon McVittie <smcv@debian.org> Mon, 22 Jul 2024 10:21:26 +0100
+
+ ostree (2024.6-1) unstable; urgency=medium
+
+ * New upstream release
+ * d/rules: Disable libcomposefs support.
+ libcompose is not yet packaged in Debian (RFP: #1064457) and there
+ is no longer a vendored copy included in ostree. I am not able to
+ take responsibility for maintenance of libcompose, but I have no
+ objection to re-enabling the relevant libostree features if someone
+ else packages it.
+
+ -- Simon McVittie <smcv@debian.org> Sat, 08 Jun 2024 16:06:43 +0100
+
+ ostree (2024.5-1) unstable; urgency=medium
+
+ * New upstream release
+
+ -- Simon McVittie <smcv@debian.org> Tue, 26 Mar 2024 16:15:22 +0000
+
+ ostree (2024.4-1) unstable; urgency=medium
+
+ * New upstream release
+ * Drop non-Debian-specific patches, applied upstream
+
+ -- Simon McVittie <smcv@debian.org> Thu, 07 Mar 2024 10:54:27 +0000
+
+ ostree (2024.3-1) unstable; urgency=medium
+
+ * New upstream release
+ * d/p/tests-Generalize-has_gpgme-has_sign_ed25519-into-has_ostr.patch,
+ d/p/tests-Use-skip_without_ostree_feature-to-detect-libarchiv.patch,
+ d/p/test-admin-deploy-var-Don-t-rely-on-OSTREE_FEATURES.patch:
+ Add proposed patches to fix an autopkgtest failure
+
+ -- Simon McVittie <smcv@debian.org> Mon, 19 Feb 2024 21:02:32 +0000
+
+ ostree (2024.2-1) unstable; urgency=medium
+
+ * New upstream release
+ * Re-enable composefs.
+ We can't run its unit tests on a Debian 12 kernel with /var/tmp on
+ tmpfs, but they do pass on a sid kernel or if /var/tmp is disk-backed.
+ * Build-depend on dh-sequence-gir instead of using --with
+ * Update Lintian overrides for ostree-boot
+
+ -- Simon McVittie <smcv@debian.org> Sun, 11 Feb 2024 14:42:35 +0000
+
+ ostree (2024.1-1) unstable; urgency=medium
+
+ * New upstream release
+ * Package ostree-state-overlay@.service in ostree-boot
+
+ -- Simon McVittie <smcv@debian.org> Wed, 24 Jan 2024 10:21:50 +0000
ostree (2023.8-2) unstable; urgency=medium
projects / ostree.git / commitdiff