[12:04] desktopguide.pot -> accept [12:04] on desktopguide? [12:04] on xubuntu-docs [12:04] voil [12:04] yay === mdke hugs [12:05] np! [12:05] wow my backlogs are massive [12:05] not bad service for midlight on a sunday [12:05] some don't reach where I was pinged [12:05] *night [12:05] hehe [12:05] yeah, need to go to bed, swimming in 7h [12:05] doesn't your client collect the pings? === sabdfl [n=mark@ubuntu/member/pdpc.silver.sabdfl] has left #launchpad [] === mdz_ [n=mdz@201.160.19.41.cableonline.com.mx] has joined #launchpad === Znarl [n=karl@bb-82-108-14-161.ukonline.co.uk] has joined #launchpad [12:34] spiv: awake? === Keybuk [n=scott@quest.netsplit.com] has joined #launchpad === WaterSevenUb [n=WaterSev@195-23-238-144.nr.ip.pt] has joined #launchpad === Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad [01:40] Is there a bigger version of the launchpad.png logo somewhere? === jd_ [n=jd@wikipedia/Meanos] has joined #launchpad === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === jd_ [n=jd@wikipedia/Meanos] has joined #launchpad [02:03] jamesh: matsubara/launchpad/strip-white-space - can you please review this today [02:04] spiv: you have a new review === ..[topic/#launchpad:lifeless] : Conversion to knits occuring, PQM is down. https://launchpad.net/ | developer meeting: Thu 18 May, 1200UTC (wiki:MeetingAgenda) | launchpad-users@lists.canonical.com (wiki:MailingLists) | Channel logs: http://tinyurl.com/72w39 === Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #launchpad [02:12] spiv: heh, line drop [02:12] I noticed :) [02:12] so yeah [02:13] I have an all in one repository on ballent [02:13] and the inventory index is 860K [02:13] the knit is 90M [02:14] sofor sftp the minimum cost is 2Mb download to understand the repository, and then a few kb to push the revision [02:14] mpool: ^^^ this is why full reads of the index concern me :) [02:19] lifeless, agree [02:20] lifeless, i thought conversion to knits had been deferred to the 22nd? [02:20] in the last thing i read [02:20] mpool: where ??? [02:20] kiko wrote me and asked about the possibility [02:20] I replied [02:21] meh. === lifeless wakes stevea up [02:21] emr, no, kiko will be a better target [02:21] kiko: ping === AlinuxOS [n=AlinuxOS@d83-176-107-55.cust.tele2.it] has joined #launchpad [02:32] spiv: meh, cant contact steve OR kiko [02:33] lifeless: So what's the plan? === AlinuxOS [n=AlinuxOS@d83-176-107-55.cust.tele2.it] has joined #launchpad [02:34] spiv: thinking we should abort [02:35] which is extremly frustrating [02:36] Yeah. [02:36] Well, I'll get on with other stuff for the moment. [02:37] ok === lifeless reenables PQM === mpt__ [n=mpt@203.109.220.214] has joined #launchpad === mpt__ [n=mpt@203.109.220.214] has joined #launchpad === mpt__ [n=mpt@203.109.220.214] has joined #launchpad === mpt__ is now known as mpt [03:30] Goooooooooooooooooooooooood afternoon Launchpadders! [03:44] lifeless, is the #launchpad topic out of date? [03:47] yes [03:47] https://launchpad.net/ | developer meeting: Thu 18 May, 1200UTC (wiki:MeetingAgenda) | launchpad-users@lists.canonical.com (wiki:MailingLists) | Channel logs: http://tinyurl.com/72w39 === LeeJunFan [n=junfan@adsl-69-210-207-5.dsl.klmzmi.ameritech.net] has joined #launchpad === stub [n=stub@ppp-58.8.2.81.revip2.asianet.co.th] has joined #launchpad === dsas [n=dean@host81-158-82-247.range81-158.btcentralplus.com] has joined #launchpad [07:15] lifeless: ping === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === dsas [n=dean@host81-158-82-247.range81-158.btcentralplus.com] has joined #launchpad === mpt [n=mpt@203.109.220.214] has joined #launchpad === mpt_ [n=mpt@203.109.220.214] has joined #launchpad [08:35] morning [08:35] Is chinstrap down or slow? [08:35] not down [08:35] Whenever I try to pull from it it times out [08:35] hrmm [08:35] quite loaded [08:36] ok, ssh works [08:36] I'll try again [08:36] archyvsyn is doing a lot of stuff [08:36] so, i'm guessing its IO is saturated [08:44] lifeless: ping === jinty [n=jinty@212.Red-83-54-75.dynamicIP.rima-tde.net] has joined #launchpad === cmvo [n=cmvo@62.225.11.174] has joined #launchpad [08:57] Hi! Can I close a bug in launchpad that I reported? [08:59] if the bugs fixed sure === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad [09:01] kgoetz: I should have asked: How can I close a bug? :-) I can't find the right option staring at the bug page. [09:01] cmvo: :) click on the name of the bug (next to where it says 'severity' and 'priority', and change it to 'rejected' [09:01] cmvo: click on the product or package name in the table at the top of the bug page [09:03] kgoetz, jamesh: Argh! Thats well hidden :-) I thought it would lead me back to the package page. Thanks! === rpedro [n=rpedro@87-196-32-106.net.novis.pt] has joined #launchpad [09:04] no worries cmvo :) [09:04] hi ddaa [09:04] hello jamesh [09:05] ddaa: I was looking at a bit of the logic for recording the commit dates in bzrsync.py, and I think it is recording the wrong date for commits [09:06] sounds annoying [09:06] the revision timestamp is recorded as a UTC timestamp, but bzrsync.py offsets the timestamp by the timezone [09:06] the revision's timezone, that is === stub [n=stub@ppp-58.8.2.81.revip2.asianet.co.th] has joined #launchpad [09:08] mh [09:09] I have to admit that I do not quite understand datetime things [09:09] kgoetz: How should I set the status? The bug is not relevant for the package, but I don't want to reassignt it to another package. I just want to close it. [09:09] my understanding is that bzr is storing the date as a UTC timestamp plus a timezone offset [09:09] cmvo: set it to rejected if it's not a problem, or fix releaed if it's been fixed [09:09] so when recording the data in the database we should probably be ignoring the timezone data [09:10] mh... okay, so attaching the tz causes sqlobject to adjust the timestamp when storing in the db? [09:10] the problem isn't really obvious in the Launchpad web UI because we just display a commit date [09:10] ddaa: meeting on irc in 50 mins / [09:10] ? [09:11] kgoetz: Ok, thanks. [09:11] SteveA: sure, I was about to prepare the agenda [09:12] jamesh: do you think we should mention that issue in the meeting, or just opening up a bug for discussion would be enough? [09:12] i think it is worth mentioning significant bugs [09:13] but perhaps they don't require discussion [09:13] ddaa: either way. The fix would be to remove two lines of code (and add tests) [09:15] jamesh: ah, I see... === ddaa did not quite read it right [09:15] jamesh: as SteveA said === ddaa goes to prepare meeting === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === SteveA discovers a touchpad trick to send the mouse pointer across to the other side of the screen in an instant [09:18] two fingers? [09:19] yeah, tappiing one finger, then tapping another elsewhere while releasing the first [09:20] it takes some practice to be useful, because the direction is relative not an absolute position on the screen [09:20] it probably looks like very fast acceleration from first finger point to the other [09:20] *wow this finger just teleported* [09:21] maybe write a flatland remake, world as seen from a touchpad [09:21] scrolling can be done on a touchpad too: "scroll" your finger at the right side of the pad :) [09:23] uws: tapping the bottom right corner looks like a right-click too [09:23] not for me [09:23] I can tap with 2 fingers for a middle mouse click [09:24] and tap with 3 fingers to right click [09:24] paste paste paste paste paste paste paste [09:24] jamesh: my bottom right corner is rounded (ibm thinkpad) [09:26] uws: my new laptop doesn't have a touchpad :( None of these gestures work very well with the little joystick thingee [09:33] jamesh: ibm thinkpads have both (and I connect my logitech trackman wheel using USB :) [09:34] uws: not on the X series [09:39] jamesh: ah, mine is from the r series. gsynaptics is pretty cool btw. capplet for the touchpad... [09:40] uws: I bought an external mouse in case I can't get used to it [09:40] uws: but it works pretty well [09:41] I've not used a normal mouse for daily work for 4 years now... my trackball is my best friend === carlos [n=carlos@175.Red-88-9-38.dynamicIP.rima-tde.net] has joined #launchpad [09:45] morning [09:51] SteveA: jamesh: spiv: mpool: lifeless: meeting in 10 mins in #launchpad-meeting [09:51] answere nature calls and workraves now [09:59] spiv: ping! [09:59] ddaa: Still 1759 here :P === malcc [n=malcolm@host81-154-31-97.range81-154.btcentralplus.com] has joined #launchpad [10:00] spiv: you are now officially late :) [10:00] -> #launchpad-meeting [10:00] ddaa: I'm there :P [10:09] morning all === erdalronahi [n=erdal@p50876292.dip.t-dialin.net] has joined #launchpad === jinty [n=jinty@62-15-158-30.inversas.jazztel.es] has joined #launchpad === ploum [n=ploum@ubuntu/member/ploum] has joined #launchpad === SnkBite [n=SnkBite@212.25.63.35] has joined #launchpad === mpt [n=mpt@203.109.220.214] has joined #launchpad === WaterSevenUb [n=WaterSev@195-23-238-149.nr.ip.pt] has joined #launchpad === erdalronahi [n=erdal@p508754BF.dip.t-dialin.net] has joined #launchpad === cmvo [n=cmvo@62.225.11.174] has left #launchpad [] [11:39] carlos: you know all the new templates with empty translations that appeared recently? are they getting translations merged, or should the translation teams start working overtime on them? [11:41] mdke: usually, that means that there isn't translations at all [11:42] mdke: we fixed the bug that hide resources to translate if you don't have any translation yet [11:42] carlos: we've had quite a few emails to the various lists about it, an example is https://lists.ubuntu.com/archives/rosetta-users/2006-May/001511.html [11:42] oh right [11:43] so there is a lot of translating to do :) [11:43] I guess ;-) [11:44] mdke: mark developed already a way to show resources priorities [11:44] man, everything is done at the last minute with Ubuntu :/ [11:44] I guess we will land that soon [11:45] I'll answer some of the email s [11:46] jordi: ? [11:46] jordi: are you handling those emails? [11:47] it doesn't matter, I'm happy to send a couple [11:48] mdke: yeah, you are doing a really good work helping on the mailing list. Thank you very much [11:49] np at all === Yannig [n=yannick@AToulouse-254-1-91-123.w86-207.abo.wanadoo.fr] has joined #launchpad [11:54] Hello everybody :) [11:54] May I ask a dumb question? :) [11:54] carlos: rosetta-users? yes, in general. I might have a few pending from last week tho [11:55] Yannig: go ahead! [11:55] jordi: and ubuntu-translators [11:55] I'm beginning to translate Ubunto into Occitan and I don't really know if I'm doing it well: Occitan is not in https://launchpad.net/rosetta/groups/ubuntu-translators/ [11:56] -translators I'm lagging a lot behind, yup :/ [11:56] Yannig: you don't need to have a translation team to translate in Ubuntu [11:56] Yannig: you are doing correctly for now. [11:56] But it's best to have a team so you can control who can and who can't translate. [11:56] (and I don't find everything that has to be translated in https://launchpad.net/distros/ubuntu/dapper/+lang/oc/) [11:57] Yannig: you should find it now [11:57] Sorry for last message: it does work now, Launchpad may have waited for a certain number of translations to be done [11:57] we fixed that last week [11:57] Thanks :) [11:58] Yannig: wow, you have a bunch of things to do... ;-) [11:59] Yannig: I think you should start with https://launchpad.net/distros/ubuntu/dapper/+source/debian-installer/+pots/debian-installer/oc/+translate [11:59] How can I create a team that will be included into Gnome translators or Ubuntu translators? [11:59] is the most important part that you will not be able to update later. I think the timeline to translate the installer is really soon [12:00] Fair enough, I'll work on it this afternoon [12:02] carlos: this thursday is the freeze [12:02] Yannig: next thursday is the timeline... [12:02] https://wiki.ubuntu.com/DapperReleaseSchedule [12:03] yeah [12:03] I just found it [12:03] Hum, not much time :p [12:05] So, do I have to create a team for Occitan translations that will be included into Gnome translators or Ubuntu translators? If so, how can I do please? :) [12:17] Yannig: create an Ubuntu team [12:17] Yannig: https://wiki.ubuntu.com/RosettaFAQ#head-b356f13978780b88ed4844602554339ac2c33774 [12:17] you have there the procedure === erdalronahi_ [n=erdal@p50877EF8.dip.t-dialin.net] has joined #launchpad [12:20] erdalronahi_: hi [12:21] hi carlos [12:21] dude, sorry, I was so busy last week that forgot your bug... [12:21] erdalronahi_: do you have time to take a look to it today? [12:22] well, maybe in the evening [12:22] ok [12:22] erdalronahi_: please, ping me [12:22] but the situation is quite clear, [12:22] as i have stated in my mail [12:22] if you want to, you can even delete everything, [12:22] and re-import everything from Breezy [12:23] erdalronahi_: what do you mean by 'lost'? [12:23] completely removed [12:23] or do they appear as suggestions? [12:23] there is nothing lost completely [12:24] everything has moved to suggestions [12:24] but to copy some thousand translations from the suggestions [12:24] is an awful lot of work [12:25] erdalronahi_: I could work out something to select them again, but you should take into account what I said about the fuzzy flag [12:26] what did you say about the flag? [12:26] I could either activate them directly and you check it later or activate them and set the needs review flag so you need to accept every entry later (just disabling the Needs review flat) (when I said fuzzy, please, read Needs review) [12:26] erdalronahi_: I don't have a way to know if the needs review flag was set or not when you added a new translation [12:26] activate them all [12:27] so if I automatically activate a translation and had the needs review flag set, it will lack it [12:27] We will go through them, but it's better to have activated translations [12:27] Activate them all, [12:27] I will set the flag again if necessary [12:28] o select the best from the suggestions [12:29] ok [12:29] I will work out the needed SQL commands to do it [12:30] erdalronahi_: if there are more than one suggestion, I'm going to activate the newer one [12:30] that's the best [12:30] didn't know the time is also saved [12:31] yeah, we have many metadata stored that is not yet exposed in our UI === erdalronahi_ is now known as erdalronahi [12:33] good to have it :) [12:33] hope it will work like a wiki in the future, [12:33] where you can see who did what and when [12:34] carlos, I have to leave [12:35] do you need something from me? [12:35] not sure if we will reach that level of details, but we will be near [12:35] erdalronahi: no, thank you, I will do my changes on the staging server and send you an email to check that all is ok [12:35] and will apply that to production [12:35] ok [12:35] great [12:36] will there be an opportunity to complete more of the translation [12:36] before the new locale-pack is built? [12:37] erdalronahi: openoffice translation follows the language pack timelines [12:37] well, language packs re being built daily now :) [12:37] openoffice translations are not [12:38] right, is not so easy [12:38] but what I mean is that we should get at least an update every month [12:38] after release [12:38] We couldn't add much now, because it was so hard to find the missing translations [12:38] Well, that's what you said for Breezy, too :) [12:38] I know it's hard, [12:39] I am seeing all the trouble you (and us) have [12:39] But in the and it all works out [12:40] erdalronahi: right, I said that, but this time is true ;-) [12:41] we have full language packs imported in Rosetta now [12:41] Thanks carlos for the information :) [12:41] we hadn't for breezy [12:41] Yannig: you are welcome [12:43] Yes, that is very good, to see what is ahead === erdalronahi is now known as erdalronahi_away [12:51] hi, I'm wondering if the ability to put preformatted text into bug comments has been discussed or added [01:00] Yannig: you need to create the ubuntu-l10n-oc team to add it to the ubuntu translators team [01:01] lifeless: ping? [01:03] lifeless: SteveA: BjornT: kiko: jamesh: review meeting? [01:04] spiv: I guess lifeless is still unavailable today [01:04] jamesh: Seems so. [01:04] carlos> Done :) === jamesh wonders what spiv is doing on chinstrap === stub [n=stub@ppp-58.8.2.81.revip2.asianet.co.th] has joined #launchpad [01:06] jamesh: A merge of rocketfuel into an oldish branch I don't have locally. I fear it's reweaving or something. [01:06] spiv: okay. That'll probably take ~ 10 hours [01:07] jamesh: 10 hours to get the merge done??? [01:07] carlos: if it is an old branch and is currently reweaving [01:08] may be faster in the other direction [01:08] jamesh: Yeah, I was hoping it'd finish over dinner, but it seems unlikely now, so I'll abort it. [01:08] branch rocketfuel ; pull --overwrite mybranch ; merge rocketfuel [01:09] Yeah. Or even just reapply the diff of the changes, it doesn't have a complex merge history w.r.t. rocketfuel. === spiv checks the log file. Yeah, it was reweaving. [01:11] so, who wants to chair the meeting? [01:14] oh, forgot about the meeting. i'm here now. [01:14] Well, that makes three of us here... [01:15] should we start? [01:16] jamesh: I guess that means you're chairing ;) [01:16] * [01:16] Roll call [01:16] * [01:16] Agenda [01:16] * [01:16] Next meeting [01:16] * [01:16] Queue status. [01:16] * [01:16] properties should not be expensive. SteveAlexander [01:16] * [01:16] ensuring "[trivial] " merges are really trivial -- perhaps random post-merge reviews? diffstat in commits mails? something else? AndrewBennetts [01:16] bah [01:16] okay, that's the agenda [01:17] next meeting: same time next week? [01:17] sounds good [01:17] Fine by me. [01:18] queue status. [01:18] there is nothing on the general queue to be allocated. Does anyone have branches that need to be reallocated? [01:18] not me [01:18] I'm fine. [01:20] So lifeless brought up the issue of ancient branches sitting in needs-reply or merge-conditional/merge-approved state [01:20] There were responses about most of the really old ones, iirc [01:20] so that's probably fine. [01:21] SteveA: are you around to describe "properties should not be expensive"? [01:23] The basic gist was that property access looks cheap in Python code, so properties that are expensive to calculate are waiting to be misused possibly leading to timeouts [01:24] e.g. a property that performs a bunch of big queries each time it is accessed might be better to implement as a method rather than a property [01:24] This is mentioned in PEP 8 now. [01:24] So in theory this is already part of our review policy ;) [01:25] so if you see properties like this during review, it is worth asking questions about it [01:26] Last item on the agenda is spiv's. Do you want to elaborate? [01:26] For whatever reason, I think people sometimes submit merges with [trivial] that are more than a two-line change here or there. [01:27] And so there's some significant changes that aren't getting reviewed. [01:27] I've been thinking that including something like the diffstat of the merge in the commit emails would make it obvious which "trivial" changes are actually touching 70 lines across 5 files. [01:28] So I propose that someone updates PQM to do this, or perhaps suggests another alternative. [01:28] Or just convinces me that it's not a significant problem :) [01:29] I could imagine a 70 line trivial change where the change is trivial but it adds a test to make sure that the problem doesn't regress ... [01:29] but I get your point [01:29] Right. [01:29] It's entirely possible for a trivial change to be lengthy. [01:30] But it doesn't hurt to have it flagged as a good idea for a post-commit review. [01:30] Getting diffstat output in the commit emails is probably something that only lifeless can do [01:30] And post-commit reviews are easy to generate diffs for: "bzr diff -r 999..998" [01:31] we could also try to push people to ask a reviewer to review it before submitting it for merge. if it's truely trivial, it shouldn't take a reviewer more than a few minutes to review. [01:31] I've mentioned it verbally to lifeless in the past, and his opinion was "patches to pqm welcome" === cprov [n=cprov@201-68-7-102.dsl.telesp.net.br] has joined #launchpad [01:33] good morning [01:33] one possibility would be a script that emails launchpad-reviews with a summary of [trivial] commits [01:33] I wonder how much spam that would produce? [01:33] jamesh: Probably not too much. I like that idea. [01:34] i think that sounds like a good idea. ideally it shouldn't produce much spam. === morgs [n=morganc@www2a.your-server.co.za] has joined #launchpad [01:35] batching it once per day would limit the impact. [01:35] it probably be good to include the diff in the email as well, since it shouldn't be that big, and it would make it easy to do a post-review. [01:35] jamesh, BjornT: once per day, with diffs, sounds ideal to me. [01:36] kiko: around? [01:36] I guess I can look at writing a script after I've got the sprint scheduler stuff out of the way [01:36] i'm not sure batching is necessary, currently there are just a few trivial commits per day. [01:37] Is there anything else anyone wants to bring up? [01:38] no, can't think of anything else [01:38] Not from me. [01:38] jamesh: hello [01:38] hi SteveA [01:38] was there a reviewers' meeting? [01:39] SteveA: yeah. I was just about to close it. Do you want to bring anything up? [01:40] i just skimmed the scrollback [01:40] i'd like us to spend sometime improving our pqm-process tools and scripts [01:40] but not just this week [01:40] hi [01:41] review meeting in 20 minutes [01:41] do we have a launchpad-project product for describing our code-commit process? [01:41] lifeless: Er... [01:41] lifeless: In minus 40, I think :) [01:41] perhaps [01:41] if we have such a product, then we can add specs and bugs for that [01:41] 1100 GMT ? [01:41] lifeless: it is 11:41 GMT right now [01:41] including a spec about exactly how we want pqm to be sending emails to the lists, so that it is more useful [01:42] indeed [01:42] SteveA: https://launchpad.net/products/launchpad-development-infrastructure probably covers such tools [01:42] my bad, I'm very sorry I wasn't here, I thought it was an hour later [01:42] jamesh: cool. let's get a braindump spec in there for notifications from pqm [01:43] lifeless: It happens. Anything you want to add to the scrollback? [01:43] yes [01:43] the email commit plugin is the thing to teach diffstat to [01:43] where we can write about the need for diffstats in pqm emails, and maybe batching trivial change notifications with stats/diffs [01:43] pqm uses that vanilla [01:43] https://launchpad.net/products/launchpad-development-infrastructure is the product to file bugs on [01:43] i'm proposing a spec for how we ideally want things to work [01:44] then we can have bugs / branches for developing in that direction incrementally [01:44] SteveA: great. specs on that product to I think [01:44] i'd prefer this to just knocking off features that are easy as we think of them, although we can do that as well of course [01:44] who will braindump that spec? === SteveA looks at jamesh, spiv and bjorn [01:45] well [01:45] I'd like an informational spec [01:46] that describes the overarching goal. I think you and I should do that Steve. [01:46] i think there was some interesting discussion earlier in this meeting [01:46] then things that take us towards that should have braindumps or better, which can be worked on with bugs and branches [01:46] (which i missed) [01:47] i know... jamesh: i propose we have a skype call tomorrow morning [01:47] okay [01:47] where we can discuss your ideas for this. i'll write up some notes for that [01:47] um, from that [01:47] and that can form the basis of the spec [01:47] I'll include all the discussion in the meeting minutes [01:48] SteveA: perhaps we are talking at cross purposes. I am saying that we do not have a 'Spec' that covers the entire review process end to end *with* assistance for automation [01:48] then i can talk with lifeless, spiv, bjorn and others [01:48] (I mean discussion of this meeting in the minutes) [01:48] SteveA: if you are talking about the finer grained stuff, I'm entirely happy with what you proposed. [01:49] lifeless: getting too abstract for me. let's have this discussion when there is something written down. [01:49] that way, it becomes concrete, as "I propose this be several specs" or "we need a spec that includes this, and also these other things" [01:50] mpt: around? [01:50] SteveA: ok. lets do that. You'll discuss with jamesh and braindump ? [01:50] yeah [01:50] i'll write that in my diary for tomorrow [01:51] SteveA: then wednesday morning we can talk ? [01:51] jamesh: spiv: btw email plugin is at http://people.ubuntu.com/~robertc/baz2.0/plugins/email/ [01:51] lifeless: Thanks. [01:51] jamesh: thank you for doing adhoc chairing, I really appreciate it [01:52] lifeless: no problem. [01:52] if there isn't anything else, I think that's the end of the meeting === morgs [n=morganc@www2a.your-server.co.za] has left #launchpad [] [01:52] jamesh: countdown? :) === salgado [n=salgado@200.171.140.32] has joined #launchpad [01:52] 10 [01:52] 9 [01:52] 8 [01:52] 7 [01:52] 6 [01:52] 5 [01:52] 4 [01:52] 3 [01:52] 2 [01:52] 1 [01:53] end. [01:53] :) [01:53] boom-tish [01:53] jamesh: thanks for chairing. [01:53] thanks james === bradb [n=bradb@modemcable092.66-130-66.mc.videotron.ca] has joined #launchpad === matsubara [n=matsubar@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [02:01] SteveA: the knit upgrade did not happen, kiko asked for a delay on saturday, I replied but had no response from either of you before monday, tried to ring you both (I thought it would be -just- acceptable timewise), but no joy [02:01] SteveA: I hope I did not wake you [02:01] i didn't receive a call [02:02] kiko had some concerns about it having a bad effect on the new shipit rollout. i wanted to talk with him on the phone about it, but we didn't manage to. [02:03] sure. [02:03] Its no skin off my nose - PQM is slow and will remain so until the conversion is done. [02:03] My personal suspicion is that PQM's slowness is much more of a burden than a knit conversion ;) [02:03] one thing i did want to ask you [02:03] shoot [02:04] if something unexpectedly goes wrong with the conversion, and we find out on the first or second PQM merge into it [02:04] what are the options to proceed? [02:04] rm -fr .bzr/; mv .bzr.backup .bzr ;) [02:04] 1) restore the master branch [02:04] (from local copy, not tape) [02:05] 2) debug and fix in place [02:05] those are the options [02:05] we know PQM runs knits ok - several branches are already in knit form - bzr, cscvs, dists. [02:05] restoring the master branch puts us back in the position just before the switch to knits? [02:05]