No WorkingTree exists error over ftp

Asked by Horacio Caniza on 2009-03-24

I am trying to set up a bazaar repository in a ftp server hosted by godaddy. Even though I follow the tutorial without problem when working on my local machine I cant get it to work over ftp.
It goes like this:
bzr init aftp://<email address hidden>/bazaardirectory/workingdirectory //all directories exists
bzr add aftp://<email address hidden>/bazaardirectory/workingdirectory
bzr: ERROR: No WorkingTree exists for "aftp://<email address hidden>/bazaardirectory/workingdirectory".
Since the latter works perfectly on my local machine I am guessig it has to do with godaddy, however, i dont see why anything should go wrong with something so simple.
Just as aditional info, if I ftp://domain.info from the console, i can see the .bzr directory and everithing in it.
Thanks for the help.

Question information

Language:
English Edit question
Status:
Answered
For:
bzr Upload plugin Edit question
Assignee:
No assignee Edit question
Last query:
2009-03-24
Last reply:
2011-03-16
Robert Collins (lifeless) said : #1

On Tue, 2009-03-24 at 02:45 +0000, Horacio Caniza wrote:
> New question #65148 on bzr Upload plugin:
> https://answers.launchpad.net/bzr-upload/+question/65148
>
> I am trying to set up a bazaar repository in a ftp server hosted by godaddy. Even though I follow the tutorial without problem when working on my local machine I cant get it to work over ftp.
> It goes like this:
> bzr init aftp://<email address hidden>/bazaardirectory/workingdirectory //all directories exists
> bzr add aftp://<email address hidden>/bazaardirectory/workingdirectory
> bzr: ERROR: No WorkingTree exists for "aftp://<email address hidden>/bazaardirectory/workingdirectory".
> Since the latter works perfectly on my local machine I am guessig it has to do with godaddy, however, i dont see why anything should go wrong with something so simple.
> Just as aditional info, if I ftp://domain.info from the console, i can see the .bzr directory and everithing in it.
> Thanks for the help.

You need to do the init + add + commit steps locally.

Once you have done that you can do
bzr push aftp://<email address hidden>/bazaardirectory/workingdirectory
which will push your bzr history there.

You probbably want the bzr-upload plugin though, if you are publishing a
website.

-Rob

Thank you very much Robert. I had the wrong workflow.. i am working
alone, but with a centralized server, so technically solo but not quite
the same.
Thanks again.

Robert Collins wrote:
> Your question #65148 on bzr Upload plugin changed:
> https://answers.launchpad.net/bzr-upload/+question/65148
>
> Status: Open => Answered
>
> Robert Collins proposed the following answer:
> On Tue, 2009-03-24 at 02:45 +0000, Horacio Caniza wrote:
>> New question #65148 on bzr Upload plugin:
>> https://answers.launchpad.net/bzr-upload/+question/65148
>>
>> I am trying to set up a bazaar repository in a ftp server hosted by godaddy. Even though I follow the tutorial without problem when working on my local machine I cant get it to work over ftp.
>> It goes like this:
>> bzr init aftp://<email address hidden>/bazaardirectory/workingdirectory //all directories exists
>> bzr add aftp://<email address hidden>/bazaardirectory/workingdirectory
>> bzr: ERROR: No WorkingTree exists for "aftp://<email address hidden>/bazaardirectory/workingdirectory".
>> Since the latter works perfectly on my local machine I am guessig it has to do with godaddy, however, i dont see why anything should go wrong with something so simple.
>> Just as aditional info, if I ftp://domain.info from the console, i can see the .bzr directory and everithing in it.
>> Thanks for the help.
>
> You need to do the init + add + commit steps locally.
>
> Once you have done that you can do
> bzr push aftp://<email address hidden>/bazaardirectory/workingdirectory
> which will push your bzr history there.
>
> You probbably want the bzr-upload plugin though, if you are publishing a
> website.
>
> -Rob
>

Petr Viktorin (encukou) said : #3

If you want to keep the project history on the remote server, you want the Centralized (or Centralized with local commits) workflow from the User guide.
Just remember you can't have a remote working tree, use the upload plugin for publishing changes.
Also, keep in mind that if you push to a publicly available location, anyone will be able to checkout your code, so be careful if you have database passwords or such in the history.

You can also keep the history on your local machine, and only `bzr upload` the actual files to the server. Use the Solo workflow for that.

If your problem is solved, would you please mark the question in Launchpad as Solved?

Xavi (xavidp) said : #4

Hi all:

I had a similar problem when I pushed my branch to a server over bzr+ssh, and the copy in the remote server only had the .bzr folder in place, but not any of the files from my local machine that I committed, etc.
When attempting to do 'bzr update' I got the message:

bzr: ERROR: No WorkingTree exists for "file:///path_to_folder/.bzr/checkout/".

The solution to this issue is provided at the Bazaar (wiki) FAQ:
http://wiki.bazaar.canonical.com/FAQ#How%20to%20recreate%20working%20tree%20in%20a%20branch%20that%20was%20pushed%20over%20sftp?

In short:
just do a: 'bzr checkout .' inside that remote folder, and since then, 'bzr update' will update the remote working tree.

Btw, and fyi: the plugin push_and_update is very handy to easu the task to push revisions to remote hosts over ssh!
https://code.launchpad.net/bzr-push-and-update

Cheers

Can you help with this problem?

Provide an answer of your own, or ask Horacio Caniza for more information if necessary.

To post a message you must log in.