Pushing into shared repository without trees on SMB share is not using repository to store revisions

Nicholas Allen allen at ableton.com
Wed Nov 1 19:14:29 GMT 2006


>
> It shouldn't, so we should figure out why it thinks it needs to do that.
> I assume you did something like:
>
> bzr init-repo --no-trees Z:/mounted/network/share/
>   
Actually I created the shared repository on my hard drive and then I 
copied it to the network share using explorer.
> Or are you using //host/network/share (I thought bzr currently didn't
> work properly with those paths)
>
> Also, are you sure that the repository path is visible in the filesystem?
>   
Yes it is. We all have rights to write there and it is where I copied 
the repository. Also if I create the branch in that directory and then 
push to the created branch that works. So the push to an existing 
location uses the repository just fine.
> Like it could be that you did "bzr init-repo --no-trees /srv/repo" and
> then are only exporting "/srv/repo/branches" => Z:/ or something like that.
>
> The repository needs to be visible to the client.
>   
It is.

> It is *also* possible that we have a bug if the repository is at the
> root of a directory. I thought we squashed all of those bugs, but we did
> have them in the past.

I am still using the 0.12 RC. Could it be a bug fixed in 0.12?

Nick




More information about the bazaar mailing list