IMPORTANT: LLVM.org server move on June 24th! (SVN impact)

LLVMers,

The LLVM.org server which hosts SVN, GIT mirror, documentation, and the main 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

You can continue to access SVN via the old URL 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 —relocate https://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@sqlby.me.

Thanks,
Tanya

Woohoo, thanks for your and Mike’s hard work maintaining the project’s critical infrastructure!

. :slight_smile:

Is the new server supposed to work already? I'm getting:

$ svn co --depth=empty https://svn.llvm.org/llvm-project
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

-Dimitry

Is the new server supposed to work already? I'm getting:

No. The DNS entries were certainly added in advance to allow proper propagation.

+1 Thanks to all for all the (ongoing) hard work keeping this stuff going!

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?

-Tom

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

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

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?

Hi Chandler,

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?

The old URLs will still work. We will double check that everything
will be "like before".

But now git-svn will be unable to rebuild revisions without switching URL and breaking git hashes. Have folks tried this? What commands should git-svn and hit mirror users use to update?

But now git-svn will be unable to rebuild revisions without switching URL
and breaking git hashes. Have folks tried this? What commands should git-svn
and hit mirror users use to update?

They will use old URLs for the sake of compatibility.

Those URLs already broke when the certs expired? I’m guessing new certs will come online after the move finishes.

I really don’t understand how this is expected to work long term. Anyways, I’ll let you all get back to trying to pull stuff together. Once everything is back in a healthy state, please update with more details about the plan here for git users.

It’s possible I’m off base here, but a couple of things:

a) This shouldn’t be a problem if you’re using git with mono-repo (which we should be actively encouraging git-svn users to migrate to, given that it seems to be agreed upon that this is going to happen in some way or another in the future), since it’s not using git-svn.

b) IIUC the git-svn url is embedded in the commit message, but only locally, not on the server. So the server should continue to work fine, but if you switch URLs the only thing wrong would be your local git hashes, which would probably have to be rebuilt by running git svn rebase --force or something similar.

While svn seems to work, the current mono-repo does not seem to be updating.

Takumi, do you know anything about this?

I think the scripts that update the monorepo will have to be adjusted somewhat, not sure what all is required there.

We’ve verified that git-svn and the main git mirrors are healthy.

I am about to push the monorepo.

One divergence. Craig updated his mailto (since r306197) but new repo doesn’t have his new address.