This page outlines user-visible aspects of the impending completed migration of the sourceware.org / gcc.gnu.org server to a new server at a new colocation facility.

  1. Date
  2. Expectations
  3. Contact
  4. Status
  5. FAQ

Date

Plan: 2020-03-07 and 08: the entire weekend. Some fallout expected to continue afterwards.

Expectations

Expect that sourceware.org / gcc.gnu.org will be unreachable as of Saturday morning. During the weekend, its IP address will change. After the weekend, it will come up, with the following set of services prioritized:

  • developer logins (restricted-shell, ssh)
  • version control systems (git, git-over-ssh)
  • basic web services
  • bugzilla data & instances
  • mailing lists, switching from ezmlm/listarch/qmail to mailman & postfix

Most other subsystems will be brought online in the subsequent days as quickly as possible. Old information will not be lost, but may take a while to bring everything back to accessibility. The intent is to allow our beloved developers to get started with minimal downtime, and our overseers not to have to cram every bit of migration into a weekend.

One major change will be the deprecation of qmail/ezmlm/mhonarc, and replacing it with postfix/mailman. This will make the web interface more modern (self-management etc.), the infrastructure nice pure rhel, but some conveniences / familiarity with the mhonarc archives will unfortunately be lost.

One incidental change is that users who never set up a high-quality RSA or EC/etc. public key for authentication, and have only a low-quality DSA key, are no longer able to log on. Please send a new modern public key to overseers@.

Contact

Overseers plan to be reachable via the overseers@sourceware.org email address, except during the migration weekend itself! The best way to contact them and monitor the general goings-on is join the freenode IRC channel #overseers.

Status

  • 2020-02-26 this announcement
  • 2020-03-03 DNS TTLs have been shortened to anticipate DNS switchover
  • 2020-03-04 TESTING begins - some recent snapshots copied in read-only mode, browse only!
  • 2020-03-04 TESTING: ssh -v server2.sourceware.org should work about the same
  • 2020-03-04 TESTING: git://server2.sourceware.org/ and ssh://server2.sourceware.org/ access to snapshots of git repos is available
  • 2020-03-05 TESTING: Your anon-FTP and anon-CVS :pserver: prayers have been answered.
  • 2020-03-06 SNAFU: cygwin.com has become prematurely redirected to the new server, sorry, treat as read only!
  • 2020-03-07 GAME ON
    • rsync, ftp, enabled
    • ssh: and git: based git operations working
    • mailing lists now served by postfix/mailman, more info coming later
    • bugzilla services (mysql, the bugzilla perl code
    • moinmoin wikis (gcc, sourceware)
    • gitweb - some broken
  • 2020-03-08 gitweb and many other things fixed
  • 2020-03-09 mailman filtering/munging policies in flux
  • 2020-03-11 most bugzilla related features working, but not yet git->email->bugzilla
  • 2020-03-12 http/https: based git operations working
  • 2020-03-12 email to {gcc,sourceware}-bugzilla working
  • 2020-03-15 mnogosearch local web search engine working
  • 2020-03-20 archaeology support subversion working for gcc.gnu.org

We plan to assemble status/details of the various services here, as they come online. (See also details)

FAQ

  • Will the new machine be faster?

    Yes. 256GB RAM, 64-core, Centos8 should make a big difference.

  • How will the new mailing lists look?

    See https://gcc.gnu.org/mailman/listinfo https://sourceware.org/mailman/listinfo . It's similar but different.

    We hope this more standard system will be generally suitable. DMARC-inspired munging policy of From:/etc. headers is still being discussed. Attachment filtering policy being tweaked. We are sorry for the configuration flux, as we all get used to this system.

  • How to report problems?

    #overseers IRC or email to overseers@sourceware.org