SVN and SSH?

I have crash when using SSH.

Do I need SSH when using SF.NET?

@LiveForIt

It's difficult to tell what went wrong because I don't know what "get_mplayer" is but I'm guessing that it's a script containing the checkout commands so that you don't need to type long checkout lines. I just checked out the mplayer trunk from sf.net and it's huge! (800+ MB)

Assuming that the commands in get_mplayer were incorrect, I'll tell you how I checked out the sources. I've never been able to get OS4 Subversion (SVN) to work with the new repository access methods at sf.net. I use the old HTTP method. Here is how I checked out the trunk:

svn co https://svn.code.sf.net/p/mplayer-for-amigaos/code/trunk mplayer

The checkout took almost a half hour with my slow Internet connection. If you've never worked in an sf.net repository, you may get prompted for a password when you checkout the code or commit for the first time. It's possible that you may get an SSL certificate errot the first time you enter your password. I started getting those errors last year but abalaban has a workaround that causes SVN to ignore SSL errors. Refer to the topic "Subversion certificate error" in the AmigaOS4 forum here at Amigans.net if you encounter that problem.

P.S. If you want to check out the entire mplayer repository you might use:

svn co https://svn.code.sf.net/p/mplayer-for-amigaos/code mplayer-repo

@xenic

Quote:

Well yes, this is the check out line I'm using:

svn checkout --username=liveforit svn+ssh://liveforit@svn.code.sf.net/p/mplayer-for-amigaos/code/trunk mplayer-for-amigaos-code

I tried with out "+ssh", that works, but then I can't commit the changes to repository, so that wont work. I read some where that you most use +ssh when you use SF.net.

Quote:

Yes SVN is slow, in addition some smart ass put some benchmark videos in repository, this films are big. Once you have downloaded it SVN its fast committing changes, so initial download time does not matter much.

Quote:

http://www.amigans.net/modules/xforum ... m=25&topic_id=6706&order=

@xenic

Don't think that worked, or maybe I'm doing some thing wrong.

maybe its time check out sgit, hopefully its usable.

@LiveForIt

It reads the servers file, but it does not do anything.

@LiveForIt
The svn+ is the new method that has never worked for me. Try this:

svn checkout --username=liveforit https://svn.code.sf.net/p/mplayer-for-amigaos/code/trunk mplayer

or try:

Perform an anonymous checkout with: (notice http - not https)
svn checkout http://svn.code.sf.net/p/mplayer-for-amigaos/code/trunk mplayer

Then cd into the mplayer directory that you just checked out and try to make a commit. SVN should ask for username and password and then ask if you want to save. Once that is done all you have to do is enter the mplayer directory to enter commands and commit stuff.

NOTE: There is a space between trunk & mplayer in the above commands.

EDIT: Did you create an assignment for the Subversion config files?
assign subversion: Work:subversion (or wherever).

@LiveForIt

Silly question but do you have ssh instaled and does ENV:SVN_SSH point to it?

I don't know if that will work, but it certainly wont if you don;t

@broadblues


I do not have a SVN_SSH file in ENV:

What format should the path be in Linux or a Amiga format, o_O.

where should the private key for SSH be store anyway?
In devs:ssh or home:.ssh?

@LiveForIt

Don't know about path format in SVN_SSH could be either, try one and see what errors you get in the snoopy log, as I said I don't know if it will work, but it's something you need setup before it will work, if it will.

SSH stores it's stuff in

HOME:.ssh

it should put the leys in there auto matically as long as you have a HOME: assign created.

SVN needs a Subversion: assign (I'd guess you probably have that).

@LiveForIt

I dont know the ssh problems, but the DSI problem can be
a too small stack size, svn it's not using the cli stack size,
but only 200000 bytes it's in the snoopy log, for increase it
you must set the SVN_STACK_SIZE env variable, the reading
of this variable fail in your snoopy log, try something like
2000000 (ten times the default)

@pvanni

After seting SVN_SSH and SVN_STACK.

5.Work:pro_2014_svn> svn checkout --username=liveforit svn+ssh://liveforit@svn.code.sf.net/p/mplayer-for-amigaos/code/trunk mplayer-for-amigaos
svn: This function has not been implemented on this platform
5.Work:pro_2014_svn>

It's clear that SVN is too old and outdated.

@broadblues

Trying SGIT now.

It does download from https, but its slow, can't be many kb/s per sec. It be interesting to see if I can commit changes, to GIT repository, once I have downloaded the code.

@LiveForIt

Ok, I think SGIT works, its bit silly it allows me to commit changes even if I have not changed anything.

And also SGIT commit –m "my comment", does not commit to server, only locally, so I have to do.

SGIT push origin master

I don't get way I need to say origin master, does it not know I'm working on master?

But anyway it works.

SGIT pull origin master

Does not work yet, so its ok as long as I'm the only one working on it, if two people commit to the same repo, it get messy I think.

@LiveForIt

That's GIT for you. It clones entire repos, inherently inefficient IMHO It's designed for projects that fork a lot, rather than projects where most work is shared in a central repo.

But it's the fashion now, till the next idea comes alomg.

@broadblues

It's clear that SGIT needs a lot of work, but it works better than an outdated SVN. I'm sure it will improve.

Inefficacy might be simple due to lack threading or something like that in the network code, the first thing people remove from the code when porting to AmigaOS is fork(); that does mean they replace it with something that works on AmigaOS.

I have used GIT on Linux and it works fine, GIT for windows, is simply too easy to use. Generate private key /pub key is done for you automatically.

SGIT I think ignores public & private keys, at least I most type password and username every time I do a sgit push.

@LiveForIt

Quote:
Have you tried the https:// checkout method that Xenic suggested? Soureforge also allows read/write access via https (link).

Quote:
That's how git works. If you're using git instead of sgit then commit also only commits changes to your local repository copy, and you need to "git push" your commit to the remote "origin master." I use Tortoisegit on Windows, which takes care of this stuff.

Git takes some getting used to if you're used to svn's way of doing things.

Hans