Andreas Krey wrote:
>On Thu, 19 Sep 2013 08:36:19 +, Lorenz wrote:
>...
>> you can use:
>>
>> svn propget svn:externals -R repoURL
>>
>> to get all external definitions.
>
>Does that actually work again on big repositories?
>It used not to, and just omit some.
don't know, never tried it
Phillip,
Thanks for the reply. I was hoping it would allow me to sync without regard
file locks. In the end I just used rmlocks to remove the lock and then
re-ran svnsync.
I am still a bit confused about the difference between --steal-lock and
--disable-locking. I understand that --steal-lock basi
Dear Sir
We got this error "Can't parse lock/entries hashfile /foldername/filename.
Serialized hash missing terminator" in one of our repositories when trying
to browse or update the repository.Running svnadmin lslock on the
repository folder on the server also produced the same error message
Does anyone have any experience with this? Or suggest a way to retain all the
commit history from mercurial?
Chanchala
Seumas Soltysik writes:
> I am using svnsync to sync a mirror with a master. However, I am getting
> the following error:
> svnsync: E160039: User '' does not own lock on path '/foo/bar'
>
> I understand why this is happening but I am not sure what the solution is.
>
> Based upon the svnsync
I am using svnsync to sync a mirror with a master. However, I am getting
the following error:
svnsync: E160039: User '' does not own lock on path '/foo/bar'
I understand why this is happening but I am not sure what the solution is.
Based upon the svnsync documentation it would appear that the
On 19 Sep 2013, at 08:31, Ben Reser wrote:
> On Wed Sep 18 23:02:31 2013, Paul Wagland wrote:
>> I can see that for the svn_auth.h, however I don’t see how rerunning
>> autogen.h will change the order of the includes in swigutil_pl.c? What
>> should the proper fix for that be?
>
> Why exactly
On Thu, 19 Sep 2013 08:36:19 +, Lorenz wrote:
...
> you can use:
>
> svn propget svn:externals -R repoURL
>
> to get all external definitions.
Does that actually work again on big repositories?
It used not to, and just omit some.
Andreas
--
"Totally trivial. Famous last words."
From
Axel S wrote:
>We have some shared libraries, and these are referenced as static
>externals in all tagged versions of our different projects.
>
>After reorganizing the directory structure of our shared libraries, I
>see that all tagged versions now gives an error. I realised that the
>externals
