- You are here:
-
Home
-
Q&A
-
Q&A
-
PowerBuilder
- SVN at 2017 R2 does not work
-
Robert Inzinger
- PowerBuilder
- Friday, 2 February 2018 08:29 AM UTC
After I delete the Workspace folder and the subversion repository folder, and recreating both new i can add the workspace.
But if I try to commit the workspace PB IDE hangs:
Do you already attempt to connect the files to a subversion repository using something like TortoiseSVN? Was this something that was already associated with a Subversion server?
Look for a 'hidden' .svn folder in the workspace directory. You may need to turn on "show hidden files and folders" in Windows Explorer to see it. If you find one, delete it. That's the SVN configuration data. It sounds like it's already pointed to something. Deleting it and then reattempting to connect the workspace to Subversion again.
Depending on the version of Subversion you may need to check subfolders for the .svn folder as well.
- Bruce Armstrong
- Saturday, 3 February 2018 22:31 PM UTC
- Robert Inzinger
- Monday, 5 February 2018 07:09 AM UTC
I use TortoiseSVN 1.9.4 and Subversion 1.9.4. We use Subversion for our source control for none Powerbuilder projects and it works fine.
I create a new empty folder in our repository to and our workspace.
After I try to add to Repository there was no .svn folder.
- Page :
- 1
However, you are not allowed to reply to this question.
If you have not added the whole workspace to source control yet, it is not possible to commit only PBLs.
Can you please follow the instructions provided in Bruce's article to add your workspace to source control: https://community.appeon.com/groups/powerbuilder/powerbuilder-2017-r2-new-feature-subversion-svn-source-control-support?
Regarding the error "The specified path is already a working copy for a different URL", the most possible reason is that the local directory that stores the workspace is already under source control before you perform the current operation.
Best regards... Julie