[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: out of date error during commit

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-10-08 17:53:27 CEST

"Vazquez, Jose" <jose.vazquez@baesystems.com> writes:

> bash-2.03$ svn status
> M java\HFBBA\.nbattrs
> M java\HFBBA\Client.form
> M java\HFBBA\Client.java
> M java\components\.nbattrs
> M java\components\Sample.java
> A java\components\SampleView.form
> A java\components\SampleView.java
> A java\components\SampleViewDisplay.form
> A java\components\SampleViewDisplay.java
> M java\components\angleDisplay.java
> M java\components\angleSelector.java
> ? svn-commit.tmp
> bash-2.03$
> bash-2.03$ svnlook date /HFBBA_svn_repository
> 2003-10-02 19:08:40 -0400 (Thu, 02 Oct 2003)
> bash-2.03$
> bash-2.03$ svn ci -F svn-commit.tmp
> Sending java\HFBBA\.nbattrs
> svn: Transaction is out of date
> svn: Commit failed (details follow):
> svn: out of date: `/trunk/java/HFBBA/.nbattrs' in txn `j'

Out-of-date means the repository file is newer than the working-copy
file. You can't commit.

It looks like what happened is that your commit went through in the
repository, but your working-copy was never notified. It thinks you
still have a bunch of local mods. If you run 'svn update', all of the
redundant changes should just be merged in, except that you'll get
obstructed updates on the schedule-add files. So that's a no-go.

Just checkout a fresh working copy, and verify that the latest changes
are already in the repositroy.

Or, run 'svn revert -R .', to remove all your local changes. Then
remove all the schedule-add files. And then run 'svn update'.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 8 17:55:32 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.