[12:17] <bradb> salgado: ah, found the cause of that bug whose exception you showed me
[12:17] <salgado> bradb, cool. what was it?
[12:17] <bradb> i can reproduce it when I click "Change" on the +duplicate form, where there's an ID in there and I don't chagne it
[12:17] <bradb> hence the "empty bug_delta" bit of the error msg
[12:31] <lifeless> try pqm again please
[12:31] <lifeless> bad config foo by me.
[12:35] <cprov> lifeless: anything wrong with PQM ?
[12:35] <cprov> Executing pre-commit hook "TZ=Asia/Calcutta make check_merge" at Thu Jul  7 23:31:48 2005   /bin/sh: TZ=Asia/Calcutta make check_merge: No such file or directory   pre-commit hook failed with error code 32257 at Thu Jul  7 23:31:48 2005
[12:36] <cprov> lifeless: sorry, have seen the email from salgado 
[12:36] <lifeless> cprov: ^^^
[12:37] <cprov> time to go ... see you later tonight
[01:41] <Keybuk> meh
[01:41] <Keybuk> Python's re module doesn't understand [[:digit:] ] 
[01:51] <lifeless> really?
[01:51] <Keybuk> yeah
[01:52] <Keybuk> this, children, is why we don't use regexps as "interoperable" config
[01:52] <ddaa> it does understand \d though
[01:53] <Keybuk> sure, but when you're parsing someone else's config that uses regexps for special things ...
[01:59] <lifeless> ddaa: hey, we're running 1.4 in importd-land now right ?
[01:59] <ddaa> lifeless: it would be surprised of learning otherwise
[01:59] <lifeless> ddaa: I've some code I'd like to to spend some time on tomorrow - say a half days worth, see where it gets to - the locations support.
[02:00] <ddaa> interesting problem, but either too much (it makes resource aquisition, like nicknames or document ids, quite complex) or too little (it's not really robust as it's limited to star-topology)...
[02:00] <ddaa> lifeless: well, I think I specced the thing quite thoroughly, doing it just one of those "simple matter of engineering"...
[02:01] <ddaa> lifeless: please specify "half day"
[02:01] <ddaa> I can imagine at least three different values for that.
[02:02] <ddaa> 12h (half of a legal day), 8h (half of a waking day), 4h (half a working day), 3h (half of a working day minus email etc.), 1h (half of what is left after imports on a good day)...
[02:04] <lifeless> ddaa: 4h minimum, you may choose 8inventory_link_target or 12 at your discretion.
[02:05] <ddaa> that's funny how random bits of baz source code make irruption in your speech... have you considered seeking counsel?
[02:05] <ddaa> I mean, that's starting to be concerning...
[02:06] <ddaa> lifeless: here is a design challenge.
[02:06] <ddaa> I have this body of well tested, designed, document source code. But I want to replace by something simple and less functional to go forward.
[02:06] <ddaa> Should I just rm the stuff?
[02:07] <lifeless> is anything using the stuff you don't want ?
[02:07] <ddaa> Or do you have an idea how to keep it around while preservig it from bitrot?
[02:08] <carlos> lifeless, ddaa hi, I need some support with bazaar
[02:08] <ddaa> It's not a matter of "don't want". It's just that it has assumptions that make it more complex to develop than what I can be bothered to put up with right now. So I want to replace by something that makes more assumptions.
[02:08] <carlos> lifeless, ddaa I'm trying to merge a patchset into production because stub got some conflicts and asked me to do it
[02:09] <ddaa> replay?
[02:09] <carlos> and the merge gives me conflicts and touches lots of files I didn't changed with that changeset
[02:09] <carlos> ddaa, replay?
[02:09] <ddaa> neverming
[02:09] <carlos> no, merge
[02:09] <lifeless> carlos: you should not be merging to do a cherry pick
[02:09] <carlos> This is the output of the merge:
[02:09] <carlos> https://chinstrap.ubuntu.com/~dsilvers/paste/fileEimVAo.html
[02:09] <lifeless> carlos: you need to :
[02:09] <carlos> lifeless, ok, then?
[02:09] <lifeless> switch to the production branch
[02:10] <lifeless> replay your specific patchset 
[02:10] <carlos> lifeless, stuart asked me to branch from production
[02:10] <carlos> I'm working on my own branch
[02:10] <lifeless> figure out whether it needs other patch sets that are in devel but not production, or deal with the conflicts
[02:10] <lifeless> ok, on your branch then
[02:10] <carlos> carlos.perello@canonical.com--2004/launchpad--production--1.24--base-0
[02:10] <carlos> ok
[02:11] <lifeless> so use 'replay' to get a single patch.
[02:11] <carlos> perfect, it works now
[02:11] <carlos> the conflict is with the test
[02:11] <carlos> I suppose it's ok if I just fix it, right?
[02:12] <lifeless> fix and commit
[02:12] <lifeless> then we can pull that into production
[02:13] <lifeless> ddaa: so...
[02:13] <lifeless> ddaa: you have a codebase A that is used by some client code, but is proving hard to change, OR
[02:14] <lifeless> ddaa: you have a codebase A that is not used by client code and is proving hard to change
[02:14] <ddaa> it's used by client code
[02:14] <ddaa> but the client code can be easily modified
[02:14] <lifeless> do you think the codebase is right - is it the correct solution ?
[02:15] <ddaa> Thinking of it... the interface probably needs not change much...
[02:15] <ddaa> It is generally heading in the right direction for the problem it's trying to solv.
[02:15] <ddaa> The issue is that I want to change for a simpler problem.
[02:15] <lifeless> ok
[02:16] <lifeless> so - start writing the code for the simpler problem in terms of the current codebase.
[02:16] <lifeless> migrate client code to that using standard refactorings
[02:17] <ddaa> Mh... so you are saying "remove tests and support code for cases that will no longer be supported"?
[02:17] <lifeless> if you don't want to solve the problem they try to solve - yes
[02:17] <ddaa> mh...
[02:18] <lifeless> if you do, but you just want a simpler api for the client code, then you need to work on a simpler api that uses the more complex code. Unsurprisingly these approaches are nearly identical.
[02:20] <ddaa> I'm pondering whether the interesting uses cases (mostly bridging nat boundaries and improving latency between close nodes) can be supported eventually without rewriting the same code I'm going to remove...
[02:22] <ddaa> I guess yes... I can still have those use cases with a central arbitrator for resource allocation...
[02:23] <ddaa> And a mesh-topology p2p network is an order of magnituder more complex that what I'm doing now... would probably need a near complete rewrite of the internals...
[02:24] <ddaa> always sad to have to throw away some good crack...
[02:26] <ddaa> actually... I can get p2p functionality only client-server support in the leafs... and that's probably even better design.
[02:26] <ddaa> lifeless: thanks
[02:28] <carlos> lifeless, mirroring the branch. Thank you 
[03:12] <carlos> good night
[04:31] <dilys> Merge to rocketfuel@canonical.com/launchpad--production--1.24: Cherry pick Rosetta fixes into production (patch-4: carlos.perello@canonical.com, rocketfuel@canonical.com)
[04:49] <bradb> does that mean she's fixed?
[06:09] <jamesh> mpt: looks like I'll be on the same flight to Brazil as you now.
[06:10] <mpt> You're going via Auckland?
[06:11] <jamesh> yep
[06:11] <mpt> cool
[06:11] <jamesh> Perth -> Sydney -> Auckland -> Buenos Aires -> Sao Paulo
[06:12] <jamesh> mpt: there was a meeting in Brazil last year (before I joined)
[06:14] <mpt> heh, someone called Malone "the Universe Bugzilla"
[06:14] <mpt> Who deals with Launchpad login problems?
[06:17] <mpt> jamesh: Do you want to talk about calendar menus sometime?
[06:19] <bradb> mpt: my guess is that SteveA deals with lp login problems
[06:20] <mpt> hey bradb, sorry I'm late
[06:20] <mpt> we could talk Malone menus now if you like
[06:20] <bradb> hm, how long would that take, do you think/
[06:21] <bradb> i wasn't planning on doing that tonight, to be honest, but if it's pretty quick, maybe (it's 0h20 here)
[06:25] <mpt> bradb: probably half an hour
[06:26] <mpt> no particular hurry, I can add them myself (just a bit slower than Real Zope Hackers)
[06:26] <bradb> what do i have to know from you about menus?
[06:26] <mpt> what menus should appear where, and what should be the selected item on particular pages
[06:26] <mpt> I guess I could just put that in the LaunchpadMenus spec
[06:27] <bradb> i.e. you'll tell me exactly what menu items to put on what pages, etc?
[06:27] <mpt> yah
[06:28] <bradb> wild. yeah, it might be more effective if you could either 1. update the spec or 2. write a little email about that. if you'd prefer to do neither of those, perhaps we can try to find another time (on the weekend? busy tomorrow night) to discuss them. your call.
[06:28] <mpt> ok, I'll do (1)
[06:30] <bradb> lifeless: i just saw this in another failure mail from pqm (longish paste):
[06:30] <bradb> Traceback (most recent call last):
[06:30] <bradb>   File "/home/pqm/arch/queue/workdir/rocketfuel@canonical.com/rocketfuel@canonical.com---launchpad--devel--0/launchpad/lib/CVS/tests/test_CVS.py", line
[06:30] <bradb> +1927, in testChangeLog
[06:30] <bradb>     self.assertEqual(logForChangeset(cs), expectedLog)
[06:30] <bradb> AssertionError: 'Summary: aa\nCSCVSID: MAIN.2\nKeywords: cscvs:MAIN.2\n\nAuthor: foo\nDate: 1970-01-12 13:50:00 Asia/Culcutta\naa\n' != 'Summary:
[06:30] <bradb> +aa\nCSCVSID: MAIN.2\nKeywords: cscvs:MAIN.2\n\nAuthor: foo\nDate: 1970-01-12 13:50:00 Asia/Culc\naa\n'
[06:30] <lifeless> hahahah
[06:30] <lifeless> fixing
[06:31] <bradb> thanks
[06:31] <lifeless> turns out cscvs's test suite depends on TZ :!
[06:31] <bradb> mpt: good idea, thanks.
[06:31] <lifeless> or something like that anyway
[06:32] <lifeless> submit again please
[06:32] <bradb> ok, waiting for make check to finish here then will resubmit two branches
[06:39] <mpt> ah, crud, /home has run out of space again
[06:39] <bradb> HEH
[06:39] <bradb> lifeless: resubmitted both branches. fingers crossed!
[06:39] <mpt> The cure for this is deleting one's revlib, correct?
[06:40] <bradb> yes
[06:40] <bradb> that's what i do anyway
[06:40] <mpt> and my revlib is ~/archives/mpt@canonical.com?
[06:40] <lifeless> NO
[06:40] <bradb> no!
[06:40] <mpt> ok ok
[06:40] <lifeless> baz my-revision-library
[06:40] <lifeless> don't delete the revlib itself.
[06:40] <mpt>  /home/mpt/.arch-revlib
[06:41] <lifeless> rm -rf $(baz my-revision-library | head -n 1)/*@*
[06:41] <bradb> lifeless: will Bad Things Happen if you remove the revlib dir itself?
[06:42] <lifeless> Yes
[06:42] <mpt> bash vs. nautilus cagefight!
[06:42] <lifeless> you will nuke the config in the revlib, disabling it and making it greedy rather than sparse.
[06:42] <bradb> right
[06:42] <lifeless> neither of which are desirable.
[06:43] <mpt> Mine contains both =greedy and =sparse files
[06:43] <lifeless> they need to be preserved
[06:43] <mpt> both of which are empty
[06:43] <lifeless> thats fine
[06:57] <lifeless> rm -V ?
[06:57] <lifeless> bah
[06:57] <lifeless> -v
[07:00] <mpt> I mean a percentage, not a scroll of filenames
[07:01] <mpt> so I could calculate whether I have enough time to get (a) a drink, (b) fish and chips, or (c) a social life
[07:02] <lifeless> count =(($(find . | wc-l )) ; rm -v | ....
[07:02] <lifeless> ;0
[07:02] <lifeless> heres a trick you can use
[07:03] <lifeless> rather than deleting them, rename them 
[07:03] <lifeless> i.e. rename s/^/foooo/ .../*@*
[07:03] <lifeless> now they won't be used.
[07:03] <lifeless> rm -rf .../fooooo*@*
[07:03] <lifeless> and just start working again
[07:04] <lifeless> ext3 is very slow at deleting such stuff :|
[07:09] <mpt> oh, it finished several minutes ago
[07:10] <mpt> I didn't know it was going to take that long, though
[07:10] <mpt> One day I'll have time to learn all that shell trickery
[07:10] <mpt> after I retire, maybe
[07:13] <mpt> A real smart delete command would show me the progress only if the prorgress was doing to take longer than a few seconds
[07:19] <jamesh> It's almost worth creating a non-ext3 filesystem to store the revlib
[07:20] <jamesh> (maybe mounted via loopback, if you don't want to mess with partitions)
[07:20] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  autofocus the searchtext field when the bug listing page is loaded (patch-2048: brad.bollenbach@canonical.com)
[07:22] <bradb> when fl-cow gets into ubuntu, maybe i'll try out some hard link fu with baz
[07:22] <jamesh> fl-cow?
[07:23] <jamesh> ah.  copy on write
[07:23] <bradb> right
[07:23] <bradb> daf seems to use it with success with baz hard link trickery
[07:23] <jamesh> bradb: just use an editor that breaks links on save
[07:23] <jamesh> :)
[07:24] <bradb> i'm already grasping at my sanity as it is
[07:24] <bradb> :P
[07:24] <jblack> jamesh: If only it were that simple. All of your tools need to break hardlinks 
[07:24] <jamesh> I should see if using --link speeds up the pending-reviews/ page
[07:24] <bradb> jblack: /exactly/ :)
[07:24] <jamesh> since it only touches the tree with baz and rm
[07:24] <jblack> btw, yreah. putting revlib on something else like reiser is a good idea. just lvm a 4-5 gig partition for it. 
[07:26] <jamesh> I suppose reiser isn't too bad an idea, since it doesn't matter if the data gets trashed :)
[07:26] <jblack> In five years of heavy reiser use, I've had one serious problem.
[07:26] <jblack> No. two.
[07:27] <jblack> when it breaks, it does tend to break badly though.
[07:27] <jamesh> that's including or excluding hardware related problems?
[07:27] <bradb> 2 x 5 = 10 (years shortened lifespan)
[07:28] <jblack> both were software. 
[07:28] <jamesh> jblack: okay then.  that's two more than I've run into with ext2/ext3 then.
[07:29] <jblack> Yeah. I've never had a massive software ext failure
[07:29] <jamesh> anyway, ~ 2 catastrophic failures in 5 years is no problem for a revision library (which is just a cache)
[07:30] <jblack> btw, one of the failures was a unintentionally hand-wiped partition table. ;) 
[07:32] <jblack> but yeah. I'd try it for .arch-cache, your revlib, /tmp, various odds-n-ends where you could see performance benefits but wouldn't feel bad if the data went away.
[07:32] <jblack> Night. 
[08:04] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=SteveA]  fix bug and task page titles to be 1. consistent, 2. alphabetize well, 3. be better microcontent (i.e. lose the word 'Editing ...'). some other trivial fixes that would have been merged separately already if pqm didn't break. (patch-2049: brad.bollenbach@canonical.com)
[08:36] <SteveA> morning
[08:37] <SteveA> lifeless: how's the pqm hanging?
[08:39] <lifeless> SteveA: I broke the config last night
[08:39] <lifeless> SteveA: but other wise, much improved I think
[08:40] <SteveA> cool
[08:40] <SteveA> i'll try a merge
[09:33] <sabdfl> morning
[09:34] <sabdfl> stub: does staging have the branch you tagged off for production on tuesday?
[09:35] <stub> sabdfl: I havn't selected the production patch level yet. Staging just runs head.
[09:35] <stub> Currently running head as of about 7 hours ago
[09:35] <sabdfl> stub: there is some major issue with anything related to distro's, is it a known problem?
[09:35] <stub> Nothing that I'm aware of
[09:36] <sabdfl> https://staging.ubuntu.com/distros/ubuntu/hoary/
[09:43] <sabdfl> this is odd, i cant reproduce the staging bug on my local machine at all
[09:45] <sabdfl> bradb-away: if you get this, please ack
[09:56] <SteveA> mpt: ping
[09:57] <stub> sabdfl: That page is broken because DistroRelease.architectures fails with more than one DistroReleaseArchitecture. I tracked it down for debonzi last night. I don't know if he has a fix in for review or not.
[09:57] <stub> (because the orderBy clause is stuffed)
[09:59] <mpt> SteveA: pong
[10:00] <SteveA> mpt: on linkifying.  what is most useful to me for adding it to DPoT is not algorithms as such, but test cases 
[10:00] <mpt> ok
[10:00] <SteveA> i develop this kind of thing in a test-driven way 
[10:01] <SteveA> and test cases are the best way to ensure that it comes out the way it should, and that any bugs or changes are clearly communicated and dealt with
[10:01] <SteveA> so, can you stick some test cases on the DPoT page
[10:01] <SteveA> and, then i
[10:01] <SteveA>  'll add linkfying to that work
[10:01] <mpt> sure, thanks
[10:02] <SteveA> jamesh: thanks for the input on the linkification thread.  I must say though, I think the thread's been missing the point, in the sense that it's been about exchanging regexes rather than examples / test cases.
[10:03] <mpt> oh daf
[10:04] <SteveA> i think the problem occured because kiko developed a proof-of-concept patch to linkify text
[10:04] <SteveA> but rather than using this as merely a proof of concept, it became elevated into "the solution"
[10:04] <sabdfl> stub: that fix definitely needs to land in production :-)
[10:05] <SteveA> even though the real thing that lands will look substantially different, because it needs to be integrated into the DPoT sequence of transformations
[10:05] <jamesh> SteveA: I suppose so.  Do we have a page on the wiki for linkification?
[10:05] <SteveA> mpt is going to add examples to DisplayingParagraphsOfText
[10:06] <SteveA> and i'll implement it as part of that
[10:06] <jamesh> I could probably whip up a few test cases
[10:06] <SteveA> if we need linkification in other kinds of presentation, then we'll generalize later
[10:06] <SteveA> i just want it working for paragraphs of text to start with
[10:06] <SteveA> jamesh: that would be helpful.  can you co-ordinate with mpt about what he is doing?
[10:07] <jamesh> okay.
[10:07] <SteveA> i was thinking about this last night, and i know just how to integrate it with the DPoT code which Bjorn reviewed, which should land in pqm any minute
[10:10] <daf> mpt: ?
[10:10] <mpt> daf: Did the language selector work for you before you landed it?
[10:11] <daf> SteveA, jamesh: I'd like not to have any branches getting stale while I'm away, so I'd like to get them merged today if possible
[10:11] <daf> mpt: yes
[10:11] <daf> mpt: I've found a bug in it since
[10:11] <daf> mpt: which is awaiting review
[10:11] <mpt> is it reported?
[10:11] <SteveA> daf: so, do you have things that need instant review?
[10:11] <mpt> daf: https://launchpad.ubuntu.com/malone/bugs/964 ?
[10:12] <daf> SteveA: a quick review would be very much appreciated
[10:12] <daf> I have three branches pending review
[10:12] <daf> two small, one large
[10:12] <sabdfl> mpt: can we discuss menu layout?
[10:12] <mpt> sabdfl: sure
[10:12] <daf> menus, prefs page fix, import fascism
[10:13] <mpt> daf: the problem I have with it is that I can't see any languages
[10:13] <daf> the import fascism one is mostly trivial, but with one or two things which are not thrown in
[10:13] <SteveA> daf: are they up to date on jamesh's revew helper page?
[10:13] <daf> SteveA: yes
[10:13] <sabdfl> mpt: in zermatt we said the menu system would look like this:
[10:13] <daf> mpt: hmm, that bug is not familiar
[10:13] <SteveA> daf: i'm looking at the menus one
[10:13] <daf> mpt: is it a CSS bug?
[10:13] <sabdfl>  - a major facet-selector in the top bar
[10:13] <daf> SteveA: great, thanks
[10:14] <sabdfl>  - up to 5 tabs for the current context and facet
[10:14] <sabdfl>  - an actions portlet containing actions for the current context, irrespective of facet, as well as
[10:14] <mpt> daf: not sure yet
[10:14] <sabdfl>  - actions for the current context, and facet, that don't qualify to be tabs
[10:14] <sabdfl> right?
[10:14] <sabdfl> SteveA: ^?
[10:14] <mpt> sabdfl: sounds right
[10:15] <sabdfl> ok
[10:15] <sabdfl> the current page layout is a good start
[10:15] <SteveA> the   - an actions portlet containing actions for the current context, irrespective of facet,
[10:15] <SteveA> is not part of the menus system at present
[10:15] <SteveA> could be added straightforwardly.  well actually...
[10:15] <SteveA> it is there
[10:16] <SteveA> under a different name, for a different purpose
[10:16] <SteveA> so anyway...
[10:16] <mpt> ExtraFacetMenu?
[10:16] <SteveA> yeah
[10:16] <SteveA> sabdfl: i have a question and need some clarification 
[10:16] <sabdfl> mpt: now let's talk layout
[10:17] <SteveA> actually, it isn't clear to me how to ask the question.
[10:17] <sabdfl> i envisaged that the facet selectors would be a tight, distinctive tab-like cluster, two-layered (up and down), probably to the right of the top bar
[10:17] <SteveA> so instead, keep going, and if the menus system doesn't accommodate what you and mpt need, i'll fix.
[10:17] <mpt> daf: the box ends up being 20px high, and I can't see why
[10:17] <sabdfl> in the current page style, i would have them occupying both the lightblue and the dark blue lines, to the right, in a block, with the current facet highlighted
[10:18] <mpt> sabdfl: hmm, there's two problems with that
[10:18] <sabdfl> the tabs i imagined would go where you currently have the facets
[10:18] <mpt> (1) as I think I mentioned in Zermatt, that only works when you have an even number of facets
[10:18] <sabdfl> that would make it tighter
[10:18] <sabdfl> no, there can be a blank facet
[10:18] <sabdfl> bottom right
[10:18] <mpt> and (2) it causes jumping tabs, as featured in the Interface Hall of Shame
[10:19] <sabdfl> jumping tabs?
[10:19] <SteveA> mpt: why do they need to jump?
[10:19] <mpt> because if it's going to look like a tab, the current facet has to go at the bottom
[10:19] <mpt> otherwise it's disconnected from what it's being a tab for
[10:19] <SteveA> mpt: think of a set of selection buttons on an old radio
[10:20] <sabdfl> stub: in the final landing of the new distrorelease translations pages, there's a cronscripts/update-stats.py
[10:20] <mpt> see the multi-row tabs in Windows (e.g. MS Word's prefs)
[10:20] <SteveA> they are individually in or out
[10:20] <SteveA> not really "tabs".  that's the mental image i got from mark's description just now
[10:20] <mpt> SteveA: sure, hence the term "radio buttons" :-)
[10:20] <SteveA> classic 1950s space craft controls...
[10:20] <Kinnison> Morning
[10:21] <mpt> Kinnison: How soon does cprov usually get in?
[10:21] <sabdfl> stub: could you arrange for that to run every few hours, please?
[10:21] <Kinnison> mpt: He tends to get in around 12:30 UTC
[10:21] <stub> sabdfl: sure. When did it land?
[10:22] <sabdfl> thursday morning, with the rest of the prettiness
[10:22] <mpt> Kinnison: Ok, I'll try to wake early to discuss Soyuz menus
[10:22] <Kinnison> mpt: Okay
[10:23] <sabdfl> mpt: i dont think it will be a problem
[10:23] <sabdfl> the facet is the facet, always in the same place
[10:23] <carlos> morning
[10:23] <Kinnison> mpt: I might not be around desperately late because I need to collect a van but I'll do my best to be around
[10:23] <carlos> daf, around?
[10:23] <sabdfl> bradb-away: had her rubbed out?
[10:23] <sabdfl> the tabs are the tabs, always in the same place
[10:23] <sabdfl> nothing's jumping
[10:23] <daf> carlos: yes
[10:23] <carlos> daf, meeting?
[10:24] <sabdfl> the alternative is for us to lump all of this stuff into the actions portlet:
[10:24] <sabdfl>  - facet
[10:24] <sabdfl>  - facet
[10:24] <sabdfl>   - facet
[10:24] <sabdfl>   - facet
[10:24] <sabdfl>  - tabs
[10:24] <sabdfl>  - tabs
[10:24] <sabdfl>  - tabs
[10:24] <sabdfl>  - minor tab
[10:24] <sabdfl>   - minor tab
[10:24] <sabdfl>   - minor tab
[10:24] <sabdfl>  - minor context menu
[10:24] <sabdfl>  - minor context menu
[10:24] <sabdfl> but.. that would become rather long-winded
[10:25] <mpt> yes
[10:25] <daf> carlos: yes
[10:26] <mpt> daf: I think it's that the <div> doesn't have a height
[10:27] <mpt> a height declared
[10:27] <mpt> and it's a float
[10:27] <sabdfl> stub: could you run that script on staging now, and tell me how long it takes to run?
[10:27] <stub> jblack: Do you have a time frame for supporting baz archives on the supermirror with branches containing that CONTINUATION marker? (I don't know what version of baz these appeared in)
[10:27] <daf> mpt: the CSS uses max-height: 20em, IIRC
[10:27] <mpt> daf: Yes, that's a max-height, it's not a height.
[10:27] <daf> hum
[10:28] <daf> it seems to work intermittently
[10:28] <daf> one would think it would default to a minimum height of the natural height of the content
[10:28] <mpt> iz gecko bug
[10:28] <daf> yes
[10:28] <daf> if you could come up with a test case and report a bug, that'd be lovely
[10:28] <jamesh> daf: you could set an explcit height in em's
[10:28] <daf> kthxbye
[10:29] <daf> jamesh: the problem with that is that it looks ugly if you only have 3 items
[10:29] <daf> jamesh: but it would work in this particular case, yes
[10:29] <jamesh> daf: you don't have three items though ...
[10:29] <daf> since there's always going to be many items
[10:29] <daf> we do use the multi-selector in the PO export pages
[10:29] <daf> and they sometimes do have only 3 options
[10:29] <jamesh> daf: the div also needs a solid border
[10:30] <carlos> stub, hi, could you execute again the SQL sentences I gave you yesterday to know the po/pot import status?
[10:30] <daf> jamesh: I'll let mpt be the judge of that ;)
[10:30] <carlos> stub, btw, thanks for the production fix
[10:31] <mpt> daf: the div also needs a solid border
[10:32] <stub> launchpad_prod=# SELECT COUNT(*) FROM POTemplate WHERE rawimportstatus=2;
[10:32] <stub>  count
[10:32] <stub> -------
[10:32] <stub>    102
[10:32] <stub> (1 row)
[10:32] <stub> launchpad_prod=# SELECT COUNT(*) FROM POFile WHERE rawimportstatus=2;
[10:32] <daf> mpt: feel free to [trivial]  that in then :)
[10:32] <stub>  count
[10:32] <stub> -------
[10:32] <stub>  16590
[10:32] <stub> (1 row)
[10:32] <stub> carlos: If you need that regularly, I can cron it.
[10:33] <carlos> ok, so we are fucked, the poimport script is not importing anything...
[10:33] <carlos> stub, that would be a good idea until breezy is imported completely
[10:45] <mpt> SteveA: Did you see http://lists.ubuntu.com/archives/ubuntu-devel/2005-July/008688.html ?
[10:45] <mpt> (I'd ask him to report a bug, but the problem is that he can't report bugs)
[10:45] <SteveA> oh
[10:46] <SteveA> he's calling malone "bugzilla"
[10:46] <SteveA> i don't understand the report
[10:46] <SteveA> hmm
[10:46] <SteveA> okay\
[10:46] <SteveA> maybe i do
[10:46] <SteveA> registration mail isn't reaching the guy
[10:47] <SteveA> that's on production, so that requires looking at production logs to work out if the mail was sent
[10:47] <SteveA> we'd need to know if the mail he registered with is the one he is mailing with
[10:47] <SteveA> and then stub would need to look at the logs
[10:48] <SteveA> stub: have there been any problems with launchpad production sending out mail?
[10:50] <sabdfl> stub: i've added a few more bits to BrazilTopics for you
[10:54] <stub> Nothing I can see in the logs re: problems sending email. At least for the last couple of hours.
[10:55] <Kinnison> stub: are we passing things off to the MTA directly on the appserver, or are we trying to smarthost it out straight away?
[10:56] <stub> sabdfl: The script took about 25 minutes
[10:56] <stub> Kinnison: it goes SMTP to localhost
[10:57] <SteveA> sabdfl: in the add bounty browser code, it raises Unauthorized if there is no logged in user.  is that view protected by a launchpad.AnyPerson permission?  if so, the test and raise of Unauthorized can that be replaced with an assert.
[10:57] <sabdfl> stub: thanks, could we cron that every 12 or 24 hours please?
[10:57] <stub> sabdfl: Yes.
[10:57] <SteveA> stub: Thu Jul 7 05:10:59 CDT 2005  was when the mail   http://lists.ubuntu.com/archives/ubuntu-devel/2005-July/008688.html  was sent
[10:57] <sabdfl> SteveA: ok, will clean bount stuff out in due course
[10:58] <SteveA> i'm reviewing a small imports clean up from daf, and noticed this near by.  it does no particular harm as it is, just not squeaky clean.
[10:59] <sabdfl> SteveA: quick questions about the zodb
[10:59] <SteveA> okay
[10:59] <sabdfl>  - would that be a good way for a cronscript to leave behind cached values for the appservers?
[10:59] <sabdfl>  - do scripts have access to it?
[10:59] <sabdfl>  - is the api to store/retrieve items in the zodb documented anywhere?
[11:00] <Kinnison> stub: so it's getting rid of the mails ASAP to a proper MTA, that's good
[11:00] <SteveA> it is not a good way for a cronscript to leave behind cached values for the appservers
[11:00] <SteveA> because we're using the zodb just for browser session information
[11:00] <SteveA> and there is one zodb storage per app server process
[11:01] <daf> SteveA: https://launchpad.ubuntu.com/malone/bugs/1303
[11:01] <daf> seems bug mail is lagged
[11:01] <SteveA> affinity is used to keep a browser always hitting the same app server
[11:01] <Kinnison> When are we moving to www.launchpad.net ?
[11:01] <stub> SteveA: Can't see anything in the logs with that email address
[11:02] <SteveA> stub: thanks.  any other ideas based on the report http://lists.ubuntu.com/archives/ubuntu-devel/2005-July/008688.html  ?
[11:02] <sabdfl> SteveA: would the best way to cache system-wide value be to create a LaunchpadCache table with a single row?
[11:02] <SteveA> sounds like the cleanest way to me
[11:02] <sabdfl> or name/value paired rows?
[11:02] <SteveA> what kind of value?
[11:02] <SteveA> a blob?  an int?
[11:03] <stub> SteveA: The usual - user error, browser cache problems. We could try doing the request using that email address and see what happens. 
[11:03] <sabdfl> true, i guess it will just have to have a lot of columns, though i only care about int's at the moment
[11:04] <SteveA> maybe cleaner to use a specific table for each type of caching
[11:07] <stub> Blech. We can do it with multiple columns, but I've seen what that approach looks like after 6 months of extensions...
[11:08] <stub> Stick with just ints for the time being, and if we need to refactor it later we can.
[11:09] <stub> sabdfl: I suggested a LaunchpadCache (id serial, name integer, updated timestamp, value integer) table to Daf/Carlos originally
[11:09] <SteveA> 'name' from a DBSchema? 
[11:09] <stub> Yup
[11:10] <daf> stub: I was going to go with that, but sabdfl had the idea of calculating them at startup time in a utility, which means you don't need to have to worry about persistent storage
[11:10] <daf> the first page load is slow, but it's fine after that
[11:11] <stub> Which makes detecting slow pages on staging problematic ;)
[11:11] <daf> true
[11:12] <daf> I guess we do restart production a fair bit
[11:12] <daf> which means that users will still get a very slow page fairly often
[11:12] <stub> cron is better. Any query with response times measured in seconds rather than milliseconds doesn't belong in the web app.
[11:14] <daf> fair enough
[11:20] <stub> lifeless: PQM is hung
[11:23] <SteveA> mpt: can you invite the universe "bugzilla" reporter to come onto #launchpad and be helped to log in here?
[11:23] <mpt> ok
[11:28] <mpt> done
[11:29] <daf> Keybuk: you should know better
[11:30] <Keybuk> than?
[11:30] <daf> oh, wait
[11:31] <daf> mpt: it's not Keybuk, is it?
[11:31] <Keybuk> huh?
[11:31] <mpt> daf: No, someone called Frans Cool
[11:31] <Keybuk> daf: what are you waffling on about?
[11:32] <stub> Email seems pretty screwed on production. I'm not seeing log messages and stuff isn't appearing in the queues.
[11:33] <SteveA> stub: do you need an elmo?
[11:33] <stub> I don't think messages are getting that far.
[11:34] <SteveA> oh, so they're getting lost in the launchpad 
[11:34] <mpt> Kool, rather
[11:35] <SteveA> stub: do you need assistance looking into this, or can i go and get lunch?
[11:37] <stub> I'll have a look. Messages are going out SMTP just fine, so things are being lost internally.
[11:37] <daf> ah, that's why dilys is not announcing bugs reliably
[12:08] <Kinnison> jamesh: thanks for that review, it looks great. I'll ask celso to do as much of what you asked as he can before we merge today
[12:12] <sabdfl> cheers all
[12:12] <sabdfl> great work, launchpad team, i think it's really coming together nicely
[12:12] <sabdfl> mpt: please could you play with the thoughts i laid out for the top bar?
[12:12] <Kinnison> have fun in HEL sab
[12:12] <Kinnison> see you in SC
[12:12] <sabdfl> the tabsl should go in nicely where the facets are currently if the facets shunt to the right
[12:13] <sabdfl> stub: looking fwd to seeing the next production update, it should be looking very slick
[12:14] <Kinnison> hey elmo.
[12:15] <elmo> hi Kinnison 
[12:15] <daf> I need to go out for a bit
[12:15] <daf> back later
[12:35] <carlos> stub, I'm improving Rosetta's poimport script and I'm adding support to use config files
[12:35] <carlos> stub, which one should I update? default/launchpad.conf ?
[12:35] <carlos> stub, anyone else?
[12:36] <stub> carlos: staging/launchpad.conf would be good too for when I get those things running on staging. I like to configure the production config myself though.
[12:36] <carlos> ok
[12:36] <carlos> which one is used with tests?
[12:37] <stub> default/launchpad.conf in the <canonical testrunner> section
[12:37] <carlos> stub, there are also staging[1-4]  directories ...
[12:37] <carlos> what about them?
[12:38] <stub> carlos: I should remove them - they were being used for load balancing testing
[12:44] <carlos> ok
[01:19] <carlos> SteveA, I have a friend that wants to blog about launchpad's wiki now that it's open
[01:19] <carlos> SteveA, is it ok or should wait for an official announcement?
[01:54] <carlos> SteveA_, did you see my question about launchpad's wiki?
[02:00] <BjornT> anyone know how I can select distinct BugTasks (using BugTask.select()), while ordering on, for example, Bug.id?
[02:01] <BjornT> if I set distinct=True, it complains that Bug.id is not in the select fields
[02:01] <SteveA_> carlos: no
[02:02] <carlos> carlos SteveA, I have a friend that wants to blog about launchpad's wiki now that it's open
[02:02] <carlos> carlos SteveA, is it ok or should wait for an official announcement?
[02:02] <SteveA_> BjornT: that's a good question for andrew, once he gets back next week
[02:04] <BjornT> SteveA_: yeah. i was hoping that someone else would know. but it can wait until next week.
[02:04] <SteveA_> carlos: i would prefer waiting for an official announcement, but if your friend is keen she (or he) should go ahead.  the wiki has been opened in a bit of an ad-hoc manner.  i'd like to check out with kiko what policies we need on there.
[02:04] <carlos> ok
[02:07] <SteveA_> BjornT: i recall that spiv did some work in that area before, and i'm kind of surprised you're having a problem with it
[02:09] <carlos> SteveA_, distinct=True fails under some conditions, perhaps this is one of them
[02:10] <carlos> at least I remember that spiv said that
[02:34] <salgado> stub, around?
[02:34] <stub> salgado: Yup
[02:35] <salgado> do you remember the name change widget we discussed?
[02:36] <stub> salgado: Yup
[02:37] <salgado> so, I'm stuck in a problem: 
[02:37] <salgado> I can see at least two things that I want to validate
[02:37] <salgado> 1) If the name follow the convention (no spaces, starting with a letter, etc)
[02:37] <salgado> 2) if the name is not already used by someone else
[02:38] <salgado> but as we can specify only one constraint in our schema I can't see how to have validators for these two things
[02:39] <stub> And there is a reason you can't combine them into a single constraint 1) The name is not already in use and follows conventions ?
[02:40] <bradb> morning
[02:41] <bradb> mpt: not sure if somebody later responded to your comment, but there was mail to the list about the intermittent mail failures *goes to read morning mail*
[02:42] <salgado> stub, then the validator function would have to receive a third argument, which is the current name
[02:43] <salgado> stub, and unless I make this function raise some exceptions, I will not be able to tell, for sure, what was the problem (if the names was already in use or invalid)
[02:44] <stub> I don't see what the difference between needing two validators and using a single validator. If you validate 'name not in use by someone else' then you either need to pass the current username in or pick it up from context somehow.
[02:46] <SteveA_> what does a validator get in order to do its job?
[02:46] <SteveA_> it's validating new input into a field
[02:46] <SteveA_> so, it should have access to the new input, and to the field
[02:46] <SteveA_> the field should be a bound field, of course, and so give access to the current value
[02:46] <salgado> stub, sorry, I'm not following you
[02:47] <salgado> SteveA, AFAICT a validator function will get only the input value
[02:47] <SteveA_> salgado: the issue is not that you need two separate validators.  it is that you need to get certain information to a validator.
[02:48] <SteveA_> salgado: can you point me at a validator, and i'll take a look
[02:48] <salgado> SteveA, launchpad.interfaces.person.valid_person_name()
[02:48] <stub> The problem you said you had was "we can specify only one constraint in our schema I can't see how to have validators for these two things". The solution to that is you just have a single validator that performs both functions. 
[02:49] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  Fix bugs 1284, 1285 - no links to product releases from product or productseries (patch-2050: morgan.collett@canonical.com)
[02:49] <salgado> but as it is now, I can't perform the second validation in a validator function, because it doesn't get the old value
[02:49] <SteveA_> salgado: i will look at the validation infrastructure and tell you what you can do
[02:50] <stub> the validator has access to the context I think, which is the field. You might be able to pull the initial value from the field, or traverse back to the object the field was generated from.
[02:50] <stub> (Which beats cheating and pulling it from the Launchbag
[02:50] <SteveA_> which would be wrong
[02:51] <SteveA_> oh,and i need to make the fascist forbid use of the launchbag in database code
[02:51] <salgado> yep. /me requested that to Andrew. :)
[02:52] <stub> This isn't database code - it is browser code
[02:52] <salgado> stub, the validators I'm aware of have access only to the input value. nothing else
[02:52] <stub> urgh.... actually it *is* database code :-(
[02:53] <SteveA_> i think it's a valid database constraint
[02:53] <SteveA_> it doesn't depend on the current person
[02:53] <SteveA_> just the current value of the field
[02:54] <salgado> agreed
[02:56] <stub> salgado: Vocabularies get context. If you model your control on a Choice you can use the Choice validation, which simply asks the Vocabulary.
[02:57] <SteveA_> yeah
[02:57] <SteveA_> to do this with a normal constraint, you need to jump up a stack frame
[02:58] <SteveA_> inspect the bound field
[02:58] <stub> (Note that a vocabulary does not have to represent a finite set. All our existing Vocabulary instances implement IIterableVocabulary. The base vocabulary instances don't require it)
[02:58] <stub> Yech!
[02:58] <stub> Bad Steve!
[02:58] <SteveA_> that, or implement a TextField subclass to support this
[02:59] <SteveA_> overriding _validate
[02:59] <SteveA_> that is probably the best way to do it, if the vocabulary stuff doesn't work out
[02:59] <SteveA_> just implement a PersonNameField
[03:00] <SteveA_> class PersonNameField(TextField):
[03:00] <SteveA_>     def _validate(self, value):
[03:00] <stub> That would be cleanest
[03:00] <SteveA_>         TextField._validate(self, value)
[03:00] <SteveA_>         # salgado's validation goes here
[03:01] <salgado> this way it would first call the user-specified validator (the constraint argument) and later my validation?
[03:01] <SteveA_> stick it in interfaces/person.py, but don't include it in the __all__
[03:01] <SteveA_> yes
[03:02] <SteveA_> and, you get the current state from 'self'
[03:02] <SteveA_> and the new state from 'value'
[03:03] <salgado> but I'd like to make this widget generic enough so it can be used for things that have a unique name other than a person
[03:03] <SteveA_> do we have any uses for this yet?
[03:04] <salgado> I can see uses for products/projects/polls at least
[03:04] <SteveA_> i think you should do this for person now
[03:04] <SteveA_> and then make it generic once you have it working well for person
[03:04] <SteveA_> let's actually get it into production for Person first
[03:05] <SteveA_> or at least, on staging
[03:05] <salgado> looks like a plan. I'll do this
[03:05] <SteveA_> i am not aware of any specs or open bugs that require it for other things right now
[03:05] <SteveA_> but i'm sure we can generalize it easily enough
[03:07] <stub> salgado: You could make it generic by using a Vocabulary to say 'is this name in use', or by adapting self to something that provides a function to say 'is this name in use'
[03:07] <stub> salgado: So it could be refactored easily once you get the basics working
[03:08] <SteveA_> and once we get a standard IFooSet base
[03:08] <SteveA_> it may be that "is this name in use" or "get thing with this name" will be a standard api
[03:09] <SteveA_> in which case, you'd just give it an interface that extends IContentObjectSet
[03:10] <SteveA_> hi david
[03:10] <salgado> thanks SteveA and stub. :)
[03:11] <SteveA_> various people i know who speak some french were impressed with the example of shining wit you explicated yesterday.
[03:11] <salgado> stub, btw, I need to bother you some more: is there anything missing for the karmacache updater cronscript to be run?
[03:11] <ddaa> SteveA_: hu?
[03:11] <stub> salgado: Someone with a better memory to do the rollouts?
[03:11] <SteveA_> the french version of spoonerism taken to the Nth degree
[03:12] <salgado> stub, heh. thanks
[03:12] <ddaa> SteveA_: there must be a slight desync...
[03:13] <SteveA_> "choix dans les dates" and all that
[03:13] <ddaa> SteveA_: the contrepteries I remember mentioning yesterday were quite ordinary...
[03:13] <SteveA_> they caused a snigger or two in lithuania
[03:13] <SteveA_> but really, i just wanted an example to say "shining wit" in that context.
[03:13] <SteveA_> s/example/opportunity/
[03:13] <daf> :)
[03:14] <ddaa> ah!
[03:14] <daf> maybe you can help me, Steve
[03:14] <daf> I'm debugging a test failure
[03:14] <SteveA_> daf: what's up
[03:14] <ddaa> you evil bastard
[03:14] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=salgado]  some cleanup of calendar templates (patch-2051: mpt@canonical.com)
[03:14] <daf> so, there's a page on PublishedPackageSet
[03:15] <daf> and the view class for this page calls .query() on self.context
[03:15] <SteveA_> ddaa: it's the standard british response to a mention of spoonerism ;-)
[03:15] <daf> PublishedPackageSet implements IPublishedPackageSet
[03:15] <daf> and IPublishedPackageSet defines a query method
[03:15] <ddaa> we just call that "l'art de dcaler les sons"
[03:15] <daf> but the page test fails with a ForbiddenAttribute error
[03:16] <ddaa> I'm not totally clear on why the salinity of female organs is that important... but nevertheless
[03:17] <daf> aha
[03:17] <daf> I think I know what it is
[03:17] <SteveA_> your colloquialisms go over my head
[03:17] <SteveA_> daf: it sounds like it should work.  so, i guess something is amiss in the configuration.
[03:17] <ddaa> "l'art de dcaler les sons", that's self-referential
[03:18] <daf> SteveA_: the <securedutility> was missing an <allow>
[03:18] <SteveA_> "secaler" is to make dry?
[03:18] <SteveA_> daf: aha
[03:18] <stub> salgado: It is very noise. I'm seeing lots of:
[03:18] <stub> Exception exceptions.AttributeError: "'NoneType' object has no attribute 'cache'" in <bound method Transaction.__del__ of <sqlobject.dbconnection.Transaction object at 0xb723ef6c>> ignored
[03:18] <stub> Exception exceptions.AttributeError: "'NoneType' object has no attribute 'cache'" in <bound method Transaction.__del__ of <sqlobject.dbconnection.Transaction object at 0xb719a04c>> ignored
[03:18] <daf> SteveA_: thanks for rubber ducking :)
[03:18] <SteveA_> stub: i have a fix to that coming
[03:19] <SteveA_> stub: it's part of my "rip parts out of sqlos"
[03:19] <ddaa> "dssaler" is to purge from its salt (as in sailing equipment)
[03:19] <SteveA_> ddaa: you can stop there
[03:20] <ddaa> I know you are familiar with the rest of it :)
[03:20] <ddaa> I can go with only explaining the non-dirty bit
[03:22] <SteveA_> stub: basically, rather than returning None under these circumstances, the connection descriptor will return a dummy transaction that has a dummy cache
[03:23] <salgado> stub, please don't go to sleep. the karmacache updater just triggered a bug
[03:24] <ddaa> random thought...
[03:25] <ddaa> did you guys considered compressing page (as in eliminating all non-significant whitespace, comments and other cruft) before sending them on the wire?
[03:25] <stub> salgado: I can purge the KarmaCache table. Probably best.
[03:25] <salgado> stub, please do so then
[03:26] <stub> Done
[03:26] <salgado> https://launchpad.ubuntu.com/errors/showEntry.html?id=1120828917.60.850024609079
[03:26] <salgado> I'm sure I have a test for that
[03:26] <SteveA_> ddaa: why bother?
[03:26] <SteveA_> ddaa: gzip content transfer encoding will do that
[03:27] <lifeless> SteveA_: either CE or TE, there is no CTE.
[03:28] <SteveA_> i obviously meant "we can GZIP the CONTENT for TRANSFER ENCODING" ;-)
[03:29] <lifeless> SteveA_: TE is very sparsely supported, for a number of reasons, and CE is seriously problematic for others - browser support has been heinous - such as send a CE gif to a netscape 4.x and crash it
[03:30] <SteveA_> i'm pretty sure that firefox <--> apache will gzip stuff
[03:31] <SteveA_> slashdot does it.  i just looked there with firefox
[03:31] <elmo> not opportunisitically it won't
[03:31] <lifeless> SteveA_: apache 2 has a replace mod_gzip of its own, the original mod_gzip guys who I did some work with are not very positive about it. The 1.3 mod_gzip will work fine with firefox yes - but you need to consider the impact of non compliant proxies (like the majority of soho ones) :[
[03:31] <elmo> but you can configure apache to do it (e.g. www.ubuntu.com does)
[03:31] <SteveA_> and it's doing gzip content encoding of the page
[03:32] <lifeless> one of the nastier things about CE is that it fucks with the content - is a gzip CE on a tar.gz meant to give you a tar on disk ? Its semantically unclear.
[03:33] <SteveA_> my point is, i think we should turn on gzip encoding for our pages, before we look at stripping whitespace from our pages
[03:33] <SteveA_> pages are identified by their mime type
[03:33] <lifeless> SteveA_: sure.
[03:33] <SteveA_> lifeless: when are you writing http 2.0 ?
[03:33] <lifeless> SteveA_: heh.
[03:34] <lifeless> SteveA_: there likely won't be a 2.0. There may be a 1.2 if the current errata gets big enough.
[03:34] <lifeless> the extension mechanism in 1.1 does work well - see dav et al.
[03:35] <daf> there's an "et al"?
[03:37] <SteveA_> daf: you need a t-shirt saying "Daf, pronounced according to RFC 2518"
[03:38] <daf> that's a good idea
[03:38] <daf> it would save a lot of bother
[03:39] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=BjornT]  DisplayingParagraphsOfText (patch-2052: steve.alexander@canonical.com, mpt@canonical.com)
[03:41] <SteveA_> wow, that took its time
[03:42] <daf> perhaps PQM is just backlogged
[03:42] <daf> it would be nice to be able to see the PQM queue somehow
[03:42] <ddaa> lifeless: where is that code you wanted me to look at about archive locations?
[03:43] <carlos> debonzi, Kinnison 13:11:38 ERROR   FMO courtesy of TROUP & TROUT inc. on gadfly (1:1.0.0-8ubuntu3)
[03:43] <carlos> ?
[03:43] <ddaa> lifeless: I guess you meant "code I want you to write"
[03:43] <daf> carlos: that's a gina error
[03:43] <carlos> I know
[03:43] <carlos> but I don't understand the error ;-)
[03:44] <daf> FMO being the technical term
[03:44] <daf> for when something or other happens to a source package
[03:44] <debonzi> carlos: it means that when tring to insert the binarypackage for gadfly the sourcepackage was not found
[03:45] <carlos> oh, ok
[03:49] <SteveA_> debonzi: did you see daf's message about broken searches
[03:49] <SteveA_> ?
[03:51] <debonzi> SteveA_: not yet..
[03:51] <debonzi> SteveA_: will take a look now
[03:56] <stub> 13:13:08 ERROR   FMO courtesy of TROUP & TROUT inc. on python-kde3 (3.11.3-1) 13:13:08
[03:56] <stub> WARNING Sourcepackage python-kde3 (3.11.3-1) not found for python2.3-kde3 (3.11.3-1)
[03:56] <stub> debonzi: Do either of these actually deserve to be WARNING or ERROR? We have rather a lot of them...
[03:58] <SteveA_> stub: does "direct delivery" mean non-transactional ?
[03:59] <stub> SteveA: It is transactional. It means email is delivered as part of commit rather than queued, which slows down pages that trigger emails.
[03:59] <debonzi> stub: Well.. personaly I think it could be WARNING... since it is just telling that a binarypackage could not be imported because gina could not find a binarypackage to it.
[03:59] <debonzi> sorry
[03:59] <debonzi> stub: a sourcepackage to it
[03:59] <SteveA_> stub: do we run queued mail delivery on staging in any way at all?
[04:00] <dilys> New Malone bug 1306 filed on product FOAF by Guilherme Salgado: PersonSet.createPerson should produce nicer exceptions than IntegrityError
[04:00] <dilys> https://launchpad.ubuntu.com/malone/bugs/1306
[04:00] <stub> debonzi: So can we fix it so it doesn't happen? We need to shrink the output Gina sends - if they are actual problems that we need to fix, they should stay high level. If we just have to put up with them, they should become INFO or DEBUG.
[04:02] <stub> Or maybe they should stay warnings and we run gina with -qq and only output ERROR messages.
[04:04] <SteveA_> this sounds like the kind of information that the owner of the buildds will want to know
[04:05] <debonzi> stub: I believe it happens in two cases: 1) The sourcepackage is not available on archive; 2) It is on archive, was imported into launchpad, but the binarypackage info has some problem on the SOURCE field and gina can't define the sourcepackage. The first one I think we can do nothing. The second one, we could try to improve the sourcepackage lookup but I don't know precisily how to do that.
[04:06] <debonzi> SteveA_: agree.. I think it will be a problem for all the packages that build-depends on this one that could not be imported.
[04:06] <stub> ok. So it sounds lilke the FMO one becomes an INFO or DEBUG and the WARNING stays the same
[04:06] <stub> or both waning...
[04:06] <stub> probably both warnings...
[04:10] <stub> debonzi: Let me know if you do any work on gina today and I'll give her a run tomorrow against staging.
[04:10] <bradb> stub: trying to customize SinglePopupWidget like:
[04:10] <bradb>         <browser:widget
[04:10] <bradb>            field="sourcepackagename"
[04:10] <bradb>            class="canonical.widgets.popup.SinglePopupWidget"
[04:10] <bradb>            extra="tabindex=1" />
[04:10] <bradb> i get this exception when viewing the page:
[04:10] <bradb> ...
[04:11] <bradb>     *  Module zope.app.form, line 91, in __call__
[04:11] <bradb>       instance = self._widget_factory(*args)
[04:11] <bradb> TypeError: __init__() takes exactly 4 arguments (3 given)
[04:11] <debonzi> stub: sure.. does she still stoped on the createPerson problem?
[04:11] <bradb> stub: i can customize a TextWidget in the same way just fine though (no errors, autofocus Just Works, etc.) any ideas?
[04:11] <SteveA_> bradb: i guess the SinglePopupWidget doesn't except extra args
[04:11] <stub> debonzi: That was the last run I have tried. I got tied up with other stuff today.
[04:11] <SteveA_> bradb: probably a simple signature change
[04:11] <bradb> SteveA_: its base class has an extra attribute
[04:12] <bradb> SteveA_: the extra arg is actually vocabulary
[04:12] <stub> bradb: I don't know if the extra attribute is wired up or was ever working. Feel free to fix it ;)
[04:12] <bradb> (i.e. the arg that the __init__ expected but didn't get is vocabulary)
[04:12] <debonzi> stub: right.. no problem.. I saw it happens once and was a problem with Upper case letters on emails.. I fixed that.. will check why is happening again.
[04:13] <stub> debonzi: When did you fix it? Am I running an old version?
[04:13] <bradb> ItemsWidgetBase.__init__'s sig is:
[04:13] <bradb> def __init__(self, field, vocabulary, request)
[04:13] <bradb> i don't understand why it expects both field /and/ vocabulary
[04:14] <debonzi> stub: I don't believe so.. IIRC was just before I ask you to merge my branch into your
[04:14] <bradb> stub: would hacking SPW's __init__ to be self, field, request be horrid and wrong?
[04:14] <stub> ok.
[04:15] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=jamesh]  testrunner improvements (?) (patch-2053: stuart.bishop@canonical.com)
[04:15] <salgado> you guys better bring warm cloathes when comming to Brazil. this place is getting quite cold. 
[04:15] <stub> bradb: I can't remember what it is supposed to be - I've forgotten how all that stuff works ;)
[04:16] <salgado> s/cloathes/clothes
[04:16] <stub> And nobody wanted the conference in Bangkok!
[04:20] <bradb> salgado: how cold?
[04:21] <salgado> bradb, 10 degrees sometimes
[04:21] <salgado> the problem is that we get this inside the office
[04:22] <daf> stub: I did!
[04:31] <cprov> salgado: buddy, stop crying ! buy some descent closes or work outside, under sun ;) in the common world sense *BR HASN'T COLD WEATHER* 
[04:33] <bradb> heh
[04:37] <SteveA> so, i'm leaving sunny warm lithuania for 3 weeks to go to sub zero brazil?
[04:38] <stub> Ahh stuff it. You guys can go to Brazil. I'm going to Bangkok and attending via IRC :)
[04:39] <salgado> we have a swedish that's here for 7 months and he's complaining about the cold
[04:40] <debonzi> salgado: hey.. stop telling lies :)
[04:40] <morgs> SteveA: your DisplayingParagraphsOfText landing is great, but it puts &lt;p&gt; and not <p> in my product page...
[04:40] <salgado> the problem is that we don't have heating stuff in houses and offices (we don't need them in 95% of the days in a year)
[04:40] <cprov> salgado: don't trust those half-swedish people ;)
[04:40] <SteveA> morgs: did you use the 'structure' keyword?
[04:40] <morgs> SteveA: no, I'll try that
[04:41] <salgado> okay, okay. I gave my advice
[04:41] <SteveA> page templates automatically escape stuff
[04:41] <salgado> now I'm going to make some tea, so I can hold the cup to get my hands warm
[04:41] <morgs> SteveA: Aah... that works.
[04:41] <SteveA> you need to say tal:replace="structure foo/fmt:..."
[04:41] <SteveA> cool
[04:41] <morgs> Nice, thanks very much
[04:44] <SteveA> morgs: one thing to note
[04:45] <SteveA> soon it will be linkifying too
[04:45] <morgs> SteveA: hmm?
[04:45] <morgs> SteveA: OK
[04:45] <SteveA> so note if there are any places you don't want that
[04:45] <morgs> OK
[04:48] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=SteveA]  add addLanguage/removeLanguage to IPerson, pagetest for the Rosetta prefs page (patch-2054: daf@canonical.com)
[04:48] <daf> ooh
[04:51] <salgado> SteveA, do you think I can review daf's menus branch? (I'd like to do it because I was reading about the menus yesterday and this seems like a good oportunity to see some code of it)
[04:51] <salgado> of course, there's the problem that I don't know too much about them
[04:51] <daf> salgado: Steve already did it this morning :/
[04:52] <salgado> oh. :-(
[04:52] <salgado> I haven't went through my launchpad-reviews folder yet
[04:52] <salgado> I should have done so
[04:52] <SteveA> salgado: nothing stopping you from looking at it
[04:52] <daf> yes, Steve's right
[04:53] <salgado> indeed. I was definitely going to use that as example when doing the menus for foaf
[04:54] <daf> stub: oi, you forgot to put a status/[@DATE@]  on your cronscripts branch
[04:54] <cprov> salgado: the same for soyuz, I guess
[04:54] <daf> (I've added them now)
[04:55] <morgs> SteveA: Are we supposed to use fmt:url for all urls?
[04:55] <stub> ta
[04:55] <morgs> I see some portlets have it and most don't...
[04:55] <SteveA> morgs: no
[04:55] <daf> Steve is going to add a feature which is going to remove the necessity for the _parent_url hacks I added
[04:55] <daf> so that part is not a great example of menuing
[04:55] <SteveA> morgs: use it for urls to objects within launchpad
[04:56] <morgs> OK
[04:56] <morgs> Well, that's still *most* URLs in portlets etc...
[04:57] <salgado> stub, what patchlevel are we running in staging?
[04:58] <stub> salgado: 2047. Should I push the upgrade button?
[04:59] <daf> stub: is it big and red?
[04:59] <stub> Of course. 
[05:00] <daf> with a plastic flip-back cover and two keys?
[05:00] <salgado> stub, that (supposed) fix is already there, then. :-(
[05:02] <salgado> stub, that problem you saw with gina (the IntegrityError) was raised recently? (I mean after the upgrade to patch-2047)
[05:02] <stub> salgado: Oh.... gina is running her own branch because the recent changes arn't in rocketfuel yet.
[05:03] <stub> Looks like she is only up to 2011
[05:04] <salgado> hmmm. then if you cherrypick patch-2042 into it that problem should be fixed
[05:04] <stub> No need to cherry pick - I'll just sync it.
[05:04] <salgado> debonzi, ^^
[05:05] <salgado> in the last 20 lines is the answer to your email. :)
[05:05] <debonzi> salgado, cool.. thanks
[05:15] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=salgado]  clean up templates with names starting with 'c' (patch-2055: mpt@canonical.com)
[05:16] <salgado> everytime I see dilys name in yellow I think it's my branch that get merged... but no, it's someone else's branch which I reviewed. :-(
[05:19] <carlos> salgado, ;-)
[05:20] <salgado> and again... it's not my turn on pqm. 
[05:20] <salgado> come on pqm, I have some things that I need to merge here
[05:41] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  Switch production to directDelivery temporarily (patch-2056: stuart.bishop@canonical.com)
[05:42] <ddaa> well, I have two merges queued and soon a third...
[05:42] <ddaa> so you guys do not be too impatient :)
[05:51] <ddaa> morgs: it's entirely unclear whether that is parallelisable...
[05:51] <ddaa> Clearly, running the test suite, should be parallelisable.
[05:51] <ddaa> But we still need to have only one merge checked at a time.
[05:52] <ddaa> morgs: btw, while you are here :)
[05:52] <morgs> Well at least a faster machine...
[05:53] <ddaa> not sure that would help that much, in test suites I'm familiar with, a lot of time is spent on i/o and explicit waits (to work around bugs in cvs).
[05:54] <ddaa> clearly a faster maching would help for running Keybuks test of the form "test that 2+2 = 4"
[05:54] <ddaa> dunno what is the bottleneck for launchpad tests...
[05:56] <morgs> Oh well, let's see how well the LP team scales, especially in deadline season!
[05:56] <ddaa> morgs: in series +edit pages where the rcs is svn, the page is initially loaded showing (empty) cvs details even though the dropdown has SVN selected. One has to reslect SVN so the JS will show the svn details.
[05:57] <ddaa> Are you aware of that bug, or should I file it?
[05:57] <morgs> That is new to me, please file it.
[05:57] <ddaa> Okay. Will do.
[06:03] <dilys> Merge to rocketfuel@canonical.com/launchpad--production--1.24: Update production mail config (patch-5: stuart.bishop@canonical.com)
[06:17] <dilys> New Malone bug 1309 filed on product Registry by David Allouche: +source does not show svn details on load, mouse action required
[06:17] <dilys> https://launchpad.ubuntu.com/malone/bugs/1309
[06:17] <ddaa> morgs: here it is
[06:30] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  Fix bugs 1284, 1285 - no links to product releases from product or productseries (patch-2057: morgan.collett@canonical.com)
[06:38] <morgs> ddaa: thx
[06:59] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  Add KarmaActionName to dbschema.__all__ and add a distinct to IKarmaActionSet.selectByCategoryAndPerson() (fix https://launchpad.ubuntu.com/malone/bugs/1260). (patch-2058: guilherme.salgado@canonical.com)
[07:10] <sivang> Kinnison: then go get some rest :-)
[07:11] <Kinnison> sivang: tempting
[07:11] <Kinnison> sivang: fairly soon I'll be able to stop for the weekend
[07:21] <Luciph3r> re-salve
[07:29] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  RDF formatting changes per bug 1248 (patch-2059: morgan.collett@canonical.com)
[07:35] <Kinnison> hey brad
[07:36] <bradb> hey Kinnison 
[07:37] <Kinnison> time for rest and then fridge moving
[07:37] <Kinnison> ciao
[07:43] <jbailey> bradb: *poke*
[07:43] <bradb> ouch
[07:57] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=SteveA]  another round of import fascism and other cleanups (patch-2060: daf@canonical.com, morgan.collett@canonical.com)
[07:59] <daf> last I checked, traversers.py importing from DB and about 15 imports of things not in __all__
[08:00] <SteveA> many of the cases of importing from outside __all__ that i have seen have been when module A imports N from module B
[08:00] <SteveA> module B has N in its __all__
[08:01] <SteveA> then module C imports name from module A
[08:01] <SteveA> rather than from module V
[08:01] <SteveA> rather than from module B
[08:03] <sabdfl> hey lunchpadders
[08:03] <sabdfl> salgado: ping
[08:04] <salgado> sabdfl, pong
[08:04] <sabdfl> salgado: hi
[08:04] <sabdfl> i'm finally getting to work through foaf
[08:04] <sabdfl> cleanup an ui
[08:04] <sabdfl> some initial feedback:
[08:04] <sabdfl> generally great work, thank you!
[08:04] <sabdfl> you've made too much use of interfaces
[08:05] <sabdfl> IPerson and ITeam really don't need to be distinct
[08:05] <sabdfl> in zcml/person.zcml things were a mess because of this
[08:05] <sabdfl> i'm cleaning it up
[08:05] <sabdfl> all of the portlets really belong on IPerson
[08:05] <sabdfl> and you can use <tal:block condition="context/isTeam"> if you need to
[08:06] <sabdfl> there was a bit of a mess in portlet-team-actions.pt for example
[08:06] <sabdfl> all of that is going going gone
[08:06] <sabdfl> ack?
[08:07] <salgado> I have been blocked in some other stuff. I don't know what the status of the portlets and this stuff
[08:07] <salgado> are you going to get rid of ITeam?
[08:07] <sabdfl> salgado: i haven't gotten rid of it entirely
[08:08] <salgado> I think we need it to have distinct pages for persons and teams
[08:08] <sabdfl> just slimmed it down
[08:08] <salgado> do you have something in mind to manage this?
[08:08] <sabdfl> salgado: there are some pages we need for teams that we don't need for people
[08:08] <sabdfl> but we don't actually need a different team-index.pt
[08:08] <sabdfl> that's goooone
[08:08] <sabdfl> most of the stuf is either:
[08:09] <sabdfl>  - a completely separate page
[08:09] <sabdfl>  - a tal:condition
[08:09] <sabdfl> it's crackful to have a completely differnet set of portlets, duplicated, as you had
[08:09] <sabdfl> now, on the memberships
[08:09] <sabdfl> it's a little confusing ;-)
[08:09] <sabdfl> the interface that you have has
[08:09] <salgado> ahh, I see. store both templates in a single file and choose them with a tal:condition?
[08:09] <sabdfl>  - allmembers
[08:10] <sabdfl>  - active/admin/etc/members
[08:10] <sabdfl>  - teammemberships (which are not the memberships IN this, but OF this, even though the data model does it the other way around)
[08:10] <sabdfl> salgado: yes, because 90% of the details are the same
[08:10] <sabdfl> where there are forms and funcitonality that are UNIQUE to a team, have that in a different +foo page
[08:11] <sabdfl> i'll fix it up and land it next week, i just wanted you to know it's going to be a big patch
[08:11] <sabdfl> but it should look good
[08:11] <sabdfl> and its going quickly, because youve given me a pretty solid base
[08:12] <sabdfl> that's all so far
[08:12] <salgado> nice to know the work I did is at least easy to be refactored. I always work with that in mind
[08:12] <sabdfl> i can see, and appreciate it
[08:13] <salgado> I've been refusing to play with the problems between person/teams pages because we had some discussion about moving teams to another path (/teams) for example
[08:13] <salgado> and I was affraid that I could have to refactor it all over again
[08:14] <salgado> but anyway, thanks for helping me with this. :)
[08:21] <dilys> Merge to rocketfuel@canonical.com/pybaz--devel--0: [r=jamesh]  raise SourceTreeError instead of Exception in ArchSourceTree constructors (patch-36: ddaa@ddaa.net)
[08:26] <sabdfl> salgado: ok, another thing
[08:26] <sabdfl> person.subscriptionPolicyDescription
[08:26] <sabdfl> is going
[08:27] <sabdfl> because you can just context/subscriptionpolicy/title
[08:27] <sabdfl> and /description
[08:28] <salgado> indeed. it used to return a description that was hardcoded instead of using the values from dbschema
[08:32] <sabdfl> it's goooone :-)
[08:32] <sabdfl> salgado: did you deliberately want to show the preferred email of a team, even to anonymous users?
[08:33] <salgado> I don't think that's necessary
[08:33] <salgado> we can show them only to logged in users, as we do with people email
[08:33] <sabdfl> i wondered if that was just accidental :-)
[08:34] <sabdfl> actually, there is some argument to say that a team's email is less sensitive than a person's
[08:34] <salgado> but a team email address is usually something public 
[08:35] <SteveA> it isn't hard to join launchpad
[08:35] <SteveA> so, i don't see a problem with people having to join launchpad in order to see a team email address in the clear
[08:36] <sabdfl> mpt is on such crack if he did these pages!
[08:37] <sabdfl> hey SteveA
[08:37] <SteveA> evening 
[08:37] <SteveA> how's the debconf?
[08:40] <SteveA> sabdfl: did you see the news about mandrake / connectiva's debian derivative ?
[08:44] <sabdfl> SteveA: yes
[08:44] <sabdfl> SteveA: doomed, i think
[08:45] <sabdfl> if they make that their primary distro base, they will each lose big chunks of their user base to us :-)
[08:45] <SteveA> they could become an ubutu derivative, of course...
[08:46] <bradb> salgado: is merging accounts working? if so, i'm going to do a quick usability test with jbailey on it right now.
[08:46] <salgado> bradb, please DO IT. :)
[08:46] <salgado> and yes, it should be working
[08:46] <jbailey> salgado: The bug is still open. =)
[08:46] <salgado> jbailey, which one?
[08:47] <jbailey> 572
[08:47] <bradb> up to 275 lines of jbailey brain dump so far...
[08:47] <jbailey> I think I'm amusing him
[08:47] <salgado> OMG, it's assigned to malone. :(
[08:48] <jbailey> Sure, I was in malone and trying to do the work.
[08:48] <jbailey> Is that bad?
[08:48] <salgado> I always do some triaging in foaf/launchpad bugs
[08:49] <salgado> but never in malone bugs. I wasn't aware of it
[08:50] <jbailey> Ah, sorry for the hassle.
[08:51] <salgado> no worries
[08:51] <salgado> but dude, you have three accounts in launchpad
[08:51] <jbailey> Do I?
[08:51] <salgado> you must be a rock star. all our scripts are creating accounts for you. :)
[08:51] <jbailey> I'm aware of two of them, I guess.
[08:51] <salgado> https://launchpad.ubuntu.com/people?searchfor=all&name=jeff+bailey
[08:51] <bradb> salgado: sssh!
[08:51] <bradb> i'm doing a usability test
[08:52] <salgado> oh, sorry
[08:52] <bradb> :P
[08:52] <jbailey> *lol*
[08:52] <jbailey> One of the accounts has no email address associated with it, apparently.  That should be fun to figure out. =)
[08:53] <jbailey> It'll be fun when this thing starts merging in all my upstream accounts too. =)
[08:54] <salgado> maybe it has email addresses associated. the problem is just that that email is not validated and thus we can't make sure it's yours
[08:54] <jbailey> I think I use 3 different ones.
[08:55] <salgado> I could tell you exactly what is going on with your accounts (why you have them and the reason of the problems), but they closed the backdoor I used to use to access the production database. :P
[08:57] <jbailey> salgado: Apathy tends to overcome anyway.  As long as it's all working, I'm not fussed about how it works.  I spent enough time staring at bugzilla's guts and gnats' guts.  If I never have to hack another bug trackig system, I won't feel unfulfilled. =)
[08:58] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=jamesh]  Fix buttress test coverage. (patch-2061: david.allouche@canonical.com)
[09:00] <salgado> hmmm. I just realized I can do an evil hack that would be of great help for people merging accounts
[09:01] <salgado> bradb, btw, what do you think of make our vocabs show something like "username (No validated email address)" in the cases where a user doesn't have a preferred email?
[09:06] <bradb> salgado: one sec
[09:07] <bradb> hm, i like the intent
[09:07] <bradb> but i confess that i don't think a normal person will know the implications of "No validated email address" without having to do some reflection
[09:09] <bradb> that might be an mpt question
[09:10] <salgado> indeed
[09:16] <bradb> right, we're wrapping up at jeff's, i'm going to dump the braindump to the list when i get home (so people can see what it sounded like right from the users mouth), and then i'll write a proper summary in the next few days
[09:26] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  Bug 130: Multiple paragraphs in DOAP project description field (patch-2062: morgan.collett@canonical.com)
[09:30] <Mez> how do i get access to malone?
[09:30] <Mez> like i have editbugs on bugzilla
[09:38] <Mez> anyone?
[09:39] <dilys> Merge to rocketfuel@canonical.com/cscvs--devel--1.0: [r=spiv]  test suite style fixes, better reaping of cvs server processes (patch-100: david.allouche@canonical.com)
[09:52] <sabdfl> salgado: do you know the branch name that will become production on tuesday?
[09:53] <sabdfl> lifeless: ^?
[09:59] <salgado> sabdfl, no, I don't know.
[10:15] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial]  Bug 1289: Make product text less bold (patch-2063: morgan.collett@canonical.com)
[10:43] <dilys> Merge to thelove@canonical.com/dists--bazaar--1.5: new build (patch-36)
[10:44] <dilys> Merge to thelove@canonical.com/bazaar--devo--1.5: Much simpler and better fix for archive-mirror source choosing (patch-29: Matthieu.Moy@imag.fr)
[10:56] <dilys> New Malone bug 1315 filed on product Malone by Brad Bollenbach: Usability braindump needs to be summarized into a report
[10:56] <dilys> https://launchpad.ubuntu.com/malone/bugs/1315
[10:57] <bradb> kiko-afk: interestingly enough, the EoS seemed pretty much dead obvious to jbailey 
[10:58] <bradb> there was no indication from observing his actions of him wondering things like "does this get added as a comment?", etc.
[10:59] <bradb> i have a feeling that's because he's used the whiteboard before in bugzilla. someone not familiar with bugzilla (and even people that are, that never bother with the whiteboard) may be a little bit less comfortable with that field
[11:13] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=spiv,jamesh]  Auto Buildd System implementation. (patch-2064: celso.providelo@canonical.com)
[11:16] <bradb> dilys: knock knock
[11:17] <ddaa> growing impatient?
[11:17] <bradb> wondering why she didn't spew out the bug report i just filed (i got the bugmail)
[11:17] <bradb> (and she's in the recipient list)
[11:17] <ddaa> dilys seems to drop packets sometimes
[11:18] <ddaa> she did not log one my merges that go through
[11:18] <sivang> bradb: hi :-) when will the ubuntu memebrs section be ready? I get system error on it
[11:18] <bradb> hi sivang. to what URL are you referring?
[11:20] <sivang> bradb: sec, I'll paste it here
[11:21] <sivang> bradb: it works now!
[11:21] <sivang> what the hell happend
[11:21] <Mez> anyone here who can give me the equivalent of editbugs on malone?
[11:22] <bradb> Mez: we don't yet have the functionality to edit more than one bug at a time in malone
[11:22] <Mez> bradb ... so who assigns bugs to someone ?
[11:23] <sivang> bradb: how can I get my name into ubuntu memebrs? I'm an approved one
[11:23] <Mez> who closes bugs etc etc
[11:23] <Mez> sivang - speak to mako
[11:23] <bradb> Mez: on a public distro bug, anyone. on a public upstream bug, only the maintainer/assignee can edit the task
[11:23] <Mez> bradb... so why Cant I do anything to any bug except comment on them
[11:24] <bradb> Mez: can you give me a URL?
[11:24] <Mez> https://launchpad.ubuntu.com/malone/bugs/1201
[11:25] <bradb> Mez: what do you want to do from this screen?
[11:25] <Mez> well, prefereably mark the bug as fixed / similar
[11:25] <bradb> Mez: what have you tried so far?
[11:26] <Mez> I cant see anywhere to change the status
[11:26] <bradb> Mez: can you tell me a bit about where you're attempting to do this? what are you expecting to be possible at this point?
[11:26] <Mez> ok
[11:27] <Mez> I've just found where to change it
[11:27] <bradb> ok :)
[11:27] <Mez> you click on the bit under needs fixing in
[11:27] <Mez> grr
[11:27] <Mez> thats not very self explanatory
[11:28] <bradb> Mez: how would you have preferred or expected that to have worked?
[11:28] <sivang> oh god, I'm only now reading the news about the foundation
[11:28] <Mez> somewhere more intutive... or labelled "change the status" or somethign
[11:29] <bradb> Mez: right. i'm glad you mentioned that this confused you. there's been enough users that have brought that to my attention now to indicate that it's a high-priority usability fix we need to make.
[11:29] <bradb> s/there's/there have/
[11:29] <Mez> lol - I'm glad it's not just me then :D
[11:32] <SteveA> jamesh: ping
[11:32] <sivang> bradb: https://launchpad.ubuntu.com/distros/ubuntu/breezy/+members <== again gives an error
[11:33] <sivang> SteveA: true, I already tried earlier :-)
[11:40] <bradb> sivang: sorry dude, that's outside my area of lp knowledge. i'll file a bug for you though so that the right person sees it.
[11:42] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: [r=kiko]  simple clean up and little fixes (patch-2065: daniel.debonzi@canonical.com)