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

RE: SVN Update does not add new files

From: Bert Huijben <bert_at_vmoo.com>
Date: Sat, 24 Apr 2010 15:06:34 +0200

> -----Original Message-----
> From: Martin Cerny [mailto:cerny.m_at_gmail.com]
> Sent: zaterdag 24 april 2010 12:27
> To: dev
> Subject: SVN Update does not add new files
>
> Hi,
> I'm experiencing a bug with SVN.
> I have a branch of our main project. I did some work on it in school and
then
> wanted to update the status of my working copy at home. The files that
> were changed were correctly reflected in the working copy, but new files
> that I added at school were not added to my working copy at home. I can
see
> the files in correct place while browsing the repository with TortoiseSVN.
I
> tried updating both with TortoiseSVN 1.6.6, and via NetBeans plugin using
> svn version 1.6.6 and then with version 1.6.11 to no avail. Switching to
the
> trunk and then back to the branch fixes the problem.
>
> The work at school was done using some older version of TortoiseSVN
> (1.6.2 I guess, but I am not certain)
> Our subversion server is version 1.6.6. I am sorry, but I can't grant you
acces
> to the repository itself, since it's a company server.

If I remember correctly TortoiseSVN 1.6.2 is based on Subversion 1.6.1,
which still had the bug that was fixed in Subversion 1.6.2:
  * set depth=infinity on 'svn add' items with restricted depth (r37607)

Another possible cause for this issue (but far less likely) is issue #3569
(http://subversion.tigris.org/issues/show_bug.cgi?id=3569): svn update
--depth <DEPTH> allows making a working copy incomplete

The first issue can be resolved by using 'svn update --set-depth infinity'
on the working copy (and is fixed in later clients). The second can only be
resolved by a new checkout and isn't fixed yet.

And of course it could be another issue, so if you have a different
reproduction recipe to show, please send it to this list. (In all cases I
heard it was one of these two reasons... and in most cases the working copy
was marked sparse long ago, without anybody noticing)

        Bert
Received on 2010-04-24 15:07:09 CEST

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