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

Re: AW: Re: What to do?

From: Steve Ewart <steve_at_ewart.net>
Date: 2006-03-07 08:15:19 CET

 I think Jeremy's approach is the first step in narrowing down the problem.

It should be very simple to do.

1. Copy your 'broken' copy of the code to a temp1 directory.
2. Delete all _svn directories under temp1. If you are on Windows, search
for _svn in Explorer and delete them from the search window.
3. Do a checkout to a temp2 directory.
4. Copy the contents of temp1 onto temp2.
5 Try the commit function that you were having trouble with on temp2.

This should either alleviate the problem or tell you that it is not likely a
messed up local directory.
That's what I would try.

Steve

On 3/6/06, Markus Karg <markus.karg@quipsy.de> wrote:
>
> Unfortunately the local WC is very large. There are a lot of local
> changes in a lot of files, and the files are in a lot of very deeply nested
> directories (as usual due to Java's package structure). So doing this
> manually without incidentially mangling .svn folders tends to be as long as
> reworking the past day... :-(
>
> Thanks for your kind help, anyways.
>
> Maybe someone knows a tool that can repair the broken WC?
> I mean, it's not my data what is broken but the .svn folders.
> So there should be a tool that can detect the problem and possibly repair
> it?
>
>
>
> Mit freundlichem Gruss / With kind regards
> Markus KARG, Staatl. gepr. Inf.
> Entwicklung / R & D
> QUIPSY QUALITY GmbH
>
> ------------------------------
> *Von:* Jeremy Pereira [mailto:jeremyp@jeremyp.net]
> *Gesendet:* Di 07.03.2006 07:58
> *An:* Markus Karg
> *Cc:* kauer@biplane.com.au; users@subversion.tigris.org
> *Betreff:* Re: AW: Re: What to do?
>
>
>
> On Mar 7, 2006, at 15:47, Markus Karg wrote:
>
> Karl,
>
> sure I can use my backup, but losing one day's work is not nice. The
> intention of asking the community was to find a solution that prevents
> losing one day of work.
>
> I have done a svnadmin verify and it didn't tell any errors. So I think
> the repository is ok. How to check the local filesystem? I've done a cleanup
> (no problems reported) and tried the commit again, but still there is the
> same error.
>
> Any ideas (other than: "Remove your local work and checkout from
> repository.")?
>
>
>
> If you can check out the code from the repository and your locally changed
> files are still readable, you can check out to some other place, copy your
> local changes over the top of the new working copy (be careful no to mung
> the .svn directories) and then commit that. After that, you can delete the
> original corrupt W/C and either check out again or even move the second W/C
> to replace the original.
>
>
> If you can no longer read the locally modified files, that's probably the
> end of them.
>
>
>
>
> Mit freundlichem Gruss / With kind regards
> Markus KARG, Staatl. gepr. Inf.
> Entwicklung / R & D
> QUIPSY QUALITY GmbH
>
> ------------------------------
> *Von:* Karl Auer [mailto:kauer@biplane.com.au <kauer@biplane.com.au>]
> *Gesendet:* Mo 06.03.2006 16:58
> *An:* users@subversion.tigris.org
> *Betreff:* Re: What to do?
>
>
>
> On Mon, 2006-03-06 at 16:11 +0100, Markus Karg wrote:
> > Filesystem is corrupt
> > svn: Commit failed (details follow):
> > svn: Ungültige Reihenfolge bei Änderung: Neue Knoten Revisions ID ohne
> > Löschen
>
> Use your backups, Luke.
>
> Can you check out the latest revision? If so, maybe the filesystem it's
> talking about is yours, not the repository's.
>
> Regards, K.
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Karl Auer (kauer@biplane.com.au) +61-2-64957160 (w/h)
> http://www.biplane.com.au/~kauer/ +61-428-957160 (mob)
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>
Received on Tue Mar 7 08:16:33 2006

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