heeyeonwiz / pbscc-proxy

Automatically exported from code.google.com/p/pbscc-proxy
0 stars 0 forks source link

PBSCC 2.00.59 incompatible with TortoiseSVN 1.7 #30

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Install TortoiseSVN 1.7, including svn command line
2. Upgrade existing working tree which PB 10.5 / PBSCC 2.00.59 is pointed 
towards
3. Open Powerbuilder project

What is the expected output? What do you see instead?

All objects appear to not be under source control in PB, when they are actually 
still under source control (when viewed from a non-upgraded computer).

What version of the product are you using? On what operating system?

PBSCC 2.00.59, Powerbuilder 10.5 EBF 14592, Windows XP Professional 2002 SP 3

Please provide any additional information below.

See http://tortoisesvn.net/tsvn_1.7_releasenotes.html ... 1.7 is a big change 
for TortoiseSVN.

Original issue reported on code.google.com by toff.til...@gmail.com on 2 Nov 2011 at 11:47

GoogleCodeExporter commented 8 years ago
What lock strategy are you using?

Original comment by daggett....@gmail.com on 3 Nov 2011 at 5:29

GoogleCodeExporter commented 8 years ago
It's the lockby property strategy. I had tried the newer strategy but it
didn't seem to work well, when we set up our PBSCC about 6 months ago.

Original comment by toff.til...@gmail.com on 3 Nov 2011 at 5:37

GoogleCodeExporter commented 8 years ago
"lock" strategy works fine. 
it should work with new version of svn.
if you have troubles just ask questions or open an issue...
--
about "prop" strategy:
it uses file parsing of the .svn/entries file
it seems in the version 1.7 of svn the sqlite database used to store work copy 
information...

development required...

Original comment by daggett....@gmail.com on 3 Nov 2011 at 5:44

GoogleCodeExporter commented 8 years ago
just an idea:

it should be possible to write sql that will retrieve data into same xml 
structure as
returned by the command:

svn stat --xml --non-interactive --trust-server-cert -u -v "WORK_COPY_PATH"

in this case parser already written and minimum work is required in cpp code.

Original comment by daggett....@gmail.com on 3 Nov 2011 at 7:05