Return-Path: Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: (qmail 37400 invoked from network); 13 Jan 2011 07:40:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Jan 2011 07:40:12 -0000 Received: (qmail 86153 invoked by uid 500); 13 Jan 2011 07:40:11 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 85516 invoked by uid 500); 13 Jan 2011 07:40:09 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 85509 invoked by uid 99); 13 Jan 2011 07:40:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jan 2011 07:40:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of djcbecroft@gmail.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qy0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jan 2011 07:40:04 +0000 Received: by qyk32 with SMTP id 32so4607460qyk.16 for ; Wed, 12 Jan 2011 23:39:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=G4m3lJp4wtymXkIFPHKnJ1jZm3MHrsqJ2uFOpxw7f2s=; b=FdN0NSbEf9seSu1YLWQ+l/gu15W7ana50NsxEONr4K1o6rhwtXiuAjmmmoODGiIdcW h9Q/enkYendu2I2qpI3KbCOobQiSo/sO0qxPi+Qbdu7zhTbr9OFYXeLj0VkOTNWMPEUm 1yESrW7KwtJ2nw1fuN3PN+Km5/BFFxkgNLAJY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=pMK+TjnQa29GmgGH9v5vpv6FKWF4Ss9jPftLDean+2OTiXStOIHmUyIhaYUn6W0rmd Az4ovMJmVbOx13xdRuXU9CLkfmD+YTdmA44DulHnQc26Ri2jYEEEKswIzemOdD7Ql7pb I8lrGel0p0Jyt5Ye/TJfU9rBJ3X7+/JONhEjY= Received: by 10.229.233.18 with SMTP id jw18mr1685857qcb.122.1294904381922; Wed, 12 Jan 2011 23:39:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.218.212 with HTTP; Wed, 12 Jan 2011 23:39:21 -0800 (PST) In-Reply-To: <7D9DAFB3B4BB25428AC1E4360D5A94618BC4AE@KOL-SLK-MBX01.wipro.com> References: <81939A763626854B8ECA106278B28F34010F13FD@BLR-SJP-MBX02.wipro.com> <4D2DB341.5030108@elego.de> <7D9DAFB3B4BB25428AC1E4360D5A94618BC4AE@KOL-SLK-MBX01.wipro.com> From: Daniel Becroft Date: Thu, 13 Jan 2011 17:39:21 +1000 Message-ID: Subject: Re: SVN Subversion- object level checkout To: amit.sasmal@wipro.com Cc: mdiers@elego.de, users@subversion.apache.org, sudip.datta@wipro.com, pabitra.mallick@wipro.com, avik.nandi@wipro.com, sourav.sroy@wipro.com Content-Type: multipart/alternative; boundary=0016363b8fbcb3e2810499b56b58 --0016363b8fbcb3e2810499b56b58 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Jan 13, 2011 at 5:24 PM, wrote: > Hello Micheal, > > Thanks for your mail. > > We are using Tortoise SVN-1.6.7 alongwith Power Builder 11.5. > > We want to lock (check-out) the core power builder object from SVN so > that only one user can modify the object for that time. For this case, > If we want to open the workspace from the repository (SVN) we are > getting the attached message. > > Please let us know the correct process for the Power Builder connectivty > with the proper Tortoise SVN SCC version to lock the core PB object. > > Appreciate your quick help. > > Regards, > I'm guessing that .PBW file relies on the rest of the files in that directory. You'll need to checkout that directory prior to opening. Cheers, Daniel B. > Amit Sasmal. > Wipro Technologies. > > > -----Original Message----- > From: Michael Diers [mailto:mdiers@elego.de] > Sent: Wednesday, January 12, 2011 7:27 PM > To: SOURAV ROY (WT01 - Manufacturing) > Cc: users@subversion.apache.org; Sudip Datta (WT01 - Manufacturing); > Pabitra Mallick (WT01 - Manufacturing); Avik Nandi (WT01 - > Manufacturing); Amit Sasmal (WT01 - Manufacturing) > Subject: Re: SVN Subversion- object level checkout > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 2011-01-12 09:57, sourav.sroy@wipro.com wrote: > [...] > > We will use Tortoise SVN (Subversion) as version control system or SCM > > > tool for our project. We are facing an issue for which we would like > > to get a solution. > > > > We are linking SVN to Powerbuilder 11.5. We are trying to checkout > > files at object level. Every .pbl file, have many files inside. But > > SVN is not able to checkout those individual files which are inside > the pbl file. > > So is there a way by which SVN can checkout those files which are > > inside pbl. > > > > TortoiseSVN 1.6.7, 2010/01/22 > > Subversion 1.6.9 > [...] > > Sourav, > > you need to play by PowerBuilder's rules, I'm afraid. Trying to use > TortoiseSVN or any other "plain" Subversion client for checkin/checkout > will cause you grief. > > You can still use TortoiseSVN for other tasks, like browsing logs, > tagging and branching. > > The IDE supports the SCC API, and you need to use a plug-in for the IDE > that can drive Subversion via SCC. This will magically do the right > thing with objects in PBLs. Note that SCC encourages a serialized > workflow with reservation ("locking") of objects. > > We evaluated PushOK's product a couple of years ago; at the time, it > proved a good fit for our customer's needs. > > http://stackoverflow.com/questions/1162141/is-there-a-viable-scc-integra > tion-for-subversion > > (Please upgrade to Subversion 1.6.15. Subversion 1.6.9 sports a number > of bugs that have been fixed since its release.) > > - -- > Michael Diers, elego Software Solutions GmbH, http://www.elego.de > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (Cygwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk0ts0EACgkQcEKlWnqVgz0QngCfcTZ5gHe8upwsAH5x3zNZbFXB > 6vEAn27V2eskpxWfOfh5Hyu6747LFZlg > =jf++ > -----END PGP SIGNATURE----- > > Please do not print this email unless it is absolutely necessary. > > The information contained in this electronic message and any attachments to > this message are intended for the exclusive use of the addressee(s) and may > contain proprietary, confidential or privileged information. If you are not > the intended recipient, you should not disseminate, distribute or copy this > e-mail. Please notify the sender immediately and destroy all copies of this > message and any attachments. > > WARNING: Computer viruses can be transmitted via email. The recipient > should check this email and any attachments for the presence of viruses. The > company accepts no liability for any damage caused by any virus transmitted > by this email. > > www.wipro.com > --0016363b8fbcb3e2810499b56b58 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Jan 13, 2011 at 5:24 PM, <amit.sasmal@wipro.com&= gt; wrote:
Hello Micheal,

Thanks for your mail.

We are using Tortoise SVN-1.6.7 alongwith Power Builder 11.5.

We want to lock (check-out) the core power builder object from SVN so
that only one user can modify the object for that time. For this case,
If we want to open the workspace from the repository (SVN) we are
getting the attached message.

Please let us know the correct process for the Power Builder connectivty with the proper Tortoise SVN SCC version to lock the core PB object.

Appreciate your quick help.

Regards,

I'm guessing that .PBW file relies on= the rest of the files in that directory. You'll need to checkout that = directory prior to opening.

Cheers,
Daniel B.
=A0
Amit Sasmal.
Wipro Technologies.


-----Original Message-----
From: Michael Diers [mailto:mdiers@elego= .de]
Sent: Wednesday, January 12, 2011 7:27 PM
To: SOURAV ROY (WT01 - Manufacturing)
Cc: users@subversion.apache.= org; Sudip Datta (WT01 - Manufacturing);
Pabitra Mallick (WT01 - Manufacturing); Avik Nandi (WT01 -
Manufacturing); Amit Sasmal (WT01 - Manufacturing)
Subject: Re: SVN Subversion- object level checkout<= br>
-----BEGIN PGP SIGNED MESSAGE-----<= br> Hash: SHA1

On 2011-01-12 09:57, sourav.sroy@w= ipro.com wrote:
[...]
> We will use Tortoise SVN (Subversion) as version control system or SCM=

> tool for our project. We are facing an issue for which we would like > to get a solution.
>
> We are linking SVN to Powerbuilder 11.5. We are trying to checkout
> files at object level. Every .pbl file, have many files inside. But > SVN is not able to checkout those individual files which are inside the pbl file.
> So is there a way by which SVN can checkout those files which are
> inside pbl.
>
> TortoiseSVN 1.6.7, =A02010/01/22
> Subversion 1.6.9
[...]

Sourav,

you need to play by PowerBuilder's rules, I'm afraid. Trying to use=
TortoiseSVN or any other "plain" Subversion client for checkin/ch= eckout
will cause you grief.

You can still use TortoiseSVN for other tasks, like browsing logs,
tagging and branching.

The IDE supports the SCC API, and you need to use a plug-in for the IDE
that can drive Subversion via SCC. This will magically do the right
thing with objects in PBLs. Note that SCC encourages a serialized
workflow with reservation ("locking") of objects.

We evaluated PushOK's product a couple of years ago; at the time, it proved a good fit for our customer's needs.

http://stackoverflow.com/= questions/1162141/is-there-a-viable-scc-integra
tion-for-subversion

(Please upgrade to Subversion 1.6.15. Subversion 1.6.9 sports a number
of bugs that have been fixed since its release.)

- --
Michael Diers, elego Software Solutions GmbH, http://www.elego.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0ts0EACgkQcEKlWnqVgz0QngCfcTZ5gHe8upwsAH5x3zNZbFXB
6vEAn27V2eskpxWfOfh5Hyu6747LFZlg
=3Djf++
-----END PGP SIGNATURE-----

Please do not print this emai= l unless it is absolutely necessary.

The information contained in this electronic message and any attachments to= this message are intended for the exclusive use of the addressee(s) and ma= y contain proprietary, confidential or privileged information. If you are n= ot the intended recipient, you should not disseminate, distribute or copy t= his e-mail. Please notify the sender immediately and destroy all copies of = this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient shoul= d check this email and any attachments for the presence of viruses. The com= pany accepts no liability for any damage caused by any virus transmitted by= this email.

www.wipro.com

--0016363b8fbcb3e2810499b56b58--