Bazaar

Revisions not showing up on remote server

Asked by jsherk

Ok, this is a rather interesting problem...

Per the tutorial, I setup a shared repository then create a project and check it out. I then add files and commit!

It was working, but all of a sudden, whenever I do a commit it appears to work but when I check the repository on the remote server, the files are not there!

Here is the output from the commit...
Connected (version 2.0, client OpenSSH_4.3)
SSH <email address hidden> password:
Authentication (password) successful!
Secsh channel 1 opened.
[chan 1] Opened sftp connection (server version 3)
Committing to: sftp://<email address hidden>/home/repos/myProjectFolder/
modified myNewFile.tx
Committed revision 5.

You can even watch the progress meter as the file(s) are uploaded!

But when I go to home/repos/myProjectFolder/ it is empty and no files are in it!

Any thoughts or ideas as to what is happening? I am new to Bazaar so all suggestions welcome!

Question information

Language:
English Edit question
Status:
Solved
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Solved by:
Vincent Ladeuil
Solved:
Last query:
Last reply:
Revision history for this message
Best Vincent Ladeuil (vila) said : 		#1

The history of your project is stored in the '.bzr' folder on the server.

The *working tree* is not update so you don't see the files themselves. If you branch from the server, the working tree will be created locally and will contain your modifications.

You don't need a working tree on the server to share a branch with other developers.

If you want a working tree on the remote server but no history try the bzr-upload plugin.

If you want to maintain both a branch *and* a working tree on the remote server, try the bzr-push-and-update plugin.

Revision history for this message
jsherk (jeff-forerunnertv) said : 		#2

Ok, I get it... I was concerned because I assumed (never assume) that the remote server repository should show a copy of the most recent files, but the init-repo command (on remote) included no-trees option which I now see means that there will be no working tree on the remote, and all the revisions are hidden away in the .bzr folder.

Thanks Vincent for explaining that to me!

Revision history for this message
jsherk (jeff-forerunnertv) said : 		#3

Thanks Vincent Ladeuil, that solved my question.