Codehaus Update
May 19th, 2006After fighting with backups (check your backups, kids!), we’ve started getting the haus back online. Subversion repositories are back, read-only over HTTP at http://svn.codehaus.org/, the various distribution repos are back, such as http://dist.codehaus.org/. We did lose some commits in the SVN, and some deployments may be missing from dist. Now’s the time to sanity-check.
We’re continuing to work to get CVS, mail, and read/write access to Subversion back as soon as possible.
We truly appreciate all of the efforts to help, and your patience has been outstanding. We realize how painful downtime is.
May 19th, 2006 at 12:55 pm
Thanks.
May 19th, 2006 at 1:07 pm
Oh, yeah, http://svn.codehaus.org/ isn’t going to give you anything useful at the moment. But project-specific URLs, such as http://svn.codehaus.org/xfire will.
May 20th, 2006 at 7:16 am
Once everything is restored you should alert everybody that they must export & trash their working copies because otherwise very bad things might happen. See here
May 20th, 2006 at 9:55 pm
[...] Looks like Groovy has been hit with the same outage problems that a lot of open source projects have encountered this month. RangerRick has a good summary of how fink is dealing with the problems at sourceforge. [...]
May 21st, 2006 at 6:46 am
Holger,
I reviewed your comments and did some testing of my own (along with the help of our service provider Contegix).
While you can not force the client with an invalid working copy to update; there is not much they can do to harm the Subversion repository.
The scenarios I tested were as follows:
a) User attempts to commit changes from their revision 10 working copy against an older revision 5 restored repository: SVN blocks this due a bad checksum on the existing revisions.
b) User attempts to update their revision 10 working copy against an older repository (rev 5): SVN blocks this due to an unknown revision
c) User attempts to update their revision 10 working copy against a newer repository (rev 11): SVN blocks this due to a bad checksum
d) User attempts to update their revision 10 working copy against a repository (rev 10 - but a different rev 10): SVN pretends this is ok (when it isn’t really ok).
I only see option D being an issue - and that will still not allow the repository to be compromised by user error.
On this basis we’re going to reallow access to the subversion repositories as despots agree.
We will still be telling people to regrab their working copies; but the risk of compromise is limited.
Cheers,
Ben
May 22nd, 2006 at 2:12 am
That must have been a stressy weekend for you people! anyway good thing you got it running, for the most part anyway.
i was looking for m2eclipse but that’s not yet available I saw. Any idea when it’s up for download?
Anyway, good luck with setting up.
Ronald
May 22nd, 2006 at 12:46 pm
I’m also interested in m2eclipse.
Also, as a quick reminder for you: I’d like to see the following page, and it doesn’t seem to be back yet. I assume this is in a category of pages that are in your “yet to recover” list.
http://mevenide.codehaus.org/download.html
Thanks!
May 23rd, 2006 at 6:20 am
Hi,
I’m about to embark on converting my team to maven 2 in preparation for a big project we’re starting. We are severely “bandwidth-challenged” here in Africa, so it is critical that we use maven-proxy. I cannot have my people play with maven because the download speed is too painfully slow. However, I have no idea how to configure maven-proxy. The confluence site hints that the only docs for it are in http://www.codehaus.org/maven-proxy/core/src/test/resources/org/apache/maven/proxy/config/PropertyLoaderTest1.properties, but I’m still getting error 404 when trying to open that url. Any idea when it would be available?
Alternatively, can you perhaps just post an example configuration file?
Please, I’m getting enough flak as it is for wanting to move away from Ant.
May 23rd, 2006 at 6:28 am
Sorry, the url I’m trying is http://cvs.maven-proxy.codehaus.org/maven-proxy/core/src/test/resources/org/apache/maven/proxy/config/PropertyLoaderTest1.properties?rev=1.1&view=markup
The one I posted is what comes up once you click this one.
May 23rd, 2006 at 2:10 pm
Hi,
what happened to mojo.codehaus.org, all of maven 2 mojo docs appear to reside at that address, which seems to be dead. Please advise.
May 23rd, 2006 at 11:33 pm
Got the maven-proxy configuration file, thanks!
May 25th, 2006 at 4:09 pm
Is the server that handles mailing lists still down? I just tried to subscribe to the drools user list by sending an e-mail to: user-subscribe@drools.codehaus.org and got this response:
ezmlm-manage: fatal: Sorry, I’ve been told to reject all requests (#5.7.2)
Does this have anything to do with your downtime, or is it something else?
Thanks
May 27th, 2006 at 4:41 am
Val: Subscriptions are now handled via https://xircles.codehaus.org/manage_email
This will let us do some more “exciting things” with our lists. Stay tuned!
June 6th, 2006 at 4:52 pm
“Comment by Johan Hoogenboezem
May 23, 2006 @ 11:33 pm
Got the maven-proxy configuration file, thanks!”
Johan, where did you get the configuration file? Please email me a link if you could… mjohnsonaz74@hotmail.com or just send me the sample that you have. Thank you!