[12:28] <sabdfl> dudes
[12:45] <kiko> sabdfl!
[12:46] <sabdfl> hey kiko
[12:46] <sabdfl> just starting work on your present
[12:46] <kiko> fixing some issues linkchecker popped up
[12:47] <kiko> interesting issue though
[12:47] <kiko> http://localhost:8086/distros/ubuntu/hoary/+sources/evolution/+pots/evolution-2.2/st/+translate
[12:47] <kiko> sabdfl, the targets of each Facet link are really non-obvious
[12:47] <sabdfl> yes
[12:47] <kiko> I fixed the obvious errors, but the result is very confusing
[12:47] <sabdfl> remember i was saying that the inheritance idea wasn't as smooth as i'd hoped, in brazil
[12:47] <kiko> yes
[12:48] <sabdfl> the fact that you can switch context is jarring
[12:48] <kiko> the way it should be (IMO)
[12:48] <sabdfl> ?
[12:48] <kiko> is that we should be under one context 
[12:48] <kiko> and then have subcontexts 
[12:48] <sabdfl> except....
[12:49] <kiko> that would hopefully cover the depth of rosetta and malone
[12:49] <sabdfl> it's almost as though, when you mouseover the "Bugs" link, the breadcrumb related to the relevant context should be highlighted
[12:49] <sabdfl> SOME sort of visual cue as to *what* +bugs you'll be looking at
[12:49] <kiko> hmmm
[12:49] <sabdfl> i know that's crack
[12:49] <kiko> well
[12:49] <kiko> the visual cue I'm thinking of would be clear
[12:49] <kiko> Product: Mozilla Firefox
[12:49] <sabdfl> but that's what i found myself looking for - some idea, when i click on the facet, where I'll be
[12:49] <sabdfl> we could work that into the page title
[12:49] <kiko> and then all the facets would apply to that product
[12:50] <sabdfl> but...
[12:50] <kiko> I am unhappy that it doesn't cover series though
[12:50] <sabdfl> it's not even
[12:50] <kiko> yes
[12:50] <sabdfl> bugs would drop you to product, if you were on translations, which are at a series level
[12:50] <kiko> because we have translations (and at some point bugs) for that series
[12:50] <kiko> but calendars would always be for products, I imagine
[12:50] <sabdfl> when we have bug-target-to-series that will be less of an issue
[12:50] <kiko> right
[12:51] <kiko> but calendar is still a problem :)
[12:51] <sabdfl> but the system will never be n-way symmetrical
[12:51] <sabdfl> ed zacchary
[12:51] <kiko> suicide run
[12:51] <kiko> how to solve, how to solve
[12:51] <kiko> well, be happy you're not the only one worried about that
[12:51] <kiko> :)
[12:52] <kiko> sabdfl, the immediate fix is quite horrific but works
[12:52] <kiko> can I send you a patch?
[12:52] <sabdfl> ah
[12:52] <sabdfl> hmm.
[12:53] <kiko> well, for some value of works
[12:53] <kiko> it stops us 404ing
[12:53] <sabdfl> no, land it if you think it's the right thing to do
[12:53] <kiko> and takes us to pages
[12:53] <sabdfl> with a review ;-)
[12:53] <kiko> perhaps not the right pages though
[12:53] <sabdfl> it sounds non-trivial
[12:53] <kiko> I was wanting your review, sneaky man
[12:53] <kiko> it's only like 30 lines
[12:53] <sabdfl> i am working on your gift
[12:53] <sabdfl> ok, privmsg
[12:53] <cprov> kiko: I've been working on some facets for soyuz, removing unreacheable links, in fact, creating specific facets classes for items in my domain, looks like we do have a symmetrical problem to solve or workarround.
[12:54] <kiko> cprov, makes me cry
[12:54] <sabdfl> i want to create a bounty facet too
[12:54] <sabdfl> i polished up the bounty system, it's ready to roll now
[12:54] <sabdfl> just as a registry
[12:55] <cprov> kiko: in which sense ?  I doubt you changed the same pieces I did.
[12:56] <kiko> cprov, well, the problem is rather difficult to solve. I think it requires some infrastructure
[12:56] <kiko> you shouldn't need to write complex code in the facets
[12:57] <kiko> the default handler should search through the parents and decide what/if to link to
[12:57] <kiko> cprov, can you get me dsilvers' pastebin url?
[12:59] <kiko> sabdfl, https://chinstrap.ubuntu.com/~dsilvers/paste/fileA7FOdg.html
[12:59] <kiko> sabdfl, and I don't even have a hole in the ground <wink>
[01:02] <sabdfl> kiko: do we have a calendar for a *sourcepackage*?
[01:02] <sabdfl> bugs looks fine
[01:02] <sabdfl> just calendar for a sp has me surprised
[01:02] <sabdfl> otherwise, looks perfectly reasonable
[01:07] <cprov> kiko: do we encourage complex code like that in facets ? I mean, nothing terrible wrong, but aren't we missing something in the facets infrastructure to reach our aims ?
[01:07] <Keybuk> ah, it helps to run "upgrade.py" before "security.py"
[01:07] <Keybuk> this explains a lot
[01:09] <sabdfl> Keybuk: :-)
[01:09] <sabdfl> the explosive kind? with the heads on them?
[01:10] <Keybuk> no, no, just ordinary plain ones from a few years back
[01:10] <Keybuk> try getting into a country if those fall out at passport control ;)
[01:10] <cprov> ehe, time to go. see you.
[01:14] <kiko> sabdfl, we don't have a calendar for a sourcepackage; then you do IProductOwner that raises a TypeError, which I catch
[01:15] <kiko> so we're safe there
[01:16] <kiko> hmmm
[01:16] <kiko> sabdfl, should the calendar be the calendar for the distro or distro release?
[01:17] <sabdfl> i don't know, honestly. none of them make sense as a switch from a pofile
[01:17] <sabdfl> perhaps these facests should just be disabled
[01:17] <kiko> I rather agree to be honest
[01:17] <cprov> somebody knows what this error means: testAnwersOnce (CVS.tests.test_CVS.PServerHelperTest) ... ERROR     (came from PQM failure)
[01:18] <sabdfl> i often find myself wanting to jump from the product world into the distro world, and not sure what the most efficient route is
[01:18] <kiko> cprov, an error in cscvs
[01:18] <sabdfl> cprov: hmm... try again
[01:18] <kiko> cprov, should be an odd timing issue -- just retry
[01:18] <sabdfl> sometimes cscvs does weird things with timing of process entries and exits
[01:18] <kiko> sabdfl, the most efficient route today is to go to the product overview page and through a portlet :-/
[01:18] <cprov> sabdfl: ok, I'll, thanks 
[01:19] <sabdfl> kiko: not if you want to jump to distro with no Packaging data between that product and that distro
[01:19] <kiko> sabdfl, if you're happy with the patch, I'll land it. if you want me to disable facets, I can do that too. 
[01:19] <sabdfl> i want to jump to /distros/ generally
[01:19] <kiko> sabdfl, ah
[01:19] <kiko> that's an interesting problem
[01:19] <kiko> I hadn't understood entirely
[01:19] <sabdfl> i *almost* think we want links to /distros/ and /people/ and /products/ and /projects/ somewhere on every page
[01:20] <kiko> well
[01:20] <sabdfl> remember the "pillars of launchpad"
[01:20] <kiko> I would argue that the frontpage is the way to go
[01:20] <sabdfl> sure
[01:20] <sabdfl> seen the new one?
[01:20] <kiko> sabdfl, how do I make it show up
[01:20] <sabdfl> its a bit busy but will come into focus with some tweaking
[01:20] <sabdfl>  /real-index.html
[01:21] <sabdfl> or staging.ubuntu.com
[01:21] <kiko> wow!
[01:21] <sabdfl>  [trivial] 
[01:21] <kiko> portlets are crack though
[01:21] <kiko> you know that by now :)
[01:21] <sabdfl> not really... just need a tinge of colour to make them less important than the central page content
[01:22] <Keybuk> sweet
[01:22] <sabdfl> same for the "most active projects" listing, needs to be slightly "lower" than the core bit
[01:22] <sabdfl> the idea is to focus people on the registry, but tease them with translations, bugs, bounties etc
[01:22] <kiko> what about ubuntu?
[01:23] <kiko> or the distro world
[01:23] <Keybuk> if you look at ubuntu you see the "most active package" and "most active maintainer" and stuff?
[01:24] <sabdfl> Keybuk: could do, nice idea!
[01:25] <sabdfl> oops
[01:25] <sabdfl> i do believe the portlet on the home page is showing the LEAST active contributors
[01:26] <sabdfl> lazy fucks
[01:26] <sabdfl> hmm....
[01:26] <sabdfl> no, maybe the karma update scripts just haven't run on production yet, so we don't have karma data for anybody
[01:26] <sabdfl> the new karma cacheing ones
[01:27] <sabdfl> mpt: i'm going ahead with your page
[01:27] <sabdfl> it's a very good start, thank you
[01:27] <sabdfl> i understand your reservations, but i think we will deal with them one by one
[01:27] <sabdfl> calendars should not be using tabs, for a start
[01:44] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  Update production email and staging configs for launchpad.net domain (patch-2281: stuart.bishop@canonical.com)
[02:15] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=salgado]  Temporary directory for GNUPGHOME and atexit register to remove it on normal termination, removing unused properties, polish on docstring. (patch-2282: celso.providelo@canonical.com)
[02:47] <ddaa> Yay!
[02:48] <ddaa> I finally put the CVS parser stuff to the point where I can actually start working on fixing the python import problem...
[03:55] <kiko-zzz> congrats ddaa
[04:53] <Keybuk> stupid question time
[04:53] <Keybuk> I need to update two tables affected by each other's constraints
[04:53] <Keybuk> is there a way to do that?
[04:54] <elmo> remove the constraints temporarily?
[04:54] <Keybuk> I thought it'd work like that within a transaction (ie only check the constraints at commit) but it doesnt seem to
[04:58] <Keybuk> ah, SET CONSTRAINTS ALL DEFERRED after the begin
[05:00] <Keybuk> though that doesn't seem to work
[08:12] <Madeye> Hi
[08:12] <Madeye> guys I'm getting this error message while trying to login to launchpad.
[08:12] <Madeye> The email address 'Jad@php.net', which you're trying to use to login has not yet been validated to use in Launchpad. We sent an email to that address with instructions on how to confirm that it belongs to you. As soon as we have that confirmation you'll be able to log into Launchpad.
[08:13] <Madeye> if there is any admin right now, would they please re-send the confirmation key? and by the way, I have already confiremed, and I have already participated in some translation, so it's abvious its system problem 
[08:50] <BjornT> Madeye: didn't you get a new validation email when you tried to login?
[08:50] <Madeye> BjornT, no
[09:05] <BjornT> Madeye: strange, you should have gotten an email. i'm not sure what's wrong
[09:06] <BjornT> Madeye: the one to talk to is salgado, but he's in Brazil, so he won't be around for a while (if he'll be around at all this weekend)
[09:07] <Madeye> he's the only guy who can help ?
[09:08] <Madeye> what a dectatorship in an open source movement :-)
[09:12] <BjornT> Madeye: i'm sure that other people can help as well (but salgado knows the most about these things), so you could try ask again when some more people are around. i'll try to take another look to see if i can find what's wrong.
[09:18] <Madeye> thank you
[09:24] <BjornT> Madeye: you could try go to https://launchpad.net/+forgottenpassword and type your email address there. then you should get an email with a link, where you can reset your password. after you've done that your address should be validated 
[09:32] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  fix bug 1810. (patch-2283: bjorn.tillenius@canonical.com)
[01:45] <Jad> BjornT, i've tried, but i havn't got the reset email yet 
[02:42] <sabdfl> ddaa: rock on. then my weekend present is for kiko AND you