[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Files added to repository by others don't come down with 'svn update'

From: Yuri <yuri_at_rawbw.com>
Date: Thu, 16 Jan 2014 03:43:30 -0800

On 01/16/2014 03:04, Ashish Kaushik wrote:
> I hope by "/Somebody else added few files into the repository/" You
> mean they have committed the file to the respository as well because
> just adding the file to repository would not make those available to
> others.
> It has to be committed as per SVN nomenclature.

Yes, they committed the files into the repository. When I check out the
fresh copy of this repository I see those files.
But I don't see them in the original repository which I talked about in
the description.

Now I am looking into SQLite databases of this bad (damaged) repository
and the good one (freshly checked out).
I run this query on wc.db for one of the problematic files for both
"SELECT * FROM NODES where local_relpath like
'%google-perftools%patch-static_vars%' order by local_relpath;"

Good DB output:
native fbsd:nokeywords yes svn:mime-type

Bad DB output:
text/plain svn:eol-style native fbsd:nokeywords

The major difference is that this file has two records in "Bad DB" and
only one record in "Good DB". Bad DB has an extra record with op_depth=4
and 'base-deleted'.

I never deleted those files, I added them myself locally because they
are new, but never checked them in.
And even if they were in local pending delete state, new files with the
same path coming from the repository with update should at least cause
the conflict.

What do you think?

Received on 2014-01-16 12:44:11 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.