Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 322148

Summary: WTP Source Editing git mirror missing items
Product: Community Reporter: David Carver <d_a_carver>
Component: GitAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED FIXED QA Contact:
Severity: blocker    
Priority: P3 CC: thatnitind
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description David Carver CLA 2010-08-09 11:05:28 EDT
The WTP Source Editing git mirror of the CVS repository appears to be out of synch and missing several items.   For example, there is no R3_2_0 branch in the git repo, but there is a R3_2_maintenance branch.

There are also several files that seem to be missing from HEAD as well, for example, http://dev.eclipse.org/viewcvs/index.cgi/sourceediting/plugins/org.eclipse.wst.sse.ui/schema/characterPairing.exsd?root=WebTools_Project&view=log

Is missing from the git repo, but the plugin.xml in the git repo is refering to this file.

Can we get a re-creation of the WTP Source Editing git mirror to correct this as well as the following additional issue:

There is an origin/origin branch in the git repo, but HEAD should not be pointing to this branch, it should point to master and origin/origin should not be in the repo at all.

Marking this as a blocker as anybody that is cloning this repo is getting bad repos to try and work with.
Comment 1 Nitin Dahyabhai CLA 2010-08-10 08:58:32 EDT
R3_2_0 is actually a tag, and the entire tree wouldn't be tagged with it, just the plug-ins, tests, and features we ship.
Comment 2 David Carver CLA 2010-08-10 09:48:38 EDT
(In reply to comment #1)
> R3_2_0 is actually a tag, and the entire tree wouldn't be tagged with it, just
> the plug-ins, tests, and features we ship.

Regardless there are missing files.  For example, characterPair.exsd is missing from the mirror repo.  It seems that the mirror is not picking up new file additions, just changes to files that were there when the initial conversion was done.
Comment 3 Denis Roy CLA 2010-08-10 14:02:49 EDT
The sourceediting repo is being recreated now.  It is taking forever.
Comment 4 David Carver CLA 2010-08-10 14:18:07 EDT
(In reply to comment #3)
> The sourceediting repo is being recreated now.  It is taking forever.

Thanks, I'll test it when it is complete.
Comment 5 Denis Roy CLA 2010-08-11 09:28:51 EDT
Looks like the import is completed.  Feel free to try it out.
Comment 6 David Carver CLA 2010-08-11 10:45:56 EDT
Thanks I'll try it out now.
Comment 7 David Carver CLA 2010-08-11 11:53:49 EDT
I'm still seeing some odd things here.  The first is the following:


origin
  remotes/origin/Branch301
  remotes/origin/Cleanup0508
  remotes/origin/HEAD -> origin/origin
  remotes/origin/JSDT302
  remotes/origin/JSDT303
  remotes/origin/R0_7_maintenance
  remotes/origin/R1_0_maintenance
  remotes/origin/R1_5_5_patches
  remotes/origin/R1_5_branch
  remotes/origin/R1_5_maintenance
  remotes/origin/R1_5_maintenance_patches
  remotes/origin/R2_0_2_patches
  remotes/origin/R2_0_maintenance
  remotes/origin/R3_0_0_patches
  remotes/origin/R3_0_1_patches
  remotes/origin/R3_0_3_patches
  remotes/origin/R3_0_4_patches
  remotes/origin/R3_0_4_updates
  remotes/origin/R3_0_5_2_patches
  remotes/origin/R3_0_5_patches
  remotes/origin/R3_0_maintenance
  remotes/origin/R3_1_2_patches
  remotes/origin/R3_1_maintenance
  remotes/origin/R3_2_1_patches
  remotes/origin/R3_2_maintenance
  remotes/origin/Refactor0428
  remotes/origin/T_Early302
  remotes/origin/david_williams_tempBranch
  remotes/origin/david_williams_tempTest29
  remotes/origin/david_williams_tempTests
  remotes/origin/david_williams_tempTests2
  remotes/origin/jsdtDev11082007
  remotes/origin/master
  remotes/origin/nitind_31m6_inferrence
  remotes/origin/origin
  remotes/origin/tempBug155790


In particular the branches that begin as:

origin/origin

There should be no branch called origin.   I would expect only to have remote/origin/master

I'm not sure how the git - cvs conversion is working but it appears to be creating a origin branch, and not adding it's synchronization stuff to the master branch.  Do all synchronizations happen on the origin branch?  If so this will cause issues with standard tooling like GitHub that expect the master branch to be the primary branch to pull synchronizations from.  It also can confuse end users that clone the repos and don't get something they would normally expect to see.
Comment 8 Denis Roy CLA 2010-11-22 13:50:58 EST
(In reply to comment #7)
> I'm still seeing some odd things here.  The first is the following:
> 
> 
> origin

Dave, you you want me to delete the mirror and restart using -o master ?
Comment 9 David Carver CLA 2010-11-22 14:20:54 EST
(In reply to comment #8)
> (In reply to comment #7)
> > I'm still seeing some odd things here.  The first is the following:
> > 
> > 
> > origin
> 
> Dave, you you want me to delete the mirror and restart using -o master ?

Yes, I would suggest doing that. Once that is done I can test it out over the next several days and see how it is doing.
Comment 10 Eclipse Webmaster CLA 2011-01-06 09:43:25 EST
Has using the master option helped?

-M.
Comment 11 David Carver CLA 2011-01-06 10:23:15 EST
Sorry, I haven't had a chance to reclone.  Let me clone today and try to update tomorrow.
Comment 12 David Carver CLA 2011-01-06 12:27:41 EST
This looks better.   I no longer see an origin/origin reference.   I do see an origin/master reference so that looks like it should be fine.

I did have to manually checkout the master, but it worked.
Comment 13 Denis Roy CLA 2011-03-10 14:51:35 EST
Looks like we're done here.