On Mon, Dec 04, 2006 at 05:04:16PM +0200, Yuval Aviel wrote:
> I'd be grateful if someone can reproduce or confirm this bug.
(as would I; any takers?)
> The shared disk is a Windows shared NTFS partition, that I mount using cifs.
> Here is the line from /etc/fstab:
> //miragesrv/applic /mnt/applic cifs
> ,workgroup=MIRAGE 1 2
> fresnel:wc > svn import /tmp/proj/ file:///mnt/applic/repo/ -m "initial
> Adding /tmp/proj/trunk
> Adding /tmp/proj/trunk/Tolerances
> Adding /tmp/proj/trunk/Tolerances/get_fun_ranges.m
> svn: Can't unlock prototype revision lockfile for transaction '0-1':
> Permission denied
I can't imagine why we'd get a permission denied error while trying to
unlock a file we've just locked. Note that while this is new code for
1.4.2, we do the same file operations to manage locking for the fs-wide
write-lock, so it should work just the same.
Did 1.4.0 work okay?
> fresnel:wc > ls -Rlt /mnt/applic/repo/db/transactions/
> total 0
> drwxrwxrwx 1 aviel aviel 0 Nov 28 12:54 0-1.txn
> total 0
> This directory does not exist in the local repository, so I assume it holds
> info of the transaction being made.
That's right. Strange that it's empty, since I would have expected that
it'd either have files in it (such as the prototype revision lockfile,
for one), or it'd have been deleted completely. It's probable that we
encountered another error when trying to clean up the transaction
directory, so we left it alone.
> Any suggestions?
Yes - could you produce an strace of the failing 'svn import' command?
That might give us a clue as to whether the problem is happening at the
local or remote end. To save the bandwidth of everyone on this list,
could you open a new issue and upload the strace output as an
Received on Tue Dec 5 01:14:28 2006
- application/pgp-signature attachment: stored