https://code.launchpad.net/~vcs-imports/gradle/trunk is broken, how can it be fixed?

Asked by Russel Winder

VCS Import of this branch appears to be totally broken, what is the way of getting it working again.

lp:gradle is a manual mirror of what the VCS import ought to look like.

Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Paul Hummer Edit question
Solved by:
Celso Providelo
Solved:
Last query:
Last reply:
Whiteboard:
2009-06-03 gary Tried to answer, and assigned to rockstar to verify my answer.
Revision history for this message
Gary Poster (gary) said :
#1

My suspicion is that this is because of the certificate. This is what happens when I try to ``svn ls https://svn.codehaus.org/gradle/gradle-core/trunk`` locally:

Error validating server certificate for 'https://svn.codehaus.org:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: *.codehaus.org
 - Valid: from Fri, 06 Jun 2008 00:00:00 GMT until Sat, 04 Jul 2009 23:59:59 GMT
 - Issuer: http://www.usertrust.com, The USERTRUST Network, Salt Lake City, UT, US
 - Fingerprint: 92:14:7a:72:73:24:1d:d7:15:09:29:d4:c5:35:c7:02:6c:71:7f:3d

I will ask someone from the codehosting team to verify, but my guess is that getting the certificate signed by a trusted authority would help.

Gary

Revision history for this message
Paul Hummer (rockstar) said :
#2

It looks like http works just as well as https for this repo, so I've moved the import over to http. That removes one level of complication, but that error looks like an issue reading the svn repo itself. If this still fails after the change, this import might be a good candidate for the bzr-svn integration stuff we've been planning.

Revision history for this message
Russel Winder (russel) said :
#3

The Subversion repository was replaced in situ and the Launchpad mirror never recovered from this change. I suspect deleting this mirror and recreating is the best thing to be done. This will then rescan the repository which is needed due to there being a total change of history.

I have made my personal manually maintained Bazaar branch mirror the main branch for this Subversion repository until such time as the automated mirror works again.

Revision history for this message
Best Celso Providelo (cprov) said :
#4

Russel,

I've deleted the original import and created the new one for you (over http as rockstar recommended).

https://code.edge.launchpad.net/~vcs-imports/gradle/trunk

Flip the branches and mark this question solved once you verify the results are okay.

Revision history for this message
Russel Winder (russel) said :
#5

The import has been running 17 hours and not succeeded. The repository isn't that big, I suspect there is an importing problem.

Is there a difference between https://code.edge.launchpad.net/~vcs-imports/gradle/trunk and https://code.launchpad.net/~vcs-imports/gradle/trunk ?

Revision history for this message
Russel Winder (russel) said :
#6

I just branches it myself:

|> time bzr branch http://svn.codehaus.org/gradle/gradle-core/trunk Gradle_Trunk
Branched 1263 revision(s).

real 11m4.835s
user 3m40.114s
sys 0m4.852s
|>

Revision history for this message
Russel Winder (russel) said :
#7

OK, it seems that it took 20 hours to do an 11 minute branch and I wasn't sufficiently patient.

https://code.launchpad.net/~vcs-imports/gradle/trunk does now seem to be OK.

Thanks.

Revision history for this message
Russel Winder (russel) said :
#8

Thanks Celso Providelo, that solved my question.