2009/8/10 chris bedford <chris_at_buildlackey.com>
> Hi, Stephen..
> thanks for your response.
>
> Yes. I am using file:/// protocol. Is there some other alternative
> way to do this ?
>
> Very much appreciate your help.
> -chris
>
>
> On Mon, Aug 10, 2009 at 12:48 AM, Stephen
> Connolly<stephen.alan.connolly_at_gmail.com> wrote:
> >
> >
> > 2009/8/10 buildlackey <chris.b.206_at_gmail.com>
> >>
> >> Hello.. I am getting the above error when i try to svnsync a large
> >> repository
> >> from a remote server to a local svn repository (that i created with
> >> svnadmin create ).
> >>
> >>
> >> I am running this on ubuntu via vmware (windows host), and the version
> of
> >> svn i am running is 1.4.6.
> >>
> >> >>
> >>
> >> cbedford_at_ubuntu-desktop:/cee/bn/scripts$ svn help
> >> usage: svn <subcommand> [options] [args]
> >> Subversion command-line client, version 1.4.6.
> >>
> >>
> >> The errors seem to occur at random points in the sync process...
> >>
> >> I am going to try this with windows version of svn command line client
> >> (1.5.4) i hope that works..
> >>
> >> But if anyone knows what might be causing this and can give me a pointer
> >> i'd
> >> be very grateful.
> >>
> >> - chris
> >
> > Sounds like the user permissions are not set correctly...
> >
> > are you by any chance accessing the repository with the file:///
> protocol?
> >
> > I ask because that is the protocol that is most likely to screw up your
> file
> > permissions.
> >
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/svnsync-fails%3A--Can%27t-move-%27%3Cpath%3E-revprops-742.tmp%27--to--%27%3Cpath%3E-revprops-742%27--Permission-Denied-tp24894736p24894736.html
> >> Sent from the Subversion Users mailing list archive at Nabble.com.
> >>
> >> ------------------------------------------------------
> >>
> >>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2381971
> >>
> >> To unsubscribe from this discussion, e-mail:
> >> [users-unsubscribe_at_subversion.tigris.org].
> >
> >
>
1. Please keep replies on the list
2. Please do not top post
3. I am not sure what your solution might be, but when you use file:/// you
need to ensure that the user accessing via file:/// has permissions to write
to the repository. file:/// is really best served for testing and
debugging, you are usually better served by going through either http/https
or svn Note that ssh+svn is going to have similar issues w.r.t. file
permissions as the svnserve process in that case is owned by the user sshing
in and therefore file permissions can be changed as the user changes
-Stephen
>
>
>
> --
> Chris Bedford
>
> Founder & Lead Lackey
> Build Lackey Labs
> http://buildlackey.com
> skype: chrisb206
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2382011
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-10 12:07:41 CEST