similar to: [LLVMdev] Upgrading llvm.org: Don't Use SVN Until We're Done

Dear All, If everything goes according to plan, Tanya will be done with the backups soon, and I will begin the process of upgrading llvm.org. As an FYI, Ubuntu requires that I do an upgrade release by release, so I'm going to reboot the machine a few times as I install progressively newer versions of the OS. You might see the web services coming online briefly after each reboot. Do not

rkotler at ubuntu-rkotler:~/llvm_trunk$ svn update svn: OPTIONS of 'https://rkotler at llvm.org/svn/llvm-project/llvm/trunk': could not connect to server (https://llvm.org)

Going down now. I'll send mail when its back up. -Tanya On Oct 26, 2011, at 3:12 PM, Tanya Lattner wrote: > Just FYI, I will be upgrading to 1.7.1 (from 1.5.4). > > Thanks, > Tanya > > On Oct 26, 2011, at 3:05 PM, Tanya Lattner wrote: > >> I'll be upgrading the SVN server on llvm.org this Friday from 9pm - whenever I am done. >> >> You will

Just FYI, I will be upgrading to 1.7.1 (from 1.5.4). Thanks, Tanya On Oct 26, 2011, at 3:05 PM, Tanya Lattner wrote: > I'll be upgrading the SVN server on llvm.org this Friday from 9pm - whenever I am done. > > You will notice that all web and of course svn services will be down during this time. > > Thanks, > Tanya > _______________________________________________

> On Jun 22, 2017, at 12:00 PM, Tom Stellard <tstellar at redhat.com> wrote: > > On 06/21/2017 03:22 PM, Tanya Lattner via llvm-dev wrote: >> LLVMers, >> >> >> >> TheLLVM.org <http://LLVM.org>server which hosts SVN, GIT mirror, documentation, and the mainLLVM.org <http://LLVM.org>website is moving to a new server on June 24th. As a

Hi, Got the same error, switching to https fixes the issue. Regards, ismail On Wed, Jun 28, 2017 at 12:50 AM, Tanya Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I haven’t gotten a lot of people mentioning this specific error, so I hope > others will speak up. > > What version of the svn client are you using? > > Thanks, > Tanya > > On Jun 27, 2017,

All, The server that runs the mailing lists will be down for maintenance starting Friday Dec 18th at 10:30PM PST. I do not expect a long downtime, but please keep this in mind if you see any issues with the lists during this period. I will send an email once I am finished. No other services should be affected. Thanks, Tanya

Thanks, fixed. On Sun, Jun 25, 2017 at 10:28 PM, Davide Italiano via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Sat, Jun 24, 2017 at 4:02 PM, Tanya Lattner via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> LLVMers, >> >> We have completed the move to the new server for LLVM.org. One casualty of >> this move was that svn.llvm.org was NOT enabled

On 06/28/2017 02:41 PM, Dmitry Babokin via llvm-dev wrote: > I've also switched to https and it solved the problem. > > With http, it's still failing almost always, when I'm behind corporate > proxy. And it does work when I'm not behind the proxy. Not sure if > it's a problem of the proxy, or it's interplay between the proxy and > svn server. I've

Hi, After the move I have problems with svn checkout of trunk and 4.0 branch. I get the whole bunch of different errors during checkout, including: svn: E000054: Error running context: Connection reset by peer svn: E000060: Operation timed out svn: E000104: Error retrieving REPORT: Connection reset by peer svn: E120106: ra_serf: The server sent a truncated HTTP response body. Sometimes I'm

All, After a long day, llvm.org is back up. Many thanks to John Criswell for helping with this upgrade. We hope that everything is working correctly, but if you see a problem, please email llvm-admin at cs.uiuc.edu. You are free to access svn and commit. If you have questions, please let me know. -Tanya

All, The following llvm.org certificates will be renewed tomorrow, Friday Sept 22nd at ~7:30AM PDT. bugs.llvm.org <http://bugs.llvm.org/> clang-analyzer.llvm.org <http://clang-analyzer.llvm.org/> clang.llvm.org <http://clang.llvm.org/> compiler-rt.llvm.org <http://compiler-rt.llvm.org/> dragonegg.llvm.org <http://dragonegg.llvm.org/> git.llvm.org

The svn and web server will be up and down tonight between 9PM and 10PM PDT for some maintenance. We recommend not accessing svn during this time period. Thanks, Tanya

Chris Lattner wrote: > On Mon, 7 Nov 2005, John Criswell wrote: > >> Tanya Lattner wrote: >> >>> Everything builds fine on sparc. The configure script needs to be >>> fixed though (see previous email). >> >> >> I'm not getting the error with the configure script (on Kain, anyway). >> I've tried it with --with-f2c and with f96

March or April? ;) -Tanya On Fri, 4 Apr 2008, John Criswell wrote: > Dear All, > > The LLVM network services (llvm.org web site, SVN server, etc.) will be > offline starting at 10:30 am Central Time on Tuesday, March 8. We are > moving the machine hosting these services to the server room where it > will be a dedicated server machine from Tuesday henceforth. > > I

I'll be upgrading the SVN server on llvm.org this Friday from 9pm - whenever I am done. You will notice that all web and of course svn services will be down during this time. Thanks, Tanya

Tanya Lattner wrote: > > Everything builds fine on sparc. The configure script needs to be fixed > though (see previous email). I'm not getting the error with the configure script (on Kain, anyway). I've tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my $PATH. Can you verify that the configure script works for you without the --with-f2c option?

On Mon, 7 Nov 2005, John Criswell wrote: > Tanya Lattner wrote: >> Everything builds fine on sparc. The configure script needs to be fixed >> though (see previous email). > > I'm not getting the error with the configure script (on Kain, anyway). I've > tried it with --with-f2c and with f96 (NAG Fortran compiler) in and out of my > $PATH. > > Can you

LLVMers, The LLVM.org <http://llvm.org/> server which hosts SVN, GIT mirror, documentation, and the main LLVM.org <http://llvm.org/> website is moving to a new server on June 24th. As a result of the move commit access will be locked out beginning 09:00PDT on the 24th. We hope to have the move complete and commit access restored to everyone in a timely manner, however, a move of

Any issues with permanently accepting the intermediate certificate, which I did this morning, when getting the message? Thanks in advance Garrison On Jun 29, 2011, at 12:13, John Criswell wrote: > On 6/28/11 3:56 PM, John Criswell wrote: >> Dear All, >> >> The good news is that the new llvm.org SSL certificate is installed and >> appears to be configured