You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Konstantin Kolinko <kn...@gmail.com> on 2011/10/18 15:38:06 UTC

E155010: "The node was not found" when updating a sparse working copy

Hi!

When I have a sparse wc and there have been some changes in the
omitted subdirectories,
the "svn up" command may produce spiritous warnings trying to update
files that do not exist locally.

I am using 1.7.0, http: or https: protocol, Neon library.

Script that reproduces this issue with apache.org repository:
[[[
svn co http://svn.apache.org/repos/asf/tomcat/site/trunk/@1183302 wc
svn up -r 1183302 wc/docs --set-depth empty
svn up -r 1183305 wc
]]]
svn: E155010: The node '(...)\wc\docs\security-6.html' was not found.


I have not found any bad consequences from it, as if it were pure cosmetic,
but there is "Very big problems with access rights (authz file using)
in SVN v1.7.0" [1]
thread on users@ now, and these issues might be related.

[1] http://subversion.markmail.org/thread/ctniegc3sicosmul


Best regards,
Konstantin Kolinko

RE: E155010: "The node was not found" when updating a sparse working copy

Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
> Sent: dinsdag 18 oktober 2011 15:38
> To: users@subversion.apache.org
> Subject: E155010: "The node was not found" when updating a sparse working
> copy
> 
> Hi!
> 
> When I have a sparse wc and there have been some changes in the
> omitted subdirectories,
> the "svn up" command may produce spiritous warnings trying to update
> files that do not exist locally.
> 
> I am using 1.7.0, http: or https: protocol, Neon library.
> 
> Script that reproduces this issue with apache.org repository:
> [[[
> svn co http://svn.apache.org/repos/asf/tomcat/site/trunk/@1183302 wc
> svn up -r 1183302 wc/docs --set-depth empty
> svn up -r 1183305 wc
> ]]]
> svn: E155010: The node '(...)\wc\docs\security-6.html' was not found.

Ok, this one is easy to reproduce with this clean reproduction script.
(Confirming this as an issue)
I will look into this.

	Bert