Hi,
We're about to apply necessary schema changes for Wikimedia's MediaWiki
1.17 upgrade to the Toolserver databases. We will apply the changes to
one server for each cluster at once; while the primary server is being
updated, user databases will be unavailable, but replication won't be
interrupt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex:
> Alex Brollo wrote:
>> I'd like to install into my toolserver account djvuLibre binaries.
> Or just file a JIRA ticket to have it installed for everyone.
It is already installed, and has been for some time:
willow% pkginfo|grep djvu
TS
On Sat, Feb 5, 2011 at 7:06 PM, Alex Brollo wrote:
> Some day I'll understand such a statement "file a JIRA ticket". By now,
> aramaic is much be simpler. :-)
לישנא דארמאי לא קשיא לחדא.
:)
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.or
sounds nice,
idea would be to use open layers
see this example:
http://openlayers.org/dev/examples/kml-layer.html
mike
On Sun, Feb 6, 2011 at 1:06 PM, Maarten Dammers wrote:
> Hi everyone,
>
> For Wiki Loves Monuments
> (http://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Monuments) I'm
> harv
Hi everyone,
For Wiki Loves Monuments
(http://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Monuments) I'm
harvesting information about monuments (cultural heritage) into a
database. These monuments can be found in the database p_erfgoed_p at
sql. The tables are in the form monuments_ and ther
If the api was only a thin wrapper around some base classes, then indeed you
would not need fauxrequest. However the api does much processing itself and
in practice using fauxrequest is much easier.
Bryan
Op 6 feb 2011 02:29 schreef "Krinkle" :
Ilmari Karonen wrote:
> On 02/06/2011 12:42 AM, Kr
