=== elmo [~james@213.151.107.243]  has joined #launchpad
[01:37] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: Fixed sampledata and removed an obsolete assert (patch-1025)
[02:34] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: fix PO template creation (patch-1026)
[03:48] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: many templates links fixes (patch-1027)
=== smurfix_ [~smurf@smurfix.developer.debian]  has joined #launchpad
=== smurfix_ [~smurf@213.151.107.243]  has joined #launchpad
=== SteveA [~steve@213.151.107.243]  has joined #launchpad
=== stub [~stub@213.151.107.243]  has joined #launchpad
[10:48] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: Database patches and Z3 auth workaround (patch-1028)
[11:10] <daf> SteveA: ping
=== smurfix_ [~smurf@smurfix.developer.debian]  has joined #launchpad
=== cprov [~cprov@213.151.107.243]  has joined #launchpad
[11:34] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: Missed Interface Attributes (patch-1029)
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== stub [~stub@213.151.107.243]  has joined #launchpad
[11:53] <carlos> stub: wait, daf just requested the merge (he forgot to do that)
[12:06] <stub> carlos: I just did the rollout. Does daf still have PQM commits going through?
=== salgado [~salgado@213.151.107.243]  has joined #launchpad
[12:12] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: little fixes (patch-1030)
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== stub [~stub@213.151.107.243]  has joined #launchpad
=== cpro1 [~cprov@213.151.107.243]  has joined #launchpad
=== cpro1 [~cprov@213.151.107.243]  has left #launchpad [] 
=== cprov [~cprov@213.151.107.243]  has joined #launchpad
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== sabdf1 [~mark@213.151.107.243]  has joined #launchpad
=== stub [~stub@213.151.107.243]  has joined #launchpad
[02:23] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: bazaar renaming and initial soyuz refactoring for distribution, distrorelease (patch-1031)
=== cprov [~cprov@213.151.107.243]  has left #launchpad [] 
=== cprov [~cprov@213.151.107.243]  has joined #launchpad
=== salgado [~salgado@213.151.107.243]  has joined #launchpad
=== kiko [~kiko@213.151.107.243]  has joined #launchpad
[04:04] <kiko> cprov, yo
=== kiko [~kiko@213.151.107.243]  has joined #launchpad
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== salgado [~salgado@213.151.107.243]  has joined #launchpad
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== kiko [~kiko@213.151.107.243]  has joined #launchpad
=== lulu_ [~lu@213.151.107.243]  has joined #launchpad
=== sabdf1 [~mark@213.151.107.243]  has joined #launchpad
[06:26] <sabdf1> halllaauu
[06:27] <sabdf1> l
[06:27] <sabdf1> l
[06:27] <sabdf1> 1
[06:27] <sabdf1> odd
=== lulu_ [~lu@213.151.107.243]  has joined #launchpad
=== lulu_ [~lu@213.151.107.243]  has joined #launchpad
=== lulu_ [~lu@213.151.107.243]  has joined #launchpad
=== lulu_ [~lu@213.151.107.243]  has left #launchpad [] 
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== elmo [~james@213.151.107.243]  has joined #launchpad
=== sabdf1 [~mark@213.151.107.243]  has joined #launchpad
[08:05] <carlos> sabdf1: is working the wireless from the rooms?
[08:06] <elmo> carlos: is now, yep
[08:06] <sabdf1> carlos: some rooms :-)
[08:06] <carlos> elmo: ok, thanks
=== carlos goes to his room and plans to ask a pizza ...
[08:07] <sabdf1> carlos: could you order me one too, please?
=== elmo [~james@213.151.107.243]  has joined #launchpad
[08:10] <carlos> sabdf1: which room?
[08:10] <sabdf1> 128
[08:10] <carlos> sabdf1: and what do you want?
[08:11] <carlos> wait, I will call you when I order it
=== carlos moves to his room
[08:11] <carlos> later
[08:11] <sabdf1> cool, thanks!
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
[09:03] <carlos> food!!!!!
[09:07] <elmo> dude, what room are you in???
[09:09] <carlos> 133
=== carlos [~carlos@213.151.107.243]  has joined #launchpad
=== carlos builds zope3
[10:05] <carlos> Is interesting to see that zope3 is in hoary :-)
[10:32] <sabdf1> hmm... so when we release hoary, we can start using zope3 instead of crack-of-the-day :-)
[10:34] <carlos> sabdf1: at the moment it's in universe
[10:35] <carlos> and it's not available for ppc
[10:35] <carlos> I had to compile it myself
[10:36] <carlos> grrr
[10:36] <carlos> and the dependencies are wrong
[10:36] <carlos> :-(
[10:37] <sabdf1> so, a small project then :-)
[10:38] <carlos> I suppose that this explains all:
[10:38] <carlos> EXPERIMENTAL PACKAGE. NO UPGRADE PATH FROM EARLIER VERSIONS OR
[10:38] <carlos>  TO UPCOMING VERSIONS PROVIDED UNTIL THE FINAL 3.0 RELEASE.
[10:39] <carlos> but it's a final release 3.0.0-1
[11:01] <carlos> sabdf1: ping
[11:02] <sabdf1> carlos: pong
[11:03] <carlos> sabdf1: what about adding a javascript spell checking to rosetta using something like google suggestions?
[11:04] <carlos> sabdf1: http://www.google.com/webhp?complete=1&hl=en
[11:04] <sabdf1> carlos: do you think it can be done in javascript?
[11:05] <sabdf1> i would think perhaps easier to do it on the server, and display it in the browser window, asking the user to confirm it?
[11:05] <carlos> sabdf1: it's just the idea we had to get the product list with javascript + xmlrpc
[11:05] <sabdf1> right
[11:05] <sabdf1> so the spellcheck happens on the server
[11:05] <carlos> yeah
[11:07] <carlos> I have seen several spellcheckers in javascript already but using cgi or .php files
[11:08] <sabdf1> cool
[11:08] <sabdf1> let's see if we can do that
[11:09] <carlos> ok
[11:52] <lifeless> hey guys.
[11:53] <lifeless> I have a request for  you for bazaar
[11:53] <lifeless> I have a new merge algorithm, which Works For Me (tm).
[11:54] <lifeless> on launchpad it can take up to 30 seconds to calculate where to merge from, but it is able to handle loops, tags from tags, and more, happily.
[11:54] <lifeless> (or at least, it should :)).
[11:54] <lifeless> How do you feel about that being merged into bazaar as is, before optimisation.
[11:55] <sabdf1> lifeless: correctness is more important than performance for us
[11:55] <carlos> lifeless: bazaar is really slow here already and it's a problem with the harddisk I/O
[11:55] <sabdf1> if you think it's stable, merge it in
[11:56] <carlos> so if that don't make it slower
[11:56] <carlos> it's ok for me
[11:56] <lifeless> cool. ok, I'll finish the tests for it that I'd want as minimal coverage, then merge it in. It should make workflow a lot easier for collaborating sub-teams.
[11:57] <sabdf1> lifeless: i think we want more than minimal coverage
[11:57] <lifeless> carlos: yah, I've got optimisation as a massive todo.
[11:57] <carlos> lifeless: that will be really good
[11:57] <lifeless> sabdf1: FSVO minimal. I am very pro testing, as you know.
[11:57] <sabdf1> it's not reasonable to ask the rf team to use crack-of-the-minute bazaar unless you have really, really good test coverage
[11:58] <lifeless> sabdf1: ack.
[11:58] <sabdf1> 30 secs to calculate the merge point, then how long to do the merge?
[11:59] <lifeless> 30 seconds to generate the merge point, then a standard 3-way merge, which you've said is faster than two way anyway.
[11:59] <lifeless> you can turn off the new algorithm with '--star-merge' to the merge command.
[11:59] <lifeless> I won't be merging this tonight no matter what.
[12:00] <lifeless> (just in case you are worrying :))