Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

Am 25.02.2018 um 23:22 schrieb Pascal Hambourg: > Package: udev > Version: 232-25+deb9u1 > > This a follow-up to bug #855798 "udev: MemoryDenyWriteExecute=yes should > not be applied to udev plugins" which was closed because the affected > program was not part of Debian. Now it seems that gzip is

Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

Package: udev Version: 232-25+deb9u1 This a follow-up to bug #855798 "udev: MemoryDenyWriteExecute=yes should not be applied to udev plugins" which was closed because the affected program was not part of Debian. Now it seems that gzip is also affected by MemoryDenyWriteExecute=yes when run by

Accepted systemd 237-3~bpo9+1 (source) into stretch-backports

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Feb 2018 18:22:14 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve libnss-systemd

systemd_237-3~bpo9+1_source.changes ACCEPTED into stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Feb 2018 18:22:14 +0100 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve

Processing of systemd_237-3~bpo9+1_source.changes

systemd_237-3~bpo9+1_source.changes uploaded successfully to localhost along with the files: systemd_237-3~bpo9+1.dsc systemd_237-3~bpo9+1.debian.tar.xz systemd_237-3~bpo9+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

On Tue, 20 Feb 2018 19:38:08 +0100 Gert Wollny wrote: > Am Dienstag, den 20.02.2018, 15:31 +0100 schrieb Michael Biebl: > > > > > Kernel: Linux 4.15.1-cm-fx6-my (SMP w/4 CPU cores; PREEMPT) > > > > > > Does this also happen with a Debian provided kernel? If so, which > >

Processed: forcibly merging 887343 890095

Processing commands for cont...@bugs.debian.org: > forcemerge 887343 890095 Bug #887343 {Done: Michael Biebl } [systemd] systemd-timesyncd does not start with DynamicUser=yes Bug #50 {Done: Michael Biebl } [systemd] systemd-timesyncd fails to start Bug

Bug#880158: marked as done (systemd-container: machinectl incorrectly reports "No machines." when using --no-legend)

Your message dated Sun, 25 Feb 2018 15:02:18 + with message-id and subject line Bug#880158: fixed in systemd 232-25+deb9u2 has caused the Debian Bug report #880158, regarding systemd-container: machinectl incorrectly reports "No machines." when using