[01:14] I never noticed this before: I just branched using bzr-svn and it reported branched through revision 26 of a repository at revision 25. Is it always +1 ? [01:34] db-keen: Are you sure that there aren't 26 revisions somewhere in the repository? [01:34] I'm just heading to bed, but that'd explain it. [01:34] Anyhoo, jelmer is the man to ask. [01:34] Night! [01:35] db-keen: are there 26 in svn. and 25 in bzr? [01:35] (sorry, its later i can't tell if i'm ready it right :P) [01:35] gah [01:35] reading it right, evn [01:36] Odd_Bloke, Jc2k: yeah, I've checked and double checked, 26 in bzr, 25 in svn [01:37] i think if there is a branching operaion (e.g. svn cp from to) then the revision numbers will be different [01:37] svn revnos are repository wide [01:37] bzr revnos are branch wide [01:37] you could for instance have 2000 commits in an svn revno, but one branch with only 10, if you bzr branch that bzr will show 10 [01:38] lifeless: but I have an extra revision in bzr, not the other way around [01:38] oh [01:38] offhand, no idea.perhaps svn is 0-based? [01:40] not in my experience, it isn't [01:41] pretty sure bzr adds the +1 whenever you branch [01:41] perhaps it does, I just never noticed [01:42] I think that is what I read in the docs, not completely sure I remember it correctly though [01:42] 'branch' isn't an action for bzr - two branches one made from another with no commits, have the same revnos [01:43] branch is an action for svn, but it also adds a revno [01:44] perhaps its an svn copy to make a branch? [01:46] that's correct, but how does that fit? [01:49] 'evening [01:50] db-keen: if you branched the root of the svn repository, that's correct [01:51] jelmer: ah, perhaps that's why I never noticed, it's much more common to just branch trunk [01:52] oh wait I am thinking of merge [01:52] when you merge the revno is bumped [01:57] Toksyuryel: technically, it's when you commit [02:00] radix: when you commit obviously, but I was thinking of other times the revno is bumped; a merge is one of those times [02:00] Toksyuryel: no, it's only when you commit. [02:00] Toksyuryel: Just running "bzr merge" doesn't actually modify the branch - it doesn't add a revision [02:00] You have to "bzr commit" the merge for it to actually be added to the branch, in the form of a new revision [02:35] radix: though it'd be nice if merge did commit ;) [02:35] weirdo :P [02:35] you kike unreviewed code that much? [02:35] s/k/l [02:36] lifeless: I recommend dvorak [03:22] anyone know exactly how bzr-svn branches are "supposed" to work? [03:22] chandlerc, how do you mean? [03:22] ie, the whole subversion branching scheme [03:22] chandlerc: See "bzr help svn-branching-schemes" [03:22] i've gotten a weird error with my bzr-svn repository, and i'm wondering if i just set it up incorrectly... (sorry for the bounce.. dunno what my internet is doing) [03:22] i just read that [03:22] ;] [03:23] but how should it look from the bzr side? [03:23] if you'd just like to check out one branch in svn, branching schemes shouldn't be erelevant at all [03:23] currently, all development is done on mainline, but I'm sure that'll change down the road [03:24] do you just arrange the paths locally of your bzr branches the same way as the subversion branches are? [03:24] or does it only look at the url you push to? [03:24] there's no requirements as to how you arrange it locally [03:25] jelmer: here is the error i'm getting: http://pastebin.org/42285 [03:26] chandlerc: That's unrelated to branching schemes [03:26] You seem to be trying to create a new branch in svn [03:26] ok... i'd still like to understand them, but not right now [03:26] and i'm not, i'm running "bzr push" [03:27] but you're pushing into a svn repository? [03:27] yes, but its one i've been pushing too [03:27] to too. ;] [03:27] anybody heard of a clear case plugin for bzr? [03:28] chandlerc: but the location you're pushing to doesn't contain a branch yet apparently [03:28] chandlerc, You may have to use "bzr svn-push" rather than "bzr push" [03:28] since the branch doesn't exist yet [03:28] i'm very certain it does [03:28] bzr is trying to run mkdir since it can't find that directory [03:28] Related branches: [03:28] push branch: svn+https://inc.googlecode.com/svn/parser/trunk [03:28] ... [03:28] # bzr push [03:28] what is the technical difference between pull and merge? [03:29] its the same URL i've been using that command with for 2 months now [03:29] pull follows one path in the dag [03:29] merge combines two branches that are separate in the dag but started from some common point [03:30] does pull autocommit? [03:30] nothing autocommits [03:30] to the local branch [03:30] ok [03:30] pull replaces the current branch tip [03:30] but no new commit object is created [03:30] jelmer: its one of the more bizarre errors because it started happening without anything changing (that I know of...) [03:31] chandlerc: What does "bzr branching-scheme svn+https://inc.googlecode.com/svn/parser" return? [03:31] I find it strange that when I "update" my local mirror of a project that I commit the change [03:31] I've just been entering a "updated from trunk" message. Is that what you guys do? [03:31] unknown command [03:32] jelmer: btw, i'm following the 0.4 release branch, not using fixed releases [03:32] chandlerc: 'bzr svn-branching-scheme..." [03:32] jelmer: Not a branch [03:33] for both parser and parser/trunk [03:33] tethridge: if you have a local mirror, why are you using update & not pull ? [03:34] well, to be honest, I was confused by whether I should do a merge or a pull. [03:34] I guess I should be doing a pull [03:34] chandlerc: hmm, google branch appears to be disallowing operations on the repository root [03:34] I'm not sure why I need a local mirror [03:34] why not just have a task branch for each task? [03:34] tethridge: sure, you can do that [03:34] is it just a speed thing? [03:35] jelmer: would this have been a change on their side to break this, or in how bzr-svn is doing things? [03:35] Is there an easy way to have bzr give me a "bzr log" output with diffs included? [03:35] so if I'm not connected I could create task branches [03:35] jelmer: or in how i'm doing things w/ bzr-svn [03:35] Or do I have to run "bzr diff" over and over and over? [03:35] so nobody knows of a clear case plugin? [03:36] tethridge: well, I don't know why you are doing $whatever you are doing :P [03:36] I think I have it figured out now [03:36] it takes a little bit to switch modes from using something like svn [03:36] brandon_rhodes: I don't think there is at the moment [03:36] tethridge: so I think a more useful pull/merge/update explanation for you is: [03:37] chandlerc: I'm not sure [03:37] 'pull' is used to maintain an exact copy of another branch. [03:37] 'merge' is used to combine someone elses work into your branch [03:37] chandlerc, you may want to run "bzr selftest --starting-with=bzrlib.plugins.svn" to make sure your checkout of bzr-svn works ok [03:37] lifeless: drat. Thanks for the answer, though. :-) [03:38] 'update' is used when two people are sharing a branch (and thus works like update in cvs/svn) [03:38] jelmer: no such option: --starting-with [03:38] chandlerc: s/--starting-with=bzrlib.plugins.svn/^bzrlib.plugins.svn/ [03:38] lifeless, I don't really see a difference between pull and update [03:39] I see what you mean between pull and merge [03:39] tethridge: pull is different if you branch, instead of checkout [03:39] it pulls changes from one branch into another [03:39] tethridge: say there is a branch at URL [03:40] tethridge: no working tree, just a branch. [03:40] ok [03:40] tethridge: to work on this you can either make a new branch, hack, and then integrate your work into the branch (via push, or by doing a checkout+merge+commit) [03:41] tethridge: or you can work directly on the branch, by doing a checkout [03:42] in the latter case you get a local working tree, and unless you specified --lightweight, a mirror of the branch, but bzr keeps it synchronised with URL, any change made locally is made to URL too [03:42] if two people both do 'bzr checkout URL' and then one of them commits [03:42] the other one can't commit - because their local working tree does not contain the changes introduced by the others commit [03:42] to get those changes they do 'bzr update' [03:43] I see [03:43] which synchronises their local working tree version with the current branch tip of URL [03:43] which workflow do most projects use? [03:43] (and if there is a local mirror branch object, it is synced too). Finally, if they had done an offline commit in the checkout, it gets turned into a pending merge. [03:44] that makes sense [03:44] I'm almost finished reading the tutorial, but that helps [03:44] not tutorial, user guide [03:44] generally the gatekeeper for a project - the person running trunk - does all the commits to the trunk [03:45] if there are multiple gatekeepers, then they will have a shared branch -- s ingle branch that the gatekeepers all have checkouts of [03:45] jelmer: i'm really hoping to get a good setup going w/ googlecode btw, hoping to get a not insignificant blog post written up about it [03:45] features are normally done on different branches (made by doing 'bzr branch') [03:45] jelmer: to that end, if there is something that needs to be tweaked on their side, let me know! =] [03:46] I remember reading recently on planet ubuntu about launchpad having something like bugbuddy. For some reason I thought it was something different though. You guys know what I'm speaking of? [03:46] chandlerc: no, I think there's nothing that has to be changed on that side [03:46] I can't find the post now [03:46] chandlerc: I saw a blog from a googler about git-with-gcode [03:46] chandlerc: To be sure you may want to check with a released version of bzr-svn [03:46] chandlerc: I found that amusing knowing what bzr-svn can do :P [03:46] ;] [03:46] the blog post was mentioning how the conversation about whether or not to approve the bug was in launchpad, which sounds like what bugbuddy does [03:47] bpeterson: hi [03:47] lifeless: i'm going to try and do bzr-svn justice, although my usage is light so far, i'm hoping it'll get increasingly heavy [03:47] bpeterson: I'm in sydney, ETIMEZONE last night [03:47] chandlerc: Cool [03:47] lifeless: regarding the TooManyConcurrentRequests on ssh error: #125784 [03:47] yes [03:47] chandlerc: I'm happy to help trying to get it to work for you [03:47] =D [03:48] it's been working great until the other day when this error started showing up [03:48] quite odd [03:49] lifeless: I'm in the US [03:51] anyhow [03:51] I don't have new info for you [03:51] have you tried andrews patch? [03:53] no [03:53] I hope I can merge it cleanly! [03:53] jelmer: http://pastebin.org/42288 [03:54] jelmer: what does openchange use for text indices [03:54] i don't think any of those are my problem... [03:54] lifeless, what would we need text indices for ? We don't have a server yet :-) [03:55] chandlerc, that looks ok [03:55] jelmer: for answering client folder searches [03:55] jelmer: btw, bzr pull fails with the Not a branch error, but no traceback, its just the push that crashes [03:56] jelmer: but i'm really mystified as it clearly is a branch... the parent and push branch... [03:56] chandlerc, please try running with -Dtransport [03:56] k [03:57] which will provide the best information? the push or the pull? or the svn-branching-scheme? [03:57] lifeless: I don't think we do search yet [03:58] k [03:58] jelmer: err... nm, none of those commands gave any additional output wth -Dtransport [03:58] chandlerc, it's writting to ~/.bzr.log [03:59] doh, my bad [03:59] i remember than now of course... ok, which one would you like, or all of them? [04:00] http://pastebin.org/42290 [04:00] that's push, and pull... [04:03] chandlerc, can you try "bzr pull svn+http://inc.googlecode.com/svn/parser/trunk" ? [04:05] http://pastebin.org/42292 [04:09] without the s [04:09] doh [04:09] sorry [04:09] missed that [04:09] yup, that worked [04:09] is it my subversion? [04:11] I suspect a SSL certificate expired or something [04:11] mm, lemme try doing an https something via svn [04:11] python-subversion doesn't pass that information on yet but just returns an error [04:12] bingo [04:12] wow, so simple... [04:13] ahhh, now i get a much more interesting failure [04:13] so how would i set two different branching schemes for two different "modules" in my subversion repo? [04:14] i have svn/parser/{trunk,branches,tags}, but also svn/wiki which doesn't have the {trunk,branches,tags} scheme [04:14] when i 'bzr push' to svn/parser/trunk, it inspects the svn/wiki area, and errors because branches is missing... [04:15] you can't use a different branching schemes within the same repository [04:15] that's... a problem for googlecode [04:16] chandlerc: but every project has its own repository [04:16] yes, but every repository has a "wiki" directory [04:16] with no trunk, branches, or tags [04:16] lifeless: Andrew's patch works for me! Can we get it applied? [04:16] so if the project wants branches... [04:16] The fact that "branches" is required is a bug in bzr-svn [04:17] http://pastebin.org/42294 is the traceback [04:17] but i'd really like to be able to bzr branch 'svn+https://inc.googlecode.com/svn/wiki' ... will that not work? [04:18] chandlerc, bug 235301 [04:18] Launchpad bug 235301 in bzr-svn ""bzr: ERROR: libsvn._core.SubversionException" committing to SVN after top-level "branches" directory has been removed" [Undecided,New] https://launchpad.net/bugs/235301 [04:19] chandlerc, "bzr branch svn+http://inc.googlecode.com/svn/wiki" works fine here [04:19] mk... so i just can't "branch" the wiki root [04:19] which is fine honestly [04:19] wiki root? [04:20] sorry, so i can't bzr branch from that URL, and then svn-push into a different path to create a subversion "branch" [04:20] because it doesn't follow the branching scheme [04:20] you _can_ branch from that URL [04:20] yea, i misspoke, its pushing a new subversion branch that i was anticipating breakage [04:21] no, that shouldn't be a problem either I think [04:21] ? then what does the differing branching schemes do? [04:21] it's relevant for merge tracking [04:22] hmmm, ok [04:22] i think i follow that [04:22] branching schemes should go away in the future [04:22] cools, simpler is better. =D [04:23] I'm considering just hiding them for 0.4.11 since they appear to cause more confusion than they're worth [04:23] hehehe [04:24] any ETA on the bug? its a blocker for me, i'd just like to know. [04:24] additionally, if i can help work up a patch for it, i'd be happy to [04:27] not sure, haven't had time to look into it yet [04:27] I'll see if I can fix it for 0.4.11 [04:28] =D [04:28] it'll sadly break 90% of googlecode projects. [04:29] i'm gonna poke at it some, but i may get lost in the python (not my strongest language) [04:31] If there's anything I can help with, let me know [04:31] bpeterson: could you mention that in the bug [04:31] The sun appears to be coming up here in .ie though, time for some sleep [04:31] g'night * [04:37] beuno: just remembered, you did see my plugin-info plugin announcement right ? [04:37] night jelmer [04:46] sweet, fixed it [04:54] grats [04:54] open sores wins again [05:04] I dislike this time of year [05:04] the Sun stays up and fools you into thinking it's mid evening when in fact it's closer to midnight [05:04] then, after you get a bit of darkness to get a few hours decent work done [05:04] it comes up again [05:04] heh [05:11] back on SST huh ? [05:12] yeah [05:12] clearly my personal timezone has already made the shift from management to development [05:12] even if my employment status hasn't yet caught up [05:15] :P [05:17] which reminds me [05:17] really must write my job description [06:49] hello guys, any help? I tried branching Tortoise for Windows XP by 'bzr branch https://code.launchpad.net/~amduser29/tortoisebzr/trunk' [06:50] after it i issue command 'python TortoiseBZR.py' but got an error saying 'Failed to find bzrlib module! Include the path to bzrlib in PYTHONPATH environment...' [06:51] I set the PYTHONPATH to 'set PYTHONPATH=C:\Program Files\Bazaar\lib' but still it shows that error [06:51] any idea? [06:52] what is in C:\Program Files\Bazaar\lib [06:52] specifically is there a C:\Program Files\Bazaar\lib\bzrlib ? [06:52] first, thanks for reply lifeless. oh no, actually I didn't find bzrlib under ...\lib directory [06:53] I found this library.zip, does it contains the bzrlib? let me check [06:53] if the library has bzrlib in it [06:53] then put the library on the path - C:\Program Files\Bazaar\lib\library.zip [06:53] oh yeah, I found a directory named bzrlib inside that library.zip, so I need to extract it in that directory under ..\lib? [06:54] ah i see [06:54] okay trying... [06:54] I don't use windows [06:54] so can't offer more than generic help for you though, sorry [06:54] markh is doing a lot on this stuff I believe [06:56] it will need to be in your "global" environment, so processes like explorer.exe see the env var [06:56] just setting it at a command-prompt will not work properly [06:56] indeed me too :( my friends wants me to try it in windows. [06:56] markh: what do you mean setting in the command prompt? [06:56] how are you setting the PYTHONPATH variable? [06:56] so something like going to My Computer by right clicking it... blah2... way. [06:57] ok - sorry - I just re-read the above. It sounds like you are having trouble with registration anyway. [06:57] yeah, I set the PYTHONPATH thru command prompt, I set actually under the My computer... Advance... Environment variables but the path is C:\ [06:57] so, once you set the variable, you try and re-execute the 'python' command? [06:57] in a command-prompt? [06:58] speak their name and they appear; the wonders of the net. [06:59] :) [06:59] markh: actually I did just under command prompt, it executse exlcuding that error, but when I hit the carriage return there's a Message box so I just click 'OK' but it does execute [06:59] ah markh it says The procedure entry point ?PyWinObject_AsHANDLE@@YAHPAU_OBJECT.... something like that [07:00] but after clicking ok the TurtoiseBZR.py executes its scripts [07:00] bugger - it sounds a little like the pywin32 install is screwed up :( [07:01] oh - right- you are trying to use tbzr with a binary install of bzr itself [07:01] that might be a struggle :( [07:01] markh: oh, that's a bug? ah what do you mean by that? [07:02] iiuc, tbzr basically expects to be running from a source distro of bzr [07:02] markh: completely separate to the current discussion you might like to send commits for the stuff you are doing to the bazaar-commits list; we encourage contributors to do this as a way of getting visibility [07:03] re: binary install - the 'binary' of bzr has only a small subset of the regular python libraries [07:03] it should be possible to do an add-on installer to add what tbzr needs as well as tbzr itself etc etc, but I don't believe anyone has done that so far [07:03] lifeless: yes, I do need to do that - I'll be making some announcement this week, then next week I go to sydney to work with a few of the guys [07:04] markh: including me ;P. Though the vf merge and stacking will be consuming me [07:04] lifeless: oh cool :) I'm not sure who you even are ;) [07:04] /who lifeless [07:04] non-obvious nicks ;) [07:04] pidgin doesn't know what /who means :) [07:05] oh, right click and info on my nick? [07:05] (gui clients, feh) :) [07:05] :) Ahh - cool - will be good to meet! [07:06] so yeah, we do need better binary "packaging" story on Windows IMO, especially keeping plugins in mind [07:06] yup [07:06] alexander basically designed it all [07:06] and AFAICT his design is sane, but noone stepped up to do actual packages [07:08] I'm wondering if py2exe is a good idea if we really want plugins to be seamless. An alternative is to install a (basically) full stand-alone Python tree, running from source code, with a few front-end .exe files that are actually the entry-points. Kinda 1/2 way between py2exe and a source distro. Possibility is things like eggs etc would work seamlessly [07:08] but I've no firm ideas or opinions [07:08] IIUC, setuptools already provides a tool to generate such executables [07:09] I have a bad opinion of eggs; but perhaps they are the best solution for windows. [07:09] broadly though many plugins have dependencies that are a superset of pywin32+bzr [07:09] e.g. they want 'patch' or 'pysvn' or '...' [07:09] eggs or not, the idea is that it looks alot more like a "normal" python distro, so any way of getting packages on is likely to work, or nearly work :) [07:10] so however we approach it we need the act of 'install plugin X' to also 'install missing deps for X' [07:10] what's cheese? [07:10] ideally yeah, but I fear with py2exe, some plugins would fail to work even if you manually attempted to install all plugins [07:10] sorry [07:11] install all deps [07:11] to my mind, the py2exe thing isn't really a problem as a result, because we can pickup missing standard library modules as part of their dependencies [07:11] markh: are there other causes for failure that I'm not aware of then ? [07:12] what happens when a plugin needs an obscure python lib module we didn't include in the .zip file? Or we just ensure the entire lib is there? [07:12] (I guess I should be more explicit - if we did what py2exe/freeze do on a per-plugin basis, then subtract the set we know ship in the bzr py2exe .zip, we get the extras) [07:12] markh: I uninstalled bzr, the package with Windows_Installer_bzr.exe, then install the bzr-1.5.win32-py2.5.exe [07:13] would that be fine? I try going to command prompt and issuing 'bzr' but it is now not recognize, how to make it recognize or use bzr in that way? [07:13] markh: right, I'm saying that the .zip for a packaged plugin potentially includes std library modules too. [07:13] toyto1: so you need to say "python c:\path\to\bar" [07:14] lifeless: right - if it is OK that only plugins which have had the special "packaging for windows" magic done before they can be used, I'd expect that would work fine. [07:14] markh: what path, only for python? I already set the path PATH=C:\Python25;%PATH% [07:14] windows doesn't look at the shebang line [07:15] sorry - /path/to/bzr [07:15] markh: so I think that installing plugins by 'bzr branch' can only be expected to work for source installs of bzr and folk willing to manually install deps. binary installs (both unix and windows) should work with the recommended $target binary package of bzr [07:15] so "c:\src\bzr\bzr", assuming that file exists [07:15] (the source distro of bzr has the entry point without a .py extension) [07:16] lifeless: right - I guess I need to understand the scope of plugins better [07:17] markh: Its pretty broad. [07:17] markh: Sorry I didn't notice it but found the 'Start -> Program Files -> Bazaar -> Start bzr' then it shows me the command prompt at directory C:\Python25\Scripts [07:17] markh: bzr-svn is one of the most cool plugins I know of. [07:17] (in terms of technology, and in terms of what it allows users to do) [07:18] so setting or adding like PATH=C:\Python25\Scripts;%PATH% would recognize 'bzr' in command prompt, isn't it? [07:18] toyto1: no - the cmd prompt doesn't consider a file named 'bzr' could be executable [07:18] no, windows needs a .bat or .com or .exe file to do that [07:18] setup.py can create a bzr.bat [07:18] uhm [07:18] python setup.py build --in-place [07:19] not sure if that will work, but it is worth a shot [07:19] I don't recall doing any build at all :) [07:19] markh: we don't require one. [07:19] markh: but you can if you wish, to build the C accelerator modules. [07:20] markh: ohmm I have that notion because when I try installing the bzr as package w/o python, then trying at command prompt issuing bzr it works actually but I unisntalled it. let me try [07:20] one advantage of binary installs is that the C modules are prebuilt [07:20] toyto1: yes, the binary install installs a bzr.exe [07:20] I expect that windows users will very rarely run from source unless they are interested in hacking on bzr itself [07:21] yup, me too. But we should keep it easy to do, to make casual contribution straight forward. [07:22] It is far far easier to make the decision to run from source on a linux box. IMO we want to avoid saying "to do X, you must be running from source" on Windows if we can (which isn't to say anyone is planning that or anything :) [07:23] markh: ah its now recognize at command prompt after I append C:\Python25\Scripts at Environment Variables [07:23] right - I guess its finding the bzr.bat [07:23] markh: oh, completely agree, for unix too. source installs should only be needed for development-of-bzr. [07:24] markh: I think every bzr dev will agree :) [07:24] Well, I run source on windows because the official release is broken :) [07:24] markh: and now when I try to python TortoiseBZR.py the error that I told you that shows with 'OK' button is now gone. Thanks guys :) [07:24] cool :) The next thing will be to check it actually works with explorer :) [07:25] kumi_: you have filed bugs? [07:26] Nope, it was that merge bug you called my attention to [07:26] You stated it was already fixed in HEAD so I didn't bother [07:27] markh: ohmm I tried editing a file, then right clicking it then I clicked BZR Diff it says 'BZR Error ... Unknown Diff Command' [07:27] any idea? [07:27] kumi_: oh right [07:27] kumi_: I thought you means some specific to windows errata [07:30] well there is a slight win32 bug I noticed. The included start_bzr.bat in bzr.dev calls bzr.exe, which doesn't exist [07:31] ah interesting [07:31] if there isn't a bug, having one would be good [07:32] where do I file it? [07:32] launchpad.net/bzr [07:34] hrm === abadger19991 is now known as abadger1999 [07:36] toyto1: I'm not sure where that message would come from - its in a message box? [07:37] https://bugs.launchpad.net/bzr/+bug/238277 [07:37] Launchpad bug 238277 in bzr "tools/win32/start_bzr.bat in bzr.dev branch incorrectly calling bzr.exe" [Undecided,New] [07:37] Hi. I'm still trying to convert an svn repo to something else, bzr being the first choice. I have run into a problem, though, that several revisions are broken in the svn repo, and generate errors when one tries to check them out. Does anybody know whether it's possible to make bzr-svn ignore some revisions and how that would work? [07:38] (that is, running bzr branch) [07:39] fdv: oh interesting [07:39] fdv: actual svn corruption? [07:39] lifeless: yes, it is :p [07:40] fdv: I think the usual answer would be to do a svndump, svnfilter them out, then restore the dump [07:40] fdv: if you can't do that, i think you'd need to raise a question on questions.launchpad.net/bzr-svn [07:40] I am sure noone has needed this facility to date; and it has implications with the revision mapping logic [07:40] markh: yeah, python error related. I think it shows that error because the bzr was not recognize under python scripts, what do you think? because after I reinstalled that bazaar package installer w/no python then install the bzr-...pythonwin32.exe it's okay now [07:41] I mean okay that it doesn't show that message prompt anymore. [07:41] uh [07:41] pain :p [07:41] lifeless: ok, thanks, then I might have a solution, at least :) [07:41] toyto1: does it work though? [07:41] but my problem now is using that tortoise with Bzr Commit and Bzr Commit says Uknown command commit/diff [07:42] nah :( even I have already installed the paramiko and pycrypto libraries [07:42] lifeless: yes, I'd think it raises some issues [07:42] my spam filters die on weekends [07:42]