[01:34] <jbicha> wow, eclipse on armel took 3 tries to build, the first timed out and the second crashed
[03:25] <gale-michael> I dislike eclipse, so slow ...
[06:48] <alo21> hi all
[06:49] <alo21> I have a problem on building juju with pbuolder or debuilder
[06:49] <alo21> could someone help me, please?
[06:49] <dholbach> good morning
[06:51] <micahg> alo21: a pastebin of a log snippet would help
[06:53] <alo21> micahg: here is the log: http://pastebin.ubuntu.com/1063822/
[06:54] <micahg> hrm, I can't be of much help here, maybe someone else can
[06:55] <alo21> micahg: thank you anyway
[06:57] <alo21> micahg: could success of a building depends by computer?
[06:58] <micahg> alo21: maybe, some of those failures might be heisenbugs
[12:32] <arand> For an SRU (universe), should I be subscribing ubuntu-sponsors at the same time, or after ubuntu-sru? Also, is a debdiff required or is an bzr branch ok, and should it be merge-suggested or just linked to the bug report?
[12:33] <arand> c.f. https://bugs.launchpad.net/ubuntu/+source/pango-graphite/+bug/540035
[13:20] <bullgard6> Why does  Debian  provide the DEB program package  xulrunner and Ubuntu does not? http://packages.debian.org/search?keywords=xulrunner&searchon=names&suite=stable&section=all
[13:22] <LordOfTime> !info xulrunner precise
[13:22] <LordOfTime> hm good question
[13:24] <Zhenech> probably because ubuntu does not split out xulruner from firefox/thunderbird
[13:24] <dholbach> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-June/000719.html
[13:24] <dholbach> ... Firefox 3.0 (and xulrunner 1.9) are now unsupported by Mozilla. ...
[13:28] <bullgard6> According to http://en.wikipedia.org/wiki/XULRunner is the stable release currently 13.0  dated June 1, 2012  (26 days ago).
[13:29] <Zhenech> bullgard6, so what is your point?
[13:31] <bullgard6> Zhenech: I'd like to know if I can access this package through Ubuntu repositories now or in a near furure.
[13:31] <LordOfTime> as an FYI, don't trust Wikipedia for everything
[13:32] <LordOfTime> s/everything/anything/
[13:32] <Zhenech> bullgard6, what do you need plain xulruner for?
[13:33] <bullgard6> Zhenech: For running Chatzilla with less overhead.
[13:33] <Rhonda> Huhm.  Strange that I have to renew my MOTU membership always around debconf. :)
[13:33]  * Rhonda peeks at cody-somerville 
[13:33] <Laney> AFFIRM YOUR LOYALTY
[13:34] <LordOfTime> what Laney said
[13:35] <Zhenech> bullgard6, humm… the seamonkey-chatzilla package depends on seamonkey-browser, which might work as "xulrunner" :)
[13:35] <LordOfTime> Zhenech: that installs the mozilla program "Seamonkey"
[13:35] <LordOfTime> just as an FYI
[13:36] <Zhenech> LordOfTime, which is the browser, which should be able to run arbitary xul stuff if poked long enough :)
[13:36] <LordOfTime> indeed
[13:37] <Zhenech> no idea how big the poking has to be though
[14:43] <bullgard6> dholbach, Zhenech, LordOfTime: thank you for commenting.
[15:23] <dholbach> are we having a MOTU meeting later on? can anyone chair? I might be a bit late because I'm on a call right now
[15:37] <coolbhavi> dholbach, yes the motu page says so!  at 16.00 UTC
[16:00] <coolbhavi> dholbach, ping
[16:14] <dholbach> coolbhavi, pong
[16:14] <dholbach> ok, so nobody started the meeting :)
[16:32] <vibhav> dholbach: Which meeting?
[16:35] <AmberJ> How do we specify a Launchpad PPA as build dependency when using Launchpad's "daily builds"?
[16:36] <TheLordOfTime> AmberJ:  specify the dependency within the PPA you're building to?
[16:36] <TheLordOfTime> s/to/in/
[16:46] <dholbach> vibhav, MOTU meeting
[16:46] <vibhav> dholbach: ah
[16:47] <vibhav> dholbach: You still busy?
[16:47] <dholbach> yes
[16:47] <dholbach> got another meeting coming up in 10 and trying to finish something else beforehand
[16:47] <AmberJ_> Did anyone answered my question? If yes, can someone copy/paste it? Thanks.
[16:47] <vibhav> How many hands do you have?
[16:47] <dholbach> vibhav, do you need help with anything?
[16:47] <AlanBell> AmberJ_: not sure you can do that
[16:48] <TheLordOfTime> i only think you can do that if you specify the other PPA's dependency within the PPA you're using a daily build recipe in
[16:48] <TheLordOfTime> (i.e. a daily builds ppa or something)
[16:49] <vibhav> dholbach: Ah fine, caryy on
[16:57] <AmberJ_> TheLordOfTime: Right, I should try adding PPA dependency to daily builds PPA
[16:57] <TheLordOfTime> AmberJ_:  yep, try that and see if that helps
[16:57] <TheLordOfTime> since i run into this all the time with my backports ppas
[16:57]  * TheLordOfTime keeps backport builddeps in a separate PPA
[16:57] <TheLordOfTime> s/backport/backported/
[16:58]  * micahg is sorry he missed the meeting
[16:59] <micahg> TheLordOfTime: amberJ: the alternative is to set your PPA to build against backports and request backports for what you need (assuming it can be backported)
[17:00] <TheLordOfTime> micahg:  i try to run my PPAs as close to the main builders as I can (on main builders for the standard repos, ERR: Backports cannot build-dep on other backports)
[17:00] <TheLordOfTime> but you're right
[17:01] <TheLordOfTime> setting the PPA to build against backports would fix the issue of having to have the build-deps in another PPA
[17:01] <TheLordOfTime> (unless those build-deps were rejected for normal backporting)
[17:05] <AmberJ_> I have added PPA dependency to daily build and requested to build again. Let's see if this works..
[17:05] <AmberJ_> In the meantime, I'll start with backports development process..
[17:20] <AmberJ_> The build completed successfully. But it did a source only build (it seems so). How can I do 'binary' "daily builds"?
[17:21] <micahg> hrm?  the recipe is a source build and should produce binaries
[17:24] <AmberJ_> micahg: You are right. Binary builds are pending but it shbows success for something... Does it shows success for source build (or what)? http://i.imgur.com/nw44T.png
[17:24] <AmberJ_> *shows
[17:25] <micahg> AmberJ_: I think the recipe just shows that it successfully uploaded a source build
[17:26] <AmberJ_> Ok, thanks micahg! :)
[17:28] <bkerensa> micahg: your making the headlines on reddit :)
[17:28] <micahg> hrm?
[17:29] <bkerensa> micahg: http://www.reddit.com/r/Ubuntu/comments/vp4r3/chromium_ppas_unmaintained/
[17:29] <bkerensa> ;)
[17:29] <micahg> :(
[17:29] <bkerensa> heh
[17:30] <micahg> well, anyone who's interested in helping to maintain chromium can let me know :)
[17:30] <bkerensa> should do a call for help :)
[17:31] <bkerensa> maybe ill blog about it and ask if anyone wants to contribute
[17:50] <arand> For an SRU (universe), should I be subscribing ubuntu-sponsors at the same time, or after ubuntu-sru? Also, is a debdiff required or is an bzr branch ok, and should it be merge-suggested or just linked to the bug report?
[17:52] <micahg> arand: ubuntu-sru doesn't need to be subscribed until it's uploaded unless you think it's so risky that you want pre-approval
[17:53] <micahg> merges to lp:ubuntu/foo show up in the sponsorship queue automatically
[17:53] <micahg> whether you use a debdiff or not is your preference
[17:53] <arand> Ah, -sru approves the -pending -> -updates, hmm, was a long time since I did this...
[17:56] <arand> Ah, right, so if I merge-propose to lp:ubuntu/lucid/pango-graphite I don't need to subscribe sponsors to the bug?
[17:58] <micahg> right, but just keep in mind that the bzr branch can't actually be merged if there hasn't been an SRU before, so if that's why you're doing it, don't, if you prefer the workflow, that's fine
[18:09] <arand> micahg: Hmm, odd that that doesn't work... This is a new upstream (micro)release, and the orig.tar.gz uses a tarball-in-tarball format, so should I be linking a .dsc (e.g. from a PPA) here?
[18:10] <micahg> arand: which package is this?
[18:10] <micahg> oh, right, you said pango-graphite
[18:11] <arand> Riddell: Nowadays you'll need a bug supervisor https://answers.launchpad.net/launchpad/+question/140509
[18:11] <micahg> so, for a microrelease, you need a microrelease exception
[18:11] <arand> Erhm...
[18:11] <arand> c.f. https://bugs.launchpad.net/ubuntu/+source/pango-graphite/+bug/540035
[18:13] <micahg> arand: you should cherry pick the fix vs a new upstream release for an SRU
[18:13] <arand> micahg: I read the wiki page as that only being neccessary in case of larger ones or if it was expected to do several microreleases.
[18:14] <micahg> arand: well, I don't the SRU team will accept a micro release at this point without an exception or pre-exception trial approval
[18:14] <Laney> yeah, if all of the changes in the new release are SRUable then you can upload that
[18:15] <Laney> MREs are about getting a pass on some parts of the normal process
[18:17] <arand> Well, sound like I should mail the techincal board to discuss it, anyways :)
[18:17] <Laney> look at the diff and decide
[18:19] <Laney> https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases
[18:19] <arand> There's a 15 line diff, plus minor documentation and autotools regen.
[18:32] <arand> Hmm, the reason I'm claiming the changes to be SRUable are that 1.) This new version is in Debian stable, 2.) It fixes a very critical bug (making login not work, plus several other applications crash), 3.) It's very hard to see how anything done to the package could make it worse than it is currently 4.) It looks like a reasonably small change.
[18:33] <arand> The problem is that 1.) I do not understand the fixes, 2.) I don't know if 3 of those 15 lines would suffice to fix the bug...
[18:34] <arand> But I think that the package should be either SRUd or ripped from lucid, on account of the seriousness of the bug.
[18:35] <arand> Should I bring this up on a mailing list (ubuntu-devel?) or simply carry on with the SRU? Or something else?
[18:39] <micahg> arand: I'd suggest asking for a pre-ACK, having a filtered diff for review might be helpful as well
[18:40] <arand> Yeah, full and filtered are already attached to the bug report.
[18:41] <arand> Ok, so the pre-ack is requested from technical-board@lists.ubuntu.com ?
[18:41] <micahg> arand: if you just take the filtered diff and add a changelog entry, that should be fine as an SRU
[18:42] <micahg> err, well, that filtered diff as a patch
[18:42] <micahg> assuming it builds that is
[18:43] <arand> Ok, I figured since the SRU page said "Note that some noise introduced by autoreconf is okay"
[18:43] <Laney> you could do it either way imho
[18:44] <arand> And that since the version is in Debian, it would decrease the diff to (both) upstream, and hence be nicer.
[18:44] <micahg> that only applies in the devel release
[20:49] <ajmitch> micahg: what, you're looking for suckers for chromium? ;)
[20:49] <micahg> ajmitch: yeah :)
[20:51] <ajmitch> just looking at your old answer on askubuntu, how much space were the builds taking up?
[20:52] <micahg> ajmitch: the space isn't the problem anymore, it's getting it to build
[20:52] <ajmitch> it chokes a bit on quantal?
[20:53] <micahg> no, I can't build a source package ATM, (well, and the choke on quantal)
[20:54] <ajmitch> oh dear
[20:55] <micahg> if someone really wants to dig in, I think it just needs a translations update
[20:55]  * ajmitch could add it to his ever-growing todo list :)
[20:55] <ajmitch> though I think it should be added near the bottom of my list
[20:55] <micahg> one needs about ~5GB of disk space as it requires checkouts of some hefty branches
[20:56] <ajmitch> that's not too bad
[20:57] <ajmitch> what are you using to generate a new source package at the moment?
[20:58] <micahg> the get-orig-source rule
[20:59]  * ajmitch should probably upgrade a system to quantal
[21:00] <micahg> ajmitch: not needed, chroots work beautifully
[21:00] <ajmitch> yeah but I should upgrade for the breakage anyway
[21:01] <ajmitch> my desktop at home doesn't get used much except for gnome-terminal, firefox & chromium
[21:01]  * Laney wonders if kvm broke in Q
[21:02] <Laney> sid VM is suddently dead
[21:02] <ajmitch> that's :(
[21:04] <AmberJ_> If I run 'pbuilder create' and then run it again, does it updates existing pbuilder chroot?
[21:05] <AmberJ_> I know there's 'pbuilder update' for this but then what does RE-running 'pbuilder create' do?
[21:05] <jtaylor> use update to update it
[21:05] <jtaylor> either fail or replace the old one
[21:06] <TheLordOfTime> from what i've seen it nukes the old one and recreates it
[21:06]  * TheLordOfTime did that by accident once
[21:06] <AmberJ_> Ah right, 'pbuilder update' is wht way to go... Thanks!
[21:07] <ScottK> ajmitch: How many months would it take you to do the checkout though?  Assuming it's not from a NZ server, that is.
[21:07] <ajmitch> ScottK: probably about 6 months
[21:07] <ScottK> Probably doesn't fix micahg's timeline very well.
[21:13] <ajmitch> ScottK: checked out about 1GB so far
[21:13] <ajmitch> usually my problem is data caps rather than speed :)
[21:13] <ScottK> OK.
[21:14] <ajmitch> except when fetching from LP, that's just painful
[21:14] <ScottK> Is .nz upstream of .au in the big data pipes to the rest of the world?
[21:14] <ScottK> Maybe you got all StevenK's bandwidth.
[21:14] <ajmitch> NZ is closer to the US on the main cable we use
[21:14] <ajmitch> I'd better watch out, he'll probably fly over & hurt me
[21:16] <ajmitch> though he's probably not awake yet to notice
[22:02] <micahg> bkerensa: thanks for the blog post, one of these days I need to get my own blog
[22:05] <iulian> Blogs are boring. :)
[22:06] <TheLordOfTime> arguing is worse
[22:13] <ScottK> TheLordOfTime: arguing is fun.  You just have to do it carefully around here or someone whacks you with the CoC.
[22:14] <ajmitch> yes, you have to respectfully tell people that they suck
[22:48] <ajmitch> micahg: so I'd try & build it all if I could only connect to svn.webkit.org from home, seems to be some routing breakage causing me pain :)
[22:50] <micahg> ajmitch: hrm?  you shouldn't need that
[22:50] <ajmitch> get-orig-source seems to be trying to check out specific revisions of things from there
[22:51] <micahg> orly?  hrm, weird
[22:51] <ajmitch> yarly
[22:52] <micahg> hrm, that must be upstream chromium doing something funny
[22:52] <ajmitch> wouldn't surprise me
[22:53] <ajmitch> this is from branching lp:chromium-browser, I presume that's the best place to start?
[22:53] <micahg> that should work (although it might be a bit behind)
[23:28] <micahg> ScottK: Laney: I forget, backports doesn't respect components, right?