Re: [Oorexx-devel] Failure in committing...
On Fri, Aug 17, 2012 at 10:03 AM, Mark Miesfeld miesf...@gmail.com wrote: Be sure and read the tortiseSVN guide I pointed you to. I didn't read it, but I'm sure it explains how to use svn+ssh with tortiseSVN. Oliver, The doc is short, it is at: https://sourceforge.net/p/forge/community-docs/TortoiseSVN/ Taking a look at it, it says not much configuration change needs to be do to TortoiseSVN. So, I think your problem is just that you didn't update your URL. The doc says TortoiseSVN will prompt you for your password each time you commit. The doc is mostly about how to set things up so you don't get prompted. You need to check out a *new* fresh copy from the repository using a URL similar to this: svn+ssh://miesf...@svn.code.sf.net/p/oorexx/code-0/ooDialog or svn+ssh://miesf...@svn.code.sf.net/p/oorexx/code-0/docs/trunk/oodguide but replace miesfeld with your SourceForge ID of course. Use a new directory, don't overwrite your existing directory. Once you do that, merge any changes you have made, but not checked in, from your old working copy into your new working copy. Then commit. If you still have problems, let us know. -- Mark Miesfeld -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Failure in committing...
OK. I have managed to do this (as far as the checking out a new repository goes). Here is how I managed 1) Navigate in windows explorer to the root of the old svn 2) right click choose SVN checkout from the tortoise section of the context menu 3) copied Mark's provided URL, substituting my sourceforge userid for his and leaving off the subdirectory ie svn+ssh://sahana...@svn.code.sf.net/p/oorexx/code-0/http://miesf...@svn.code.sf.net/p/oorexx/code-0/ooDialog When you type in the url, tortoise automatically edits the target directory to create a new tree 4) Hit OK 5) I was then faced with four prompts (I'm no longer sure of the order). One of them asked if I trusted the server, and offered to store the key in the registry, the other three with no explanation asked for a password. I said yes to storing the key and typed my sourceforge password into the three prompts. I am now recieving a new copy of the repository. hth Jon On 18 August 2012 07:44, Mark Miesfeld miesf...@gmail.com wrote: On Fri, Aug 17, 2012 at 10:03 AM, Mark Miesfeld miesf...@gmail.com wrote: Be sure and read the tortiseSVN guide I pointed you to. I didn't read it, but I'm sure it explains how to use svn+ssh with tortiseSVN. Oliver, The doc is short, it is at: https://sourceforge.net/p/forge/community-docs/TortoiseSVN/ Taking a look at it, it says not much configuration change needs to be do to TortoiseSVN. So, I think your problem is just that you didn't update your URL. The doc says TortoiseSVN will prompt you for your password each time you commit. The doc is mostly about how to set things up so you don't get prompted. You need to check out a *new* fresh copy from the repository using a URL similar to this: svn+ssh://miesf...@svn.code.sf.net/p/oorexx/code-0/ooDialog or svn+ssh://miesf...@svn.code.sf.net/p/oorexx/code-0/docs/trunk/oodguide but replace miesfeld with your SourceForge ID of course. Use a new directory, don't overwrite your existing directory. Once you do that, merge any changes you have made, but not checked in, from your old working copy into your new working copy. Then commit. If you still have problems, let us know. -- Mark Miesfeld -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Failure in committing...
You need to check out a *new* fresh copy from the repository using a URL similar to this: svn+ssh://miesf...@svn.code.sf.net/p/oorexx/code-0/ooDialog or svn+ssh://miesf...@svn.code.sf.net/p/oorexx/code-0/docs/trunk/oodguide Ah-Ha! Many thanks, Mark, it all works now. I'd been using http: not svn+ssh (which is new to me - but then I've never needed to bother about the various formats of URLs). Btw, you might like to have a look at the Customer compoment in Ex07. It makes use of a model-view framework aimed at making coding of app dialogs a lot easier (i.e. when you have multiple dialogs in an app). The Order and Product components don't yet use this framwork, and barf if they're started from the Order Management dialog. So, dbl-click startup.rex to get the OrderManagement dialog. Then dbl-clk on Customer List and then dbl-clk on a Customer - it now opens with its correct data. Also, under Help on the Order Management dialog, there's an item called MessageSender. This aims to replace the function of stand-alone execution of individual components that was in Exercise06. Selecting Message Sender opens a message sending dialog. You can then exercise individual components. For example, try entering the following: Target: CustomerModel CU0003 Method: query Data: nothing Then press Send. The data held by the CustomerModel component is returned. Also, try sending a showmodel message to target ObjectMgr The with the data CustomerModel CU0003 An instance of Customer (the one whose key is 'CU0003') pops up. Btw, the copious messages on the console are temporary. Atb, Oliver -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Failure in committing...
Using TortoiseSVN, I just tried to commit some stuff and got: Command: Commit Error: Commit failed (details follow): Error: Access to '/p/oorexx/code-0/!svn/act/7245f0f6-5ee3-0244-97bb-49b8c9753ae1' Error: forbidden Completed!: I guess this is to do with the password stuff that was discussed on this list a couple of days ago? (Although updating from the repos worked fine.) -- Oliver Sims -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Failure in committing...
Oliver, Be sure and read the tortiseSVN guide I pointed you to. I didn't read it, but I'm sure it explains how to use svn+ssh with tortiseSVN. You are going to need to use svn+ssh to commit for now to prevent corruption. Once you get it set up, it is just as easy to work with as it was before. This post of mine: Command line svn+ssh in Windows directions also explains how to generate the private key you will need. -- Mark Miesfeld On Fri, Aug 17, 2012 at 9:18 AM, Oliver Sims oliver.s...@simsassociates.co.uk wrote: Using TortoiseSVN, I just tried to commit some stuff and got: Command: Commit Error: Commit failed (details follow): Error: Access to '/p/oorexx/code-0/!svn/act/7245f0f6-5ee3-0244-97bb-49b8c9753ae1' Error: forbidden Completed!: I guess this is to do with the password stuff that was discussed on this list a couple of days ago? (Although updating from the repos worked fine.) -- Oliver Sims -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
