=== jblack_ [~jblack@mercury.merconline.com] has joined #launchpad === spiv_ [~andrew@fuchsia.puzzling.org] has joined #launchpad === debonzi [~debonzi@200.158.100.251] has joined #launchpad [12:39] debonzi: ping [12:41] whaaaaa [12:42] my bug disappeared :-( [12:42] ah, no, here it is. :-) [12:49] whoop, there it is... === lalo [~lalo@200-096-070-061.paemt7014.dsl.brasiltelecom.net.br] has joined #launchpad [01:02] SteveA: is it a Soyuz or a Launchpad meeting that's happening at 12:00 UTC? [01:08] on monday? soyuz afaik. [01:09] daf: tomorrow is launchpad, on monday, soyuz [01:10] right. [01:12] oh, I see === kiko is now known as kiko-afk [01:26] daf: is there any way yet to run the importer from the web interface? [01:26] I have reason to believe #1935 would only happen in the script and ftest - it seems to be tied to the "zopeless" code in canonical.database [01:27] no, you can't import over the web yet, but it will be imported [01:27] s/imported/implemented/ [01:28] pity - I would like to test this hypothesis, but I don't want to spend an hour hacking traversal just for this :-P [01:30] you might well be right [01:34] ugh [01:34] I'm right :-P [01:34] zopeless is simply discarding values [01:34] the only thing that acutally *happens* on a zopeless setup is an insert, or so it seems [01:34] jblack_, pong === lalo takes a big breath and starts trying to figure it out [01:35] I traced the code [01:35] what happens is this: [01:36] in the adapter code, something like "msgset.sequence = self.len" is executed [01:36] debonzi! Lets fix your problem. :) [01:36] this invokes an SQLObject function [01:36] which sets a value somewhere and also sets a dirty flag on the msgset object [01:37] but it seems that the value is never actually written to the database [01:37] SQLBase is also involved somewhere [01:37] I think I know what might be happening [01:37] stub and I looked at problems with transactions / writing to the database [01:38] there's code in canonical.publishing that deals with this [01:38] by clearing an sqlobject or sqlos connection cache [01:38] and explicitly starting transactions etc. [01:38] This code won't be invoked for a zopeless setup [01:39] perhaps it is needed in this casE? [01:39] oh [01:39] you're talking about it? sorry :-P was looking at the code [01:39] here's what happens [01:40] the "zopeful" setup uses sqlos transaction objects [01:40] get_transaction().begin() [01:40] name = getUtility(IConnectionName).name [01:40] key = (thread.get_ident(), name) [01:40] cache = sqlos.connection.connCache [01:40] if cache.has_key(key): [01:40] del cache[key] [01:40] [01:40] so when an object is marked "dirty", it's inserted in a queue of objects that have to be flushed [01:40] do that at the start of the script [01:41] and get_transaction().commit() at the end [01:41] the zopeless setup doesn't have any similar logic - there is no queue of objects to flush, so when the transaction is committed, there is no way to know what objects must be sync'ed [01:41] (the "queue flush" thing of sqlos basically calls the sync() method of each object in the queue) [01:42] SteveA: I tried putting in a get_transaction().commit() at the end [01:43] (naiively) [01:43] there seems to be, on first read, two possible fixes - either do make a queue of objects to sync(), or don't set lazyUpdates at all [01:43] I think for a script or ftest the second approach may be better suited [01:45] lalo: I need to go to sleep now. Can you send a mail to the launchpad list with what you've found out, after you've done a bit more trying things? [01:45] ok [01:45] thanks [01:45] np [01:45] SteveA: wouldn't adding comments to the bug make sense? [01:46] daf: perhaps. I want spiv and stub to see this. [01:46] then perhaps they should be CC'd to the bug === carlos goes to bed and tries to recover the hours he wasted programming on Powerbuilder instead of sleep since last week [01:46] see you tomorrow [01:47] I think I'll post to the list with a summary of what's going on and an URL to the bug [01:47] carlos: 'nite [01:49] suppose we need a component for this kind of stuff (database, sqlo, sqlos, canonical.database) === lalo does a dance [01:53] lalo: yes, a component would make sense [01:55] removing SQLBase._lazyUpdates makes my tests pass :-D [01:55] yay for being right [01:56] just have to be sure to commit at the end of the script [01:56] ...which we're already doing, so it's ok [02:00] launchpad_test=# select * from pomsgset where sequence = 0; [02:00] id | primemsgid | sequence | potemplate | pofile | iscomplete | obsolete | fuzzy | commenttext | filereferences | sourcecomment | flagscomment [02:00] ----+------------+----------+------------+--------+------------+----------+-------+-------------+----------------+---------------+-------------- [02:00] (0 registros) === kiko-afk is now known as kiko [02:02] lalo: hurrah! [02:03] hmm. canonical.database is in launchpad, so technically I can commit [02:03] not very sure how to proceed in this case :-/ [02:06] who is the right person to poke about the bugzilla component? === lalo decides the list is it :-P [02:07] Steve or Dave can do it [02:10] then the list is it indeed [02:16] SteveA, Hi [02:17] spiv_, ping [02:21] spiv_, I saw that some links in sourcepackage still broken.. I'm gonna to fix it tonight I sent the changes to rocketfuel tomorrow morning.. see u [02:21] s/I sent/and send === debonzi go dinner [02:22] jblack_, you missed him again :-( [02:23] no I didn't. [02:23] that's why he disapeared for awhile right after he came back. I hooked 'em [02:26] ah. [02:26] did you fix it? :) === jblack_ grins === lalo is off for the night - be back in a few hours [02:38] lol === lalo [~lalo@200-102-075-177.paemt7014.dsl.brasiltelecom.net.br] has joined #launchpad === kiko is now known as kiko-afk === stub [~zen@dialup-131.80.220.203.acc05-dryb-mel.comindico.com.au] has joined #launchpad === lalo [~lalo@200-180-185-073.paemt7003.dsl.brasiltelecom.net.br] has joined #launchpad === stubish [~zen@dialup-30.83.220.203.acc06-dryb-mel.comindico.com.au] has joined #launchpad === justdave_ [~dave@24.247.63.44.gha.mi.chartermi.net] has joined #launchpad === justdave_ is now known as justdave === jblack_ is now known as jblack === sabdfl [~mark@wblv-228-55.telkomadsl.co.za] has joined #launchpad === Signon time : Tue Sep 7 09:17:35 2004 === Signoff time : Thu Sep 9 09:51:49 2004 === Total uptime : 2d 0h 34m 14s === warthylog [~warthylog@port1845.ds1-khk.adsl.cybercity.dk] has joined #warthogs === Topic for #warthogs: /join #ubuntu === Topic (#warthogs): set by Keybuk at Tue Sep 7 20:30:22 2004 === #warthogs [freenode-info] help freenode weed out clonebots, please register your IRC nick and auto-identify: http://freenode.net/faq.shtml#nicksetup === warthylog [~warthylog@port1845.ds1-khk.adsl.cybercity.dk] has joined #launchpad === Topic for #launchpad: how's england? wet but soon, I will go back to Wales and how will wales be? probably wet, too === Topic (#launchpad): set by kiko at Fri Aug 27 16:07:21 2004 === #launchpad [freenode-info] why register and identify? your IRC nick is how people know you. http://freenode.net/faq.shtml#nicksetup === Signon time : Thu Sep 9 09:51:53 2004 === Signoff time : Thu Sep 9 09:53:00 2004 === Total uptime : 0d 0h 1m 7s === warthylog [~warthylog@port1845.ds1-khk.adsl.cybercity.dk] has joined #launchpad === Topic for #launchpad: how's england? wet but soon, I will go back to Wales and how will wales be? probably wet, too === Topic (#launchpad): set by kiko at Fri Aug 27 16:07:21 2004 === lulu [~lu@host217-37-231-28.in-addr.btopenworld.com] has joined #launchpad [11:01] Hi guys - anyone know how the Rosetta logo came about? Who made it? and is it from clip art? === carlos [~carlos@69.Red-80-33-181.pooles.rima-tde.net] has joined #launchpad [12:13] morning [12:15] hi carlos === doko [doko@dsl-082-082-140-133.arcor-ip.net] has joined #launchpad [12:51] carlos: the Rosetta server is down - do you know how to fix it? [12:52] no, sorry. I don't have access to it [12:52] daf is the only one with an account in that server and perhaps lalo, but I'm not sure [12:54] I am sure spiv and Stu also have. [12:54] spiv: u around? [12:54] lulu: Just woke up :) [12:54] morning hon! sleep well? [12:55] spiv: would u mind checking the rosetta server mate - it's down and I'd like it available if at all possible. thanks in advance :o) [12:55] I don't think I have an account on it. [12:56] I just tried, and I don't seem to :/ [12:56] lulu: I always sleep well, it's the waking up that's the problem ;) [12:57] mmm - this isn't good - we need to have more than one person who can kickstart it when down....can't rely on only one person. All launchpad team leaders should have access. I'll chat to Stevo. [12:57] spiv: :o) [12:57] SteveA: ping [12:58] daf: ping [12:58] Carlos: how are your graphs looking? === spiv_ is now known as spiv [01:00] meeting in 60 mins right? [01:00] lulu: the graphs are in place, waiting for the changes from Limi [01:00] sabdfl: yes [01:02] carlos: what changes are required from limi? [01:02] lulu: png and css changes [01:02] we are using still my images [01:03] carlos: ok. I'll add that to the to do list. Anything else you need from limi next week on Rosetta? [01:04] lulu: he should do a global review of all UI, It's the bug #1934 [01:05] https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=1934 [01:05] https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=1934 [01:05] carlos: ok - does he have an account on Bugzilla? [01:05] yes [01:05] carlos: good - thank you. [01:07] carlos: as the server is down - I can't see if the warty applications have been added to the home page of Rosetta. [01:07] have they? [01:07] lulu: limi added some code to the templates [01:07] but it's not done [01:07] finised [01:07] grrr [01:08] finished [01:08] wait I will take a screenshot of my local installation [01:08] does that need limi, or can you guys just hard code the links? [01:09] If that's the final UI it will have, we don't need limi [01:09] https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=1932 [01:09] that's the bug report related with that feature [01:10] lulu: and this is the metabug https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=1915 that list all pending things for the Alpha release [01:10] any bug report you add should block that one [01:10] that way we are sure we don't forget anything === lulu just creating a bugzilla account... [01:12] lulu: http://gollum.pemas.net/~carlos/Screenshot-Rosetta.png [01:12] that's the main page now [01:13] ok - the translatable packages in Ubuntu - do we have all of those in the database? [01:14] if not, we need to get them in, with the correct title, descriptions and package names. [01:14] i haven't looked at the bug, but is inputting the data part of it? [01:14] lulu: we are creating the scripts to do it [01:14] carlos: who is? and when will they be done? [01:14] and we need to talk with arch people to fetch the projects from the arch repository [01:15] ok - who's responsible for this task? [01:15] https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=1931 [01:15] I'm creating the script to create persons into launchpad [01:16] so I suppose I will create also that script [01:18] carlos: it's assigned to Daf I see....depends on how many bugs you have, Daf has, Lalo has.....and if he needs to delegate it to you. [01:18] how many rosetta bugs do we have outstanding? [01:19] lulu: all bug reports are assigned by default to Daf [01:19] as soon as we are free, we pick any bug with the NEW tag and change the assgned field [01:20] ok - if you want to take it on, then great. we go live next week..... [01:20] lulu: https://bugzilla.warthogs.hbd.com/bugzilla/showdependencygraph.cgi?id=1915 [01:20] there you will see the status with a graph [01:21] the green ones are the open ones, the grey ones are fixed already [01:22] ok - lots to do....I'll let you get on with it Carlos...hope Daf wakes up soon. [01:24] lulu: ok, but don't worry, some bugs are trivial to fix [01:25] carlos:then lets get them done....running out of time! :o( [01:33] hi [01:34] daf: morning [01:35] daf:hiya [01:35] daf: i tried to call u this morning. jane wants to know where the rosetta logo came from - did u design it? [01:36] lulu: hmm, I think my phone was downstairs [01:36] lulu: I went to bed at 7am, so I might not have heard it annyhow :) [01:36] lulu: yes, I designed the logo [01:37] daf: cool - did u use clipart? [01:37] lulu: nope [01:37] daf: drew it? [01:37] yes [01:38] daf: good - will you get in touch with Jane then - she sent an email to Warthogs. cheers! [01:38] daf: why bed so late/early? [01:38] lulu: it happens to my sleep patterns... I was fixing bugs :) [01:39] lulu: right, hadn't read my mail yet today -- I'll reply now [01:40] daf: good to hear u fixing bugs :o) we have 4 days to go, so we need to squash as many as possible asap. hows; the schedule looking today? [01:40] daf: thanks :o) [01:50] daf: wow... no more plural forms missing error :-P [01:52] carlos: yeah, I finally got around to fixing it [01:53] daf: the po traversal is working now. [01:54] oh, great! [01:54] when we don't have a pofile, I suppose we could export the .pot file, right? [01:54] it fails now [01:54] hmm [01:54] or show only a message? [01:54] what's the URL? [01:54] it's not yet at rocketfuel [01:54] but for instance: [01:54] http://localhost:8085/++skin++Debug/rosetta/projects/gnome/evolution/evolution-2.0/cy/po [01:55] I'm not sure which is best [01:55] that will fail because we don't have the cy pofile (yet) [01:55] by the way: what do you think on having the PO file as an attachment vs. having it inline? [01:55] hmm, in fact, http://localhost:8085/++skin++Debug/rosetta/projects/gnome/evolution/evolution-2.0/cy also fails so we should fix it also [01:55] daf: GTP people prefers them as inline [01:56] like you [01:56] what's your opinion? [01:56] daf: that's an easy change [01:56] I think that you should download it and open with an editor [01:57] but it's long ago since my last active translation, so perhaps I don't have in mind the real user case [01:57] I'm not 100% sure about -- I prefer inline myself, but I don't know what other people like [01:58] I suppose we will know it with the alpha :-) [01:59] :) [01:59] carlos: once you have finished the traversal, do you have other things to work on? [02:00] Choose any bug from the list of pending things [02:00] hi folks. Launchpad meeting here in 1 minute! [02:00] SteveA: hi [02:00] daf: I was thinking on implement the project/product/resource creation script [02:00] #1931 [02:00] hi all [02:01] hiya! === cprov [~cprov@200-206-134-238.async.com.br] has joined #launchpad [02:01] cprov: Hello :) [02:01] spiv: hi === debonzi [~debonzi@200-206-134-238.async.com.br] has joined #launchpad [02:02] Just in time :) [02:02] hi mark [02:03] hi * [02:03] cprov, debonzi: hi. Can kiko make it to this meeting? [02:03] SteveA: of course, just one minute more :) [02:03] ok, thanks [02:03] SteveA, Hi === kiko [~kiko@200-206-134-238.async.com.br] has joined #launchpad [02:04] ok, should we get going? [02:04] by me, bombs away [02:04] let's [02:05] stevea, could you set the stage, then let's have each team describe status and issues [02:05] go ahead steve [02:07] what I'd like to do today is to talk with each team about exactly what the current short-term and medium-term goals for their part of launchpad is === sabdfl [~mark@wblv-228-55.telkomadsl.co.za] has joined #launchpad [02:07] and how they are progressing towards those goals [02:08] what things are standing in the way of progres [02:08] s [02:08] Can we start with the soyuz team? [02:09] I spoke with kiko yesterday about how that is going [02:09] Ok. [02:09] and we're having a meeting on monday to go through the system, as checked in [02:09] and go through all of the soyuz functionality [02:09] but first, [02:09] what are the current short-term and medium-term goals of the soyuz project? [02:10] well [02:10] (short-term meaning pre-sprint, I assume) [02:10] we've got the functionality we discussed at the oxford hackathon laid down [02:11] and we have been producing mockups and implementing them [02:11] how are we doing on the db-to-html mapping? [02:11] something like fire and motion [02:11] fire and motion? [02:11] all pages are intended to be db-backed, and there are very few things left that are stubbed out [02:12] ok, is this accessible on rosetta.warthogs.hbd.com yet? [02:12] kiko: am I right in recalling that you think that all will be DB-backed by the meeting on monday? [02:12] https://rosetta.warthogs.hbd.com/soyuz [02:12] most of the stubbed out information remaining is stuff that hasn't been really discussed or doesn't have db backage yet. [02:13] SteveA, well, certainly not *all* of the content in the pages, but all the content which can be displayed from the database (given our existing database infrastructure) [02:13] ok [02:13] if you look at the checklist and at the pages you'll see there's not a lot left. [02:13] so, on monday, I'd like to go through each relevant database entity, and we'll look at the page(s) that present it [02:13] in that case well done [02:14] as I said yesterday, by the middle of next week, unless we have a trusted domain expert that can guide us into moving the database forward together with the pages, we'd like to be assigned some extra work. [02:14] kiko: so, there are some changes to the database that you want to discuss. Can these be discussed at the sprint? [02:14] they can, but that leaves us with ~ 10 days that could be invested somewhere that needed it. [02:15] sabdfl: how about I get at least one of them to help me with infrastructure? [02:15] good idea [02:15] now [02:15] (actually, kiko suggested it in our meeting yesterday) [02:16] (thanks kiko) [02:16] we need a consolidation / cleanup process that spans the infrastructure [02:16] (y/w) [02:16] I can lead that, but I don't have time to execute it all [02:17] now, medium and long-term we are *really* in need of someone to guide us more closely [02:17] steve, can you map out the areas that need that work for me this afternoon, then I can give the go-ahead on async time for that [02:17] you mean, a package maintainer, a user of souyz [02:18] well, a soyuz user, yes, but someone with a reasonable vision of how everything should fit together and time to spend with us [02:18] sabdfl: I can send you a short bullet-pointed list. Will that be enough? I already have a lot of work planned for this afternoon. [02:18] yes, that's fine [02:18] so far we've been winging it based on what we know about distributions and what we discussed at oxford, but we're running low of fuel already [02:19] sabdfl: ok, willdo [02:19] kiko: we can cover a lot of ground during the sprint [02:19] daf: rosetta passwd? [02:20] sabdfl: great, but we would appreciate someone after that that could be in close contact, do you think we can arrange someone with the cycles for that? [02:20] sabdfl: wartyhoarygrumpy, I think [02:20] kiko: I should be more available from now on. The US leg of my travelling was more disruptive than I'd anticipated. [02:21] spiv: even so, you're not a domain expert. You don't know what a package maintainer needds. [02:21] spiv, problem is we need someone who really can make decisions based on domain knowledge [02:22] that did the trick, thanks [02:22] Good point. [02:22] kiko: the immediate goal is presenting what's in the database [02:22] that's already in its final steps [02:22] we'll look over progress towards that on monday [02:22] elmo and kinnison will get going on archive management stuff at high speed [02:23] soyuz team needs a more distant horizon to work with from there on :-) [02:23] as soon as we are using their new code for archive management we can dogfood ubuntu, which will mean LOTS of users [02:23] kiko: are there any database changes that you need? [02:23] i believe our db is already a nice superset of the existing db management stuff, so that should go quickly [02:23] SteveA, there are some, yes. [02:24] kiko: is there a wiki page, or something like that, listing them? [02:24] sabdfl: when will elmo and kinnison start that? [02:24] daf: is https://rosetta../ working ? I'm just getting blank pages [02:25] daf: same here [02:25] oh, me too [02:25] it was working a minute ago [02:25] SteveA: at the sprint [02:25] SteveA, not summarizing DB changes by themselves, we have a checklist, some wiki bullet items and a couple of email requests. [02:25] great. [02:25] SteveA, we'll summarize them. [02:25] kiko: ok, we can go through those on monday too. [02:26] SteveA: I'm getting some interesting Zope errors on the server [02:26] daf: let's look at it after this meeting [02:26] sure. [02:26] is that everything for soyuz so far? [02:27] i have a question [02:27] what sort of sample data are you guys using? [02:27] Completely hand-crafted. [02:27] SteveA: hmm, restarting the server made it go away -- perhaps it was demo-bogons [02:27] daf: keep the logs [02:27] It would be good to start basing it on actual real data. [02:28] is there anything stopping us from using real data? [02:28] SteveA, well.. is there real data? [02:28] SteveA: logs are always kept [02:28] Do we already have tools for extracting metadata from deb packages, and that sort of thing? [02:28] daf: mail the relevant ones to me please [02:28] I'd guess sourcerer has some of this stuff. [02:29] the sample data is built from what we *think* would be reasonable [02:29] but you have to realize that some of the stuff -- release team, for instance -- doesn't exist anywhere that I know of [02:30] the package side of things could be extracted from ubuntu debs, definitely [02:30] so, a good task starting next week is to get real sample data in there, augmented with made up data where needed [02:30] maybe that's a task for 50% of the soyuz team post-next-week. [02:30] yeah, agreement [02:30] Yep. [02:30] i'm trying to figure out if we can get the system to monitor our archive and automatically try to represent the data in there [02:31] elmo: listening in? [02:32] do you mean monitor, as in "real time", or as in "let's import/sync with the archive from time to time" ? [02:32] that would be awesome, but does keybuk's team have the tools up to speed to give us this data? [02:32] sync from time to time [02:32] phew [02:32] daf, could you please merge into rosetta.warthogs.hdb.com the fix I've sent to rocketfuel [02:32] there's a database used to manage the existing archive, it's part of a set of tools called "katie" that james mostly wrote for debian [02:32] sabdfl: yeah [02:32] debonzi: sure [02:33] daf, thanks [02:33] and james and daniel (silverstone) will write a new set for us [02:33] debonzi: hmm, it says that everything is up to date [02:33] elmo, is the katie db for auckland on auckland? [02:33] no, it's on jackass - auckland is the public mirror machine, jackass is the private master archive server [02:34] daf, realy? I've sent a fix for sourcepackage pages some minutes ago. [02:34] do you think you could send a dump of the db to kiko and me? [02:34] ah, killer [02:34] debonzi: is the merge complete yet? [02:34] daf: Yep. [02:34] yeah, I see it [02:34] daf, I think so [02:34] daf, nice :) [02:35] sabdfl: it's 2.5Mb compressed - shall I make it available via http and send you the URL ? [02:35] sure [02:35] debonzi: is it working? [02:35] thanks elmo [02:35] hmm, no it's broken again [02:35] daf, I've got black page [02:35] s/black/blank [02:36] elmo, url is good. [02:36] last page accessed before it broke was /soyuz/distros/ubuntu/src/warty [02:36] same error as before [02:36] daf: I see what the problem is. [02:36] daf: It was me :) something is broken on SQLObject [02:37] Anything more for soyuz? [02:37] cprov: oops :) [02:38] Let's move on. [02:38] Rosetta. [02:38] daf: the immediate goals for rosetta, [02:38] spiv: can we talk on #soyuz ? [02:38] and how are things progressing towards it [02:38] immediate goal: fix all bugs which prevent the alpha release [02:38] daf: can you give me a status on rosetta first please? [02:38] you can see these here: [02:38] https://bugzilla.warthogs.hbd.com/bugzilla/showdependencygraph.cgi?id=1915 [02:39] cprov: Ok. [02:39] some of those have been fixed, but are waiting on merges to rocketfuel [02:39] daf: the wiki page that describes what "alpha release" means? [02:40] SteveA: good idea [02:40] https://www.warthogs.hbd.com/RosettaAlpha describes our goals for the alpha release [02:40] kiko/sabdfl: sent [02:41] thanks james [02:41] once we have our alpha-critical bugs fixed, we'll have real projects imported into a test server which we'll make available to our testers [02:41] we'll make the test server available as rosetta.ubuntulinux.org [02:42] then, we'll fix any bugs we or our testers find as well as adding functionality for our beta release [02:42] daf: the other day, we were discussing the "import POT/PO -> alter through the web -> export POT/PO" cycle [02:42] SteveA: yep [02:42] where does that stand now? [02:42] it has less bugs in it than it did the other day [02:42] daf: Could we add the beta release date to the wiki? [02:42] what can I do with it? [02:43] you can do all of those things [02:43] I can take a POT file and PO file for ProjectX, and use a script to import it (if I have access to the DB) [02:43] I can take a POT file and a PO file for ProjectX, and upload it to a web form [02:44]