On 23/11/14 03:03, Adam Borowski wrote: > On Sun, Nov 23, 2014 at 02:07:42AM +0100, Christian Kastner wrote: > > On 2014-11-23 01:16, Adam Borowski wrote: > > > On Sat, Nov 22, 2014 at 09:09:55PM +0100, Tomasz Buchert wrote: > > >> On 10/11/14 10:56, Christian Kastner wrote: > > >> I cannot confirm this bug in both cases I've tried: > > >> > > >> * amd64 (Linux 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) > > >> x86_64 GNU/Linux) > > >> * amrhf (Linux 3.14.4.1-bone-armhf.com #1 SMP Tue Jun 3 12:37:22 UTC > > >> 2014 armv7l GNU/Linux) > > > > > > My tests: > > > armhf 3.8.13.28: FTBFS > > > > Was this either a Debian or a vanilla kernel? I ask because 3.8 kernels > > are often vendor-provided variants of certain ARM devices. > > I have heard myths of ARM devices that can run upstream kernels, but I have > yet to see one :p. This one is git://github.com/hardkernel/linux, a pretty > well behaved one as vendor kernels go.
Guys, I went crazy and tested this assertion. I've upgraded the vendor arm kernel to the testing kernel and guess what - it didn't boot... (I'll have to fix it when I'm back home) That said, one of the Debian developers built it for me on armhf 3.16.3 (slightly newer than the testing kernel) and it went fine. If you still think that it may not work in jessie, you could ask for rebuild (https://release.debian.org/wanna-build.txt). If not, you could downgrade the severity to unblock keyutils for the jessie release (I'm not sure if tagging with +sid will stop it being RC). Tomasz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
