On Apr 12, 2007, at 15:55, David Jacopille wrote:
> Just did clean install of 1.4.3 with deps on OS X 10.4.9 and am
> attempting
> to follow the basic instructions in the SVN documentation
> explicitly but I'm
> not getting very far. I’m not using Apache or WebDAV – I’m working
> locally
> in all cases. Please review and provide suggestions. Thank you!
>
> Step 1: Create: Seems to work OK – it creates a directory with SVN
> stuff in
> it.
> svnadmin create --fs-type fsfs /Volumes/bosotoraid/svn/chart_svn/
>
> Step 2: Import: Possibly some problems
> Here I’m importing everything in the ~/stuff_to_import folder
> which has
> 4 things in it:
> ~/stuff_to_import/branches/
> ~/stuff_to_import/trunk/
> ~/stuff_to_import/release_tags/
> ~/stuff_to_import/trunk/TECHNICAL RELEASE NOTES.dot
>
> svn import ~/stuff_to_import file:///Volumes/bosotoraid/svn/
> chart_svn -m
> "initial import"
>
> Adding /Users/djac/stuff_to_import/trunk
> Adding (bin) /Users/djac/stuff_to_import/trunk/TECHNICAL RELEASE
> NOTES.dot
> svn: Can't get exclusive lock on file
> '/Volumes/bosotoraid/svn/chart_svn/db/transactions/0-1.txn/rev-lock':
> Operation not supported
>
> also tried ‘chmod –R 777 /Volumes/bosotoraid/svn/chart_svn/*’
> but that
> did not improve the import.
Ok, so an error occurred.
> Step 3: List: Generates no output or errors
> svn list file:///Volumes/bosotoraid/svn/chart_svn/
Since an error occurred, the import was aborted, so it is correct
that you should see no output from svn list since there is nothing in
the repository to list.
> Step 4: Checkout: Confirms I checked out revison 0 but there’s no
> evidence
> of anything having happened.
> svn checkout file:///Volumes/bosotoraid/svn/chart_svn/ /Volumes/
> USB/svn/
>
> Checked out revision 0.
>
> The command ‘ls –la /Volumes/USB/svn/’ lists no chart_svn
> directory or
> any other new files.
Also correct. No import occurred, so your repository still only has
revision 0, the initial empty revision.
What is /Volumes/bosotoraid? Is it a local disk or a mounted network
drive? Network drives can be problematic, so try a local disk
instead. If it is already a local disk, then try your internal hard
disk anyway, just to try a "completely normal" disk for comparison.
If it works there (and it should) then there is a problem of some
kind with this other disk you're using. If it's a network disk, how
are you accessing it? NFS? SAMBA? AppleShare? SAN? Switching the
connection method could improve the situation. A SAN connection
should definitely work, since that makes the disk a local disk as far
as the computer can see, but the others may not work.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 13 00:38:14 2007