Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

How do you commit correctly?

<< < (2/4) > >>

Pecan:
thanks

But I don't even know what tortoiseSVN is. I entered the
cmd from WinXPsp2 cmd.exe winow while sitting in the
checked out /truck directory

thanks
pecan

thomas:
You cannot commit using svn://
Either you have to use svn+ssh:// or you use https://

You have a user account at BerliOS set up, I assume?

Pecan:
thanks thomas


Yup, I created an account and got confirmation from Berlios.

I changed the svn line as instructed, but get the following reply


--- Code: ---
C:\Usr\Proj\cbBeta\trunk>svn --username {me} --password {mypassword} commit svn+s
sh://svn.berlios.de/codeblocks/trunk
svn: Can't check path 'svn+ssh:\\svn.berlios.de\codeblocks\trunk': The filename,
 directory name, or volume label syntax is incorrect.

C:\Usr\Proj\cbBeta\trunk>

--- End code ---

thomas:
Lol, wait, it does not work that way :)

1. You need a BerliOS account, but accounts are only updated via a cron job every 6 hours. So if your notice is not 6 hours old, then you will have to wait.

2. You have the choice of typing in your password a thousand times or using public key authentication instead. I strongly recommend the latter because it is not only more secure, but also more convenient.

3. Authentication tokens, too, are only updated every 6 hours, so do that NOW and save some time :)

4. You will either need Putty to create the SSH tunnel or you can use TortoiseSVN. You should get Putty in any case, because you need the key generator. Google for "putty", the first hit will get you there. Download the zip file that says "containing all the binaries": http://the.earth.li/~sgtatham/putty/latest/x86/putty.zip

5. Unpack, scan for viruses, and launch PUTTYGEN.EXE. Hit "Generate" and move the mouse until it is done, then enter your passphrase. Save your private key.
Copy the string in the textfield on top. This is important. You cannot just save the public key and upload that file, this won't work. You must copy the stuff in the "Public key for pasting...." field.
Go to the BerliOS site, log into your user account, go to "Account Options" and scroll all the way down. Click on "Edit keys" and paste your key there. Submit.

Sit back and relax while I type on, we have 6 hours now ...

6. Now you have the choice of using svn via the commandline or using TortoiseSVN. I occasionally use commandline for specific tasks, but generally you will want to use TortoiseSVN because it is a lot more convenient: http://tortoisesvn.tigris.org
Download that and install it (if you want, that is).

7. Open Putty.exe and enter svn.berlios.de under host name, and 22 under port name. On the left, go to Connection->Data and enter your username into "Auto-login username". Under Connection->SSH->Auth, click on "Browse" and locate the private key file that you saved earlier.
Click onto "Session" on top to get back to the first screen, enter a session name and save that session.
Put Pageant.exe into your autostart folder. Pageant will cache your passphrase in RAM, so you only have to enter it once. Edit the shortcut to pageant in your startmenu so it looks like C:\path\to\pageant.exe C:\path\to\private.key. Then pageant will load your key at startup and ask for the passphrase to unlock it, that is the most painless way.

8. If you plan to use command line, go to %APPDATA%\subversion and edit the file config. If you only use TortoiseSVN, you can skip this. Uncomment the section [tunnels] and enter the path to plink.exe like this:
[tunnels]
ssh = C:/tools/plink.exe
Be sure to use slashes, not backslashes. It will not work if you use backslashes.

9. Now for the actual work:
If you use TortoiseSVN, make a new folder, open that folder, and right-click inside it. Select "SVN Checkout..." and enter svn+ssh://YOURUSERNAME@svn.berlios.de/svnroot/repos/codeblocks/trunk into the dialog. Confirm and wait a few seconds. Then go to your plugin's folder and replace the files in there with your new files (but do not touch the .svn folder!). Right-click and select "SVN Commit...", you will be asked for confirmation and have the chance to select/deselect individual files and enter a comment. Click OK and you are done.
If you use command line, make a folder, navigate there, and type:
svn svn+ssh://YOURUSERNAME@svn.berlios.de/svnroot/repos/codeblocks/trunk. Put in the new files.
Then do a cd src\plugins\contrib\keybinder and type svn commit -m "A MESSAGE DESCRIBING YOUR CHANGES".

Urxae:

--- Quote from: Pecan on December 14, 2005, 05:09:58 pm ---
--- Code: ---
C:\Usr\Proj\cbBeta\trunk>svn --username {me} --password {mypassword} commit svn+s
sh://svn.berlios.de/codeblocks/trunk
svn: Can't check path 'svn+ssh:\\svn.berlios.de\codeblocks\trunk': The filename,
 directory name, or volume label syntax is incorrect.

C:\Usr\Proj\cbBeta\trunk>

--- End code ---

--- End quote ---

Try it without the URL. The commit command doesn't need it, it's saved in the working copy. In this case that working copy will have to be checked out using svn+ssh or https though. TortoiseSVN's "Relocate" command might come in handy if you didn't check it out that way (I'm not sure how to do this using command-line SVN).
Since you probably only want to commit the plugin and not any other changes you may have made you might also want to put "plugins\contrib\keybinder" where the URL used to be.

Navigation

[0] Message Index

[#] Next page

[*] Previous page