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