Your text says the maintenance will start at 08:00 UTC, but the link implies 00:00 UTC. Which is it?<br><br>Shubinator<br><br><div class="gmail_quote">On Tue, May 31, 2011 at 2:41 PM, River Tarnell <span dir="ltr"><<a href="mailto:river.tarnell@wikimedia.de">river.tarnell@wikimedia.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hi,<br>
<br>
On the morning (UTC) of June 6th we will performance general maintenance[0]<br>
on all servers. Services will be affected as follows:<br>
<br>
Service | Expected impact<br>
--------------------------+--------------------------------------------------<br>
Entire platform | As described in maintenance schedule[0]<br>
FishEye | Unavailable for < 10 minutes<br>
<br>
[0] <a href="https://wiki.toolserver.org/view/Maintenance_schedule" target="_blank">https://wiki.toolserver.org/view/Maintenance_schedule</a><br>
<br>
Start time: Monday, 6th June, 0800h UTC (or possibly earlier)<br>
<a href="http://time.tcx.org.uk/utc/2011-06-06/00:00" target="_blank">http://time.tcx.org.uk/utc/2011-06-06/00:00</a><br>
<br>
End time: Monday, 6th June, 1200h UTC (estimated)<br>
<a href="http://time.tcx.org.uk/utc/2011-06-06/12:00" target="_blank">http://time.tcx.org.uk/utc/2011-06-06/12:00</a><br>
<br>
Details:<br>
<br>
We will install current operating system patches on all servers, which will<br>
require a reboot of each system.<br>
<br>
--<br>
<br>
We will enable IPv6 on the NFS server, which might make /home<br>
unavailable for a short period even if hosts are up.<br>
<br>
--<br>
<br>
FishEye will be upgraded to 2.5.5.<br>
<br>
--<br>
<br>
We will perform general software upgrades for ts-specs (/opt/ts). A list of<br>
software to be upgraded can be found at:<br>
<br>
<<a href="https://wiki.toolserver.org/view/Admin:Pending_maintenance_tasks" target="_blank">https://wiki.toolserver.org/view/Admin:Pending_maintenance_tasks</a>><br>
<br>
Some software may be unavailable or function incorrectly during the upgrade<br>
process, which we estimate will take under 30 minutes.<br>
<br>
Note: Mono will not be upgraded due to a build failure which was not<br>
fixed in time for the maintenance.<br>
<br>
ts-specs (/opt/ts software) changes<br>
- -----------------------------------<br>
<br>
We now build software with GCC stack-smashing protection (-fstack-protector) by<br>
default, and several packages have been rebuilt to benefit from this. This<br>
should not cause any user-noticable changes.<br>
<br>
Some notable changes are detailed below:<br>
<br>
webp<br>
- ----<br>
<br>
The "webpconv" binary is no longer provided; instead, use cwebp and dwebp.<br>
<br>
OpenSSL<br>
- -------<br>
<br>
We will install a set of root CA certificates for OpenSSL, which will enable<br>
SSL connections (e.g. from cURL or wget) to work by default, as long as the<br>
certificate is valid, rather than requiring the user to provide a certificate<br>
or disable checking.<br>
<br>
The set of installed certificates will be the current Mozilla root certificate<br>
set (from Firefox) and the Toolserver CA certificate from<br>
<a href="https://fingerprints.toolserver.org" target="_blank">https://fingerprints.toolserver.org</a>.<br>
<br>
Python 3<br>
- --------<br>
<br>
The default version of Python 3 (/usr/bin/python3) will change to 3.2. Python<br>
3.1 will be removed during the following maintenance.<br>
<br>
MySQL<br>
- -----<br>
<br>
The MySQL client will be upgraded to 5.5.12, and will move from<br>
/opt/ts/mysql/5.1/bin to /opt/ts/bin. If you currently call "mysql" without a<br>
path, you do not need to change anything. If you use<br>
"/opt/ts/mysql/5.1/bin/mysql", you should change to "/opt/ts/bin/mysql" (or<br>
preferably remove the path and rely on $PATH). The old (5.1) client will still<br>
be available for now.<br>
<br>
The MySQL client library will also move to /opt/ts/lib. The old client library<br>
will still be available, but if you have any compiled software which links<br>
against MySQL, you should re-compile it with the client library in /opt/ts/lib.<br>
<br>
libpng<br>
- ------<br>
<br>
libpng has been upgraded from 1.4 to 1.5. A 1.4 runtime library is provided<br>
for compatibility, but if you have any software that links against libpng, you<br>
should recompile it with 1.5. The following warning (from the libpng<br>
documentation) applies to this upgrade:<br>
<br>
The libpng 1.5.x series continues the evolution of the libpng API,<br>
finally hiding the contents of the venerable and hoary png_struct and<br>
png_info data structures inside private (i.e., non-installed) header<br>
files. Instead of direct struct-access, applications should be using<br>
the various png_get_xxx() and png_set_xxx() accessor functions, which<br>
have existed for almost as long as libpng itself. (Apps that compiled<br>
against libpng 1.4 without warnings about deprecated features should<br>
happily compile against 1.5, too.)<br>
<br>
GCC<br>
- ---<br>
<br>
GCC has been upgraded to 4.6.0. This should be backwards compatible, so there<br>
is no need to recompile software. There are two relevant changes for C++ users:<br>
<br>
* If you define _XOPEN_SOURCE, you need to use -D_XOPEN_SOURCE=600.<br>
-D_XOPEN_SOURCE=500 will not work.<br>
<br>
* GCC 4.6 will no longer accept a const object without a ctor, i.e.:<br>
<br>
struct S { };<br>
const S o;<br>
<br>
The fix is to either add an empty constructor, or explicitly default-initialise<br>
the object:<br>
<br>
const S o = S();<br>
<br>
- river.<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.11 (SunOS)<br>
<br>
iEYEARECAAYFAk3lYHIACgkQIXd7fCuc5vKCpgCfTKXkByYIjD8f7sFhSRk+kMSl<br>
BksAoI86/sVpyhFt6YoFpYjI+OUS+OQj<br>
=+Pc2<br>
-----END PGP SIGNATURE-----<br>
<br>
_______________________________________________<br>
Toolserver-l mailing list (<a href="mailto:Toolserver-l@lists.wikimedia.org">Toolserver-l@lists.wikimedia.org</a>)<br>
<a href="https://lists.wikimedia.org/mailman/listinfo/toolserver-l" target="_blank">https://lists.wikimedia.org/mailman/listinfo/toolserver-l</a><br>
Posting guidelines for this list: <a href="https://wiki.toolserver.org/view/Mailing_list_etiquette" target="_blank">https://wiki.toolserver.org/view/Mailing_list_etiquette</a><br>
</blockquote></div><br>