=== kiko [~kiko@200-206-134-238.async.com.br] has joined #launchpad === salgado [~salgado@200-206-134-238.async.com.br] has joined #launchpad [12:37] Merge to rocketfuel@canonical.com/launchpad--devel--0: changed bug assignment statuses to the more clearly-named New, Accepted, Rejected and Fixed to overcome usability problems experienced while testing (patch-814) === salgado_ [~salgado@200-206-134-238.async.com.br] has joined #launchpad === kiko_ [~kiko@200-206-134-238.async.com.br] has joined #launchpad === salgado_ [~salgado@200-206-134-238.async.com.br] has joined #launchpad === kiko [~kiko@200-206-134-238.async.com.br] has joined #launchpad [12:56] Ouch, that 
 change on bug messages is horrific
=== kiko_ [~kiko@200-206-134-238.async.com.br]  has joined #launchpad
=== kiko_ [~kiko@200-206-134-238.async.com.br]  has joined #launchpad
=== kiko_ [~kiko@200-206-134-238.async.com.br]  has joined #launchpad
=== stub [~stub@dsl-246.248.240.220.dsl.comindico.com.au]  has joined #launchpad
[01:25]  stub: dude, did you look at the 
 change? :)
[01:26]  I merged that into Rocketfuel, didn't I?
[01:27]  yeah, but i mean did you look at it in the UI? it's nasty dude.
[01:27]  because, of course, lines aren't wrapping anymore.
[01:27]  Did some limited tests here. Hmm...
[01:29]  that's why i suggested only for code snippets.
[01:30]  Still got the same problem. I need more CSS-fu I think :-(
[01:30]  stub: with code-only though, you only get the problem when people are stupid, which will happen from time to time, but i don't expect it to be the common case
[01:31]  e.g. i don't think pasting 100-column wide code snippets is the common case
[01:31]  I feel certain that the common case will be forgetting to put in (or not even knowing) the special markup required to flag a code snippet.
[01:32]  in any case, i'm about the land a change to the default search criteria, so that it's New/Accepted. i'm leaving the other widgets alone until i've discussed them more with Mark, because he has some concern about them being difficult to handle when all the packages, products and people come into it.
[01:32]  stub: eh, you can only help the user so much, of course...
[01:33]  if you say "use 
 for code snippets" and they don't, well...
[01:33]  it could even be a little note nearby the textarea
[01:33]  If Malone does not do the right thing, people will use other systems. If we start accepting certain HTML codes, and making people escape them somehow when they want to include them, it will be yet-another-markup language and piss people off.
[01:34]  And we can't fix this with documentation on the web, because of the email interface.
[01:34]  stub: it's not YAML though! it's just only allowing them to use HTML tags that we /can/ allow them to use whilst not creating a security compromise.
[01:35]  stub: email users will already be familiar with the web UI, and those that aren't should expect (and will have to) read a little tutorial on how to format their email correctly anyway.
[01:35]  It is - people will be composing HTML in their text email clients, and god help the poor sods who are sending HTML mail.
[01:36]  and again, we're thinking too far ahead right now. we need some little bit of markup for code no matter which way you look at it, but we don't much care about the incoming mail UI atm, because (i hope) it won't be part of the first release anyway.
[01:36]  Oh - I think I see. For the nice_pre, space should only be converted to   at the start of the line.
[01:38]  what problem does that solve?
[01:38]  I'm thinking ahead to the email interface, because I don't want all our comments to break when we switch it on (because they were assuming fixed width display, and suddenly the system chooses to render them proportional with collapsed whitespace). (Hmm... I guess at least in this case we can run through and add the 'code' marker around the entire existing messages)
[01:38]  It will allow the browser to break lines I think.
[01:39]  stub: dude, i think you're assuming everybody that uses malone uses mutt.
[01:39]  stub: rest assured, this isn't the case. think of all the gnome developers, kde developers, etc.
[01:39]  At the moment, it is not breaking them because I stupidly told it to *not* break them in about the most explicit way possible.
[01:41]  I don't mean text clients (oh... so 90's!).  I mean text mode. All developers I know only send plain text emails (if for no other reason than the flamage they receive on public forums)
[01:42]  stub: i'd be delighted if, when writing an email, all i had to do to highlight some code was:
[01:42]  
[01:42]  x = 1
[01:42]  

[01:42]  the font we had seemed pretty decent, as proportional fonts go
[01:43]  mixing prop with pre-for-code would look fairly professional, like, heck, our wiki.
[01:43]  Yes, And I'd be pissed off at the system if i sent 'You need to do something like '
...
' and the system decided to interpret y markup, or worse still, only *some* of my markup.
[01:44]  stub: "interpret your markup"??! huh? we wouldn't touch anything inside the 
, obviously
[01:45]  it's verbatim, which you'd expect.
[01:45]  and you'd understand why we do the same thing that other sites do in restricting html tags used for security reasons.
[01:46]  but anyway, gah, whatever, i'm not too arsed. i just hope we can do another rollout today, so that the statuses become more sane and the default search params become slightly more sane too.
[01:47]  stub: if sabdfl actually *likes* the look of all 
 messages though, i'd boggle. :)
[01:48]  Roundup looks like it is formatting the text server side to 80 columns (and preserving whitespace and using a monospace font)
[01:48]  Actually, it looks quite fine here. You need to use a different monospace font that courier ;)
[02:15]  stub: will you be able to push up a new dogfood today?
[02:15]  Yes
[02:15]  great...my patch for default search params should land any minute.
[02:16]  if i implement "Quick Searches" like at http://plone.org/collector, we can basically drop the bugs assigned to, and bug submitted by reports.
[02:16]  implement tomorrow, that is
[02:29]  Sounds good.
=== kiko [~kiko@200-206-134-238.async.com.br]  has joined #launchpad
[02:30]  Get a good collection of default ones in and we won't have to bother with making used-defined quick searches either ;)
=== kiko [~kiko@200-206-134-238.async.com.br]  has joined #launchpad
=== BradB heads out
=== BradB is now known as BradB|away
[03:15]  lifeless: Does arch do anything sucky with line endings like subversion, or does it just leave them the way they were saved?
[03:53]  kiko: So - Malone has this 'select a sourcepackage' requirement
[03:53]  kiko: Unfortunately, there appears to be no way a user can select the correct sourcepackage without knowing the primary key id
[03:56]  kiko: I suspect I either need to make UNIQUE(Sourcepackage.distro, Sourcepackage.sourcepackagename) or somehow only display a 'sane' list of sourcepackages (perhaps only displaying the sourcepackage with a given distro and name that has the latest creation date (which needs to be added))
[03:57]  hmmm
[03:57]  right.
[03:58]  There could be a problem with UNIQUE distro/name because of inherited packages, I think.
[03:58]  this part of the workflow really hasn't been considered yet, so it sucks to be you the first one to have the problem.
[03:59]  you *could* make a select distinct on them -- how do you feel about that?
[04:01]  I can have multiple identical rows in the sourcepackage table, only differing by id. If I only display distinct rows, I need to know which one is 'current' and assign bugs to that, or perhaps I should always use the first one? I'm really not sure
[04:02]  can't people file bugs against old releases?
[04:02]  I personally think that we either need UNIQUE(Sourcepackage.distro, Sourcepackage.sourcepackagename) or refactor the database schema - the situation seems wrong.
[04:02]  kiko: If they can, they have no way of telling the old releases from the new ones at the moment.
[04:02]  It isn't a database issue, it is a UI issue.
[04:03]  (but I suspect the UI issue is caused by the database design, and that this design is causing problems elsewhere too)
[04:04]  Do you know who would know if UNIQUE(distro, sourcepackagename) would break the model? People I've asked all suspect, but nobody can actually tell me a use case.
[04:05]  well
[04:05]  hmmmmmmm
[04:06]  (we might have to move sourcepackage.maintainer into sourcepackagerelease to snapshot this historical information, but apart from that...)
[04:06]  sourcepackagename is merely a normalization table, avoiding duplicating the package name in the sourcepackage table.
[04:07]  Yer - pointless optimization IMO but I havn't pushed it too hard ;)
[04:07]  the issue is that you can have multiple sourcepackages with the same name but representing different packages 
[04:08]  so you could have a web browser called firebird and a database called firebird
[04:08]  however I do think that you can't have firebird the browser and firebird the database in the same distribution as it would, well, not work, right?
[04:09]  That is what I think. If anything, the issue would be that if Ubuntu had firebird-the-browser in warty, and firebird-the-database in hoary.
[04:09]  That might be our pathalogical use case?
[04:10]  (If so, it indicates to me that sourcepackage should be related to distrorelease rather than distro)
[04:10]  I'm not sure if the Manifest causes trouble - it isn't documented so I'm not sure about it.
[04:12]  The other Malone alternative might be to assign bugs to a (distro, sourcepackagename) or a (distrorelease,sourcepackagename) instead of to a sourcepackage.
[04:13]  Hmm... if that *is* our pathalogical use case, we might need to prevent it from happening anyway because an Ubuntu user upgrading that package might get a nasty surprise ;)
[04:47]  exactly
[04:48]  I think over a whole distro you need the sourcepackagename to be unique.
[04:48]  you'll need mark to confirm, though, because none of this is complicated unless we consider derivative distros, and that's where my knowledge endgs
[04:48]  ends
[04:49]  I really don't like sourcepackagename very much and I've said it often -- I don't think it brings us anything at all 
[04:50]  I need to dig up a database design book which explains why sourcepackagename is wrong - I've gotten too used to relying on my intuition and not having to rationalize my decisions to anyone else ;)
[04:53]  Mark seemed to think the existing design on sourcepackage was required for some reason but was unable to come up with a use case - suggested it was discussed at the conference but I was hoping to have the UI fixed before then ;)
[04:55]  yeah.
[04:55]  so the use case you have is the user is trying to say in what package he's encountering the bug?
[08:01]  lifeless: pqm hung
[08:01]  elmo: pqm hung
=== lifeless [~robertc@dsl-78.1.240.220.rns01-kent-syd.dsl.comindico.com.au]  has joined #launchpad
[09:12]  lifeless: pqm is hung
[09:13]  fixed
[09:37]  Merge to rocketfuel@canonical.com/launchpad--devel--0: made New and Accepted the default statuses in the bug listing search (patch-815)
[09:47]  hey stub
[09:48]  stub: sourcepackagename is partly because a lot of the actual pointers in the real world are to sourcepackagename, not to a specific sourcepackage
[09:48]  the debian bug system, for example, assigns bugs to a sourcepackage name
[09:49]  even if we move sourcepackagename back into sourcepackage, you still have the basic problem that a sourcepackage with a given name is not unique
[09:50]  stub: can i merge the corrected BugMessage refactoring?
[09:50]  I added:
[09:50]  ALTER TABLE Message
[09:50]      ALTER COLUMN id SET DEFAULT nextval('message_id_seq');
[09:51]  yes - go for it.
[09:52]  Keeping sourcepackagename in a seperate table makes sense when you factor in those references I guess (the arguments for become stronger and against less clear anyway).
[09:52]  it's a shitty situation, but we're trying to model a difficult problem
[09:53]  i'm thinking of refactoring Malone to assign bugs to (distro, sourcepackagename) rather than sourcepackage
[09:54]  Yup - that would be a solution. I've just been poking people trying to workout the best solution, and if there is an underlying problem with the data model.
[09:56]  I think we need to come up with the most pathalogical case we plan on supporting - the firebird one above seems pretty good, but I don't know if we want to support that behaviour or prevent it.
[09:59]  Merge to rocketfuel@canonical.com/launchpad--devel--0: nice_pre CSS implementation for dogfooding (patch-816)
=== Kinnison [~dsilvers@host81-153-126-219.range81-153.btcentralplus.com]  has joined #launchpad
[10:24]  Dudes.
=== lulu [~lu@host217-37-231-28.in-addr.btopenworld.com]  has joined #launchpad
[10:35]  morning Kinnison
[10:36]  hey sabdfl 
[10:37]  sabdfl: Assuming kiko and cprov agree; I'd like to have cprov working with me from Monday. Does that sound okay to you?
[10:38]  absolutely
[10:38]  stretch cprov a little
[10:38]  stub: ok, i'm using patch 4-10-0
=== Kinnison puts in the order for the rack
=== Kinnison oils the rope
[10:41]  easy on the quartering
[10:43]  Can I at least draw him?
[10:44]  steady on
[10:44]  he might take that personally
[10:44]  True; I'd best stick to keeping this purely professional
[10:47]  Now PQM is awake again, I'll do a dogfood update. Yell now if people have patches they want rolled out today that aren't yet committed.
=== elmo [~james@82.211.81.249]  has joined #launchpad
[10:54]  morning elmo
[10:54]  sabdfl: I did a very rough time-plan last night; I'm going through it now making sure it seems sane
[11:15]  Merge to rocketfuel@canonical.com/launchpad--devel--0: bugmessage refactoring (patch-817)
[11:20]  sabdfl: Unfortunately every time I think I'm done; I think of another thing to get gina to do :-)
[11:23]  stub: did that bugmessage refactoring make it into the dogfood update?
[11:23]  It will - just shutdown the existing services when I saw the dillys message
[11:24]  thanks!
=== cprov [~cprov@200.158.100.251]  has joined #launchpad
[11:55]  cprov: is Kiko around?
[11:58]  SteveA: congrats on getting the ZODBAnnotations service up and running
[12:01]  thx
=== Kinnison sighs as his time-estimates balloon :-(
[12:03]  with the ftp server, I think we might want to put a try:except: around the callbacks
[12:03]  and log errors at that point
[12:03]  SteveA: sounds like a sensible precaution
[12:07]  stub: I just read the email about a simpler way to restore backups.  Is the "wisdom of the dba" being recorded anywhere other than the mailing list?
[12:09]  Not at present. Something like an FAQ may be appropriate.
[12:10]  Procedures that exist are documented in launchpad/database/schema/README, but that is more for acting-dba's.
[12:10]  Kinnison: no, I think 
[12:13]  Merge to rocketfuel@canonical.com/launchpad--devel--0: bugassignment renumbering (patch-818)
[12:13]  cprov: Any idea when he normally turns up?
[12:15]  Kinnison: sorry, but today I have no idea, maybe within this hour . may I help you ?
[12:16]  cprov: I need to talk with you and him ;-)
[12:17]  cprov: sabdfl has agreed to let me ask for your time on lucille :-)
[12:17]  cprov: Which will give you a chance to see how things work from the other end of the package process in soyuz ;-)
[12:29]  cprov: would you like to take on some of the deeper challenges in the package management system behind soyuz?
[12:30]  sabdfl: yes
[12:30]  Hurrah
=== Kinnison adds the scary-shit to the list of things to give cprov ;-)
[12:31]  cprov: excelle nt
[12:31]  sabdfl: I'm just getting a kind of lost helping SteveA and Brad to have "better output on failed tests" 
[12:31]  you've done a great job on the front end so far
[12:32]  remember all those questions about "how uploads happen" and "what happens when a new package arrives" that I said not to worry about?
[12:32]  now's the time to start thinking about them :-)
[12:32]  Kinnison has made a good start and will lead  this work
[12:32]  you will work for Kinnison on tasks he assigns
[12:33]  he knows exctly what he wants done, and can help you when you get stuck
[12:33]  sabdfl: thanks, but I feel I can do more on it ... just need more "time" (48 hours day would be nice) 
[12:33]  together you two need to get the back-end stuff working for the end of es-conf
[12:33]  sabdfl: great !
[12:35]  cprov: My plan involves getting you into the lucille stuff starting on Monday. That gives you today and tomorrow to finish of the stuff you're working on and hand off anything to other people. Does that sound enough or do you want more time than that? (sabdfl: Do you want cprov to be exclusively on lucille or partially on lucille until es-conf?)
[12:36]  Kinnison: i think lucille should remain your baby
[12:36]  give cprove related tasks with a lower learning curve
[12:36]  to start with
[12:36]  sabdfl: Yeah; my plan had that kind of ramp-up
[12:37]  so, for example, the build system integration
[12:37]  sabdfl: I have a identified quite a bit to do on gina for now ;-)
[12:37]  ok
[12:37]  Kinnison: 2 days to finish my current tasks will be enough
[12:37]  sabdfl: I think the build-system integration is actually quite a deep thing. I have a curve mostly planned out for now ;-)
[12:39]  ok
=== carlos [~carlos@69.Red-80-33-181.pooles.rima-tde.net]  has joined #launchpad
[12:48]  Kinnison: sabdfl: I'm very happy to work on this, let's book a meeting soon to talk about your plans and the targets
[12:48]  cprov: Yes; I'd like to make sure kiko is happy with all this too
[12:52]  Kinnison: let me help you with a simple phone call :)
=== kiko [~kiko@200-206-134-238.async.com.br]  has joined #launchpad
[12:53]  Kinnison: done, in few minutes he will arrive
[12:53]  hi kiko
[12:53]  minutes!
[12:53]  hey everybody
[12:53]  today is "I hate SSL certificates" day!
[12:54]  kiko: To bring you up to speed... sabdfl and I had a meeting yesterday and we decided that it would be good to get cprov on board with me as a lucille developer. cprov is interested in this and we've basically agreed that he will start working with me on Monday. Is this okay with you?
[12:54]  kiko: sorry I should say "seconds" ...
[12:54]  Kinnison, sounds good to me -- cprov has been wanting to get his hands dirty on it for a while already I suspect.
[12:55]  I was actually curious because yesterday you said an extra pair of hands would be good
[12:55]  kiko: Excellent ;-)
[12:55]  I was going to offer but since the topic died out I thought you had reconsidered.
=== Kinnison puts a tick-mark in kiko's b33r column
[01:04]  kiko: ssl certificates are paying for this little gig :-)
[01:05]  Kinnison, tell me more about where lucille is going
[01:05]  sabdfl, jesus, good point, you could give me some hints, openssl is kicking my ass.
[01:05]  hold on, this is really soyuz, not lucille
[01:05]  lucille is one component of soyuz
[01:05]  Mmm.... SSL certificates. Although I did get a $25 amazon gift certificate in thanks for calling Thawte extortionists in a survey. Sorry Mark :-)
[01:05]  lucille manages APT archives for distros - ubuntu and derivatives
[01:06]  sabdfl: Lucille manages a tad more than that to be fair
[01:06]  stub: dude, i think they started that after i left
[01:06]  vrsn
[01:06]  sabdfl: She also manages the queues. She's the *archive manager*
[01:06]  excuses, excuses
[01:06]  what we are talking about is extending cprov's work to include more of the workflow of package management
[01:06]  sabdfl: Indeed; so queue stuff; upload handling etc.
[01:06]  including the web-presented side of it, I expect?
[01:07]  kiko: Yes; I hope so
=== Kinnison doesn't want to have to learn zope
[01:07]  from upload, through build, through publishing, and including offering the package to derivatives
[01:07]  kiko: especially :-)
[01:07]  Kinnison has a really good understanding of how that workflow should look
[01:08]  we need to give him a second pair of hands, and also someone with web / zope flair, so cprov sprung to mind
[01:08]  if this means we can finally fix the "Pending" feature in source package, I want to donate to the effort
[01:08]  kiko: yes it does
[01:09]  sabdfl, today's our first day running ubuntu diskless at async
[01:09]  kiko: ltsp?
[01:09]  we encountered a few tricky issues but all in all it's excellent.
[01:10]  no, ltsp runs apps on the server -- we run apps on the client. it's pure NFS.
[01:10]  can we sanely fold that into hoary as a standard feature?
[01:10]  I'd need to ask salgado, but there are a few package tweaks that would need to be done.
[01:11]  the issue is that what we do is install ubuntu into a directory on the server and export that via NFS
[01:11]  we use a custom-built kernel, and some init.d hacks
[01:11]  I wonder if this would be a "package" to install on the server or something else.
[01:11]  it's currently a tarball.
[01:12]  Sounds like ideally it'd be a debootstrap following by a chroot and an install of a few choice patching packages
[01:12]  (it would be an 800MB package)
[01:12]  Kinnison, let's talk a bit about this in spain, I'd like to package it nicely
[01:12]  s.following.followed.
[01:12]  kiko: make sure you note down to talk about it or I'll forget
[01:12]  sure thing
=== carlos leaves to get lunch
[01:24]  carlos: we have a meeting in 5 minutes
[01:31]  sabdfl: Should everyone with a chinstrap account be allowed to access a launchpad_dogfood backup?
[01:35]  stub: no
[01:37]  elmo: Is there a group I can use? There is a request on launchpad@ to get a copy of the dumps for development work and I either need a drop point for people without accounts on mawson or deny it.
[01:37]  SteveA: I'm here
[01:37]  stub: who needs it who doesn't have an account on mawson?
[01:37]  elmo: I
[01:38]  anyone else?
[01:38]  carlos requested it. I have no idea if there are others.
[01:38]  carlos: congratulations you now have an account
[01:39]  thanks for playing "Lucky Account Lotto"
[01:39]  X-)
[01:39]  Ta elmo.
[01:39]  elmo: thanks
=== debonzi [~debonzi@200.158.100.251]  has joined #launchpad
[01:49]  daf: ???
[01:57]  carlos: I have another meeting later, and other things to do today.  Let's talk anyway.  Daf can read later.
[01:57]  ok
[01:57]  here or #canonical-meeting?
[02:00]  Do bzipped files rsync well?
[02:01]  ok.  Is the rosetta alpha running on the dogfood system?
[02:02]  stub, well, not efficiently, but it works
[02:03]  SteveA: seems like some data is still pending of upload, but I'm not sure
[02:03]  SteveA: I know daf was uploading files already
[02:04]  when we talked about it yesterday, we all thought that it could be done by the end of yesterday.
[02:04]  what happened?
[02:06]  SteveA: I'm not sure, but I think the scripts we have to import the files were not updated with latest changes we hace when moving to the common infrastructure
[02:06]  what, exactly, is left to do?
[02:07]  SteveA: guessing here (I was not able to talk with daf, I left to sleep before he finished). Import the files into launchpad
[02:07]  I think I got an account in mawson today, so I could help now daf 
[02:07]  on this task
[02:08]  ok.  I wish daf were here.
[02:08]  daf: buy yourself a big alarm clock that has no "snooze" button.
[02:08]  :-P
[02:09]  let's assume that the dogfood stuff will be done a bit later today.
[02:09]  ok
[02:09]  next, we have two important things
[02:09]  1. get more people using rosetta
[02:10]  2. the rosetta team needs to lead the rest of launchpad in internationalizing the application
[02:10]  before I went on vacation, I emailed a list of resources on how to internationalize applications in python and zope
[02:10]  did you read these?
[02:11]  not in depth
[02:11]  but I got the idea
[02:11]  did you start to apply what you had learned to the rosetta code?
[02:12]  not yet
[02:12]  I was working fixing bugs more than adding new feature
[02:12]  s
[02:12]  yesterday I started adding new features
[02:12]  this is an important feature for dogfooding rosetta
[02:12]  so I will do it now
[02:12]  I mean, from now
[02:13]  ok, great.  there are three parts to this.
[02:13]  1. start internationalizing rosetta
[02:13]  2. get the pot files into the rosetta dogfood system for translation
[02:14]  3. write up how to do this so that others on the launchpad team can see what they need to do to existing code, and what they need to do with new code.
[02:14]  the rosetta team are the "internationalization csars" for launchpad.
[02:14]  :-)
[02:15]  SteveA: should we add projects to translate as we decide? (outside the list we already were talking about)
[02:16]  you mean in addition to stuff from ubuntu, zope3, plone, zwiki ?
[02:16]  hmm, with all ubuntu resources we have already a big tasks
[02:17]  I was talking about which ubuntu resources should we add
[02:17]  until we could automatice the import
[02:18]   /s/automatice/automate/
[02:18]  okay
[02:19]  the thing to consider is whether you can get more people using rosetta by adding a particular project
[02:20]  ok
[02:20]  and how are we going to translate ubuntu's website?
=== carlos is talking about the content
[02:21]  not sure if it will be handled by rosetta
[02:21]  that doesn't have anything to do with rosetta at this point
[02:22]  ok
[02:26]  SteveA: anything else?
[02:27]  that's it for now, at least until daf turns up and we can talk about the dogfood
[02:27]  ok
[02:27]  keep me informed about how the internationalization stuff is going
[02:27]  I can help out if you have questions
[02:28]  ok
[02:28]  will do
[02:29]  thanks
[02:41]  SteveA: sorry, but I'm not able to find the links you sent about zope i18n, I read them but seems like I forgot to add a bookmark
[02:41]  do you have them around?
[02:44]  I think I found it: http://zope.org/Wikis/DevSite/Projects/ComponentArchitecture/HowToDoI18nAndL10nForZope3/Zope3Internationalization
[02:51]  Merge to rocketfuel@canonical.com/launchpad--devel--0: No more unused imports in soyuz app components. BugAssignmentStatus ajustment. (patch-819)
[03:01]  carlos: I have sent you another copy
[03:01]  SteveA: thanks
=== BradB|away is now known as BradB
[03:04]  morning
[03:07]  Hey brad
[03:11]  SteveA: ok, I know why I didn't found it, it's inside my inbox folder instead of the folder I have with your mails ..
[03:13]  BradB: please, tell me the RIGHT way to set a customized "optionflags" for a set of python tests 
[03:37]  cprov: canonical.functional.FunctionalDocFileSuite has an example of how to do it.
[04:04]  BradB: how is your css knowledge?
[04:05]  carlos: limited
[04:05]  hmm
[04:05]  why?
[04:05]  who knows css in launchpad team?
[04:05]  BradB: we have a problem with css in rosetta
=== Kinnison knows some css
[04:06]  Kinnison: could you look at http://localhost:8086/rosetta/projects/gnome/evolution/evolution-2.0/translate ?
[04:06]  Kinnison: from your local launchpad installation?
[04:06]  is that part of the default data?
[04:06]  we are showing check buttons and they are expanded because some css magic...
[04:07]  Kinnison: yes
[04:07]  you need default data
[04:07]  how do I load default data?
[04:07]  a make inside database/schema should be enough
[04:08]  launchpad/database/schema
[04:08]  okay
=== Kinnison starts a launchpad
[04:09]  user/password?
[04:09]  carlos@canonical.com
[04:09]  test
[04:09]  or foo.bar@canonical.com and same password
[04:09]  okay; I can see the page
[04:09]  look under the language name
[04:10]  that's a check button
[04:10]  woah
[04:10]  that has the same size of the entry text
[04:10]  and you want to know why yes?
[04:10]  well, know why and fix it :-)
=== Kinnison looks
=== carlos [~carlos@69.Red-80-33-181.pooles.rima-tde.net]  has joined #launchpad
[04:14]  Kinnison: my X server died
[04:15]  The problem appears to be that the checkbox is inside a