# The form data below was edited by perforce # 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: job000593 Status: open Project: perforce-software-p4convert Severity: B ReportedBy: norman_morse ReportedDate: 2016/09/19 10:16:25 ModifiedBy: perforce ModifiedDate: 2019/02/19 10:51:35 OwnedBy: norman_morse Description: Renaming a directory or a file (in case only) will fail to remove the old file or old directory contents. From case 00251808 During a case sensitive conversion on Linux Configuration: com.p4convert.p4.caseMode=FIRST com.p4convert.p4.lowerCase=true Renaming the .../FileQueuer directory to .../fileQueuer works, but a copy of .../FileQueuer remains. ---- SVN entry ------ Node-path: trunk/batch/java/src/com/idx/ec/web/struts/actions/queue/fileQueuer Node-kind: dir Node-action: add Node-copyfrom-rev: 40642 Node-copyfrom-path: trunk/batch/java/src/com/idx/ec/web/struts/actions/queue/FileQueuer Node-path: trunk/batch/java/src/com/idx/ec/web/struts/actions/queue/FileQueuer Node-action: delete ----conversion log------ 19 Jul 2016 18:14:36,746 INFO com.perforce.common.process.ProcessNode ... 40643.0 B:D - trunk/batch/java/src/com/idx/ec/web/struts/actions/queue/fileQueuer 19 Jul 2016 18:14:36,757 INFO com.perforce.svn.process.SvnProcessNode ... detected CASE rename operation 19 Jul 2016 18:14:36,757 INFO com.perforce.common.process.ProcessNode ... 40643.1 R:D - trunk/batch/java/src/com/idx/ec/web/struts/actions/queue/FileQueuer 19 Jul 2016 18:14:38,060 INFO com.perforce.common.process.ProcessChange ... mapping: r40643 => @137707 DevNotes: Type: Bug