I tried to commit via a web-interface (php calling svn), and the permissions
were wrong; the user couldn't write to a file in the working copy to set
a new status, IIRC.
Now I've got a kind of problem:
1) I can't commit
2) I can't recover
3) svn st says the files are to be committed.
How can I get my working set working again?
(See near the end of this mail for the various outputs of svn)
This is svn #5697.
And, BTW, another question.
If there are several user with each a working set, the files therein
are mostly the same. (I'm speaking about ~500MB data, so ~1GB working set,
multiplied by some number of users ... a whole lotta bytes :-)
I've got a script which (hard-)links files if they have the same data.
As far as I see (using strace(), looking briefly into source) svn ALWAYS
creates a temporary file and renames that after modification.
So it should be safe to use the hardlinks, should it not?
Or am I missing something?
At least in the working copies there should be no harm; but if I may hardlink
text-base-files too, it would be a major saving.
(Say, from n users * 2 * 500MB to 500MB + 10% ...)
# svn ci -F svn-commit.2.tmp
Adding (bin) sw/clone/PnPDrv/Other/sccmn50m.cab
svn: Item already exists in filesystem
svn: Commit failed (details follow):
svn: file already exists: filesystem `/svnroot/repos/clone/db', transaction
`o', path `/sw/clone/PnPDrv/Other/sccmn50m.cab'
# svnadmin lstxns /svnroot/repos/clone
# svnadmin recover /svnroot/repos/clone
Acquiring exclusive lock on repository db.
Recovery is running, please stand by...
The latest repos revision is 4.
# svn st
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Apr 25 19:32:46 2003