[03:48] <StevenK> wallyworld: Can I pick your brain?
[03:48] <bigjools> he's in my kitchen
[03:48] <StevenK> You've put him to work?
[03:48] <bigjools> only thing he's good for
[03:48] <StevenK> True
[03:49] <StevenK> bigjools: He's chained to the cooktop?
[03:49] <bigjools> actually I think he's stealing my food
[03:49] <StevenK> That sounds more like wallyworld
[03:49] <bigjools> will have to send him to Port Arthur
[03:49] <StevenK> I didn't think he was cooking you anything :-)
[03:51] <wallyworld> StevenK: hello there
[03:54] <StevenK> wallyworld: What did you score? :-P
[03:54] <wallyworld> fresh bread
[03:55] <StevenK> wallyworld: I'm looking at the BMP page, and I can't work out how the inlineedit widgets get created to start with
[03:55] <wallyworld> lol. i can't recall ottomh. i can look at the code
[03:55] <StevenK> wallyworld: javascript/branchmergeproposal.reviewcomment.js uses them in Y.lp.widgets[name], but I can't work out what populates them
[03:56] <wallyworld> i'll have alook
[03:57] <wallyworld> except i need to re-install some stuff cause my raring went tits up a couple of weeks ago and i had to rebuild, so give me a minute
[04:09] <wallyworld> StevenK: so, branchmergeproposal-index.pt loads the javascript, wheich then hooks up the widgets, is that the bit you are after?
[04:12] <StevenK> wallyworld_: I can't work out what populates Y.lp.widgets[name]
[04:13] <wallyworld_> StevenK: ok, let me look. my fucking computer shutdown due to low battry. i thought it would have suspended, but noooooo
[04:14] <StevenK> I think it's the trickery in branchmergeproposal-index.pt <tal:widget replace="structure view/commit_message_html"/>
[04:15] <StevenK> Which returns a TextAreaEditorWidget
[04:18] <StevenK> wallyworld_: Or am I barking up the wrong tree?
[04:18] <wallyworld_> StevenK: so, BranchMergeProposalView has a property commit_message_html
[04:19] <wallyworld_> which loads a TextAreaEditorWidget
[04:19] <wallyworld_> which has a template text-area-editor.pt
[04:19] <wallyworld_> which has javascript with a line: lpns.widgets['${view/content_box_id}'] = widget;
[04:20] <wallyworld_> so the tal replace injects the value of the property
[04:20] <wallyworld_> which uses the editor tal to render some html
[04:20] <wallyworld_> make sense?
[04:21] <StevenK> wallyworld_: Yes, clear as mud
[04:21] <wallyworld_> you sure?
[04:59] <wgrant> StevenK: Hm, does your workitem preloading not exclude deleted ones?
[05:00] <StevenK> wgrant: It would seem not :-(
[05:00] <wgrant> StevenK: Can has fix? :)
[05:01] <StevenK> wgrant: Should I change load_referencing to ignore them, or just not add them to the defaultdict if deleted?
[05:02] <wgrant> StevenK: load_referencing might already take extra conditions. If not, I'd suggest letting it take extra conditions.
[05:03] <wgrant> It seems like it would be generally useful.
[05:04] <StevenK> wgrant: No extra conditions
[05:26] <StevenK> wgrant: Is there a bug?
[05:26] <wgrant> StevenK: I don't think so.
[05:27] <StevenK> wgrant: http://pastebin.ubuntu.com/6016516/
[05:28] <wgrant> StevenK: Looks reasonable.
[05:44] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/no-preload-deleted-workitems/+merge/181708
[05:45] <wgrant> StevenK: Land it.
[05:45] <wgrant> :)
[08:03] <wgrant> StevenK: Your caching introduced a seriously weird bug where adding workitems to a blueprint that has none returns an empty workitems_text
[08:03] <wgrant> I'm investigating, but it's really really weird.
[08:04] <wgrant> The new SWIs aren't being flushed immediately for some reason.
[08:04] <wgrant> Will investigate and fix tomorrow.
[08:04] <StevenK> wgrant: Why are you playing with workitems, out of interest?
[08:05] <wgrant> StevenK: QAing your thing.
[08:05] <wgrant> Hm
[08:05] <wgrant> SWI is a StormBase, not an SQLBase, so it shouldn't have been working without an explicit add.
[08:05] <wgrant> I wonder how they are being added today.
[08:05] <StevenK> Heh
[08:06] <wgrant> I intend to deploy your fix shortly.
[08:44] <stub> Because fixing SWI flushing is what you do on Saturday :-P
[08:57] <shadej> hi
[08:58] <shadej> I want to participate on ubuntu devt software localization
[08:58] <shadej> quick start help?
[12:27] <dowson> The instructions mentioned here: https://dev.launchpad.net/Soyuz/HowToUseSoyuzLocally is out of sync with the source tree here: http://bazaar.launchpad.net/~canonical-launchpad-branches/launchpad-buildd/trunk/files
[12:28] <dowson> I can't find a lib/canonical/buildd folder in the launchpad-buildd source tree.
[12:29] <wgrant> dowson: That's now in lp:launchpad-buildd
[12:29] <wgrant> Or you can just install launchpad-buildd from ppa:launchpad
[12:30] <dowson> I want to build from sources. I tried the following command: bzr branch lp:launchpad-buildd
[12:30] <wgrant> That's correct.
[12:30] <dowson> is that the correct command?
[12:31] <dowson> I want to try out the local build slave
[12:31] <wgrant> Yes.
[12:31] <dowson> https://dev.launchpad.net/BuildFarm/TryOutBuildSlave
[12:31] <dowson> Build the package
[12:31] <dowson>   cd lib/canonical/buildd
[12:31] <dowson>   debian/rules package
[12:31] <dowson>   dpkg-buildpackage -b
[12:31] <dowson> so there is no lib/canonical/buildd folder
[12:32] <wgrant> No, it's just in the root now
[12:32] <wgrant> Because it's in its own branch.
[12:32] <dowson> what should I be doing?
[12:33] <dowson> should I create the folder lib/canonical/buildd
[12:33] <dowson> and then execute the the rest of the commands?
[12:37] <wgrant> dowson: No, omit the cd
[12:37] <wgrant> The package is in the root of lp:launchpad-buildd
[12:39] <dowson> I'm sorry, I can't find it.
[12:39] <dowson> the root of the package doesnt have a lib folder to begin with
[12:39] <wgrant> There is no lib/canonical/buildd
[12:39] <wgrant> That tree was moved into a separate branch
[12:39] <dowson> oh, so just run the second set of commands .. ok got it now.
[12:40] <dowson> if I have to setup a pbuilder chroot, does the rest of the instructions still hold good here: https://dev.launchpad.net/BuildFarm/TryOutBuildSlave
[12:42] <wgrant> dowson: A pbuilder chroot?
[12:42] <wgrant> For what?
[12:42] <wgrant> Launchpad doesn't use pbuilder.
[12:42] <dowson> this for soyuz.
[12:43] <wgrant> HowToUseSoyuzLocally describes where to get a prebuilt chroot.
[12:43] <dowson> the instructions in the link above talked about setting up a pbuilder root. I will be trying to cross compile Ubuntu for ARM locally on an X86_64 machine.
[12:44] <wgrant> Why are you trying to do that?
[12:44] <dowson> I want to build for my i.MX6 board, with a specific toolchain generated from the Yocto project, and then use that to fully rebuild a Ubuntu for ARM distro, using that toolchain.
[12:46] <dowson> I get an error while running the debian package command
[12:46] <dowson> dh_clean
[12:46] <dowson> make: dh_clean: Command not found
[12:46] <dowson> make: *** [clean] Error 127
[12:46] <dowson> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
[12:46] <dowson> debuild: fatal error at line 1350:
[12:46] <dowson> dpkg-buildpackage -rfakeroot -d -us -uc -S failed
[12:46] <wgrant> Doing that with Launchpad without thoroughly knowing Launchpad from a normal user's perspective is going to be quite a challenge.
[12:46] <wgrant> And without knowing Debian packaging well.
[12:46] <dowson> I know, but I want to give it a shot.
[12:47] <dowson> I'm familiar with cross compiling using Yocto and openembeded, I haven't done building Ubuntu before.
[12:47] <wgrant> Those two are designed for cross-compilation.
[12:48] <wgrant> Ubuntu can't be cross-compiled as such; if you want to do it cross-arch then you have to build it with qemu
[12:52] <dowson> yes, i understand.
[12:53] <dowson> I plan on using an Yocto generated QEMU for this.
[12:54] <dowson> I just need to know how to tie in my Yocto generated QEMU to the Ubuntu build infrastructure, and where to get the package specifications to perform a build of Ubuntu 12.04 for ARM, using a custom toolchain, also generated using Yocto.
[12:59] <dowson> is there a file that you can point me to, where the qemu image and cross-compiler toolchain location and name is specified?
[12:59] <wgrant> There's no easy way to just rebuild Ubuntu.
[12:59] <wgrant> There's nothing like that.
[12:59] <wgrant> We don't generally cross-compile, except for some relatively experimental ARM PPA builds, which just use qemu-user-static.
[12:59] <wgrant> Which isn't terribly reliable.
[13:00] <dowson> I have an actual target board as well, a freescale i.MX6 quad, which already has ubuntu running on it. but I want to bootstrap it from scratch
[13:00] <dowson> I prefer to try the QEMU approach first if possible, rather than native compilation.
[16:25] <dowson> Is there some documentation that describes how to build Ubuntu with qemu?