About
A Java-based CVS & SVN converter.
- 11
Members - 18
Followers - 2
Branches
Owners
Moderators
Members
Followers
| 3 years agoAdam Morriss committed change 28433 into main Typo corrected | ||
Add a comment | ||
| 3 years agoAdam Morriss committed change 28432 into main Minor tweaks to the language, corrected spelling errors | ||
| 3 years agoAdam Morriss committed change 28431 into main Updating the project readme; supported status is not correct. | ||
| 4 years agoKarl Wirth created job000751 for perforce-software-p4convert: 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. « | ||
| 4 years agoPaul Allen committed change 26953 into main Move //guest/perforce_software/p4convert to //guest/perforce_software/p4convert/main | ||
| 5 years agoJen Bottom created job000750 for perforce-software-p4convert: Provide the option to ignore the case of file extensions in the P4Convert typemap. The customer has many files in an SVN repo who's extensions only di...ffer by case. They would like the files to be treated the same, regardless of extension case, and not have to specify every variation in the typemap. Currently the typemap seems to take the case of an extension in to account. This can mean that some files who's extension only differs by case, are stored with a type the user does not want or intend. « | ||
| 5 years agoJen Bottom created job000749 for perforce-software-p4convert: P4Convert sometimes throws warnings about case issues, then fails with the following errors: CASE-SENSITIVITY ISSUE: From node is missing from data...set; skipping! Please check case options and platform types. com.p4convert.p4.caseMode = NONE com.p4convert.p4.lowerCase = false Caught exception on exit java.nio.file.FileAlreadyExistsException: /logs/tmp/<Directory> perforce_migration/<Dir>/p4_root/ws/svn/<Dir>/trunk/<Dir>/<Dir>/alpha/<Dir>/ <File>.cfg at java.base/sun.nio.fs.UnixCopyFile.copy(Unknown Source) at java.base/sun.nio.fs.UnixFileSystemProvider.copy(Unknown Source) at java.base/java.nio.file.Files.copy(Unknown Source) at com.perforce.svn.change.RevisionImport.duplicatePath(RevisionImport.java:172) at com.perforce.svn.change.RevisionImport.branchPath(RevisionImport.java:128) at com.perforce.svn.change.ChangeImport.addPath(ChangeImport.java:265) at com.perforce.common.node.NodeImport.dirAction(NodeImport.java:63) at com.perforce.common.node.NodeImport.action(NodeImport.java:49) at com.perforce.svn.process.SvnProcessNode.processDir(SvnProcessNode.java:465) at com.perforce.common.process.ProcessNode.process(ProcessNode.java:56) at com.perforce.svn.process.SvnProcessChange.processChange(SvnProcessChange.java: 170) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:59) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:21) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caught EXIT shutting down ... The customer suspects a race condition. They say: The case handling warning seems to be just that; a warning. The actual conversion error is thrown regardless of if the warning is present or not. If you look at the full log file I attached, the warning isn't present, but the same warning and stack trace is. I believe there's a race condition present in the converter. If re-run the conversion a couple times, it gets past this error. Unfortunately we can not obtain their data to try to reproduce the issue. I am logging this job to record the problem. « | ||
| 6 years agoNorman Morse created job000744 for perforce-software-p4convert: | ||
| 6 years agoNorman Morse modified job000743 for perforce-software-p4convert: 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 l...ocation. 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... « | ||
| 6 years agoNorman Morse modified job000743 for perforce-software-p4convert: 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 l...ocation. 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 « | ||
| 6 years agoNorman Morse created job000743 for perforce-software-p4convert: An SVN file which branches a deleted revision will fail. Apparently SVN will "copy" the latest, undeleted version of a file to the new location, an...d 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 cases/00369890 « | ||
| 6 years agoPerforce maintenance modified job000741 for perforce-software-p4convert: Labels with spaces cause a crash in the converter. From case 00369890, dump files are on warp:/warp/cases/00369890 Conversion has no problem...s until we enable the "exclude.map", which throws this exception: 03 Dez 2018 11:31:25,356 ERROR com.perforce.common.process.ProcessChange ... Caught exception on exit java.lang.ArrayIndexOutOfBoundsException: 2 at com.perforce.p4java.impl.generic.core.MapEntry.parseViewMappingString(MapEntry.java:279) at com.perforce.p4java.impl.generic.core.MapEntry.<init>(MapEntry.java:74) at com.perforce.p4java.impl.generic.core.Label$LabelMapping.<init>(Label.java:117) at com.perforce.common.label.LabelImport.buildViewMap(LabelImport.java:183) at com.perforce.common.label.LabelImport.submit(LabelImport.java:170) at com.perforce.common.process.ProcessLabel.submit(ProcessLabel.java:143) at com.perforce.common.process.ProcessChange.submit(ProcessChange.java:195) at com.perforce.svn.process.SvnProcessChange.processChange(SvnProcessChange.java:187) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:59) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:21) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 03 Dez 2018 11:31:25,366 INFO com.perforce.common.process.ProcessChange ... Caught EXIT shutting down ... cat exclude.map # exclude Subversion tags: ^tags/.* I am able to reproduce this, in the debugger the crash happens in com.perforce.p4java.impl.generic.core.MapEntry.parseViewMappingString(MapEntry.java:279) which seems to get confused by spaces in the client entry. « | ||
| 6 years agoPerforce maintenance modified job000739 for perforce-software-p4convert: | ||
| 6 years agoPerforce maintenance modified job000738 for perforce-software-p4convert: | ||
| 6 years agoPerforce maintenance modified job000735 for perforce-software-p4convert: | ||
| 6 years agoPerforce maintenance modified job000721 for perforce-software-p4convert: | ||
| 6 years agoPerforce maintenance modified job000716 for perforce-software-p4convert: Update documentation to include more accurate dump filter When dumping an SVN repo the dump sometimes incorrectly marks a merge of multiple revisions... to a target branch as only a merge of the first revision to target. When converted this causes inaccurate contents on the target branch. To avoid this take the SVN dump in this specific way: svnadmin dump /path/to/repo | svndumpfilter include /path--drop-empty-revs --renumber-revs > my.dmp « | ||
| 6 years agoPerforce maintenance modified job000599 for perforce-software-p4convert: Branching a file to the same path with a different case can cause the branch to fail and the source file to be deleted. From case 00251808 Durin...g a case sensitive conversion on Linux Configuration: com.p4convert.p4.caseMode=FIRST com.p4convert.p4.lowerCase=true SVN ------------------- Node-path: trunk/cedi/cedi-jbehave/jbehave-integration-tests/src/test/resources/us19_egate_e2e_volume_test.story Node-kind: file Node-action: add Node-copyfrom-rev: 54573 Node-copyfrom-path: trunk/cedi/cedi-jbehave/jbehave-integration-tests/src/test/resources/Us19_egate_e2e_volume_test.story LOG ------------------- 21 Jul 2016 08:33:01,867 INFO com.perforce.common.process.ProcessNode ... 54575.2 B:F - trunk/cedi/cedi-jbehave/jbehave-integration-tests/src/test/resources/us19_egate_e2e_volume_test.story (UTF-8) 21 Jul 2016 08:33:01,904 WARN com.perforce.common.client.P4Factory ... p4java: //idxedi_s2_t4/trunk/cedi/cedi-jbehave/jbehave-integration-tests/src/test/resources/us19_egate_e2e_volume_test.story - file(s) not on client. 21 Jul 2016 08:33:01,922 WARN com.perforce.common.client.P4Factory ... p4java: //idxedi_s2_t4/trunk/cedi/cedi-jbehave/jbehave-integration-tests/src/test/resources/us19_egate_e2e_volume_test.story - file(s) not opened on this client. The result is the new file does not get created, and the original file gets deleted. « | ||
| 6 years agoPerforce maintenance modified job000593 for perforce-software-p4convert: 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 sensi...tive 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 « | ||
| 6 years agoPerforce maintenance modified job000505 for perforce-software-p4convert: CVS import mode conversions do not properly escape some special characters in filepaths. In particular '%' java.lang.Exception: Cannot creat...e diretory: /home/realsupport/PUBLIC.Main.11901/p4_root/rti/main/RTI/RTI/devroot/rti-projects/SimConvert/examples/abrams.cdb/rotational_bumpstops.tbl/msc_0001.rbu25,d This is the file in CVS: /cvsroot/RTI/RTI/devroot/rti-projects/SimConvert/examples/abrams.cdb/rotational_bumpstops.tbl/Attic /msc_0001.rbu%25,d Example from case 00234251 « | ||
| 6 years agoPerforce maintenance modified job000343 for perforce-software-p4convert: Converter Warnings on files with lock attributes in import mode: "can't change +l type with reopen; use revert -k and then edit -t to change type." ... The file was converted in import mode and has these attributes: ... #1 change 730252 add on 2003/11/24 by xyzzy@plugh_stg (binary+Fl) I don't see any lost data, this may only be cosmetic, or not... customer case 00190893 This is related to a limitation in the release notes: SVN property svn:needs-lock cannot be imported to a distributed Perforce server and may raise the error: can't change +l type with reopen; use revert -k and then edit -t to change type. https://swarm.workshop.perforce.com/projects/perforce-software-p4convert/ « | ||
| 6 years agoPerforce maintenance modified job000337 for perforce-software-p4convert: Some Symbolic Links are not created in Perforce during an import mode SVN conversion. Convert mode seems to work. This Problem has not been reprodu...ced internally: Case 00176418 The Links were created in the initial SVN revision along with about 6000 other files. No errors are reported from the conversion and the filesnames are added to the auditlog.txt file, but the links are missing from Perforce depot. Target of the links are known to exist, and were created in the same submit as the links. Is there a race condition? Could it be Linux specific? I've asked customer for a Shrunken Dump, and I fixed some of the link entries, and I still was unable to reproduce this problem on my mac. « | ||
| 6 years agoPerforce maintenance modified job000334 for perforce-software-p4convert: Warnings generated for "CASE-SENSITIVITY ISSUE" are deceptive and should be more informative. Frequently a warning like this: 23:09:28,...729 pool-1-thread-1 WARN com.perforce.svn.process.SvnProcessNode ... 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 Actually has to do with a node missing from the dataset, not just a Case Sensitivity issue. This error can also happen with filtered and/or corrupt subversion repositories. It would be much better to report the missing path and version. That way the user can diagnose the issue without requesting Subversion mini-dumps etc... I would like an error report like this: 23:09:28,729 pool-1-thread-1 WARN com.perforce.svn.process.SvnProcessNode ... From Node Missing From Dataset; Skipping! ... From Path: /path/to/file ... From Version: #### This could be a CASE-SENSITIVITY issue: Please check case options and platform types. com.p4convert.p4.caseMode = NONE com.p4convert.p4.lowerCase = false « | ||
| 6 years agoPerforce maintenance modified job000328 for perforce-software-p4convert: Simplify target depot path configuration. It is easy to mess up the configuration of where converted files will go during a conversion. You need t...o set TWO configuration options: com.p4convert.core.depotPath= depot_name com.p4convert.core.subPath=dir/dir/subdir These options should be combined into one target depot path parameter com.p4convert.core.targetDepotPath=//depot_name/dir/dir/subdir It is easy enough for the converter to strip the "//" and separate the depot name from the subpath, and generate the correct internal configuration. I have seen several users get very confused with the current configuration, we should change this to reduce support calls and make their life easier. « | ||
| 6 years agoPerforce maintenance modified job000299 for perforce-software-p4convert: | ||
| 6 years agoPerforce maintenance modified job000294 for perforce-software-p4convert: P4Convert: Initially uses environment user (SVN) Initially P4Convert picks up the P4USER from the environment and runs commands against the Perforce... server before switching to the user in the config file: (P4USER=FRED) Perforce server info: 2015/06/03 11:33:35 pid 18054 FRED@noclient 127.0.0.1 [p4convert/PUBLIC.Main.12912] 'user-info' Perforce server info: 2015/06/03 11:33:35 pid 18054 FRED@noclient 127.0.0.1 [p4convert/PUBLIC.Main.12912] 'user-users' Perforce server info: 2015/06/03 11:33:35 pid 18054 FRED@noclient 127.0.0.1 [p4convert/PUBLIC.Main.12912] 'user-user -f -i' Perforce server info: 2015/06/03 11:33:35 pid 18054 p4-user@noclient 127.0.0.1 [p4convert/PUBLIC.Main.12912] 'user-depots' Perforce server info: 2015/06/03 11:33:35 pid 18054 p4-user@noclient 127.0.0.1 [p4convert/PUBLIC.Main.12912] 'user-depot -i' This causes the following error when protections stop the user from being created: Caught exception on exit com.perforce.p4java.exception.AccessException: Access for user 'FRED' has not been enabled by 'p4 protect'. « | ||
| 6 years agoPerforce maintenance modified job000292 for perforce-software-p4convert: Directions for enabling debugging in the converter are obsolete. https://swarm.workshop.perforce.com/projects/perforce-software-p4convert/view/main/d...ocs/publicsite-generated/chapter.notes.html All these directions refer to debug.log4j.xml while what is provided is debug.log4j.properties. The directions need to support the available files. « | ||
| 6 years agoPerforce maintenance modified job000291 for perforce-software-p4convert: P4Convert needs to be able to scan all paths in a dump to see if they are legitimate or not and then report all illegal path errors in one pass. ...; It should look for illegal characters, and illegal character sequences (like ...). The current behavior of crashing and then forcing a restart of the conversion for every illegal path is too time consuming and annoying for customers with large legacy dumps they wish to import into perforce. « | ||
| 6 years agoPerforce maintenance modified job000290 for perforce-software-p4convert: Convert mode will store Perforce paths with illegal characters. Later attempts to integrate these files to a different location in Perforce re...turn an error similar to: "Non-printable characters not allowed in '//importisedepot/branches/ise_12_fcs_patch15_br/cpm/jars/devicedeploy/^?^?'. It also appears to be impossible (or extremely difficult) to delete, rename or obliterate these files since they have unprintable characters. In Import mode, these same files return the "Non-printable characters" error during conversion, so the resulting Perforce depot never gets the bad paths. Associated with case 00153828 « | ||
| 6 years agoPerforce maintenance modified job000238 for perforce-software-p4convert: It appears the CVS conversion isn't treating the 'Attic' directory properly. I have seen a few instances where the attic versions are showing up in br...anches with labels as if they were regular files. What is the intended handling of the 'Attic' versions of the files? Should I clean out the attic before running the conversion? « | ||
| 6 years agoPerforce maintenance modified job000236 for perforce-software-p4convert: | ||
| 6 years agoPerforce maintenance modified job000225 for perforce-software-p4convert: Labels are not getting created in Perforce. I created a small sample Subversion repository with only one file under trunk. I then branched that file t...o a folder in the tags directory. I created the exclude.map with ^tags/.* and set the config variables accordingly. The conversion run indicates: ... exclude.map: ^tags/.* ... Searching for labels... ... Branch map count: ... A:1 test_svp2p4labeltest which seems to indicate it sees the tag. The tags directory itself is not imported (as expected) but then no label is created in Perforce. « | ||
| 6 years agoPerforce maintenance modified job000223 for perforce-software-p4convert: | ||
| 6 years agoPerforce maintenance modified job000217 for perforce-software-p4convert: Perforce labels spanning branches I'm using Convert mode and converting labels and branches. As it stands, the labels are applied to various branch v...ersions. For example: $ p4 -p 1666 files @IPX_C19 //depot/icm/proj/USB30phy/BCG_28NM/rtl/rtl/files.f#5 - integrate change 247907 (ltext) //depot/icm/proj/USB30phy/BCG_28NM/rtl/rtl/usb30_core2dfe.sv#7 - integrate change 247935 (text+Fx) //depot/icm/proj/USB30phy/BCG_28NM/rtl/rtl/usb30_dfe.sv#8 - integrate change 247982 (text+Fx) ... //depot/icm/proj/USB30phy/BCM63381_A0/rtl/rtl/usb30_phy.sv#8 - integrate change 247971 (text+Fx) //depot/icm/proj/USB30phy/BCM63381_A0/rtl/rtl/usb30_rxpmd_clk_gen.sv#2 - integrate change 247858 (ltext) //depot/icm/proj/USB30phy/BCM63381_A0/rtl/rtl/usb30_txpmd_clk_gen.sv#2 - integrate change 247859 (ltext) ... //depot/icm/proj/USB30phy/main/rtl/rtl/usb30_mdio_creg.sv#1 - import change 247738 (ltext) //depot/icm/proj/USB30phy/main/rtl/rtl/usb30_mdio_csreg_5.v#2 - integrate change 247439 (text+Fx) //depot/icm/proj/USB30phy/main/rtl/rtl/usb30_mdio_csreg_8.v#2 - integrate change 247439 (text+Fx) All these files reside in the same directory in the tree - only differing because of the branch directory. Since these labels are applied on different branches, I cannot 'sync' to a label and pick up the entire fileset in one place. In CVS I would be able to run 'cvs get -r <label> <module>' and end up with all files tagged with that particular label - no matter the branch. During conversion, would it make more sense to apply the label to all the files on a particular branch so they're all visible? « | ||
| 6 years agoPerforce maintenance modified job000218 for perforce-software-p4convert: Subversion tags with spaces in name result in crash when label conversion is on: com.perforce.p4java.exception.RequestException: Error in label specif...ication. Error detected at line 1. Wrong number of words for field 'Label'. at com.perforce.p4java.impl.mapbased.server.Server.handleErrorStr(Server.java:4909) at com.perforce.p4java.impl.mapbased.server.Server.createLabel(Server.java:1101) at com.perforce.common.label.LabelImport.<init>(LabelImport.java:72) at com.perforce.common.process.ProcessFactory.getLabel(ProcessFactory.java:88) at com.perforce.common.process.ProcessLabel.labelChange(ProcessLabel.java:52) at com.perforce.svn.process.SvnProcessNode.processDir(SvnProcessNode.java:455) at com.perforce.common.process.ProcessNode.process(ProcessNode.java:50) at com.perforce.svn.process.SvnProcessChange.processChange(SvnProcessChange.java:179) at com.perforce.common.process.ProcessChange.runSingle(ProcessChange.java:90) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:53) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:20) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) « | ||
| 6 years agoPerforce maintenance modified job000214 for perforce-software-p4convert: Symlink issue when mergeInfoEnabled Configuration: com.p4convert.svn.mergeInfoEnabled=true Error: p4java: can't create directory... for /hhh/xxx/src/sss.c p4java: //depot/xxx/src/sss.c - file(s) not on client. java.lang.Exception: Cannot create directory: /hhh/xxx/src at com.perforce.common.ConverterException.<init>(ConverterException.java:12) at com.perforce.common.asset.AssetWriter.open(AssetWriter.java:111) at com.perforce.common.asset.AssetWriter.writeClientFile(AssetWriter.java:174) at com.perforce.common.asset.AssetWriter.write(AssetWriter.java:124) at com.perforce.svn.change.RevisionImport.writeClientFile(RevisionImport.java:1022) at com.perforce.svn.change.RevisionImport.dirtyEdit(RevisionImport.java:787) at com.perforce.svn.change.RevisionImport.integFile(RevisionImport.java:956) at com.perforce.svn.change.ChangeImport.addRevision(ChangeImport.java:394) at com.perforce.common.node.NodeImport.fileAction(NodeImport.java:70) at com.perforce.common.node.NodeImport.action(NodeImport.java:47) at com.perforce.svn.process.SvnProcessNode.processFile(SvnProcessNode.java:317) at com.perforce.common.process.ProcessNode.process(ProcessNode.java:46) at com.perforce.svn.process.SvnProcessChange.processChange(SvnProcessChange.java:179) at com.perforce.common.process.ProcessChange.runSingle(ProcessChange.java:90) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:53) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:20) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caught exception on exit com.perforce.common.ConverterException at com.perforce.common.asset.AssetWriter.open(AssetWriter.java:111) at com.perforce.common.asset.AssetWriter.writeClientFile(AssetWriter.java:174) at com.perforce.common.asset.AssetWriter.write(AssetWriter.java:124) at com.perforce.svn.change.RevisionImport.writeClientFile(RevisionImport.java:1022) at com.perforce.svn.change.RevisionImport.dirtyEdit(RevisionImport.java:787) at com.perforce.svn.change.RevisionImport.integFile(RevisionImport.java:956) at com.perforce.svn.change.ChangeImport.addRevision(ChangeImport.java:394) at com.perforce.common.node.NodeImport.fileAction(NodeImport.java:70) at com.perforce.common.node.NodeImport.action(NodeImport.java:47) at com.perforce.svn.process.SvnProcessNode.processFile(SvnProcessNode.java:317) at com.perforce.common.process.ProcessNode.process(ProcessNode.java:46) at com.perforce.svn.process.SvnProcessChange.processChange(SvnProcessChange.java:179) at com.perforce.common.process.ProcessChange.runSingle(ProcessChange.java:90) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:53) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:20) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caught EXIT shutting down ... « | ||
| 6 years agoPerforce maintenance modified job000209 for perforce-software-p4convert: Unable to process file: /projects/engcm_icm_scratch/CVS_CONVERSION/usb30phy/cvsrepo/rtl/usb30_phy_mdio.sv,v java.lang.reflect.InvocationTargetExcepti...on at sun.reflect.GeneratedConstructorAccessor3.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at com.perforce.cvs.parser.rcstypes.RcsObject.add(RcsObject.java:36) at com.perforce.cvs.parser.RcsReader.parsePhrase(RcsReader.java:250) at com.perforce.cvs.parser.RcsReader.parseRcsDeltas(RcsReader.java:193) at com.perforce.cvs.parser.RcsReader.<init>(RcsReader.java:87) at com.perforce.cvs.process.CvsProcessChange.buildBranchList(CvsProcessChange.java:199) at com.perforce.cvs.process.CvsProcessChange.processChange(CvsProcessChange.java:67) at com.perforce.common.process.ProcessChange.runSingle(ProcessChange.java:90) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:53) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:20) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:504) at java.lang.Integer.parseInt(Integer.java:527) at com.perforce.cvs.parser.rcstypes.RcsObjectNum.<init>(RcsObjectNum.java:17) at com.perforce.cvs.parser.rcstypes.RcsObjectNumList.<init>(RcsObjectNumList.java:12) ... 17 more « | ||
| 6 years agoPerforce maintenance modified job000203 for perforce-software-p4convert: | ||
| 6 years agoPerforce maintenance modified job000193 for perforce-software-p4convert: p4convert documentation needs to provide a "scary message index" with a description of what each of these messages mean, how it effects the quality of... the conversion. And what needs to be done because of it... Many, Many users contact support with these questions. Here's my current list of scary messages: "... :Unmappable char set, storing file as-is" "... SKIPPING: cannot delete a non-existant revision." "... ... Non-unicode server, downgrading file to text" "... Unknown Charset, using binary" "... CASE-SENSITIVITY ISSUE:" « | ||
| 6 years agoPerforce maintenance modified job000192 for perforce-software-p4convert: The problem reported in job000145 still exists. I can provide a CVS repository which exhibits this behavior. This seems to stem from not handling t...he 'dead' state. The CVS history shows: ---------------------------- revision 1.12.2.1 date: 2013/04/05 20:00:34; author: shg; state: dead; lines: +0 -110 file files.f was added on branch TSMC40LP on 2013-04-07 16:48:05 +0000 ---------------------------- A quick Google search gives an explanation: http://osdir.com/ml/version-control.cvs.general/2003-01/msg00060.html Based on this, the version should simply be ignored - not included in the new Perforce history of the element. « | ||
| 6 years agoPerforce maintenance modified job000168 for perforce-software-p4convert: CVS: An option to add a label description copied from the first change associated with the label. This is instead of the change made in 11760 which... hard-wired "Created by p4convert". Customer feels that since the "multi-line" change comment bug was fixed, that using the description from the first change would be more helpful than our own "Created by p4convert". In case 00089390 « | ||
| 6 years agoPerforce maintenance modified job000166 for perforce-software-p4convert: CVS in IMPORT mode reports Warning: p4java: //import/main/foo - file(s) not in label. | ||
| 6 years agoPerforce maintenance modified job000142 for perforce-software-p4convert: Add support for Subversion Delta Dump format. If subversion can handle it, why can't we? Currently if you don't have access to the Subversion serv...er, you have to use rsvndump which is an older tool that can be difficult to build, especially on Windows. P4Convert should support the output from svnrdump which is the official remote dumping tool supplied with Subversion. « | ||
| 6 years agoPerforce maintenance modified job000132 for perforce-software-p4convert: Converter should allow the configuration of which "p4d" to use. Investigation: The converter never uses the "p4d" executable, so this job doesn'...t make sense... Closing Right now it is the one on the path, with the previous converter we could specify any absolute path to a different "p4d". From case 00107916 « | ||
| 6 years agoPerforce maintenance modified job000114 for perforce-software-p4convert: Errors while syncing p4convert files on windows - invalid filenames in Windows... A simple sync of //guest/perforce_software/p4convert Within Wind...ows P4V returns: 5 errors reported can't create directory for C:\Workshop\perforce_software\p4convert\test\com\perforce\cvs\integration\dumps\CVScluster01\null_path\ \file1.txt,v mkdir: C:\Workshop\perforce_software\p4convert\test\com\perforce\cvs\integration\dumps\CVScluster01\null_path\ : The system cannot find the file specified. can't create directory for C:\Workshop\perforce_software\p4convert\test\com\perforce\cvs\integration\import\base\null_path\import\main\ \file1.txt,d\1.2 mkdir: C:\Workshop\perforce_software\p4convert\test\com\perforce\cvs\integration\import\base\null_path\import\main\ : The system cannot find the file specified. can't create directory for C:\Workshop\perforce_software\p4convert\test\com\perforce\cvs\integration\integ\base\null_path\import\main\ \file1.txt,d\1.2 mkdir: C:\Workshop\perforce_software\p4convert\test\com\perforce\cvs\integration\integ\base\null_path\import\main\ : The system cannot find the file specified. can't create directory for C:\Workshop\perforce_software\p4convert\test\com\perforce\integration\dumps\null_file\import\trunk\{{=machine}}\foo: bar.txt,d\1.1 mkdir: C:\Workshop\perforce_software\p4convert\test\com\perforce\integration\dumps\null_file\import\trunk\{{=machine}}\foo: bar.txt,d: The filename, directory name, or volume label syntax is incorrect. can't create directory for C:\Workshop\perforce_software\p4convert\test\com\perforce\integration\import\base\null_file\import\trunk\{{=machine}}\foo: bar.txt,d\1.1 mkdir: C:\Workshop\perforce_software\p4convert\test\com\perforce\integration\import\base\null_file\import\trunk\{{=machine}}\foo: bar.txt,d: The filename, directory name, or volume label syntax is incorrect. « | ||
| 6 years agoPerforce maintenance modified job000084 for perforce-software-p4convert: For CVS conversion user-name mapping is not working, with two distinct problems: 1) the --users option is not recognised 2) if a user-name mapping fi...le (users.map) is manually created with valid entries ("original-name, new-name") it is detected during the conversion process (as seen in the trace output) but the mapping is not generated. « | ||
| 6 years agoPerforce maintenance modified job000079 for perforce-software-p4convert: CVS converter does not do any Keyword detecting. So +k files are not getting created, even if a keyword is in the content. This is a different (du...mber) behavior which the existing p4convert-cvs handles. This can be verified with the "filetypes" test CVS repository. I will email this repository to paul. « | ||
| 6 years agoNorman Morse created job000741 for perforce-software-p4convert: Labels with spaces cause a crash in the converter. From case 00369890, dump files are on warp:/warp/cases/00369890 Conversion has no proble...ms until we enable the "exclude.map", which throws this exception: 03 Dez 2018 11:31:25,356 ERROR com.perforce.common.process.ProcessChange ... Caught exception on exit java.lang.ArrayIndexOutOfBoundsException: 2 at com.perforce.p4java.impl.generic.core.MapEntry.parseViewMappingString(MapEntry.java:279) at com.perforce.p4java.impl.generic.core.MapEntry.<init>(MapEntry.java:74) at com.perforce.p4java.impl.generic.core.Label$LabelMapping.<init>(Label.java:117) at com.perforce.common.label.LabelImport.buildViewMap(LabelImport.java:183) at com.perforce.common.label.LabelImport.submit(LabelImport.java:170) at com.perforce.common.process.ProcessLabel.submit(ProcessLabel.java:143) at com.perforce.common.process.ProcessChange.submit(ProcessChange.java:195) at com.perforce.svn.process.SvnProcessChange.processChange(SvnProcessChange.java:187) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:59) at com.perforce.common.process.ProcessChange.call(ProcessChange.java:21) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 03 Dez 2018 11:31:25,366 INFO com.perforce.common.process.ProcessChange ... Caught EXIT shutting down ... cat exclude.map # exclude Subversion tags: ^tags/.* I am able to reproduce this, in the debugger the crash happens in com.perforce.p4java.impl.generic.core.MapEntry.parseViewMappingString(MapEntry.java:279) which seems to get confused by spaces in the client entry. « | ||
| 7 years agoNorman Morse modified job000738 for perforce-software-p4convert: | ||
| 7 years agoNorman Morse modified job000739 for perforce-software-p4convert: | ||