=== Fujitsu [n=Fujitsu@203.23.49.35] has joined #launchpad === Fujitsu [n=Fujitsu@203.23.49.35] has joined #launchpad === Fujitsu [n=Fujitsu@203.23.49.35] has joined #launchpad === Kylekf [n=Kyle@218.208.223.236] has joined #launchpad === bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad === Trilla is now known as tim-w === Fujitsu [n=Fujitsu@203.23.49.35] has joined #launchpad === torre [i=maas1@200-98-102-84.tlf.dialuol.com.br] has joined #launchpad [01:22] Hi [01:23] im from Brazil... [01:23] Im work in one governation organization [01:25] all spleeping? [01:25] sorry my bad english [01:25] helloooooooooooooooooo === mholthaus_ [n=mholthau@johnny33.dersbach.ch] has joined #launchpad [01:36] Helloooooooooooooooooooooo === Fujitsu_ [n=Fujitsu@203.23.49.35] has joined #launchpad === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad === dsas [n=dean@host86-129-20-93.range86-129.btcentralplus.com] has joined #launchpad === Fujitsu_ [n=Fujitsu@203.23.49.35] has joined #launchpad === mpt [n=mpt@203.118.156.188] has joined #launchpad === Fujitsu_ [n=Fujitsu@203.23.49.35] has joined #launchpad === Fujitsu_ [n=Fujitsu@203.23.49.35] has joined #launchpad === Fujitsu_ [n=Fujitsu@203.23.49.35] has joined #launchpad === mpt_ [n=mpt@203.118.156.188] has joined #launchpad === rpedro [n=rpedro@87-196-110-104.net.novis.pt] has joined #launchpad === mpt__ [n=mpt@203.118.156.188] has joined #launchpad === Lord_Athur [n=alejandr@pc-10-33-214-201.cm.vtr.net] has joined #launchpad [02:59] hi all === stub [n=stub@ppp-58.8.2.196.revip2.asianet.co.th] has joined #launchpad === panickedthumb [n=travis@68-185-125-120.dhcp.rdfr.va.charter.com] has joined #launchpad [03:53] hey, I'm all signed and everything, email still isn't working [03:53] sorry, to those who are confused, I'm referring to this: [03:54] https://launchpad.net/bugs/53679 [03:54] Malone bug 53679 in launchpad "member email" [Untriaged,Rejected] [03:54] I signed the CoC before Launchpad came around [03:54] was unaware I needed to do it again [03:54] but it's done now [03:58] am I still missing something? [04:03] I'll be idle here, if you want to chime in and let me know. Thanks [04:04] panickedthumb: What is your Launchpad username? I can check out the basics and then escalate the problem. [04:04] hey guys, i wish in the package section you would be able to upload packages build for ubuntu (with a repo people can add) since the package menu is kind of frustrating for people who don't have packages in ubuntu [04:07] milosz: You might want to file a wishlist bug on Soyuz - the people who work on that (and can understand what you are asking for) are not online yet. [04:11] stub: panickedthumb === cprov [n=cprov@monga.dorianet.com.br] has joined #launchpad [04:12] stub: ping [04:12] stub: wikiname is TravisNewman, if that has anything to do with it [04:15] panickedthumb: I suspect that this is simply a propagation delay. If it takes more than 24 hours to become active, reassign your bug to james.troup@canonical.com (as he is the only person who can investigate further). If it starts working, you might want to leave the bug open with a comment requesting better documentation about the time delay. [04:15] cprov: pong [04:16] good plan stub [04:16] thanks :) [04:16] stub: when do you plan to do the rollout ? [04:17] cprov: When do you plan on being awake? I don't think malcc will be here for a few hours yet. [04:17] Although I think I can do the rollout anytime, as the database updates will not affect the current soyuz installation [04:18] So I just need to update everything except soyuz [04:19] stub: yes, right, you can rsync production into drescher, just don't replace the "current" symlink. [04:20] ok. So I will do the rollout as normal, except for keeping the codeline on drescher untouched. I will then leave it to you and Malcolm to change the current symlink at your leisure. [04:20] I'll be here in, let's say 5 hours, it will be ~ 8:00 AM UK [04:20] stub: perfect, thank you. [04:39] stub: have you had a chance to look at plitting manifests? [04:40] plitting? Oh... splitting. I've looked it over but not started on the db patch. I'll do that today. [04:41] lifeless: ^^^ [04:41] thanks! === Mhz_ [n=math@dsl-145-41.aei.ca] has joined #launchpad [04:46] hi [04:48] wow [04:48] huge party here [04:48] EEEEEEoooooooo [04:48] there's echo [04:49] hi, my name is matt [04:49] I have suggestions regarding launchpad [04:49] which is becoming some sort of a crashpad for me [04:50] ubuntu [04:50] is [04:50] great [04:50] someone? [04:50] plz? [04:50] ok [04:51] bye === Mhz_ [n=math@dsl-145-41.aei.ca] has left #launchpad ["Ex-Chat"] [04:57] Give the boy a valium === mpt_ [n=mpt@203.118.156.188] has joined #launchpad === Fujitsu [n=Fujitsu@203.23.49.35] has joined #launchpad [06:01] Gooooooooooooooood afternoon Launchpadders! [06:02] hi mpt_ === irvin [n=ipp@ubuntu/member/irvin] has joined #launchpad === rraphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [07:18] spiv, can you ssh to sodium? === spiv tries [07:20] I can, although it doesn't have my ssh key. [07:21] hrmm, I get no response === mpt_ wonders who to complain to [07:22] Spads! [07:23] mpt_: do you have your ssh config setup correctly, as elmo mentioned in his mail to the launchpad list? [07:23] Yes, I just did that [07:23] Before I did it, ssh said "sodium: Name or service not known", but now it hangs instead [07:25] What happens if you try "ssh -vv ..." [07:26] spiv, it gets up to "debug1: Connecting to sodium.ubuntu.com [82.211.81.198] port 22.", and stays there [07:27] mpt_: that's wrong. [07:27] mpt_: it should be connecting via chinstrap. [07:27] mpt_: so your ssh config must be incorrect somehow -- you're probably missing an ProxyCommand. [07:28] Should I have a "Host sodium" section in the config, modelled on the "Host chinstrap" section? === bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad [07:28] (that's what I assumed) [07:29] mpt_: if you have the lines elmo included in his recent email, "ssh sodium.ubuntu.com" should work. === stub [n=stub@ppp-58.8.2.196.revip2.asianet.co.th] has joined #launchpad [07:29] mpt_: if you want "ssh sodium" to work, then you need a "Host sodium" stanza in your ssh config, but it will need an explicit ProxyCommand line. [07:30] mpt_: which is different to chinstrap, because chinstrap is the only externally accessible box. [07:31] Now it's connecting, and asking me for a password [07:31] and my SSH passphrase doesn't work [07:32] it'll be your password in the datacentre, assuming you have one. [07:32] Your standard ssh key should work - mine just did [07:32] stub: Hmm, mine must be setup differently to yours then. [07:32] I needed to add an authorized_keys file, like I had on chinstrap. [07:33] Probably I need to poke at the internal ldap... [07:33] ssh asked me to accept sodium.ubuntu.com, is that what you're referring to? [07:33] spiv: Maybe the key stored in the ldap server is an old key, possibly from your missing laptop [07:34] mpt_: Nope - that is just your local ssh asking if it should trust the remote server key because it hasn't been seen before. [07:34] stub: likely, I suppose. [07:35] mpt_: refer to the MachineOverview page on the internal wiki [07:36] mpt_: It says how to send an email to set your SSH key. [07:36] ooh, nifty === spiv does that too... === elmo [n=james@83-216-156-21.jamest747.adsl.metronet.co.uk] has joined #launchpad === mpt_ wonders how long that will take === bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad === Fujitsu [n=Fujitsu@c58-107-52-160.eburwd7.vic.optusnet.com.au] has joined #launchpad [07:58] ok, so chinstrap has 200G of source === mpool [n=mbp@ozlabs.org] has joined #launchpad [07:58] hullo [07:59] hi [08:00] spiv: ping? [08:00] lifeless: most of which is just noise I would expect. Perhaps just move the launchpad tree across and developers can push repositories to sodium themselves? [08:00] stub: rocketfuel is moved [08:01] stub: I'm generating a list to get elmo to rsync, but yes, we can also have people copy their own across [08:02] mpool: pong [08:03] I'm happy to move mine myself. I can make sure I put all my old branches into repos as I do, rather than just my new branches. [08:04] spiv, hi [08:05] robert suggested talking to you to change some static text about bazaar on the launchpad.net front page - he says it's hardcoded in the source [08:05] or rather, not editable through the web interface [08:06] i'll send you a mail [08:06] Ok. [08:08] sent; should be pretty trivial === stub waits for rocketfuel-built to finish building === bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad === mpt__ [n=mpt@203.118.156.188] has joined #launchpad [08:17] stub: its finished === ..[topic/#launchpad:stub] : Developer meeting: Thu 20 July, 1200UTC (wiki:MeetingAgenda) | launchpad-users@lists.canonical.com (wiki:MailingLists) | Channel logs: http://tinyurl.com/72w39 [08:57] mpt__: my ssh key change has finally happened, can you connect to sodium now? === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad === rpedro_ [n=rpedro@87-196-34-248.net.novis.pt] has joined #launchpad === malcc [n=malcolm@host86-134-233-12.range86-134.btcentralplus.com] has joined #launchpad [09:10] spiv, no [09:11] morning folkies [09:12] mpt: have you gotten a reply to your change@ email yet? [09:13] yes [09:13] The "Here are the results:" section is empty [09:13] Oh. [09:13] So I guess that wasn't the problem to begin with [09:14] mpt: ah, I'm guessing maybe you have a .ssh/id_dsa.pub file, rather than a .ssh/id_rsa.pub file? [09:14] correct [09:14] (that was true in my case, so I had to adjust the example command line on the wiki page accordingly) [09:14] d'oh === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad [09:15] ok, I'll update the wiki page [09:15] mpt: well, your public key can be in either file, it just depends on what type of key you generate. [09:15] mpt: NewStaffTasks also has that command, btw. [09:16] mpt: You should get back a message quoting back the message you sent (which shouldn't be empty!), and then saying "SSH Keys replaced with ..." === bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad [09:19] mpt: the "cat: .ssh/id_rsa.pub: No such file or directory" should have been a hint that something was wrong [09:20] grrrr, it will once I start from the correct directory === mpt thinks sodium should be renamed starcity [09:25] hooray [09:25] good morning [09:26] stub: how is it going with the rollout ? did you already start ? [09:28] spiv, why is init-repo on sodium better than just copying all my branches over from chinstrap? [09:32] wow, bug 7839 is horrid [09:32] Malone bug 7839 in Ubuntu "Ubuntu bug reporting tools need to point to Ubuntu bug systems" [High,Confirmed] http://launchpad.net/bugs/7839 [09:36] oh, it's better because I wasn't using a repository before [09:36] mpt: if you use init-repo in say mpt/launchpad, then bzr pull your branches into that, then all the common revision data will be stored once, rather than duplicated for each branch. [09:37] (pushing works too) [09:37] ok [09:37] It also means that pushing a new branch to chinstrap without rsync is still reasonably quick. [09:38] er, s/chinstrap/sodium/ :) === lfittl [n=lfittl@85-125-227-78.dynamic.xdsl-line.inode.at] has joined #launchpad [09:43] spiv, so to bring a branch into my repository it's just bzr branch chinstrap:/home/warthogs/archives/mpt/launchpad/nameofbranch ./nameofbranch ? [09:43] or bzr pull? === SteveA [n=steve@82.109.136.115] has joined #launchpad === marcus_notebook [n=mholthau@86.24.203.62.cust.bluewin.ch] has joined #launchpad [09:47] mpt: "bzr get sftp://chinstrap/home/warthogs/archives/..." [09:48] (or "bzr branch" if you prefer, "get" is just a synonym for "branch") [09:51] grr [09:52] spiv, when I do that and paramiko says "Password:", what password is it referring to? [09:52] My SSH password didn't work [09:52] and neither did the usual chinstrap one [09:53] mpt: oh, right. your datacentre password, and I guess you don't have one, as per our earlier conversation... [09:53] off to RT, then [09:53] There may be a magic SSH switch to deal with this, just a sec [09:54] mpt: connect to sodium with "ssh -A sodium" [09:55] Name or service not known, ho ho === mpt tries again with s.u.c [09:55] mpt: Oh, right. Well, "ssh -A ..." :) [09:55] yay, stuff is happening [09:56] thanks spiv [09:56] mpt: You can set the ForwardAgent option in .ssh/options to make that permanent. [09:56] er, .ssh/cnofig [09:56] config. [09:57] in the *.ubuntu.com section? [09:58] Somewhere, probably there. [09:58] It's easy to test if it's working ;) === bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad [10:04] This will apparently take quite some time [10:05] hi === danilos [n=danilo@82.109.136.115] has joined #launchpad === Spads [n=crack@217.205.109.249] has joined #launchpad [10:06] I have set up a new pastebin on sodium: https://sodium.ubuntu.com/~andrew/paste/ [10:08] mpt: it'll probably go faster if the first thing you do in the repo is "bzr branch /home/warthogs/archives/rocketfuel/launchpad/devel ./rf" [10:09] mpt: you can even delete ./rf afterwards, but that will get all the revisions from rocketfuel from a local directory, so they won't need to be fetched over sftp. [10:09] Should I cancel the current branching to do that? :-) === MaSa69 [n=MaSa69@dsl-jklbrasgw1-fe1cfb00-100.dhcp.inet.fi] has joined #launchpad [10:10] mpt: Also, call your launchpad directory "launchpad" rather than "lp", or else pending reviews won't be happy. [10:10] Yeah, that should be ok, I think. === jamesh [n=james@82.109.136.115] has joined #launchpad === lbm [n=lbm@0x50a1ee0c.unknown.tele.dk] has joined #launchpad === carlos [n=carlos@82.109.136.115] has joined #launchpad [10:15] spiv: can we move across old pastes? and if so, is it worth doing? [10:15] morning [10:15] SteveA: 1) yes, quite easily, 2) not sure. [10:16] carlos: morning ;) === spiv looks at how big they are [10:16] danilos: hey dude!, long time since last time we meet! ;-) [10:17] carlos: yeah, looking forward to you buying me a beer when we meet again :P [10:17] hmmmm, what's a beer? [10:17] danilos: do I know you? [10:17] SteveA: people generally access pastes by URL, but copying them across won't help the old URLs to find the new pastebin instance. [10:18] ok [10:18] so we won't copy them across [10:18] they'll be accessible on chinstrap again eventually [10:18] Well, they should still be accessible on chinstrap. [10:18] Just that you can't add new ones. [10:19] SteveA: e.g. https://chinstrap.ubuntu.com/~dsilvers/paste/filecrSEwC.html works just fine. [10:20] spiv, have you tried your own paste service? [10:20] mpt: yes. [10:20] Submitting it gives me a blank page, just like Kinnison's one does [10:20] Is there a chinstrap reference lurking in the code somewhere? [10:20] mpt: well, it's Kinnison's code... [10:21] mpt: Hmm, that suggests your browser isn't following the redirect? [10:21] mpt: was your paste "test1"/"test2"? Posted twice? [10:22] (it's hard to tell, because I just did a "test 1"/"test 2", so it's all a bit confusing ;) [10:22] spiv, yes [10:22] mpt: Basically, all it does is emit this: [10:22] Content-Type: text/plain [10:22] Refresh: 0; URL=https://sodium.ubuntu.com/~andrew/paste/$name [10:22] Which is rather low tech. [10:22] lifeless: ping [10:23] pong [10:23] spiv: I think the paste service has an index with the titles of previous pastes there [10:23] It's a dumb CGI that doesn't even set a proper http status code. [10:23] well, it no worky [10:23] carlos: it sure does. [10:23] mpt: what browser? [10:23] hi lifeless. we should work out what we want the launchpad developers to do, and send an email out with a fresh subject line explaining it. [10:23] spiv: wouldn't that be used to get old 'pasted' texts ? [10:23] SteveA: spiv has been working on this, could we ask him to do that ? [10:24] lifeless: is it clear to you what the plan is -- what people need to do? [10:24] I've seen two things pass by in the email thread, one from you and one from mark === carlos doen't care about any previous paste file he had there, it's just in case someone else cares [10:24] spiv, Safari, but Safari *used* to work... === mpt pouts [10:24] SteveA: yes. I replied to Marks but it seems to have awoled === ddaa [n=ddaa@82.109.136.115] has joined #launchpad [10:24] I see Firefox works [10:24] lifeless: is spiv clear on what needs to be done, and does he have all required access to do it? [10:24] mpt: well, I haven't changed Kinnison's code except s/chinstrap/sodium/ and s/dsilvers/andrew/ [10:24] SteveA: lets talk with him now [10:25] mpt, spiv: we can support safari later. [10:25] lifeless, SteveA: hi :) [10:25] hello andrew [10:25] spiv: SteveA and I would like to put a new email together with clear TODO instructions [10:25] mpt: I'll put in a simple workaround for you. [10:25] mpt: if you need it. [10:25] mpt: but you can go and find your link on the list.cgi page after pasting. [10:25] no, I don't need it particularly [10:25] spiv: I like the idea of going to repos for everyone, as Mark suggested. [10:25] mpt: ok, I'll be lazy then :) [10:25] anything interesting I paste is from Ubuntu anyway [10:25] lifeless: sounds good. [10:26] lifeless: you want me to write up the details of how to do this, similar to what I've helped mpt with on this channel? [10:26] spiv, Konqueror downloads the file instead of displaying it in the browser [10:26] where there are things we can just *do* for everyone, we should do it [10:27] spiv, actually, it downloads an *empty* file that doesn't contain the text I pasted [10:27] the rest should be in a clear DOIT email [10:27] actually [10:27] better is a clear DOIT wiki page [10:27] mpt: fun. [10:27] because then we can update the instructions [10:27] without sending multiple emails [10:27] SteveA: the problem is, that we cannot tell what is relevant or not for each developer [10:28] SteveA: it *needs* to be documented and done by each developer. [10:28] spiv: so, are you up for this? [10:28] I don't think individual developers have all that much data in bzr knit format [10:28] SteveA: historical data, we can and will do for people [10:28] it is feasible to say "we copy over just bzr knit trees" ? [10:28] lifeless: I think so, but I want to be sure I understand exactly what I'm meant to do.... [10:30] Do you want me to document how to move branches from chinstrap into a repo on sodium? [10:30] SteveA: I deleted 8Gb of a 9Gb tree I copied over due to cruft [10:30] SteveA: so just saying that to the developers may be neither clear enough, nor appropriate. [10:31] spiv: I'd like you to document how to [10:31] lifeless: my proposal is, *we* determine which are bzr branches in knit format, and copy all those over. [10:31] Why does it matter if they are in knit format? [10:32] *) make a shared repo on sodium for each project - one for lp, one for bzr etc - in /home/warthogs/archives/$user/$project [10:32] I'm assuming the vast majority of revisions are merged into rocketfuel. [10:32] cprov: haven't started yet - I needed a nap ;) [10:32] spiv: because those are the only branches that may be currnet [10:32] *) pull into that each branch they wish to preserve as a branch [10:32] So if we use shared repos, there's very little cost to having old branches included. [10:33] right [10:33] SteveA: no, we cant do that except as root. permissions will kill you. Also a lot of the wasted space is due to non-repo based branches [10:33] And part of the process of pulling branches into the repo is that all branches would be knits (that are stored in the shared repo). [10:33] SteveA: which have working trees and other undesirables. [10:33] stub: no worries, ping me when you need [10:33] let's do it as root, OR do it as one user, and get the permissions changed as root after we've done it [10:33] The only problem with copying a weave branch is that it would be slower. [10:34] we can get special things set up just for today [10:34] spiv: if its going into a repo, and the repo is in knit format, it should be fast as long as the repo has already got most of the data [10:34] lifeless: yeah, that's what I thought. [10:34] lifeless: (hence my intentionally vague use of the term "slower", rather than "much slower" ;) [10:35] But I agree with Steve, I think we could automate this for everyone. [10:35] SteveA: I can start figuring out how much data is in knit format. I expect most of the 215Gb will be in knit format branches, and if so, then we still cant trivially do it as a batch process [10:35] cprov: I think r3819 should be rolled out - you happy with that? [10:36] (that is the soyuz patch that landed patch-67-06-0.sql with the pocketroot.chroot not null [10:36] stub: yes, it's exactly what i'd claim. [10:36] We're looking at about ~220Mb per user for launchpad, that's about how big the repo is for rocketfuel's launchpad. [10:36] spiv: I had a little script to do the "pull lots of branches into a repo" if that'd help [10:36] jamesh: I think I still have it swimming around my desktop somewhere ;) [10:37] http://people.ubuntu.com/~jamesh/make-bzr-repo.sh [10:37] if we do the conversion properly, we can get by with 1Gb per user - and that allows lots of users [10:38] lifeless: properly meaning shared repos and no working trees? [10:38] spiv: yes. [10:38] on chinstrap rocketfuel was 9Gb, on sodium, I've got it down to 1Gb === spiv nods [10:39] Just making sure I'm not forgetting anything important :) [10:39] at that size, we could not have migrated everyone at all. [10:40] SteveA: I replied, did you get my reply? [10:41] I just received an email from you [10:41] cool [10:41] right now on chinstra, your bzr trees take up 7Gb [10:41] I think its much saner to delegate *deciding* what to keep to each developer. [10:42] I'm happy with the direction you and spiv are going in. I just want to ensure you've thought through the different options, as we've had problems when we've asked everyone to follow some particular instructions before [10:42] as, for instance, I have no idea which of your branches are useful or not. [10:42] people choose to vary the instructions without being fully informed about why they are as they are [10:42] and then other things break [10:42] for example, people using "launchpad-repository" as their repository directory on chinstrap broke pending-reviews [10:43] SteveA: ok, in which case, yes, I think we have no better choice than good doco. But we can be very precise about what is user-varyable, and what is not. [10:43] so, I figure it is worth at least exploring setting up everything for everyone in a consistent way [10:43] spiv: how is this sounding to you ? [10:43] SteveA: we can automate the repo initialisation with a little admin chmod love [10:44] spiv: by that I mean do 'init-repo $user/launchpad && bzr branch rocketfuel/launchpad/devel $user/launchpad/devel && chmod $user $user -R' for each user [10:44] which will give people a lot less guesswork about where things go [10:46] lifeless: I see no reason why we shouldn't do that. [10:47] It eliminates the entire "Do once" section of the doc I was just sketching out. [10:48] spiv: I propose that you put your docs up on a wiki page at SodiumSetup on the launchpad wiki. [10:49] then mail the list and tell people that instructions will appear on that page, and invite people to subscribe to that page if they would like to [10:49] lifeless, SteveA: if we do that, then the migrate procedure becomes a very simple: "ssh -A sodium; cd /home/warthogs/archives/$USER/launchpad; bzr get sftp://chinstrap/home/warthogs/archives/$USER/launchpad/$BRANCH", where $USER and $BRANCH are replaced by the user, of course. [10:49] then we work on instructions here, and put them on that page when they are done [10:49] that way, people catching up with the mail thread on the launchapd list will not be so confused [10:49] (and then of course they need to remember to push to the new location, etc) [10:50] and will have clear direction from us [10:50] SteveA: I'll do that. [10:50] SteveA: but I think it would be great to do what lifeless suggests, to do the common, necessary steps for everyone automatically. [10:51] I agree wholeheartedly === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [10:51] SteveA: can you or lifeless make that happen? [10:51] I'll do it now [10:51] SteveA: excellent [10:52] SteveA: Moin claims you are editing SodiumSetup [10:52] yes [10:52] I just said I'd do it now [10:53] the documentatio should appear there only when the system is prepared too [10:53] including permissions etc. [10:53] Oh, I thought you said for me to make that page. Ah, ok. === doko [n=doko@dslb-088-073-101-083.pools.arcor-ip.net] has joined #launchpad [10:56] spiv: please dont use bzr get [10:56] lifeless: "bzr branch", sorry :) [10:56] spiv: its confusing because it does not do what baz get did, instead use and document 'bzr branch' [10:56] I'm a lazy typist on IRC. [10:57] lazy good, wrong bad :) [10:57] brb [10:57] Well, not so lazy that I use all lower-case or omit punctuation... ;) [10:57] will bzr get be deprecated soon? [10:58] lifeless: arguably, what "bzr branch" does isn't much like what "baz branch" did either ;) [10:58] lifeless: (I'll document bzr branch, of course.) [10:59] spiv: well, it makes a new bzr branch for you, which is what baz branch did [10:59] SteveA: it should get turned into an alias for checkout soon, which will make it do what baz get did do when it did do stuff [10:59] Heh, my fingers are trained to follow "sftp://" with "chinstrap". [11:04] carlos: ping [11:04] doko: pong [11:06] carlos: the OOo po's currently merge translations with the same msgid into one place; unfortunately that is broken in the current translate-toolkit. does rosetta have a problem, if I do not merge the msgid's for the next upload, and then turn merging on again, if translate-toolkit is fixed? [11:08] doko: rosetta will reject those .po files because are not valid [11:08] doko: wait, seems like we have a solution [11:08] carlos: which one's are invalid? [11:08] danilos: could you explain him how to do that? [11:09] doko: PO files which have several messages with the same msgid are invalid [11:09] doko: you can fix them using 'msguniq' tool from gettext-tools === doko grumbles that rosetta should fix these ... [11:10] doko: (look at options --use-first and -u) [11:10] doko: so I guess you could use that command as a post processing tool until pootle fixes their code or we finish the native support for OO [11:11] but aren't the message identifiers lost? "discard duplicates" [11:11] doko: yes, but I can explain what I did when I translated OOo to Serbian [11:12] danilos: I think when you translated that, you did translate the 250 separate files ... [11:12] doko: nope ;-) [11:12] danilos: but? [11:13] if I discard the message identifiers, how can I convert back to the GSI format? [11:13] doko: I only had like 50 of them: http://prevod.org/programi/openoffice/2.0/osnovno [11:13] doko: well, the trick is to create a new (or several) big PO file and discard identifiers [11:14] doko: I created one per-directory of OOo [11:14] doko: and then used that to fill-in all the 250 of them using msgmerge [11:14] ok, so how did you merge back these and generate the GSI file? [11:15] lifeless, SteveA: draft of the migration howto: https://sodium.ubuntu.com/~andrew/paste/fileOmZ7Eu.html [11:15] I've disabled the soyuz cronscripts, pending the Launchpad update. [11:15] i.e. 'for i in sw/*.po; do msgmerge -u $i path-to-my-compilation/sw.po; done' [11:15] or something like that, I forgot the msgmerge syntax === spiv proofreads [11:15] spiv: /me looks [11:15] spiv: please give a concordance of all the user ids === doko thinks it's easier to include a copy of the old translate-toolkit until the new one is fixed ... [11:16] spiv: rather than 'want to migrate', perhaps 'want to keep' [11:17] spiv: bzr sftp://sodium.ubuntu.com/home/warthogs/archives/$USER/launchpad/$BRANCH [11:17] is missing a verb [11:17] # REPLACE "sqlobject" here with whatever component you need. [11:17] mkdir -p /home/warthogs/archives/$USER/ [11:17] cd /home/warthogs/archives/$USER/sqlobject [11:17] rather than saying 'REPLACE...' [11:17] use $PROJECT or $COMPONENT [11:18] also, init-repo will mkdir for you [11:18] Oh, I didn't know that. [11:18] (about init-repo) [11:18] so bzr init-repo /home/warthogs/archives/$USER/$PROJECT [11:18] doko: maybe, the thing is that if you want a single PO file to be used, you can then use it as a compendium (-C option to msgmerge) to populate all the other PO files [11:19] spiv: also, for the 'making other project', do an ls of rocketfuel and list all their names [11:19] so there is no guesswork involved. [11:19] danilos: I'll leave that to the rosetta implementation handling GSI files ;-P [11:19] other than that, I think it looks good [11:20] wow, this is still taking forever [11:20] doko: well, your choice ;-) [11:20] lifeless: by concordance of all user ids, you mean list the user ids already in use on chinstrap vs. username? [11:21] spiv: right. what should each user use for $USER [11:21] mpt: hmm, I'm surprised, it was quite fast to copy the few branches I've copied so far. === bradb [n=bradb@modemcable048.58-130-66.mc.videotron.ca] has joined #launchpad [11:21] doko: the plan is to have such native support implemented in next two months [11:21] lifeless: does that really matter? [11:21] at least that's our timeline [11:21] aha [11:21] spiv, bzr info says this branch is in weave format 6 [11:21] lifeless: Oh, I guess if the directories are being pre-made for them... [11:21] spiv: exactly [11:22] mpt: interesting, lifeless reckoned that wouldn't be much slower. [11:22] at least, the branch is in branch format 4 and the repository is in weave format 6 [11:22] spiv: if most of the data is there [11:22] mpt: yeah, the repo format is the significant factor there. [11:22] spiv: it is fast-pathed [11:23] spiv: it will only be slow if it has to convert many revisions [11:23] mpt: it has to convert any revision in the weave not already in the local repo to a knit. [11:23] spiv: note that 'slow' is relative, of course:) [11:23] mpt: which basically means each revision not yet merged to rocketfuel. [11:24] mpt: but in short, complain to your fellow kiwi ;) [11:24] lifeless: thanks for the feedback [11:26] np [11:26] spiv: the doc reads well to me. well done. [11:26] sometime later (not this week) I want us to consider moving /home/warthogs/archives/ to perhaps /home/branches or something like that [11:26] or /home/code [11:28] damn [11:28]