All - Feel free to continue to use the old SVN path until I can get the import issue resolved with the Sourceforge admin team.
Thanks, -Ben On Dec 10, 2012, at 11:53 AM, John Peterson <peter...@cfdlab.ae.utexas.edu> wrote: > On Sun, Dec 9, 2012 at 2:25 PM, Kirk, Benjamin (JSC-EG311) > <benjamin.kir...@nasa.gov> wrote: >> On Dec 9, 2012, at 2:41 PM, "Kirk, Benjamin (JSC-EG311)" >> <benjamin.kir...@nasa.gov> wrote: >> >>> I'm going to start the Allura migration this afternoon. I'm expecting that >>> the SVN URL will change, which means everyone will need to 'svn switch' >>> once we find out what the new URL is. I'll let you know… >> >> Well this is not encouraging - >> >>> Forking/cloning repo svn in project libmesh from >>> http://libmesh.svn.sourceforge.net/svnroot/libmesh failed. The SourceForge >>> engineering team has been notified. >> >> I'll let you know what happens next, but the good news is we have an >> up-to-date github mirror ready to go in case things go south! > > Well, this page > > https://sourceforge.net/p/upgrade/ > > lists our status as "upgraded" but I doubt that since I was just able > to pull from the old SVN repo. > > Heard anything else about the upgrade failure? Ticket number, etc.? > > -- > John ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
