- Original Message -
> From: Stefan Sperling
>
> AFAIK open files cannot be deleted on Windows. So either the file was closed
> at the time the 1.6 wc log was run, or the 1.6 wc log failed to actually
> update the on-disk data.
No no no :) neither nor.
1.6 just tested the file _before_
- Original Message -
>
> I'm not sure whether that applies to Justin's particular case because
> that's only a problem if the lock gets released between the original
> workqueue run and the second workqueue run. That's a very small
> window--in most cases both runs see the lock and the b
- Original Message -
>
> But as said before, that's possibly quite hard to achieve
> in light of an existing possibly multi-layered implementation
No idea what you mean with multi-layers - wc.db and such are internal issues of
svn, of which nobody above should be made aware. I think. At
> From: Johan Corveleyn
>
> The problem is that, at the point where svn runs into this locked
> file, half of the work has already been done (the metadata in wc.db
> has already been updated). The remaining work (moving the file into
> place) is scheduled in a specific table called the work_que
- Original Message -
> From: Ulrich Eckhardt
>
> Sorry, but I'm afraid I didn't get across what I wanted to say.
Correct. Let me simplify again my test case:
1. I run svn update
2. svn update finds a file in use, aborts
3. I free the file, oops it seems I have to cleanup
Why should I
- Original Message -
> From: Ulrich Eckhardt
> Yes, probably, unless it was killed so quickly that it couldn't even cry
> for help any more, which e.g. happens if you cut the power or use "kill
> -9" on POSIX systems.
We're not talking here about natural catastrophes, but about a file w
> From: Ulrich Eckhardt
>
> Only you (the user) knows "if it was interrupted" or is maybe still
> running! I would say that this message could be improved[0], but
I beg to differ: the operation which interrupted itself because it found a file
in use knows very well that it was interrupted. So, i
> From: Johan Corveleyn
>
> cleanup' (cleanup is the only command that will unconditionally remove
> these locks, so you should only run it if you're sure there is no
> other command running concurrently, and those locks are "stale locks"
> left by other interrupted commands).
> [...]
> I don't f
Hello all,
did I just ask a stupid question :) or nobody has any idea what's going wrong
here?
Thank you very much for your patience,
JJ
- Original Message -
> From: Justin Case
>
> Hi all,
> this is something new for me (TortoiseSVN 1.7.7 with Subversion 1.7.5 on
Hi all,
this is something new for me (TortoiseSVN 1.7.7 with Subversion 1.7.5 on
Windows XP):
- I try to update something when a file is in use,
- update understandably fails, it cannot overwrite that file. Fine.
- BUT I cannot update again, I have to cleanup first!
Before days (months?) the clean
10 matches
Mail list logo
