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
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Unknown Object (Maniphest Task) | ||||
| Migrated | gitlab-migration | T367 ingest Google Code repositories | ||
| Migrated | gitlab-migration | T682 Ingest Google Code Mercurial repositories | ||
| Migrated | gitlab-migration | T957 googlecode import: Check for origin clashes and fix if any |
Event Timeline
Comment Actions
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
Comment Actions
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.
Comment Actions
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.