On 23/11/14 12:55, Christian Kastner wrote: > (Tomasz, apparently I forgot to CC you on this mail yesterday, sorry) > > On 2014-11-23 02:55, Christian Kastner wrote: > > On 2014-11-23 01:16, Adam Borowski wrote: > >> amd64 vanilla 3.16.7: builds ok > >> amd64 vanilla 3.17.3: FTBFS > > > > I can confirm that is issue exists with 3.17. > > > > The syscall is returning ENOKEY where until 3.16 it was returning EPERM. > > I am now quite certain that the issue is being caused by this kernel > commit in 3.17: > > Commit: a4e3b8d79a5c6d40f4a9703abf7fe3abcc6c3b8d > KEYS: special dot prefixed keyring name bug fix > > The thing is, I'm not sure whether this needs to be fixed in keyutils, > or in the kernel. I now contacted upstream about this. Depending on the > answer, I'll either fix keyutils, or reassign to src:linux. > > Either way, I tagged this "sid" as it can only appear with a kernel that > will not be part of Jessie. So that should solve the RC problem, no? > > Thank you for all your work, guys! > > Christian
My pleasure! I think that this bug is not RC anymore - it is not listed here: https://udd.debian.org/bugs/bugs/bugs/bugs/?release=jessie_and_sid&patch=ign&merged=ign&done=ign&fnewerval=7&rc=1&sortby=id&sorto=asc&ctags=1&ctags=1&cdeferred=1#results Good luck with 3.17 :D - if you need help, let me know. Tomasz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
