P4DTI issue job000377

TitleCan't use Perforce 2000.2 client with Perforce 2001.1 server
Statusclosed
Priorityessential
Assigned userGareth Rees
OrganizationRavenbrook
DescriptionIf you try to run the P4DTI using a Perforce 2000.2 client but a Perforce 2001.1 server, then the P4DTI stops with an error from Perforce.
The error message is:
Perforce error: (P4DTI-7087) Error detected at line 29.
Value for field 'Options' must be one of noallwrite/allwrite,noclobber/clobber,nocompress/compress,unlocked/locked,nomodtime/modtime,normdir/rmdir.
AnalysisThis is because "p4 -G client -o" fails in this client/server combination. We could in theory work around this bug by constructing our own client specification instead of getting Perforce to produce one for us, but that would have its own compatibility problems, because the set of options changes from release to release. So instead, we should:
1. Report to Perforce as a bug in the 2001.1 server (it should be backwards compatible with old clients).
2. Add the error message to the AG so that people encountering this problem can track it down.
This is Perforce job 6208.
How foundcustomer
Evidence<http://info.ravenbrook.com/mail/2001/07/31/11-49-55/0.txt>
<http://info.ravenbrook.com/mail/2001/07/31/12-07-30/0.txt>
<http://info.ravenbrook.com/mail/2001/07/31/12-31-04/0.txt>
Observed in1.1.4
Created byGareth Rees
Created on2001-07-31 12:31:54
Last modified byGareth Rees
Last modified on2001-12-10 19:53:48
History2001-07-31 GDR Created.

Fixes

Change Effect Date User Description
14590 closed 2001-07-31 12:48:54 Gareth Rees Added error message from incompatibility between Perforce client and server to section 11.3 of the AG.