Bug#916670: cryptsetup doesn't work in buster

I have the same problem (though note that the configure script does in fact exit without an error despite printing the error to the console. I have to use dpkg-reconfigure to reproduce the error. I assume my system isn't bootable but I'm not eager to test this): root@tweedle:~# dpkg-reconfigure

Processed: reassign 942301 to src:linux-latest, forcibly merging 941042 942301

Processing commands for cont...@bugs.debian.org: > reassign 942301 src:linux-latest Bug #942301 [src:liux-latest] linux-image-amd64: dep linux-image-5.2.0-0.bpo.3-amd64 not available in buster-backports Warning: Unknown package 'src:liux-latest' Bug reassigned from package 'src:liux-latest' to

Processed (with 1 error): tagging 942301, reassign 942301 to src:liux-latest, forcibly merging 941042 942301

Processing commands for cont...@bugs.debian.org: > tags 942301 - a11y Bug #942301 [linux-image-amd64] linux-image-amd64: dep linux-image-5.2.0-0.bpo.3-amd64 not available in buster-backports Removed tag(s) a11y. > reassign 942301 src:liux-latest Bug #942301 [linux-image-amd64] linux-image-amd64:

Bug#940820: UML not loading on Debian buster with a 5.2 kernel from testing

This is a regression in the randomization of the va setting. UML will boot on debian 4.19 kernel host  with kernel.randomize_va_space = 2 UML will not boot debian 5.2 kernel host with kernel.randomize_va_space = 2 UML will boot on 5.2 once kernel.randomize_va_space is set to 0 on the host. So

Bug#898060: Stall NFS clients: RPC request reserved 84 but used 272

Hi, two months ago we upgrade to Debian 10 and since then the issue vanished ... Regards! Guido

linux-signed-arm64_5.2.17+1~bpo10+1_source.changes ACCEPTED into buster-backports, buster-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Sep 2019 16:38:54 +0100 Source: linux-signed-arm64 Binary: kernel-image-5.2.0-0.bpo.3-arm64-di nic-modules-5.2.0-0.bpo.3-arm64-di nic-wireless-modules-5.2.0-0.bpo.3-arm64-di

linux-signed-i386_5.2.17+1~bpo10+1_source.changes ACCEPTED into buster-backports, buster-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Sep 2019 16:38:54 +0100 Source: linux-signed-i386 Binary: kernel-image-5.2.0-0.bpo.3-686-di nic-modules-5.2.0-0.bpo.3-686-di nic-wireless-modules-5.2.0-0.bpo.3-686-di nic-shared-modules-5.2.0-0.bpo.3-686-di

linux-signed-amd64_5.2.17+1~bpo10+1_source.changes ACCEPTED into buster-backports, buster-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 Sep 2019 16:38:54 +0100 Source: linux-signed-amd64 Binary: kernel-image-5.2.0-0.bpo.3-amd64-di nic-modules-5.2.0-0.bpo.3-amd64-di nic-wireless-modules-5.2.0-0.bpo.3-amd64-di

Bug#940848: nfs-utils:CVE-2019-3689: root-owned files stored in insecure /var/lib/nfs

Hi, Incidentally I contacted SuSE security who agreed that fs.protected_symlinks is not a valid mitigation (they will update MITRE). I also improved the piuparts check: #!/bin/sh -ex if [ -e /var/lib/nfs ]; then     ls -ld /var/lib/nfs     ls -ld /var/lib/nfs/sm     if [ "$(dpkg -l | grep '

Bug#942301: linux-image-amd64: dep linux-image-5.2.0-0.bpo.3-amd64 not available in buster-backports

Package: linux-image-amd64 Version: 5.2+106~bpo10+1 Severity: important Tags: a11y Dear Maintainer, When backports are enabled, running apt update shows that linux-image-amd64 can be upgraded, but upgrading fails. See also: https://packages.debian.org/buster-backports/linux-image-amd64

Bug#887045: still getting this warning occasionally

linux-image-4.19.0-6-amd64 (4.19.67-2+deb10u1) [237004.349757] [ cut here ] [237004.349843] WARNING: CPU: 0 PID: 391 at drivers/net/wireless/intel/ iwlwifi/mvm/tx.c:1434 iwl_mvm_rx_tx_cmd.cold.32+0x11/0x27 [iwlmvm] [237004.349846] Modules linked in: devlink nf_tables