still wedging on r3033

[Rich Drewes <dr...@interstice.com>]

Hello,

I svnadmin dumped my repository and svnadmin loaded it back into r3033.  
I still find it depressingly easy to wedge things.  For example, if some
source files have been updated by another user and I attempt to check in
my copies of the same files, the commit fails (as it should) but the
update also fails (as it shouldn't), e.g.:

[svn@cortex-0 newn47]$ svn commit
Sending        Brain.cpp
svn: Transaction is out of date
svn: Commit failed (details follow):
svn: out of date: `Brain.cpp' in txn `1d'
[svn@cortex-0 newn47]$ svn update
svn: Problem running log
svn: in directory .
svn: start_handler: error processing command 'merge' in .
svn: Working copy not locked
svn: svn_wc_merge() returned an unexpected error
svn: directory not locked ()
[svn@cortex-0 newn47]$ svn cleanup
svn: Problem running log
svn: in directory .
svn: start_handler: error processing command 'merge' in .
svn: Working copy not locked
svn: svn_wc_merge() returned an unexpected error
svn: directory not locked ()
[svn@cortex-0 
newn47]$ svn --version
Subversion Client, version 0.14.2 (r3033)
   compiled Sep 12 2002, 20:51:40

Any ideas?  I'm still set up with local users on a local filesystem.  Is
r3033 not recent enough still?  It's the latest tarball but not taken from
the svn repository obviously.

Thanks,
Rich


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: still wedging on r3033

[Rich Drewes <dr...@interstice.com>]

On 13 Sep 2002 cmpilato@collab.net wrote:

> Rich Drewes <dr...@interstice.com> writes:
> 
> > Any ideas?  I'm still set up with local users on a local filesystem.  Is
> > r3033 not recent enough still?  It's the latest tarball but not taken from
> > the svn repository obviously.
> 
> subversion-r3033.tar.gz is the latest tarball, but as of this writing,
> 3165 is the youngest revision of Subversion.  If you want to run
> bleeding-edge subversion, use your r3033 svn binary to checkout the
> latest Subversion source code.  See the INSTALL file in the top-level
> of your tarball tree for more details.

Thanks.  I upgraded to Subversion r3165.  When the second user tries to 
commit files that another users has also committed, I get this:

[svn@cortex-0 newn47]$ svn commit
Sending        Brain.cpp
subversion/libsvn_client/commit.c:660: (apr_err=160028, src_err=0)
svn: Transaction is out of date
svn: Commit failed (details follow):
subversion/libsvn_ra_local/commit_editor.c:113: (apr_err=160028, 
src_err=0)
svn: out of date: `Brain.cpp' in txn `1d'
[svn@cortex-0 newn47]$ svn update
C  BuildBrain.cpp
C  Brain.cpp
Updated to revision 48.

The local directory contains .mine, .47, and .48 versions of the files in
conflict.  So, I think all is well . . . except that the error message on
the commit is a bit alarming and unhelpful.  Is that the way it's supposed
to look?  I remember older versions seemed to have more descriptive and
less alarming messages for failed commits . . .

Thanks again for your help,
Rich


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: still wedging on r3033

[cm...@collab.net]

Rich Drewes <dr...@interstice.com> writes:

> Any ideas?  I'm still set up with local users on a local filesystem.  Is
> r3033 not recent enough still?  It's the latest tarball but not taken from
> the svn repository obviously.

subversion-r3033.tar.gz is the latest tarball, but as of this writing,
3165 is the youngest revision of Subversion.  If you want to run
bleeding-edge subversion, use your r3033 svn binary to checkout the
latest Subversion source code.  See the INSTALL file in the top-level
of your tarball tree for more details.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org