# The form data below was edited by norman_morse # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature]. Required. # # Release: Release in which job is intended to be fixed. Job: job000743 Status: closed Project: perforce-software-p4convert Severity: B ReportedBy: norman_morse ReportedDate: 2019/03/04 11:14:39 ModifiedBy: norman_morse ModifiedDate: 2019/03/06 14:27:05 OwnedBy: norman_morse Description: An SVN dump file entry which branches a deleted revision will fail. Apparently SVN will "copy" the latest, undeleted version of a file to the new location. Perforce does not undelete it at the head revision, the way svn does. This causes comparison problems between the files in the SVN repository and the Perforce depot. Conversion errors show: 22 Feb 2019 17:31:24,968 INFO com.perforce.common.process.ProcessNode ... 10691.2 B:F - branches/_experimental/2012 NOVIS Refactoring/NOVIS/Screencast/AbstractScreencast.cpp (UTF-8) 22 Feb 2019 17:31:24,968 WARN com.perforce.common.client.P4Factory ... p4java: //Scopis/trunk/NeuroNavigation/Application/IO/AbstractScreencast.cpp@10670 - all revision(s) already integrated. 22 Feb 2019 17:31:24,968 WARN com.perforce.common.client.P4Factory ... p4java: //Scopis/branches/_experimental/2012 NOVIS Refactoring/NOVIS/Screencast/AbstractScreencast.cpp - file(s) not on client 22 Feb 2019 17:31:24,968 WARN com.perforce.common.client.P4Factory ... p4java: //Scopis/branches/_experimental/2012 NOVIS Refactoring/NOVIS/Screencast/A Exploring this in the debugger shows that The SVN dump entry for 10691.2 is referencing a deleted revision of AbstractScreencast.cpp. Dump is on warp in warp/cases/00369890 030619 - norman_morse Duplicate of job000599 closing... DevNotes: Type: Bug