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

Chandler Carruth via llvm-dev llvm-dev at lists.llvm.org
Sat Jun 24 01:07:42 PDT 2017

This thread doesn't have any instructions on what to do if you use git-svn
and the git mirrors built with git-svn. That's really alarming. A huge
number of developers are using that. The getting started docs have that.
This move should have it as well.

Worse, all the docs I see say that the git log messages, because the encode
the URL of the SVN server in them, have to be completely rebuilt after
relocating a git-svn repository. This would completely invalidate all of
the git hashes for all of the git mirrors. Several folks have indicated
they are relying on that, including but not limited to the Swift github
clones. What is the plan there?

On Fri, Jun 23, 2017 at 10:00 PM Mike Edwards via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> On Fri, Jun 23, 2017 at 5:52 PM, Zachary Turner via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>> 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
> The new url is not accepting commits yet. If you need to commit tonight
> you will need to just accept the expired cert and you may still commit.  At
> 09:00PDT tomorrow we will lock out access to the SVN repository and
> commence with the change.  We will notify the list as planned when we have
> completed the move.  I'm very sorry for the confusion caused by the expired
> cert this evening.  Hopefully once everything is done tomorrow we will not
> run into this issue again.
> Thanks,
> Mike
> _______________________________________________
> 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/42491474/attachment.html>

More information about the llvm-dev mailing list