[00:00] :\ [00:00] I see why it happens, though. [00:00] lamalex: Do you have the log from the original run of rocketfuel-setup? [00:01] wgrant: where would it be [00:02] lamalex: In the terminal buffer. [00:02] wgrant: no, dont have anymore [00:02] lamalex: What does 'make' do? [00:04] it's running some scripts, i'll let you know how it terminates [00:11] wgrant: http://paste2.org/p/429291 [00:14] lamalex: OK, that's what I would expect. [00:14] lamalex: Does rf-get work now? [00:15] just got the shipit error [00:15] lamalex: Great. Apply the patch and rerun rf-get. [00:16] I'll run rf-setup myself this morning and see exactly how it breaks. [00:16] At least we don't have a circular bootstrapping issue. [00:17] wgrant: that shipit error was with your patch [00:24] lamalex: But did the script continue to run? [00:25] Without the patch it should be fatal. With the patch it should continue. [00:36] but now make run fails :P [00:36] and is there a simple way to make the instance public so I can access it? it's on my vps.. [00:37] ah, i see [00:38] make schema? [00:38] utilities/launchpad-database-setup? [00:39] https://dev.launchpad.net/Running/RemoteAccess [00:39] wgrant: yah just saw that last bit [00:42] hmm rocketfuel-setup seems to have not pulled in twisted? [00:43] rocketfuel-get should do that. [00:43] Do you still have the output of its last run? [00:43] http://paste2.org/p/429309 [00:43] rocketfuel-get's last run? [00:43] Yes. [00:43] Oh. [00:44] I know. [00:44] utilities/link-external-sourcecode ../../lp-sourcedeps [00:44] That wouldn't have worked when rf-setup ran it, because rf-get failed. [00:45] (I'm currently running rf-setup locally to work out what's broken...) [00:46] lots :P [00:46] now it needs bzr loom which it didnt pull [00:46] rf-get should do that. [00:46] and link-external-sourcecode should link it in so LP can see it. [00:49] wgrant: think this is the issue? http://paste2.org/p/429313 [00:49] lamalex: Yes. Looks like you killed rf-get in the middle at some point? [00:49] not afaik but possibly [00:49] lamalex: Just remove that subvertpy dir and rerun. [00:50] where's the subvertpy dir? in ../../lp-sourcedeps/sourcecode/subvertpy [00:50] ? [00:50] Yes. [00:52] merci [00:52] Alright, rf-setup running. Let's see what breaks. [00:53] (update-sourcecode - as used by rocketfuel-get - was rewritten earlier in the week, so its unsurprising that something is broken) [00:57] Is it working better now? [00:58] I /think/ [00:58] rerunning make schema [01:00] * lamalex crosses his fingers [01:00] woo! [01:00] thanks wgrant [01:01] lamalex: That was quick. [01:01] Does make run work now? [01:18] wgrant: yup! up and running [01:19] lamalex: Excellent. [01:19] Filing two bugs now. [01:20] lamalex: Bug #432830 [01:20] Bug #432830: rocketfuel-setup does not work [01:50] wgrant: is it possible to set up registration emails for a different domain name? [01:51] hm why is superspace in here [01:51] nm [01:51] my terminal just hadn't refreshed [01:54] lamalex: What do you mean? All email is redirected to root@localhost, as you'd want for a dev setup.; [01:55] wgrant: ah, ok [02:06] wgrant: any info on what i need in terms of a keyserver for soyuz? [02:07] lamalex: I have full docs on setting up a local Soyuz setup. Let me check that they're up-to-date and upload them somewhere. [02:07] :) merci [02:09] lamalex: It used to be much harder, but I've patched bits and pieces so it's pretty easy now. [02:09] How much do you want to do? [02:10] * lamalex isn't sure what the limits are.. I want to be able to push and build? [02:16] lamalex: http://williamgrant.id.au/f/1/2009/running-soyuz.html has the basics of a pretty awful dev setup. There are a few things there that are only necessary if you're running Karmic. [02:20] thanks [02:34] lamalex: When you get to the chroot building stage, it really is much easier to grab an Ubuntu one. [02:34] \ [02:36] lamalex: Oh yeah, you might also have to change the NTP host in /etc/launchpad-buildd/default [02:38] \o/ Branch index redesign has landed. [02:40] rockstar: This I must see. [02:40] * wgrant updates [03:58] sinzui: Do I want to file bugs on dodgy padding in the side portlets? [03:59] I think so. [04:00] wgrant: can you point me to a page to see an example? [04:00] sinzui: There's 0.3em too much padding at the bottom of the context actions portlet. [04:00] There's too much at the top of side portlets that start with an h2. [04:01] i see [04:01] There is also too much at the bottom of the side abr [04:01] So there is. [04:01] I could not get a simple even boarder when I played with it 2 days ago [04:01] I also think the dark grey of the side bar could also do with some decoration (eg. rounded corners?) [04:03] I'll set beuno on to that issue. [04:03] It would also be really nice to un-break the tabs/watermark for distroseries/distoarchseries/distributionsourcepackage/sourcepackage/productseries. [04:03] But I guess that's unlikely for 3.0 :( [04:03] that is a 4.0 goal [04:04] So it's just going to be utterly confusing until then? [04:04] There is a bug that we did not get to fix since the breadcrumb code landed late. I want to show karmic in the crumbs, not 9.10 [04:05] That doesn't really help the crazy behaviour of the tabs on https://edge.launchpad.net/ubuntu/+source/dpkg [04:06] However, the 3.0 UI is a really really great improvement. [04:06] Particularly as the migration will actually be finished. [04:07] Well the UI will be consistent enough that the problems will be more obvious. [04:07] I there some non-sense in sidebars and heading that I don't think will be resolved until 3.10 [04:08] I think it's a bad idea for 3.1.10 to be 6 weeks, but I guess you've no choice what with Karmic in the middle. [04:08] IMO a normal-length cycle to fix 3.0 quickly could be better. [04:10] Yes. We should have have an extra week in July/August but we had dates we had committed too at that time [04:10] Ah. [04:11] 6 weeks is tool long for a release. this UI was too long... [04:11] better than not getting it finished like 1.0 and 2.0. [04:11] but that is what happens when you do a mediocre job the previous year [04:11] :) [04:12] lamalex: Did you run into any issues/ [06:26] wgrant: haven't tried yet. Went out for a bit. Will probably mess around more with it tomorrow, wondering now how to do a vcs import [06:29] lamalex: That's one thing I've not done, but I hear it's fairly easy. [06:30] lamalex: What are you wanting to do with it? [06:31] import a git repo [06:56] hm.. can't figure out what script to run to ge the import to actually happen [06:58] lamalex: cronscripts/code-import-dispatcher.py [06:59] ahh [07:02] thanks :) [07:03] Is it working? [07:03] I haven't locally used vcs-imports at all, and codehosting only minimally. [07:04] not sure, it looks like it ran, but it's not showing any revisions [07:04] Check the directory manually. [07:04] where's that [07:04] It won't show revisions in the web UI until you scan the branch. [07:04] No idea. [07:05] Well, it should be somewhere under /var/tmp [07:05] ah, so need to run another script to scan the branch? [07:05] Yes. [07:05] There's a make target for it.. [07:05] * wgrant hunts. [07:06] make sync_branches [07:07] hmm.. failed [07:07] supermirror-pull.py: error: Unhandled arguments ['upload'] [07:08] Try just 'make scan_branches'? [07:08] Might not have to pull it. [07:10] hmm the vcs I added gives an error [07:10] 2009-09-19 06:08:22 INFO OOPS-1358BS1: Transport error: Server refuses to fulfill the request (403 Forbidden) for http://bazaar-internal.launchpad.dev/00/00/00/4d/.bzr/branch-format (~vcs-imports/jolicloud-netbook-config/trunk) [07:10] No idea. [07:10] yah [07:24] got it, apache config failure [07:37] Damn, build failre. [07:37] +u [07:41] u+something [07:41] * wgrant thwacks lifeless. [07:42] mmmm [08:52] The breadcrumbs and title on https://answers.edge.launchpad.net/ubuntu/karmic/+source/gnome-terminal/+addquestion make me sad. [08:53] The most specific title segment is buggy, and also contains all of the information in the rest of them. [08:57] I'm not a fan of breadcrumbs as a concept [08:58] I think they're a great idea, but not quite in the current implementation. [09:06] restarted poppy on germanium [09:07] elmo: Thanks. [09:21] How easy is it for somebody to look up an OOPS that occurred at a particular URL? [09:27] (in particular I'm interested in the traceback for the OOPS caused by a POST to https://api.edge.launchpad.net/beta/ubuntu/+archive/test-rebuild-20090909 around 0740 UTC today. [09:58] Can I express conjunction in TALES without having to resort to python: ? [11:45] henninge: thanks for doing the testfix [12:36] bac: np [12:38] henninge: it was nice to wake up seeing all of that red but finding you'd already got a fix in. [12:38] bac: see, there *is* an advantage of us all living in differnt time zones ... ;-) [12:39] henninge: i feel bad for the dudes down under. it seems they spend a lot of time cleaning up after us... [12:41] bac: but from what I hear, they also have it nice and quiet. Just a few of them, always reviewing each other's branches, no long queues ... ;) [12:54] Hm, this is interesting. [12:54] I have a case where the root context of an object is incorrect. [12:54] It's a distribution archive. The object directly above it is a distribution. [12:54] Yet the root context is an IPerson. [12:55] I think this is because there's an adapter from IArchive to IPerson, which descends from IRootContext. [12:57] It seems pretty fragile. === henninge is now known as henninge-afk [14:01] mwhudson: ping === Ursinha is now known as Ursinha-afk [20:47] bac: 1 am on a sunday, not likely [22:33] mwhudson: yeah, my tz math was off! [23:51] I don't see breadcrumb guidelines on the 3.0 conversion page [23:51] Some of them are pretty bad at the moment, eg: [23:51] 1. Ubuntu [23:51] 2. “conky” package [23:51] 3. Questions for “conky” package in Ubuntu [23:51] 4. Ask a question about conky in ubuntu [23:51] I'd be happy to go around and fix them, if there were guidelines or a known-good example.