"Martin Letenay" <mle@whitestein.com> wrote on 09/12/2005 10:47:05 AM:
> I've just commited fix to issue #390.
> We've discovered it on last Friday and it's an ugly one.
> You can pretty easy get your working copy screwed up just by using
update from
> synchronize view.
>
> The problem was introduced with 0.9.33 - the performance fix for
updates.
> Instead of calling update() on individual resources, now the
update(File[])
> method of javahl is called.
>
> However, JavaHL does not actually do any sanity checks there, so when it
is
> passed an array with wrong order of resources
> (incoming files before its parent incoming directory), the incoming
files will
> be skipped.
> However your WC pretends everything went fine and you'll just miss some
files from then.
> The only way how to fix such corrupted WC I knew of, was to switch to
some
> earlier revision within same branch and then switch back to HEAD ...
>
> The fix is commited now, but I'm afraid that the bug is so serious we
should
> release a new 0.9.34 version just because of it.
OK, I have been pretty busy with some work stuff and have a lot of
unfinished stuff in my workspace. When I get some time, I will set that
aside and get a new release out. Hopefully later today or tomorrow.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Tue Sep 13 01:10:08 2005