Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-1044

"status -u foo" yields "Working copy not locked"

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • all
    • 0.21
    • unknown
    • None
    • Linux

    Description

      This happens with clients r3987 and r4137, and server r3987.  The
      server runs
              Linux offby1 2.4.18crypto #1 Sat Nov 16 15:06:52 PST 2002 i686
      unknown
      ; I've seen the problem using the 3987 client on the same machine, as
      well as on other Linux machines and a Cygwin machine.
      
      I configured thusly:
      
              ./configure --prefix=/usr/local/svn --with-apxs=/usr/bin/apxs2
      
      I'm using Version: 4.0.14-1 of the Berkeley DB stuff
      
      I don't know how you'll reproduce this :(  It repros for me every
      time, but I assume (as I'll explain below) that the problem is
      triggered by something wrong in my repository.
      
      Anyway, here's what I do and see:
      
          15:35:41 [offby1@offby1 config-files]$ svn status -v -u .emacs.el
          subversion/libsvn_wc/lock.c:422: (apr_err=155005, src_err=0)
          svn: Working copy not locked
          svn: directory not locked (mozbook)
      
      Note that `mozbook' is indeed a subdirectory of the current directory.
      
      `svn cleanup' does not make the problem go away.
      
      If it matters, here's the output of `svn info' in that directory:
      
          15:31:16 [offby1@offby1 config-files]$ svn info
          Path: 
          Url: http://localhost/svn/repos/trunk/config-files
          Revision: 15
          Node Kind: directory
          Schedule: normal
          Last Changed Author: erich
          Last Changed Rev: 15
          Last Changed Date: 2002-12-12 11:44:13 -0800 (Thu, 12 Dec 2002)
      
      Note that, if I try an equivalent command on another repository
      (namely the subversion sources themselves), I have no trouble:
      
          15:43:43 [offby1@offby1 getopt_tests_data]$ svn status -v -u
      svn_stderr 
                       4110     3250     kfogel   svn_stderr
          Head revision:   4110
      
      This is why I assume the problem has something to do with my
      repository.
      
      And the problem recurs on many different machines, as long as they're
      talking to the same server.
      
      I can't recall exactly how I created the repository, but I think it
      went about it in an entirely straightforward way: I created a
      directory with `cvs export' (because the stuff was originally under
      CVS control), then did `svn import'.  I am fairly certain that I then
      did a few `svn mv's afterward -- and that each time, each argument to
      mv contained a URL (thus they were all "complete server-side
      renames").
      

      Original issue reported by offby1

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              subversion-importer Subversion Importer
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: