17th July 2008

Subclipse not working after Sourceforge SVN migration

posted in Cahiers de l'Informatique |

Today Yesterday we’ve had a really busy day fixing obscure bugs in order to prepare the next release of the Contract core components. What we didn’t know was that the Sourceforge.net SVN migration was scheduled for yesterday. 12 hours of read-only access has been really painful, mainly concerning concurrent development.

However, after the migration finished, I still couldn’t commit the huge amount of changes I had done through the day. In fact, it was giving me the same error as during the whole day:

svn: Commit failed (details follow):
svn: Commit failed (details follow):
svn: MKACTIVITY of ‘/AgentWS/!svn/act/f371347b-0541-0410-8082-ddb3ab739141′: 403 Forbidden (https://ist-contract.svn.sourceforge.net/svnroot/ist-contract)

I even checked with a different SVN client and I could perfectly commit with no problem. Looking for a solution in Google didn’t help very much and I started panicking over the idea of having to check everything out in a separate project (or workspace) and remake all the changes. My sources in Eclipse didn’t even get updated with the changes I had made with the SVN client.

But then, the miracle. After checking out in a blank workspace, I switched back to the faulty one to start checking which files were changed. I don’t know exactly why, but I tried updating a project… and it worked!!!

Don’t ask me how and why these things happen, or if it’s even something only related to Subclipse. I am too tired right now to think on a logical conclusion. Probably it has to do with the host certificate or something like that but, in any case, these things can really spoil a mood in case of bad luck or a solution misleading. Anyway, software developing wouldn’t be so interesting without this kind of nonsense problems, would it?

Just kidding.

This entry was posted on Thursday, July 17th, 2008 at 6:38 am and is filed under Cahiers de l'Informatique. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

There are currently 3 responses to “Subclipse not working after Sourceforge SVN migration”

Why not let us know what you think by adding your own comment! Your opinion is as valid as anyone elses, so come on... let us know what you think.

  1. 1 On July 18th, 2008, Paul said:

    I’m having such problems as well but I think it’s something related to maintenance or whatever.Happens daily at about 20 o’clock GMT…very bad thing! I’m using subversive.

  2. 2 On July 19th, 2008, Paul said:

    http://www.nabble.com/problems-with-svn-commit-td18495773.html

  3. 3 On July 19th, 2008, tranchis said:

    Well, I haven’t had the “403 Forbidden” since the maintenance finished but it’s true that sometimes it’s really really slow or the connection “resets by peer”.

    I guess it’s something normal considering that they have migrated everything to a completely different location. It will get better soon, I guess :)

Leave a Reply