Unable to restore deleted objects when switching back to former revisions in PowerBuilder

Thank you for your quick reply.

We tried your cheat and it works. That solution is not perfectly satisfying
in case we want to switch back the whole project to a former monthly patch
level, but a least it is a possibility when deleted objects will be causing
trouble.

We also found another workaround in using tags. Deleted files are restored
correctly whenever we switch back to a previous tag and perform
GetLatestVersion twice. The workaround is working properly on condition
that at least one existing object in the PBL containing the deleted files
is checked for GetLatestVersion.

Dear PushOk-Team,

we are currently evaluating PushOk SVNSCC Proxy for use with PowerBuilder
10.2 IDE. We want to migrate a large project (approx. 9500 objects) from a
PB Native10 repository to Subversion source control system.

The plug-in is working fine so far, but we encountered a problem when
restoring deleted files. When trying to switch back to an older revision
(using "GetLatestVersion->Advanced->Update to Revision" or using
"GetLatestVersion->Advanced->Switch to Revision") there is no possibility
to restore files that have been deleted in the current revision. Whilst
existing files are correctly updated to the desired revision, files removed
in the meantime do not appear in the list of source control items.

We suppose there is a problem applying the appropriate pbg-file to the list
of source control items after using the advanced GetLatestVersion dialog.
Deleted files are received properly but do not get imported when switching
back to the older revision where the files still existed. The corresponding
pgb-file remains the content of the head revision. It is not even possible
to import the files manually. PowerBuilder stops with the message: "Import
failed. Entry is not checked out and therefore cannot be overwritten."

By the way we found out that there seems to be a difference in treating the
pbg-file between the options "GetLatestVersion->Advanced->Remove File fom
SVN Repository" and the PB option "Entry->Source Control->Remove from
Source Control". Please have a look at the added log messages in order to
reproduce our test scenario.

We are wondering whether you could give us any idea to solve the mentioned
problem.

Regards,
Ronny Plontke