[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subclipse-users
Subject:    Re: ResourceVariantTreeSubscriber.1 - error message
From:       Mark Phippard <MarkP () softlanding ! com>
Date:       2005-06-30 12:25:22
Message-ID: OF439F179A.AB3FB38D-ON85257030.0043CA31-85257030.00447A99 () softlanding ! com
[Download RAW message or body]

lukjel <lukjel@poczta.onet.pl> wrote on 06/30/2005 06:16:10 AM:

> I'm a big fan of SVN and I used to use eclipse so - there is only one
> choice - subclipse :)
> But I'm very confused because of  so many errors... especially under
> linux.
> Let's say this one from title.
> It comes up when I want to synchronize my project with svn repo.
> Why? How can I make synchro?
> 
> I know - there are some differents - I change .svnignore (in true it
> was done by plugin). When I just use COMMIT (from submenu for root
> project) I've got error:
> 
> <message>
> 
> org.tigris.subversion.svnclientadapter.commandline.CmdLineException
> svn: Commit failed (details follow):

This message shows that you are using the Command Line adapter.  If 
possible, you should invest the effort to get JavaHL installed on your 
system and use that adapter.  It works much better.

> 
> svn: Your file or directory '.' is probably out-of-date
> 
> svn: The version resource does not correspond to the resource within
> the transaction. Either the requested version resource is out of date
> (needs to be updated), or the requested version resource is newer than
> the transaction root (restrat the commit).
> 
> </message>
> 
> Of course - There is no chance that this message is ok. I'm currently
> alone and project is fresh (refresh by eclipse and also I tried to
> make UPDATE).

There is no chance that this message is not correct.  First off, the 
message is comming straight from the svn command line.  Second, it is very 
easy for a single user WC to become stale.  It is called mixed-revision 
working copies and it bites everyone.  When you commit a file, that file 
is updated to the latest revision, but the folder that contains it is not. 
 You have to do an explicit update on the folder to bring it to the same 
revision.  For most operations, this does matter, but there are certain 
operations that you cannot perform unless the folder is at the HEAD 
revision.  Things such as setting properties on the folder or 
deleting/renaming files within the folder.

> I don't see any chance to make commit.
> When I tried this  under windows - there was noproblem!
> 
> I'm using eclipse 3.1 (finall but error is rather old) with subclipse
> 0.9.31 and SVN installed localy (bad...) 1.2.
> My system is: gentoo 2005.0 with java from sun 1.5.0.04 (new update).
> I'm connecting with svn 1.2 installed on apache2
> 
> Any ideas?

Do Team -> Update when you get this error message.  In general, try to get 
JavaHL working.

Mark


_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs. 
_____________________________________________________________________________

[prev in list] [next in list] [prev in thread] [next in thread]