[00:00] bigjools: the idea is to have the actual recipe part (the payload?) or both manifests and recipes stored the same way, in some SourcePackageRecipeData table [00:00] then SourcePackageRecipe (the editable thing) and SourcePackageRecipeBuild will both refer to this table [00:00] SourcePackageRecipe will have the stuff needed to locate the recipe [00:01] there will be a linking table linking SourcePackageRecipeData and Branch [00:01] ok [00:01] SourcePackageRecipeBuild will mostly be like Build i guess [00:01] I can pore over this on my flight home on Friday [00:02] and we'll add a (nullable) link from SourcePackageRelease to SourcePackageRecipeBuild [00:02] I am not working tomorrow (Thursday here) [00:02] ok [00:02] i'll send my followup mail to your gmail address too [00:03] I guess the FK makes more sense in a way if you treat it like "this package came from a recipe, here it is" [00:03] ok I am going AFK for a bit but I will check back before I go out [00:04] ok [00:04] thanks for the hints [00:05] bigjools/wgrant: what creates Builds out of curiosity? [00:05] mwhudson: An upload. [00:05] Or queue-builder, but not normally. [00:05] wgrant: so they're created at the same time as sourcepackagerelease? [00:06] mwhudson: Right. [00:06] ok [00:14] sinzui: Is there a good reason that lp.registry.interfaces.sourcepackage.SourcePackageFileType doesn't live somewhere like lp.soyuz.interfaces.files? [00:20] i guess this build from recipe plan doesn't have an analogue of sourcepackageupload really [00:20] i wonder if that's a problem [00:21] You mean a PackageUploadSource? [00:21] Or something else? [00:22] sorry [00:22] sourcepackagerelease [00:23] Ah. [00:23] That would be a manifest, I guess, but there isn't one of those yet... [00:23] yes i guess so [00:27] damn [00:27] up arrow in the terminal to get 'make run' takes longer if the last was 'make clean run' [00:27] Heh. [00:28] :-) [00:28] thumper: make schema run is worse i think [00:28] not any more [00:28] make schema runs faster for me than make clean biuld [00:29] hah [00:29] bent javascript to my will yet again! [00:30] ... [00:30] grr [00:30] not working [00:30] * thumper needs food badly [00:33] mwhudson: Are jtv and yourself the only non-Soyuz BFB people? [00:33] thumper: javascript is such a tease like that [00:33] wgrant: i guess [00:33] wgrant: jml is pretty involved too, and some work from the bzr end of course [01:02] Just out of curiosity, is there an easy way to manage launchpad branches? In the past, I've followed the guide on the wiki to get the source, made my changes, commited, and pushed. Then, once it was accepted, I reverted my changes and updated the branch. Is there a better workflow? [01:03] nhandler: you shouldn't need to revert the branch [01:03] nhandler: You should probably have a separate branch for each piece of work. [01:03] nhandler: i have a slightly extreme set up, i have repo with no trees and a directory that contains lightweight checkouts from the repo [01:03] Ah. [01:04] and make a new branch + checkout for each new bit of work [01:05] wgrant or mwhudson: How would I go about doing that? Would I just pass an additional argument to bzr commit once I make my changes? [01:05] nhandler: no [01:06] i do bzr cb trunk feature-X; cd feature-X; hack hack hack; bzr ci; bzr push [01:06] cb is an alias for "cbranch --lightweight --hardlink" [01:06] * wgrant is boring and uses 'bzr branch devel some-feature' [01:08] Ok thanks a lot [01:09] And I'm not sure if it is just backed up, but I haven't gotten an email yet bac [01:09] nhandler: it has only been 2.5 hours, hasn't it? [01:09] The test suite takes more than 3. [01:10] wgrant: I wasn't aware of that, thanks [01:10] There's a looooot of sloooow tests. [01:16] bigjools: http://pastebin.ubuntu.com/328119/ <- updated patch, if a wad of sql makes sense to you :-) [01:16] mwhudson: wgrant: bzr switch -b FTW [01:16] or branch --switch too [01:16] * mwhudson definitely wants to write some code that uses this before landing the patch tho [01:16] lifeless: i like my working trees to be named after the branch [01:16] lifeless: Handy. [01:17] lifeless: Although I'd prefer it if it shelved my uncommitted changes, like switch-pipe. [01:17] wgrant: patches reviewed. [01:17] i guess i could abuse branch --switch to something like that but the tree build time for launchpad is ok now tbh [01:25] I use lightweight checkouts too [01:26] although --hardlink isn't supported in 2a yet [01:26] lifeless: what does branch --switch do? [01:27] lifeless: can it rename the directory? [01:28] thumper: no === jelmer_ is now known as jelmer [02:42] wgrant: no reason. We have not spent much time breaking the larger classes into domains yet. Your welcome to reorganise them. [03:21] I'm thinking about fixing LP Bug #400393. It looks pretty straightforward. I personally am in favor of mpt's suggestion, but I think either would work. [03:21] Bug #400393: "Updating branch..." message reads oddly [03:31] * wgrant wonders why people want digests. [03:32] wgrant: because they want to make their email harder to read i guess [03:33] because they don't want that mail at all [03:34] i guess [03:44] * mwhudson hates at the fact that the launchpad database only accepts file://localhost/ urls but bzrlib only accepts file:/// ones for the first time in a while [03:48] mwhudson: you can fix lp if you like ;) [03:48] yeah, probably the right thing to do [03:48] where's that dba [03:49] lifeless: can i fix bzr too? [03:49] mwhudson: yes. [03:49] file:///localhost/ should be accepted already, I thought. [03:50] bah, s//////// [03:50] :) [03:53] anyway, nope, url_to_local_path still complains in trunk [04:02] man i suck at typing my gpg passphrase today [04:02] just don't type your passphrase in irc [04:03] well, judging by today's performance i wouldn't be able to [04:32] i think this traceback means i should stop work for the day: http://pastebin.ubuntu.com/328196/ [04:32] mwhudson: I would say so. [04:33] hm, probably python version fun actually [04:34] I considered that, but it looks too obscure. [04:34] yes [04:34] bzrlib was built with 2.6 [04:34] pretty obscure yes :) [05:39] why is edge still running 9928? Should it not have updated last night? [05:41] I heard whispers of a couple of security fixes that I haven't seen landing on public branches, so perhaps updates are turned off for those. [05:45] I don't see anything in the branch lists. Could have been a while ago, in a sub-component, or I'm looking at the wrong list. [06:07] mars: was a landing made by a lp-bzr dev in northern NZ; it would have broken at least one edge server, so we disabled [09:05] mwhudson, I've replied to your "first cut" thread. [09:12] Anyone know of any simple Python libraries to help write /etc/init.d type control scripts? I'm getting sick of hacking up makefiles or shell scripts. [09:12] stub: Upstart! [09:13] Hmm... user services is a planned feature [09:14] This is all in tree dev stuff [09:14] Ah. Sad. [09:14] I don't know of anything Pythony to help generate the boilerplate. [10:02] stub, you could make a quickly template, perhaps [10:02] A whatly template? [10:03] stub, 'quickly' is a python app made by didrocks and rickspencer3 that is all about making projects quickly. [10:04] basically by doing the boilerplate generation for you [10:04] maybe that's not what you want. [10:11] danilos: didn't your patch to make test_template_listing_admin_links pass land? === lionel__ is now known as lionel === matsubara-afk is now known as matsubara [12:15] Does anyone know of a clever way to "mock up an import"? [12:17] I'm trying to write a test for test the class we use to run tests on EC2 instances, but afaict it imports python modules that are available in the EC2 image but not in LP itself. [12:28] jtv, you can insert something into sys.modules, I think. [12:28] jtv, it's just a dict. [12:28] jtv, but you can probably do something nicer by splitting the code you are testing away from the code that's difficult to test. [12:30] jml: yes, I guess I'll do that [12:30] the latter [12:30] jtv, good call :) [12:31] I wonder if it'd be terribly bad of me to isolate the invocation of the function I can't import, _plus its import_, in a method that I can override for the test. [12:33] it depends. [12:33] without context, it sounds a little dodgy [12:36] jml: wait, I'll paste [12:37] jml: https://pastebin.canonical.com/25062/ [12:37] dodgy, yes, but perhaps not so compared to not testing this stuff at all and suffering regular breakage [12:38] jtv, you want to test that method? [12:38] jml: no, I want to test the class I put it in without ImportErrors [12:38] And incidentally of course I also want to mock up the call to that function it wraps. [12:39] Without this my test can't even import the class it wants to test [12:39] jtv, I'd suggest changing it so that the method you've added only gets called if a launchpad login is not provided as a parameter. [12:39] jtv, also, I can tell you how to import that [12:40] jml: I'd really hate to change the API though, just to test a fix for the current widespread breakage [12:40] jtv, from bzrlib.plugin import load_plugins; load_plugins() [12:41] jml: how will that affect the other stuff we do in ec2? [12:41] jtv, I don't know. [12:41] hmm [12:42] and it's not tested (which is what I'm trying to make a small first step away from) [12:42] how come that this URL load a answer component, while it's in the translations namespace ? https://translations.launchpad.dev/rosetta/+addquestion [12:42] jtv, what do you mean it's not tested? [12:42] jml: the class I'm trying to write a test for isn't tested [12:43] I don't know how much more of this stuff is around the corner, so frankly I just want a quick fix for now [12:43] jtv, devscripts.ec2test should be running load_plugins() on import. [12:43] jtv, running load_plugins() is the quick fix. [12:44] * jtv tries [12:44] adiroiban1, it might be registered on more than just translations layer/facet [12:45] adiroiban1, you'd need to look into lp/answers/browser/configure.zcml to see what's the case there :) [12:45] i tried to search the answer/browser/configure.zcml for "translations" .... but there was not such hint [12:45] adiroiban1, btw, I've seen your branch, I'll take a look later, but I don't understand why you've got that big wdml change in there? how did you get it? [12:46] jml: I guess I'd have to load_plugins() from the module that currently tries to import that function? [12:46] danilos: regarding the branch. I fixed it :) ... don't know how I got that [12:46] jtv, yes [12:46] jtv, is this module in the devscripts.ec2test package? [12:47] yes [12:47] adiroiban1, ok, cool [12:47] danilos: i think that file was modified by one of the debugging scripts.... but I have reverted and pushed a new revision... it should be nice and clean now [12:47] jtv, then load_plugins should already have been called by the time you import it. [12:47] adiroiban1, well, it's not registered in the translations facet, it's just not limited to the answers one :) [12:47] jtv, see devscripts/ec2test/__init__.py [12:47] jml: not much luck anyway: [12:47] from bzrlib.plugin import load_plugins [12:47] load_plugins() [12:47] login = get_lp_login() [12:48] NameError: global name 'get_lp_login' is not defined [12:48] jtv, it doesn't work like that. [12:48] https://pastebin.canonical.com/25063/ [12:49] https://pastebin.canonical.com/25064/ should also work [12:49] * jml apologises for using the secret pastebin [12:50] jml: first one doesn't... [12:50] File "/home/jtv/canonical/lp-branches/bug-488695/lib/lp/scripts/utilities/importfascist.py", line 163, in import_fascist [12:50] module = original_import(name, globals, locals, fromlist) [12:50] ImportError: No module named launchpad.account [12:52] adiroiban1, right, and about the answers, this is what would make the difference: http://paste.ubuntu.com/328447/ (though, I am sure some links would break if you just did this, which is why nobody ever bothered to fix it up for all the pages) [12:52] jtv, I'll try. [12:53] danilos: still lost in url traversals ... and a quick search on the net was not enough for finding a good tutorial [12:53] jml: btw I hope the "thank you for helping with this" is implicit, but just in case: thanks for helping with this. :-) [12:53] BjornT_, btw, the test passes on db-devel for me locally, I'll try to figure out what's going wrong [12:54] adiroiban1, I don't think there's one, we are doing a lot of custom things in LP as well (like one layer for each application/virtual host) [12:55] adiroiban1, if I were you, I wouldn't worry about it too much, because Zope is very flexible in how you do it, and we use all of those possible ways :) [12:56] danilos: i was just looking at bug 193750 , and this is the only reason I bumped into url traversal .... otherwise I try to avoid it :) [12:56] Bug #193750: remove references to +addticket [12:57] jml: I think I'll just circumvent this entire factory that's giving me trouble. [12:57] jtv, ok [12:57] jml: I'll still have to silence the import error of course [12:58] how about I move the import into the factory, so circumventing the factory also circumvents the import error? [12:59] danilos: but I learned something today about the usage of layer from configure.zcml [13:00] jtv, fwiw, get_lp_login is called on the client side [13:00] jtv, so if the 'ec2' command is working at all, it should be able to be imported [13:01] jml: any idea why I can't import it from the test? Sorry for leaning so much on you here; I'm terrified of getting stuck on this silly detail! [13:01] jtv, which means that something in the test environment is substantially different to something in the normal usage environment [13:01] jtv, I don't know what that difference is [13:02] jtv, and I would figure out that difference using normal debugging techniques. [13:03] but I'm not going to do that, because now I am going to have lunch and start doing the things that I ought to have started four hours ago. [13:03] jml: I understand... I'm almost out of time myself. [13:03] jtv, np [13:03] jtv, well, good luck. sorry I couldn't help more. [13:04] hope to have good news tomorrow... [13:10] adiroiban1, :) [13:10] BjornT_, entire TranslationsWindmillLayer passes for me [13:10] danilos: should I then look at bug 192775 ? [13:11] Bug #192775: Notification after upload refers to "1 files" [13:12] adiroiban1, sure, though 193750 is easy as well (it's about replacing addticket with addquestion, not really a big deal :) [13:13] danilos: i can replace that text, I was thinking it also requires adding a "sane" link [13:13] adiroiban1, btw, for Zope Page Templates, you might want to bookmark http://www.zope.org/Documentation/Books/ZopeBook/2_6Edition/ZPT.stx and http://www.zope.org/Documentation/Books/ZopeBook/2_6Edition/AdvZPT.stx (from ZopeBook; it's for Zope 2.x, but these chapters are very much still relevant) [13:13] to answers.lp.net ... and not to translations.lp.net/rosetta/+addquestion [13:15] adiroiban1, you can construct such a link in the view using canonical_url with rootsite='answers', but I wouldn't worry about it for now [13:15] jtv: are you working on the ec2 shutdown problem? [13:15] bac: yes [13:16] jtv: how's it going? i was looking at it a bit too [13:16] bac: the fix is easy, adding a test is hard [13:16] jtv: :( [13:18] danilos: ok. I have already changed that text in my local branch (replace all +addticket with +addquestion)... I will add that branch as a merge proposal [13:19] adiroiban1, cool, do make sure to run the full test suite, or at least all the translations tests (bin/test -vvt lp.translations) [13:20] danilos: ok [13:20] adiroiban1, also, it's useful to note in the MP how one can easily test/see what you are changing, i.e. "go to translations.launchpad.dev/evolution/+blahblah to see how the links now point to a different location" [13:21] danilos: yes... I read the MP cover letter wiki pages and I will try to use that format. [13:24] adiroiban1, cool, thanks :) [13:26] danilos: in lp parlance, "in the view" mean in the .pt files ? [13:27] adiroiban1, no, it means in the browser/*.py classes :) [13:27] adiroiban1, all those classes have names like POTemplateView or POTemplateAdminView or... [13:27] danilos: ok... then templates are just the look :) [13:27] adiroiban1, yeah [13:30] adiroiban1, in traditional sense, zope view is a bit of a controller and a bit of a view, and zope page template is the view [13:32] adiroiban1: ok. I can understand it... also "class" from configure.zcml can gives tips about view class [13:33] adiroiban1, that's right, it's all tied together in ZCML [13:34] * jml going off IRC for a bit. Back later. [13:44] BjornT_, I've seen many (16 out of 33) tests fail with something like http://paste.ubuntu.com/328473/ in the browser with full make jscheck, so I don't know what's wrong; all translations tests pass locally [13:46] danilos: that's odd. i've seen one jscheck run where a lot of tests failed, probably due to that same failure. i also can't get the translations tests to fail locally, i'm trying to run the full suite now, to see whether that makes any difference [13:58] morning launchpadders [13:58] morning flacoste [14:10] danilos: the tests pass when running the full suite as well. i'm not sure what is going on here... [14:18] BjornT_, we may want to enhance the build output so that the LP webserver's log is also available. Tracebacks will be printed in there. [14:24] mars: yeah. it would also be nice, if you could easily boot up a buildbot slave image, and run the tests interactively [14:47] Chex, rockstar, danilos, sinzui, allenap: LP production meeting in 13 min @ #launchpad-meeting === jtv1 is now known as jtv [14:49] noodles775, hi, is bigjools on holiday today? [14:49] matsubara: Well, I was aware that he wouldn't be here for the second half of the day, but it was a surprise to me that he's not here now too. [14:50] He was heading home today. [14:51] noodles775, right. we'll have the LP production meeting in 10 min. would you be able to cover for him? [14:51] matsubara: sure. [14:51] noodles775, thank you [14:51] danilos: should I add you as the review of MP for bug 193750 or should I found someone else ;) [14:51] Bug #193750: remove references to +addticket [14:51] ? [14:51] adiroiban1, you can probably get a faster review if you go to #launchpad-reviews [14:52] adiroiban1, look at the topic to see who's online [14:52] adiroiban1, and leave the default reviewer (it's entire LP team), so anyone can claim the review [14:52] ok. i'll do [14:52] adiroiban1, I'd be happy to do it, but just exposing you to more of the processes :) [14:53] danilos: yep. As I'm still learning, I'm happy to go by the book [14:54] adiroiban1, thanks :) [14:56] danilos: should I also ask for someone else to review MP for bug 487970 [14:56] ? [14:56] Bug #487970: distroseries/+templates page should display last update date for templates [14:56] adiroiban1, no, that's fine, I'd be happy to take a look at that [14:56] danilos: ok === salgado is now known as salgado-lunch [15:22] I'm thinking about fixing LP Bug #400393. It looks pretty straightforward. I personally am in favor of mpt's suggestion, but I think either would work. I'm not sure how much discussion is really involved for it [15:22] Bug #400393: "Updating branch..." message reads oddly [15:26] nhandler, does grep-find turn up the string "Launchpad is processing new changes" in the templates or the tests? [15:27] if so, then it should be an easy fix :) [15:31] mars: Yeah, a grep comes up with: code/templates/branch-index.pt: Launchpad is processing new changes to this branch and will be [15:34] nhandler, excellent, and quite easy to fix then. You just need to pick the new text. [15:34] mars: Unless there are any objections, I think I'll go with mpt's suggestion. [15:36] And I'm not sure if this is a known issue or an issue on my part, but I tried to do a 'rocketfuel-branch' yesterday, and got a few messages similar to "This Python has API version 1013, module gpgme._gpgme has version 1012." === matsubara is now known as matsubara-lunch [15:36] well, I personally find the voice that mpt uses in his text to be a bit too advanced. I'm partial to Tieflegger's suggestion - closer to the "Don't make me think" mantra. [15:37] nhandler, you need to run 'make clean'. That is Python2.4 compiled code getting in the way of the Python2.5 runtime. [15:37] My words didn't have enough syllables in them? :-) [15:38] mars: In that case, I might use a combination of the two. I like the more personal feel of "We'll have the changes here for you shortly" [15:38] * jml likes mpt's suggestion [15:38] mars: Ok, I thought doing a rocketfuel-setup would have cleaned that stuff [15:38] mpt, well, it reminded me a bit of reading Dickens - you have to hold more than seven words in your head to understand the sentence in context. High writing, but not right for the lows of the internet [15:39] mars, are we reading the same thing? [15:39] How about "Launchpad is processing new changes to this branch. We'll have them here for you shortly." ? [15:40] that's the one I liked [15:40] mars, that one isn't in the bug report [15:41] jml, mpt used a comma, which makes the voice more sophisticated, and in my opinion, a bit more difficult to read. [15:41] mars, no I didn't. [15:41] mars, No he didn't. This is the suggestion: "This branch has been changed in the past few minutes. We’ll have the changes here for you shortly." [15:41] mpt, wasn't that jml's suggestion? It's in a comment. [15:41] Here are the 2 suggestions: https://bugs.edge.launchpad.net/launchpad-code/+bug/400393/comments/1 [15:41] Bug #400393: "Updating branch..." message reads oddly [15:42] jml, I was reading "Launchpad is processing new changes to this branch, which will be available in a few minutes." [15:42] mars, that's Colin Watson [15:42] mars, that would be cjwatson's suggestion [15:43] argh, sorry mpt [15:43] I heard "mtp's bug", and missed the actual reporter :( [15:44] so, I /do/ like mpt's suggestion. nhandler, I think you should just go with whatever is right. And I think mpt is right :) [15:47] mars: Alright, that is fine by me ;) [15:50] * mars goes to file a bug titled "A bug's reporter should stand out more on the bug report" [15:52] mars, that's already reported :-) [15:52] Well, actually, there's an open bug report on highlighting comments from the reporter, which wouldn't have helped here [15:53] There's also a wontfix (iirc) report that the reporter should be more closely tied to the description, which was wontfixed on the grounds that the description can be edited by other people [15:53] (though it wasn't in this case) [15:53] I wonder, is it in any significant number of cases? [15:54] I lack the SQL skill to whip up a query for that [15:55] yes [15:55] descriptions are edited frequently [15:55] Its part of the SRU process in fact [15:55] (for Ubuntu that is) [15:55] It is also a common part of the Ubuntu bug triage process [15:56] indeed [15:57] I guess knowing the reporter is only a problem if the bug is opinionated. Ubuntu bugs are not, they are subjective shared tickets? [15:57] by opinionated, I mean it somehow makes a suggestion on a subjective topic [15:58] Ubuntu bugs are objective [15:58] I only care about who the reporter is when I have strong urges to hurt them. [15:58] which is also a subjective opinion :) [15:59] (or when I want to get in touch with the person more directly because they aren't responding to comments to the bug) [16:01] I think the original reporter does matter. It matters more as you introduce indicators as to a person's standing in the community. [16:01] So for ubuntu, it does not matter right now [16:01] noodles775, I think it does matter [16:01] but it may matter later if we add badges [16:01] err [16:01] mars, I think your point has merit [16:02] I'm sure I would have filed a bug sooner or later [16:02] as I've been annoyed several times at the few ms delay to find the reporter name [16:02] I'm thinking of what stackoverflow does, actually [16:03] they have badges to show when a developer poses a question. It helps you to understand the context, and allows you to make some assumptions. === beuno is now known as beuno-lunch === salgado-lunch is now known as salgado === jtv is now known as jtv-afk === matsubara-lunch is now known as matsubara === beuno-lunch is now known as beuno [17:58] what sort of hardware do the code imports run on, 32-bit or 64-bit? [17:58] jelmer: a mixture [18:06] mars: do you have a sec? [18:07] abentley, I have a few minutes [18:07] mars: How do I make a test pause until the contents of an element have been updated? [18:07] when doing pagetest is there a way to get a link by id ? It looks I can only get on by text or url [18:07] mars: A windmill test. [18:07] mars: The element is a textbox. [18:08] abentley, you could try waits.forElement on something in the box that you want to see [18:08] oh [18:09] abentley, for a textbox you may have to put in a hard waits.sleep() call [18:09] mars: I have: client.waits.forElement(xpath='//[contains(., "> content")]') [18:09] but not too long, as it should update quickly [18:10] abentley, interesting, and that doesn't work? Try it with the sleep() and see if the XPATH works after a long enough wait [18:16] client.waits.sleep(5) gives TypeError: __call__() takes exactly 1 argument (2 given) [18:16] ? [18:17] that is odd [18:17] mars: Does it require named parameters? [18:17] abentley, check the docs, maybe the parameters are less than obvious [18:18] the docs say waits.sleep takes a milliseconds parameter. [18:18] do any other tests call that function? [18:19] mars: I tried passing it in as a named argument, and that seemed to work. [18:19] odd [18:20] abentley, salgado, I'm off for lunch, back in a while === ursula is now known as Ursinha [19:13] thumper, you around? [19:14] To test out a bzr-related change, do I need to add my ssh key to Sample Person in order to push a branch ? [19:14] jml: evening [19:15] mwhudson, hello [19:15] nhandler, I tend to use ./utilities/make-lp-user $USER [19:15] nhandler, which adds an ssh key automatically if it finds one [19:16] jml: Will that let me push to any user's branch in the dev environment? [19:16] mwhudson, I'm glad I made you laugh :) [19:16] nhandler, no, just the user that it creates. [19:16] nhandler, but, umm, [19:17] nhandler, './utilities/make-lp-user $USER bzr-experts' will probably let you push to any branch in the dev env [19:30] jml: I just looked at my ~/.ssh/config, it looks like rocketfuel setup a ~/.ssh/launchpad_id_dsa key and configured it for bazaar.launchpad.dev. It looks like it uses the user, 'mark' [19:30] nhandler, get rid of that. use ./utilities/make-lp-user [19:30] lol, ok [19:39] mwhudson, do you know if thumper is around today? [19:39] jml: should be [19:39] jml: it's only 8:40 though, he's probably herding kids [19:39] ahh right [19:42] jtv: thanks for spotting the problem with ec2 test [19:42] has anyone fixed it yet? [19:47] my survey says no [19:49] jml: I've run the make-lp-user script, modified the entry rocketfuel had made in ~/.ssh/config to use the ssh key linked to the new launchpad.dev account, but I get a 'Received disconnect from 127.0.0.88: 2: Too many authentication failures for nhandler'. Is there an equivalent of bzr launchpad-login that I need to do? [19:49] nhandler, uhh, maybe [19:50] nhandler, what does 'ssh bazaar.launchpad.dev' tell you? [19:50] jml: Same message as above [19:51] nhandler, did you use your unix user name as the argument to make-lp-user [19:52] jml: I used $USER. I confirmed on the web interface that an nhandler user was created (nhandler@example.com:test) and it was linked with one of my ssh keys (which I have listed for this host in ~/.ssh/config) [19:52] * nhandler loves how he spends more time testing his fixes than creating the patches ;) [19:55] someone review this: https://code.edge.launchpad.net/~mwhudson/launchpad/ec2-test-oops/+merge/15294 [20:00] nhandler, you don't need to do a bzr launchpad-login thing if ssh bazaar.launchpad.dev is failing [20:00] nhandler, umm [20:00] nhandler, try that command with -v or -v -v and pastebin it maybe? [20:03] jml: http://paste.ubuntu.com/328759/ [20:04] morning [20:05] mwhudson, done [20:05] nhandler, looking [20:06]