[llvm-dev] IMPORTANT: LLVM.org server move on June 24th! (SVN impact)

[Zachary Turner via llvm-dev]

It looks like we're already locked out?

svn: E170013: Unable to connect to a repository at URL '
https://llvm.org/svn/llvm-project/compiler-rt'
svn: E230001: Server SSL certificate verification failed: certificate has
expired

And the new URL doesn't work yet either, when I try to use the switch
command I get this:

Error validating server certificate for 'https://svn.llvm.org:443':
 - The certificate hostname does not match.
Certificate information:
 - Hostname: bugs.llvm.org
 - Valid: from May 13 15:56:00 2017 GMT until Aug 11 15:56:00 2017 GMT
 - Issuer: Let's Encrypt Authority X3, Let's Encrypt, US
 - Fingerprint: 04:F3:AB:B9:57:69:1D:4D:78:B5:AC:2E:58:F4:81:77:FF:D2:CC:A6
(R)eject, accept (t)emporarily or accept (p)ermanently? p
svn: E170013: Unable to connect to a repository at URL '
https://svn.llvm.org/llvm-project'
svn: E175009: The XML response contains invalid XML
svn: E130003: Malformed XML: no element found




On Fri, Jun 23, 2017 at 12:49 AM Tanya Lattner via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

>
> > 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 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 this magnitude will take several hours to complete.
> >>
> >>
> >>
> >> In addition, this is the first step in moving SVN to a new URL:*
> svn.llvm.org <http://svn.llvm.org>*
> >>
> >>
> >
> > Hi Tanya,
> >
> > It looks like updates to the download.html page in the www-releases
> > repository are no longer being synced to the website, Is this related to
> > the upcoming move?
>
> Its not really related. Its no longer a post-commit hook but updated every
> 30 minutes. However, there was an issue and its now fixed. Once we finish
> the move, we will be either creating a new post commit hook or finding
> another approach (releases are not hosted on the same server as SVN
> anymore).
>
>
> -Tanya
>
> >
> > -Tom
> >
> >>
> >> You can continue to access SVN via the old URLllvm.org/svn <
> http://llvm.org/svn>but we would like people to start moving over to the
> new URL. This will allow us more flexibility in moving SVN and SSL
> certificates going forward.
> >>
> >>
> >>
> >> After the server move, you will may need to do the following:
> >>
> >>  *
> >>    Switch to the new URL via this command (you may need to adjust for
> your specific repo):
> >>
> >> svn switch —relocatehttps://llvm.org/svn/llvm-project/
> https://svn.llvm.org/llvm-project/
> >>
> >>  *
> >>    Accept the new certificate when using svn
> >>
> >>
> >>
> >> A huge thank you to Mike Edwards for leading and helping this move.
> Mike has generously donated his time to help with system administration
> going forward and is still looking for volunteers to help with our ongoing
> operations needs.  If you are interested in helping out please contact Mike
> at mike at sqlby.me <mailto:mike at sqlby.me>.
> >>
> >>
> >>
> >>
> >>
> >> Thanks,
> >> Tanya
> >>
> >>
> >>
> >> _______________________________________________
> >> LLVM Developers mailing list
> >> llvm-dev at lists.llvm.org
> >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >>
> >
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170624/cff157fb/attachment.html>