- systemd (241-7~deb10u6+rpi1) buster-staging; urgency=medium
++systemd (241-7~deb10u7+rpi1) buster-staging; urgency=medium
+
+ [changes brought forward from 239-9+rpi1 by Peter Michael Green <plugwash@raspbian.org> at Thu, 20 Sep 2018 20:22:45 +0000]
+ * Disable testsuite, it fails on some of our buildboxes (probablly because of
+ old kernels).
+ * Add breaks on raspi-copies-and-fills, it doesn't seem to get on with
+ this version of systemd/udev.
+
+ [changes brought forward from 239-9+rpi2 by Peter Michael Green <plugwash@raspbian.org> at Thu, 20 Sep 2018 22:47:19 +0000]
+ * Force build with gcc-7 (LP: #1793415)
+
+ [changes brought forward from 241-1+rpi2 by Peter Michael Green <plugwash@raspbian.org> at Tue, 02 Apr 2019 19:29:26 +0000]
+ * Bump "breaks" on raspi-copies-and-fills to << 0.12
+ (raspi-copies-and-fills was reverted by the raspberry pi foundation)
+
- -- Raspbian forward porter <root@raspbian.org> Sun, 07 Feb 2021 22:54:50 +0000
++ -- Raspbian forward porter <root@raspbian.org> Thu, 01 Apr 2021 12:57:10 +0000
++
+ systemd (241-7~deb10u7) buster; urgency=medium
+
+ * core: make sure to restore the control command id, too.
+ Fixes a segfault in systemd that can be triggered when both
+ daemon-reload and a service restart happen concurrently. (Closes: #984495)
+ * seccomp: allow turning off of seccomp filtering via env var.
+ Since glibc 2.33 faccessat() is implemented via faccessat2(), which
+ is breaking running containers that use such a version of glibc under
+ systemd-nspawn in Buster.
+ Turning off seccomp filtering via the SYSTEMD_SECCOMP env var makes it
+ possible to run such new containers. (Closes: #984573)
+
+ -- Michael Biebl <biebl@debian.org> Thu, 18 Mar 2021 20:59:14 +0100
systemd (241-7~deb10u6) buster; urgency=medium
projects / systemd.git / commitdiff