Re: can't commit

final detail...
- making a backup of the local copy
- forcing delete
- adding again the backup
works

but it has been a pain and it is hard to know what are the
problematic files unless you commit them one by one *and* when a file
is problematic svn waits forever in transmit phase and you can't
easily kill the process.

Is there a system to check and fix the whole rep?

What did it happen?

On Mon, 18 Feb 2008 23:30:43 +0100
Ivan Sergio Borgonovo <mail_at_webthatworks.it> wrote:

> Some more details... I've tried to shorten a file that was not that
> important (notes)...
> I'm unfortunately using the Italian localisation...
>
> in the Transmit phase it seems it print more dots...
>
> I'm submitting one by one files some don't commit, some do.
>
>
>
> On Mon, 18 Feb 2008 23:13:57 +0100
> Ivan Sergio Borgonovo <mail_at_webthatworks.it> wrote:
>
> > I keep on getting this from today:
> >
> > [Mon Feb 18 20:06:00 2008] [error] [client 62.173.160.218] Could
> > not get next bucket brigade [500, #0]
> >
> > on Debian sarge (Apache/2.0.54 (Debian GNU/Linux) DAV/2 SVN/1.1.4)
> >
> > I googled and I've found
> > http://www.szakmeister.net/blog/fsfsverify/
> >
> > I tried it on the last rev (not all rev) with no success.
> >
> > What should I do next?
> > Does it make any sense to run fsfsverify on all revs?
> >
> > checkout works fine
>
>
>

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org