/srv/irclogs.ubuntu.com/2005/01/18/#launchpad.txt

=== 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
jblackDilys on vacation? 04:06
jameshjblack: on the other channel04:22
=== lamont beats his head on baz
lamontgiven a source tree, how do I make it go into baz?06:43
lamont1.0.1, of course.06:43
jblackfirst you init-tree archivename/this--that--version, tune your =tagging-method, add the files, then import06:49
stubcd mysourcetree; baz init-tree mycategory--mybranch--1.0.1; find . | grep -v \{arch\} | grep -v .arch-ids | xargs -n1 baz add; baz import -S06:49
lamontwhat does the -S do?06:50
lamontah, setup06:50
lamont baz init-tree lamont.jones@canonical.com--2004-work/livecd-rootfs--mainline--006:51
lamontbaz add debian debian/*06:51
lamontbaz import -S06:51
lamontimport: project tree has no default version06:51
lamont  tree: /home/lamont/warthogs/livecd/work06:51
lamontis that what it should say?06:51
=== lamont decides that maybe a few hours sleep, followed by an hour or two of reading docs might be the best answer
stubOoh... latest baz doesn't have -S. Just baz import.07:00
lamontsame error, of course07:00
=== lamont is using 1.0.1-2
stubI can't help then - I'm way ahead with crack07:01
lamontrather than the unsupported crack-o-the-day07:01
stubIt is supported crack-o-the-day for us. All of the launchpad team is using it.07:02
lamontand 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
lamontadmittedly, that's not a hard sell.07:03
stubYeah - lifeless tells mark and mark tells mdz and it happens ;)07:03
lamontmeanwhile, anyone on the hoary team is faced with the decision of using what our users are (hoary), or using crack-o-day07:04
lamontall of which just helps add to the frustration that leads to 'cvs import'07:05
stubIf you have used crack-o-day, it is a no brainer decision. It is *much* better.07:05
lamontthen either ship it or support what you ship] 07:05
stubbaz 1.0.1 was pretty much just tla with fewer bugs IIRC07:06
lamontyeah, I'm more likely to just import it into tla 07:06
lamontsince, as it currently sits, it's (a) useless, and (b) unsupported07:06
=== lamont decides to stop venting now
stubThe 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
lamontyeah - 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 tomorrow07:08
stubIf I remember the documentation on that, it might be worth saving some time and start by poking jblack ;)07:09
lamontnah - just whack google for tla meets hello world, use the tla commands and then use baz for everything after that.07:10
stubThat is the doc I remember. It prompted me to get off my arse and write the initial baz command line strawman ;) 07:12
lamontheh07:13
lamontit's crap, but the commands are there at a rate of almost 1 per page07:14
=== 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
lifelessbaz 1.0.1 can read launchpad08:28
lifelesslamont: you forgot 'init-tree some-fully-qualified-verison-here'08:28
lamontlifeless: 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 repository08:30
lamontbut it really would be nice to get something more usable than 1.0.1 into hoary08:31
lamontesp now that the upstream version freeze has arrived08:31
lifelesslamont: we had a whole argument on this at Mataro08:31
lamontyeah.  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 call08:32
lifelessI'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
lamontI just know it would be embarassing to ship 1.0.1 with hoary08:32
lifelessbecause 1.0.1 is a known quantity. 1.1 *might* have a data-eating bug tomorrow.08:32
lifelessif I have to fix 20-odd archives, I'll survive.08:32
lifelessbut if I have to fix 1K archives, I'm in deep shit.08:32
lifelessto turn it around, why doesn't hoary use kernel 2.7 ?08:33
lamontunderstood..  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
jblackthere isn't one? 08:33
lamontbecause we know we won't be shipping 2.7?08:33
lifelessdeb http://bazaar.canonical.com/packages/debs/ ./08:33
lamontI'll ponder some more whether I want to eat dogfood, or switch to the newer baz08:34
lifelessanyway, in 1 week 1.1  will be released, and you'll get 1.1 in hoary08:34
lamontremember to work through the exception process to get approval before you upload it...08:35
lifelesslamont: its easy, I don't package it for hoary.08:35
lamontwho does?08:36
lifelessmdz08:36
lamontwhich just means that the discussion comes beforethe packaging.08:36
lifelessthe discussion all happened in Mataro, AFAIK its a done deal.08:36
lamontanyway, seriously bedtime here.  g'night08:36
lifelessthe whole mataro thing was whether 1.2 or 1.3 would be acceptable.08:37
=== sabdfl [~mark@host217-37-231-28.in-addr.btopenworld.com] has joined #launchpad
sabdflhi all, we need to zero in on the problems holding back the production server10:28
sabdflstub, spiv, carlos, SteveA, who's around to brief me on the status?10:29
stubsabdfl: Morning. Meeting in 2.5 hours which will get you a full update if you are around.10:32
bob2that sounds like a "no" ;-)10:33
stub;)10:34
=== sabdfl [~mark@host217-37-231-28.in-addr.btopenworld.com] has joined #launchpad
sabdflerk, sorry, gaim crashed10:34
lifelesssabdfl: you know about launchpad-dev ?10:35
sabdflah, thought it was launchpad-devel, that's why there's nobody else there :-)10:35
=== 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]
SteveAhey jamesh 02:23
SteveAlet's have a chat about calendaring while the soyuz discussion is going on on the other channel02:23
jameshokay02:23
SteveAwhat still needs to be done before you can merge stuff into the main launchpad code?02:24
SteveAthere's the database layout review02:25
SteveAand that'll start happening today when mark and stu look over the email you sent02:25
jameshthere are a number of things that need to be done, but I'm not sure which ones need to be finished before merging02:25
SteveAwas there an issue about implementing http PUT?  that needn't delay a merge though02:25
jameshrecurring events probably doesn't need to be done before merging.02:26
SteveArihgt02:26
SteveAright02:26
jameshI haven't hooked up the iCalendar export/import yet02:26
jameshso haven't looked into the PUT issue02:26
SteveAokay02:26
SteveAwhere there any changes to the rest of launchpad as part of the calendaring stuff?02:27
jameshmost of it is self contained02:27
lifelessSteveA: how much longer do I need to be around. its 00:3002:27
SteveAi'd like to review the stuff that isn't02:27
jameshthe only changes to be made elsewhere is adding a "calendar" field to tables that can have calendars02:27
SteveAlifeless: no longer.  thanks for coming to the meeting02:27
lifelessnp. night ..02:28
jameshand updating the corresponding sqlobject to add the field and implement ICalendarOwner02:28
jameshwith that, the calendar code automatically hooks up the URL02:28
jameshI also need to add code for managing subscriptions before people can properly make use of the calendar02:29
SteveAis this stuff in your archive mirror on chinstrap?02:29
jameshmost of it is02:29
jameshthere is a bit of stuff I haven't committed/mirrored yet02:30
SteveAcan you do that soon?02:30
SteveAand send me an email with a sort of high-level guide to help me see what code is where?02:30
SteveAi'd like to look through the code, so i can understand how it fits together02:30
SteveAI'll be traveling to england tomorrow, so i could look through things on the plane02:31
jameshI'll commit what I have tonight and send the email.02:31
SteveAthanks james02:31
SteveAkiko, mark and i will talk about the longer term plans for calendaring in london next week02:32
=== SteveA [~steve@adsl-213-190-44-43.takas.lt] has joined #launchpad
=== cprov [~cprov@200.158.100.251] has joined #launchpad
lamontcan I nuke {arch}/++pristene-trees with impunity?04:35
sabdflddaa: can you go ahead with the newt import please?05:04
sabdflddaa: i'm trying to see how smooth the process is for an outsider05:04
ddaaokay05:05
ddaathe smoothness depends very much on how broken is the cvs :-/05:06
=== 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 []
mdzI just created a project when I should have created a product05:51
mdzcan someone clean it up?05:52
kikocprov, mdz corroborates project/product-explorer functionality05:53
cprovkiko: I see05:54
mdzwell, the name of it is 'sudo' if anyone feels like fixing it06:00
mdzA SYSTEM ERROR OCCURRED06:08
mdzPC LOAD LETTER06:08
mdzthis is very frustrating06:08
mdzI spend 10 minutes filling out the 5 required fields, 2 of paragraph length, and am rewarded with "A system error occurred"06:08
mdzsabdfl: my experience with the process so far would not be described as 'smooth'06:09
mdzif 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 know06:11
sabdflmdz: relax, please create a product, point at the cvs repo, and i'll work on the DOAP front page a little06:13
mdzsabdfl: I can't create a product; that's the trouble06:16
mdzI just tried to do alsa-driver06:16
mdzpreviously openoffice.org06:17
mdzsudo seemed to work, as did evms06:17
BradBmdz: it's probably because of the .'s and -'s in the names06:23
BradBI'm guessing, but that seems a definite possibility.06:24
mdzBradB: the name I used for alsa was "driver"06:24
BradBoh06:24
mdzsince that's what they call it upstream, and it'll be unique within the ALSA project06:24
BradBmdz: product names are globally unique06:25
mdzthat's not what it told me on the web page06:25
mdzUpstream Product Details06:25
mdzName (Required)06:25
mdzThe short name of this product, which must be unique among all the products from the same project.06:25
BradBouch06:25
BradBso 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
cprovyep, It might be my fault, I'll update the description06:26
mdzusing "ALSA driver" doesn't work any better, though (a system error occurred)06:26
mdzand I'm fairly certain there is nothing else called that06:26
BradBmdz: fwiw, a valid name is ^[a-z0-9] [a-z0-9\\+\\.\\-] +$06:27
mdzBradB: then where did "Alsa utilities" come from?06:28
mdzis that a database constraint or an input validation?06:28
BradBis that the title, or the name? i.e. when you traverse to it, do you see an Alsa%20utilities in the URL?06:28
BradBmdz: DB constraint06:28
mdzBradB: ok, so it must be the title06:29
BradBmdz: I don't recall offhand if we also check that in app-level code.06:29
mdzthere ought to be a link from a product to the project that it's associated with; I can't find one06:29
BradBthis is where i hand off to cprov ;)06:30
BradBmdz: is the regex above enough to not get system errors now though?06:30
=== lamont_r [~lamont@216.17.255.18] has joined #launchpad
cprovmdz: yes, in "Product Review" you can select a project than you will see the Project portlet on right side06:32
sabdflcan someone think of an example of a real project other than apache, mozilla, debian?06:32
mdzGNU06:32
mdzALSA06:33
mdzGNOME06:33
mdzUbuntu06:33
sabdflok, it's the project creation that's b0rked in general06:36
sabdfllet me see if i can replicate locally06:36
=== 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 []

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!