[00:14] hi poolie [00:14] turns out the EINTR bug was very shallow [00:15] hi jam, i saw your mail, and i'm happy to hear that [00:15] did you talk to aaron at all? [00:17] maxb: merged, thanks. [00:17] poolie: I haven't yet. For some reason I got hives last night, and couldn't sleep for the itchiness, so I ended up starting a bit late [00:18] I think it was an allergic reaction to something, but I have no idea what [00:18] I didn't eat anything different, etc [00:19] I did write up most of the decisions I've taken [00:19] so I'm pretty close to getting feedback time [00:20] poolie: have you seen ? [00:21] it may well not be anything to do with your change, [00:22] I've seen that sort of failure on a bunch of different cases when poking things [00:23] right, bed for me. [00:59] If I do bzr revert -r -11 is there some easy way to get what revno I've reverted to? I tried bzr revno --tree but didn't work [01:01] No, revert doesn't change the revno of anything, it just edits files. It's not really any different from `bzr diff -r-11 | patch -R`. [01:03] jam that's great [01:04] mgz no i hadn't, thanks for pointing it out [01:07] mgz, that's interesting it didn't fail on ubuntu [01:07] the scope replacer thing ought to be platform-independent [01:12] poolie: would it be a python 2.7 thing? [01:12] maybe [01:13] I believe mgz is known for random python versions :) [01:30] hi spivvo [01:36] Hi poolie [01:37] hey there, how are you? [01:53] Pretty good. Mary's got a new laptop, new enough to be giving her mild grief with video driver issues :/ [01:53] oh, what kidn? [01:54] A 13" Dell Vostro [02:05] spiv, actually, would you mind investigating the scopereplacer? [02:05] it may have been my landing that broke it but i don't think it's especially related to anything i know [02:05] http://babune.ladeuil.net:24842/job/selftest-freebsd/183/testReport/junit/bzrlib.tests.blackbox.test_branch/TestBranchStacked/test_branch_stacked_from_smart_server/ [02:11] actually nm [02:13] Heh. [02:13] >> Greetings To You, [02:13] On behalf of the OBAMA'S FOUNDATION and UNITED NATIONS, [02:13] we wish to notify you as a beneficiary of $900,000.00 USD in compensation of [02:13] scam victims. [02:13] mm i bet [02:15] rotfl [02:37] hey all - I know fuckall about fedora - is there a "more sensible" way to get recent bzr on fedora12? [02:37] 'debtakeover' [02:38] hehe [02:38] there's a fedora maintainer [02:38] why do you ask? [02:38] lifeless: and if I remember correctly, this is a known bug that's fixed in 2.2, right: http://hudson.drizzle.org/view/Drizzle-build/job/drizzle-build-drizzleslap/593/console? [02:38] lifeless: well, because I've got a fedora box with 2.0.5 on it, and I believe I'm suffering from a bug fixed by upgrading... [02:38] mtaylor: that looks like a fs fail to me [02:39] lifeless: there's 112G available on the box... [02:39] what fs [02:39] ext4 [02:39] when did it last crash/power down unexpectedly [02:40] oh! recently apparently [02:40] poo [02:40] lifeless: so my solution here is kill repo and re-pull, yes? or can I just kill that file? [02:40] uhm [02:40] * lifeless hands you over to a bzr person [02:40] spiv: ^ [02:40] lifeless: I think you qualifiy still as a bzr person even if that's not your job title ;) [02:43] its more that [02:43] - the answer is complex [02:44] - you need to dig a bit to get the actual answer on a case by case basis [02:44] - we should make that more automated [02:51] Sorry, my net connection dropped out, so I missed the start of the conversation. Which file is damaged? [02:51] (Then, apparently unrelated, my wireless router needed to be restarted too...) [02:51] 13:38 < mtaylor> lifeless: and if I remember correctly, this is a known bug that's fixed in 2.2, right: http://hudson.drizzle.org/view/Drizzle-build/job/drizzle-build-drizzleslap/593/console? [02:53] mtaylor: just deleting the file won't help; bzr will still expect that file to exist. Simplest fix is to delete and recreate that repo, yes. [03:03] so, I am running this command here [03:03] $ bzr dpush [03:03] Using saved location: svn+ssh://svn.twistedmatrix.com/svn/Twisted/branches/strports-endpoints-4473 [03:03] 8817kB 38kB/s | pushing revisions:generating file id map 0/1 [03:03] why have I dpushed almost 10M of data for a couple of tiny diffs? (you can see them at twistedmatrix.com/trac/timeline, they are not big) [03:06] the 10M includes local disk IO rewriting your history. [03:36] Is there an easy way to query for all the documentation bugs in Launchpad? I can't remember how to do that. [03:37] jbowtie, all the bzr doc bugs, or all altogether? [03:37] the easiest way is to click 'doc' in the tag cloud [03:38] jbowtie: which will take you to https://bugs.edge.launchpad.net/bzr/+bugs?field.tag=doc [03:38] I meant the bzr doc bugs, those are the ones I want to work on. [03:38] that would be excellent [03:38] poolie: Thanks for that, will hopefully send through a bunch of patches the next few days. [03:39] poolie: Just remember that when I apply for Ubuntu Developer status. [03:39] :) [03:41] It's a shame that all the Canonical positions require you to be in the American or European timezones, I'd apply for job so I could work on Bazaar/Launchpad full time. [03:44] jbowtie: http://webapps.ubuntu.com/employment/canonical_BSE/ (in /topic) doesn't require those timezones AFAIK [03:45] Lots of positions don't. [03:46] spiv: You're right, I hadn't seen that one! Looks like I will be applying when I get home tonight. [03:47] wgrant: I suppose so, but every time I see one it has the timezone requirement attached. [03:48] jbowtie: definitely apply [03:50] poolie: Oh, I will. Though I suspect you just want to make sure I actually write those documentation patches. :P [03:50] it will help :) [03:50] i'm reading cvs now as it happens but i don't expect the gate will close for another week or so === tchan1 is now known as tchan [04:03] poolie: just passing around, don't bang your head too much on the scopereplacer thing, I've seen it a few times, it has always been transient [04:03] oh, hi [04:03] how strange [04:04] poolie: often triggered for smart server test so it may be related to some thread ordering differences in turn triggering different import ordering [04:04] not worth the effort until it happens too often [04:08] :/ [04:08] ok, thanks [04:18] poolie: last occurrence was http://babune.ladeuil.net:24842/job/selftest-freebsd/98/testReport/junit/bzrlib.tests.blackbox.test_branch/TestBranchStacked/test_branch_stacked_from_smart_server/ [04:18] jun 14 [04:19] run #184 just succeeded, transient again [04:19] * vila back to bed [04:53] lifeless: I guess I can rebase first, then dpush? [04:56] Hmm. [04:56] Is there a way to construct bzr+ssh URLs to be $HOME-relative? [04:56] like, I can 'scp foo bar:' and it'll just drop 'foo' into my home directory on bar [04:58] glyph: yes [04:58] glyph: bzr+ssh://host/~/foo [04:59] (requires bzr 2.1 or newer on the server) [05:01] maybe we should just add $host: [05:04] And make trailing slashes significant? ;) [05:09] oh like rsync? :) [05:11] hnnnnnnnnngh [05:11] spiv: hey good idea! [05:11] whoops typo [05:11] what I meant was [05:11] "spiv: die in a fire" [05:11] the only way i ever get rsync command lines right is if they're in my shell history [05:11] Thanks a lot though! I will be using "~" a lot now! :) [05:11] :) [05:12] mwhudson: how do you get the rsync command lines you typoed out of your shell history [05:12] glyph: it's a mystery [05:12] well, actually trial and error i guess [05:14] it is actually a bit logical [05:14] "a" means "the thing a", and "a/" is "everything inside a" [05:15] that's what ayn rand was talking about [05:15] 'a is a and a/ is not a' [05:15] haha [05:17] poolie: as a source it makes sense to me. the problem is when you put it on the destination [05:17] 'sync a with remote:a' and 'sync everything in a with remote:a' [05:17] like... what does that mean? [05:17] it makes no difference to the destination [05:17] rsync a remote:b [05:18] and you will end up with remote:b/a/... [05:18] rsync a/ remote:b and you'll end up with remote:b/... containing what was in a [05:18] the fact that it looks like it might do something does make it confusing of course [05:34] glyph: it will still do the same work [05:34] glyph: the point is that the 8M doesn't represent 'network IO' [05:35] it represents 'IO' [05:37] lifeless: I didn't think we included local IO in the transport activity reporting [05:37] lifeless: a quick grep suggests I'm right... [05:37] I was moderately sure we did [05:37] if we don't its arguably a bug (NFS etc) [06:33] we don't include localtransport io [06:34] i don't know what bzr-svn may be doing for its own io [06:34] lifeless: the reasoning is that for the common base case of branching from lp to localhost, it would naively double the data transferred and the rate [06:34] obviously you can account for stuff to make that even out but maybe yagni [06:41] https://bugs.launchpad.net/bzr-mac-installers/+bug/621446 [06:41] Launchpad bug 621446 in Bazaar Mac Installers "AttributeError: paths when trying to svn-import (affected: 2, heat: 15)" [Undecided,New] [06:42] Can somebody poke the responsible parties there? the 2.2.0 mac installer on bazaar.canonical.com still has 1.0.4dev. [06:43] glyph: can you send a mail? i don't see them online atm [06:44] Send a mail to whom? Do you mean put a comment on the bug? [06:45] hm, so i thought that 1.0.4dev would have this fixed [06:45] * poolie looks [06:45] but there is now a 1.0.4 final [06:46] Mmmm... it may have been due to the old buggy repository. Let me try again. [06:47] Nope, reconfirmed outside of the shared repo. Very, very definitely affects the 1.0.4dev in the current bzr mac installer. [06:58] poolie: thanks [07:06] and 1.0.4 works? [07:06] does 'bzr plugins -v' confirm you're using the plugin from the installer? [07:30] i have a question about branches and git and it's differences, who could possibly help me? [07:36] Probably a number of people, but only after you ask the question :> [07:39] ok :) I am trying to decide between Git and Bzr and i favor git a little bit because of it's branch support. However, i work with 2 windows developers and have avarage repositories < 30Mb of php & images [07:39] i find bazaar far more clearly [07:40] but i fear that local branching might be a breaking drawback [07:40] am i right to think this or is this not something that will likely bother me? Git and bzr both seem to do their basics well [07:41] but git evangelists love their index, cheap branching and the tree-eating monster [07:41] and i am confused what to pick [07:41] (not to much text i hope?) :) [07:43] Well... those are pretty broad points. Hard to give a specific answer, since there's no real specific question... [07:43] Certainly the branch representations are rather different, so they have different advantages and drawbacks. [07:44] And one drawback of the bzr way is that some minor setup is required to share history among local branches, and rather more setup and ongoing care to share a single working tree among them git-style. [07:44] ah, can you name a bazaar advantages? I know git's: 1 tree and easy push [07:44] Contrarily, an advantage is that it's way easier and less hackish to have working trees of multiple branches at once with shared history. [07:45] And it's also somewhat easier and more obvious to push only a particular branch around. [07:45] in my case branches will normally be about bugfixes or small features that need to be merges later on [07:46] Me, I find that multiple WT's on the different branches make a lot of things a lot easier. It sounds like you're doing web stuff, and it's handy to be able to have a browser tab on one branch, and another on another branch, at the same time, rather than having to switch back and forth one at a time. [07:47] I don't think there's always a clearcut winner on which method is better, even in some specific cases; certainly in general it's all over the place. [07:48] I would lay good odds that bzr grows a native and robust variant of git-style before git grows a native and robust variant of bzr-style. [07:48] Though AFAIK neither is right around the corner, so that's more of a longer-term thing. [07:50] this is very true. bzr to git is much better then the other way around. also i am fearing the windows developers (2) will not like the git-hassle [07:51] oops [07:51] @fullermd but you love bzr over git i assume? [07:52] Oh, yes. That's why I'm here :) [07:52] i guess for simple vcs is does not really matter and bzr seems the safer choice [07:53] why did you go for bzr? [07:53] Oh, mostly for dumb and superficial reasons. But I stayed because I found better reasons. [07:54] There are things git has that I wish bzr did (and that multiple-branches-in-one-tree thing is a big one). [07:54] But, I think bzr can grow those capabilities without changing or compromising any of the advantages of the way it currently does things. [07:54] And I don't think git can do the complement; it would be a much bigger change in their model of things to support side-by-side branches and WT's with shared history. [07:56] I also particularly like bzr's exploitation of merge asymmetry. I've seen git-using projects go to a lot of trouble to try and avoid situations that that makes a non-issue. [07:56] hi all ! [07:56] haha, my initial choice for git was it's hardcore status and the tree-eating monster on their homepage... but i find it hard to justify my choices now with bzr having API support and git does indeed seem to remain git [07:57] it was made for large speed-needing many devvers projects like linux [07:58] hi vila [07:59] Sure, I expect there will always be performance/resource-usage advantages you can point at for git. How much they matter in a relative or absolute sense, probably less clear. And certainly for small projects, I don't think it matters what you pick at this point perf-wise. === spike_ is now known as spikeWRK [11:22] ~~~ [11:28] bialix: hi ! You're on the beach looking at waves ~~~ ? [11:29] bonjour vila! [11:29] not on the beach unfortunately [12:28] hello vila, bialix [12:28] won't be here for long [12:30] poolie: yeah, *you* are on your way to the beach ;) [12:30] oh my, already 13:30, time for lunch === poolie changed the topic of #bzr to: Bazaar version control | try https://answers.launchpad.net/bzr for more help | http://irclogs.ubuntu.com/ | Patch pilot: vila | Release Manager: vila | bzr 2.2.0 is officially out | work on bzr: http://webapps.ubuntu.com/employment/canonical_BSE/ === Ursinha-afk is now known as Ursinha [14:23] vila: ping [14:23] bialix: pong [14:23] do you by any chance know what's the difference between wt format 5 and 6? [14:24] 1.14 format creates wt5 and 2a creates wt6 [14:26] bialix: let me check, in the meant time, why do you care ? [14:26] I have format1 plugin to avoid 2a as default; wanna update it to 1.14 [14:27] bialix: from the docstrings, wt6 supprot views [14:27] ah [14:27] ok, thank you [14:27] wt5 support content filtering [14:28] ok [14:28] bialix: by the way, you still need this plugin ? poolie didn't add a config option for it ? [14:29] I dunno. I have several machines with bzr 1.18 .. 2.1.2 on them, so I'd better safe than sorry [14:29] still can't upgrade to 2.2 because of problems with bzr.exe and bundled pyqt [14:29] waiting for 2.2.1 [14:30] right, so I'm supposed to release that tomorrow ;) [14:30] I'm using workingtree.list_files to go through files in a checkout [14:30] vi-la! vi-la! vi-la! [14:30] I'd like to inspect the contents of these files [14:31] should I just use normal Python facilities to open the file or is there some more efficient bzr-like way? [14:32] there is method to get the content regardless of workingtree/revisiontree [14:32] also this method supposedly should normalize the file if content filters defined, I guess [14:33] jml: there is get_file_text that you can use with the file_id IIRC + what bialix said [14:34] jml: so it won't be especially more efficient, but easier for you to code I presume [14:35] using the bzr APIs makes it easier to support things like acting against the tip revision of a remote branch, if that would ever be useful to you [14:38] vila: as I understand you will pair with poolie on release tomorrow morning your time? I will hope to see that tomorrow, as fan [14:41] bialix: yeah, that's the plan, I will now go prepare my branches and notes to be ready ;) [14:41] thanks guys :) [14:43] I have a vision of vila bearing bundles of sticks. [14:43] And possibly marching on a castle. [14:44] ...with a big black tower ? [14:46] ... while poolie sneaks with the ring? [14:46] ehhehe. [14:46] my preciouuuus ! That's where it was ! [14:46] :-D [16:02] am i understanding a testament correctly? it only signs the current tree (or of any given revision) but not its history? [16:03] I believe so, you can find more from jam I think on the mailing list. [16:04] knittl: correct [16:04] ok, thanks [16:06] yup, under the topic "security", dated 2009-11-05 [16:06] can you paste a link? :) [16:06] I'm using gmail search, google is a bit crap about indexing the https list archives [16:06] so.. one sec [16:07] https://lists.ubuntu.com/archives/bazaar/2009q4/064053.html [16:07] great, thanks a lot [16:10] Hi all [16:10] hey gary. === Ursinha is now known as Ursinha-lunch [16:31] Heya GaryvdM ! [16:31] Hi bialix [16:31] GaryvdM: have you asked jam about PyQt [16:31] ? [16:31] PyQt downgrade for 2.2.1 [16:31] No - Thanks for the reminder [16:32] also, for 2.2.1, should look at the manifest thing [16:32] probably just want to put the dll in a subfolder and add magic xml. [16:33] jam: We would revert to an older version of pyqt. Please could you install it on the ec2 machine. [16:33] * GaryvdM goes to find the bug an download url. [16:35] I've got several old versions locally, which do you want? [16:36] GaryvdM: http://bialix.com/python/PyQt-Py2.6-gpl-4.5.2-1.exe + http://bialix.com/python/PyQt-Py2.6-gpl-4.5.2-1.exe.asc [16:36] mgz: right, manifest [16:36] Ah - thats it :-) [16:37] I haven't tested it locally yet for simple application. should test tonight [16:37] and bug 632501 [16:37] Launchpad bug 632501 in QBzr "[win32] Subwindows only paint after a keyboard/mouse event. (affected: 1, heat: 10)" [Critical,Confirmed] https://launchpad.net/bugs/632501 [16:38] http://www.no-ack.org/2010/09/complete-guide-to-py2exe-for-pygtk.html <- perhaps a little interesting [16:38] btw, Gary, I'm a bit worried about this one: https://bugs.launchpad.net/bugs/640082 [16:39] Launchpad bug 640082 in QBzr "bzr command output is not shown in qbzr output window (affected: 1, heat: 6)" [Undecided,New] [16:39] bialix: Are you able to reproduce that. I wonder if bzrw.exe is causing that? [16:40] that sounds like a good theory gary. [16:40] Gary, no, I did not try [16:40] why? [16:40] mgz, GaryvdM : ^ [16:40] the standard streams don't point anywhere with WinMain rather than main [16:41] it seems like the bug from Gordon is not involved bzrw.exe [16:42] mgz: I'm sure we should invoke the subprocesses as bzr.exe [16:42] * bialix is checking [16:42] yeah, could be something else. [16:43] mgz: yep, we're forcing bzr.exe even if initial GUI invoked with bzrw.exe [16:44] I did it long ago when I first time started to play with bzrw.exe idea [16:47] bialix: I just tested. The bug happens with bzrw qpull, but not bzr qpull [16:47] bam [16:47] bad [16:47] I have an idea to fix this. [16:48] yes? [16:48] Let me try do a installer build without tbzr (thats where I got stuck...) [16:49] this is just silly: http://lists.sourcegear.com/pipermail/veracity-users/2010-September/000033.html [16:49] Rather than blackhole the std(out/err), just leave them [16:50] GaryvdM: I don't follow [16:51] bialix: what's veracity? [16:51] Glenjamin: new DVCS [16:51] ah yes, thats what the world needs. [16:51] is it sarcasm? [16:52] yes [16:52] also their google-fu sucks [16:52] ok [16:53] didn't they have a non-d vcs already? [16:53] my point not about veracity, but about claim that fast 'hg verify' is what user want to run often [16:53] and yeah, that post is silly, but says something about the different projects [16:53] mgz: yes, replacement for some silly vcs by m$ [16:53] mgz: Yes - it was called Vault. I used it for a while [16:53] i think it was more that the poster cares about the results, and if his users wont ever run it then that VCS is ruled out as an option [16:55] * bialix is trying to read the article mgz gave about py2exe, black page background kills his eyes [16:55] Any idea what's up with this? Unable to copy ownership from '/home/S6B5B28EB.s' to '/home/S6B5B28EB.s/.bazaar': IOError: [Errno 1] Operation not permitted: '/home/S6B5B28EB.s/.bazaar'. [16:55] turn off author style then bialix :) [16:56] mgz: how [16:56] bialix: In Firefox: View > Page Style > No Style [16:56] ...depends on your browser? [16:56] hrm.. I just clobbered permissions and it's working now ;) [16:56] mgz: chrome [16:57] copy-pasting to OOo may help... [16:58] er... chrome doesn't seem to make it easy. [16:58] bialix, the last section talks a bit about manifests, doesn't sound completely correct to me, but might be a starting point. [16:58] ack [16:59] Hmm veracity is free (Apache License). [17:01] mgz: IIRC manifest should be in the same directory as exe [17:01] crazy [17:03] it's changed at least twice since the last time I needed to actually ship any compiled code, so I really have no idea [17:12] So there's only two things veracity does that current tools dont it seems, cross platform C and repo user accounts [17:13] ,gz: http://py2exe.org/index.cgi/Tutorial section 5.2.1 [17:13] mgz: http://py2exe.org/index.cgi/Tutorial section 5.2.1 [17:13] Python is written in cross platform C.... :-) [17:13] their words: "We love Python too, but C is a lowest common denominator that can be ported or integrated everywhere we need to go." [17:14] mgz: or we should add to installer redistributable installer [17:14] i don't quite see how that doesn't apply to python - the only actual argument is speed i'd have thought. but meh [17:14] no, we want the bundled + manifest way [17:14] does bzr use pyrex/pysco at all? [17:17] Glenjamin: we do use pyrex, we don't use psyco [17:18] mgz: then we have to make sure ec2 build host has proprely licensed msvc 2008? [17:18] and then copy required dll as part of py2exe run, oh my... [17:18] I think it did? jam at least had full versions of the compilers I think. [17:19] ec2 has the full versions of the compilers [17:19] jam: can I have access to ec2 when GaryvdM will build an installer? [17:19] i'd imagine throwing pscyo at long running operations might speed them up a bit [17:20] at least read-only? [17:20] bialix: fine with me, I'll need your ip address [17:20] Glenjamin: we rarely have a long running bzr process [17:20] at least from the command line point of view [17:21] and IIRC, psyco doesn't save state between runs [17:21] jam: my ip address... I don;t have dedicated one [17:21] bzr check springs to mind [17:21] it depends on the i-net provider [17:22] bialix: I could potentially use a range, but I can always just set the one you have right now [17:22] I'll also need a username/pass for you, but I can generate that [17:23] I see [17:23] I need to get in sync with Gary [17:25] bye for today [17:34] can anyone suggest a good letter to abbreviate the --no-backup option to revert? === Ursinha-lunch is now known as Ursinha [17:37] Ω [17:48] UnicodeEncodeError: 'ascii' codec can't encode character u'\u03a9' in position 17: ordinal not in range(128) [17:48] :( [17:49] optparse wigs out on unicode it seems === deryck is now known as deryck[lunch] [17:53] Hi roryy. I see you are from South Africa. Where are you base? [17:53] I'm in Randburg. [17:53] hi GaryvdM. In Centurion [17:53] Oh cool. [17:53] not too far :) [17:54] roryy is the one who fixed two bugs in bzr the other day without changing any code at all [17:54] yers. look out for my new book, "zen coding" [17:54] roryy: Are you coming to sfd? [17:55] i don't know what sfd is [17:55] Software Freedom day - I'll find a link with the details . [17:56] ah-ha [17:57] google suggests softwarefreedomday.org [17:57] http://wiki.softwarefreedomday.org/2010/Africa/South%20Africa/Pretoria [17:59] hrm, this w/e [17:59] Yes [18:01] ah - you're doing a python talk [18:01] you work at csir? [18:02] No - I work for lsd.co.za [18:03] an ex-colleague now at csir thinks numpy is awesome === deryck[lunch] is now known as deryck [19:04] hm. it says in the source code of testament.py 'indented-text form similar to log; human readable' [19:04] what text? [20:05] ping LOSA [20:06] hello vila [20:07] mbarnett: 2.3b1 will be released tomorrow, sorry for the late query :-( [20:07] mbarnett: I need a pqm branch and the corresponding instance [20:07] mvo: I just filed a RT ticket for it [20:07] mvo: sry, bad Xchat :-/ [20:08] mbarnett: I just filed a RT ticket for it [20:08] what is the RT #? [20:08] * vila checks mail [20:09] mbarnett: #41434 [20:14] vila: hmm, this is a non trivial change and I am neck deep in another problem. Let me see if I another losa might have time to work on this. [20:15] vila: what time tomorrow will it be released? [20:16] mthaddon: hopefully before 16:00 UTC [20:16] vila: ok, in that case I can do it tomorrow before then [20:16] yay! [20:16] mthaddon: great ! ping me if you need more info [20:17] mbarnett: thanks for the chase ! [20:17] np [20:17] mthaddon: one thing I failed to mention is: which branch should you start with [20:17] vila: ok, please add that to the RT [20:18] mthaddon: I have a question first: can you push this branch later (once) so we start with the "right" revision ? [20:19] vila: I'm not sure I understand the question - can you frame it another way for me? [20:19] mthaddon: [20:20] mthaddon: AIUI, you need to install a pqm instance (handwaving, I've no idea what it requires) including a branch of bzr itself, *and* push this branch to lp [20:20] mthaddon: from there we send requests to the pqm instances to merge new revisions [20:21] vila: let's back up a bit - I was asking about what you mean by "can you push this branch later (once) so we start with the "right" revision" - I understand how to setup a new branch in PQM [20:21] mthaddon: my question is: can you run a 'bzr pull --overwrite' and a 'bzr push lp:2.3' on this branch ? [20:22] vila: this is a new branch, so what am I pull --overwriting? [20:22] mthaddon: a new branch, yes, but with a content [20:22] vila: I'm not sure what that means... [20:22]