[02:04] <lifeless> OOPS-2175060c461b7eb75e41de249e4108e9
[02:04] <lifeless> bigjools: ^
[03:06] <james_w> is there anything I can do with an upload stuck with 1k to go?
[03:06] <james_w> (ppa)
[03:06] <james_w> I'd really like to avoid uploading this again
[03:07] <wgrant> james_w: No. FTP or SFTP?
[03:08] <james_w> wgrant, ftp it looks like
[03:08] <wgrant> Ah, good
[03:09] <james_w> wgrant, so I should just kill it and re-upload?
[03:09] <wgrant> Yeah, probably
[03:09] <wgrant> And use SFTP
[03:10] <wgrant> Because it's not FTP
[03:10] <james_w> there's no way we could like fish it out and rsync the rest and then push it back in?
[03:10] <wgrant> Not worth it unless it's psychonauts-sized.
[03:10] <james_w> though it looks like we have a new version to push, so it's probably not worth saving after all
[03:10] <james_w> psychonauts/8
[03:11] <james_w> but I'd like to go to bed rather than babysitting an upload :-)
[03:11] <wgrant> But you're not in australia, so that shouldn't be a problem :)
[03:11] <SamB_MacG5> what the ?
[03:11] <SamB_MacG5> pyschonauts *8*?
[03:11] <wgrant> SamB_MacG5: divided by 8
[03:12] <james_w> thanks wgrant
[03:13] <SamB_MacG5> why do you people even know the size of psychonauts in the first place?
[03:19] <wgrant> SamB_MacG5: It's substantially larger than any other Debian package we've dealt with, and required a bit of hackery to get it through.
[03:19] <wgrant> So it's a little infamous.
[03:20]  * SamB_MacG5 thought it was a PS2 game ...
[03:21] <wgrant> It was released for Windows years ago, and Linux (and Ubuntu Software Centre) as part of the Humble Indie Bundle in May
[03:22]  * SamB_MacG5 doubts he would have anything beefy enough to run it on
[03:23] <SamB_MacG5> (besides the PS2)
[04:48] <james_w> wgrant, there's no progress information with sftp?
[04:55] <wgrant> james_w: I don't think bzrlib exposes it to dput
[04:55] <james_w> wgrant, ok
[04:56] <lifeless> well
[04:56] <lifeless> the dput glue doesn't hook in right
[04:56] <james_w> data seems to be flowing
[04:56] <wgrant> I'd always heard bzrlib didn't easily expose it
[04:56] <james_w> so I'll go to bed and hope
[04:56] <lifeless> lies
[04:56] <wgrant> But that was probably 3rd-hand
[04:56] <lifeless> and if not lies, fixable, if they filed a bug or whatever.
[08:03] <nunnsby> Hi all, Q: I would like to see something implemented in TurnkeyLinux. They say make your suggestions at the Lunchpad site. What do I need to do on the site to do this?
[08:04] <nunnsby> *launchpad
[08:04] <nunnsby> lol
[08:05] <nunnsby> and um secondly ... how do I get to sign in with my open id?
[08:05] <nunnsby> I'm not quite understanding that bit
[08:06] <nunnsby> I have one through both google and my own, yet maybe I'm missing something wrt to how to sign in using it?
[08:06] <tsimpson> a search give me https://bugs.launchpad.net/turnkeylinux
[08:06] <tsimpson> you must register with Launchpad before you can log in, then your Launchpad account will be an OpenID account too
[08:06] <tsimpson> but Launchpad itself doesn't support external OpenID providers
[08:09] <nunnsby> tsimpson: ahhh, okay, so now that I have a launchpad login I can use it for openid?
[08:09] <nunnsby> tsimpson, cheers mate, got it. tx
[08:09] <tsimpson> yes
[09:42] <roravun> Is it feasible to use launchpad with code hosted on external server? I know there is an import feature. But can I setup repo on launchpad to serve as mirror of the external repository (and the external repository is not bazaar)
[09:42] <roravun> L
[09:42] <roravun> *?
[10:07] <vivekimsit> Hi folks! I have to merge my changes to this branch: http://bazaar.launchpad.net/~c2c/c2c-rd-addons/trunk/files/head:/sale_order_reopen/ , please tell me how to proceed?
[10:16] <czajkowski> mgz: any advice?
[10:19] <vivekimsit> Hmm, I think no one is free today :)
[10:19]  * mgz has a quick look
[10:20] <mgz> vivekimsit: so, have you got changes in a branch already?
[10:21] <mgz> if not, you want to do `bzr branch lp:~c2c/c2c-rd-addons/trunk c2c` to get a local copy
[10:21] <mgz> make you changes there
[10:22] <mgz> then push to lp:~YOURLPNAME/c2c-rd-addons/NAMEFORBRANCH (replace the caps)
[10:22] <czajkowski> mgz: thanks
[10:23] <mgz> then if you go to https://code.launchpad.net/~YOURLPNAME you should see that new branch, and can navigate to its page
[10:23] <mgz> that has a "propose for merging" link, which you can use to create a merge proposal against the branch you created it from
[10:25] <mgz> vivekimsit: see https://help.launchpad.net/Code and https://help.launchpad.net/Code/Review for more detail
[10:26] <vivekimsit> mgz: Ya! my changes are ready are tested just need to propose my changes in the target branch!
[10:28] <vivekimsit> mgz: Ok! I don't need graphical interface in this case? just push to lp:~YOURLPNAME/c2c-rd-addons/NAMEFORBRANCH (replace the caps) will do the work?
[10:30] <mgz> that will upload the code, then you can use the webpage to give details for the reviewers when you propose the merge
[10:30] <mgz> (there's also a commandline interface to that, but you probably want to see the web page version to start with)
[10:31] <vivekimsit> mgz: here "NAMEFORBRANCH" can be any name?
[10:31] <mgz> yup, so, what I tend to do,
[10:32] <vivekimsit> mgz: And proposing merge will be from the web frontend only, thanks!
[10:32] <mgz> is try and pick a short name that describes what the branch does, and append the bug number if there is one
[10:33] <tsimpson> seems all the links from /Code/Review to the bazaar documentation are all broken :(
[10:33] <mgz> tsimpson: joy. well, it's a wiki at least so fixable
[10:33] <czajkowski> tsimpson: maybe the folks in #bzr might help there with the documentation
[10:34] <mgz> it's the launchpad wiki czajkowski :)
[10:34] <tsimpson> mgz: can "anyone" edit it, or just special LP people?
[10:35] <tsimpson> because I got a nice "Internal Server Error" page when I tried to log in
[10:35] <czajkowski> mgz: well true but bzr folks tend to know more :)
[10:35] <mgz> I'm... waiting on login currently
[10:35] <czajkowski> mgz: which page let me see
[10:35] <tsimpson> czajkowski: it's just the links from the wiki to the doc, they all seem to point to index.html#some-ref rather than the actual pages
[10:36] <czajkowski> which page in the wiki ..
[10:36] <tsimpson> czajkowski: https://help.launchpad.net/Code/Review
[10:36] <mgz> czajkowski: can you log in to the help.launchpad.net wiki? it's... just spinning for me, and tsimpson got a 500
[10:37] <czajkowski> yup
[10:37] <czajkowski> I can log in
[10:37] <czajkowski> so if you tell me what needs changing will make the change now
[10:38] <mgz> /Code/Review has some dead links to bazaar-vcs.org
[10:39] <mgz> they get forwarded to the new domain, but don't have the split into multiple pages
[10:39] <mgz> eg, index.html#merging-changes -> merging_changes.html
[10:39] <czajkowski> http://doc.bazaar.canonical.com/bzr.dev/en/user-guide/index.html#merging-changes
[10:39] <czajkowski> is what the first one changes to
[10:40] <czajkowski> do you want me to make that change
[10:40] <mgz> ...and now login works
[10:40] <tsimpson> and for me to...
[10:42] <czajkowski> mgz: you making the changes or shall I
[10:42] <mgz> I just hit submit, then realised you had the lock
[10:43] <czajkowski> ok let me log out
[10:43] <mgz> okay, that's done. sorry for the confusion :)
[10:43] <czajkowski> logged out
[11:27] <vivekimsit> how to remove a branch?
[11:28] <mgz> vivekimsit: be more specific? from launchpad or from your machine, and for what reason?
[11:28] <vivekimsit> Ok! I got it!
[11:28] <vivekimsit> from launchpad
[11:28] <vivekimsit> I saw there is an option
[11:28] <vivekimsit> thanks
[11:29] <mgz> generally you only use delete branch on launchpad if you uploaded something by mistake
[11:30] <mgz> you can just leave old branches around, once they've been merged or marked as abandonded they drop from the default view
[16:39] <zyga> hey
[16:40] <zyga> I'm trying to use launchpadlib to look at questions
[16:40] <zyga> the production launchpad claims there are 5 (five) questions
[16:40] <zyga> the first question is the distribution object for ubuntu (at index 0)
[16:40] <zyga> the second question is the project called 'sikuli'
[16:41] <zyga> am I doing something wrong or is LP just wrong here?
[16:46] <james_w> zyga, which API call are you using?
[16:51] <zyga> james_w, I've sent an email to canonical-tech about it (there's a code sample there)
[18:55] <Munchor> Hi there
[18:55] <Munchor> https://launchpad.net/elementary/+milestone/luna-beta1 Any reason why that page is timing out for lots of users but other LP pages aren't?
[19:01] <xnox> Munchor: because page timeout depends on db cache and how bug it is.
[19:02] <xnox> Munchor: e.g. you can't load anything about linux package, due to sheer size of bugs / links /etc.
[19:02] <xnox> Munchor: try refreshing, many times... should be fine =)
[19:02] <Munchor> xnox, sooo we have too many bugs?
[19:03] <xnox> milestoned... probably
[19:04] <xnox> Munchor: if you go to bugs and search for bugs for that milestone does it work?
[19:04] <xnox> (or blueprints)
[19:05] <xnox> Munchor: well if you go to individual sub project it does work.
[19:08] <Munchor> yeah xnox
[19:09] <xnox> Munchor: hmm... ubuntu is different because it's a distro with packages, not a meta-projects with sub-projects.
[19:09] <Munchor> xnox, that's a good idea
[19:10] <Munchor> Perhaps we need to contact Launchpad staff to make elementary a distro
[19:10] <czajkowski> no they're limited to ubuntu and a few others.  for distro
[19:11] <Munchor> czajkowski, then after elementary OS Luna is released we'll contact them, maybe we get enough users to convince them
[19:13] <xnox> czajkowski: why? there is fedora as a distro on launchpad. they are not asking for soyuz, just bugs and specs.
[19:13] <xnox> e.g. they will have to continue manage branches in the projects.
[19:13] <czajkowski> xnox: Fedora is there as a holding page and has details back to fedora page they dont use the bug tracker here.
[19:14] <dobey> it is possible to have a distribution added to launchpad.
[19:14] <dobey> it is just generally not the best/appropriate thing to do
[19:15] <czajkowski> dobey: exactly
[19:15] <dobey> for distributions based on ubuntu, it probably makes some sense
[19:16] <dobey> but i don't think it will solve the specific issues that Munchor is inquiring about, either
[19:16] <dobey> lots of bugs are lots of bugs, and a timeout will happen regardless of whether they're filed against a distro, or a project
[19:16] <Munchor> Yeah dobey, that's what I thought, but if xnox said it
[19:17] <czajkowski> no I think it's the searching by milestone having the issue
[19:17] <czajkowski> jcsackett: ping
[19:45] <jcsackett> czajkowski: pong.
[19:45] <czajkowski> jcsackett: any idea why Munchor url is timing out, https://launchpad.net/elementary/+milestone/luna-beta1
[19:47] <jcsackett> czajkowski: looking now.
[19:58] <jcsackett> czajkowski: not sure; there's a longish sql statement involving specifications, which could be responsible.
[19:59] <czajkowski> jcsackett: nods wondering is it the +milestones messing it up
[19:59] <jcsackett> czajkowski: not sure what you mean.
[20:00] <czajkowski> searching for things /+milestones seems to give me issues at times
[20:01] <jcsackett> czajkowski: ah, yeah. we have a couple of milestone related timeout bugs, i think. this is ProjectMilestone, which is a bit different.
[20:01] <czajkowski> ah I see
[20:01] <jcsackett> but it shares that it can load a lot of data--related bugs and specs.
[20:02] <jcsackett> as i don't see a timeout bug reported for projectmilestone, i'll go ahead and report one, and bring it to the rest of the squad's attention at our meeting in a few hours.
[20:02] <czajkowski> jcsackett: thank you :)
[20:02] <czajkowski> Munchor: see ^^^
[20:13] <czajkowski> Munchor: https://bugs.launchpad.net/bugs/1053083
[20:31] <Munchor> sorry I was having dinner
[20:32] <Munchor> Thank you all for your help
[20:32] <Munchor> We'll be patient for a fix :)
[21:18] <zyga> hey everyone, I'm poking launchpad via launchpadlib and I got a 500
[21:18] <zyga> I'm trying to iterate all the merge requests on launchpad
[21:18] <zyga> (on the project itself)
[21:18] <zyga> could that be caused by not using chunking to iterate the collection?
[21:18] <zyga> (and hence the request gets killed)
[21:18] <zyga> is there any chunking API?
[21:21] <dobey> sounds like a situation that would cause a timeout, indeed
[21:21] <zyga> is there a way to chunk the request somehow?
[21:21] <zyga> I can make a reproducible 3 liner that crashes lp
[21:21] <zyga> login anonymously, iter merge proposals  on 'launchpad'
[21:22] <dobey> do you really want all merge proposals ever?
[21:23] <zyga> I want to iterate yeah
[21:23] <zyga> as the filtering is insufficient
[21:24] <zyga> I want all things without a commit message and not landed (and not in progress)
[21:24] <zyga> and all things older than X days
[21:24] <zyga> so likely yes, correct me if I'm wrong, I need to iterate
[21:24] <zyga> actually ignoring landed MPs could be an easy workaround if that's doabl4
[21:24] <zyga> e
[21:25] <zyga> getMergeProposals(status=...) ?
[21:25] <dobey> i think branch.landing_candidates already ignores merged/rejected proposals, and gives you active ones
[21:25] <zyga> what's the possible value of status there?
[21:25] <dobey> are you using that, or are you using the project?
[21:25] <zyga> on the project, I use getMergeProposals()
[21:26] <dobey> do you care about merges that aren't into the lp:launchpad branch though?
[21:26] <zyga> hmm, I don't want to hardcode any project logic, I guess it's fine to ignore things that don't land on the non-main series but I'm not sure how to express that on LP api
[21:27] <zyga> (project logic as in logic for a particular project, eg. launchpad)
[21:28] <dobey> project.development_focus.branch will give you the development focus branch for a target, and branch.landing_candidates should give you a filtered list from there
[21:28] <zyga> trying
[21:28] <dobey> if you do getMergeProposals() on the project itself, you're going to get all merge proposals ever for that project, even random people merging into random other branches
[21:29] <zyga> right
[21:29] <zyga> for some projects that may be appropriate
[21:29] <zyga> how can I filter using status argument on that operation?
[21:29] <zyga> status='not merged' ?
[21:30] <zyga> dobey, I still get 500 your proposal
[21:30] <dobey> no, status is a list of strings; the same strings you see in the lp ui
[21:30] <dobey> so status=['Approved', 'Needs Review'] for example
[21:31] <zyga> ok
[21:31] <dobey> however, if there are a lot of branches with that status, you'll still likely see a timeout :-/
[21:31] <zyga> http://paste.ubuntu.com/1215706/ <- my code, crash log -> http://paste.ubuntu.com/1215705/
[21:32] <zyga> so
[21:32] <zyga> no iter/chunk api and forced timeout == no api for collections
[21:33] <dobey> oh, you aren't hitting a timeout
[21:33] <zyga> oh?
[21:33] <dobey> you're hitting a bug in launchpad apparently
[21:33] <zyga> (brb, coffee)
[21:33] <zyga> I thought timeouts kill the request and give you 500s
[21:34] <dobey> zyga: so can bugs
[21:35] <dobey> zyga: search for the oops id on oops.canonical.com :)
[21:35] <zyga> trying
[21:36] <zyga> oh
[21:36] <zyga> it's a bug indeed
[21:45] <zyga> dobey, we've been looking at the backtrace with cr3 and it seems launchpad has two BranchMergeProposal rows with the same 'merge_diff' id/number
[21:45] <zyga> dobey, it's probably historical cruft of some sort
[21:48] <dobey> perhaps. :)
[21:48] <dobey> but it's a server side issue, and not something i can help you with any further. someone on the lp squad will have to fix it :)
[22:09] <tgm4883> If I mark a branch as private, do only the owners get to see the branch, or anyone that has priviledges to see private branches can see it?
[22:10] <tgm4883> I'd think the former, but the wording makes it seem the other way, which is undesired
[22:10] <tgm4883> "Only shared with users permitted to see private user information."
[22:10] <wgrant> tgm4883: The branch owner and anybody that the project owner allows
[22:10] <wgrant> On the project's Sharing page
[22:11] <tgm4883> wgrant, how would you allow it to outside of the project owner?
[22:11] <tgm4883> ah the sharing page
[22:11] <tgm4883> I don't recall seeing that before I marked this private
[22:12] <tgm4883> (doing all this in the staging area)
[22:12] <wgrant> The sharing page is new a couple of weeks ago
[22:12] <tgm4883> cool
[22:12] <wgrant> Ah, you're trying to set up a commercial project on staging?
[22:12] <tgm4883> well, I was testing it
[22:13] <tgm4883> not really a commercial project, but not really something that is meant for public
[22:13] <tgm4883> I work at a college, rather than setup a bzr server here, I'd rather just use LP
[22:14] <tgm4883> stuff that would exist on these branches is going to be pretty specific to our setup
[22:15] <wgrant> Ah. You need a commercial subscription if your code isn't public and open source, anyway. But feel free to poke around on staging.
[22:17] <tgm4883> define public and open source? I can still select the project uses GPL v3. These branches will house things like our scripts to sync out to google apps, guest wireless provisioning stuff, etc
[22:18] <tgm4883> I have no issue giving out the source to these either, I'd just rather have it private in case a password slips in there somehow (although i've setup bzr to not push the conf files)
[23:38] <mark06> hi all, is the branch status field really used for anything at alll?
[23:38] <mark06> *all
[23:40] <lifeless> it determines what branches are shown by default on project pages
[23:43] <mark06> ah, only mature in this case? can't we have it automatically changed to development if a new commit or overwrite changes branch after a mature setting?
[23:43] <lifeless> merged and abandoned are not show
[23:43] <lifeless> the rest are
[23:44] <lifeless> and yes there is some automation in there
[23:44] <lifeless> I forget what it is
[23:44] <wgrant> The only automation is that it's set to Merged when it's merged.
[23:44] <wgrant> Development/Mature can't be judged automatically
[23:44] <wgrant> a Mature branch shouldn't become Development just because I commit a bugfix
[23:45] <wgrant> It's more about the overall state of the branch. eg. my release branch is mature, because I ensure that only good stuff goes into it
[23:45] <wgrant> Trunk might be Development, because it's not always stable
[23:45] <wgrant> And I have an Experimental feature branch which is really really unstable.
[23:46] <wgrant> but as lifeless says, only Abandoned and Merged have special meanings
[23:46] <wgrant> And then it's only that they're hidden by default
[23:46] <mark06> I think it's reasonable to assume branch is not mature anymore if a new commit comes in, since the mature status need to be determined manually by a person
[23:47] <wgrant> The branch status is usually used at a higher level than that
[23:47] <mark06> it would also be nice if we could set a branch as mature directly from bazaar, as a push option
[23:47] <wgrant> It doesn't change on a commit-by-commit basis
[23:47] <wgrant> mark06: What are you trying to do?
[23:48] <wgrant> Perhaps you want to use merge proposals instead
[23:49] <mark06> nothing much, it's just that I don't know what to set on mine, if I follow field description, then I need always to remember to change between mature and development depending on whether a commit is unstable or not
[23:51] <mark06> would it be reasonable to change all to development, which is default value for new branches, and just stop caring about it?
[23:51] <wgrant> Right, those descriptions are sort of several years old and not very sensible
[23:51] <wgrant> Most feature branches are just Development
[23:52] <wgrant> Then get automatically set to Merged
[23:52] <wgrant> Release branches are probably Mature
[23:52] <mark06> ok, I will do that, thanks wgrant, lifeless
[23:52] <wgrant> I don't know of anyone who still uses the Experimental/Development/Mature statuses as they're described on the edit page
[23:52] <wgrant> They evolved
[23:55] <mark06> what does this message mean? "This branch is now a personal branch for <my name>"? I got it when renaming a +junk branch
[23:57] <wgrant> wallyworld_: ^^ Did your target change branch forget to check that the value had actually changed?
[23:57] <wallyworld_> wgrant: nope
[23:57] <wgrant> mark06: +junk branch == personal branch
[23:57] <wallyworld_> it checked, unless i made a mistake in the check
[23:58] <wgrant> wallyworld_: It's a complex boolean conditional with no parentheses
[23:58] <wgrant> So there's probably a mistake
[23:58] <wgrant> +            if (target is None and self.context.target is not None
[23:58] <wgrant> +                or target is not None and self.context.target is None
[23:58] <wgrant> +                or target != self.context.target):
[23:58] <mark06> wgrant: but branch was already a +junk/personal branch
[23:58] <wgrant> I don't even know what that means
[23:59] <wgrant> mark06: Yeah, but I think there's a bug in the check to determine whether it's actually changed
[23:59] <wgrant> That code was changed yesterday
[23:59] <wallyworld_> wgrant: brackets not needed - and takes precedence over or, brackets just make it harder to read
[23:59] <mark06> ah ok wgrant