linux-signed_2.8_source.changes ACCEPTED into unstable

2016-10-20 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Oct 2016 00:55:00 +0100 Source: linux-signed Binary: kernel-image-4.7.0-1-amd64-di nic-modules-4.7.0-1-amd64-di nic-wireless-modules-4.7.0-1-amd64-di nic-shared-modules-4.7.0-1-amd64-di

Bug#841453: marked as done (linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty)

2016-10-20 Thread Debian Bug Tracking System
Your message dated Fri, 21 Oct 2016 04:26:45 + with message-id and subject line Bug#841453: fixed in linux-signed 2.8 has caused the Debian Bug report #841453, regarding linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove

Processed: Re: Bug#841261: ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard

2016-10-20 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:linux 4.8~rc8-1~exp1 Bug #841261 [ulogd2] ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard Bug reassigned from package 'ulogd2' to 'src:linux'. No longer marked as found in versions ulogd2/2.0.4-2+deb8u1. Ignoring

Re: Bug#841261: ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard

2016-10-20 Thread Paul Wise
Control: reassign -1 src:linux 4.8~rc8-1~exp1 Control: retitle -1 linux: 4.8 causes crashes in ulogd2 due to bug in netfilter code On Thu, 2016-10-20 at 11:00 +0200, Julien Cristau wrote: > I think this should just be reassigned, there's not much point working > around a kernel bug. Doing that

Processing of linux-signed_2.8_source.changes

2016-10-20 Thread Debian FTP Masters
linux-signed_2.8_source.changes uploaded successfully to localhost along with the files: linux-signed_2.8.dsc linux-signed_2.8.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-20 Thread Konstantin Demin
2016-10-21 1:49 GMT+03:00 Ben Hutchings : > It's a bug when a compiler fails to compile valid code. > > Ben. > > -- > Ben Hutchings > Never put off till tomorrow what you can avoid all together. Dear Ben, there are no actual bug in compiler, just a caveat to work with it.

Bug#841473: linux-image-4.7.0-1-amd64: Nouveau driver stops working freezing system

2016-10-20 Thread André Isidoro Fernandes Esteves
Package: src:linux Version: 4.7.6-1 Severity: important Dear Maintainer, * What led up to the situation? System video froze without any notice, all i could savage from the log files: Oct 21 00:29:58 elektrum kernel: [98341.161363] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-20 Thread S. R. Wright
I agree. When the version changes from 6.2.0-6 to 6.2.0-7, only bug fixes should be included, not changes in functionality. In this case setting enable-default-pie essentially broke backwards compatibility. Kernel code that built in -6 failed to build in -7. That, I agree, should be

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-20 Thread Ben Hutchings
On Fri, 2016-10-21 at 01:21 +0300, Konstantin Demin wrote: > It's not a GCC bug but kind of new feature. It's a bug when a compiler fails to compile valid code. Ben. > Take a look at this changelog entry: >  gcc-6 (6.2.0-7) unstable; urgency=medium > >    [ Matthias Klose ] >    * Configure

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-20 Thread Konstantin Demin
It's not a GCC bug but kind of new feature. Take a look at this changelog entry: gcc-6 (6.2.0-7) unstable; urgency=medium [ Matthias Klose ] * Configure with --enable-default-pie and pass -z now when pie is enabled; on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x.

Bug#841438: --enable-default-pie breaks kernel build on amd64

2016-10-20 Thread Ben Hutchings
On Thu, 20 Oct 2016 19:05:51 +0200 Gianfranco Costamagna wrote: > control: severity -1 normal > control: reassign -1 src:linux > control: affects -1 gcc-6 >  > Hi Linux Kernel maintainers, > as you already know, the default PIE flag breaks the kernel build, can I >

Processed: reassign 841419 to src:linux, forcibly merging 841438 841419

2016-10-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 841419 src:linux Bug #841419 [linux-source-4.7] linux-source-4.7: debian linux source package incompatible with default gcc6 in unstable? Bug reassigned from package 'linux-source-4.7' to 'src:linux'. No longer marked as found in

Bug#841420: --enable-default-pie breaks kernel builds

2016-10-20 Thread Bálint Réczey
Control: tags -1 - patch 2016-10-20 18:48 GMT+02:00 Sven Joachim : > On 2016-10-20 17:54 +0200, Bálint Réczey wrote: > >> Control: reassign -1 linux 4.7.8-1 >> Control: severity -1 serious >> Control: tags -1 patch >> >> Hi David, >> >> 2016-10-20 14:02 GMT+02:00 David Weinehall

Processed: Re: Bug#841420: --enable-default-pie breaks kernel builds

2016-10-20 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - patch Bug #841420 [linux] --enable-default-pie breaks kernel builds Bug #841368 [linux] gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled Removed tag(s) patch. Removed tag(s) patch. -- 841368:

Bug#841438: This is agcc bug : upstream kernel irself fails to build with this gcc so reassigne to gcc-6

2016-10-20 Thread Eric Valette
I never use debian kernel and connaot compile upstream kernel with gcc-6 now. --eric

Processed: reassign 841453 to src:linux-signed

2016-10-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 841453 src:linux-signed 2.7 Bug #841453 [linux-image-4.7.0-1-amd64] linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty Bug reassigned from package

Bug#841453: linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty

2016-10-20 Thread Jakub Wilk
Package: linux-image-4.7.0-1-amd64 Version: 4.7.6-1 Severity: serious I you have linux-image-4.7.0-1-amd64 installed, then upgrading to linux-image-4.7.0-1-amd64-unsigned fails: # apt-get install linux-image-4.7.0-1-amd64-unsigned Reading package lists... Done Building dependency tree Reading

Bug#841420: --enable-default-pie breaks kernel builds

2016-10-20 Thread Sven Joachim
On 2016-10-20 17:54 +0200, Bálint Réczey wrote: > Control: reassign -1 linux 4.7.8-1 > Control: severity -1 serious > Control: tags -1 patch > > Hi David, > > 2016-10-20 14:02 GMT+02:00 David Weinehall : >> Package: gcc-6 >> Severity: important >> Version: 6.2.0-7 >> >>

Bug#841420: --enable-default-pie breaks kernel builds

2016-10-20 Thread S R Wright
Concurring with Wolfgang; pulling the source straight from kernel.org and using identical .config files will work with 6.2.0-6 but fail with 6.2.0-7. I was able to build and install 4.8.3 with no issues after back-revving gcc et. al. to 6.2.0-6 -- sRw On 10/20/16 11:09, Wolfgang Walter

Processed: your mail

2016-10-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 841368 linux 4.8.1-1 Bug #841368 [gcc-6] gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled Bug reassigned from package 'gcc-6' to 'linux'. No longer marked as found in versions gcc-6/6.2.0-7. Ignoring request to alter

Bug#841420: --enable-default-pie breaks kernel builds

2016-10-20 Thread Wolfgang Walter
Hello, with this version of gcc-6 I can't build vanilla kernels any more. It fails with even with CC_STACKPROTECTOR_STRONG disabled: scripts/kconfig/mconf Kconfig configuration written to .config *** End of the configuration. *** Execute 'make' to start the build or try 'make help'.

Processed: Re: Bug#841420: --enable-default-pie breaks kernel builds

2016-10-20 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 linux 4.7.8-1 Bug #841420 [gcc-6] --enable-default-pie breaks kernel builds Bug reassigned from package 'gcc-6' to 'linux'. No longer marked as found in versions gcc-6/6.2.0-7. Ignoring request to alter fixed versions of bug #841420 to the same values

Processed: Re: Bug#841423: LVM: raid1 kernel module not loaded

2016-10-20 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 dmsetup 2:1.02.133-1 Bug #841423 [initramfs-tools] LVM: raid1 kernel module not loaded Bug reassigned from package 'initramfs-tools' to 'dmsetup'. No longer marked as found in versions initramfs-tools/0.125. Ignoring request to alter fixed versions of

Bug#841423: LVM: raid1 kernel module not loaded

2016-10-20 Thread Ben Hutchings
Control: reassign -1 dmsetup 2:1.02.133-1 On Thu, 2016-10-20 at 14:27 +0200, Cesare Leonardi wrote: > Package: initramfs-tools > Version: 0.125 > Severity: normal > > Initially i thought to file this bug to lvm2 package but now i suspect > it's more related with kernel modules dependencies and

Bug#841423: LVM: raid1 kernel module not loaded

2016-10-20 Thread Cesare Leonardi
Package: initramfs-tools Version: 0.125 Severity: normal Initially i thought to file this bug to lvm2 package but now i suspect it's more related with kernel modules dependencies and the manual_add_modules() hook of initramfs-tools. Suppose your system has lvm2 installed but not mdadm. Now

Bug#841419: linux-source-4.7: debian linux source package incompatible with default gcc6 in unstable?

2016-10-20 Thread Giacomo Mulas
Package: linux-source-4.7 Version: 4.7.8-1 Severity: important Dear Maintainer, this morning the update of my debian sid system brought me a "medium" upgrade for the linux source package. I therefore proceeded to (try to) rebuild it, via a standard "make oldconfig" using the previous (it's a

Bug#841387: nfs-utils: typo in idmapd.conf

2016-10-20 Thread Ferenc Wágner
Package: nfs-utils Severity: minor Dear Maintainer, /etc/idmapd.conf (debian/idmapd.conf in the packaging repository) says: # set your own domain here, if id differs from FQDN minus hostname with "id" instead of "it". Please consider correcting this. -- Thanks, Feri.