Questions? Feedback?powered byOlark live chat software
Bug 3309

SVN Update does not work on Target 15 October, 2019

Ludwin Feiten
09 September, 2019
Product: PowerBuilder Category: Other
Version: 2019 Publishing: Public
Classification: Priority: P3
Status: Reproducing Reason:
Tom Jiang 15 October, 2019
Hi Ludwin,

Sorry, we can't reproduce the issue on our side!
1. Can you use TortoiseSVN to check the objects in question and see if they are in the repository? 
2. Please let us know if you can reproduce it with a simple test case and provide it to us for further analysis. 

Thanks & Regards,

Tom Jiang
Ludwin Feiten 15 October, 2019
Hi. 
Anything new?
Can you find out where "An explicit update tried to update the path" and  "hat doesn't live in the repository and cannot be brought in." is issued? Do you get this back from SVN?
Ludwin Feiten 17 September, 2019
Hi Tom,

#1. We haven't moved any Objekts or PBL in the Windows Explorer. All Changes made inside PowerBuilder and were commited to the repository.

#2. All changes are commited to the repository, but the error still exists.

#3. We get the same error on different machines, with different users and also, when we connect to the workspace in a new empty folder.
Tom Jiang 10 September, 2019
Hi Ludwin,

#1. Have you moved some of the objects or PBLs using the Windows Explorer but didn't commit the change to the repository?
#2. If you commit everything in the workspace, do you still get the error when doing an SVN Update? 
#3. If you check the workspace to another folder using Connect to Workspace, do you still get this issue? If you don't get the issue, can you compare it with the one in question and see if there any differnces that might be causing this issue?

Regards,

Tom Jiang
Chris Pollach 09 September, 2019
Hi Ludwin;

  Thank for that detailed information! I personally do not have any suggestions for you at this time on your issue. However, I will now transfer this ticket over to the main Support/Engineering team for their feedback on your problem.

Regards ... Chris
Ludwin Feiten 09 September, 2019
*Phenomenon:
I do an "SVN Update" on the target and I get a lot of this messages for multiple PBLs.
- An explicit update tried to update the path [C:\Projekte\Sozialoffice\Entwicklung\PB2019\SO\auswertung\beschaeftigung] that doesn't live in the repository and cannot be brought in.
- An explicit update tried to update the path [C:\Projekte\Sozialoffice\Entwicklung\PB2019\SO\ws_objects\auswertung\beschaeftigung] that doesn't live in the repository and cannot be brought in.
- An explicit update tried to update the path [C:\Projekte\Sozialoffice\Entwicklung\PB2019\SO\ws_objects\auswertung\beschaeftigung\beschaeftigung.pbl.src] that doesn't live in the repository and cannot be brought in.
It is always this three messages.

Then I select the respective PBL and perform a "SVN Update". Now I get the objects:
SVN update
SVN client is updating files. Please wait...
Updating the updated file: C:\Projekte\Sozialoffice\Entwicklung\PB2019\SO\ws_objects\Auswertung\beschaeftigung\beschaeftigung.pbl.src\n_cst_so2_beschaeftigung_wizardrule.sru.
Updating the updated directory: C:\Projekte\Sozialoffice\Entwicklung\PB2019\SO\ws_objects\Auswertung\beschaeftigung\beschaeftigung.pbl.src.
Updating the updated directory: C:\Projekte\Sozialoffice\Entwicklung\PB2019\SO\ws_objects\Auswertung\beschaeftigung.
Importing n_cst_so2_beschaeftigung_wizardrule.sru . . .
Compiling types for n_cst_so2_beschaeftigung_wizardrule.sru . . .
Regenerating n_cst_so2_beschaeftigung_wizardrule.sru . . .
Successful get of C:\Projekte\Sozialoffice\Entwicklung\PB2019\SO\Auswertung\beschaeftigung\beschaeftigung.pbl(n_cst_so2_beschaeftigung_wizardrule.sru)
SVN update success.
SVN update completed.
 ---------- Done Source Control

*Reproduce Steps:
don't know. This error occures not to all of our project - but many.

Remarks:
If engeneering knows what couses the message 
"An explicit update tried to update the path [ ...\ws_objects\....pbl.src] that doesn't live in the repository and cannot be brought in." 
we could use any hint .

We use: TortoiseSVN 1.11.1, Build 28492 - 64 Bit , 2019/01/08 21:40:39 ipv6 enabled
Subversion 1.11.1, -release apr 1.6.5
OS:
All 
Platform:
64-bit 
Database Type:
 
Database Version: