Toolserver-l

toolserver-l@lists.wikimedia.org

1612 discussions

Perl & Python upgrades
by River Tarnell 01 Jun '10

01 Jun '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Several Perl and Python modules have been upgraded on the Solaris servers; a full list of upgrades is available at <https://jira.toolserver.org/browse/MNT-606>. Additionally, Perl 5.12 has been installed. This can be tested using /usr/bin/perl5.12; if there are no problems, it will become the default perl shortly. Some modules are not currently available for Perl 5.12, such as RRDTool and Graphviz. These will become available before the default is changed. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkwDP+YACgkQIXd7fCuc5vKzTQCgut3RpQEVU5PJrvGfjqH2StzK Pz0AnA8+KAV6CZ5jEPJqkToKsrLDKM4C =QnG/ -----END PGP SIGNATURE-----

2 2

Account-Extending June
by DaB. 31 May '10

31 May '10

Hello folks, at first of June, the toolserver-accounts will expire again. If you need your account further, please send an eMail to ts-accounts201001(a)dabpunkt.eu before this date. The eMail should contain your login-name in the subject and in the body. Please do NOT send the eMail to this mailing-list; write a NEW eMail, DON'T use the answer-function of your eMail-client (because it will send the eMail to this mailinglist). If you send the eMail to the mailinglist, you will get the "Can't use his/her eMail-client"-price (and some jokes from the regulars) and NO extending. This time, I will use our wiki to list account-names for which I got an email for (see [1]) — please be a little bit patient after you sent me the email. Maybe I will also send lists per mail too. Please notice that tools of expired users will be disabled, so if you plan to not extent your account, make sure that you transfer your tools to another ts- user before 1. June. We hope that this is the last time that we use email for account-extending and that we can use something new next time. If you have questions, please use the TS-Maillinglist. Sincerly, DaB. [1] https://wiki.toolserver.org/submit/Account-Extending_2010-01 -- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885

4 7

Need advice regarding compliance of a tool with TS rules
by stanlekub 31 May '10

31 May '10

Hi all, I was asked for a tool (which I wrote), but re-thinking of it I'm not totally sure it complies with toolserver's rules. Can I have your opinion please ? Basically, this is some sort of topic-based editcounter, which fetches the 10 users who contributed the most on the given theme, and does put it in a table like this[1] (for the Mascarene Islands topic in this example). Columns are 'username', 'editcount', 'number of distinct pages'. Thanks in advance, stan. [1] http://fr.wikipedia.org/w/index.php?title=Utilisateur:HAL/Test50&oldid=5380…

2 2

Bots editing while logged out
by Mike.lifeguard 31 May '10

31 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, There is a discussion on enwiki [1] which concerns bots editing while logged out. The proposal is to block the toolserver IP range to prevent this from happening -- however, this shouldn't be necessary since bots should never edit while logged out. Bot frameworks should help bot operators and authors by using an edit assertion [2] - is anyone aware of a framework which /doesn't/ do that? So, this is a reminder to please take care when writing scripts: check if your framework handles this for you, and if not, be sure to write your bot such that it edits only while logged in. If the toolserver IP range does end up being blocked, is anyone aware of read-only tools which would be adversely affected by the IP being blocked? Such tools are poorly designed, and their authors should fix them sooner rather than later, even if the block isn't placed in the end. - -Mike [1] http://en.wikipedia.org/?oldid=364741979#Proposal_to_softblock_Toolserver_I… [2] http://www.mediawiki.org/wiki/Extension:Assert_Edit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwDPWUACgkQst0AR/DaKHtTlACfW8XWbH/Pi1Yh1ExkaHVhabLa +y0AnRBSsHt7QYcWbUcPu4rANySCkFO2 =989j -----END PGP SIGNATURE-----

2 1

Set your default license
by River Tarnell 30 May '10

30 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, We have now introduced the concept of a default license for each account. This is documented on the wiki: <https://wiki.toolserver.org/view/Default_license>. In the future, selecting a default license will be required at account creation time (for new account), and at the next account renewal time (for existing accounts). I suggest people set their license now rather than leaving it until then. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkv6lXEACgkQIXd7fCuc5vLl0wCgvNuZiswGiH9xJg9IFZc5fkNG wTgAn35BkatTtn4IgVjFLkZJ1YSgnaP9 =Ch03 -----END PGP SIGNATURE-----

12 22

(re-)set your LDAP password and email address
by River Tarnell 26 May '10

26 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, It is now possible to reset your LDAP password automatically if you have an LDAP email address set. To do this, run "resetpass". However, this only works if you have an LDAP email address configured. All new accounts have this by default, but older accounts may not. To set your LDAP email address, run "setmail". This will tell you if you have an email address set or not, and let you set one if you don't. Once you set your LDAP email address, we recommend replacing your .forward file like this: $ echo USERNAME(a)toolserver.org >$HOME/.forward This will avoid having to update your email address in two places. There is no requirement that you set an LDAP email address. However, if you don't, you will not be able to reset your LDAP password if you forget it. LDAP passwords will be used for more things in the future, including account renewals. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkv8EHwACgkQIXd7fCuc5vJIPQCgvbmzshQpPIRahgINrZR18yAF WhYAnifSDlMafycJ9S35bbojMLCfoE0y =F5/S -----END PGP SIGNATURE-----

4 4

'setpass' and 'resetpass' no longer available on nightshade
by River Tarnell 26 May '10

26 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've rewritten these two utilities to improve security. The new versions depend on OS-specific features to work, and rather than duplicate code (which is likely to introduce security issues), I chose to drop Linux support. These tools are therefore only available on Solaris login servers (e.g. willow) from now on. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkv8fBQACgkQIXd7fCuc5vKBLwCfXVNHPy9HAcgQNf2yeYK+MeXz FL8An2168XJSBibxScH5LDexj9K61ZnU =8dNl -----END PGP SIGNATURE-----

3 3

Reboot of nightshade tonight
by DaB. 25 May '10

25 May '10

Hello all, I updated the kernel of nightshade a few minutes ago and now it needs a reboot. So I will reboot nightshade arround 22:15 UTC. The downtime should be quite low (few minutes) if no problems occure. You can follow the process at [1] if you like. Sincerly, DaB. [1] https://jira.toolserver.org/browse/MNT-593 -- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885

1 0

Is it allowed under the toolserver rules to make a tool that generates a podcast for wikinews content
by bawolff 24 May '10

24 May '10

Hi. At Wikinews, we have an audio sub-project - Audio Wikinews. It records the daily news in a radio-broadcast report style. Anyways, we upload the ogg files to commons, which is great, but iTunes/iPods don't like vorbis, which is a large potential audience. Would it be allowed to have a podcast feed on the toolserver, with mp3 versions of the files also on the toolserver so we could get audio wikinews into itunes? I imagine having a podcast/rss feed is within the rules, but having the mp3's on the toolserver seems borderline as a non-free format, and somewhat like using toolserver to serve actual content (although its not really wiki content). Anyways, I thought I'd ask just to see. Thanks, Bawolff

4 4

Emergency contact procedure
by River Tarnell 23 May '10

23 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As part of some work to improve the reliability of the Toolserver, by making sure admins are aware of problems, we have set up a new email address for reporting outages. This replaces the previous "send a text to river" procedure (the motd will be updated shortly). The new address is: ts-major-outage (at) TCX (dot) ORG (dot) UK You should mail this address in case of major problems, for example: * A login server is broken * The web server is broken * A normal database is broken (but not a fast server, unless it breaks something else) Don't use this for less urgent problems, such as: * JIRA or FishEye is broken * SVN is broken Admins will be usually be automatically notified of these problems, so you might want to check in IRC or the status page to see if it's already known before reporting it. - river. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (HP-UX) iEYEARECAAYFAkv5MsIACgkQIXd7fCuc5vK2pgCgkK1D5WFTQxNx19asVOn/dFs+ EpgAoI3ZbVfm+NEwpnJd8tGctOFcYgCb =wY/4 -----END PGP SIGNATURE-----

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Toolserver-l