Page MenuHomeSoftware Heritage

googlecode import: Check for origin clashes and fix if any
Closed, ResolvedPublic

Description

Make sure we are not hitting the same origin clashes issue we had with svn origins.
If they exist, we must clean that up.

Related T897

Event Timeline

Yes, we are hitting the same problem.

ardumont@uffizi:~% grep -c eclipselabs /srv/storage/space/mirrors/code.google.com/sources/INDEX-hg
325
ardumont@uffizi:~% grep -c apache-extras /srv/storage/space/mirrors/code.google.com/sources/INDEX-hg
49
ardumont changed the task status from Open to Work in Progress.Feb 13 2018, 3:33 PM
ardumont renamed this task from googlecode import: Check for origin clashes to googlecode import: Check for origin clashes and fix if any.
ardumont updated the task description. (Show Details)
ardumont updated the task description. (Show Details)Feb 13 2018, 6:46 PM

Listing of the googlecode dumps recomputed with the right origin urls (in the actual INDEX-hg, old one is referenced as INDEX-hg.deprecated).

Remains to update the existing origins (in db) with the right urls but not today.

Remains to update the existing origins (in db) with the right urls but not today.

Status on fixing hg origins:

  • apache-extras
  • eclipselabs

But...
There also exists clashes from within the googlecode ones as well (because multiple different source repository archives ended up having the same origin instead of different ones).
So back at updating the index and the origins for those.

ardumont closed this task as Resolved.Feb 14 2018, 10:16 AM

So back at updating the index and the origins for those.

Done.