On May 25, 2009, at 01:45, Eirik Maus wrote:
> Gavin 'Beau' Baumanis wrote:
>>
>
>> On 21/05/2009, at 8:06 AM, Eirik Maus wrote:
>>
>>> Commit failed. Now I can’t do anything without cleaning up first
>>> – not even clean up (?!). All directories and files are writable.
>>> Does anyone have a clue?
>>> It seems like the only option is to edit the .svn/entries file,
>>> but it is very hard to find any information on the file format.
>>
>>
>> I ha this problem once myself.
>>
>> The only way "I" could get it corrected was to checkout a new
>> working copy.
>> (Of course make a copy of your local files that have been edited
>> - but not yet committed, so you can re-apply those changes to the
>> new Working copy.
>>
>> There may well be a better solution, but I couldn't find one at
>> the time.
>
>
> Oh, I really really hope I can solve this using the existing
> working copy. I’ve just performed a major redesign across 6 project
> modules changing several module names and all of the dependencies,
> and also moving files between modules and renaming them. It will
> not be easy to map all those changes to a new checkout. I must
> probably give up and start a new repository based on the working
> copy. To me this is equivalent of “svn repository completely frozen”.
I don't know what you mean by "repository completely frozen" but in
this case I don't see any reason to believe that anything is wrong in
the repository, only that for some reason something has happened to
the working copy. The goal is for the repository to be bullet-proof.
It seems the working copy isn't quite as bullet-proof and can
sometimes get corrupted. Working copies are assumed to be more or
less disposable. It is unfortunate that you had so much uncommitted
work in your working copy at the point when it apparently became
corrupted. In the future, it might be prudent to do refactoring work
in a branch. That way you can commit more often and if a working copy
becomes corrupted in the future you would not stand to lose as much
work.
> It is hard to believe that the relation between the repository and
> the working copy cannot be saved by editing the “entries” file.
> After all, it seems like a minor error internally. I’ve had similar
> problems with CVS earlier, and they could always be fixed with a
> minor edit of the repository or working copy configuration files.
> Why is this not possible with SVN?
Editing the entries files manually is not supported. That's all. You
can do it but we will not help you. The format of the file is not
described, and will not be described because the Subversion
developers do not want people editing the files manually. There
should be no need to. If there is a situation where Subversion can
write incorrect information to the entries files, then that bug needs
to be identified and fixed in Subversion. Any help you can give in
that regard would no doubt be appreciated by the developers.
But note that the working copy format is being completely rewritten,
so perhaps this kind of problem will go away in the redesign (to be
replaced, no doubt, by a new set of problems to be discovered and
understood).
http://subversion.tigris.org/issues/show_bug.cgi?id=3357
http://svn.collab.net/repos/svn/trunk/notes/wc-ng-design
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2353442
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-25 12:06:02 CEST