[07:39] <gioele> I got an oops while using a mainline kernel. Is there a tool in Ubuntu to report oops to kerneloops.org?
[07:47] <smb> 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] <smb> 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] <apw> they do sound like things we did very recently, so ... i could believe they have not been syncd
[15:37] <rtg> smb, maybe it never acquired then.
[15:37] <rtg> them*
[15:37] <rtg> I've been known to forget to forward port. we haven't done a resync in awhile.
[15:38] <smb> Yeah there is a certain diff...
[15:38] <apw> i did only debian when i did the emergency one at the weekend
[15:39] <smb> Guess I should send a diff then... :)
[15:41] <rbasak> ppisati: your post sounds reasonable, but could you also post it to cross-distro please?
[15:56] <ppisati> rbasak: yep, i'll do
[15:57] <ppisati> rbasak: i was waiting for some other answer just to hear what the general consensus was
[15:58] <rbasak> 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] <apw> start_line_y = weechat.infolist_integer(infolist, "start_line_y")
[16:27] <wilhelm1> apw: Does building a 64bit kernel on 32bit software require cross compiling?
[16:28] <apw> wilhelm1, "kinda" the tool chain generally can build both 32 and 64 bit in the case of x86
[16:28] <apw> wilhelm1, i would normally not cross build, but build in a 32bit chroot on a 64bit box
[16:28] <apw> oh .. you said the other way round, interesting ...
[16:29] <apw> i think in theory the compiler has -m64 avaialble, though if the package knows how to trigger that
[16:32] <wilhelm1> apw: Are the 64bit linux softwares cross compiled or built from 64bit toolchains?
[16:33] <apw> 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] <wilhelm1> So apw is it built on a 64bit machine on software that was written and compiled for it?
[16:37] <apw> we nativly compile the kerenls yes
[16:37] <apw> people do cross them, but not for the archive
[16:38] <wilhelm1> Where do we get the code from is it always forked from debian?
[16:42] <apw> for the kernel we work mostly directly against mainline, as we are generally versions ahead of debian
[16:45] <wilhelm1> apw: That is kernel.org or vger?
[16:45] <apw> linus' releases
[16:46] <wilhelm1> apw: Where are linus' releases found?
[16:46] <apw> we get them from his git tree, but they are also released as tarballs on kernel.org
[16:47] <wilhelm1> Share with me the link to his git tree.
[16:48] <apw> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
[16:55] <wilhelm1> Do we use any security measures to verify the authenticity of what is taken from git?
[17:00] <apw> wilhelm1, yes, we use only signed (and verified) tags as base
[17:02] <wilhelm1> apw is we defined as canonical?
[17:02] <apw> we is defined as those of us in the kernel-team who pull in new upstream versions, be it mainline or stable
[17:06] <wilhelm1> apw: How many times has the signing key changed since the last in person meeting with linus?
[17:07] <apw> wilhelm1, i only know of it changing once
[17:08] <wilhelm1> once too many?
[17:08] <apw> we have strong web of trust connections to both of the keys he has used
[17:09] <wilhelm1> apw: What is linus' email?
[17:10] <apw> he has various emails, but he is using Linus Torvalds <torvalds@linux-foundation.org
[17:46] <wilhelm1> signing off now
[20:24] <wilhelm1> The bots could deliver fresh baked bread daily.
[20:24] <wilhelm1> Is there a goal?
[20:24] <wilhelm1> fresh baked bread daily