[12:05] ok, I detected an error in my code, reruning the tests ... [12:12] what was the problem? [12:16] daf: a cosmetic change I did [12:16] it broke the python syntaxis [12:16] and seems like I forgot to test it [12:17] the tests work now [12:17] ah, good :) [12:17] you'll be submitting a merge request, then? [12:17] but it's weird that it caused that big problem... [12:17] yes [12:22] request sent [12:32] Merge to rocketfuel@canonical.com/launchpad--devel--0: Preliminar po/pot import from the web and added a missing FROM (patch-916) [12:32] daf: there you have === carlos goes to see TV [12:33] daf: do you need anything from me? [12:33] not right now [12:33] thanks [12:33] ok [12:34] daf: I know that the current code does not catchs any error. It's a know "feature" ;-) [12:34] I planned to fix it tonight, but the test error took more time that it should [12:34] /s/that/than/ [12:36] do we have a bug open for it? [01:05] Merge to rocketfuel@canonical.com/launchpad--devel--0: add a confirmation message showing bug id after adding a bug (fixes #94) (patch-917) [01:11] Malone bug #94 fixed for package malone: No confirmation of bug ID or success when a bug is filed [01:11] https://dogfood.ubuntu.com/malone/bugs/94 [01:50] [01:50] Night all === stub [~stub@dsl-246.248.240.220.dsl.comindico.com.au] has joined #launchpad === spiv_pants [~andrew@home.waugh.id.au] has joined #launchpad === warthylog [~warthylog@port49.ds1-van.adsl.cybercity.dk] has joined #launchpad === Topic for #launchpad: lunchpad: home of the sandwich artists | fogo na bomba | "qorking along happily, with SteveA egging us on" === Topic (#launchpad): set by sabdfl at Tue Oct 19 11:05:38 2004 === warthylog [~warthylog@port49.ds1-van.adsl.cybercity.dk] has joined #launchpad === Topic for #launchpad: lunchpad: home of the sandwich artists | fogo na bomba | "qorking along happily, with SteveA egging us on" === Topic (#launchpad): set by sabdfl at Tue Oct 19 11:05:38 2004 === debonzi [~debonzi@143.223.62.81.cust.bluewin.ch] has joined #launchpad === elmo [~james@82.211.81.249] has joined #launchpad [09:14] morning [09:14] stub: hey hey hey [09:14] production update time ? [09:14] eh? [09:15] Are there any pending db changes for production? I need to pick a bunch of code updates, would be easier to do a full drop than cherry pick. [09:16] Just the Karma table and some Rosetta po-whatsit table constraints. [09:17] so,.. shall we ? [09:17] Unless the production code needs those changes (doubtful), I'd rather leave the production database at the same patchlevel. [09:18] so, I don't know if the production code will be affected. in production we hae project, product, buttress, sourcesources, so anything theat the UI touches from there will be impacted. [09:20] anyway, you pung. [09:20] Shouldn't be a problem with the tables I mentioned. However - are you using the Z3 auto generated forms, and in particular any of the 'popup' widgets (select-a-person, select-a-product,select-a-sourcepackage) [09:21] (If so, a rollout will be more difficult because the current trunk has a load of full text stuff with scarey database changes, as well as needing a new .deb installed on emperor) [09:22] ah. ok, I'll cherry pick the specific commits I need. [09:22] stub: did you see Kinnison's problems with the locale of the full text seach stuff ? [09:23] stub: also, how's the deployment of roundup going? [09:23] I know nothing about Kinnison's problems [09:24] I haven't heard back from Elmo re: somewhere to install roundup [09:24] roundup ?? [09:25] issue tracker until we develop our own [09:25] like malone ? [09:25] or bugzilla ? [09:25] malone is a bug tracker [09:26] so - you pinged me for something ? [09:27] I was wondering about the cacherevs in the rocketfuel archive and mirroring (in particular, there appear to be two undocumented options in 'baz archive-mirror' that would speed up mirroring). Also about how baz determines what archive format to use, since 'baz make-archive --mirror-from' appears to use tla-format. [09:30] baz make-archive should be creating baz format. does for me. [09:30] dpkg -l bazaar ? [09:31] ii bazaar 1.0 arch revision control system [09:31] (updated from own-built today, as per launchpad@ instructions) [09:32] ok. cat .archive-version for the new archive you've made === stub is freeing diskspace [09:38] Yup - your are right. I repeated the procedure and the .archive-version is baz this time. User error. [09:56] stub: Kinnison was getting an error "ERROR: Can't find tsearch config by locale". I think this is because postgres was running with the locale en_GB. [09:56] stub: the error is described here. http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/docs/tsearch-V2-intro.html [09:59] On a side note, you seem to get all sorts of crazy things happening if you don't run PostgreSQL as locale C (since it starts using locale aware sorting'n'stuff and things go all pear shaped) [10:00] isn't it the encoding that makes more difference than the language? [10:03] encoding describes the stored data, so PostgreSQL can validate that the data is correct (yes - this is valid UTF8), and convert to whatever encoding the client requests. === silbs [~sbsm0084@host217-37-231-28.in-addr.btopenworld.com] has joined #launchpad [10:04] The locale alters the results of functions like sort (I think ) [10:04] So those crazy germans get their stuff sorted the way they like it [10:07] I'll need to go into more depth on this - consensus seems to be 'stick to locale C, and this should have really been the default even if your system locale is set differently', so the fix might be to enforce that rather than have the tsearch2 gumf cope with different locales [10:07] (It crops up on the mailing lists regularly, with the normal end result being some poor sod has to blow away their database, recreate and reload from backup [10:07] won't a UTF-8 locale use Unicode collation order, though? [10:08] Different locales sort the same string differently - in particular, german collates a-z differently to english locales [10:09] ah [10:10] well, as long as the shared testing/production databases uses the correct locale, we shouldn't have any problem, right? [10:11] Using different locales introduces a new variable into the unit tests. [10:12] oh, of course === lulu_ [~lu@host217-37-231-28.in-addr.btopenworld.com] has joined #launchpad === lulu_ [~lu@host217-37-231-28.in-addr.btopenworld.com] has left #launchpad [] [10:45] Morning [10:45] Merge to rocketfuel@canonical.com/launchpad--devel--0: page template improvements; add page template title check (patch-918) [10:53] BradB: ? [10:54] brad is unlikely to be around until ca. 12.30 [11:32] So, anyone here know lots about our use of sqlobject and can tell me where to find an example of how to join two tables where table B has a column A which is a foreign key to A's id column? [11:35] Kinnison: I can probably answer that. === kiko [~kiko@200-206-134-238.async.com.br] has joined #launchpad [11:44] sources = MultipleJoin('DistroReleaseQueueSource') [11:44] builds = MultipleJoin('DistroReleaseQueueBuild') [11:44] look right? [11:45] Yep. [11:45] Sorry, getting distracted by my home ADSL being down :/ [11:45] morning [11:47] You can do TableB.select("TableB.columnA = TableA.id", clauseTables=[TableA] ) [11:48] being able to get at queueitem.sources will do me nicely :-) [11:55] spiv_pants: tell me about how shipit is going === cprov [~cprov@200.158.100.251] has joined #launchpad [11:57] Morning cprov [11:58] hey celsn [11:58] cprov: with respect to the 'performance' angle, we can store a view in the database to extract all the information we want from the logevents table [12:03] Kinnison: kiko: morning [12:04] cprov: another comment. Make the table name singular since the class name in the app will be the table name and an instance of the class is a single row of the table [12:04] cprov: In general table names should be singular [12:04] Kinnison, uhhhh, that's not agreed upon [12:04] kiko: No? [12:04] Kinnison: of course we can, but views cannot perform miracles :), anyway I understand your point [12:05] in my book (SQL FOR SMARTIES) tables are always plural. [12:05] cprov: Hopefully the indexes can perform the miracles [12:05] I'm just contesting the "in general" portion [12:05] you could say "in launchpad" and I could agree [12:05] kiko: I was thinking "in general within the company" okay, "in launchpad...." [12:06] Kinnison: about the singular table name, in our context, I agree === kiko is victimized by standards he did not invent [12:06] kiko: You prefer plural table names? [12:06] SteveA: Well. The script to sync up ids in the shipit db to the launchpad db is close to working as well as it can. That leaves the tool to make the report scripts continue to work as the only other major task. [12:07] Kinnison, yes, certainly [12:07] Right at this second I'm frustrated by my home DSL suddenly being down (I'm at jdub's atm). [12:07] and joe celko knows better [12:07] kiko: I can see arguments either way on the plural vs. singular argument === Kinnison has always used singular and personally believes it to be more correct [12:07] spiv_pants: what about the shipit code? what about having a "new shipit alpha test" server running on mawson? [12:08] singular singular singular [12:08] The shipit code is looking good. [12:08] My testing has run out of problems. [12:08] SteveA: glad we agree on this :-) [12:08] spiv_pants: you're not testing hard enough then :-) [12:08] spiv_pants: I want to see a demonstration of it running on mawson. That way, mako and jane and lu can use it [12:09] Kinnison: any other remarks on "Log System" ? [12:09] SteveA: Agreed. [12:09] spiv_pants: now? [12:09] Kinnison, cprov: did you make any headway into getting the publishing tables merged? [12:11] kiko, Kinnison: it really depends if you see a table as a collection of things or as representing a class of things. Collections can be either singular or plural; plural if they are "countable" things, singular if they are things that you'd commonly refer to by quantity. Classes of things should always be singular. [12:11] kiko: merged? [12:12] SteveA: I always see a table as a class. But then I'm off the OO school of database design [12:12] (which is crackheaded) === kiko runs === Kinnison wonders if many people use the OO capabilities of pgsql :-) [12:12] Kinnison, well, yes. we want to fix the status section of sourcepackage. [12:12] nope, few do. [12:12] Because we are writing an OO application with a relational storage, then our tables "serve" the application, and should be named with the singular. [12:12] kiko: Eh? [12:13] there is much more code in the application than in the database or in database queries. [12:13] lifeless: Which I think is a pity :-) [12:13] kiko: merged ? do you mean the [DBA] request ? there's nothing to merge yet === SteveA moves on to solve the "vi versus emacs" problem once and for all... === lulu__ [~lu@host217-37-231-28.in-addr.btopenworld.com] has joined #launchpad [12:14] SteveA: I'd rather you didn't. I use both [12:14] lu. [12:14] Kinnison, well. [12:14] Merge to thelove@canonical.com/bazaar--devo--1.0: merge in brown-paper bag baz archive format support (patch-70) [12:16] Kinnison, never mind. I was hoping we had a schema laid down for publishing that could be merged at this point.. [12:16] kiko: the publishing schema is already fairly much done [12:16] kiko: Or do you mean inheritance policy? [12:16] Kinnison: it is simple really. Everyone should be using emacs. Except when using vi. Unless they're using both at once. [12:17] SteveA: oooh *illuminated* [12:17] I am not really sharp on the details of what is necessary schema-wise (your master plan is obscure to me) but I *would* like us to be able to say that source package A has release X pending [12:17] You don't know what you mean by "pending" though [12:17] I can tell, because noone knows yet [12:17] This is one of the things we need to discuss very early in Mataro [12:17] we're on the same page :) [12:18] All I do know is that inheritance policy is very very different from publishing [12:18] pending is not and will never be in the publishing tables [12:18] can you afford giving me the "dummy" explanation? [12:18] these terms are just collections of letters to me with no semantic [12:19] visit https://wiki.canonical.com/Lucille_2fBraindump [12:19] that's not the dummy explanation hopefully [12:19] search for "Thoughts on the derivative distro process" [12:19] I've visited it a number of times [12:19] then read "Derivative distro crack" [12:19] and "Use cases for Derivative distributions" [12:20] That is all I know about it because that's the results of talking with sabdfl about it :-) [12:21] I don't *entirely* grasp why this is a problem for "pending". is it the point that you can not tell if a certain distro will *inherit* a certain package from another? [12:21] okay, here's a concrete question that is "dummies" [12:21] does the upload system handle uploads of packages to specific distros? [12:22] An upload is zero or one sources plus zero or more binary package builds uploaded to a distrorelease (and plausibly a distroarchrelease within that distrorelease) [12:23] okay. [12:23] so if you upload a package to a certain distro, is that package not in some visible status "pre-pending, pre-approval, etc"? [12:23] Kinnison: OO databases will always be fringe tech until a standard query language is standardized and widely adopted. The closest I'm aware to this goal is Enterprise Java Beans. [12:24] when a package is uploaded it does into the queue as "unchecked" [12:24] when the package passes preliminary checks it moves into either "accepted" or "new" (or various other states which are unimportant right now) [12:24] an upload in "accepted" gets published and passes into "done" [12:25] Kinnison, would it be reasonable to display "unchecked" on a package page? [12:25] That transition happens within a single run of the queue [12:25] If you really want to work through the queue for a distrorelease then sure. [12:25] IMO it's pretty pointless though [12:25] is it pointless giving feedback that a package is still unchecked in the queue? [12:25] Kinnison: let's have a real case, I'm an pkg uploader, how can I keep track of my just-uploaded package ? tell me the steps til it becomes a current Ubuntu-Hoary-i386 package [12:26] kiko: You can display packages in the publishing tables in "Pending" state [12:26] AN ANSWER! === kiko . o O ( it's going to rain ) [12:27] kiko: That means that the package has been accepted into the distrorelease (I.E. is for publishing) but has yet to be published into the distro [12:27] But currently there's no way to know if a package is pending acceptance into a distrorelease [12:27] E.g. from inheritance or a fresh upload [12:29] Okay, so my multiple joins fail === Kinnison wonders if they have to come last [12:29] nup :-( [12:30] sources = MultipleJoin('DistroReleaseQueueSource') [12:30] builds = MultipleJoin('DistroReleaseQueueBuild') [12:30] what is wrong with those? [12:30] They cause: [12:30] AttributeError: 'LaunchpadStyle' object has no attribute 'tableReference' [12:31] https://chinstrap.warthogs.hbd.com/~dsilvers/queue.py is the entire file [12:31] very very very simple stuff === carlos [~carlos@69.Red-80-33-181.pooles.rima-tde.net] has joined #launchpad [12:33] Kinnison, could we handle the upload 50% at this point? [12:34] kiko: ? [12:35] But currently there's no way to know if a package is pending acceptance into a distrorelease [12:35] E.g. from inheritance or a fresh upload [12:35] could we handle at least the upload case? [12:35] kiko: assume I am a small child and need things explaining to me. What do you mean by "handle the upload 50% at this point" ? === Kinnison adds joinColumn values to his MultipleJoin()s and they work now [12:36] sorry for the noise [12:36] well [12:37] did I misread the comments you made above? [12:37] Kinnison, it would clarify a lot if you exercised answering cprov's question.. [12:37] The database can represent uploads, yes === Kinnison attempts to describe the workflow for an upload then [12:38] give me a moment to commit this pqm merge [12:39] Kinnison: btw, haven't you defined the joinColumn=' ' on MultipleJoin ? [12:41] cprov: see my utterance from 5 minutes ago ;-) [12:41] Right, okay, please bear with me as I go through this process.. [12:41] 1. Ubuntu developer builds the source package [12:42] 2. Ubuntu developer uploads it to the lucille upload server [12:42] 3. this triggers the UploadHandler to take the new upload; validate it and import it into the database and librarian. [12:42] 4. This creates a queue/unchecked entry for the upload [12:42] That is the upload process [12:42] Then we have the queue process [12:42] 1. queue/unchecked is checked and validated. [12:43] 2. The accepted item is moved to queue/accepted [12:43] 3. queue/accepted items have their publishing records made and marked 'pending' [12:43] 4. more housekeeping occurs which is unimportant right now [12:43] That is the queue process [12:43] Now we have the publishing process [12:43] Merge to thelove@canonical.com/bazaar--devo--1.0: merge in brown-paper bag baz archive format support test suite fixes (patch-71) [12:43] 1. The pending publication records are scanned [12:43] 2. The pending files are copied into the archive from the library [12:44] 3. the pending records are marked as published [12:44] 4. The published records are scanned [12:44] 5. Any no-longer-needed records are marked superceded [12:44] 6. The superceded records are scanned [12:44] 7. Any utterly unreferenced records are moved to PendingRemoval and are given a time-to-live [12:44] 8. Any PendingRemoval entries which are now dead are removed [12:45] 9. The on-disk archive files are updated [12:45] That is the publication process [12:45] So the three processes together form the end-to-end chain of events [12:45] Merge to rocketfuel@canonical.com/launchpad--devel--0: Queue tables for Lucille (patch-919) [12:45] The first is triggered by the upload [12:45] the second is a regular event (perhaps every 5 minutes) [12:45] the third is a less often regular event (30 minutes for ubuntu, perhaps every hour, or every day or whatever for other distros) [12:46] Does that make sense to people? [12:46] I'm still reading [12:46] so U4 is a step we could provide feedback on (package has been uploaded but not checked) [12:47] daf: I've read through your recent rosetta emails. great stuff. can you put together the list of the things you need to do next, to improve the translation process? [12:47] U4 is kinda a limbo state [12:47] Particularly the package may get rejected at that stage [12:47] then Q2 perhaps. and Q3 certainly [12:47] well, U4 is nice for keeping track of the upload rate [12:47] After Q3 you can report [12:48] U4 will include making a LogEntry to say about the upload [12:48] that could go into a notices thing? [12:48] Plausibly [12:48] cprov and I will be discussing the LogEntry stuff today [12:48] Px is very very hazy to me [12:49] Kinnison, is Q3 the same as saying the source package is Accepted in the source package page? [12:49] or are we confusing concepts [12:49] Imagine that most of the queue states are entirely housekeeping and you don't tend to see them [12:49] particularly things may pass through many states in a single transaction [12:50] What matters in Q3 is that the publishing record is created and marked as pending [12:50] ah. accepted in the queue. not a packaged accepted in the distro. right? [12:51] Indeed [12:51] s/ged/ge [12:51] THANKS! [12:51] The queue really is just for lucille to track uploads [12:51] where in Px does the inheritance issue show itself [12:51] Nowhere [12:51] inheritance is separate [12:52] (or rather not yet discussed in enough depth to be integrated) [12:55] ok, 1.0.1 baz release should fix the problems reported yesterdayu. === Kinnison stuffs that explanation on the wiki for posterity [12:56] lifeless: debs ready? [12:58] meeting in 3 mins [12:59] Kinnison: ya-huh [01:00] SteveA: workrave wants me to rest-break, I may be a minute or two late :-) [01:00] okay [01:00] I should probably do the same [01:03] has anyone seen these? [01:03] DatabaseException: ERROR: current transaction is aborted, commands ignored until end of transaction block SELECT COUNT(*) FROM EmailAddress WHERE email = 'foo.bar@canonical.com' [01:03] that doesn't look good [01:03] meeting time === spiv_pants gets back from dinner just in time [01:04] all present, say "aye!" or "@1e!" if you're 1337 [01:04] aye [01:04] aye! [01:04] @le [01:05] aye! [01:05] urp [01:05] lifeless: can you look in on the meeting occassionally? [01:05] sure === Kinnison raises his hand [01:06] elmo: can you also look in on the meeting occassionally? [01:06] BradB: ? [01:06] daf: ? [01:06] cprov: ? [01:06] salgado sends apologies. he has an important final exam right now. === lifeless high fives Kinnison [01:07] BradB will be around in 25 mins or so [01:07] SteveA: err, as much as I can - I'm in the DC and my connectivity isn't assured.. [01:07] elmo: I'd think that being in the DC you'd have more connectivity than you can handle! [01:07] no connectivity in the DC ?!?!? [01:07] SteveA, as in *final*, last exam of his undergrad career [01:07] debonzi: Sounds like my fault. Got a traceback to email me? [01:07] stub, sure [01:08] Ok, let's start with Baz. [01:08] stub, Ill sent you an email [01:08] Is anyone not yet using Baz? [01:08] SteveA: I can only use my laptop in certain places and sometimes I have to get out of the way of the contractors in here trying to do their work === SteveA wonders why he captialized Baz [01:08] stub, a lot is your fault, based on my experience from yesterday :) [01:09] ok, cool. everyone is using baz. [01:09] SteveA: here [01:09] hi celse [01:09] hi celso [01:09] I'm using bazoo [01:09] heh, with rocketfuel changed, you are *all* using baz :) [01:10] no choice but ;) [01:10] alias tla=baz [01:10] next, roundup and the issue tracking application. [01:10] roundup? === kiko missed a page [01:10] lifeless: Do we have a script to run to convert our local archives to the new format? [01:11] stub: nope, but I'll do one up. [01:11] stu will be leading the making of an issue tracking / trouble-ticket tracking application. this starts with deploying roundup for this purpose, and integrating roundup's concept of logged in users with launchpad [01:11] elmo is sorting out somewhere to host this roundup instance. [01:12] The roundup end of things will be doing the minimum required to handle commercial and non-commercial support requests. [01:12] I'd like to be able to give jane a decent estimate of when roundup will be running. Any ideas stub and elmo? [01:12] Friday === stub crosses his fingers [01:13] what can we expect to see on friday? [01:13] or would it be by the end of friday? [01:13] you guys have crazy schedules [01:13] Roundup running, accepting issues, login using the auth server. [01:13] kiko: stub has been working on this before today [01:13] And a flag for commercial support === kiko shrugs [01:14] stub: we'll want it to look like it is part of the ubuntu site too [01:14] or at least, have the right logo and colours [01:14] hiya [01:14] hi mark [01:15] ok, next, shipit [01:15] SteveA: This time friday [01:15] I'm working on setting it up on mawson at the moment. [01:15] spiv_pants: you're installing the "new shipit that authenticates using a launchpad authserver" on mawson [01:15] stub: thanks. please keep me up to date with how it's going. [01:16] spiv_pants: what exactly are you setting up? [01:16] That should be done tonight, connectivity allowing. (my home dsl is down, but I'm at jdub's atm, but it's starting to get late) [01:17] do you need to get mysql onto mawson? [01:17] so you need any help from elmo to get this running on there? [01:17] An authserver for the shipit web app to talk to, and then install the shipit cgis somewhere and get the admins to get apache somewhere pointing at that. [01:17] It uses postgres. [01:17] why are we moving shipit? [01:18] we're not [01:18] sabdfl: This is a test instance, for the new launchpad-enabled code. [01:18] this is a place to test that the new shipit works as intended [01:18] ok [01:18] What postgresql server is shippit talking to, and is it being backed up? [01:18] stub: you mean, the real one? [01:18] yes [01:19] spiv_pants: do you know? [01:19] I don't know much about the production shipit -- I know mako has some dumps in his home dir on chinstrap. [01:20] So I suspect the answer is "not as well as it could be". [01:20] mako's the guy to ask, I think. [01:20] spiv_pants: can you find out from mako, and take charge of arranging what is necessary [01:20] Yup [01:20] Ok. [01:21] thanks. please keep me informed about how this is going, and how getting the demo ship-it running is going [01:21] next: auth server [01:21] stub: did we have a problem last week with the auth server going insane when it was disconnected from the database? [01:22] It stopped authing and elmo bounced it. I don't know if it crashed, hung, or what but elmo might. [01:23] spiv_pants: can you get whatever logs you need from elmo, or get them yourself if you have login rights, and try to reproduce the problem? [01:23] There is a bug in Malone, which I think spiv has grabbed already [01:23] stub: Yeah, I have. [01:23] ok, great [01:23] spiv_pants: have you made any progress on it so far? [01:24] Well, I have it using some newer code backed ported from SVN Twisted that in theory fixes the problem deployed, and frustratingly it made no difference :/ [01:25] can we live with "we need to restart the auth server when restarting the golden database" for now? [01:25] I think the next simplest thing to try is probably to make a simple wrapper for psycopg that does the reconnection transparently -- I think stub had a use for that as well? [01:26] because I'd like spiv_pants to concentrate on shipit until that is done. [01:26] SteveA: Sure. Just means someone who can bounce the authserver needs to be around during maintenance - PostgreSQL and emperor have been reliable. [01:26] (If we did make that wrapper, it would probably solve the similar problem in launchpad itself as well) [01:27] okay, let's look at that wrapper when we're together in mataro. [01:27] spiv_pants: can you annotate the bug in malone accordingly? [01:27] Sounds good. I will. [01:27] great. [01:27] soyuz and lucille next [01:28] Kinnison: what's been happening with your work? [01:28] Right [01:28] Personally I've been working on Gina and then on the lucille queue stuff [01:29] Once the dogfood updates happen today; mawson will be in a position to cron-run the script I have to get gina importing hoary into dogfood everyd ay [01:29] also explaining to us numbskulls how it works [01:29] Kinnison: Dogfood update has happened [01:29] kiko: Aww, I do that for fun :-) [01:29] stub: In that case, later today I'll get gina cronned and running [01:29] Kinnison: aha [01:30] SteveA, stub: I can't update the bug, the page on dogfood is broken :/ [01:30] The lucille queue stuff is coming along slowly but surely. I've been refining my ideas of the queue processing and also helping cprov through getting to grips with the rest of lucille [01:30] Oh, no, just the link. [01:30] I've committed to rocketfuel the sqlobject classes and interfaces for the queue so people can start to interrogate it [01:30] (although nothing puts stuff in the queue yet) [01:31] I did a quick explanation of the end-to-end for uploading through to publication for kiko earlier. It's in the irclog for this channel and also on the Lucille page of the wiki [01:31] cprov: would you like to tell what you've done on lucille (you can cover your non-lucille stuff when stevea asks) [01:32] Kinnison: sure [01:32] morning [01:32] I've been working on Librarian Wrapper, it is able to locally cache the files when we run librarian in anoter location [01:33] hi brad. you haven't missed anything you absolutely need to know about [01:33] ok [01:33] it works, but still missing some FS lock to avoid multiple instances [01:33] cprov: what is the librarian wrapper to be used for? [01:34] SteveA: it caches the files locally on LP machine, so we are able to have links to them [01:35] does the librarian server files via apache, or on its own? [01:36] cprov: What is the use case for that? [01:37] Librarian server by its own on a twisted.web server, the wrapper able us to serve by apache [01:38] stub: the Librarian will run hiden inside your network, and we will keep the package archive under apache and organized as a true archive [01:39] I think we need some docs that explain how a full Launchpad must be deployed. [01:39] indeed [01:39] This is becoming rather complex, and I don't feel comfortable that I understand it all. [01:40] SteveA: I need to leave jdub's shortly so I can get the last train back home. Is there anything else you need from me for this meeting? [01:40]