You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Mojca Miklavec <mo...@gmail.com> on 2011/10/28 05:07:30 UTC

update --depth=empty ignored since 1.7

Dear list,

I'm experiencing some weird behaviour of SVN 1.7. The following
sequence of commands fails to respect --depth=empty:
    svn co --depth=empty http://foundry.supelec.fr/svn/metapost
    svn up --depth=empty metapost/tags

(you can use 'anonymous' as a username if it asks) The first command
runs fine, but the second one starts fetching all tags.

The workaround is to use
    svn up --set-depth empty metapost/tags
before fetching anything with "svn up", but --depts=empty seems to be
respected in 1.6.16 and also makes a lot more sense the way it worked
earlier.

Is this a bug or my misunderstanding of how the above commands are
supposed to work? I noticed that some depth=empty-related issues are
mentioned in changelog for 1.7.1, but subversion 1.7.1 as shipped with
MacPorts on Mac OS X 10.7 doesn't seem to solve the problem for me.

Thank you very much,
    Mojca

Re: update --depth=empty ignored since 1.7

Posted by Philip Martin <ph...@wandisco.com>.
Mojca Miklavec <mo...@gmail.com> writes:

> I'm experiencing some weird behaviour with SVN 1.7. The following
> sequence of commands fails to respect --depth=empty:
>    svn co --depth=empty http://foundry.supelec.fr/svn/metapost
>    svn up --depth=empty metapost/tags
>
> (you can use 'anonymous' as a username) The first command runs fine,
> but the second one starts fetching all tags. If I try to open
> repository in web browser, it reports that the server is using SVN
> 1.4.2 (r22196) which is a bit old, but with SVN 1.6.16 the same
> sequence of commands worked fine - depth=empty seems to be respected.

That certainly looks like a 1.7 bug, I've raised issue 4046

http://subversion.tigris.org/issues/show_bug.cgi?id=4046

-- 
Philip

update --depth=empty ignored since 1.7

Posted by Mojca Miklavec <mo...@gmail.com>.
Dear list,

I'm experiencing some weird behaviour with SVN 1.7. The following
sequence of commands fails to respect --depth=empty:
   svn co --depth=empty http://foundry.supelec.fr/svn/metapost
   svn up --depth=empty metapost/tags

(you can use 'anonymous' as a username) The first command runs fine,
but the second one starts fetching all tags. If I try to open
repository in web browser, it reports that the server is using SVN
1.4.2 (r22196) which is a bit old, but with SVN 1.6.16 the same
sequence of commands worked fine - depth=empty seems to be respected.
I cannot reproduce the behaviour with
    http://svn.apache.org/repos/asf/subversion
where the same commands work just fine.

Is this a bug in SVN client 1.7.(0/1) or my misunderstanding of how
the above commands are supposed to work? I noticed that some
depth=empty-related issues are mentioned in changelog for 1.7.1, but
subversion 1.7.1 as shipped with MacPorts on Mac OS X 10.7 doesn't
seem to behave any differently.

Thank you very much,
   Mojca