1. Sebastian Sebastian
  2. scm-manager

Issues

Issue #358 resolved

svn copy and move failed "svn: E175002"

Ruben Tieland
created an issue

When i try to move a file i get the following error:

svn: E175002: REPORT of '/scm/svn/GUP/!svn/bc/0/Oplevering/5.2.0/SQL/003.Student .Verbintenis.sql': 200 OK (http://dmnas.rocmn.lan)

and when i try to copy a folder i get almost the same error:

svn: E175002: REPORT of '/scm/svn/GUP/!svn/bc/0/Koppeling/Bron/Bron-FS/trunk': 200 OK (http://dmnas.rocmn.lan)

commit, update, remove works fine.

Comments (9)

  1. Sebastian Sebastian repo owner

    I could not reproduce this issue, i've done the following:

    $ scm-cli-client create-repository -t svn -n issues/358
    ID:             FpO16FRk81
    Name:           issues/358
    Type:           svn
    E-Mail:
    Description:
    Public:         false
    Archived:       false
    Creation-Date:  2013-03-25 13:22:06
    Last-Modified:
    URL:            http://localhost:8081/scm/svn/issues/358
    Permissions:
    
    $ svn co http://localhost:8081/scm/svn/issues/358
    Checked out revision 0.
    
    $ cd 358
    
    $ svn mkdir trunk tags branches
    A         trunk
    A         tags
    A         branches
    
    $ svn commit -m 'added project structure'
    Adding         branches
    Adding         tags
    Adding         trunk
    
    Committed revision 1.
    
    $ cd trunk
    
    $ svn mkdir a b c
    A         a
    A         b
    A         c
    
    $ svn commit -m 'added more directories'
    Adding         a
    Adding         b
    Adding         c
    
    Committed revision 2.
    
    $ echo a > a/a.txt
    
    $ svn add a/a.txt
    A         a/a.txt
    
    $ svn commit -m 'added a'
    Adding         a/a.txt
    Transmitting file data .
    Committed revision 3.
    
    
    $ svn move http://localhost:8081/scm/svn/issues/358/trunk/a/a.txt http://localhost:8081/scm/svn/issues/358/trunk/b/b.txt -m 'move a to b'
    
    Committed revision 4.
    

    It is possible that you provide steps to reproduce the issue like the ones above, from repository creation until the move execution. If you could not reproduce this issue with a test repository please post the trace log from a failed move operation.

  2. Ruben Tieland reporter

    I try'd it with a new repository created with SCM Manager (SCMManagerAddRepoTest2.png). The move still fails. Where can i find the trace log.

    C:\Work>svn checkout http://dmnas.rocmn.lan/scm/svn/Test2 --username xxxxx --password xxxxx Checked out revision 0.

    C:\Work>cd Test2

    C:\Work\Test2>svn mkdir trunk tags branches A trunk A tags A branches

    C:\Work\Test2>svn commit -m "added project structure"

    Adding branches

    Adding tags

    Adding trunk

    Committed revision 1.

    C:\Work\Test2>cd trunk

    C:\Work\Test2\trunk>svn mkdir a b c

    A a

    A b

    A c

    C:\Work\Test2\trunk>svn commit -m "added more directories"

    Adding a

    Adding b

    Adding c

    Committed revision 2.

    C:\Work\Test2\trunk>echo a > a\a.txt

    C:\Work\Test2\trunk>svn add a\a.txt

    A a\a.txt

    C:\Work\Test2\trunk>svn commit -m "added a"

    Adding a\a.txt

    Transmitting file data .

    Committed revision 3.

    C:\Work\Test2\trunk>svn move http://dmnas.rocmn.lan/scm/svn/Test2/trunk/a/a.txt http://dmnas.rocmn.lan/scm/svn/Test2/trunk/b/b.txt -m "move a to b"

    svn: E175002: REPORT of '/scm/svn/Test2/!svn/bc/0/trunk/a/a.txt': 200 OK (http://dmnas.rocmn.lan)

  3. Log in to comment