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