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
databases:
"SELECT * FROM NODES where local_relpath like
'%google-perftools%patch-static_vars%' order by local_relpath;"
Good DB output:
1|devel/google-perftools/files/patch-static_vars.cc|0|devel/google-perftools/files|1|head/devel/google-perftools/files/patch-static_vars.cc|339827|normal|||file|(svn:eol-style
native fbsd:nokeywords yes svn:mime-type
text/plain)||$sha1$523055927a64af17578d4a64b9c10c05352b6e07||339812|1389815574658219|mandree|282|1389792191000000|(svn:wc:ra_dav:version-url
77
/ports/!svn/rvr/339812/head/devel/google-perftools/files/patch-static_vars.cc)||
Bad DB output:
1|devel/google-perftools/files/patch-static_vars.cc|0|devel/google-perftools/files|1|head/devel/google-perftools/files/patch-static_vars.cc|339905|normal|||file|(svn:mime-type
text/plain svn:eol-style native fbsd:nokeywords
yes)||$sha1$523055927a64af17578d4a64b9c10c05352b6e07||339812|1389815574658219|mandree|||(svn:wc:ra_dav:version-url
77
/ports/!svn/rvr/339812/head/devel/google-perftools/files/patch-static_vars.cc)||
1|devel/google-perftools/files/patch-static_vars.cc|4|devel/google-perftools/files||||base-deleted|||file||||||||||||
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?
Yuri
