Bug#864143: marked as done (initramfs-tools: missing dependency on busybox?)

Your message dated Mon, 05 Jun 2017 01:41:03 +0100 with message-id <1496623263.3477.3.ca...@decadent.org.uk> and subject line Re: Bug#864143: initramfs-tools: missing dependency on busybox? has caused the Debian Bug report #864143, regarding initramfs-tools: missing dependency on busybox? to be

Bug#863914: linux-libc-dev: Install separate from /usr/include

Control: tag -1 - moreinfo On Sun, 2017-06-04 at 09:14 -0400, Zack Weinberg wrote: > > On Sat, Jun 3, 2017 at 5:05 PM, Ben Hutchings wrote: > > > It would be much easier to arrange > > > this if the kernel's headers were installed in a location separate from > > >

Processed: Re: Bug#863914: linux-libc-dev: Install separate from /usr/include

Processing control commands: > tag -1 - moreinfo Bug #863914 [linux-libc-dev] linux-libc-dev: Install separate from /usr/include Removed tag(s) moreinfo. -- 863914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#863290: src:linux: no warning that btrfs RAID5/6 is buggered up

RAID1 actually needs a warning too. It will not work as "classic" RAID1 e.g. it need to be able to make two copies always to not get stuck in read only mode. You will not loose your data which is a good thing, but to be safe you need a minimum of 3 devices (I would prefer four or more to be on

Bug#863290: src:linux: no warning that btrfs RAID5/6 is buggered up

On 4 June 2017 at 05:46, Svein Engelsgjerd wrote: > > I would like voice my concern as well. Btrfs RAID5/6 really needs a warning. > These days most (if not all) of the problems you see with Btrfs is caused by > the unstable features

Bug#863914: linux-libc-dev: Install separate from /usr/include

On Sat, Jun 3, 2017 at 5:05 PM, Ben Hutchings wrote: >> It would be much easier to arrange >> this if the kernel's headers were installed in a location separate from >> /usr/include and then symlinked into /usr/include. (It would be fine to >> symlink just the directories.)

linux_4.9.30-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Jun 2017 03:03:01 +0100 Source: linux Binary: linux-source-4.9 linux-support-4.9.0-3 linux-doc-4.9 linux-manual-4.9 linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 libusbip-dev

Processing of linux_4.9.30-1_source.changes

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

Bug#863907: marked as done (Fix cross compilation build-dependencies for 4.9.x)

Your message dated Sun, 04 Jun 2017 11:50:04 + with message-id and subject line Bug#863907: fixed in linux 4.9.30-1 has caused the Debian Bug report #863907, regarding Fix cross compilation build-dependencies for 4.9.x to be marked as done. This means

Bug#862723: marked as done (Touchpad and keyboard are not detected on Acer Chromebook 14 with kernel 4.9)

Your message dated Sun, 04 Jun 2017 11:50:04 + with message-id and subject line Bug#862723: fixed in linux 4.9.30-1 has caused the Debian Bug report #862723, regarding Touchpad and keyboard are not detected on Acer Chromebook 14 with kernel 4.9 to be

Bug#863550: marked as done (linux: NFSv4 callback processes fills process table)

Your message dated Sun, 04 Jun 2017 11:50:03 + with message-id and subject line Bug#862357: fixed in linux 4.9.30-1 has caused the Debian Bug report #862357, regarding linux: NFSv4 callback processes fills process table to be marked as done. This means

Bug#862813: marked as done (linux: Please build loop-modules udeb on m68k)

Your message dated Sun, 04 Jun 2017 11:50:04 + with message-id and subject line Bug#862813: fixed in linux 4.9.30-1 has caused the Debian Bug report #862813, regarding linux: Please build loop-modules udeb on m68k to be marked as done. This means that you

Bug#863290: marked as done (src:linux: no warning that btrfs RAID5/6 is buggered up)

Your message dated Sun, 04 Jun 2017 11:50:04 + with message-id and subject line Bug#863290: fixed in linux 4.9.30-1 has caused the Debian Bug report #863290, regarding src:linux: no warning that btrfs RAID5/6 is buggered up to be marked as done. This

Bug#863344: marked as done (linux-image-4.9.0-3-arm64: qOAarm64 kernel missing some DRM modules)

Your message dated Sun, 04 Jun 2017 11:50:04 + with message-id and subject line Bug#863344: fixed in linux 4.9.30-1 has caused the Debian Bug report #863344, regarding linux-image-4.9.0-3-arm64: qOAarm64 kernel missing some DRM modules to be marked as

Bug#862555: marked as done (linux: please ship efivarfs into efi-modules)

Your message dated Sun, 04 Jun 2017 11:50:04 + with message-id and subject line Bug#862555: fixed in linux 4.9.30-1 has caused the Debian Bug report #862555, regarding linux: please ship efivarfs into efi-modules to be marked as done. This means that you

Bug#861898: marked as done (Please backport SPCR patch for ACPI console on arm64)

Your message dated Sun, 04 Jun 2017 11:50:03 + with message-id and subject line Bug#861898: fixed in linux 4.9.30-1 has caused the Debian Bug report #861898, regarding Please backport SPCR patch for ACPI console on arm64 to be marked as done. This means

Bug#843448: update with both patches applied

On Sun, 2017-06-04 at 13:33 +0200, Steinar H. Gunderson wrote: > On Tue, May 30, 2017 at 04:27:05PM +0800, gustavo panizzo wrote: > > I've attached the second patch. updated, for others to try. Vagrant, can you > > try this on your boards too? > > Given that stretch release is in only a few

Bug#843448: update with both patches applied

On Tue, May 30, 2017 at 04:27:05PM +0800, gustavo panizzo wrote: > I've attached the second patch. updated, for others to try. Vagrant, can you > try this on your boards too? Given that stretch release is in only a few weeks, time is running out for this bug. Is the general thought that the risk

Bug#864143: initramfs-tools: missing dependency on busybox?

Package: initramfs-tools Version: 0.130 Severity: normal Dear Maintainer, initramfs-tools-core recommends busybox, but it appears to be required. I got this with an update after it was removed: Processing triggers for initramfs-tools (0.130) ... update-initramfs: Generating

Bug#711450: marked as done (debian-kernel-handbook: Possible typo in example on Chapter 6)

Your message dated Sun, 04 Jun 2017 12:17:47 +0100 with message-id <1496575067.3992.64.ca...@decadent.org.uk> and subject line Re: debian-kernel-handbook: Possible typo in example on Chapter 6 has caused the Debian Bug report #711450, regarding debian-kernel-handbook: Possible typo in example on

Bug#683026: marked as done ([debian-kernel-handbook] deb-pkg builds amd64 image package on i386)

Your message dated Sun, 04 Jun 2017 12:14:55 +0100 with message-id <1496574895.3992.62.ca...@decadent.org.uk> and subject line Re: [debian-kernel-handbook] deb-pkg builds amd64 image package on i386 has caused the Debian Bug report #683026, regarding [debian-kernel-handbook] deb-pkg builds amd64

Re: Enlighten me, please.

On Sun, Jun 4, 2017 at 3:40 AM, Ben Hutchings wrote: > On Sun, 2017-06-04 at 03:23 -0700, Jose R R wrote: >> Niltze [Hello], Konstantin- >> >> I am relatively new to git. >> >> Will you be so kind (if you know, of course) to convey how to checkout >> a particular tag --and

Bug#782784: marked as done (debian-kernel-handbook: Please package debian-kernel-handbook 1.0.16)

Your message dated Sun, 04 Jun 2017 11:46:50 +0100 with message-id <1496573210.3992.60.ca...@decadent.org.uk> and subject line Re: debian-kernel-handbook: Please package debian-kernel-handbook 1.0.16 has caused the Debian Bug report #782784, regarding debian-kernel-handbook: Please package

Re: Enlighten me, please.

On Sun, 2017-06-04 at 03:23 -0700, Jose R R wrote: > Niltze [Hello], Konstantin- > > I am relatively new to git. > > Will you be so kind (if you know, of course) to convey how to checkout > a particular tag --and subsequent branch-- of debian experimental > kernel package? > > In the past I

Enlighten me, please.

Niltze [Hello], Konstantin- I am relatively new to git. Will you be so kind (if you know, of course) to convey how to checkout a particular tag --and subsequent branch-- of debian experimental kernel package? In the past I have downloaded Sid branch (according to Kernel Handbook) thus: git

Bug#863290: src:linux: no warning that btrfs RAID5/6 is buggered up

Package: src:linux Followup-For: Bug #863290 Dear Maintainer, I would like voice my concern as well. Btrfs RAID5/6 really needs a warning. These days most (if not all) of the problems you see with Btrfs is caused by the unstable features (https://btrfs.wiki.kernel.org/index.php/Status). RAID5/6