[00:05] abentley: Thanks for the review. :) I'll resubmit tomorrow. [00:05] Odd_Bloke: np [00:07] Odd_Bloke: in fact, KeyError is at least a plausible exception for name_hook to throw. === jamesh_ is now known as jamesh [02:16] does anyone have a clue how to do log-type operations without a whole heap of whole-history operations yet? [02:31] New bug: #200412 in bzr "Undescriptive error message when user isn't part of LP team." [Medium,Confirmed] https://launchpad.net/bugs/200412 [02:35] hi, i ran the command " bzr init-repo sftp://username@silenceisdefeat.org/~/repo" and bzr was hung up without any output. I use bzr 1.2 standalone win32 version under cygwin bash shell. How can I debug my problem? [02:36] New bug: #200413 in bzr-webserve "Rss feeds should show revisions" [Undecided,New] https://launchpad.net/bugs/200413 [02:39] have a look in ~/.bzr.log [02:39] thx === bpeterson changed the topic of #bzr to: "http://bazaar-vcs.org/ | Bazaar 1.2 is out! | https://launchpad.net/bzr/1.2/1.2" [03:02] This is the content of .bzr.log: [03:02] bzr arguments: [u'init-repo', u'sftp://username@silenceisdefeat.org/~/repo'] [03:02] looking for plugins in C:/Documents and Settings/jerryc/Application Data/bazaar/2.0/plugins [03:02] looking for plugins in C:/Program Files/Bazaar/plugins [03:02] looking for plugins in c:\Program Files\Bazaar\lib\library.zip\bzrlib\plugins [03:02] Looking for plugins in 'c:\\Program Files\\Bazaar\\lib\\library.zip\\bzrlib\\plugins' [03:02] Names in archive: ['__init__.pyc', 'launchpad/__init__.pyc', 'launchpad/account.pyc', 'launchpad/lp_indirect.pyc', 'launchpa [03:05] I can not figure out from this content. should i install python and bzr source to debug? [03:06] red: Certain -D options might help. [03:06] I dunno. [03:07] ok, I will try _D [03:08] you need a -Dxxx option, but I can't seem to find the list of them anymore [03:08] bzr help global-options [03:08] I dunno which one would help though. [03:08] thx [03:09] None of them seem relevant to me. [03:09] red: Do other things over sftp work? [03:10] red: I'd guess it has to do with prompting you for your password. [03:10] But I dunno. [03:11] is this command correct " bzr -Derror init-repo --no-tree sftp://chenbin@silenceisdefeat.org/~/repo"? I tried "sftp://username:passwd@url [03:11] there is no prompt for password if i run "sftp://username@url" [03:12] Yeah, but -Derror isn't helpful here.. [03:12] Does ~ work? [03:12] I've never used it. [03:12] On sftp it does; bzr+ssh doesn't. [03:12] (but don't worry, that'll be fixed a release or two after the smart server is added) [03:13] I just tried it on both sftp and bzr+ssh and it seemed to screw up badly. [03:13] real command is "bzr init-repo sftp://username@silenceisdefeat.org/~/repo" [03:14] Never mind, I'm an idiot. [03:14] I created repo at first on remote server [03:15] I cannot install software on silenceisdefeat.org [03:15] (I was using "sftp//" instead of "sftp://".) [03:15] does 'ssh username@silenceisdefeat.org ls ~/repo' work? [03:18] sh username@silenceisdefeat.org "ls ~/repo" does work. [03:18] ssh username@silenceisdefeat.org "ls ~/repo" does work. [03:20] I've got it [03:21] this seems a bug of bzr [03:22] I don't know why, but on the dos command shell, I succeeded and got the password prompt. in the cygwin, there is no password prompt and the whole program is hung up. [03:23] As I mentioned af first, I install bazaar 1.2 standalone version. But I run the bzr command in cygwin bash shell. [03:33] I reported the bug at https://bugs.launchpad.net/bzr/+bug/200436. Thank you all. [03:33] Launchpad bug 200436 in bzr "bazaar 1.2 (standalone) failed in cygwin shell" [Undecided,New] [04:14] New bug: #200436 in bzr "bazaar 1.2 (standalone) failed in cygwin shell" [Undecided,New] https://launchpad.net/bugs/200436 === doko_ is now known as doko [08:59] hi guys , where I can set what revision that I want to branch? [09:13] Hopefully he figured it out... [09:15] hi... I'm just learning bzr. how would I find out when (which revnos) was a particular file changed? [09:15] muszek: bzr log file? bzr annotate file? [09:15] Peng: thanks [11:21] dato: ping [11:30] jelmer: pong [11:32] dato: I was wondering if you could sponsor a bzr-dbus upload? [11:40] jelmer: yes, I noted it in my TODO when you sent mail to -maint [11:41] dato: Cool, thanks. [11:41] jelmer: I just need to find a bit of time for it :) [11:41] :-) [11:41] We missed at the sprint last week! [11:42] * dato wonders if "you" or something else is missing above [11:42] uhm, yes :-) [11:43] *g* === mrevell is now known as mrevell-lunch === mvo_ is now known as mvo === mrevell-lunch is now known as mrevell [13:46] any idea when bzr-svn for bzr 1.2 will be available? [13:49] uniscript: Hopefully somewhere at the end of this week [13:49] OK great ta === FreeNode is now known as herb [14:01] jelmer: I'm up to date with http://people.samba.org/bzr/jelmer/bzr-svn/stable/, and I'm getting "using experimental bzr-svn mappings; output may change between revisions" . . . there's nothing to worry about as far as normal usage (esp. with respect to data-loss), is there? :-) [14:03] nevans: you should not be using it for production type data but a release instead [14:04] New bug: #200569 in bzr "[PATCH] v1.2 setup.py fails under python 2.3.5" [Medium,Confirmed] https://launchpad.net/bugs/200569 [14:07] jelmer: thanks. I'll switch to one of the release branches. [14:12] jelmer: should I delete my svn-cache or my bzr repo? could running off of the newer code have "corrupted" either of them so that the older release branch of bzr-svn won't know how to cope? [14:16] New bug: #200575 in bzr ""Address already in use " crashes smart server" [Undecided,New] https://launchpad.net/bugs/200575 [14:17] nevans: In theory, yes. In practice however, there haven't been any regressions recently afaik [14:21] jelmer: s/adaption/adoption/ [14:22] LarstiQ: ? [14:23] jelmer: the title of your blog post :) [14:23] doh! [14:39] jelmer: I forgot to ask you last week. What's the bzr-svn release that corresponds to bzr 1.2? [14:39] AfC: There is none yet [14:40] I had meant to release it last week but was distracted by other things [14:40] I'm sitting here at the GTK hackfest listening to these guys next to me absolutely slaughter themselves fighting with git usage. I'd like to just go "and here it is in bzr" but I kinda need to have my shit together first [14:40] jelmer: certainly [14:40] jelmer: no worries [14:41] * AfC wonders if his distro has backported the subversion changes that bzr-svn relies on. [14:41] AfC: what distro are you running? [14:41] I hope so. I had a very poor time trying to get subversion working built from source. [14:41] jelmer: Gentoo [14:41] AfC: There is an overlay (not sure what that means exactly) that has them [14:41] https://edge.launchpad.net/bzr-gentoo-overlay [14:42] jelmer: overlay is the equivalent of "well, I posted a patch". Until it's into Gentoo's official tree it's meaningless. [14:42] ah, ok [14:42] It's like expecting people to depend on a .deb that's not official. It may exist, but it's not usable without a fight [14:43] Don't worry, it'll all be fixed when svn 1.5 is released... I'm sure it'll happen in a week or two, no problem. [14:43] fullermd: oh really? That's encouraging [14:44] [Part of this is that someone did an import of GTK using launchpad, but that's really not any use so long as the upstream project is using Subversion] [14:44] Well, it's been a couple weeks out for, like, 18 months now... [14:44] I suppose I could risk trying that overlay. I don't know who wrote it, what's in it, or whether it is trustworthy. [14:44] fullermd: that too [14:45] Now if launchpad used bzr-svn, THAT would be useful. [14:46] Using other overlays in Gentoo is pretty easy, IIRC. [14:46] More like adding something to your /etc/apt/sources.list. [14:46] I didn't say it wasn't easy. I said it wasn't sound [14:46] Ok. [14:47] [and even more pragmatically, in my experience when someone does a private overlay the problem goes away for them so they no longer are incented to push their work to upstream (in this case, the distro proper) - which means the problem remains unsolved for everyone else] [14:48] [so, for me to go and use that overlay would mean I would no longer be agitating for the problem to be fixed, and the quality level for everyone else remains low. Far better for bzr if the necessary fixes get into Portage officially] === bigdo2 is now known as bigdog [15:10] AfC: LP does SVN imports... [15:11] Odd_Bloke: but you don't mean "using bzr-svn to publish a branch which is actually backed by an external project that is in Subversion" do you? [15:11] AfC: Probably not, but I'm not sure I understand exactly what you mean. :) [15:12] import (as I understand it) is a one way transform for a project that is switching VCS. bzr-svn allows you to use Bazaar against an upstream project that uses (and will continue to use) Subversion [15:12] what I was just suggesting would be interesting & cool would be [15:12] AfC: LP does tracking imports, so that any new upstream revisions are mirrored. [15:12] if Launchpad hosted the bzr-svn infrastructure and sync'd against upstream [15:12] Hm. [15:13] AfC: it has been discussed in the past [15:13] jelmer: I didn't really think it was likely to be an original idea [15:13] I'm probably only sensitive to this because it's taken a while for me to get bzr-svn up and running [15:13] AfC: However, the restrictions that bzr-svn puts on the way conversions are done make it impossible to be used by launchpad [15:14] Well, I'm just as happy to leave them out of it. [15:14] AfC: bzr-svn uses deterministic revision ids so can't change the way mappings are done without changing the revision ids [15:14] jelmer: oh? What restrictions are these? [15:14] jelmer: interesting [15:15] abentley: I meant the referential integrity has to be maintained [15:15] Why is that a problem? [15:17] it makes it impossible to change the mappings halfway through [15:17] without changing revids [15:17] if I add support for svn:keywords in bzr-svn now, I need to change the revision id prefix it's using [15:18] wheras launchpad could just add support for it and add it in the new revisions it imports without users getting funny "Branches diverged" errors [15:20] Otoh, deterministic conversions are useful, and Launchpad might be willing to put up with that upgrade pain for such a gain. [15:21] abentley: True, but afaik that was the reason launchpad decided against bzr-svn a while back [15:22] abentley: btw, did path tokens get discussed later in the week during the sprint ? [15:22] No, they were never discussed. [15:22] Could someone vote 'Resubmit' on http://bundlebuggy.aaronbentley.com/request/%3C20080310005229.11704edf@lapbert.oxbridgetech%3E for me? [15:23] Odd_Bloke: Just submit the fixed version. [15:23] abentley: :-( [15:24] abentley: Sure. :) [15:24] hmm, I think this is the first year I haven't brought up revision id aliases [15:24] :-P === weigon__ is now known as weigon [16:01] Earlier I started with putting an existing project folder under version control (init, add, commit), now I'd like to have that folder as a repository and move the existing files to a subfolder ('main') to allow me to create branches in separate folders next to the 'main' subfolder. How should I proceed? Is it possible to do this afterwards and keeping the current revisions? [16:04] Prodoc: Create a separate shared repo (using 'bzr init-repo repo') and 'bzr branch repo/main'. [16:06] Odd_Bloke: performing 'bzr branch repo/main' before or after I copied the existing project (including the .bzr folder I assume), to the 'main' folder? [16:07] Prodoc: The 'bzr branch' will do the copying, as well as using the shared repository. [16:09] so I just have to perform the 'bzr init-repo repo' on the current version controlled folder? [16:10] Prodoc: It's best to do it outside of the version-controlled folder, to avoid confusion. [16:10] You can move the repository (and it's branches) where you want later. [16:12] ah yes, now I see what you mean, cheers [16:14] ow, and the existing revision history will be retained? [16:14] yes [16:14] hi poolie [16:18] How is bazzar diff from git ? [16:18] How is an orange different to an apple? [16:19] ok I will get to the point. [16:20] git has a lot more citric acid? :p [16:20] I found these distributed scms suffer compatibility between windows and linuxes [16:20] not really distribted. [16:20] Also bear in mind that while we're bzr users in here, many of us won't know git that well [16:20] Or at all [16:21] basically how easy to get my revisions between windows and linux machines. [16:21] so I don't have to worry about setting up ssh or starting a deamon to pull/push to and from. [16:21] afaik, bzr still has better windows support than git [16:21] Bazaar has pretty good Windows compatibility, but not many of the developers concentrate on Windows, and it has case-insensitive issues. [16:21] The repo format is portable, the program is portable... to my knowledge though, bzr won't itself handle linefeed issues [16:21] Peng: indeed [16:22] LeoNerd: we want to do that though [16:23] I don't mind even if would handle ascii files as binary objs. [16:23] The current workaround is using a text editor that doesn't suck. :P [16:23] Oh, that's not necessarily a requirement. People could even use emacs... [16:24] or vim. [16:24] tsk :P [16:24] (g)vim can easily cope with either line format anywhere [16:24] But.. I imagine you're going to be storing source code, etc..? [16:24] the problem is other tools, like, say, patch [16:24] Make sure the compiler/interpreter on each platform can cope [16:24] LarstiQ: patch will happily convert line endings [16:25] luks_: does it nowadays? It sure used to convert everything to native on windows. [16:25] at least the one on windows does [16:26] anyway, for interested people, http://bazaar-vcs.org/SprintLondonMarch08/Brainstorms and http://bazaar-vcs.org/LineEndings would be starting points for implementing it [16:26] I just need a simple tool to efficently transfer versioned binary diffs between windows and linux and not worry about setting up a whole lot of servers doing push and pull it should simply ask during syncing chose the remote and local when conflicts arrive. [16:26] Pengwn: that's as trivial as running "bzr send" [16:27] LarstiQ: the problem with implementing in is that bzrlib reads from the working tree all over the source base :( [16:27] there is no central place for such operations [16:27] when I do bzr send from a window machine how would the other window machine recieve it? [16:28] luks_: reads or writes? [16:28] both, and md5sums [16:28] luks_: the idea is to have a transform layer via tree operations [16:28] I've tried it a few months ago, but I gave up as it would mean refactoring quite a lot of code [16:29] Pengwn: "bzr send" works over email [16:29] luks_: did you document your experiences somewhere? [16:29] so yuou get the patch by mail, and then "bzr pull" it [16:29] LarstiQ: nope [16:29] ok [16:29] just in my private and probably already deleted branch :) [16:29] doh :P [16:30] to put it a little simpler I would like to have versioned files with unison syncing and samba transparency. [16:30] any tool that would remove the trouble of setting up samba would be awesome. [16:30] not sure if that's simpler [16:30] * luks_ doesn't know that means :) [16:31] Pengwn: bzr is a version control tool, not a backup solution and not directory sync tool [16:32] if your only intention is to move files between machines, bzr or any other vcs is probably not going to make you happy [16:32] yep that's what I am looking for then a versioned diff backup solution able to sync from any linux window system. [16:35] unison ? [16:35] I've only used it between Linux boxen, but I know it's designed for Lin/Win or Win/Win too [16:37] problem with unison it goes thru the whole directory structure and takes to much band width this way git handles better with sha1 comparison but pulling and pushing to linux is ok but to windows is a pain in the *** [16:38] Umm... [16:38] unison runs on both machines [16:38] It does local timestamp and checksumming, nowhere near the network [16:39] You have to run it _on_ both machines, though [16:39] Running it on one side to do a local-to-SMB isn't going to gain you anythingh [16:42] how hard is it to setup bazar to do bzr send and get ? [16:43] Pengwn: pretty easy, assuming there is a reasonable way to send mail from the source [16:43] like either sendmail or an smtp server [16:44] can I unison to sync directories then use bzr on top of it ? [16:44] I mean bzr locally on windows and linux boxes? [16:45] sync directories or repos i.e. [16:45] another option would be "bzr serve" if you can temporarily open a port on one of the machines, and they are accessible from each other [16:45] bzr serve is a python server? [16:45] or c server? [16:46] Python [16:46] almost everything in bzr is python [16:46] is bzr server a push pull thing or I can commit and checkout from it like cvs? [16:47] both [16:47] cool. [16:47] but it doesn't handle any authentification [16:47] fine with me. [16:47] atleast plain text passwords? [16:47] No [16:47] nope, nothing [16:48] Use bzr+ssh if you want security [16:48] ssh is not for windows :) [16:48] There are SSH daemons for Win32 AFAIK [16:48] another big problem otherwise would have stuck to git. [16:48] You can certainly use windows as a client to bzr+ssh [16:49] https://code.launchpad.net/~parker-friikz/bzr-auth/trunk [16:49] * awilkins has done it [16:49] can I limit the clients to bzr serve? [16:49] client connection i.e.? [16:49] say to one. [16:49] heh [16:50] maybe I should continue with that :P [16:50] Pengwn: are you planning to use it on a central server? [16:50] Parker-: you shuold! :) [16:50] is it usable yet? [16:50] mostly yes [16:50] :D [16:51] but.. it works [16:51] Pengwn: if it's a central server and it runs any unix based system, you can just use bzr+ssh [16:51] which works fine on windows as a client [16:52] need to leave train.. laters.. [16:53] Ok this is the scenario. I work on windows , linux boxes all over the place I want to commit/checkout on any box and before leaving in the evening to save my code/commits on any spare box available at the client side. I work mostly in a vpn so I can connect to any box but don't want to go thru headace setting up ssh/samba what ever crap. [16:56] Pengwn: if ssh is installed on your target psuh box, your headache is limited to generating keypair for yourself and adding it to the authorized_keys list in your /home/.ssh folder on the target [16:56] And then running pageant / putty on the Win32 bopx [16:56] or just to use password :) [16:56] luks_: Ah, well, I learned to do it before bzr had auth callbacks :-) [16:57] It finally pushed me over to using PK auth for everything, none of my boxen support password anymore. [17:00] Anyway, yes, Pengwn, you just need plink (from putty suite) to use win32 as an ssh client. Small, no-install executable. [17:00] actually, you don't [17:00] Other client in mind? [17:00] the bzr installer comes with paramiko installed [17:00] which provides ssh support without any external dependencies [17:01] * awilkins ... is out of date because of the auth-callbacks thing [17:01] I needed something with an ssh-agent [17:01] paramiko _can_ use putty's ssh agent :) [17:02] awilkins: the headace there is I am working on a windows box all day after ftping my repo now I come to my hotel room connect to slow vpn and save changes to a windows laptop. ftp is again damn slow and remote windows box doesn't have ssh setup. [17:03] Have to go catch train back later [17:04] Pengwn: bzr will download only as much as it needs, which usually isn't that much after one working day [17:04] you mean with bzr serve? [17:04] or bzr-ssh? [17:04] any transport [17:04] you would simple replace the 'ftping my repo' step with 'bzr push' [17:04] and then 'bzr pull' on the laptop [17:05] cool. [17:05] I will try that out then. [17:05] you can use sftp://, ftp://, bzr+ssh://, bzr:// [17:05] thanks luks. [17:06] so bzr is well supported on windows and linux very well? [17:06] I mean my bzr serve should hang I am screwed again. [17:07] bzr works equally on windows and linux [17:07] the only things that are different are caused by missing features of either OS [17:07] the best windows scm server is p4s.exe. perforce's. Never hanged on me maybe once. [17:08] basically I have to say how well is python on windows : ) [17:08] but probably the best you can do is to always push the changes to one server and use that server from each machine you are working on [17:09] that's the problem. servers sometimes in different location country and bandwidth sucks. [17:10] Pengwn: it's not clear to me exactly what problem you are trying to solve. [17:11] admin problems automation problems etc. etc. huge repo like 2GB and need to transfer around on different client places. [17:13] yeah maybe I should stip down the take away the exe/binaries but damn lazy to do that so code and installables all in one repo.:) [17:33] New bug: #200599 in bzr "exception error "Connection reset" caused by push" [Undecided,New] https://launchpad.net/bugs/200599 === FreeNode is now known as herb [18:00] what the difference between init and init-repo? [18:00] Bloguero__Connor, init-repo is a shared repository [18:01] so, init is only for private? [18:01] Bloguero__Connor, I wouldn't call it private, it's jsut for one repository [18:01] the otbher one shares the revisiones [18:02] so it saves space if you're branching the same repo [18:02] Er. init-repo creates a shared repo; init creates a branch. [18:02] wich one saves space? [18:03] and init will create a non-shared repo if you are not in a shared repo when you call it. [18:03] Bloguero__Connor, it depents on what you're going to do ;) [18:04] "bzr help repositories" [18:08] OK. If someone creates a sharedrepo at http://someplace.com/repoX, and I want to colaborate, should I use "bzr branch http://..."? [18:08] Bloguero__Connor, share repos are only relevant locally [18:08] why? [18:08] Bloguero__Connor: A 'shared' repo is only called 'shared' because multiple branches use it to store revisions. [18:09] Those branches share the repository. [18:14] If I have sftp access to the shared repo, what diff make if it is local or in another machine? [18:15] Bloguero__Connor, none [18:16] beuno, you said before that share repos are relevant only locally [18:16] Bloguero__Connor, right, because they save space when creating new branches in the shared repo [18:16] they re-use the same common revisions [18:16] so you don't duplicate them [18:16] but it makes no difference when branching out externally [18:18] Bloguero__Connor: I think you may be being confused by the use of the word 'repository'. In bzr, a repository is _only_ a place to store revisions. Branches are what make sense of these revisions (and are what you can share in the way you seem to mean). [18:18] so share repo is called shared because it shares files between branches, not because it shares branches between users. [18:19] Bloguero__Connor: Yes. :) [18:20] guys back. [18:21] I did bzr serve --directory=c:\myhome [18:21] how do i access or sync with this from another windows machine? [18:23] Pengwn, bzr://host/branch [18:23] I am getting errors saying bzr: ERROR: not a branch "C:/myhome/" [18:24] Pengwn: Is C:/myhome/ a branch? [18:24] using bzr pull bzr://141.144.64.18:4155/myhome [18:24] nope directory. [18:25] Pengwn: That'll be your problem then. You can only pull from branches. [18:26] is branch nick and branch one and the same? [18:27] Pengwn: no [18:27] ok how to create a branch and serve it? [18:27] there's no default branch? [18:28] Pengwn: "cd branch; bzr serve" [18:28] or "bzr serve --directory=c:\location\of\branch" [18:29] Pengwn: bzr init & bzr add (or be more specific here) & bzr commit [18:29] cd c:\myhome; bzr init ; bzr add; bzr commit ; bzr serve ?? [18:30] then on my other machine bzr pull bzr://141.144.64.18:4155/myhome ?? [18:30] Pengwn, that's right, if you just want to have one branch, yes [18:30] you probably don't want to do add your whole home directory, though [18:31] luks_, it's a windows home, it's probably empty :p [18:32] james_w, does bazaar still use absolute paths with the smart server, or deso it do relative now? [18:32] beuno: in what sense? [18:32] beuno: I don't know I'm afraid. [18:32] if I do bzr serve --directory ~/src/bzr ; then bzr branch bzr://larstiq/bzr.dev works [18:32] LarstiQ, that's it [18:33] thanks :D [18:33] beuno: how is Prague? [18:33] james_w, absolutely great. Having a chance to get back some brain-functions working :p [18:33] :-) [18:34] james_w, tomorrow is your last day at previous work? [18:34] james_w: hey, meant to ask the other day: are you coming to debconf? [18:34] Does anyone know who admins planet.bazaar-vcs.org? [18:34] LarstiQ: same for you [18:34] beuno: yes it is \o/ [18:34] dato: I wasn't planning on it, but it sounds like there may be a chance that I am now. [18:35] james_w: ok :) [18:35] james_w, so from when on can I start complaining about Ubuntu doing things wrong to you? [18:35] beuno: um, you'd be better of complaining to someone else? :) [18:36] oh damn do i have to bzr init on both machines? [18:36] Pengwn, no, just do branch instead of pull [18:36] (once, to create the initial branch) [18:36] dato: I think it would be great if at some point you could send a message to the list outlining the features that made git so compelling for you. [18:37] dato: I realise you have mentioned a couple already, which is better than most people who just say that there are things without really pointing them out, so thanks for that. [18:38] ok, I could think about them [18:38] * dato takes a note [18:38] dato: thanks. [18:42] dato: I had been filling in fields in penta slowly, I need to complete that. [18:46] Wow bzr is cool on windows. [18:46] hope it's equivalently cool on linux :) [18:47] by next best tool :) [18:47] Pengwn, like everything else, even cooler :p [18:48] beuno: now now :P [18:48] but seems I have to go the physical c:\myhome directory and do bzr pull bzr://hostname:4155 [18:48] * beuno goes back to his corner and sits back down again [18:49] the bzr://hostname:4155/myhome doesn't work. [18:49] says c/myhome/ is not a branch. === ja1 is now known as jam [18:50] jam: o/ [18:50] Pengwn: what does `bzr info` say when in c:\\myhome ? [18:51] Odd_Bloke: hi [18:51] jam: Thanks for the reviews earlier. :) [18:51] np, trying to get the merge queue down to something reasonable [18:52] Odd_Bloke: did you have a good train journey back home? [18:52] jam: Yeah, managed to get a seat and everything. :p How was your flight? [18:52] branch root: . [18:52] Related branches: [18:52] parent branch: bzr://141.144.65.18:4155/ [18:53] hi jam. [18:53] The flight was rather uneventful, they managed to arrive 30-min early, but then take >1hr to get my luggage unloaded [18:53] hi james_w [18:53] Perhaps the luggage arrived on time. :p [18:54] Pengwn: and you did "cd c:; bzr serve" first? [18:54] (if you did cd C:\myhome, then the appropriate branch is "bzr branch bzr://hostname/" [18:54] no cd c:\myhome; bzr serve [18:54] Since paths are relative to the cwd [18:55] otherwise it would be branching "c:\myhome\myhome" which obviously doesn't exist [18:57] hey thanks [18:57] bzr://hostname:4155/myhome works [18:57] LarstiQ: ok :) [18:57] after cd c:\ ; bzr serve [18:58] how the hell it bzr know c:\myhome is the bzr root without being in it? [18:58] Pengwn: Because that's where you ran 'bzr serve' from? [18:58] Peng: it maps URLs to file system paths [18:58] erg. pengwn [18:59] ahh got now cd c:\myhome; bzr://hostnaem:4155/ fails :) [19:02] The logic is then If bzr serve find the BZR ROOT client cannot use the path info. If bzr serve doesn't find the BZR ROOT the client has to tell it where to find it. :) [19:04] Pengwn: bzr serve doesn't care where it is run from, it will take an incoming request and then look in $serveroot + $relpath [19:04] Pengwn: so yes [19:05] hello jam [19:05] Pengwn: you could also (on a unix system) do `bzr serve --directory=/` and that way expose your entire filesystem, but you probably don't want that [19:05]