[07:39] I got an oops while using a mainline kernel. Is there a tool in Ubuntu to report oops to kerneloops.org? [07:47] gioele, There is the kerneloops package. Though the setup by default reports through apport. But iirc you can run it manually and modify the options then. [15:36] apw, rtg Hm, am I looking the wrong place or could it be that the generic inclusion list in utopic lost some elements? Just saw someone complaining about virtio_scsi and it indeed appears to be missing (compared to trusty) [15:37] they do sound like things we did very recently, so ... i could believe they have not been syncd [15:37] smb, maybe it never acquired then. [15:37] them* [15:37] I've been known to forget to forward port. we haven't done a resync in awhile. [15:38] Yeah there is a certain diff... [15:38] i did only debian when i did the emergency one at the weekend [15:39] Guess I should send a diff then... :) [15:41] ppisati: your post sounds reasonable, but could you also post it to cross-distro please? [15:56] rbasak: yep, i'll do [15:57] rbasak: i was waiting for some other answer just to hear what the general consensus was [15:58] ppisati: thanks. I think we'll probably want to get consensus on cross-distro. I think it's fine to not yet have consensus but still have a discussion there. [16:01] start_line_y = weechat.infolist_integer(infolist, "start_line_y") [16:27] apw: Does building a 64bit kernel on 32bit software require cross compiling? [16:28] wilhelm1, "kinda" the tool chain generally can build both 32 and 64 bit in the case of x86 [16:28] wilhelm1, i would normally not cross build, but build in a 32bit chroot on a 64bit box [16:28] oh .. you said the other way round, interesting ... [16:29] i think in theory the compiler has -m64 avaialble, though if the package knows how to trigger that [16:32] apw: Are the 64bit linux softwares cross compiled or built from 64bit toolchains? [16:33] wilhelm1, we build them all "nativly" in a chroot of teh appropriate type, in some cases we can share the builders, for example a 64bit x86 builder can build either 32 or 64 bit chroots [16:36] So apw is it built on a 64bit machine on software that was written and compiled for it? [16:37] we nativly compile the kerenls yes [16:37] people do cross them, but not for the archive [16:38] Where do we get the code from is it always forked from debian? [16:42] for the kernel we work mostly directly against mainline, as we are generally versions ahead of debian [16:45] apw: That is kernel.org or vger? [16:45] linus' releases [16:46] apw: Where are linus' releases found? [16:46] we get them from his git tree, but they are also released as tarballs on kernel.org [16:47] Share with me the link to his git tree. [16:48] git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git [16:55] Do we use any security measures to verify the authenticity of what is taken from git? === sz0 is now known as sz0` [17:00] wilhelm1, yes, we use only signed (and verified) tags as base === sz0` is now known as sz0 [17:02] apw is we defined as canonical? [17:02] we is defined as those of us in the kernel-team who pull in new upstream versions, be it mainline or stable [17:06] apw: How many times has the signing key changed since the last in person meeting with linus? [17:07] wilhelm1, i only know of it changing once [17:08] once too many? [17:08] we have strong web of trust connections to both of the keys he has used [17:09] apw: What is linus' email? [17:10] he has various emails, but he is using Linus Torvalds signing off now === sz0 is now known as sz0` === sz0` is now known as sz0 === sz0 is now known as sz0` === sz0` is now known as sz0 === sz0 is now known as sz0` === cyphermox_ is now known as cyphermox === sz0` is now known as sz0 [20:24] The bots could deliver fresh baked bread daily. [20:24] Is there a goal? [20:24] fresh baked bread daily === e11bits_ is now known as e11bits === Trevinho_ is now known as Trevinho === spossiba_ is now known as spossiba === Sarvatt_ is now known as Sarvatt === fmasi is now known as Guest97162