[01:43] rockstar: still there? [01:49] thumper, yes. [01:50] (for various definitions of the word "there") [01:50] did you work out the upgrade branches issue? [01:52] thumper, no. I started looking through logs but then got distracted by an actual ec2 email (!) [01:52] ok [01:52] ...and now I seem to have lost my connection to devpad and cannot reconnect. [01:52] ssh: Could not resolve hostname chinstrap.canonical.com: Temporary failure in name resolution [01:53] wtf? [01:54] we need a losa query to work out which upgrade branch is in progress [01:54] because it isn't being logged [01:59] sinzui: I don't suppose you can take a 5 minutes call? [02:00] thumper, I do [05:19] moinish [06:02] lifeless: hi [06:03] anyone remember how to get a vocabulary from a name? [06:09] maxb: They are caused by the same issue. [06:13] * thumper is hanging out for the day to end [06:14] almost got this bug fixed [06:14] StevenK: how are you enjoying soyuz? [06:15] thumper: It's challenging, but I'm enjoying it [06:18] thumper: They are named utilities IIRC, so getUtility(IVocabulary, 'foo') (not sure if that is the real interface to use) [06:18] stub: thanks, but I've got it now [06:18] stub: I've avoided the need :) [06:19] IVocabularyFactory looks like... anyway. [06:19] stub: I don't suppose there is a way to replace the vocabulary being used in form_fields easily is there? [06:20] * thumper fires up pdb again [06:21] thumper: I think you create a new interface and override that attribute. Not sure. [06:21] hmm [06:22] I have to do it somewhat dynamically [06:22] it seems I have to do the form_fields.omit, then add the new one [06:22] I was just wondering if there was a short circuit [06:22] although I feel that the underlying fields that are being referenced are exactly that, references [06:22] and changing the vocabulary could be hazardous [06:50] stub: thanks, your help got me a lot further. Added comments to bug 388997. [06:50] Bug #388997: +imports page should handle URL "hacks" more gracefully, instead of OOPS with LookupError [06:51] * thumper EODs [06:52] g'night thumper [06:53] danilos: that branch for setting BuildQueue.processor looks good to me... what work does it still need? [06:53] jtv, QA :) [06:53] pah [06:54] jtv, well, I'd like to QA it before I get it landed :) [06:54] sissy [06:56] danilos: two separate issues there afaics... is the branch good, and does it solve the problem. As part of the former, I can give you a review now. [06:56] jtv, heh, certainly then :) [10:16] bigjools: Can I get a full publisher log at some point? The last one was truncated early on. [10:24] wgrant: ppa or ubuntu? [10:24] bigjools: The latter. [10:24] (the former I can't really see, since it is full of private stuff) [10:24] (and the latter is the one that is really really really slow) === vila is now known as mgz [10:37] bigjools: I know how that build go corrupted yesterday. [10:37] The one where the build was 'Needs building', but the job was FAILED. [10:37] There's a bug in the abort handler. === matsubara-afk is now known as matsubara [13:18] hi [13:19] i would like have some help about installing launchpad [13:20] Hi ghostoyo. I might be able to help. What is the problem? [13:21] i have install bzr [13:21] then i launch the script rocketfuel-setup [13:22] i have an error : ERROR: The user root has not registered any SSH keys with Launchpad. [13:23] then i have a question i must to give some keys but i donnu which [13:23] ghostoyo, what do you see when you type "bzr whoami"? [13:23] root [13:23] ghostoyo, and have you set up a launchpad account? [13:24] yes i have a launchpad account [13:25] ghostoyo, and "bzr launchpad-login" shows the correct user? [13:25] no it's not the same [13:25] well, it should be your launchpad username [13:26] one is the account that will be signing the commits [13:26] the other is the account that communicates with launchpad [13:26] No Launchpad user ID configured. [13:27] how i can configure a account ? [13:28] ghostoyo, if you have a launchpad account set up, just type "bzr launchpad-login whatevermylpaccountnameis" [13:30] it say me that i am not registered [13:31] ghostoyo, could you tell me your Launchpad account name, so I can look it up? [13:31] Ghostoyo :) [13:35] did you found me? [13:35] ghostoyo, I'm reading the source for rocketfuel-setup, and it says that the error can be ignored. When you ran it, did the script continue despite the error? [13:36] yes but then i have a ask about som keys [13:36] You probably shouldn't be running rocketfuel-setup as root. [13:36] It's not designed for that, and probably hasn't been tested. [13:36] have u succed in install it? [13:36] Yes, as my own user. [13:37] ghostoyo, I just checked on launchpad for "https://edge.launchpad.net/~Ghostoyo", and there is not account there. [13:37] i launch the script and give you exactly the message [13:37] Does it cause an error? [13:37] It should work even without keys. [13:37] correct [13:37] ok i will try [13:38] https://launchpad.net/~milot-jean [13:38] ghostoyo: Please confirm you're not running any of this as root any more [13:38] yes i'm root [13:39] Well, that is incorrect [13:40] sorry ? [13:40] You should NOT be setting up Launchpad as root [13:41] ok [13:42] Also, when you say you want to "install" launchpad, you do realize that what you are doing is setting up a Launchpad *development* environment, *not* installing Launchpad for production usage? [13:43] yes [13:45] ghostoyo, when you run the rocketfuel-setup script (as a user account, your own or a new one like /home/launchpad), the script will ask you for your Launchpad username. Type 'milot-jean' when it does. [13:46] yes i do === Ursinha-afk is now known as Ursinha [14:05] ghostoyo, it should work then. You can try adding "set -x" to the top of the script, and it will print out each command as it is executed. You can then tell us the line with errors if it happens again. [14:15] gary_poster, should zc.buildout projects still have the "import ez_setup" line at the top of their setup.py file? [14:16] gary_poster, I'm noticing that lazr-js uses "import distribute_setup" instead. That dies horribly when you then try to run "bin/py setup.py" [14:16] mars, that and other changes I now regard as mistakes. I tried to make changes so a non-buildout workflow would still be possible It made things messier than necessary for little to no benefit. So IOW, "no" is fine. [14:16] good! [14:17] that is a nice answer :) [14:19] gary_poster, fwiw, I noticed that 1.5.0b1 also fails in isolating lazr-js from the base system when you set install-from-cache with the default setting. [14:20] gary_poster, it picks zope.interface 3.5.1 from dist-packages, then dies. What it /should/ do is look on PyPI for 3.5.3 and download it into the global .buildout/ cache. [14:22] gary_poster, I suspect that there is a new "buildout way" for 1.5.0, one that uses nice things like the global cache, and that lazr-js does not follow it. Pain ensues. [14:24] mars, ah, yes! [14:24] mars, is there a branch I can see? [14:24] the easy answer is this: [14:24] gary_poster, lp:lazr-js/1.0 [14:24] for scripts, instead of using the zc.recipe.egg recipe in buildout.cfg, use z3c.recipe.scripts [14:24] that should be it [14:25] subtle [14:25] Some recipes still need to use the new approach, so they still may be problematic [14:25] mars, I guess yes. I felt it was important to provide full backwards compatibility [14:25] I agree [14:26] it is subtle because it is not obvious that I need to change the buildout.cfg recipe in order to use the new buildout cache, and to fix the isolation problem. [14:26] gary_poster, given that there is a new "buildout way", and upgrade guide or cheatsheet may be in order. [14:29] mars, agreed about the lack of obviousness. :-/ in the same vein as the discussion we had aboutan "opinionated" buildout, I thought it might be nice to have a bootstrap (or some other script) that would give you a buildout directory set up the opinionatedly-correct way. Something much lighter weight than the lazy.yourpackage thing, but a similar way to get started. [14:29] s/discussion we had aboutan "opinionated" buildout/discussion we had about an "opinionated" bootstrap/ [14:30] right [14:32] the message : Fetching revisions:Inserting missing keys: [14:33] what i must to enter ? [15:31] sinzui, https://launchpad.net/live-installer [15:32] sinzui, Why doesn't launchpad suggest the 'live-installer' package under 'Packages in Ubuntu' section? [15:33] Usually because live-installer is not published in Maverick [15:33] cody-somerville, it may have matched, but we limit the matches to 8 [15:34] It is published. [15:34] cody-somerville, I think the latter is the case here [15:34] me too [15:34] Should I file a bug? [15:35] Lp is search DistributionSourcePackageCache. It looks like the method does not give precedence to exact matches [15:35] * cody-somerville nods. [15:36] sinzui, Also, can I have maintainership of the live-installer project on launchpad? I maintain the package in Ubuntu and participate upstream as well. [15:37] cody-somerville, you need to ask Mantas Kriaučiūnas, if he never replied a Launchpad admin can give it you [15:37] * sinzui has a plan to let registry administrators do this too === Ursinha is now known as Ursinha-lunch === matsubara is now known as matsubara-lunch === gary_poster is now known as gary-lunch === beuno is now known as beuno-lunch [17:12] EdwinGrubbs, ping, were we supposed to nuke the apidoc dirctory in r10865 ? [17:18] EdwinGrubbs, the $(API_INDEX) target in the Makefile still depends on that directory existing in source control. If you want, I can make it into a generated target instead of a checked-in one if the deletion was intentional. [17:28] mars, I'm looking at that revision now. === matsubara-lunch is now known as matsubara === Ursinha-lunch is now known as Ursinha === Pilky_ is now known as Pilky === gary-lunch is now known as gary_poster === beuno-lunch is now known as beuno [18:56] I'm testing out launchpad from ~/launchpad/lp-branches/devel, but can't locate etc/zope.conf to disable Developer mode [19:24] Why would you want to disable developer mode? [19:31] to see how much faster it is [19:52] flacoste, ping [20:00] flacoste, unping [20:20] gary_poster, do you know where in the test suite an expensive functional test for test_on_merge.py might go? [20:21] mars on call [20:21] k [20:45] gary_poster, ping [20:46] sinzui on call [20:46] notes [20:46] noted [21:47] mars, um....canonical.launchpad.scripts.tests ? [21:48] sinzui, pong [21:49] gary_poster, I was looking for something under lib/lp/ actually. I think lib/lp/scripts/tests/ or lib/lp/testing/tests/ may work. [21:49] gary_poster, it is slightly complicated by the fact we do not distinguish between unit tests and functional/integration tests, but oh well. [21:50] mars, sounds fine. "expensive" should give the build engineer pause, I would think, but I expect it's a tricky balance? [21:50] I prefer not to touch lib/canonical/... for new code. There are 6? scattered directories under there with some sort of 'test' in the name. [21:51] gary_poster, expensive because it involves IPC and a one second timeout. IPC means it is not a unit test. [21:51] mars, ah ok === matsubara is now known as matsubara-afk [22:24] http://tinychat.com/pugquit [22:26] creatix: irc spam? please don't === Ursinha is now known as Ursinha-afk === flacoste is now known as flacoste_afk