Also note that if you are adding a file in your changeset, makechangepackage will complain, but all is well: the package is written out (including new files) and you can continue with the process.

jim

On May 15, 2006, at 1:40 PM, Henry Minsky wrote:

It looks at environment var P4CLIENT I think, make sure that's set to
the right client name you're using

For example in my lps-legals sandbox I have P4CLIENT set to domokun-legals, the client I used to check out that tree.

P4CLIENT=domokun-legals
P4CONFIG=.p4config
P4HOME=c:\Program Files\Perforce
P4PORT=localhost:1666
P4USER=hminsky

Hint, if you set P4CONFIG to ".p4config", then when you're in the tree you
can execute P4 commands and it searches upwards to find a file named .p4config.

In my .p4config for the legals tree I have

$ cat ../../../.p4config
P4CLIENT=domokun-legals
P4USER=hminsky



On 5/15/06, Philip Romanik <[EMAIL PROTECTED]> wrote:
Hi,

I'm not having any luck running makechangepackage. I'm running on Windows
without cygwin. When I run the script I get:

python makechangepackage 42262
File(s) not opened on this client.

I'm running this on the same machine as I am developing on. The only
difference is that I'm using p4win (the Window's client) to checkout the
files, and makechangepackage uses the command-line interface.

Thanks!

Phil

_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev



--
Henry Minsky
Software Architect
[EMAIL PROTECTED]

_______________________________________________
Laszlo-dev mailing list

_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev

Reply via email to