/srv/irclogs.ubuntu.com/2012/05/06/#bzr.txt

dOxxxwhen you make a new commit, you're adding a connection from the current revision to the new commit00:00
dOxxxand then the branch's tip pointer is updated to point at the new commit00:00
dOxxxnote that the revision checked out in the working tree is not necessarily the same as the branch tip00:01
gwalbut with bzr update I jump to the tip?00:01
dOxxxyes00:01
dOxxxthat updates the working tree to the same state as the tip revision00:01
dOxxxconversely, bzr update -rN will update the working tree to the state at revision N00:02
gwalso my tip revision is revision 5 which is in the repository at the remote location indicated with sftp://00:02
dOxxxand in the case of the push you did earlier, it add new revisions but couldn't do the equivalent of `bzr update`00:02
dOxxxyes00:02
gwalI use the remote location exclusively as a repository ... and I just did a bzr pull on this sftp:// location from a different computer which gave me the latest revision (5)00:03
gwalI think I remember why I can't use bzr+ssh: the remote location doesn't have bzr installed00:05
dOxxxah yeah00:05
dOxxxthat does make things a little harder00:06
gwaleverything seems to be there though .. in the remote sftp:// location and my current pull of revision 500:06
dOxxxif you don't need the working tree in the remote location, you could try `bzr reconfigure --branch sftp://...` to get rid of the working tree00:08
gwalwhat does it mean to get rid of the working tree?00:09
dOxxxit means there is no checkout of the latest revision, it's just the .bzr directory with the revision data00:10
dOxxxI'm not sure if the reconfigure will work over sfpt though00:11
dOxxxsftp*00:11
gwalok ... hang on00:11
gwalno .. it complains that sftp://location/.bzr/ is not a local path00:12
dOxxxyeah I guess it can't do it remotely00:12
dOxxxyou'd need bzr on the remote machine to do it00:12
gwalyea I understand ... not sure I can get bzr on there though00:13
gwalbut in itself this isn't inherently bad is it?00:13
dOxxxno, you'll just get the warning every time you push00:13
gwalok, I can live with that00:13
gwalthanks so much for helping me with this! guess it all just boiled down to my local box holding on to its lock on the remote repository00:14
dOxxxyah00:14
dOxxxthe rspush may not have released it properly when it encounted the divergent branches00:14
dOxxxencountered*00:14
gwalyea might be that00:15
dOxxxany particular reason you were using rspush instead of push?00:15
gwalas far as I understand, push doesn't transfer my local files to the remote location?00:15
dOxxxerr...00:16
gwalnot true?00:16
dOxxxwhat exactly do you mean by "my local files" ?00:16
gwalby that I mean, I bzr add something.c locally, bzr ci this change and when I do a bzr push it doesn't seem to copy those files over to the sftp:// location00:17
gwalsorry, I'm new to bzr so this may sound stupid00:18
dOxxxthat's because it can't update the working tree over sftp00:18
gwalah00:18
dOxxxthe revision with that change has been pushed00:18
dOxxxI'm guessing rspush was able to do it though?00:18
gwalyes it was00:18
dOxxxinteresting00:18
gwalok I see your point, usually bzr push to a bzr+ssh location would do a remote bzr update after my local bzr push?00:19
dOxxxyeah00:19
dOxxxbecause it can run bzr on the remote machine00:19
gwalyea ok, that makes sense now00:19
dOxxxor at least I believe that's what it does :)00:19
gwalwell it would make sense at any rate ;)00:20
dOxxxI usually use tree-less remote repos00:20
dOxxxsince I don't need the working tree on the remote machine, just want to store the revision data00:20
gwalso essentially the kind I'm trying to use on my box that has no bzr installed?00:20
gwalthat's exactly what I want. how do you go about this yourself?00:21
gwalwhat I do is bzr init local_dir and then bzr rspush local_dir sftp://location00:21
gwal(after a bzr ci)00:21
dOxxxI use launchpad primarily so it sets that up automatically but I think if you did `bzr pusg --no-tree remote-loc` for the initial push it would create a tree-less repo00:21
dOxxxpush*00:22
gwaloh ok, I'll need to try that00:22
dOxxxah the help for bzr push says:00:23
dOxxxThe target branch will not have its working tree populated because this00:23
dOxxx  is both expensive, and is not supported on remote file systems.00:23
dOxxx 00:23
dOxxx  Some smart servers or protocols *may* put the working tree in place in00:23
dOxxx  the future.00:23
dOxxxI think "remote file systems" means protocols like sftp00:23
dOxxxso I'm guessing rspush created the working tree initially00:24
dOxxxanyway, sounds like you're sorted out?00:24
gwalyea it must've ...00:24
gwalyea man I think I am. I'll look into the --no-tree option although my current bzr version doesn't seem to know this option00:25
dOxxxah :P00:25
gwalmaybe I'll need to update my bzr version00:25
dOxxxyou may not even need that option00:26
dOxxxif use push as the first command to create the remote repo00:26
gwalgood call ... I'll give that a shot. when I read the help last time around (what you pasted above) I read the line about the working tree not being populated as meaning that my files won't get transferred00:28
gwalthanks to you though I kind of understand what that means now ... so will try push from now on as initial push00:28
dOxxxglad to help00:28
gwalthanks again and take care00:29
dOxxxcheers :)00:29
Noldorinhey fokls03:07
Noldorini'm trying to push a branch to my FTP server...03:07
Noldorini uncommitted locally than made a few more commits03:08
Noldorinbut it says there are no new revisions to push when i try to push it from locally to the server!03:08
Noldorineven when i do --overwrite it still says this03:08
Noldorinvery weird03:08
Noldorinany thoughts?03:08
LarstiQNoldorin: are you pushing to the right location?12:41
=== yofel_ is now known as yofel
trebor_homehi. i am new to bzr (cvs-user). are there texinfo files to download for 2.1.x (debian)?23:44
jelmertrebor_home: I'm pretty sure we don't have any info files in the debian package23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!