Bug#857686: (no subject)

But why? The kernel image is was built, the headers, everything - only the dependency packages wasn't built. So was it intentionally not built?

Bug#857686: marked as done (linux-image-marvell for jessie-backports release 4.9+79~bpo8+1 not properly released)

Your message dated Mon, 13 Mar 2017 23:25:47 + with message-id <1489447547.2852.9.ca...@decadent.org.uk> and subject line Re: Bug#857686: linux-image-marvell for jessie-backports release 4.9+79~bpo8+1 not properly released has caused the Debian Bug report #857686, regarding linux-image-marvell

Bug#857686: linux-image-marvell for jessie-backports release 4.9+79~bpo8+1 not properly released

Package: linux-image-marvell Version: 4.9+78~bpo8+1 The package linux-image-marvell for jessie-backports is in a broken state, as can be seen on the debian package website: https://packages.debian.org/jessie-backports/linux-image-marvell it shows version "4.9+78~bpo8+1" and a dependency on "li

Bug#738063: nfs-kernel-server: option to disable NFSv4 in /etc/default/nfs-kernel-server not working properly

On Thu, 2 Feb 2017 21:55:28 -0800 Nye Liu wrote: > This bug is still not fixed. > > In addition, it doesn't appear as though "-V 2" will enable NFSv2, which seems to > be disabled by default now. Even worse, the old nfs-common script would automatically enable statd, idmapd, and gssd if neede

Processed: tagging 857608

Processing commands for cont...@bugs.debian.org: > tags 857608 + wontfix Bug #857608 {Done: Ben Hutchings } [linux-image-4.9.0-2-rt-amd64-unsigned] linux-image-4.9.0-2-rt-amd64-unsigned: please build with CONFIG_LATENCYTOP Added tag(s) wontfix. > thanks Stopping processing here. Please contact

Bug#857608: marked as done (linux-image-4.9.0-2-rt-amd64-unsigned: please build with CONFIG_LATENCYTOP)

Your message dated Mon, 13 Mar 2017 14:27:34 + with message-id <1489415254.2852.4.ca...@decadent.org.uk> and subject line Re: Bug#857608: linux-image-4.9.0-2-rt-amd64-unsigned: please build with CONFIG_LATENCYTOP has caused the Debian Bug report #857608, regarding linux-image-4.9.0-2-rt-amd64-

Processed: severity of 857624 is normal

Processing commands for cont...@bugs.debian.org: > severity 857624 normal Bug #857624 [src:linux] kernel warning/backtrace in parport/ppdev when running as a VM Severity set to 'normal' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 857624: http

Bug#857624: kernel warning/backtrace in parport/ppdev when running as a VM

Package: src:linux Version: 4.9.13-1 Severity: important Booting a freshly installed stretch system under (jessie's) qemu-kvm results in a couple of kernel warnings related to parport on every boot. I've experienced this on a few different systems now, in different infrastructures, so I'm guessing

Bug#857608: linux-image-4.9.0-2-rt-amd64-unsigned: please build with CONFIG_LATENCYTOP

Package: linux-image-4.9.0-2-rt-amd64-unsigned Version: 4.9.13-1 Dear maintainer, the Debian kernels are currently built without the CONFIG_LATENCYTOP option: $ grep LATENCYTOP /boot/config-4.9.0-2-* /boot/config-4.9.0-2-amd64:# CONFIG_LATENCYTOP is not set /boot/config-4.9.0-2-rt-amd64:# CONFI

Processed: tagging 846792

Processing commands for cont...@bugs.debian.org: > tags 846792 - pending Bug #846792 [src:linux] linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 846792: http://bugs.debian.org/