| Title | refresh.py doesn't work with Perforce 2006.1 |
| Status | closed |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | The P4DTI refresh.py script fails when run against Perforce 2006.1 fails. When refreshing jobs from the defect tracker, it attempts to set all the fields of each job, including the 'Date' field. This field is an 'always' field, and Perforce 2006.1 changed the semantics of "p4 job -i" such that the read-only nature of 'always' fields is enforced unless the "-f" flag is used. The P4DTI does not use the "-f" flag, and so the refresh procedure fails. |
| Analysis | Why doesn't this happen in routine use of the P4DTI? Should we just turn on the "-f" flag? When updating an existing job, could look at differences? We can't delete jobs in refresh.py because that deletes associated fixes (see job000422). |
| How found | customer |
| Evidence | [1] <http://info.ravenbrook.com/mail/2006/07/10/21-46-10/0.txt> |
| Observed in | 2.3.4 |
| Introduced in | 2.3.4 |
| Created by | Nick Barnes |
| Created on | 2006-07-19 11:04:15 |
| Last modified by | Nick Barnes |
| Last modified on | 2006-07-23 14:50:37 |
| History | 2006-07-19 NB Created. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 159738 | closed | 2006-07-23 14:50:23 | Nick Barnes | Use -f flag on p4 job -i when running refresh.py script. job001468. |