code imports from sourceforge are blocked

Joey is in contact with SF about this.

Hi, We have a relationship with SF now. They are going through a datacenter move which is complicating this. They have agreed to restore service but have not given an exact date yet.

Maybe you guys should consider throttling bandwidth or something. The gnucash admin also blocked canonical because of the bandwidtch used. Maybe you can take a break every few hours and import piece by piece? Like say, import 100 revisions and pause for the amount of time that took. This would also lead to a partial import becoming available faster for the imported bzr branch.

I've asked Sourceforge about this but so far they have not replied. They are in the midst of a datacenter move so I expect it may take them some time to reply.

Would it make sense for us (i.e. Launchpad) to temporarily disable/stop all imports from sourceforge for the time being?

We seem to have access again. Probably best to leave this bug open until we know that this was intentional on their end though :)

This looks like it's still an issue:
https://code.edge.launchpad.net/~vcs-imports/openrpg/trunk

http://launchpadlibrarian.net/16103401/openrpg-trunk-log.txt

cvs [checkout aborted]: connect to openrpg.cvs.sourceforge.net(66.35.250.83):2401 failed: Connection refused

<matsubara> Rinchen: any news about the SF blockage?
<Rinchen> yeah they emailed me yesterday
<Rinchen> 1-2 weeks

Tentatively targeting to 2.1.8. SF said they should be able to unblock us fully by the 8th. We've seen intermittent restoration of service though already.

Its the 9th. Do they have any idea when they could restore it - or did they just forget?

I've emailed them again around 14:38 UTC today.

Jacob at SourceForge emailed me today:

"We had a delay in handling this part of the migration, so I'll need to circle back in a couple more weeks. Our migration efforts cover a lot of very different services (from a systems level); we've moved on to the next service and will be circling back to finish out SVN."

In a previously publicized note to SF users, the end of August was used as the completion date. So, it looks like 1st of September might be the next checkpoint.

Slipping to 2.1.9 per my previous comment. :-(

6 more days! We been waiting for months... some how i don't feel confident they will meet the dead line.

Actually, it's been less than a month :)

Time flies, but not _that_ fast.

Er, I can't count. /me hides.

Have sent another touch base email to SF today. Should have a
response in a day or so.

From SF:

Date: Fri, 29 Aug 2008 09:08:57 -0400

We're gearing up for a test of some additional NAS gear (which is the dependency for opening SVN access to you again). Hoping for that to wrap-up shortly after Labor Day. I'll be back in touch at that time with a more in-depth reply to the info you've provided here.

what about cvs? That's the beast i want.

Sourceforge has released their latest migration schedule. It appears this will linger a few more week.

MIGRATION SCHEDULE

The SourceForge.net Service Operations team is now actively working to
complete our migration from our old California datacenter to our new
Chicago datacenter. The following migration events have been scheduled:

* On Monday, 2008-09-15, SourceForge.net user account mail aliases
(@users.sourceforge.net accounts) will be migrated as per:
http://sourceforge.net/community/forum/topic.php?id=3388&page

* On Monday, 2008-09-15, Project Web service for those projects already
running in Chicago (the "bigprojects" pool) will have a brief downtime
as we move data on to new storage hardware as per:
http://sourceforge.net/community/forum/topic.php?id=3411&page&replies=1

* On Tuesday, 2008-09-16, the remainder of Project Web will be migrated
(with some downtime) as per:
http://sourceforge.net/community/forum/topic.php?id=3410&page&replies=1

* Tentatively, on Wednesday, 2008-09-17, CVS service will be migrated
(with some downtime) as per:
http://sourceforge.net/community/forum/topic.php?id=3413&page

* On Thursday, 2008-09-18, Mailing List service will be migrated (no
downtime anticipated), including Mailing List archives and Mailing List
search, as per:
http://sourceforge.net/community/forum/topic.php?id=3412&page

Given the latest schedule from Sourceforge, this won't make the release next week. I'm pushing it out again until 2.1.10. I know the SF crew is working hard to complete their move.

Emailed the SF crew again today.

There is a plan to fix this as of today. Next week maybe.

Today from Sourceforge: "Blocks have been removed fully, as far as I can see. Please go ahead and resume activity."

I confirmed that we can do checkouts now on our import machines however the automated process is still failing.

It was just one import that was failing for slightly obscure reasons. The vast majority are working fine again.

My branch is still not working :

https://code.launchpad.net/~vcs-imports/panda3d/main

Oh sorry i just noticed its failing for a different reason. I'll post that as a new bug.