You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Christian van der Leeden <li...@logicunited.com> on 2003/06/16 12:25:14 UTC
Recommended steps after the text base got corrupted
Hi,
I've got this error when trying to commit: (Subversion 0.24.0
on Gentoo linux)
svn commit
.....
Sending
BaseTest/src/com/logicunited/gaia/base/payment/ipc/IPCPayByCallTest.java
Sending
BaseTest/src/com/logicunited/gaia/base/payment/ipc/IPCPaymentTester.java
Transmitting file data ......svn: Working copy text base is corrupt
svn: Commit failed (details follow):
svn: svn_wc_transmit_text_deltas: checksum mismatch for
'/mnt/raid/Users/leeden/WorkArea/Projects/gaia/Base/Base.eomodeld/.svn/
text-base/Image.plist.svn-base':
recorded checksum: 34dd9c6b72ddc7916cc4e4f4edc9b7c8
actual checksum (hex): d18c5fcacdd012a2d47ceafbd62de676
actual checksum (base64): 0Yxfys3QEqLUfOr71i3mdg==
svn: Your commit message was left in a temporary file:
svn: '/mnt/raid/Users/leeden/WorkArea/Projects/gaia/svn-commit.tmp'
It seems that the text base is corrupt. Is there a
way to recover the text base (e.g. to sync it from the repository,
to do a forced update or whatever).
My only solution is to check out the repository again.
and then merge my changes into the newly checked out
version.
svn cleanup didn't work.
Thanx
Christian
----------------------------------------------
Christian van der Leeden
Logic United GmbH
Tel: 089-189488-66 Mob: 0163-3747111
www.logicunited.com
Re: Recommended steps after the text base got corrupted
Posted by Christian van der Leeden <li...@logicunited.com>.
It is corrupt, it doesn't contain any useful
textual information any more (just '@').
I guess this is due to a server crash some
days ago. They left this file corrupted.
Can't imagine any other reason why
it should have gotten corrupted...
OK, but there is no svn command to repair
such a text base, so I have to go through the
checkout-copy action.
Thanx
Christian
On Monday, June 16, 2003, at 02:30 PM, Ben Collins-Sussman wrote:
> Christian van der Leeden <li...@logicunited.com> writes:
>
>> It seems that the text base is corrupt.
>
> Are you saying that just because the checksum error message suggests
> that? Or have you actually looked at the text base? Just curious.
>
>> Is there a way to recover the text base (e.g. to sync it from the
>> repository, to do a forced update or whatever).
>
> No, you have to a fresh checkout, and copy your modified working files
> into the new working copy.
>
> And if your textbase *is* weird, how did it get that way? Do you have
> any idea? I mean, there's a reason we give text-bases funny suffixes
> and make them read-only. :-)
>
>
----------------------------------------------
Christian van der Leeden
Logic United GmbH
Tel: 089-189488-66 Mob: 0163-3747111
www.logicunited.com
Re: Recommended steps after the text base got corrupted
Posted by Ben Collins-Sussman <su...@collab.net>.
Christian van der Leeden <li...@logicunited.com> writes:
> It seems that the text base is corrupt.
Are you saying that just because the checksum error message suggests
that? Or have you actually looked at the text base? Just curious.
> Is there a way to recover the text base (e.g. to sync it from the
> repository, to do a forced update or whatever).
No, you have to a fresh checkout, and copy your modified working files
into the new working copy.
And if your textbase *is* weird, how did it get that way? Do you have
any idea? I mean, there's a reason we give text-bases funny suffixes
and make them read-only. :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org