[p4perl] Problem using P4->FetchClient() (CALL#2151058)

Scott Lavender Scott.Lavender at visiprise.com
Fri Sep 19 08:07:29 PDT 2008


Perforce - The Fast Software Configuration Management System.
Copyright 1995-2008 Perforce Software.  All rights reserved.
Rev. P4/NTX86/2007.3/143793 (2008/01/21).

The server is a higher patch level, but the same release:

Server version: P4D/LINUX26X86/2007.3/152469 (2008/04/24)
Server license: Visiprise Inc 154 users (support ends 2009/05/11) 

I have upgraded the server to use the 2007.3 supported P4Perl. Don't
know if you remember the dialog we had in getting my trigger scripts
reworked. I have not done the same for the build environment.

 

-----Original Message-----
From: Tony Smith [mailto:tony at smee.org] 
Sent: Friday, September 19, 2008 10:44 AM
To: Scott Lavender
Cc: p4perl at perforce.com; support at perforce.com
Subject: Re: [p4perl] Problem using P4->FetchClient() (CALL#2151058)

Scott,

Could you also send us the output of:

	p4 -V

I think this might be down to the way tickets are stored in the ticket
file in 
different versions of Perforce. Specifically, this change documented in
the 
release notes for 2007.2:

	#117342 * **
	    Different values of P4PORT for the same server instance
	    e.g. (ip:port# vs host:port#) would result in multiple
	    ticket entries in the Perforce ticket file. This has 
	    been fixed so that the same server instance will always
	    produce a single ticket entry that either P4PORT value can
	    use.  (Bug #16707, #18349).


My guess is that your P4Perl was built with an older version of the
Perforce 
API than 2007.2/117342, but that your P4 is later than that...

Tony




More information about the p4perl mailing list