[00:13] <bdrung> can someone change the status of https://code.launchpad.net/~yofel/ubuntu/lucid/ubufox/lp557240/+merge/29858 to merged?
[00:14] <yofel> bdrung: done ;)
[00:14] <bdrung> thanks
[00:22] <bdrung> yofel: can you mark https://code.launchpad.net/~serge-hallyn/ubuntu/lucid/qemu-kvm/memleak-fix/+merge/28645 as merged?
[00:23] <yofel> no, I could only mark the first one as merged because that was my branch
[00:24] <bdrung> aha, ok
[00:25] <bdrung> then i have to wait that launchpad get fixed
[00:25] <isleshocky77>  I've been looking through the packaging documentation for a while now and still I'm running in circles. Could someone set me straight. I took the source of pidgin-libnotify and modified one file. Now I want to get a build in my personal launchpad ppa for x32 and amd64
[00:27] <bdrung> isleshocky77: you might want to ask this in #ubuntu-motu
[00:27] <isleshocky77> bdrung: Thanks.
[00:39] <micahg> bdrung: #ubuntu-packaging is for PPA packaging Qs
[00:40] <bdrung> micahg: k, that's an even better place
[00:40] <micahg> :)
[01:21] <Toluxero> hi!
[01:24] <thumper> hi
[01:25] <Toluxero> hi thumper i need help with a team.
[01:25] <Toluxero> can you help me?
[01:26] <thumper> not sure how much help I can be, but ask away
[01:28] <Toluxero> the owner registered in the team is not more available and I need a ticket to send a LoCo Council, thumper
[01:29] <thumper> which team?
[01:29] <Toluxero> https://launchpad.net/~ubuntu-mx
[01:31] <thumper> https://edge.launchpad.net/~fetova is an admin of the team
[01:31] <thumper> what is it you need to do?
[01:32] <Toluxero> ahm, actually I'm a LoCo Contact of the team, but the owner is not available, the LoCo Council know the situation.
[01:33] <Toluxero> and request me a ticket support
[01:36] <thumper> https://answers.edge.launchpad.net/launchpad/+addquestion <- say the team and loco council info
[01:37] <Toluxero> ok
[01:37] <Toluxero> thats all?
[01:43] <thumper> Toluxero: that's all I think
[01:44] <Toluxero> thumper, thanks! :D
[01:46] <thumper> np
[01:47] <Toluxero> thumper, so... the question in what language?
[01:47] <thumper> english preferrably as the admins are all english speaking
[01:48] <Toluxero> oks
[01:56] <Toluxero> thumper, thanks again :D
[09:18] <mrevell> Hello
[09:19] <lifeless> !oops
[09:20] <lifeless> !help
[09:20] <lifeless> @help
[09:21] <nigelb> lifeless: !messagethebot :D
[09:21]  * nigelb hides.
[09:22] <lifeless> nigelb: if you know how to teach it a new help topic, that would be grand
[09:22] <lifeless> I wrote up a wiki page about oopses
[09:22] <lifeless> and I'd like to make it easy to point people about it
[09:32] <nigelb> lifeless: I do
[09:33] <jussi> o/
[09:33] <nigelb> lifeless: jussi will help you with it
[09:33] <nigelb> what do you want to add?
[09:33] <jussi> !owner
[09:33] <lifeless> I want tou be able to do !oops
[09:33] <jussi> :)
[09:34] <lifeless> and have it give a link to
[09:34] <nigelb> jussi: "kindly"? free?
[09:34] <jussi> lifeless: what should !oops say?
[09:34] <lifeless> https://help.launchpad.net/Oops
[09:34] <jussi> nigelb: correct
[09:34] <nigelb> whoa, cool
[09:34] <jussi> !test
[09:34] <lifeless> jussi: just giving the URL would be ok
[09:35] <lifeless> saying a little more like 'An OOPS is a system error in launchpad, please see https://help.launchpad.net/Oops' would be better.
[09:35] <jussi> lifeless: we need to follow how factoids need to be constructed, small explanation, url.
[09:35] <lifeless> jussi: syre
[09:35] <lifeless> sure
[09:36] <jussi> lifeless: ok. for future reference, use this syntax, and the bot will forward it for moderation. !oops is <reply>An OOPS is a system error in launchpad, please see https://help.launchpad.net/Oops
[09:37] <lifeless> with the <reply> in it ?
[09:37] <jussi> !oops
[09:37] <jussi> lifeless: yes
[09:37] <lifeless> ok, thanks
[09:37] <lifeless> I'll try to remember ;)
[09:37] <nigelb> \o/
[09:37] <jussi> no probs.
[09:37] <jussi> !bot
[09:37] <jussi> lifeless: that link has how to do it if you ever need it again
[09:38] <lifeless> jussi: thanks a lot
[09:38] <jussi> lifeless: also, Ive made that a specific factoid for this channel only. if you want to call it outside of here, use !oops-#launchpad
[09:39] <lifeless> ok
[09:40] <jussi> ok then. Laters!
[11:22] <aquarius> maxb, ping
[11:22] <maxb> hi
[11:22] <aquarius> yeah, I'm thick and meant just the android-trunk bit :)
[11:22] <aquarius> er, android-client
[11:22] <maxb> just wanted to check :-)
[11:23] <aquarius> Launchpad: saving me from my own stupidity. again :)
[11:24] <maxb> updated, import in progress
[11:31] <aquarius> winner, thanks
[11:40] <aquarius> If I've got two separate codebases which may share some code and are of the same sort of thing -- we have an "Android client for Ubuntu One" project on LP, but we'll actually have a few separate clients, in time (one for contacts, one for files, etc) -- should they be separate LP projects? Or are separate branches in the one project a good idea?
[11:49] <maxb> aquarius: Generally the question "Are the Bazaar branches going to have interrelated history?" is a good guide to "Should these things all be one project?"
[11:50] <aquarius> well...some of it will be interrelated. The different clients will share code, but will start from different places. I'm not sure what that means as an answer to your question :)
[11:53] <maxb> Maybe there's a shared library plus N clients, all of which are projects?
[11:58] <wgrant> aquarius: Sounds like they should be separate projects.
[11:58] <wgrant> Or a single branch.
[11:59] <aquarius> wgrant, cheers; that's exactly why I'm asking the question. Obviously all of these are doable technically; what I'm trying to do is fit in with the zen of launchpad
[12:14] <esteve> hi all
[12:15] <esteve> I bought a subscription the other day and created a proprietary project
[12:15] <esteve> but I can't seem to find the documentation to make branches private
[12:15] <esteve> doesn't anybody know where I can find it?
[12:16] <mwhudson> esteve: you have to ask an admin (aka losa) for that
[12:17] <esteve> mwhudson: thanks
[12:17] <noodles775> (that is, they can update a setting so that your project will default to private branches)
[12:18] <esteve> noodles775: so all the branches that my team pushes will be made private, am I right?
[12:18] <noodles775> Once a losa has update your project, all the branches that your team pushes for that project will be private by default, yes. (ie. pushing to ~username/project-name/branch-name)
[12:19] <noodles775> (or ~teamname/project-name/branch of course :) ).
[12:19] <esteve> noodles775: great! thanks
[12:20] <esteve> so, who is an admin/losa?
[12:21] <esteve> or can I just open a question against malone (not sure about the name)?
[12:21] <noodles775> esteve: they would normally have already jumped by this point (by mentioning losa), but they're currently off sprinting together, so it might be worth asking a question against launchpad-code.
[12:26] <esteve> noodles775: ok, thanks, I just opened one https://answers.launchpad.net/launchpad-code/+question/120715
[12:46] <X3> can anyone shed some light on why the svn revisions are off on https://code.launchpad.net/~x3lectric/xbmc/svn-trunk
[12:46] <X3> comparing to http://trac.xbmc.org/timeline
[12:47] <X3> the svn versions dont match but commits do
[12:48] <X3> the real svn displays version 32624 and the lauchapad is 2something its well off version nr
[12:49] <X3> is this a bug in launchpad?
[12:50] <wgrant> X3: Bazaar revision numbers are unique within a branch. Subversion revision numbers are unique across all branches in the repository.
[12:50] <wgrant> If you do an svn log on trunk, you'll see there are revision numbers missing (since they're in other branches).
[12:51] <wgrant> bzr doesn't know about the other branches, and doesn't count the revisions outside trunk.
[12:51] <X3> wgrant but if I build that those packages will never trigger update on ppa cause revision is way lower
[12:51] <wgrant> X3: What's your versioning scheme?
[12:51] <X3> er svn?
[12:51] <bigjools> wgrant: your branch should be on staging now
[12:51] <wgrant> bigjools: Thanks. I'll QA it.
[12:52] <wgrant> X3: I mean, how do you construct the version string for your packages?
[12:52] <X3> you mean the recipe?
[12:53] <wgrant> Yes.
[12:53] <X3> atm none cause idk how to
[12:53] <X3> + the discrepancy im totally lost
[12:54] <wgrant> If you're not already building packages from svn directly, then there are no packages with the svn revision number for your bzr packages to be less than.
[12:59] <X3> wagrant what recipe should it use that?
[13:08] <X3> can you help with recipe?
[13:32] <det> How often does PPA publication happen ?
[13:33] <maxb> 5 minutes, in theory, though it seems sluggish lately
[14:00] <bigjools> det, maxb: nominally it's 5 minutes but when the load is large it will take longer
[14:34] <det> Thanks
[14:34] <det> seems mine took like 1 hour
[15:52] <pc_magas> hi
[15:55] <pc_magas> hi
[16:34] <hexmode> rockstar: is there a bug for recipe builds on Maverick?  They fail b/c of no orig.tar.gz
[16:34] <rockstar> hexmode, not that I'm aware of.
[16:34] <rockstar> hexmode, do you have a buildlog I can see?
[16:35] <hexmode> http://launchpadlibrarian.net/53488576/buildlog.txt.gz
[16:35] <hexmode> from https://code.edge.launchpad.net/~hexmode/+recipe/org-mode-daily
[16:37] <hexmode> Also, just fyi, I'm impressed that estimated build times were actually pretty accurate this morning.
[16:38] <hexmode> rockstar: ^^ in case you missed it
[16:44] <rockstar> hexmode, well, the problem wasn't in their accuracy, but in the number of packages that were "cutting" in line.
[16:45] <hexmode> heh
[16:51] <hexmode> rockstar: final q: build schedule says "built daily" but no builds have happend for several days.  Why?
[16:52] <rockstar> hexmode, known issue, but I don't know the details.  I'll have to find out.
[16:53] <hexmode> rockstar: ok, if you know who I should bug about it, I could find out.  otherwise, thanks.
[16:54] <rockstar> hexmode, you should me about it.  :)
[17:02] <rockstar> hexmode, sorry, just got to looking at your Maverick issue, and it looks like that bug is https://bugs.edge.launchpad.net/launchpad-code/+bug/614768
[17:05] <hexmode> rockstar: thanks...
[17:52] <hexmode> rockstar: also, looks like it does a source build first (-S) and then reschedules for a binary build (ex: https://code.edge.launchpad.net/~hexmode/+recipe/emacs-daily/+build/796)
[17:52] <rockstar> hexmode, yeah, that's correct.
[17:52] <hexmode> rockstar: but, under pending builds, it doesn't really show that.
[17:52] <rockstar> hexmode, there's a bug about that, but it's not really a pending build.  It built the source package like you asked.  :)
[17:52] <hexmode> rockstar: it says "successful build" ... even though, since these are from trunk, they could fail
[17:52] <hexmode> heh
[17:53] <hexmode> rockstar: ok
[17:57] <bahamas10> i can't figure out how to get the FAQ to show up on my projects overview
[18:56] <lamont> wgrant: around?
[18:57]  * lamont bets on sleeping
[18:57] <lamont> wondering if the build-record populator that we run after PaS changes got updated for arch: linux-any packages as part of the fix
[22:24] <MTecknology> Is there any way I could have https://launchpad.net/nginx-obsolete unlinked from https://launchpad.net/~nginx ?
[22:40] <wgrant> lamont: Yes.
[22:40] <wgrant> lamont: I was thinking about that, and yes, it should work.
[22:40] <wgrant> But I really need to strip it down to a create-build-records-only mode.
[22:41] <wgrant> However, just running it right after the rollout should fix everything.
[22:41] <wgrant> And fix a few things that shouldn't be fixed, but they're not significant.
[22:45] <lamont> wgrant: heh
[22:46] <lamont> 'twould be nice if there were a way to tell it package, version, and distro-arch-series, and have it either create it because it should, or bitch-n-whine and ask if I'm really really really sure I want that even though it shouldn't exist.
[22:46] <lamont> and have it do just that one tuple, instead of walking the world
[22:46] <lamont> oh, and ponies.  I want ponies.
[22:47] <lamont> anyway, afk
[22:48] <wgrant> Hmm.
[22:49] <lifeless> MTecknology: what is nginx-obsolete ?
[22:50] <MTecknology> lifeless: it was replaced by launchpad.net/nginx
[22:50] <lifeless> grah, why ?
[22:50] <MTecknology> lifeless: Realistically.. you could simply delete it - but I don't think you guys do that
[22:50] <lifeless> anyhow - file a question on launchpad.net/launchpad asking for help
[22:50] <lifeless> there is no help contact on atm
[22:51] <MTecknology> lifeless: It was my fault- you can slap me :(
[23:02] <MTecknology> I want to make a project called builders :(
[23:02] <MTecknology> wgrant: I see the builders have returned to a state of normalcy - That's nice. :)
[23:03] <wgrant> Were they broken?
[23:03] <wgrant> They'll be even better than normal tomorrow.
[23:19] <MTecknology> wgrant: why's that?
[23:21] <wgrant> MTecknology: The buildd master has been rewritten.
[23:21] <MTecknology> wgrant: cool - any specific changes?
[23:22] <mwhudson> does more stuff in parallel
[23:22] <MTecknology> oh, cool
[23:34] <bdrung> why can't i change the status of https://code.launchpad.net/~toabctl/ubuntu/maverick/xf86-input-wacom/new_upstream_0.10.7/+merge/30469 to invalid or something similar?
[23:36] <micahg> bdrung: it's a personal branch, not an ubuntu branch
[23:39] <bdrung> micahg: but it's a merge request
[23:39] <ajmitch> bdrung: oddly enough there's the resubmit proposal & delete proposal links listed
[23:39] <bdrung> micahg: the members of the target branch team should be able to reject a merge request
[23:40] <bdrung> i could delete the merge request
[23:40] <ajmitch> ~ubuntu-branches is set as reviewer (& owner of the branch)
[23:40] <bdrung> but then the commend would vanish
[23:40]  * micahg has no idea
[23:41] <ajmitch> you're able to set the reviewer of that branch, but that still doesn't fix the problem
[23:41] <ajmitch> I think the default reviewer for all those branches needs to be changed from ~ubuntu-branches
[23:42] <bdrung> yes
[23:42] <ajmitch> we probably need the TB to do it
[23:42] <bdrung> to ~ubuntu-dev?
[23:42] <ajmitch> or maybe lifeless, he's in the owning team :)
[23:42] <ajmitch> probably not
[23:42] <ajmitch> some might be ~ubuntu-core-dev, it'll need some thought