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

Re: Break your working copy in 3 easy steps

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: 2007-02-19 09:52:08 CET

On Sunday 18 February 2007 22:59, CodeBase@web.de wrote:
> Assume there are 2 files in the repository which should always be committed
> together, such as an OpenOffice document and the PDF exported from it:
>
> /root/oo.org/mydoc.odt
> /root/pdf/mydoc.pdf

Some people consider that flawed and that only the source data should be held
there. YMMV.

> Assume there are pending changes in the doc (exported to the PDF) worth
> committing.

So there are changes in both files that should be committed, right? Subversion
doesn't care where those changes come from.

> C:\> svn commit --message "some reasonable message"
> "C:\SVNWC\oo.org\mydoc.odt" "C:\SVNWC\pdf\mydoc.pdf" --> OK
>
> Now create more changes and export them again. Repeat the step above.

Again, you changed both files.

>
> --> Modified: ...\mydoc.pdf
> Error: Commit failed (details follow):
> Error: Your file or directory ...\mydoc.pdf' is probably out-of-date
> Error: 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 (restart the commit).

Hmmm, looks like someone else already checked in a changed version of the PDF,
though it's hard to tell from that message.

> I read on the list about deleting wcprops files, but as I can't find any
> file of that name, the only way to get around the problem is to copy the
> changed file, remove the .svn folder and check it all out from scratch,
> then copy the changed file, again.

No, that shouldn't be necessary.

Some theories:
1. Something else is going on, and that is probably something you don't tell
us, probably something automated that modifies either your repository or
workingcopy.

2. Some tool is running amok and modifying the private metadata that belongs
to Subversion, e.g. some batch replace job that doesn't care about
write-protected files.

In any case, it's not in what you're telling us but in what you're not telling
us.

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/
**************************************************************************************
           Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 19 09:52:48 2007

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

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