You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Dominik Chmaj <dm...@biuro.net.pl> on 2010/02/10 10:01:19 UTC

new files on SVN

hello

I have problem with svn. I'm working with friend on project and sometimes only I
don't get new files submitted by someone. As I know I should be noticed about
all changes. I can see new files by issuing svn log or svn list, but svn up will
not fetch them. Svn st will not show any changes. So there is no file there on
my working copy, I can see it on SVN repo and there is nothing about change. Let
me know if this is know issue or maybe I'm doing something wrong.
Clean checkout will fetch everything - but this is taking quite much time. I
think here should be a way just to sync svn. Also let me know if this is not the
best place for this bug report.

ps. this is not client-related error, I got this on both windows and linux. We
upgraded svn to newest version and the problem is still there.

-- 
dmc

RE: new files on SVN

Posted by Bert Huijben <be...@qqmail.nl>.

> -----Original Message-----
> From: Dominik Chmaj [mailto:dmc@biuro.net.pl]
> Sent: woensdag 10 februari 2010 11:01
> To: users@subversion.apache.org
> Subject: new files on SVN
> 
> hello
> 
> I have problem with svn. I'm working with friend on project and
> sometimes only I
> don't get new files submitted by someone. As I know I should be noticed
> about
> all changes. I can see new files by issuing svn log or svn list, but
> svn up will
> not fetch them. Svn st will not show any changes. So there is no file
> there on
> my working copy, I can see it on SVN repo and there is nothing about
> change. Let
> me know if this is know issue or maybe I'm doing something wrong.
> Clean checkout will fetch everything - but this is taking quite much
> time. I
> think here should be a way just to sync svn. Also let me know if this
> is not the
> best place for this bug report.
> 
> ps. this is not client-related error, I got this on both windows and
> linux. We
> upgraded svn to newest version and the problem is still there.

Which Subversion release are you using?
(Subversion 1.6.0 and 1.6.1 had some issues on 'svn add' marking a directory sparse)

Are you using svn update --depth XXXX for some of the updates?

In this case you could trigger issue #3569 (http://subversion.tigris.org/issues/show_bug.cgi?id=3569)

As workaround for this specific issue I would recommend never using --depth (or -N) on svn update. (svn update --set-depth is safe)

	Bert