# The form data below was edited by karl_wirth
# 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:	job000751

Status:	open

Project:	perforce-software-p4convert

Severity:	A

ReportedBy:	karl_wirth

ReportedDate:	2021/01/19 01:52:31

ModifiedBy:	karl_wirth

ModifiedDate:	2021/01/19 01:52:31

OwnedBy:	karl_wirth

Description:
	SVN: Not handling specific delete and branch over in same revision
	
	Customers SVN dump causes errors and converter does not create the revisions. For example:
	
	117.0 A:F - trunk/US/test.txt (UTF-8)
	mapping: r117 => @5
	
	118.0 R:F - trunk/APAC/test.txt (UNKNOWN)
	CASE-SENSITIVITY ISSUE:
	    From node is missing from dataset; skipping!
	    Please check case options and platform types.
	      com.p4convert.p4.caseMode = NONE
	      com.p4convert.p4.lowerCase = false
	
	I can reproduce this with customers SVN dump on backdoor and front door methods. It's a delete and copy file over top (revision 118 in their dump file):
	
	  Revision-number: 118
	  Prop-content-length: 133
	  Content-length: 133
	  K 10
	  svn:author
	  V 5
	  admin
	  K 8
	  svn:date
	  V 27
	  2021-01-15T01:13:31.790068Z
	  K 7
	  svn:log
	  V 33
	  cp US/test.txt over APAC/test.txt
	  PROPS-END
	
	  Node-path: trunk/APAC/test.txt
	  Node-kind: file
	  Node-action: delete
	
	  Node-path: trunk/APAC/test.txt
	  Node-kind: file
	  Node-action: add
	  Node-copyfrom-rev: 117
	  Node-copyfrom-path: trunk/US/test.txt
	  Text-copy-source-md5: 9584b1f15ac103ba6abea161944577a2
	  Text-copy-source-sha1: de349faaf6b8aed497a3c751dcc6cf7baf440cd1
	
	This revision was generated by:
	
	  svn rm  trunk/APAC/test.txt 
	  svn copy  trunk/US/test.txt trunk/APAC/test.txt 
	  svn commit
	
	I have tried simple and more complicated reproductions of my own and I end up with what looks like the same revision history but it works in my case. For example:
	
	  Node-path: release/test.txt
	  Node-action: delete
	
	  Node-path: release/test.txt
	  Node-kind: file
	  Node-action: add
	  Node-copyfrom-rev: 5
	  Node-copyfrom-path: main/test.txt
	  Text-copy-source-md5: 9b70a99fe8660947dcbc5db7890038ab
	  Text-copy-source-sha1: 4d9d27ce60952fc3906a6b1319461b71b8892819
	
	Ref: 00720106 - For SVN dump.

DevNotes:

Type:	Bug