You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Hans-Georg Becker <ha...@ub.uni-dortmund.de> on 2008/03/07 07:18:05 UTC
trouble with revision numbers
Hello everyone,
I have a problem with commit. I get the message
Transmitting file data ...
svn: Commit failed (details follow):
svn: Commit failed (details follow):
svn: Revision already exists
My working versions are all up-to-date.
What's happend?
Greetings
Hans-Georg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: trouble with revision numbers
Posted by Lieven Govaerts <sv...@mobsol.be>.
Hans-Georg Becker wrote:
> Hi,
>>> Hello everyone,
>>>
>>> I have a problem with commit. I get the message
>>>
>>> Transmitting file data ...
>>> svn: Commit failed (details follow):
>>> svn: Commit failed (details follow):
>>> svn: Revision already exists
>>>
Is this the original error text? I couldn't find it anywhere in the
source code.
>>> My working versions are all up-to-date.
>>>
>>> What's happend?
>> Hm, I'm not aware of a way to get into this situation with normal svn
>> usage. Do you have access to the repository?
>>
>> If so, assmuming you're using FSFS, can you check in the folder
>> $REPO/db/revs with the file with the largest number is? Can you then
>> check if the first number in $REPO/db/current is the same?
> $REPO/db/revs: 934
> $REPO/db/current: 933,
> this folder contains the files current.tmp and current.2.tmp too
> (content: 934 1lf 1hy)
Note: before using any of the two next options, please make a full
backup of your repository!
There are two options. The safest is to move files $REPO/db/revs/934 and
$REPO/db/revprops/934 somewhere aside. If your working copy is up to
date up till 933, you should be able to commit. Note: obviously this
only works if you can redo the changes committed in r934.
The alternate method is to backup the $REPO/db/current file and replace
it with $REPO/db/current.tmp. Here I'm assuming that the only thing
failing was to move the current.tmp file in place. The big risk here is
that revision file 934 is corrupt, so check it thoroughly!
If possible, better use the first option.
>> Can you also provide some more information about the version of svn
>> client & server, whether you're using the apache module or svnserve,
>> OS etc.
> svn, version 1.4.4 (r25188) on server (ubuntu 7.10)
> Client subclipse 1.2.4 on eclipse 3.2.2
> repository mounted as folder from a Win-Server and used as local repository
>
So are you using apache to serve the repository? If so, can you check in
the error.log file if there was something that indicates an error while
committing r934?
Lieven
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: trouble with revision numbers
Posted by Hans-Georg Becker <ha...@ub.uni-dortmund.de>.
Hi,
>> Hello everyone,
>>
>> I have a problem with commit. I get the message
>>
>> Transmitting file data ...
>> svn: Commit failed (details follow):
>> svn: Commit failed (details follow):
>> svn: Revision already exists
>>
>> My working versions are all up-to-date.
>>
>> What's happend?
>
> Hm, I'm not aware of a way to get into this situation with normal svn
> usage. Do you have access to the repository?
>
> If so, assmuming you're using FSFS, can you check in the folder
> $REPO/db/revs with the file with the largest number is? Can you then
> check if the first number in $REPO/db/current is the same?
$REPO/db/revs: 934
$REPO/db/current: 933,
this folder contains the files current.tmp and current.2.tmp too
(content: 934 1lf 1hy)
>
> Can you also provide some more information about the version of svn
> client & server, whether you're using the apache module or svnserve,
> OS etc.
svn, version 1.4.4 (r25188) on server (ubuntu 7.10)
Client subclipse 1.2.4 on eclipse 3.2.2
repository mounted as folder from a Win-Server and used as local repository
An other repository runs well.
>
Hans-Georg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: trouble with revision numbers
Posted by Lieven Govaerts <sv...@mobsol.be>.
Hans-Georg Becker wrote:
> Hello everyone,
>
> I have a problem with commit. I get the message
>
> Transmitting file data ...
> svn: Commit failed (details follow):
> svn: Commit failed (details follow):
> svn: Revision already exists
>
> My working versions are all up-to-date.
>
> What's happend?
Hm, I'm not aware of a way to get into this situation with normal svn
usage. Do you have access to the repository?
If so, assmuming you're using FSFS, can you check in the folder
$REPO/db/revs with the file with the largest number is? Can you then
check if the first number in $REPO/db/current is the same?
Can you also provide some more information about the version of svn
client & server, whether you're using the apache module or svnserve, OS etc.
Lieven
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org