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

Re: Bug: lockup after adding binaries from samba

From: Jille Timmermans <jille_at_quis.cx>
Date: Wed, 5 Nov 2008 04:40:53 -0800 (PST)

On Aug 5, 4:51 pm, Stefan Küng <tortoise..._at_gmail.com> wrote:
> Joachim Lous wrote:
> > TortoiseSVN 1.5.2.  Issue present since at least 1.5
> > SVN server running 1.4.2, http access.
>
> > I have a working copy on a samba share (bear with me),
> > which although discouraged has been working fine for me.
> > After recent upgrading to 1.5.x of TSVN, I run into problems
> > every time I try to add binary files.
>
> > In the example below "T:" is the mounted samba share, and
> > i have just successfully added (but not committed) both the
> > text file "test.txt" and the image file "test.png".
>
> > When committing, I get this log in the commit window:
> >     Command: Commit
> >     Adding: T:\portal2\trunk\notes\test.png  application/octet-stream
> >     Adding: T:\portal2\trunk\notes\test.txt
> >     Sending content: T:\portal2\trunk\notes\test.png
> >     Sending content: T:\portal2\trunk\notes\test.txt
> >     Error: Commit succeeded, but other errors follow:
> >     Error: Error bumping revisions post-commit (details follow):
> >     Error: In directory 'T:\portal2\trunk\notes'
> >     Error: Error processing command 'committed' in 'T:\portal2\trunk\notes'
> >     Error: Can't move
> > 'T:\portal2\trunk\notes\.svn\props\test.png.svn-work' to
> >     Error: 'T:\portal2\trunk\notes\.svn\prop-base\test.png.svn-base':
> > Access is denied.
> >     Finished!:
>
> > This does not happen if the commit contains no new binary files.
> > Nor on local working dirs.
>
> > After the error the containing dir is locked, and cleanup reliably
> > fails. The only sound workaround I've found is to locally delete the
> > entire containing dir of the offending file, and then update its
> > parent dir to restore it all (the commit itself did after all succeed).
>
> > I know working dirs on network drives are discouraged, but since
> > this used to work fine, and still does for non-binary files, It does
> > seem to be a genuine bug in TSVN.
>
> Wrong assumption:
> * the error is thrown by the svn library
> * it works ok for local working copies and even windows network shares
>    --> svn does nothing 'illegal' when performing the file operations
>    --> it only does not work with SAMBA shares
>    --> what does that tell you where the bug really is?
>
> Stefan
>
> --
>         ___
>    oo  // \\      "De Chelonian Mobile"
>   (_,\/ \_/ \     TortoiseSVN
>     \ \_/_\_/>    The coolest Interface to (Sub)Version Control
>     /_/   \_\    http://tortoisesvn.net
>
>  signature.asc
> < 1KViewDownload

I have the same issue;
If I try to do a cleanup after the failed commit; the cleanup fails

Actions:
* Tortoise SVN commit (fails)
* Tortoise SVN cleanup (fails repeatedly)
$ chmod -R +w .svn (run on unix in the dir he can't cleanup)
* Tortoise SVN cleanup (succeeds)

So I think it is an permission problem; however I don't know whether
it is a bug in Subversion or in Tortoise

-- Jille Timmermans

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-11-05 13:50:58 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.