[07:14] <ppisati> moin
[07:23] <smb> morning
[07:58] <ppisati> smb: Stef, i've a problem with maint-startnewrelease
[07:58] <ppisati> smb: 100% i screwed the packaging
[07:58] <ppisati> smb: but i don't get why...
[07:58] <ppisati> smb: so, basically
[07:59]  * smb does not know either...
[07:59] <ppisati> hold on... :)
[08:01] <ppisati> smb: http://paste.ubuntu.com/1146380/
[08:44] <cooloney> smb: morning
[08:44] <smb> cooloney, good morning
[08:44] <cooloney> these days i'm fighting with the building test on my imx6 board
[08:45] <cooloney> i was asked to test building kdepim, gcc-4.6, chromium-browser, firefox and webkit
[08:45] <apw> cooloney, how is sbuild working out for you there
[08:46] <cooloney> i only got kdepim build successfully, but other four packages fail for some reason.
[08:46] <cooloney> sometimes out-of-memory
[08:46] <apw> cooloney, but they build on your babbage ?
[08:46] <apw> (or whatever the current buildds are?)
[08:46] <cooloney> oh, i never tried that on babbage before.
[08:46] <apw> babbage may be the wrong name, i get very confused
[08:47] <cooloney> they are supposed to be build without any error
[08:47] <apw> i probabally mean panda
[08:47] <cooloney> since we build them on panda
[08:47] <apw> you have a panda right?  so you could shift the sbuild containing disk over there and test 
[08:47] <smb> OK, if they build there with the same compiler it sounds a bit like some corruption going on on the other
[08:47] <cooloney> and sometime the system will lockup without any output after a very long building time like 8 hours.
[08:47] <apw> to see if its your environment or the machine
[08:48] <cooloney> apw: yeah, i'm trying to setup the environment with my PandaES. bs
[08:48] <apw> it might be good to literally take the same disk over there
[08:48] <apw> then you'd know it wasn't that exact sbuild environment
[08:51] <cooloney> right, i'm trying to do these on my PandaES. i tried another USB harddisk before, it looks like not very stable.
[08:51] <apw> cooloney, if they are not reliable over time, they are next to useless as that is exactly what we would want to do with them
[08:51] <cooloney> i think i need a USB disk with external power supply. i just found one, and going to do that
[08:51] <apw> cooloney, ok
[08:53] <cooloney> apw and smb, thanks for understanding. it is quite annoying about the build failure. and I will post the build logs after i tested it on my PandaES
[08:54] <cooloney> apw: and for the lxc /root prefix issue. based on your idea, i think i can post a patch to LP for you guys discussion
[08:55] <apw> cooloney, ok sounds good, point me at it when it is there, i will forget otherwise
[08:56] <smb> cooloney, As apw said I think it is a good idea (if possible) to take the environment to the Panda and see what happens there. It would rule out this as a source of error. And yes, if you have something, post it 
[08:57] <smb> cooloney, I assume it is a change to the lxc setup?
[08:57] <cooloney> smb: yeah, that's what i'm going to do. i got an SATA-TO-USB cable and an external SATA HD power supply now
[08:58] <smb> ppisati, Try the getabis posted and let us know how that works :)
[08:59] <ppisati> smb: i'm finishing another kernel than i'll test ot
[08:59] <ppisati> it
[08:59] <smb> apw, Yes, some message/warning would do ok. Hopefully you never place a package of the exact name there, but anyway.
[09:00] <apw> smb, indeed but if you do it'll be a big confusing supprise that you cannot get it to work, then i ask you to test and it works and i pull all my (remaining) hair out
[09:01] <smb> apw, No we would not want you to do that... :)
[09:01] <apw> smb, exactly, who would look like bill the cat then
[09:02] <smb> bill the cat himself?
[09:27] <cooloney> apw: i posted the patch in bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959352
[09:27] <ubot2`> Ubuntu bug 959352 in lxc "Ephemeral containers have "/rootfs" prefix in /proc/self/maps entries" [High,Confirmed]
[09:29] <apw> cooloney, thanks
[09:35] <apw> cooloney, i have also made comment that as only the rootfs part of the name leaks into the container, there may be something we can do with the way the unions are placed to get rid of it should they really not be able to cope with the prefix
[09:35] <apw> perhaps placing two unions instead of one or something
[09:38] <dileks> +        # echo "rming rootfs softlink for overlayfs" >&2
[09:38] <dileks> Removing/Deleting
[09:38] <cooloney> dileks: that's is just a comment, i followed others 
[09:39] <dileks> and I thought its rming's rootfs
[09:39] <cooloney> apw: hmmm, i don't fully understand here. 
[09:40] <cooloney> apw: do you mean we move the unions directory to some other place instead of "rootfs"?
[09:41] <apw> cooloney, me either i am just suggesting they may be able to play with mounting differnetly
[09:41] <apw> i have not looked to see how its mounted
[09:53] <ppisati> brb
[10:09]  * smb -> munch
[11:41] <jibel> todays quantal server with LVM fails to reboot after installation
[11:41] <jibel> bug 1036612
[11:41] <ubot2`> Launchpad bug 1036612 in linux "Quantal Server failed to install with LVM: VFS: Cannot open root device "mapper/ubuntu-root" or unknown-block(0,0): error -6" [Undecided,New] https://launchpad.net/bugs/1036612
[12:01] <smb> jibel, Repeatable or maybe just some failure with the initrd (which it quite often is)
[12:02] <jibel> smb, repeatable, all the automated tests that use LVM failed and reproduced manually
[12:03] <jibel> smb, alternate, which also runs a test with LVM but doesn't use a squashfs for installation passes. And it uses the same kernel
[12:04] <smb> Ok, hm. mapper/ubuntu-root... would be good to know what grub.cfg looks like and what the vg / lv is named, but I assume it uses ubuntu as hostname, too...
[12:05] <smb> I'll try to reproduce it here...
[12:08] <henrix> apw: are you aware of any network changes on tangerine or gomeisa?
[12:09] <henrix> apw: i'm not able to run rmadison anymore
[12:09] <henrix> apw: for ex., 'rmadison --architecture=source linux' seems to hang forever
[12:10] <henrix> well... no forever. it eventually exit with a 'couldn't connect to host' error
[12:10] <smb> henrix, firewall? did that work before?
[12:11] <henrix> smb: yes, it did work before
[12:11] <henrix> smb: the makefile for the meta packages actually use rmadison
[12:11] <henrix> smb: that's how i found something's changed
[12:12] <smb> henrix, Ok, so that really sounds like something changed in between
[12:12] <smb> (not on the hosts)
[12:12] <henrix> yep
[12:17] <ppisati> smb: it works
[12:17]  * smb assumes it is the getabis script and not the rmadison call
[12:18] <ppisati> smb: yep, getabi
[12:18] <smb> ppisati, Cool, then you can ack it
[12:19]  * smb closes both eyes on tangerines dmesg...
[12:20] <smb> hm gomeisa as well...
[12:20] <henrix> ouch! :)
[12:20] <smb> apw, non-accessible hardlink creation was attempted by: git
[12:26] <henrix> i've never seen this error before, but it looks like its yama related
[12:26] <henrix> sysctl kernel.yama.protected_nonaccess_hardlinks
[12:28] <smb> henrix, Yes I think it is some effect of hardening
[12:38] <smb> henrix, It might be we need to talk to sforshee ... ;)
[12:39] <smb> ... and Joe and Colin...
[12:41] <smb> ... he and I have to talk to me as well...
[12:41] <henrix> heh
[12:42] <apw> smb, so when is that happening?  when pusing or locally?
[12:42] <smb> apw, Cannot say, its just entries that happen at some point
[12:42] <apw> smb, not that it matters probabally ... as git will fall back to copying
[12:43] <smb> Must be something I cannot write to... hm, maybe --reference /usr3/...
[12:44] <smb> apw, Yeah, both are on the same disk... I guess that is what happens 
[12:45] <apw> yeah makes sense.  and git is hiding it from you probabally
[12:45] <apw> as it probally just does ln, and if that fails its copies
[12:45] <apw> assuming ln failure will be cross disk
[12:45] <smb> sounds reasonable... Just trying it, so my id should produce a new msg
[12:45] <smb> it did
[12:47] <smb> apw, And no error from git. Only scary thing is a double entry in alternates (which likely does not matter either)
[12:49] <apw> oh that is odd
[12:50] <smb> but I suspect it might be completely unrelated
[12:51]  * smb wonders whether hardlink protection might go a step too far, though
[12:52] <apw> it is doing what is intended, it is preventing you linking to things you cannot write to
[12:52] <apw> so that you cannot drop links to things you cannot modify in random places
[12:52] <apw> to be overwritten by accident
[12:52] <smb> hm, thought git would create only readable objects...
[12:53] <smb> though at some point they probably are writeable, otherwise it should not be possible to create them...
[12:58] <apw> i may be able to write to the directory but not link the files as they are yours
[13:05] <smb> apw, Well I guess, given that my objects appear to be writeable to me (on gomeisa, my local repo objects seem to be read-only) that hardlink failure is correct
[13:06] <henrix> apw: what about the rmadison failure i referred above? any idea?
[13:07] <apw> henrix, seems to work for me here now
[13:07] <apw> rmadison -a source linux
[13:07] <henrix> hmm... i'm unable to run it on tangerine or gomeisa, but it runs locally on my laptop
[13:08] <smb> And it still does not on gomeisa for me
[13:08] <smb> I asked on #is but got no answer yet
[13:08] <henrix> on gomeisa i get an error; on tangerine it seems to hang forever
[14:50]  * ogasawara back in 20
[15:10] <hggdh> sforshee: just a Q -- my touchpad when south with the new kernel on quantal, is it still an option to try your dkms?
[15:15] <sforshee> hggdh, that dkms package was only for testing. All the changes should be in quantal, so if it worked with the dkms package and doesn't work with quantal file a bug and assign it to me.
[15:15] <hggdh> sforshee: will do, thanks.
[15:19] <sforshee> mjg59, would you be agreeable to picking up the gmux switcheroo changes now, before the graphics driver issues are sorted out? That will at least get the mux state restored correctly after s3.
[15:20] <mjg59> sforshee: Yeah, I think so
[15:20] <mjg59> sforshee: It shouldn't break any existing config
[15:20] <sforshee> mjg59, no it shouldn't. I'll rebase on top of your patches for the retina then and send the patches later today.
[15:21] <mjg59> sforshee: Brilliant, thanks
[15:28] <kiko> live hangout on status update for single zimage for arm http://www.youtube.com/channel/UCIVqQKxCyQLJS6xvSmfndLA?v=4Lpzc_dkh9E
[16:37] <jsalisbury> **
[16:37] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[16:37] <jsalisbury> **
[17:23]  * ppisati -> out for a bit
[18:40]  * henrix -> EOD
[19:19]  * smb -> EOD
[20:02] <rsalveti> ogra_: bug 1008713, from linux-base/linux, but guess it affects more the images depending on flash-kernel
[20:02] <ubot2`> Launchpad bug 1008713 in linux "[STAGING] package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/perf.1.gz', which is also in package linux-base 3.4ubuntu2" [Medium,Confirmed] https://launchpad.net/bugs/1008713
[20:02] <rsalveti> as flash-kernel depends on linux-base, which then doesn't let the user to install the linux-tools-common 
[20:03] <rsalveti> which is a dependency from any specific linux-tools package, that covers perf 
[20:18] <jpds> Does anyone know if there's a way to tell if a USB port is USB 3.0 compatible ?
[20:19] <jpds> Of course; $ lsusb.