-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Over the last week we've had a few outages on hyacinth, the server for
s3, s4 and s6, caused by MySQL crashing. We expect cassia (the
remaining new database server) to be working this week, at which point
we will replace hyacinth until we can determine the problem. Until
then, there will probably be a couple more outages.
Sorry for the inconvenience.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkuqlOUACgkQIXd7fCuc5vJhrACeJak4Qs77Au42NrL7Pz1ALFRm
2FYAn3yOer2xAGrGjvB4odg6LHQfLG4r
=Zywe
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
At 04:40 UTC nightshade became unresponsive and was rebooted. No other
servers were affected.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkunnpgACgkQIXd7fCuc5vJelwCfYPlIDrR6nEUyuZHAeqfu8FQT
z5wAoLpzG8fN9C/t90n+4m1YhCP0Fgji
=OrWa
-----END PGP SIGNATURE-----
Hi all!
This is a quick reminder that registration for the Wikimedia Developers'
Workshop (in Berlin, April 14-16) will end on Sunday, March 21. Most places are
already take, but we have room for 16 more people to attend.
So, if you want to come, sign up now at <http://www.amiando.com/WMCON10DEV.html>!
More information about the workshop is available at <http://tinyurl.com/wmdev10>.
-- Daniel Kinzler
>> hi all
>>
>> many of our tools uses messages from betawiki because they are
>> translated in many languages.
>> But this messages must be synchronized and I think it's not very
>> economically if every user/tool do that self. Because of that I
>> propose
>> to create one database for all users which will be sync periodically.
>
>A database with one table per user? Sounds good.
>
>> What do you think? Are any other users interested for such a db?
>
>I would be interested.
>
>> Greetings,
>> Luxo
>
>Pietrodn
>powerpdn(a)gmail.com
I thought not one table per user, but rather one table for all messages.
On betawiki are a lot messages e.g.
http://translatewiki.net/wiki/MediaWiki:Abusefilter-revert-title/en.
So I would make a table something like
+
----------+------------------------+-----------------------------------------------------+
| LANG | MESSAGE |
TEXT |
+
----------+------------------------+-----------------------------------------------------+
| en | Abusefilter-revert-title | Revert all changes by
filter $1 |
+
----------+------------------------+-----------------------------------------------------+
| de | Abusefilter-revert-title | Alle Änderungen durch
Filter $1 rückgängig machen |
+
----------+------------------------+-----------------------------------------------------+
| fr | Abusefilter-revert-title | Révoquer toutes les
modifications par le filtre $1 |
+
----------+------------------------+-----------------------------------------------------+
the messages which will be synced should be one a list which every
ts-user can edit, so that it's easy for every user to add the messages
he requires.
--Luxo
Hello all,
cassini was non-responsive to ssh today (it made also problems in the days
before) and so I (hard-)rebooted it today and made some updates. Details under
https://jira.toolserver.org/browse/MNT-387
Sincerly,
DaB.
--
wp-blog.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Unless you build your own Python extensions in C, you can ignore this
message.
Hi,
I'm about to install an new version of Python on the Solaris login
servers. This is identical to the existing version, except it removes
the definitions of _XOPEN_SOURCE and _POSIX_C_SOURCE from the pyconfig.h
header. This has two implications for building Python modules in C:
* You can now build with C99 (-xc99=all)
* The default compilation environment is Solaris, not XPGv5.
* You can now select your own preferred version of XPG instead of being
forced to use XPGv5.
To build with C99, compile with '-xc99=all'. To build with XPGv6
instead of XPGv5, use '-D_XOPEN_SOURCE=600 -xc99=all'. If your
extension requires the old behaviour (XPGv5), build with
'-D_XOPEN_SOURCE=500'.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkujZsIACgkQIXd7fCuc5vJ9EwCfTuqf6NMDoAucAeq8+vVXSbg+
5r4AnAgDJP48nvpu/E7dSN5yGCjKiybf
=B/wS
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Wednesday morning UTC I will upgrade MySQL on rosemary. This will
involve about 20 minutes downtime while the server restarts. Queries
will be served by sql-s1 while s1-fast is down.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkue2GYACgkQIXd7fCuc5vKTTwCcDszqsuReFWF/PPDMu3dCpYoe
Z3QAniop+PJ9dndObOy1x7eLyPL2JKtm
=znxo
-----END PGP SIGNATURE-----
Hello all,
I plan to install updates of debian-packages in the next days (monday or
later). Please look at
https://jira.toolserver.org/browse/MNT-333
for a list and report if you expect problems.
Sincerly,
DaB.
--
wp-blog.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Tomorrow morning (UTC) I will reimport sql-s1's copy of enwiki from
sql-s1-fast. sql-s1 will be read-only while user databases are dumped,
then offline while data is copied from sql-s1-fast.
While sql-s1 is offline, all queries will be redirected to sql-s1-fast.
This issue is being tracked in JIRA as MNT-353.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (HP-UX)
iEYEARECAAYFAkucv4gACgkQIXd7fCuc5vKxjQCgto+hWcUDd3Fyt0wfz6VOsw+m
e7QAoK30PpuI/JZZIeNZuVGDVaeRdS88
=/7x2
-----END PGP SIGNATURE-----