[00:36] <michaelh1> Hi there.  Is there a tool to upload release files from the command line, preferably with resuming?
[00:37] <michaelh1> I saw https://answers.launchpad.net/launchpad/+question/41204 for a hardcore version...
[00:38] <jelmer> michaelh1: There are some Launchpad command line utilities, it might be useful to add a command to those
[00:38] <jelmer> michaelh1: I don't think that has happened yet though
[00:38] <james_w> michaelh1: there's one in ubuntu-dev-tools that doesn't have resuming
[00:39] <james_w> (I doubt resuming can be implemented given the interface LP currently exports)
[00:39] <jelmer> james_w: ah, cool, wasn't aware of that one
[00:39] <jelmer> michaelh1: fwiw, it's called lp-project-upload
[00:40]  * michaelh1 reads...
[00:41] <poolie> there's a script in bzr's source tree too
[00:41] <poolie> it's a bit dodgy
[00:41] <poolie> hello to all of you
[00:41]  * jelmer waves to poolie
[00:43] <michaelh1> Right.  Will play.  It's a 100 MB GCC release so we'll see how it goes
[01:04] <lavid> hello. question about recipes to automate building. i imagine i need some debian dpkg special sauce somewhere for this all to properly work. do i need to make a new branch that contains that stuff (dependencies, etc) and then do something like merge packaging lp:~rawtherapee/rawtherapee/packaging, yes? are there any fully functional examples of using recipes where the debian stuff is merged in from a branch?
[01:05] <lavid> oh, and this is what i have thusfar: https://code.edge.launchpad.net/~rawtherapee/+recipe/rawtherapee-staging
[01:12] <wgrant> lavid: https://code.edge.launchpad.net/~wgrant/+recipe/ivle-trunk is one of mine.
[01:13] <wgrant> lavid: The debian-packaging branch is a branch of trunk with debian/ added.
[02:18] <LifeIsPain> I now have access to the SF tracker for a project and so started closing bugs which should have been closed earlier, the launchpad bugs that are associated with these bugs aren't then getting updated, upon clicking on the status, they each read:
[02:18] <LifeIsPain> The information about this bug in Launchpad is automatically pulled daily from the remote bug. This information was last pulled on 2010-07-14.
[02:19] <LifeIsPain> so is the launchpad remote bug tracker slightly foobar with sf?
[03:17] <nhandler> How do I go about removing translations for a series so that the series can be deleted?
[03:19] <nhandler> Never mind, I figured it out.
[04:49] <MTecknology> Why do recipes tack on ~lucid1 or ~karmic2 or w/e
[04:49] <MTecknology> I get what they mean - I'm just wondering if those being optional tags might be better?
[04:50] <MTecknology> Like.. {debupstream}-ppa{upload} or {debupstream}~{ubuntuversion}{upload}
[04:50] <MTecknology> Might make things much more flexible. Personally - I don't get why those should need to be there. If you're uploading to different versions..
[04:51] <MTecknology> I think I kind of get it - but I'm not a huge fan
[04:52] <micahg> MTecknology: you can only have 1 version of something in a repo even in a different pocket
[04:58] <MTecknology> micahg: does it work the same in ubuntu too? You can't have the same version if the packages are different?
[04:59] <micahg> MTecknology: correct
[04:59] <MTecknology> micahg: how do you deal with that if the source version and everything are the same but the debian/ needs to change a little?
[05:00] <micahg> MTecknology: you build a 0.XX.XX.1 where XX.XX is the previous release in UBuntu at least
[05:01] <MTecknology> oh
[05:01] <micahg> MTecknology: in PPA, ~lucid1 and such
[05:01] <MTecknology> I wish launchpad recipes supported commands. I would love to just rm one file and sed one other - then the 0.7 debian would work for 0.8
[05:01] <micahg> MTecknology: here's a wiki on versioning in Ubuntu: https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update%20the%20packaging
[05:02] <MTecknology> micahg: thanks
[05:03] <MTecknology> micahg: would it be a bad idea to maybe request a feature that you can omit the ubuntu version part and build the same binary for multiple versions?
[05:04] <micahg> MTecknology: probably
[05:04] <MTecknology> oh
[05:04] <MTecknology> Any reason?
[05:04] <micahg> w/o Ubuntu version it steps on the debian build versions
[05:05] <MTecknology> micahg: I meant so you could do something like {debupstream}ppa{upload}
[05:05] <micahg> MTecknology: sounds like a bad idea
[05:06] <MTecknology> micahg: :(
[05:08] <micahg> try a dpkg --compare-versions on that and {debupstream}-1 and you'll see the issue
[05:13] <MTecknology> micahg: I was thinking {debupstream} usually has the -1 or -0 in it when I look at them - but I guess the uncommon case
[05:13] <MTecknology> micahg: in that case it'd be  {debupstream}-0ppa{upload}
[05:13] <micahg> that might work
[05:13] <MTecknology> Then just the same thing as telling launchpad to copy binary for versions
[05:14] <micahg> well, recipes shouldn't be based on a debian version, but rather the upstream project version IMHO
[05:14] <MTecknology> I'm trying to make them very easily build nginx packages
[05:24] <micahg> MTecknology: well, if debian/rules will be differnt for each release, you need a rebuild
[05:27] <MTecknology> micahg: yup - but this won't need to be
[05:28] <MTecknology> micahg: aside from one patch that needs to be removed - I can take the lenny debian/ for nginx 0.7.x and use it in maverick to build nginx 0.8.x
[05:31] <micahg> MTecknology: the point is the source needs to be rebuilt each for each series
[05:33] <MTecknology> micahg: As opposed to having it build for lucid and copy binary to maverick?
[05:33] <micahg> MTecknology: right
[05:34] <MTecknology> micahg: I know it needs to now - I just don't think it makes sense
[05:35] <MTecknology> micahg: else I could just have daily builds - then maually go out to LP and copy binary and have the same effect - except that ~lucid1 would be part of the version number in maverick
[05:36] <micahg> MTecknology: the libraries it's linked to are different in each series aren't they?
[05:38] <MTecknology> micahg: not that I know of
[05:38] <MTecknology> micahg: like I said - I can use the exact same debian/ - I can grab a .deb from lenny and toss it on maverisk
[05:38] <MTecknology> s/sk/ck/
[05:42] <LifeIsPain> ok, from my previous question, I now see that https://bugs.edge.launchpad.net/bugs/bugtrackers/sf has been disabled, which explains why none of them had been updated
[05:42] <MTecknology> !info nginx
[05:43] <micahg> MTecknology: work yes, ideal, probably not
[05:44] <MTecknology> micahg: it just seems like a waste to me
[05:45] <micahg> MTecknology: you take advantage of compiler optimizations in the toolchain and any other advantages from the libraries in the release
[05:50] <twb> So launchpad is 100% Affero GPL'd now, right?
[05:50] <twb> Are there any deployments other than Canonical's?
[05:51] <lifeless> LP is AGPL yes
[05:51] <mwhudson> i saw a link to one somewhere
[05:51] <MTecknology> twb: I was going to try but gave up realizing it'd never work :P
[05:51] <lifeless> we're aware of a couple
[05:52] <MTecknology> only internal stuff though
[05:52] <lifeless> you need to rebrand it - the icon artwork is (IIRC) trademarked
[05:52] <lifeless> MTecknology: well, its not entirely clear whether they are all internal deployments ;)
[05:52] <twb> Is there a turnkey way to do that, or do you need to grovel through the tarball?
[05:52] <lifeless> but we have folk that pop up and tell us when things are broken
[05:53] <lifeless> twb: I'm not aware of a specific turnkey way, no - but it should be as simple as replacing the icing, so fairly easy.
[06:29] <MTecknology> Build will start in 4sec
[06:29] <MTecknology> You mean 4 hours?
[06:31] <MTecknology> I'm excited to see the changes being made
[09:52] <dholbach> are we there yet? :-P
[09:53] <spm> dholbach: you'll get a smacked bottom with questions like that; :-) Not yet, but progressing well.
[09:54] <twb> "Pipe down or I'll turn this migration around RIGHT NOW and we'll rollback straight home"
[09:54]  * dholbach hugs spm and twb :)
[09:54] <twb> cooties!
[09:56] <nigelb> "Are we there yet?" hahaha
[10:29]  * bilalakhtar wishes spm and twb good luck
[10:29]  * bilalakhtar smacks dholbach 
[10:29]  * dholbach strangles bilalakhtar :)
[10:29] <bilalakhtar> Are we near?
[10:29]  * bilalakhtar kicks dholbach 
[10:30] <bilalakhtar> enough!
[10:30] <dholbach> bilalakhtar: I guess we better stay quiet in the back :)
[10:30] <bilalakhtar> dholbach: yup, nothing to do until lp is back
[10:30] <bilalakhtar> LP IS UP!
[10:30] <spm> parts *may* be up - the rollout isn't (yet) complete
[10:33] <bigjools> we need a launchpad-release-party channel
[10:33] <dholbach> bigjools: HAHAHA
[10:33] <bigjools> complete with smackdown bot
[10:49] <Laney> should I be able to edit the status of packaging branch merge proposals?
[11:01] <dholbach> spm (and everybody else): good work!
[11:19] <henninge> Laney: Does your problem still exist or was it related to Launchpad being read-only until 30 minutes ago?
[11:20] <nigelb> yay, we're there!
[11:20]  * nigelb hugs spm and others :)
[11:21] <nigelb> bigjools: totally agree on the release channel.
[11:21] <henninge> only that we are working to get rid of releases ... ;)
[11:21] <Laney> henninge: It's still there, but I don't know if it's a problem
[11:22] <Laney> https://code.edge.launchpad.net/~arky/ubuntu/lucid/sysinfo/fix-524120/+merge/19746 ← I want to edit the status of this merge proposal
[11:22] <nigelb> hahaha, we can still say "is it out yet"
[11:24] <henninge> Laney: What's your relationship to the proposal? It does not look lile you are either the submitter or on the reviewer team.
[11:24] <spm> Laney: huh. lookin'....
[11:24] <Laney> henninge: I can upload to the target
[11:25] <Laney> so I figure I should be able to twiddle the bits
[11:26] <henninge> Hm, I am not sure.
[11:27] <spm> I'd suggest per henninge's - it doesn't look like you have the perms to ok the branch for merging; only james does aiui.
[11:27]  * spm has been ordered into lunch...
[11:28] <wgrant> It's a sort of bug.
[11:28] <wgrant> Sort of.
[11:28] <wgrant> For Ubuntu, the uploaders probably should be able to review.
[11:28] <Laney> it's probably complicated as the target is lucid...
[11:28] <wgrant> But they can't.
[11:29] <Laney> wgrant: Is there a bug# for this?
[11:30] <Laney> I thought I filed a similar bug in the past
[11:31] <henninge> wgrant: "uploaders" means "being able to push to branches"?
[11:32] <Laney> bug 540250 is the one I filed a while ago
[11:33] <henninge> so, is this a regression?
[11:33] <Laney> let me find another branch
[11:34] <Laney> henninge: No. I can edit lp:ubuntu/xxx proposals it seems.
[11:36] <Laney> oh, hang on...
[11:37] <wgrant> Bug #612391?
[11:37] <Laney> *can* I actually push to lp:ubuntu/lucid/foo? Is that an alias for proposed?
[11:37] <Laney> looks right, good find
[11:39] <wgrant> No, that's the release pocket.
[11:39] <wgrant> It is read-only.
[11:41] <Laney> Could/should something be done with merge proposals like that?
[12:06]  * henninge lunches
[13:13] <paultag> Hey LPers. Can I I use lplib to pull data from the build farm for PPAs?
[13:18] <mrevell> Any soyuz guys around to answer paultag?
[13:19] <bigjools> paultag: what sort of data?
[13:20] <paultag> bigjools, basic status and cosmetics. Nothing major. I do PPA builds once in a while and as a fun little app-let I wanted to make something to track the builds. "Time" left, arches, and after they are done, a build log
[13:20] <bigjools> paultag: yes, you can do all that then.
[13:20] <paultag> bigjools, any documentation you can point me to?
[13:20] <bigjools> the best place to start is https://help.launchpad.net/API
[13:21] <paultag> bigjools, I'm quite familiar with lplib overall
[13:21] <paultag> bigjools, do you have the sub-page related to the buildfarm?
[13:21] <bigjools> ok, have you looked at http://edge.launchpad.net/+apidoc
[13:21] <bigjools> the "buildfarm" doesn't have an API as such, you need to traverse from the context archive you're interested in
[13:21] <paultag> yeah bigjools, but this is all for the raw interface. I hate guessing the interface for lplib
[13:21] <paultag> Humm
[13:22] <bigjools> that doc is the best thing to use, it's not too hard to go from there to lplib
[13:22] <bigjools> I'll give you an example to start with
[13:22] <paultag> bigjools, that'll help a ton, thanks
[13:23] <bigjools> you know how get get an archive?
[13:24] <bigjools> (aka a PPA)
[13:24] <paultag> bigjools, I've never tried, but it must be under the person object, yeah?
[13:25] <bigjools> yes, it has an archive property for the default archive, or you can call getPPAByName()
[13:25] <paultag> bigjools, cool, that should not be an issue
[13:25] <bigjools> or there's a "ppas" property for a collection of all PPAs
[13:25] <bigjools> then you can call getBuildRecords() on the archive
[13:26] <bigjools> or getPublishedSources()
[13:26] <bigjools> this is trivially easy in lplib :)
[13:26] <paultag> bigjools, I'll do my homework, thanks! :)
[13:26] <bigjools> something like launchpad.me.ppa will ewven work
[14:05] <maxb> paultag: http://paste.ubuntu.com/476928/ may give you some ideas
[14:05] <maxb> It is a script I use to promote packages from one PPA to another when they have built on all architectures
[14:06] <paultag> maxb, that rocks, thanks!
[14:06] <paultag> One of these days I'll put together an archive with all the examples I've polled for
[14:06] <maxb> I can paste you my lputil module that that paste imports you like, but that's just generic launchpadlib stuff
[14:07] <paultag> maxb, sure
[14:07] <maxb> oh, actually it does have one soyuz function at the end: http://paste.ubuntu.com/476929/
[14:08]  * paultag hugs maxb
[14:08] <paultag> thanks!
[14:25] <shadeslayer> jelmer: thanks mate ;)
[14:41] <jdub> yo gang
[14:42] <jdub> is this the most sensible place to ask about recipes?
[14:43] <henninge> jdub: I think it is, maybe somebody from them soyuz team can help you.
[14:44] <jdub> i'm getting the impression it's bleeding edge stuff, based on intriguing lack of docs ;)
[14:44] <jdub> now i know how to write one... how do i submit/commit a recipe? :-)
[14:44] <henninge> well, it is a fairly new feature, yes.
[14:46] <MTecknology> jdub: Are you in ~launchpad-dev? I think you need to be to use it decently
[14:46] <jdub> *ah*
[14:46] <MTecknology> https://launchpad.net/~launchpad-dev
[14:46] <jdub> that would explain the lack of things to push and prod!
[14:47] <MTecknology> I'm pretty sure that's the one you need to be in - then you'll be using launchpad edge - which means you get the latest and greatest
[14:47] <jdub> yeha
[14:48] <henninge> MTecknology, jdub: We just rolled out today so edge is currently identical to production.
[14:48] <jdub> oh
[14:49] <jdub> hmm
[14:49] <jdub> where should i expect to see a link to ~TEAM/+recipes ?
[14:50] <noodles775> jdub: if you push a branch and look at it, you'll should see a link for creating a recipe.
[14:50]  * noodles775 checks
[14:50] <jdub> and where/how do i edit/submit/commit a recipe?
[14:50] <henninge> MTecknology: and the team is ~launchpad-beta-testers but anybody can simply add "edge" to the url and use it.
[14:50] <MTecknology> henninge: oh.. so that's the one.. thanks
[14:51] <MTecknology> I was just thinking, I don't see kiko around much
[14:51] <henninge> MTecknology: He is not on Launchpad any more.
[14:51] <henninge> I mean, on the team.
[14:51] <MTecknology> henninge: oh
[14:51] <jdub> <- not logged in to edge. ha ha. grr.
[14:52] <henninge> MTecknology: http://www.linaro.org/management-team/
[14:53] <MTecknology> henninge: oh
[15:22] <sjamaan> jelmer: Hi, thanks for restarting the import of Chicken. However, this project moved to a new server. I put a link to the new repo in the Whiteboard at https://code.launchpad.net/~chicken/chicken/git-mirror
[15:23] <nessita> hello people! does anyone know why launchpad says that "pycasa-download@googlegroups.com  isn't a valid email address."?
[15:23] <henninge> nessita: where are you trying to use it?
[15:24] <sjamaan> nessita: Is that a trailing space?
[15:24] <henninge> sjamaan: good point ;)
[15:24] <nessita> sjamaan: d'oh!
[15:24] <nessita> sjamaan: feel free to insult me :-)
[15:25] <sjamaan> nessita: Actually, the code should probably handle that sort of thing gracefully by trimming the input
[15:25] <nessita> sjamaan: yeah, makes sense
[15:25] <henninge> nessita: what sjamaan said. Can you file a bug, please=
[15:25] <henninge> ?
[15:25] <nessita> henninge: yes of course!
[15:25] <henninge> sjamaan: or maybe check if one exists for it already ... ;-)
[15:26] <jelmer> sjamaan: I'll update it, thanks.
[15:27] <sjamaan> thanks :)
[15:29] <nessita> sjamaan, henninge: https://bugs.launchpad.net/launchpad/+bug/616834
[15:29] <henninge> nessita: thank you
[15:29] <sjamaan> :)
[15:30] <nessita> since we're at it, could anyone help me with the following: I've submitted a package as per https://launchpad.net/ubuntu/+source/ubuntu-sso-client/0.99-0ubuntu1, and the page reports "Uploaded by: pycassos". Pycassos is a team I belong to but has nothing to do with the ubuntu-sso-client project
[15:31] <nessita> I've noticed I've used natalia.bidart@gmail.com for building the package, and I have nataliabidart@gmail.com registered on LP. Maybe that generates the confusion?
[15:32] <henninge> nessita: you should be more careful with email addresses.
[15:32] <nessita> henninge: I see that now :-) How can I fix this?
[15:33] <nessita> I've tried adding natalia.bidart@gmail.com to my profile but I get this error:
[15:33] <henninge> Launchpad bug reports and also the channel logs here on freende are public, so they can easily be harvested by spammers ... ;-)
[15:33] <henninge> nessita: what I mean! :-/ Stop putting all your email addresses in public places!
[15:34] <nessita> henninge: well, I put this email address everywhere, but ok, I'll stop.
[15:34] <henninge> nessita: ;-)
[15:34] <henninge> nessita: what ever you like, I was just worried for your mailbox ... ;)
[15:34] <nessita> so, the error I've got was "The email address 'x.y@example.com' is already registered to pycassos. If you think that is a duplicated account, you can merge it into your account."
[15:35] <nessita> but I couldn't complete the merge either
[15:36] <henninge> nessita: so, do you have different lp accounts?
[15:36] <nessita> henninge: not that I know of, but I might mistakenly registered some while testing the new SSO GTK interface
[15:37] <nessita> henninge: I can try retrieving passwords
[15:37] <sjamaan> jelmer: Yet another error cropped up. Any idea if this is another bug or just a config issue?  http://launchpadlibrarian.net/53560977/chicken-chicken-git-mirror.log
[15:37] <nessita> henninge: is LP using the Ubuntu SSO accounts?
[15:37] <henninge> nessita: yes
[15:38] <henninge> nessita: Launchpad creates inactive accounts when it encounters an email address that it has no account for, like when importing translations.
[15:39] <henninge> nessita: so there may be an account for an address of yours which you did not create yourself.
[15:39] <nessita> henninge: ok, I just confirmed that there is an account for the x.y email
[15:39] <jelmer> sjamaan: It's a bug that has already been fixed upstream; I'll ask thumper if we can roll it out soon, as it appears to be affecting quite a few of the http git repos.
[15:40] <sjamaan> jelmer: A different bug, in a different component?
[15:41] <henninge> nessita: interestingly, searching for the x.y email address brings up the pycassos team ...
[15:41] <nessita> henninge: I might added that x.y email to that team, I use those emails a lot, like they were the same
[15:41] <nessita> xy@... and x.y@...
[15:41] <henninge> yes
[15:42] <jelmer> sjamaan: Different bug, same component.
[15:42] <nessita> henninge: so, I should change the email in pycassos and close the x.y account?
[15:42] <henninge> nessita: which is the x.y account?
[15:42] <jelmer> sjamaan: HTTP Git repositories are relatively rare, and this appears to be an issue with the way in which some HTTP servers deal with directories.
[15:43] <sjamaan> jelmer: Is it possible to get a notification when this bugfix is rolled out on production?
[15:43] <nessita> henninge: the x.y account is a SSO account, and I might registered that email (x.y) with pycassos
[15:44] <henninge> hm, I think there is some LP - SSO entanglement going on here. Looks like a bug somehow, nessita.
[15:45] <jelmer> sjamaan: Yeah, I can let you know.
[15:45] <nessita> henninge: ok, I'll chase some SSO gurus :-)
[15:45] <sjamaan> jelmer: I'd appreciate that
[15:45] <nessita> henninge: thanks for your help!
[15:46] <henninge> nessita: thanks, right in time for me going off... ;-)
[15:46] <nessita> henninge: enjoy!
[15:46] <henninge> thanks :)
[15:58] <MTecknology> henninge: Can I not mark that you answerred my question?
[15:58] <henninge> MTecknology: no, then the LOSAs won't pick up on it. They will mark it answered.
[15:59] <MTecknology> henninge: I marked it answered - I just recall you used to be able to mark who solved it.
[16:07] <henninge> MTecknology: thanks for caring about my karma! ;) I re-opened the question for the reason mentioned above..
[16:07]  * henninge has to go now ;)
[16:07] <henninge> Bye!
[16:11] <plundra> How the hell do you pull the source from a launchpad-thingomajig?! Without having an account, that is. I just want to pull and follow changes, not push anything.
[16:19] <shadeslayer> how much time should i wait when copying packages from one ppa to another?
[16:19] <shadeslayer> it said delayed copy of packages :(
[16:19] <Green00000> hi
[16:19] <shadeslayer> Green00000: hi :)
[16:21] <Green00000> there is no more ubuntu-shipping support ........ and i used launchpad only for this ....... how can i delet my account?????????
[16:23] <bigjools> shadeslayer: it does that when you copy between private / non-private
[16:24] <bigjools> it'll take up to 15 mins
[16:24] <shadeslayer> bigjools: ah thanks :D
[16:25] <shadeslayer> and yeah was copying b/w private and non-private :)
[16:27] <Green00000> there is no more ubuntu-shipping support ........ and i used launchpad only for this ....... how can i delet my account?????????
[16:30] <Green00000> there is no more ubuntu-shipping support ........ and i used launchpad only for this ....... how can i delete my account?????????
[16:31] <MTecknology> !repeat > Green00000
[16:35] <MTecknology> Green00000: in your account page, click change details, read the page
[16:36] <Green00000> okay.
[16:37] <Green00000> okay.
[16:37] <Green00000> thx.
[16:37] <Green00000> :)
[16:42] <Green00000> bb.
[16:50] <MTecknology> Any ideas what broke on this recipe build? http://launchpadlibrarian.net/53564608/buildlog.txt.gz
[16:58] <bigjools> MTecknology: it tells you in the log file
[16:59] <MTecknology> bigjools: dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found
[17:05] <MTecknology> bigjools: dpkg: dependency problems prevent configuration of pbuilder-satisfydepends-dummy: Is this part relevant?
[17:07] <MTecknology> bigjools: What am I missing? :(
[17:08] <bigjools> MTecknology: not sure, sorry, I'm not too familiar with recipes yet
[17:08] <bigjools> james_w might know
[17:09] <MTecknology> alrighty :)
[17:09] <MTecknology> We're kind of lost
[17:09] <MTecknology> Lucid: http://launchpadlibrarian.net/53564967/buildlog.txt.gz & Maverick: http://launchpadlibrarian.net/53564608/buildlog.txt.gz
[17:09] <jdub> is maverick currently having problems with recipe builds?
[17:09]  * shadeslayer looks
[17:09] <shadeslayer> not for Qt
[17:09] <jdub> it's not the partial depends bit
[17:09] <jdub> it's the failure of dpkg-source
[17:09] <shadeslayer> i just built qt-kde in a ppa with recipe
[17:10] <jdub> it doesn't successfully build a source package
[17:10] <shadeslayer> dude... dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found
[17:10] <shadeslayer> you need the orignal code in lp as well :P
[17:10] <jdub> yes, the same happens in the successful lucid build
[17:10] <jdub> because recipes don't build with orig tarballs
[17:11] <jdub> the recipe builder creates native source
[17:11] <shadeslayer> lemme look
[17:12] <jdub> thus my question above -> perhaps there is a problem with dpkg-source in maverick (or somehow we're tweaking a recipe builder bug)
[17:12] <MTecknology> Both logs are basically the same until dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found
[17:13] <shadeslayer> im taking a look at the package i built
[17:14] <shadeslayer> http://launchpadlibrarian.net/53561315/buildlog_ubuntu-maverick-amd64.project-neon-qt_1.0%2B1200~maverick1_FULLYBUILT.txt.gz
[17:14] <shadeslayer> MTecknology: how did you trigger the build?
[17:14] <MTecknology> shadeslayer: asking the recipe to build
[17:14] <shadeslayer> web ui?
[17:14] <dendrobates> I need to make some changes to a launchpad team and cannot figure out where to do it...
[17:15] <MTecknology> ya
[17:15] <dendrobates> ~openstack grants membership in ~nova and ~swift
[17:15] <dendrobates> I want to reverse it and have membership in ~nova and ~swift give you membership in ~openstack
[17:16] <dendrobates> any hints?
[17:16] <shadeslayer> aha!
[17:16] <shadeslayer> MTecknology: dpkg-source: warning: source directory 'recipe-0.8.49+time' is not <sourcepackage>-<upstreamversion> 'nginx-0.8.49+time~lucid1'
[17:16] <shadeslayer> use something else than time
[17:16] <MTecknology> shadeslayer: that same string worked in lucid thoguh
[17:16] <MTecknology> shadeslayer: I did change it though
[17:16] <shadeslayer> uh no...
[17:17] <shadeslayer> MTecknology: lucid ftbfs you pointed to http://launchpadlibrarian.net/53564967/buildlog.txt.gz
[17:17] <MTecknology> shadeslayer: https://code.edge.launchpad.net/~nginx/+recipe/nginx-development
[17:17] <shadeslayer> dude ...
[17:17] <shadeslayer> thats not the actual build
[17:17] <jdub> shadeslayer: that's not a ftbfs, that's a successful recipe build
[17:18] <shadeslayer> thats just the upload
[17:18] <shadeslayer> jdub: yep
[17:18] <MTecknology> shadeslayer: but the build log is there
[17:18] <jdub> the problem with the maverick one is that it's an unsuccessful *recipe* build
[17:18] <shadeslayer> ah right
[17:18] <jdub> lucid recipe completed, uploaded and built
[17:18] <dendrobates> nm, figured it out
[17:19] <MTecknology> granted the package itself actually fails to build..
[17:19] <MTecknology> but that's an issue that comes after the recipe builds
[17:19] <shadeslayer> MTecknology: i thought it was a FTBFS issue ... didnt realise its a recipe issue :P
[17:20] <MTecknology> shadeslayer: np - I'm wondering if there's any chance of a bug with building recipes for maverick or if it's just me
[17:21] <shadeslayer> no idea on that..
[17:23] <jelmer> shadeslayer: You're welcome.
[17:23] <jelmer> shadeslayer: the imports of the KDE repository are still slow, but at least they're working.
[17:23] <shadeslayer> yeah :)
[17:23] <jelmer> shadeslayer: https://code.edge.launchpad.net/~vcs-imports/kdelibs/kde4
[17:23] <shadeslayer> jelmer: that is already bookmarked :P
[17:23] <shadeslayer> i keep checking after every half an hour
[17:24] <jelmer> hehe
[17:24] <shadeslayer> jelmer: so bzr finds a particular set of revisions, imports them and then continues from there again?
[17:24] <jelmer> shadeslayer: you're unlucky the current run wasn't scheduled on pear, it's much faster than the other import machines.
[17:24] <jelmer> shadeslayer: yeah
[17:25] <shadeslayer> ah ok ... because i see loads of Imports ... so was curious
[17:25] <shadeslayer> bah.. :P
[17:25] <jelmer> shadeslayer: the import size is currently set to 1k revisions, but this number can probably be increased.
[17:26] <jelmer> shadeslayer: we don't import all revisions at the same time because that would prevent all other imports from running. This way we do 1k revisions and then schedule a new job for the next 1000.
[17:26] <jelmer> shadeslayer: (originally it also had to do with memory leaks, but they're mostly gone now)
[17:26] <shadeslayer> sound logic :)
[17:27] <shadeslayer> how come pear is faster? :)
[17:27] <shadeslayer> different connections? or configs?
[17:27] <jelmer> shadeslayer: better hardware
[17:28] <shadeslayer> jelmer: btw how much of code is mirrored @ LP ?
[17:28]  * shadeslayer thinks of LP as beast 
[17:28] <jelmer> https://code.launchpad.net/ has some stats
[17:29] <shadeslayer> doesnt say how much space it takes up :P
[17:32] <jelmer> oh, I don't know how much that is
[17:32] <jelmer> The Launchpad code folks would know.
[17:46] <dendrobates> is it possible to have nested project groups?
[17:47] <jelmer> dendrobates: As far as I know, we don't support nesting project groups.
[17:47] <dendrobates> I would like to have the openstack project contain an openstack-client project group that already contains 4 projects
[17:47] <dendrobates> ah
[17:48] <dendrobates> do you have a suggestion for large projects that contain many subcomponents developed separately
[18:07] <bdrung> can someone move https://code.launchpad.net/~vcs-imports/vlc/master to the ~videolan team?
[18:08] <bdrung> and this https://code.launchpad.net/~vcs-imports/vlc/old-trunk too?
[18:11] <rockstar> dendrobates, unfortunately, no.  It's pretty flat as it is now.  :(
[18:18] <shadeslayer> hi, https://edge.launchpad.net/~kubuntu-ppa/+archive/beta shows one package
[18:18] <shadeslayer> but https://edge.launchpad.net/~kubuntu-ppa/+archive/beta/+packages shows so many
[18:18] <shadeslayer> phooey
[18:18] <shadeslayer> nvm
[18:19] <jelmer> bdrung: You do realize that both branches have been suspended?
[18:21] <bdrung> jelmer: yes. the next thing i want to ask is a retry for https://code.launchpad.net/~vcs-imports/vlc/master - i want to build a daily PPA based on that import
[18:23] <jelmer> bdrung: That's still going to fail as Bazaar does not support nested trees yet.
[18:23] <jelmer> bdrung: To change their ownership, please file a question in https://answers.launchpad.net/launchpad-code
[18:23] <bdrung> jelmer: not good.
[18:26] <bdrung> jelmer: question filed
[18:26] <bdrung> jelmer: when will Bazaar support nested trees?
[18:28] <Meths> Can't you use a recipe to simulate the nested tree thing?
[18:28] <james_w> MTecknology: bug 614768
[18:28] <jelmer> bdrung: I don't know what the current plans are, the Bazaar list is probably the best place for that question (bazaar@lists.ubuntu.com)
[18:28] <Meths> Need to find the page I saw the instructions on now...
[18:30] <Meths> Use merge  https://help.launchpad.net/Packaging/SourceBuilds/Recipes
[18:32] <jelmer> Meths: You can use recipes to work around the lack of nested tree support in your own branches, but that won't make it possible for git imports with submodules to work.
[18:33] <maxb> bdrung: Are you asking just for the sake of organizational naming? Because I don't think the team of a vcs import branch matters much, permission wise, other than who can delete it
[18:33] <Meths> jelmer: noted.
[18:46] <bdrung> maxb: permission wise
[19:05] <MTecknology> james_w: thanks
[20:22] <daveisadork> hey, i have a package recipe that builds fine for karmic and lucid but fails for maverick...
[20:23] <daveisadork> the difference in the logs being at the point after all the packages are installed
[20:23] <daveisadork> a successful build says "All changes applied successfully. Committing to: ..."
[20:24] <daveisadork> the failed build says "All changes applied successfully. bzr: ERROR: Unable to determine your name."
[21:26] <thumper> daveisadork: thanks, it is a bug
[21:39] <daveisadork> thumper: should i report it or attach the recipe/logs somewhere?
[21:39] <thumper> daveisadork: I'm talking through the bug with rockstar right now
[21:39] <thumper> daveisadork: file a bug though
[21:39] <daveisadork> ok, thanks
[21:39] <thumper> daveisadork: if you like
[21:39] <rockstar> daveisadork, do you have a buildlog?
[21:39] <daveisadork> yes
[21:40] <daveisadork> http://launchpadlibrarian.net/53568457/buildlog.txt.gz
[23:02] <rockstar> daveisadork, did you end up filing a bug?
[23:04] <bdrung> does the daily build already work (e.g. https://code.edge.launchpad.net/~audacity-team/+recipe/daily)?
[23:05] <wgrant> bdrung: Daily builds are currently disabled, after a bug was discovered last week.
[23:05] <wgrant> But that bug is fixed, so they should be turned back on soon.
[23:06] <bdrung> great.
[23:06] <bdrung> so one of > 3 daily builds work.
[23:08] <wgrant> Where are the failures?
[23:12] <bdrung> wgrant: bzr import fails. e.g. vlc and xmms2 - missing nested support
[23:12] <wgrant> Ah.
[23:12] <bdrung> wgrant: and the cvs import of eclipse failed - failed to import root
[23:16] <bdrung> wgrant: and the hg import of audacious failed - maximum recursion depth exceeded
[23:17] <bdrung> summa summarum 1 of 5 daily builds work
[23:32] <wgrant> lamont: Is king really a virt buildd now? I thought it was the amd64 LiveCD machine.
[23:49] <daveisadork> rockstar: not yet, i had to run out for a bit but i can now
[23:52] <daveisadork> ummm what should i file against?
[23:52] <thumper> daveisadork: we've done one already
[23:52] <daveisadork> ok, got a link?
[23:53] <thumper> bug 617072
[23:53] <daveisadork> thanks
[23:56] <rockstar> Coincidentally, the patch has already landed.
[23:59] <daveisadork> ha i just saw that *after* i commented