PB9 setup issues & problems

( CVSSCC )

Type: Public Status:Closed Created: 28 Apr 04 04:00 Updated: 04 May 04 05:00

--> Igor Pushkov (admin) at 04 May 04 05:00 writes

I am sorry for delay with answer, we have some local Russia holidays
there.
So, It seems that all issues are resolved. I only want to comment
:sspi: protocol behavior:
1. To change :pserver: to :sspi: you should pull project to new
directory (or existing but with deleting all source controlled files
including CVS subfolders)
2. You not need to use your login name in CVSROOT, by default it is
your domain name.

--> Dan Cooperstock (user) at 30 Apr 04 04:00 writes

OK, I've resolved the problem of the PBLs that never seem to be connected.
What I did was to delete the directory containing the PB app, and copy down
from our network master copy only the PB workspace, target, and PBLs to a
recreated directory.

After that, everything's OK. Presumably there were some helper files in the
application's directory that were messing things up.

The larger PBLs do initially come up with only plus signs, but we can see
in the PB library painter that they are still Initializing (that word
appears in the title bar of the painter). That obviously happens in the
background, since we can still work in PB. If we wait a while they do come
up with the green circular arrow which means that they are connected to
CVS, but they need to be refreshed with a Get Latest Version in PB. (That
seems to happen the first time we connect a project on a 2nd PC with any
SCC system.)

--> Dan Cooperstock (user) at 29 Apr 04 04:00 writes

I tried the other user's PC again. To be safe, I deleted their PB workspace
and recreated it, then added back in the same target. Only two PBLs show
their objects as being registered (with the green dot). Interestingly
enough those are the ones that I had registered yesterday before this 2nd
user attached their PB project to CVS. It is the PBLs that I registered
(added to source control) AFTER the 2nd user connected that he is having
problems with.

The problem is that all objects in those PBLs show up with a plus sign on
his PC, which means they aren't registered (added) to source control. But
if we try to add them, we get a message back saying it failed, because they
were "added independently by second party". I haven't seen this problem in
other source code control systems I'm testing (Merant VM and Borland
StarTeam).

One thing I find very curious is that when either of us re-connects to
PushOK CVS Proxy after disconnecting the project from source control, and
we click on the ... to set the configuration properties, it still has
memorized our root path (e.g. :pserver:dancoo@sqltest2:/cvs) from the last
time it was connected to CVS. I can't figure out where that is being
stored.

--> Dan Cooperstock (user) at 29 Apr 04 04:00 writes

I already knew most of that - we've been using source code control with PB8
and PB9 for quite some time now. (We're checking alternatives because our
current version of MKS Source Integrity doesn't work quite right with PB9,
and it's very expensive to upgrade.)

I tried using :sspi: but when I set that up in PB, it reverts :pserver:.
(Should it still be :sspi:dancoo@sqltest2:/cvs, or do I remove "dancoo"?)

I haven't re-tested the multi-user problems yet. I'll get back to you after
that.

Thanks for all of your replies! That's great service for inexpensive
software we haven't even decided to buy yet! (I support some free software
myself, at www.FreeDonationSoftware.org, but the current investigations are
for my commercial day job.)

--> Igor Pushkov (admin) at 28 Apr 04 04:00 writes

PS. About adding new pbl files to source control. PB cannot
automatically recreate pbl files from source control. So, when you add
new pbl you should _manually_ move it to other pc, and this pbl should
be manually added to workspace. But after that it should appears as
controlled automatically (May be you also should move your workspace
file).
Sorry, but this is way how PB SourceControl integration work (not only
with our plugin).

--> Igor Pushkov (admin) at 28 Apr 04 04:00 writes

) When I\'m getting logged on, that prompts for a password, and it seems to
be my NT network password that works. (Is that transmitted over the wire in
a safe way?) Similarly, for the other user, I
) used his network logon instead of dancoo for the CVSROOT.
You can use user names on your network domain to access cvs
repositoty. It is not a requirement to use cvs as the user, it is just
a sample. You just need to know that domain users should have access
rights to the server location of repository, otherwise the will
receive error.
:pserver: protocol you use is not 100% secured. Password are crypted
but with very simple algorithm. For CVS NT, when client and server
running on windows platform is better to use :sspi:. Using this
protocol you even not need to specify your login name (by default used
your system name), and password transferred secure (using standard
windows functions).

--> Igor Pushkov (admin) at 28 Apr 04 04:00 writes

) First of all I\'m confused about your IDE tips. You say to either set
things up in PB (including NOT checking \"Perform diff on status update\")
or to click the \"Preset for PowerBuilder\" button
) in the SCC Proxy setup dialog. Is there a problem with doing both?
No this is not a problem doing both, but this is not efficient. I try
to explain. The key problem is PB option "Delete source control files
after SourceControl operation". By default it is switched off.
You may know, that PB do not work with source files directly, instead
it work with binary files (pbl). To make possible to add them to
source control it extract all objects from these files as text files,
and add to SourceControl these text files.
When mentioned option switched on (default), even is project is now
source controlled you not see there extracted text files, you only see
usual pbl and pbt files. That's way it may be switched on by default.
However, this situation is not standard for CVS. For CVS better that
source control files _exist_ on local, and without this we need to use
some tricks to make it working. These _tricks_ can be enabled in
plug-in pressing button "Preset for PowerBuilder".
However may be better to get chance to CVS work in expected behavior,
and switch of mentioned option. But after this, you project directory
will contain all extracted from pbl text files.
What we can found on internet about this does not 100% answer which
solution is better. We consider that better to adjust PB settings. But
this depends on your decision, since both methods working.
Also, may be you not find this link in docs, it can be helpful for
you:
http://www.sys-con.com/pbdj/article.cfm?id=271&count=10080&tot=4&page=1
) Also in the IDE tips you suggest perhaps turning on the \"Check server
for file status\". When I checked that, and the two sub-options below it,
opening a PBL became extremely slow! So I turned
) it back off.
We check this
) I thought we really needed to have \"Perform diff on status update\"
checked in PB, or it wouldn\'t refresh the statuses of objects
automatically. Is that not right?
No, this option 100% not needed for plug-in.
) I\'m also having some multi-user problems. I added all of the objects in
all of my PBLs to CVS, using your proxy. Then another developer connected
his copy of that PB application
We not heard about such issues. Please follow instructions on to
getting version on other PC:
http://www.pushok.com/help/cvsscc/index.php?redirect=basic_getfromscc.htm
PB have some hard hard behavior there, but this should help. Also
again take look to mentioned article.
Let me know if this not help

--> Dan Cooperstock (user) at 28 Apr 04 04:00 writes

Sorry, one more question. Are we only supposed to use the username cvs when
connecting to the root project on the CVS server? Because I set each user
up with their own network logon name. For instance, I am dancoo, so my
CVSROOT was:

:pserver:dancoo@sqltest2:/cvs

When I'm getting logged on, that prompts for a password, and it seems to be
my NT network password that works. (Is that transmitted over the wire in a
safe way?) Similarly, for the other user, I used his network logon instead
of dancoo for the CVSROOT.

Is that correct?

--> Dan Cooperstock (user) at 28 Apr 04 04:00 writes

We're testing this out with PB9.

First of all I'm confused about your IDE tips. You say to either set things
up in PB (including NOT checking "Perform diff on status update") or to
click the "Preset for PowerBuilder" button in the SCC Proxy setup dialog.
Is there a problem with doing both?

Also in the IDE tips you suggest perhaps turning on the "Check server for
file status". When I checked that, and the two sub-options below it,
opening a PBL became extremely slow! So I turned it back off.

I thought we really needed to have "Perform diff on status update" checked
in PB, or it wouldn't refresh the statuses of objects automatically. Is
that not right?

I'm also having some multi-user problems. I added all of the objects in all
of my PBLs to CVS, using your proxy. Then another developer connected his
copy of that PB application (on the same directory on his C: drive as I
have my copy on my C: drive) to CVS. But he can only see that 2 out of
about 8 of the PBLs have their objects added to source control. The others
(which I did add) appear to not be added, but if he tries to add them, he
gets an error message saying they are already added.

Help! Thanks.

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

PB9 setup issues & problems