checkout and pull on readonly branch

[Erik Bågfors]

On 9/25/06, Robert Collins <robertc at robertcollins.net> wrote:
> On Thu, 2006-09-21 at 07:44 +0000, William Dode wrote:
> > On 21-09-2006, Erik Bågfors wrote:
> > > On 9/21/06, William Dode <wilk-ml at flibuste.net> wrote:
> > >> Hi,
> > >>
> > >> I just see that we can checkout --lightweight a readonly branch. But
> > >> after that we cannot pull to stay up to date. Is it a missing feature ?
> > >
> > > Not really, try "bzr update".  What you are trying to do is to pull
> > > something into the branch that you have checked out.  Since you do not
> > > have write-access to it, that's not going to work.
> > >
> > > To update your working tree, use "bzr update"
> >
> > right, but it doesn't work now :
> >
> > wilk at domino:/vrac/python/bzr.dev$ bzr update
> > bzr: ERROR: Cannot lock: transport is read only: <bzrlib.transport.http._pycurl.PyCurlTransport url=http://bazaar-ng.org/bzr/bzr.dev/.bzr/repository/>
>
> both pull and update normally are able to alter the branch that is being
> pulled into/updated. This is not the case with a lightweight checkout,
> so the usual decorator based locking behaviour fails.
>
> I'm filing a bug now - thanks for the report.

Well.....

If I do "bzr checkout sftp://...../master slave; cd slave; bzr pull
http://....."
I do expect both "slave" and "master" to be updated with what I pull,
since I'm "bound" to that branch.

If I do not have write access to "master", I expect the pull to fail.

/Erik
-- 
google talk/jabber. zindar at gmail.com
SIP-phones: sip:erik_bagfors at gizmoproject.com
sip:17476714687 at proxy01.sipphone.com