- libseccomp (2.5.5-2+rpi1) trixie-staging; urgency=medium
++libseccomp (2.6.0-2+rpi1) trixie-staging; urgency=medium
+
+ [changes brought forward from 2.4.1-2+rpi1 by Peter Michael Green <plugwash@raspbian.org> at Wed, 24 Jul 2019 22:12:36 +0000]
+ * Move valigrind from build-depends to build-conflicts, raspbians valgrind
+ is somewhat broken and causes testsuite failures.
+
- -- Raspbian forward porter <root@raspbian.org> Wed, 11 Dec 2024 14:41:02 +0000
++ -- Raspbian forward porter <root@raspbian.org> Fri, 28 Mar 2025 11:26:03 +0000
++
+ libseccomp (2.6.0-2) unstable; urgency=medium
+
+ * Upload to unstable.
+ * Disable valgrind unit tests, it's not stable enough.
+ * Cherry-pick upstream fixes:
+ - tests_remove_the_fuzzer_from_test_62-sim-arch_transactions.patch
+ - hash_fix_strict_aliasing_UB_in_MurMur_hash_implementation.patch
+ - api_fix_seccomp_export_bpf_mem_out-of-bounds_read.patch
+
+ -- Felix Geyer <fgeyer@debian.org> Thu, 20 Mar 2025 22:12:14 +0100
+
+ libseccomp (2.6.0-1) experimental; urgency=medium
+
+ * New upstream release. (Closes: #1088935)
+ * Drop backported loongarch64 patches, applied upstream.
+ * Drop python_Fix_distutils_DeprecationWarning.patch, applied upstream.
+ * Update symbols file.
+ * Fix watch file.
+ * Refresh upstream signing keys.
+ * Run unit tests in parallel.
+
+ -- Felix Geyer <fgeyer@debian.org> Fri, 24 Jan 2025 22:10:51 +0100
libseccomp (2.5.5-2) unstable; urgency=medium