[04:06] <jblack> Dilys on vacation? 
[04:22] <jamesh> jblack: on the other channel
[06:43] <lamont> given a source tree, how do I make it go into baz?
[06:43] <lamont> 1.0.1, of course.
[06:49] <jblack> first you init-tree archivename/this--that--version, tune your =tagging-method, add the files, then import
[06:49] <stub> cd mysourcetree; baz init-tree mycategory--mybranch--1.0.1; find . | grep -v \{arch\} | grep -v .arch-ids | xargs -n1 baz add; baz import -S
[06:50] <lamont> what does the -S do?
[06:50] <lamont> ah, setup
[06:51] <lamont>  baz init-tree lamont.jones@canonical.com--2004-work/livecd-rootfs--mainline--0
[06:51] <lamont> baz add debian debian/*
[06:51] <lamont> baz import -S
[06:51] <lamont> import: project tree has no default version
[06:51] <lamont>   tree: /home/lamont/warthogs/livecd/work
[06:51] <lamont> is that what it should say?
[07:00] <stub> Ooh... latest baz doesn't have -S. Just baz import.
[07:00] <lamont> same error, of course
[07:01] <stub> I can't help then - I'm way ahead with crack
[07:01] <lamont> rather than the unsupported crack-o-the-day
[07:02] <stub> It is supported crack-o-the-day for us. All of the launchpad team is using it.
[07:03] <lamont> and yet it's not in hoary, and barring someone convincing the release manager that we should violate the upstream version freeze, 1.0.1 is what'll ship with hoary.
[07:03] <lamont> admittedly, that's not a hard sell.
[07:03] <stub> Yeah - lifeless tells mark and mark tells mdz and it happens ;)
[07:04] <lamont> meanwhile, anyone on the hoary team is faced with the decision of using what our users are (hoary), or using crack-o-day
[07:05] <lamont> all of which just helps add to the frustration that leads to 'cvs import'
[07:05] <stub> If you have used crack-o-day, it is a no brainer decision. It is *much* better.
[07:05] <lamont> then either ship it or support what you ship] 
[07:06] <stub> baz 1.0.1 was pretty much just tla with fewer bugs IIRC
[07:06] <lamont> yeah, I'm more likely to just import it into tla 
[07:06] <lamont> since, as it currently sits, it's (a) useless, and (b) unsupported
[07:08] <stub> The method you would use for tla should work with 1.0.1 too - we just can't test it (cause if we downgrade, we can't checkout launchpad since it is in a new-format archive)
[07:08] <lamont> yeah - only I don't have enough experience with importing into tla to make it a no-brainer for me... I'll grab the docs and get the import done tomorrow
[07:09] <stub> If I remember the documentation on that, it might be worth saving some time and start by poking jblack ;)
[07:10] <lamont> nah - just whack google for tla meets hello world, use the tla commands and then use baz for everything after that.
[07:12] <stub> That is the doc I remember. It prompted me to get off my arse and write the initial baz command line strawman ;) 
[07:13] <lamont> heh
[07:14] <lamont> it's crap, but the commands are there at a rate of almost 1 per page
[08:28] <lifeless> baz 1.0.1 can read launchpad
[08:28] <lifeless> lamont: you forgot 'init-tree some-fully-qualified-verison-here'
[08:30] <lamont> lifeless: yeah - with arch-meets in front of me, it only took about 5 minutes to glean the commands i needed from that and get the thing into the repository
[08:31] <lamont> but it really would be nice to get something more usable than 1.0.1 into hoary
[08:31] <lamont> esp now that the upstream version freeze has arrived
[08:31] <lifeless> lamont: we had a whole argument on this at Mataro
[08:32] <lamont> yeah.  and I still don't understand why you would rather support developers using 1.0.1 more than 1.1-pre.  But that's your call
[08:32] <lifeless> I'm happy to inflict 1.1 on folk that opt it. But I'm not interested in our crack-of-the-minute code being given to X thousand folk.
[08:32] <lamont> I just know it would be embarassing to ship 1.0.1 with hoary
[08:32] <lifeless> because 1.0.1 is a known quantity. 1.1 *might* have a data-eating bug tomorrow.
[08:32] <lifeless> if I have to fix 20-odd archives, I'll survive.
[08:32] <lifeless> but if I have to fix 1K archives, I'm in deep shit.
[08:33] <lifeless> to turn it around, why doesn't hoary use kernel 2.7 ?
[08:33] <lamont> understood..  is 1.1 at least packaged somewhere?  or is it 'grab the crack-of-the-day after making sure it's not terribly broken by asking in #launchpad'?
[08:33] <jblack> there isn't one? 
[08:33] <lamont> because we know we won't be shipping 2.7?
[08:33] <lifeless> deb http://bazaar.canonical.com/packages/debs/ ./
[08:34] <lamont> I'll ponder some more whether I want to eat dogfood, or switch to the newer baz
[08:34] <lifeless> anyway, in 1 week 1.1  will be released, and you'll get 1.1 in hoary
[08:35] <lamont> remember to work through the exception process to get approval before you upload it...
[08:35] <lifeless> lamont: its easy, I don't package it for hoary.
[08:36] <lamont> who does?
[08:36] <lifeless> mdz
[08:36] <lamont> which just means that the discussion comes beforethe packaging.
[08:36] <lifeless> the discussion all happened in Mataro, AFAIK its a done deal.
[08:36] <lamont> anyway, seriously bedtime here.  g'night
[08:37] <lifeless> the whole mataro thing was whether 1.2 or 1.3 would be acceptable.
[10:28] <sabdfl> hi all, we need to zero in on the problems holding back the production server
[10:29] <sabdfl> stub, spiv, carlos, SteveA, who's around to brief me on the status?
[10:32] <stub> sabdfl: Morning. Meeting in 2.5 hours which will get you a full update if you are around.
[10:33] <bob2> that sounds like a "no" ;-)
[10:34] <stub> ;)
[10:34] <sabdfl> erk, sorry, gaim crashed
[10:35] <lifeless> sabdfl: you know about launchpad-dev ?
[10:35] <sabdfl> ah, thought it was launchpad-devel, that's why there's nobody else there :-)
[02:23] <SteveA> hey jamesh 
[02:23] <SteveA> let's have a chat about calendaring while the soyuz discussion is going on on the other channel
[02:23] <jamesh> okay
[02:24] <SteveA> what still needs to be done before you can merge stuff into the main launchpad code?
[02:25] <SteveA> there's the database layout review
[02:25] <SteveA> and that'll start happening today when mark and stu look over the email you sent
[02:25] <jamesh> there are a number of things that need to be done, but I'm not sure which ones need to be finished before merging
[02:25] <SteveA> was there an issue about implementing http PUT?  that needn't delay a merge though
[02:26] <jamesh> recurring events probably doesn't need to be done before merging.
[02:26] <SteveA> rihgt
[02:26] <SteveA> right
[02:26] <jamesh> I haven't hooked up the iCalendar export/import yet
[02:26] <jamesh> so haven't looked into the PUT issue
[02:26] <SteveA> okay
[02:27] <SteveA> where there any changes to the rest of launchpad as part of the calendaring stuff?
[02:27] <jamesh> most of it is self contained
[02:27] <lifeless> SteveA: how much longer do I need to be around. its 00:30
[02:27] <SteveA> i'd like to review the stuff that isn't
[02:27] <jamesh> the only changes to be made elsewhere is adding a "calendar" field to tables that can have calendars
[02:27] <SteveA> lifeless: no longer.  thanks for coming to the meeting
[02:28] <lifeless> np. night ..
[02:28] <jamesh> and updating the corresponding sqlobject to add the field and implement ICalendarOwner
[02:28] <jamesh> with that, the calendar code automatically hooks up the URL
[02:29] <jamesh> I also need to add code for managing subscriptions before people can properly make use of the calendar
[02:29] <SteveA> is this stuff in your archive mirror on chinstrap?
[02:29] <jamesh> most of it is
[02:30] <jamesh> there is a bit of stuff I haven't committed/mirrored yet
[02:30] <SteveA> can you do that soon?
[02:30] <SteveA> and send me an email with a sort of high-level guide to help me see what code is where?
[02:30] <SteveA> i'd like to look through the code, so i can understand how it fits together
[02:31] <SteveA> I'll be traveling to england tomorrow, so i could look through things on the plane
[02:31] <jamesh> I'll commit what I have tonight and send the email.
[02:31] <SteveA> thanks james
[02:32] <SteveA> kiko, mark and i will talk about the longer term plans for calendaring in london next week
[04:35] <lamont> can I nuke {arch}/++pristene-trees with impunity?
[05:04] <sabdfl> ddaa: can you go ahead with the newt import please?
[05:04] <sabdfl> ddaa: i'm trying to see how smooth the process is for an outsider
[05:05] <ddaa> okay
[05:06] <ddaa> the smoothness depends very much on how broken is the cvs :-/
[05:51] <mdz> I just created a project when I should have created a product
[05:52] <mdz> can someone clean it up?
[05:53] <kiko> cprov, mdz corroborates project/product-explorer functionality
[05:54] <cprov> kiko: I see
[06:00] <mdz> well, the name of it is 'sudo' if anyone feels like fixing it
[06:08] <mdz> A SYSTEM ERROR OCCURRED
[06:08] <mdz> PC LOAD LETTER
[06:08] <mdz> this is very frustrating
[06:08] <mdz> I spend 10 minutes filling out the 5 required fields, 2 of paragraph length, and am rewarded with "A system error occurred"
[06:09] <mdz> sabdfl: my experience with the process so far would not be described as 'smooth'
[06:11] <mdz> if anyone is available to go over these problems with me, and get them fixed so that we can proceed with imports for HCT testing, please let me know
[06:13] <sabdfl> mdz: relax, please create a product, point at the cvs repo, and i'll work on the DOAP front page a little
[06:16] <mdz> sabdfl: I can't create a product; that's the trouble
[06:16] <mdz> I just tried to do alsa-driver
[06:17] <mdz> previously openoffice.org
[06:17] <mdz> sudo seemed to work, as did evms
[06:23] <BradB> mdz: it's probably because of the .'s and -'s in the names
[06:24] <BradB> I'm guessing, but that seems a definite possibility.
[06:24] <mdz> BradB: the name I used for alsa was "driver"
[06:24] <BradB> oh
[06:24] <mdz> since that's what they call it upstream, and it'll be unique within the ALSA project
[06:25] <BradB> mdz: product names are globally unique
[06:25] <mdz> that's not what it told me on the web page
[06:25] <mdz> Upstream Product Details
[06:25] <mdz> Name (Required)
[06:25] <mdz> The short name of this product, which must be unique among all the products from the same project.
[06:25] <BradB> ouch
[06:26] <BradB> so did you call something else driver by any chance? I'm just seeing if I can offer a quick solution to you before anyone else jumps in.
[06:26] <cprov> yep, It might be my fault, I'll update the description
[06:26] <mdz> using "ALSA driver" doesn't work any better, though (a system error occurred)
[06:26] <mdz> and I'm fairly certain there is nothing else called that
[06:27] <BradB> mdz: fwiw, a valid name is ^[a-z0-9] [a-z0-9\\+\\.\\-] +$
[06:28] <mdz> BradB: then where did "Alsa utilities" come from?
[06:28] <mdz> is that a database constraint or an input validation?
[06:28] <BradB> is that the title, or the name? i.e. when you traverse to it, do you see an Alsa%20utilities in the URL?
[06:28] <BradB> mdz: DB constraint
[06:29] <mdz> BradB: ok, so it must be the title
[06:29] <BradB> mdz: I don't recall offhand if we also check that in app-level code.
[06:29] <mdz> there ought to be a link from a product to the project that it's associated with; I can't find one
[06:30] <BradB> this is where i hand off to cprov ;)
[06:30] <BradB> mdz: is the regex above enough to not get system errors now though?
[06:32] <cprov> mdz: yes, in "Product Review" you can select a project than you will see the Project portlet on right side
[06:32] <sabdfl> can someone think of an example of a real project other than apache, mozilla, debian?
[06:32] <mdz> GNU
[06:33] <mdz> ALSA
[06:33] <mdz> GNOME
[06:33] <mdz> Ubuntu
[06:36] <sabdfl> ok, it's the project creation that's b0rked in general
[06:36] <sabdfl> let me see if i can replicate locally