Unable to check in objects under PB12.5 with SVN

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Checked out objects under PB11.2
2. Converted to PB12,5
3. Attempted to check in, either en masse or as indevidual object.

What is the expected output? What do you see instead?
Message 'Failed to check in ' <filename. This is also logged in Powerbuilders 
own log.
When I enabled PBSCC, I got this message in the logfile
<<SVNINFO
    svni->get( "C:\project\filename" , "C:\project\libs\filename" )=david
_SccQueryInfo: ms=3307
SccQueryInfoEx:
    svni->get( "C:\project\filename" , "C:\project\libs\filename" )=david
_SccQueryInfo: ms=0

What version of the product are you using? On what operating system?
2.01.80 with Powerbuilder 12.5

Please provide any additional information below.
This has been working under PB11.2. The workspace source control information is 
identical.  A few objects have checked in successfully, but it is not clear why.

Original issue reported on code.google.com by Dave.Har...@gmail.com on 28 Feb 2012 at 5:30

[GoogleCodeExporter]

Hello,
The log that you attached is not corresponding to checkout or checkin commands.
Please provide the full log.

Regards,
  Dmitry

Original comment by daggett....@gmail.com on 28 Feb 2012 at 6:08

[GoogleCodeExporter]

Here is the complete log file. Essentially I opened up the workspace, then 
tried to check in a single object.

Original comment by Dave.Har...@gmail.com on 29 Feb 2012 at 8:39

Attachments:

• PBSCC.log

[GoogleCodeExporter]

I even tried checking out one of the objects that had been successfully 
checked. I couldn't check it back in again.

Original comment by Dave.Har...@gmail.com on 29 Feb 2012 at 4:23

[GoogleCodeExporter]

I can see several calls of the command :
svn commit --non-interactive --trust-server-cert --targets "targets.tmp" --file 
"comment.tmp"

But there is no result in the log.

Can you test this command from command line.
The file "targets.tmp" must contain target files that you want to commit,
and "comment.tmp" must contain commit comment

Waiting for console output...

--
Regards,
  Dmitry

Original comment by daggett....@gmail.com on 29 Feb 2012 at 8:12

[GoogleCodeExporter]

I took this command from the logfile when I attempted checkin of two objects
svn commit --non-interactive --trust-server-cert --targets 
"C:\Users\DAVID\AppData\Local\Temp\pbsAD77.tmp" --file 
"C:\Users\DAVID\AppData\Local\Temp\pbsAD7A.tmp"
When run from Powerbuilder IDE I got a message that the checkin had failed.  I 
got no message at all when I ran this on the command line.
The first file contains the full paths of the objects
C:\xxxx\TR xxxx 12.5\source\xxxx\acc_dw_1\d_22_banklist.srd
C:\xxxx\TR xxxx 12.5\source\xxxx\acc_dw_1\d_22a_bankdetails.srd
The second file contains
CTR-240 test indevidual check in
which is the comment that I attached.

The reason I am going through this exercise is that we are moving our 
applications from PB11.2 to PB12.5.  I took a second, smaller application, 
checked it out with PB11.2, converted it to PB12.5, then tried to check it in 
and got the same problems as before.  After some rash experiments made that 
branch in SVN effectively useless, I copied another branch of the same code, 
repeated the exercise and it appears to have worked perfectly!  I am totally 
confused by this, but I'm wondering whether I should create a fresh branch of 
the original application, check out, convert, check in etc and see if the magic 
still works.

Original comment by Dave.Har...@gmail.com on 1 Mar 2012 at 9:17

[GoogleCodeExporter]

Before the SVN commit the amended source code is copied from lib to the source 
folder. It is clear from looking at the file system that this has worked.  I 
tried doing a Tortoise SVN commit for my source folder.  This apparently 
succeeded - Powerbuilder thinks the objects are checked in. The version numbers 
in Powerbuilder and Tortoise agree, but the timestamps do not.
I think the problem is this... The object source is no different under PB12.5 
to that under PB11.2.  While PBSCC copies the source, it doesn't commit it 
because the object appears unchanged.  In the same situation, Tortoise doesn't 
create a new revision, but it does release the lock.
Does this seem plausible?
Anyway, if the source files are unchanged, it seems to me that I might as well 
just modify our build scripts to export the source from SVN as usual and 
PowerGen it through PB12.5 rather than PB11.2

Original comment by Dave.Har...@gmail.com on 1 Mar 2012 at 10:07