[04:56] <kb9vqf> If anyone can/is willing to rescore a build or two, these are the most critical (repeatable crash fixes):
[04:56] <kb9vqf> https://launchpad.net/~kb9vqf/+archive/kde3auxbuilder/+build/1380158
[04:56] <kb9vqf> and https://launchpad.net/~kb9vqf/+archive/kde3auxbuilder/+build/1379358
[08:07] <AlanBell> soren: we went through the list one by one on a google spreadsheet, checked against wiki pages, testimonails, launchpad photos, blogs, flickr photos, asked them on IRC etc.
[08:08] <wgrant> AlanBell: That's an impressive effort.
[08:10] <AlanBell> it was a group effort thing by all of #ubuntu-women
[08:11] <AlanBell> I joined the project a couple of months ago and asked if there was any hard data and SMART goals for what they wanted to achieve
[08:11] <AlanBell> as there wasn't I helped them find some
[08:13] <AlanBell> it was a fairly manual process, I copied and pasted names from the launchpad web interface and de-duplicated the nested groups manually
[08:14] <wgrant> AlanBell: Are you aware of https://launchpad.net/~SOMETEAM/+rdf?
[08:15] <AlanBell> yes, but launchpadlib is giving me all I need I think
[08:15] <AlanBell> http://paste.ubuntu.com/334674/
[08:16] <AlanBell> the rdf thing would still leave me with the nested groups and de-duplication problem
[08:16] <wgrant> AlanBell: +rdf should handle the nesting for you, IIRC.
[08:16] <wgrant> It should just return a flat list of all members, including those of descendant teams.
[12:30] <FFEMTcJ> Anyone around? I'm in launchpad answers, and each question shows 'For: Ubuntu mozilla-firefox' - if I select edit, it shows the right package.. Does anyone else see this? I am on edge.
[12:31] <wgrant> FFEMTcJ: That's fixed in the development branch.
[12:31] <wgrant> FFEMTcJ: So it will probably be fixed on edge Mondayish;
[12:31] <FFEMTcJ> wgrant: cool.. Thanks
[14:28] <thisfred> ohai
[14:30] <LarstiQ> middag thisfred :)
[14:31] <thisfred> I'm trying to migrate a project from google code to launchpad, but am having some difficulty understanding the launchpad code hosting infrastructure. Is there a canonical (haha) resource on what series etc. exactly mean? Also: I have trunk of my imported succesfully, but I would like it to live at lp:project/trunk, and currently I can't see how (it's lp:~thisfred/project/trunk)
[14:31] <thisfred> hoi LarstiQ ! :)
[14:32] <LarstiQ> for a given series you can nominate the development focus, that can then be adressed as lp:project/series
[14:33] <LarstiQ> or lp:project for the main one
[14:33] <thisfred> (LarstiQ: I'm moving autoqueue over to lp, so I can use bzr, and have it in a PPA so it'll be easy to install for Ubuntu users)
[14:33] <LarstiQ> if I'm not messing things up
[14:33] <LarstiQ> thisfred: right, cool :)
[14:33] <thisfred> LarstiQ: right, but how do series relate to branches, if at all?
[14:34] <LarstiQ> thisfred: a series is a more abstract object that spawns releases
[14:35] <LarstiQ> looking at https://edge.launchpad.net/bzr for example
[14:35] <thisfred> Ok, I'm not sure I like another layer, but then my project is a lot simpler than say, Ubuntu ;)
[14:35] <LarstiQ> right
[14:35] <LarstiQ> so for a very simple project, you could just use 1 series "trunk"
[14:35] <LarstiQ> and spin off all releases from that
[14:35] <thisfred> I can just have one series, and that's it, I won't have to think about it
[14:35]  * LarstiQ nods
[14:36] <thisfred> I think that's what I've done
[14:36] <LarstiQ> so all branches would then just live directly under the project umbrella, and one of them' you'd nominate as the focus
[14:36] <LarstiQ> https://edge.launchpad.net/bzr/trunk/+edit
[14:37] <thisfred> https://edge.launchpad.net/autoqueue has this, I think
[14:37] <LarstiQ> after name, summary and status, there is a branch
[14:37] <LarstiQ> if you fill in ~thisfred/queue/trunk there, you will get that when you say lp:autoqueue
[14:38] <thisfred> awesome!
[14:38] <LarstiQ> for bzr trunk, it is ~bzr-pqm/bzr/bzr.dev
[14:38] <LarstiQ> (and for lp:bzr/2.0 it is ~bzr-pqm/bzr/2.0)
[14:39] <LarstiQ> thisfred: hope that helps :)
[14:39] <thisfred> LarstiQ: I think so, thanks a lot!
[14:39]  * LarstiQ now looks at the first part of the question
[14:39] <thisfred> yup, it worked!
[14:40] <thisfred> was just that last piece I was missing :)
[14:40] <LarstiQ> https://help.launchpad.net/Projects/SeriesMilestonesReleases#Series I'd guess
[14:40] <LarstiQ> thisfred: good :)
[14:42] <thisfred> now I'm gonna look at making it a proper python installable
[14:48] <LarstiQ> thisfred: .deb packaging wise?
[14:48] <thisfred> LarstiQ: well, first distutils (or whatever works, but it's not super complicated) and then I'll put it in a PPA somehow, so yeah I guess
[14:49] <LarstiQ> ok
[14:49] <thisfred> The nice thing is that the mirage acoustic analysis stuff is in a PPA already, so I think I can depend on that
[14:49] <thisfred> or copy it if not :)
[14:49] <LarstiQ> I think you'll need  to copy it
[14:49] <thisfred> I'm at the very beginning of the road to learning packaging
[14:50] <LarstiQ> but there's PPA-to-PPA copying, so that's not too hard
[14:50] <LarstiQ> thisfred: :)
[14:50] <thisfred> right
[14:50] <thisfred> It's cool though, since I keep running into it for work, so this is a good way to learn everything from the start
[14:50]  * LarstiQ nods
[14:51] <LarstiQ> thisfred: feel free to bug me if you have questions about packaging
[14:51] <thisfred> And I have 2 weeks off soon :)
[14:51] <thisfred> awesome, I will!
[14:53] <thisfred> and then when I'm done, I'm gonna experiment with a couch backend, and see if I can improve the speed
[14:53] <LarstiQ> :)
[14:53]  * LarstiQ goes to the AH and then mom for Sinterklaas
[15:31] <j^> Cannot lock LockDir(lp-mirrored:///~ubuntu-branches/ubuntu/lucid/libv4l/lucid/.bzr/repositorylock): File exists:
[15:31] <j^> https://code.launchpad.net/~ubuntu-branches/ubuntu/lucid/libv4l/lucid
[15:31] <j^> is this a common error or should i file a bug about it?
[17:34] <bjsnider> i'm confused about how to specify package versions that the build system will recognize, that do not include the ppa versions as well. only the upstream version
[17:36] <bjsnider> so for instance if i want the build system to grab a package that is 0.5.6-1+dfg5 or greater, but then ignore the fact that there is a ppa string following a tilde
[17:36] <bjsnider> i would say >= (0.5.6-1+dfg5) i assume
[17:37] <bjsnider> but if i have a version built in a ppa that then follows that upstream version number with ~ppa1 and the build system says this is not the right package because of the ppa1 part, how do i get it to ignore that?
[17:37] <bjsnider> i thought it already did unless you specify it
[17:40] <geser> -1+dfg5~ppa1 < -1+dfg5, so the requirement is not fulfilled
[17:50] <bjsnider> yes, that's the problem, but can i tell it to ignore the ppa version, with a wildcard or something?
[17:59] <geser> no, unless you find a version smaller than -1+dfg5~ppa1
[18:00] <geser> try using >= 0.5.6-1+dfg5~~