[00:12] morning spiv, jam, igc ;-) === mw is now known as mw|out [00:53] boo merge --uncommitted doesn't work over ssh [00:54] i'm not surprised, though [00:56] heh === emgent is now known as bakunin === bakunin is now known as emgent [01:45] beuno: hi [01:46] igc: ping [01:47] hi poolie [01:47] spiv: I think we should talk abot get_data_stream [01:47] tim just forwarded me the patch to fix https://bugs.edge.launchpad.net/launchpad/+bug/181157 [01:47] Launchpad bug 181157 in launchpad "Product series should have a status (like distro series)" [Medium,Confirmed] [01:47] lifeless: ok [01:47] spiv: I think I know where a bunch of problems are comng from [01:47] can you look at that quickly and tell me either any other values you think should be allowed, or anything else that comes to mind [01:47] poolie: sure [01:48] spiv: voice or irc? [01:48] lifeless: whichever suits you best [01:48] hello spiv, lifeless [01:48] I'm happy either way. [01:48] ringing you [02:01] ok, false alarm; its not the cause of the bugs we're seeing [02:01] hi poolie [02:02] igc: can you please just look at that quickly now, i want to reply to tim [02:02] commenting on the bug right now [02:02] oh cool, thankyou [02:04] poolie: done [02:04] I think we want one more status now - Pending Release (or Frozen to mirror the distro name) [02:05] "Future" or Experimental might be good as well but I'd leave it out until we explicitly need it [02:05] i.e. some project asks for it [02:19] poolie, hey [02:22] hi beuno [02:22] igc, hm [02:22] so this is like a subcategory of active development? [02:22] oh i see [02:22] so 1.4 would be in that state now, and 1.5 would be active development? [02:26] poolie, just got home, so I'll be on and off while I run errands. Do you want to talk now or would it be better for you later on? [02:33] poolie: that's right [02:53] hi all. is there a list of what environment variables/bazaar.conf options are available? [02:55] also, is last push path remembered like last merge path? (eg per repository?) [02:55] Kamping_Kaiser: bzr help env-variables [02:55] Kamping_Kaiser: bzr help configuration [02:55] spiv, ok, thanks [02:56] Kamping_Kaiser: (also at http://doc.bazaar-vcs.org/latest/en/user-reference/bzr_man.html#configuration-settings and http://doc.bazaar-vcs.org/latest/en/user-reference/bzr_man.html#environment-variables) [02:56] Kamping_Kaiser: the first time you push, it remembers the path. You can overwrite the remembered path by passing "--remember" to push. [02:57] spiv, sounds the same. thanks again :) [02:57] Not a problem [02:59] of the two help outputs i assume configuration is authoritive? it lists items env-variables doesnt [03:02] Hmm, that's a bug. [03:02] But afaik, all the items in the 'configuration' help topic do exist. [03:04] BZR_PROGRESS_BAR BZR_SIGQUIT_PDB BZR_PDB are listed in config but not env-var [03:05] bzr1.3, btw. [03:06] they both give quite different output it seems [03:10] "DEFAULT" isnt the only header currently supported by bzr is it? (ALIASES works too?) [03:16] Kamping_Kaiser: you mean sections in the bazaar.conf? [03:16] spiv, yeah. [03:19] * jml frowns [03:20] ubuntu is telling me that I can't upgrade bzr without removing bzrtools [03:20] Kamping_Kaiser: sounds like a bug in the docs. [03:20] this seems to happen a lot. [03:20] spiv, ok :( [03:23] jml: its a ppa feature [03:24] lifeless: I'm sceptical. [03:24] Yeah; when is a 1.4-compatible bzrtools/bzr-svn likely to be uploaded there? [03:24] Kamping_Kaiser: I've sent a quick patch to fix it to the list [03:24] Kamping_Kaiser: thanks for letting us know [03:25] jml: "feature" [03:25] jml: what happens is that the bzr < current upload is immediately removed [03:25] jml: hilarity then ensues [03:27] and there's no workaround? [03:27] spiv, NP. i was worried you were going to tell me to write the patch myself ;) [03:27] Kamping_Kaiser: you can if you really want to ;) [03:27] jml: You can just not upgrade bzr. [03:28] spiv, i really dont. *grin*. [03:29] RAOF: this a bit of a pain. [03:29] The current bzrtools depends on bzr < 1.4~. The PPA contains bzr 1.4rc1, and 1.4rc > 1.4~ [03:30] jml: Does current bzrtools work on 1.4? If it does, you probably have the permissions to upload a bzrtools to the PPA with relaxed dependencies. If not, we're preventing you from accidentally breaking bzrtools. [03:32] RAOF: bzrtools is version locked [03:32] RAOF: apt can resolve conflicts better if 1.3 is kept in the archive [03:33] RAOF: Not to mention the fact that even if started at the same time, bzrtools 1.4 and bzr1.4 are unlikely to enter the archive at the same time. [03:33] abentley: in fact they can't [03:34] abentley: as there is a build sequence constraint [03:34] Okay, *very* unlikely :-) [03:34] Maybe I'm spoilt by aptitude. That handles this case just fine. [03:34] :P [03:35] It handles the case where bzrtools requires bzr 1.3 and only bzr 1.4 is available? [03:35] abentley: But bzr 1.3.1~rc1 *is* available. [03:35] abentley: it offers different resolutions [03:35] RAOF: not in the ppa its not [03:35] Just not from the PPA. [03:35] But that's not jml's problem. [03:36] jml: what release are you on, and do you have backports enabled? [03:36] lifeless: hardy. [03:36] lifeless: not sure how to check for backports. [03:36] Does'nt matter, there aren't any yet. [03:37] RAOF: would for gutsy :P [03:37] jml: for reference grep backports in /etc/apt/sources.list [03:37] lifeless: Yeah, but I know he's on Hardy :) [03:45] poolie: ping; removing deprecated methods question on the list; would like a reply :P [04:09] Im working on a bug Mentored by LastiQ who is in bed...could anyone help for a WorkingTree4 question? [04:09] sorry..LarstiQ Wouter [04:10] sure [04:11] I am working on adding a switch which will output relative paths ../path/to/file/filename.py instead of the stripped out paths from bzr stat (and the like) [04:12] unfortunately, (as far as i can see) at the point the stripped out paths are output, there is no indication (like a global varable) where the working path is [04:12] aka WorkingTree4.basedir [04:13] fyi, this is a learning project for me...been doing c,c++ for 15 year...python for 15 days [04:17] this is the 'bug' https://bugs.launchpad.net/bzr/+bug/30159 [04:17] Launchpad bug 30159 in bzr "paths are always from root of branch" [Low,Confirmed] [04:18] yeah IMO...there may be to many side-effects changing the default behaviour [04:19] but i was thinking "bzr status --relative" would probably work [04:20] simple change if i know the basedir when in delta.py [04:28] jdobrien: look at status.py [04:28] yeah [04:28] jdobrien: iter_changes outputs paths from the root fo the tree [04:29] problem is, it strips out the basedir [04:30] yes, thats the correct internal representation [04:30] I think you want to do the change at output time only [04:30] yeah [04:30] so in ChangeReporter [04:30] and the Delta class for old-style status [04:31] k, which still brings me to the question...is the basedir in a global setting so i could calculate the relative path base on cwd? [04:32] it's not passed into change reporter...i could always get it again [04:33] I would add a method on Delta to set the cwd [04:33] and a parameter to ChangeReporter I think [04:34] no there is no global, because in general it doesn't exist [04:34] oh crap [04:34] on windows for instance its not per-thread [04:34] on most unixes its per-thread [04:34] i missed it...it's passed into show_tree_status [04:34] <---------------idiot [04:34] but when used as a library cwd is not ours to fool with [04:35] wt is passed in, but not cwd [04:35] the paths are already relative to wt [04:37] in this instance, wouldn't it be safe to get get the actual path (wt.basedir + path) and calc relative path based on cwd [04:38] on output only [04:38] you need to pass the path to normalise against in though [04:38] yes [04:38] as in, getcwd() isn't something library code should be calling [04:38] no [04:39] to get the abspath, use wt.abspath(relpath) [04:40] thanks [04:41] not sure how this would work/break if basedir was not a physical dir [04:41] :P [04:41] thanks for the help [04:42] bill this hour to wouter [04:42] bug 218023 [04:42] Launchpad bug 218023 in pqm "Use textwrap.dedent to make multiline strings more readable" [Undecided,New] https://launchpad.net/bugs/218023 [04:51] yay tests pass [04:52] time for a beer [04:55] maybe in the evening :P [04:55] 11:55 here USA FL [04:56] ITYm 2355 :P [04:56] 1355 here [05:20] time for /wave [05:20] poolie: good progress, I have the output stuff ~= correct [05:21] adapters tomorrow [05:21] thanks for the help [07:07] can bzr count the lines in a diff? i have a command "$(bzr diff $1 2>/dev/null |wc -l)", and i'm wondering if |wc -l is strictly necesary [07:09] I usually use "bzr diff | diffstat" myself :) [07:10] there's a "bzr diffstat" plugin, too, for the minimal typing saving [07:11] lifeless: it appears in 'bin/pqm' there is an expectation that --config must be set, but the code seems to indicate that it is to specify a non default config file [07:16] lifeless: aarrrggghhhh [07:16] lifeless: I found out why I thought that [07:16] * thumper wipes the unclean feeling away === doko_ is now known as doko [08:45] New bug: #218068 in bzr-svn "Pushing to SVN, SubversionException: "File ... already exists"" [Undecided,New] https://launchpad.net/bugs/218068 [09:28] * igc dinner [09:47] are there any good tutorials out there for using bzr for website development? Google's failing me on this. [09:48] hm i'm not sure [09:49] people seem to do it a lot [09:51] I'm not a dummy, but I can't wrap my head around how it works [09:52] must be a gui tool I can use to walk me through it, should I get a gedit extension or something? [09:54] bzr-gtk? [10:07] jimcooncat: can you please send mail with your questions to bazaar@lists.canonical.com and i'm sure someone will help you out [10:08] unfortunately i have to go in a sec [10:08] thanks poolie [10:50] hello is there a way to set a file to be treated as a binary? it seems bzr diff detects one of our pdf as text due to some ascii lines in the beginning of it. [10:51] New bug: #218115 in bzr "corrupt: attempt to add line-delta non-delta knit" [Undecided,New] https://launchpad.net/bugs/218115 [11:01] visit0r: that's a really good question and I'm surprised I don't know the answer [11:03] i seem to recall there was a flag to merge that allowed it to resolve conflicts better. i cant see that option looking at its help now - have i missed it or was it removed? [11:10] hello [11:10] how does bzr-svn work with bzr branches? [11:19] quicksilver: ok, I'll open a bug [11:28] Stavros: how do you mean? [11:28] bob2: if i have many branches on my local disk, do i have to merge before committing back to svn? does it make svn branches? [11:31] New bug: #218128 in bzr "some binary files detected as text: provide a way to flag files binary?" [Undecided,New] https://launchpad.net/bugs/218128 [11:32] Stavros: you can push from a bzr-svn bzr branch to svn, yes [11:34] yes, but how will this affect my other branches? [11:34] will i need to pull to them again? === mrevell is now known as mrevell-lunch === Pilky_ is now known as Pilky === mrevell-lunch is now known as mrevell [13:10] night === mw|out is now known as mw [13:56] Kamping_Kaiser: there are a couple, --reprocess and --lca are the recommended ones [13:57] (you can also use "bzr remerge --lca foo" to not have to redo the whole merge again) [13:57] Kamping_Kaiser: --reprocess reduces the size of the 3-way conflict chunks by finding lines that are common to both sides [13:57] --lca uses a different merge algorithm that usually does better when you have a criss-cross merge, or other more involved history. [13:58] jam, then --reprocess is probably the one thats good for aliasing to merge [13:58] Kamping_Kaiser: correct, I've often thought it should be default [13:58] I think the only reason it wasn't is because it conflicts with --show-base [13:58] (if you remove the common lines, then you don't have the context to show the base lines correctly.) [13:58] bzr conflicts drive me crazy :( i prefer svns. if --reprocess makes it less anoying i'll be a verry happy person ;) [13:59] Kamping_Kaiser: try it out and let me know. I think most systems use the "--reprocess" form by default [14:01] jam, not sure when i'll face a conflict next ;) but i'll try to remember [14:02] thanks for the help :) [14:30] New bug: #218191 in bzr "paramiko.SSHException: Server connection dropped" [Undecided,New] https://launchpad.net/bugs/218191 [15:05] New bug: #218206 in bzr "Pending-deletions error message" [Undecided,New] https://launchpad.net/bugs/218206 === bigdo2 is now known as bigdog [15:15] jam: hi! I was reading your lines above about --reprocess and --lca; from them I guess that using --reprocess and --lca in the same "bzr merge" command does not make sense? [15:17] So.. Suppose I wanted to make a "bzr sync" command which is like pull or push, whichever it finds is appropriate. Is there some example command plugin, or some doc somewhere that explains how to make a plugin? [15:17] guilhemb: I'm not sure, but I think that the style of how --lca works means that there is no need to --reprocess [15:18] You are welcome to try both [15:18] I don't think it will break anything, just that --lca doesn't leave any lines to be reprocessed [15:19] jam: ok, thanks === pmezard_ is now known as pmezard [15:31] jam, guilhemb: Yes, --lca implicitly does --reprocess. [15:31] abentley: thanks for the info [15:33] guilhemb: np [15:38] I'm working on a project with one other developer. We both work remotely on multiple laptops and move around a lot. I've run 'bzr init-repo ./' and 'bzr init' in the project directory on our ssh server, so we can both run 'bzr checkout sftp://ourserver/path/to/project/' to get a local checkout from which commits can be made to the central repo. [15:39] How can/should I create a centralized 'working' branch (not sure about my terminology) where I can commit broken code from machineA so I can 'bzr update' on machineB tomorrow and keep working, and then commit to our shared repository when my new feature is working correctly? [15:52] I think I've made progress here. I can checkout from the shared repository to my own centralized...Thing, create a branch of my centralized Thing on each of my dev systems, and 'bzr push sftp://server/Thing' from each centralized system. Then I can 'cd Thing; bzr update; bzr commit' on the server. [15:59] moquist: You shouldn't need a commit after an update (unless you've changed the content) [16:29] Scripting question... Given two branch objects, is there an easy way to tell if one is an ancestor of the other? [16:29] I.e. if I should push/pull in one direction [16:32] LeoNerd: well, 'bzr missing' I thought would give that info [16:33] I think it might be slower than it needs to be ATM [16:33] be back in a bit [16:33] Yes.. sorry.. by "scripting", I mean "I'm writing a plugin" [16:33] (to anyone else): I can tell if they're identical by comparing branch1.last_revision == branch2.last_revision [16:34] I presume one is an ancestor of the other if one's last_revision appears somewhere in the history of the other? [16:36] is 1.3.1 due to go into hardy? [16:37] sabdfl: I thought it was already there [16:37] or it may have been that the single patch that went in to 1.3.1 was added to the hardy package. [16:38] ah, it's 1.3.1~rc1-0ubuntu1, and there were no code changes between the rc and final for 1.3.1 [16:40] james_w: can we fix the version number, then? [16:41] probably, I'll submit a patch for approval from the release team. [16:46] LeoNerd: Ancestry, not history in particular. [16:46] Right.. [16:46] Should I look for the code that implements the "bzr missing" command, perhaps? That sounds likely to be doing similar tests [16:47] Probably not. [16:47] If you just want to know whether one branch is the ancestor of the other, you can determine that cheaply. [16:47] I.e. with Graph.is_ancestor or Graph.heads [16:54] Well, I'm writing a command that's basically missing => {push/pull/complain/nothing} [16:59] thanks james_w, please let me know the RM response and status [16:59] sure === Mez is now known as fishfinder === fishfinder is now known as Mez [17:02] So... perhaps it's sufficient to see if either branch can map the other's head revision into a revno [17:02] ? [17:03] Since at least one is guaranteed to fail [17:04] LeoNerd: get the two tip revisions, compare them for equality => do nothing [17:05] a in b's revision_history() => pull [17:05] b in a's revision_history() => push [17:05] otherwise error [17:05] I think that should work [17:05] Yes.. it was the being "in the history" that confused me [17:05] I've already done the first equallity one [17:06] ah, no, sorry, that only looks at mainline revisions. [17:07] but I don't think you can't pull if your head is not a mainline revision of your parent, no? [17:07] s/can't/can/ [17:10] hi dato [17:11] if your parent merges from you, then the tip of your branch will be the right hand parent of the paren't branch's tip, and you would be able to pull wouldn't you? [17:31] abentley, thanks for the amazing response to the show-author-on-commit patch, I haven't responded as I'm working on it, but I really appreciate how thorough it was :) [18:00] * lamont considers campaigning for bzr 1.3.1 in hardy, wonders what the support level from this channel is [18:00] rather, how much support for the campaign he can count on... [18:01] lamont: see a bit of backlog above, between james_w and sabdfl [18:02] james_w: I'm not sure anymore :) (sorry, I missed your line at the time) [18:03] james_w: if 1.3.1~rc1-0ubuntu1 == 1.3.1-1, I'd be happy to do the upload, assuming it's approved... [18:04] http://paste.leonerd.org.uk/?show=2184 <== my "bzr sync" command plugin. Anyone any comments? [18:06] lamont: the diff is trivial, I'm testing now, and then I'll seek permission from the release team [18:06] lamont: thanks for the offer though, I may well take you up on that if it gets approved [18:07] james_w: no worries - it's blocking some testing that I'm doing, since them machines in question have bzr_1.3.1-1~$mumble installed [18:07] and the end result is a very annoyed and failing do-release-upgrade [18:08] james_w: ah, right, it does that thingy of making your last commit not-mainline [18:08] james_w: my technique is to just upload and then explain why. :-) [18:09] lamont: oh yeah, I'd forgotten everything was frozen so that was possible [18:09] :-D [18:09] lamont: this upload would be 1.3.1-0ubuntu1, would that solve your problem? [18:09] is this an upload to debian, or to ubuntu? [18:09] no. [18:09] hm [18:10] >>1.3.1-1~CAT.6.06 [18:10] I guess I could upload to debian [18:10] I was going for Ubuntu, but we could upload to Debian and sync [18:10] I didn't, because 1.4~rc1 was around the corner [18:10] hrm... [18:10] dato: if you've got the time, that would be great. [18:10] dato: are you the normal uploader to debian? [18:10] but rc1 turned out unsuitable for upload, so I ended up uploading none [18:10] lamont: yes [18:10] sync is pain these days... [18:11] how about 1.3.1-1 to debian, and 1.3.1-1build1 to ubuntu and lots of handwavy bits about why 'build' is correct [18:11] we could fake-sync, or -1build1 one it [18:11] ^5 [18:11] fakesync would be bad. [18:11] but we want the orig.tar.gz files to be the same both places [18:11] yeah, that would work, it may make the release team think about it a bit more though. [18:11] true [18:12] nah - I'm happy to deal with release team... they're used to my craziness [18:12] :-) [18:13] lamont: are we best to just subscribe the release team to the bug and then deal with the actual upload when we have the ACK? [18:14] oh [18:14] I can provide the upstream diff that we want to incorporate. [18:14] first bzr upload with python 2.5 [18:14] not that it really matters [18:14] dato: it's been 2.5 on Ubuntu for a while, so it should be fine. [18:14] is there abug? [18:14] if we just upload 1.3.1-1build1 to hardy, we don't need a bug [18:14] a non very eloquent one: bug 218257 [18:14] Launchpad bug 218257 in bzr "Update bzr package to a non-release-candiate version number" [Undecided,New] https://launchpad.net/bugs/218257 [18:15] I was going to expand on it when I had the patch. [18:15] this would be my first upload-new-upstream-version-to-main-during-final-freeze upload, so I'm still feeling my way around [18:16] that works. the other big decision-fork is that if the bits are in debian within the next 45 min or so, there's a very good chance they'll make today's dinstall run, if not -> tomorrow. to sync them, it's best if the mirrors have had a chance to do their thing [18:16] if we just upload to hardy, then it's click-to-approve for the release manager [18:16] lamont: it'll be <45min [18:17] wow, what's all this crap pycentral now spits [18:18] dato: it doesn't spit it, it excretes it [18:19] james_w: if we know that the same .orig.tar.gz will be used by both uploads, then we can actually upload ubuntu ahead of debian if we want, and I can get back to testing,... :-) [18:19] dato: is that the "diff" stuff? [18:19] ye [18:20] s [18:20] it looks like debugging output to me [18:20] in the ideal world, we want dato's package for debian, with about 5 lines of change in changelog (for -1build1) and an upload... [18:20] james_w: are you core-dev, or who does your ubuntu uploads? [18:20] yep [18:20] ah, cool [18:20] we need to sync first though? [18:20] not if we're really really really diff from 1.3.1-1 in only the changelog [18:20] ah, no, I'm not core-dev, it was your previous statement I was agreeing with [18:21] ok. /me is happy to sponsor... so when you/dato are happy with 1.3.1-1 for debian, if I could have a copy of it, I'll smack it into hardy [18:23] I'm testing 1.3.1 now, so when dato's got the package I should have finished testing [18:24] \o/ [18:32] good lord [18:32] my wireless here sucks [18:34] uploaded nevertheless [18:37] dato: thanks. [18:37] dato: got a pointer to your bits? [18:38] yes, http://people.debian.org/~adeodato/tmp/2008-04-16/bzr/ [18:38] :-) [18:38] lamont: it's passed a selftest here, and stood up to a few minutes use [18:38] unfortunately I don't have any real work to do in bzr at the moment, so I can't test that. [18:39] james_w: that's more than my testing before I deploy...:0) [18:40] :-) [18:41] lamont: would you like me to do anything with the bug, or is it superfluous now that we have you to prod the release team? [18:42] oh. whichnumber? [18:44] 218257 [18:56] stupid wireless [18:56] james_w: the upload will close it [18:57] sigh. diff orig.tar.gz than the bazaar-vcs download page. [18:58] uh [18:59] dato: or did you already upload? [18:59] lamont: I used a pristine tarball [18:59] nfc what poolie used then [18:59] https://launchpad.net/bzr/1.3/1.3.1/+download/bzr-1.3.1.tar.gz <-- link obtained from http://bazaar-vcs.org/Download [18:59] lamont: err [18:59] hrm [18:59] lamont: when james_w said 1.3.1~rc1-0buntu1 is 1.3.1-1 [18:59] no matter - I'll make sure your .dsc unpacks. [18:59] he meant there were no code changes [18:59] not that the tarball were identical [19:00] poolie used the rc1 tarball, I guess :) [19:00] 5a2160e057d79288c186c42567aa0dc2 ../bzr_1.3.1.orig.tar.gz [19:00] he used _that_ one. :-) [19:00] that's the one I uploaded [19:01] oh right [19:01] 2c560167aea6c8bde7cfaf7883d267dc ../../bzr_1.3.1.orig.tar.gz [19:01] yeah, sorry, there was a NEWS entry, and the version number was changed, but there were no changes to the meat of the code. [19:01] off by one error [19:04] testbuilding nwo [19:08] dh_python -pbzr [19:08] dh_python: Doing nothing since dh_pycompat exists; dh_pysupport or dh_pycentral should do the work. You can remove dh_python from your rules file. [19:08] heh [19:08] yay cdbs [19:09] in my mind cdbs is still filed under "slightly less evil than dbs;" [19:13] * lamont goes to talk to the nice folks in #ubuntu-release === mvo_ is now known as mvo [19:39] Folks, I'd like to try the fastimport plugin with the cvs2svn plugin, but there's no documentation on the options to use with cvs2svn. === kiko-fud is now known as kiko [19:40] Do I output to a dumpfile? [19:40] I've seen this: includes an option now for the required output format. Python. But I don't know what that option is. [19:52] james_w: it'll get accepted post-RC :-( so fridayish sometime [19:54] cws2svn --dumpfile=app.dump ;; then cat app.dump | bzr fast-import - [19:54] Doesn't seem to work. [20:43] lamont: ok, thanks [20:44] tolstoy: does cvs2svn output in the fast-import format? [20:46] beuno: You're welcome. Hope it's helpful. === kiko is now known as kiko-phone === mw is now known as mw|food [21:10] hey [21:10] i have a project that consist of many small projects [21:10] how would i best organize it with bzr [21:11] in git there are superprojects [21:11] you can link to other repositories in them [21:16] wow, this channel is brimming with life :) [21:30] trepca: sure is [21:31] trepca: bzr will have nested trees that are like subprojects, but they are not ready yet [21:31] hi lifeless [21:31] ok, thanks [21:32] i could create a huge repository as in SVN that would hold all those projects ... but that is probably not optimal for bzr ? [21:34] yeah, that's not great [21:35] james_w: Sorry, I was out to lunch! I don't know if it outputs in that format. No command-line switches suggest that it does. [21:35] james_w: But the docs at bazaar-vcs suggests that it does. [21:36] tolstoy: I don't think that it does [21:36] ah, maybe I'm wrong, have you got a pointer? [21:36] Hold on.... [21:37] http://bazaar-vcs.org/BzrFastImport/FrontEnds [21:37] I'm using the macport version, which might be the problem. [21:39] Hm. I'm using version 2.1.0, but there's a 2.1.1 available as a tarball on their website. [21:41] "includes an option now for the required output format" [21:41] Right. [21:41] "now" suggests it is new, so the new version may be needed [21:41] And that's all I can find on the subject. === mw|food is now known as mw [21:45] Hm. I wonder if the Mac DMG install of BZR contains the bzr subversion plugin. === kiko-phone is now known as kiko [21:50] i does not [21:50] it [21:50] Alas, no, it seems not to. [22:17] how to configure bzr-email to send emails? [22:18] 'bzr help email' should contain enough info [22:18] thanks [22:40]