SSL Negotiation failed with SourceForge import

I've updated the branch URL to use http instead of https. Let's see if it goes through

Hi Diogo,

Thanks for your attention to this matter. Unfortunately, it looks like
it's failed again:
https://code.launchpad.net/~vcs-imports/mixxx/features_sqlite

Thanks,
Albert

On Thu, Jul 2, 2009 at 12:08 AM, Diogo
Matsubara<email address hidden> wrote:
> Your question #75624 on Launchpad Bazaar Integration changed:
> https://answers.edge.launchpad.net/launchpad-code/+question/75624
>
>    Status: Open => Answered
>
> Diogo Matsubara proposed the following answer:
> I've updated the branch URL to use http instead of https. Let's see if
> it goes through
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.edge.launchpad.net/launchpad-code/+question/75624/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.edge.launchpad.net/launchpad-code/+question/75624
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Hi Albert,

a new import is now schedule. Let's retry it a few times and if it doesn't work I can contact one of the developers to do a manual code import.

Thanks and sorry for the inconvenience.

Hi Albert, Diogo and Michael,

I am adding my question here because I'm having the same problem importing (for the first time) a new project from SourceForge.
This is the branch that fails: https://code.launchpad.net/~vcs-imports/postlet/trunk

It sometimes fails fairly quickly (19 minutes, 12 minutes) but it usually goes on for a fair amount of time (1 hour 40, 2 hours, 3 hours) before failing. It consistently fails with this type of message:

PROPFIND of '/svnroot/postlet/trunk/Postlet/SRC/JAVA': SSL negotiation failed: Connection reset by peer (https://postlet.svn.sourceforge.net)

I know that the repository url is now using HTTPS, however if I believe the previous messages, changing it to HTTP might not ensure success, as I see that mixxx has still not succeeded in having a proper import, even after changing the protocol to HTTP.

Is this an issue that appears automatically on all new SourceForge projects? Does it require manual import?

Thanks,
Emilien Klein.

(In the future, please ask new Questions for new issues, it's much easier for us!)

The https -> http changes does not always work, no. But every time I've tried it, it's got much further, so let's give it a go this time too!

Well, it seems that after 3 hours and 50 minutes, the import was successful! So changing HTTPS to HTTP definitely helped!

P.S.: I added my question in this one because I think that people experiencing the same issue might find it handy to have one place for this specific problem, and the title of "SSL Negotiation failed with SourceForge import" was exactly my problem, so showed up as first result in Google. But I promise I'll open new questions in the future! ;)

While we're on the topic again, my Features_sqlite import still hasn't succeeded. Any ideas?

Thanks,
Albert

Hi guys, it looks like the SVN import magically succeeded a week or so ago. Not sure what anyone did that make that happen, but thanks to whoever did something behind the scenes. :)

Albert

Huh, I don't think I did anything (I was on holiday!). Happy it worked though!