On Monday 28 August 2006 01:11 Gunter Ohrner wrote:
> > Wait a minute ... what did happen?
>
> Good question - I guess I know and it was my fault and not fsvs': I think
> the file changed after the sync-repos while the Repository also had an
> update available.
>
> However, maybe the error message should elaborate about that a bit.
I'm currently (in the background) rewriting fsvs to handle multiple urls.
There the conflict scenario will (have to be) handled.
> > What should fsvs do? Get the file to a temporary name, take it if it's
> > identical (MD5 available after transfer), and leave it with something
> > like .fsvs-conflict if it's not?
> That sounds like a viable solution.
>
> Ok, I moved the files in question away, but this made fsvs crash which I
> guess was not what should have happened... ;)
>
> Backtrace (extracted from core file, unfortunately without full debugging
> symbols in the libraries depended upon):
>
> *****************
> (gdb) bt
> #0 0x4b880768 in apr_pool_clear () from /usr/lib/libapr-0.so.0
> #1 0x08053d67 in up__close_file ()
I cannot find anything wrong in this pool handling.
Which version of apr are you using? I find bug reports about apr_pool_clear()
in google.
Thank you for your help (and patience)!
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
