[06:51] <ppisati> moin
[10:03]  * ppisati -> out for an early lunch
[11:31] <ogra_> ppisati, could you drop by in #pandaboard if you are back 
[11:52] <ppisati> ogra_: i',
[12:28] <rtg> wow, 15777 patches in this merge window so far. 3.4 -> 3.5 was only 10957
[12:29] <amitk> rtg: where is most of it coming from?
[12:29] <pedrinho> rtg: hehe thats a lot
[12:29] <rtg> amitk, dunno, haven't charted that.
[12:30] <pedrinho> rtg: can you tell if those patchs are mostly bug fix or new features?
[12:30]  * amitk suspects lots of consolidation work
[12:30] <rtg> pedrinho, yeah, right.
[12:35] <pedrinho> rtg: does ubuntu guys contrib for kernel development?
[12:49] <rtg> pedrinho, some, e.g., 
[12:49] <rtg> rtg@salmon:~/linux/linux$ git log v3.5..HEAD|egrep ^Author|egrep "canonical|ubuntu"|wc -l
[12:49] <rtg> 152
[12:54] <rtg> ogasawara, thought you were gonna upload yesterday. did you run into some snags ?
[12:54] <ogasawara> rtg: nope, was going to upload today
[12:54] <rtg> ok
[12:55] <ogasawara> rtg: figured I'd try and stretch it out another day in the event any last minute patches came in
[12:55] <rtg> I'm sure I can find something :)
[12:59] <rtg> apw, why does pre-proposed hate me ? I'm getting an  email every morning that says the Lucid source package upload has been rejected because it doesn't think my email address is valid.
[13:01] <apw> what is your email address
[13:01] <apw> (not here :))
[13:02] <rtg> apw, the usual. I assume its getting it from the changelog entry .
[13:02] <apw> forward me the email would you
[13:03] <diwic> smart bot, sending email complaining about the email address being broken. Like pressing F1 in case of keyboard error?
[13:04] <apw> heh yeah ... i assume its not using the email addy in the package, but of the "uploader" in this case
[13:04] <rtg> apw, I think I've already irrevocably deleted it. how about restarting that job for Lucid ? I'm sure it'll send me another email. 
[13:04] <apw> was it to you or kernel-ppa
[13:05] <rtg> diwic, I think it is sending the email to kernel-ppa@c.c which I'm fetching....
[13:05] <rtg> apw, ^^
[13:06] <apw> rtg, yep i have it
[13:09] <rtg> kees, 3.6 vanilla now has all of the right YAMA bits, right ? I'm dropping 'UBUNTU: SAUCE: Yama: add link restrictions' and 'UBUNTU: SAUCE: security: unconditionally chain to Yama LSM' in ubuntu-r because of conflicts.
[13:09] <apw> rtg, they sorted the chaining?  i am supprised
[13:10] <rtg> apw, kees: I meant 3.7
[13:11] <rtg> apw, isn't NF_NAT_IPV6 an oxymoron ? 
[13:12] <rtg> apw, here it is: CONFIG_SECURITY_YAMA_STACKED
[13:29] <rtg> apw, ogasawara: http://comments.gmane.org/gmane.linux.kernel/1368725 is going to affect our policy on EXPERIMENTAL
[13:32] <apw> rtg, hmmm, well we also look for (experimental) in the descriptio
[13:32] <apw> rtg, so as long as that is maintained at least we'll be ok
[13:32] <rtg> I suspect that will fall out of favor as well.
[13:33] <apw> rtg perhaps we need to just track when something arrives, so NEW == experimental :)
[13:33] <rtg> apw, I'm just turning on everything that is =m and looking more closely at options that are =y
[13:34] <apw> yeah they will all show as NEW so get consideration at UDS, so that is fine
[13:34] <apw> thanks for the head up though as it will break the processing
[13:35] <rtg> apw, I love being the harbinger of good news :)
[13:36] <apw> rtg, i am somewhat flummoxed by this lucid thing -- your sig looks just fine, and almost identical to luis' on oneiric which worked
[13:37] <rtg> apw, which is why I punted. 
[13:37] <rtg> apw, do you suppose its a LP thing ?
[13:37] <apw> its feeling like it indeed.  i will see if i can find the actual files it uploaded
[13:40] <apw> rtg, no the upload itself was successful so they are gone; bugger
[13:40] <apw> will ask if they still exist
[13:54] <ppisati> ogasawara: i'm researching a problem we have with usb and omap3 (beagle) so IF they ever fixed it, i'll probably need another upload and i don't think i'll get that by today
[13:55] <ogasawara> ppisati: ack, we can still upload after kernel freeze, it just needs to adhere to our SRU standards and policy which I suspect this would qualify
[13:56] <ppisati> ogasawara: yep, just wanted to give an heads up
[13:56] <ogasawara> ppisati: thanks
[14:11] <apw> rtg, found it, its actually your fault :)  its _precise_ thats broken, and its your signature line, you have <>'s round it
[14:11] <rtg> apw, 3.2 ?
[14:11] <rtg> oh, drat
[14:12] <apw> not quite sure what went wrong to make that happen
[14:13] <rtg> apw, ok, force pushed the fix
[14:13] <rtg> apw, I had some issues with some ENV variables, but I fixed them weeks ago
[14:14] <apw> rtg, well at least its resolved; and the error makes sense now as its saying there is crap then more <>'s within what claims to be an email addy
[14:15] <rtg> apw, so I wonder why the email I was getting was about 3.0 ? did I just mis-read it ?
[14:15] <apw> subject: [PPA kernel-ppa-pre-proposed] linux_3.2.0-32.52~pre201210030400_source.changes rejected
[14:15] <rtg> apw, indeed, I just mis-read it
[14:15] <apw> you said 3.0 and even with that in my face i saw 3.0
[14:16] <apw> numbers are hard...
[14:20] <rtg> Auto packing the repository for optimum performance always happens at the most inopportune moment.
[14:49]  * ogasawara back in 20
[15:04] <jsalisbury> diwic, your patch fixes bug 1059523 :-)
[15:04] <ubot2> Launchpad bug 1059523 in linux "[Acer Aspire One 722] Broken support of Intel HDA in 3.5.0-16 kernel" [Medium,Confirmed] https://launchpad.net/bugs/1059523
[15:04] <diwic> jsalisbury, good, can we apply it? :-)
[15:05] <jsalisbury> diwic, Probably.  It applied cleanly.  I can send it to the mailing list
[15:07] <jsalisbury> rtg, do you want a request on the kernel team mailing list for this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1059523/comments/8
[15:08] <ubot2> Launchpad bug 1059523 in linux "[Acer Aspire One 722] Broken support of Intel HDA in 3.5.0-16 kernel" [Medium,Confirmed]
[15:08] <rtg> jsalisbury, yes
[15:08] <jsalisbury> rtg, ok.  will do
[15:08] <diwic> jsalisbury, thanks
[15:08] <jsalisbury> diwic, np.  thank you ;-)
[15:38] <hggdh> ogra_: does this ring any bells? http://pastebin.ubuntu.com/1258212/
[15:39] <ogra_> hggdh, looks like the squashfs is corrupt or the module is messed up
[15:39] <hggdh> ogra_: do you want a bug on it?
[15:39] <ogra_> yeah, files it against linux-ti-omap4 for now 
[15:40] <hggdh> ack
[15:40] <ogra_> oh
[15:40] <ogra_> its not the squashfs being corrupt 
[15:41] <ogra_> its loop device support missing
[15:41] <ogra_> ppisati, ^^^
[15:41] <ogra_> see the paste above
[15:44] <hggdh> ogra_, ppisati: bug 1061036
[15:44] <ubot2> Launchpad bug 1061036 in linux-ti-omap4 "20121003 server image fails to install with s squasfs error" [Undecided,New] https://launchpad.net/bugs/1061036
[15:46]  * rtg is off to perform server surgery...
[15:48] <ppisati> ogra_: i installed the server image yesterday and it was ok
[15:48] <ogra_> strange
[15:48] <ogra_> thats todays image though
[15:49] <ogra_> could we be out of sync wrt uploads ?
[15:50] <ppisati> [flag@newluxor ~]$ ls -la Downloads/quantal-server-armhf+omap4.img 
[15:50] <ppisati> -rw-rw-r-- 1 flag flag 757923840 Oct  2 09:21 Downloads/quantal-server-armhf+omap4.img
[15:50] <ppisati> [flag@newluxor ~]$ md5sum Downloads/quantal-server-armhf+omap4.img
[15:50] <ppisati> this one is good
[15:50] <ogra_> hmm, no
[15:50] <ppisati> 25931219ba6a86e3c17ba3c2003665ff  Downloads/quantal-server-armhf+omap4.img
[15:50] <ogra_> yeah, and tehre were no kernel uploads since the 29th 
[15:50] <ogra_> weird
[15:51] <ppisati> ogra_: i'm investigating the omap3 usb thing
[15:51] <ppisati> ogra_: can you try that?
[16:51] <hggdh> ogra_: just finished another install with server 20121003, and it worked
[16:52] <ogra_> cosmic rays !
[16:52] <hggdh> ogra_: I do not follow what happened...
[17:04] <hggdh> but I closed the bug calling on the cosmic rays
[18:01]  * rtg -> lunch
[18:44] <ppisati> hggdh: toss the sd cards, sometimes they mess up the image you dd on it, it has happened to me in the past
[18:45] <ppisati> hggdh: *sd card
[18:45]  * ppisati needs food... immediately...
[19:17] <hggdh> ppisati: will ask retoaded to do that when he gets to the lab, thanks
[19:19] <retoaded> hggdh, are we removing them permanently or replacing them with new cards?
[19:23] <hggdh> retoaded: putting in new ones
[19:24] <retoaded> ack
[19:35] <alexbligh> what is the safe way of passing system an array or arguments (as opposed to a space separated string) AND redirect stdout and stderr of the system call only to /dev/null?
[19:35] <alexbligh> oops, www
[19:58]  * ppisati heads to the couch
[20:26]  * rtg -> EOD
[21:35] <kees> rtg, apw: yup, for 3.6 you can drop 'UBUNTU: SAUCE: Yama: add link restrictions', and for 3.7 you can drop 'UBUNTU: SAUCE: security: unconditionally chain to Yama LSM' (but enable CONFIG_SECURITY_YAMA_STACKED)
[22:07] <apw> kees, ack
[22:07] <apw> ogasawara, ^^
[22:08] <ogasawara> kees, apw: ack, thanks