-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20.01.2014 17:26, Tim Landscheidt wrote:
As I wrote last month in
http://permalink.gmane.org/gmane.org.wikimedia.toolserver/6450, you
can export an XML dump of your project's issues (you'll have to
download attachments manually (or write a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19.01.2014 03:21, Tim Landscheidt wrote:
These are two very different problems.
AFAICS the wiki can be moved rather easily; your mail trig- gered
me to finally create the bug from my notes written long ago :-)
(cf.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would vote strongly to keep the wiki and also JIRA somewhere
accessible. Both contain a serious amount of history and documentation.
Can that be done?
Greetings
DrTrigon
On 25.12.2013 21:05, Emilio J. RodrÃguez-Posada wrote:
Hi all;
I'm not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello DaB
Thanks for your answer!
If you make a more detailed question, maybe I can give you a more
detailed answer.
E.g. is it still planned to discontinue the TS? Having 2 payed admins
does not sound like that... - good news?
Thanks and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you're asking is it safe to move tools to Labs, my experience
so far say yes. I can't speak for all unique toolserver
features, though.Cheers,Magnus
If you don't care about losing your (nfs) file system every once in
a while and having very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all!
Pywikibot finished GIT migration. Now a question has anybody ever
tryed to clone and use the e.g. the pywikibot/compat repo on the TS?
If I do, I get and .git folder of about 200MB which nearly fills my
home quota. (this is the plain clone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello DaB!
Could you please give me a short update - the end of 2013 is
approaching, what is the current state for TS resp. Labs?
Thanks and Greetings
DrTrigon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10.08.2013 12:37, legoktm wrote:
On Sat, Aug 10, 2013 at 5:26 PM, Dr. Trigon dr.tri...@surfeu.ch
mailto:dr.tri...@surfeu.ch wrote:
Hello all!
Pywikibot finished GIT migration. Now a question has anybody ever
tryed to clone and use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
May be someone working with dumps can help?
- Original Message
Subject:[Pywikipedia-l] xmlreader.py
Date: Wed, 31 Jul 2013 20:03:17 +0100 (BST)
From: Automatik Wikipedia automati...@yahoo.fr
Reply-To: Automatik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yes, there is a minor problem with ngnix I haven?t time to fix yet.
Also there is a harmless error-message about quota at login.
The funny thing with the quota error-message is, it works correct if I
do have over-quota when loggin-in. Not so if the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luckily those externals are important just for 1 script (catimages.py)
at the moment, so if you checkout the code except those 2 externals,
you should be fine - don't worry! ;)
In fact I was thinking about doing a svnsync from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks so much!! ;)
Have a nice day!
On 23.05.2013 14:50, Marlen Caemmerer wrote:
Hello,
the SVN waited for configuration on the new installation and is
now finished.
Kind regards Marlen/nosy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for that! (btw. ;)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlGc+f0ACgkQAXWvBxzBrDDyRwCgmDHayk3D162RF/TFbgDun7lp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is SVN supposed to be down still?
DrTrigon
On 18.05.2013 22:37, DaB. wrote:
Hello all, At Saturday 18 May 2013 22:29:07 DaB. wrote:
We can only think of one solution: Replacing the solaris at the
ha-nodes with linux. But this can not start
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please make SVN work... :)
On 20.05.2013 12:39, Jason Y. Lee wrote:
Please let me know if there is any assistance I can provide.
Regards,
AllyUnion
On Mon, May 20, 2013 at 1:37 AM, Dr. Trigon dr.tri...@surfeu.ch
mailto:dr.tri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Admins!
As I noticed it seems as if the cronjobs are executed correct at the
moment, so may be TS-1635 [1] can be closed. Though the statistics on
[2] are gone. Furthermore there are several cron-servers on [3] now.
Can someone give me a brief
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Admins!
Could please someone take care of TS-1301 [1]? This ticket is now open
for quite a while and having the possibility to generate docs and
coverage reports on the TS would be very favourable.
[1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks a lot!!
On 11.04.2013 09:49, Marlen Caemmerer wrote:
Hey,
I set your account expiration to 1st June.
Cheers Marlen/nosy
On Thu, 11 Apr 2013, Dr. Trigon wrote:
Date: Thu, 11 Apr 2013 09:43:31 From: Dr. Trigon
dr.tri...@surfeu.ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If that helps, here you are:
https://jira.toolserver.org/browse/TS-1636
Greetings and all the best
DrTrigon
On 10.04.2013 16:14, K. Peachey wrote:
I would recommend opening a ticket in JIRA.
On Wed, Apr 10, 2013 at 11:17 PM, Dr. Trigon dr.tri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If that helps, here you are:
https://jira.toolserver.org/browse/TS-1635
Greetings and all the best
DrTrigon
On 10.04.2013 16:14, K. Peachey wrote:
Was this issue filed in JIRA?
On Wed, Apr 10, 2013 at 11:18 PM, Dr. Trigon dr.tri...@surfeu.ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello beloved Admins!
Today I recognized that my account has expired (what a pitty) so I
tried as usual to login and renew but just get this:
$ ssh drtri...@nightshade.toolserver.org Your account has expired;
please contact your system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PING! Any news here? Why was this ignored?
Greetings
DrTrigon
On 30.03.2013 14:37, Dr. Trigon wrote:
Hello everybody! Hello nosy!
Do you remember the issue below...? :)
On 05.03.2013 13:03, Marlen Caemmerer wrote:
Then another issue - I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everybody!
Hello nosy!
Do you remember the issue below...? :)
On 05.03.2013 13:03, Marlen Caemmerer wrote:
Then another issue - I think (again - sorry but yes! ;) we have
some problem with cron job execution. When looking at my bots
(even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05.03.2013 13:03, Marlen Caemmerer wrote:
Since about 2 days I got errors because my bot script started
running on mayapple.toolserver.org. As you might remember, back
last year (I think) there were [1], [2] and [3].
[1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello DaB!
Hello to everybody!
Since about 2 days I got errors because my bot script started running
on mayapple.toolserver.org. As you might remember, back last year (I
think) there were [1], [2] and [3].
[1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks DaB whatever you (or someone else? ;) did!
Now it works again as you can see from looking at [1] there was clearly
a drop in executed jobs now it is on a constant level again! Cool!
[1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.02.2013 01:30, DaB. wrote:
I am now noticing issues with my cronjobs too.
What exactly is the problem?
Cronjobs not getting executed (as usual... ;) - at the moment I do
also have jobs in SGE queue that do not get runned at all (at least
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
There were 2 messages here during Janury reporting problems with cron.
I am now noticing issues with my cronjobs too. By looking at [1] you
are able to see that the strange behaviour started somewhen week 2 and
3 (mid January). Do we have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Happy new year to everybody!! (thanks for all your work!)
So long, and thanks for all the fish (for this year ;))
DrTrigon
On 24.12.2012 14:04, DaB. wrote:
Hello all,
2012 was not very kind to the Toolserver and 2013 will not be much
better.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25.11.2012 23:03, Marlen Caemmerer wrote:
Hello,
nice to hear. I had a look from all sides but it seemed the SGE
master thought the queues on the hosts were full. This morning when
I looked I saw only willow doing some jobs - ortelius still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25.11.2012 23:44, DaB. wrote:
I have not decided yet if I will remain as root under this
circumstances for 2013 ? I will tell you my decision until next
Sunday.
I hope you stay - but it's (of course) your decision...
For now I will head to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today it seems to be working and fully functional again... Nice job! ;)
Thanks to all involved here!
Greetings and have a nice weekend
DrTrigon
On 24.11.2012 22:10, Platonides wrote:
On 24/11/12 21:38, Dr. Trigon wrote:
@All: If you are working
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+ 1(the same for me)
Greetings
DrTrigon
On 23.11.2012 20:46, Tim Landscheidt wrote:
(anonymous) wrote:
At some point I even logged in, clicked an issue, clicked Edit
(which uses AJAX) and then the Edit screen wouldn't load due to
me not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
I have an issue with my jobs not executed or more precise queued since
midnight:
job-ID prior name user state submit/start at
queue slots ja-task-ID
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24.11.2012 21:15, Merlissimo wrote:
At 20:32 on Nov 23th sge on turnera stopped and was started at
damiana. The qmaster thread started successfully because it
responses pings and so on. But the scheduler thread seems not to
work. qconf -tsm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09.10.2012 20:57, DaB. wrote:
Hello, At Tuesday 09 October 2012 20:57:01 DaB. wrote:
A hopefully small feature request; would it be possible to have a
more detailed view added? Max 1 day (24 hours) in order to
resolve the minutes too... (...but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Intressting - my cron jobs refused to run today with...
/bin/sh: qcronsub: not found
...until you wrote this mail. Since then it looks better again.
Thanks and greetings
DrTrigon
On 11.10.2012 13:05, DaB. wrote:
Hello all,
yesterday I removed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09.10.2012 13:14, DaB. wrote:
yesterday I hacked together a munin-script for that; you can find
it at [1] for hawthorn (the current submit-host). I will add it to
clematis (the other submit-host) and maybe the other hosts too
today.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
By the way; DaB what can we TS user do to support you here in a
somewhat strategic way?
May be this is obvious and I just missed the point - but summarizing
should not be of any harm... ;)
Greetings
DrTrigon
On 26.09.2012 12:48, DaB. wrote:
Hello
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello DaB
As we discussed yesterday evening I changed minutes for my cronjobs
from 00 to 07. As I explained yesterday only 4 of 5 jobs runned, today
after the change only (!) 2 of 5 jobs runned. So this change did not
help, but made it worse... any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.09.2012 16:46, Merlissimo wrote:
btw.: This bug only exists because many people on this mailinglist
did not like the solaris crontab format and requested to install
vixie cron as alternative cron some years ago.
As far as I remember my main
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wanted to suggest Wikidata support - but it's already done! Good work!
Greetings
DrTrigon
On 05.09.2012 03:25, Sumana Harihareswara wrote:
DeltaQuad suggested I tell the bots developers on this list about
this tool, because he hadn't heard about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looks good on a first glimpse. Thanks a lot!!
On 13.09.2012 18:12, DaB. wrote:
Hello again, At Thursday 13 September 2012 18:08:55 DaB. wrote:
A word to the pywikipedia-framework users: At the moment it is
unclear if the old python-unicode-bug is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15.07.2012 14:39, DaB. wrote:
-There is -l arch=lx now which will run your task at a
linux-host. -There is also -l arch='*' that will run your task on
linux or Solaris.
...just wondering, what about running a job on NON-linux-hosts only?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To me as someone always struggling with sql queries (since I am not an
expert at all) this sound somehow promising. May be there will be a
comprehensive set of queries going to pipes one day. Then I would simply
have to pick up the pipe and connect it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for this update and all the work included!!
On 14.07.2012 16:09, DaB. wrote:
Hello all, it is finally done, the linux-login-servers (yarrow and
nightshade) are ready to use :-). You should be able to login from
the outside to these boxes
(and this is bad)
But after all at the moment it works and I just wanted to
thank you all involved here for your help and work!!
Greetings
DrTrigon
On 15.06.2012 10:57, Dr. Trigon wrote:
Hello all!
I have a bunch of cronie jobs calling qcronsub for several times
with very similar settings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.07.2012 01:18, Platonides wrote:
I stand corrected. I had only tested with the second line.
In fact it is very good thing to look at other codes and check them
BEFORE running... ;) Thanks for your work and feedback!
Greetings
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry Trigon, but it doesn't work. It is calculating the percentage
of the hard limit at which your soft limit is set. Not really what
you wanted :)
May be we do not have the same 'quota -v' output, mine is:
Disk quotas for drtrigon (uid 1340):
,
TO, msg.as_string()) server.quit()
which is invoked as follows from cron(ie)tab:
qcronsub -l h_rt=00:05:00 -l virtual_free=50M -m as -j y -b y -N
maintenance $HOME/warnuserquota.py /dev/null
may be this helps other users having the same problems/issues.
Greetings
DrTrigon
On 12.06.2012 21:39, Dr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any updates/progress here?? DaB?
On 19.06.2012 22:07, Dr. Trigon wrote:
Don't panic = no need to hurry
But I need at least a feedback; which you gave me know! Thanks for
this!
To be honest it could become a pain to get this bot running
any useful one ;)...!
Thanks a lot and greetings
DrTrigon
On 20.06.2012 02:04, Russell Blau wrote:
On Sun, Jun 17, 2012, at 02:29 PM, Dr. Trigon wrote:
So why are some of my cronie-jobs or qcronsub calls (typically 1
per day) silently dropped?
I have been having similar experiences
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When will quota system start sending warn mails? (as already requested a
few times...)
Or; under what conditions are warn mails sent? When reaching softquota?
Greetings
DrTrigon
On 22.06.2012 23:41, DaB. wrote:
Hello all,
willow was rebooted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today 2 jobs did not execute! Does this mean it is getting worse?
Is the toolserver about to die?
Greetings
DrTrigon
On 15.06.2012 10:57, Dr. Trigon wrote:
Hello all!
I have a bunch of cronie jobs calling qcronsub for several times
with very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No anwser at all? Even after this 2nd request?
Is this because nobody *can* help? Or because nobody *wants* to help??
DrTrigon
On 12.06.2012 21:31, Dr. Trigon wrote:
Hello admins!
I opened TS-1360 [1] quite some time ago. Would it be possible
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don't panic = no need to hurry
But I need at least a feedback; which you gave me know! Thanks for this!
To be honest it could become a pain to get this bot running on TS since
it has a lot of exotic (opencv) and C/C++ dependencies... So I think it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17.06.2012 00:07, Merlissimo wrote:
All jobs named subster_en were executed successfully by sge
(mostly on wolfsbane). The return code of your python script was 0,
but the runtime was only about a minute. You can check it by
executing e.g.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is it by chance your last cron entry? Remember that there must be a
newline finalising your crontab or the last command won't get
executed.
You should get this output: $ crontab -l | tail -c1 | od -c 000
\n 001
No it is not - but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For your other questions: stderr and stdout are buffered by sge
because they are send over network. At the toolserver configuration
it is send to localhost by default because all execution servers
have the same filesystems mounted. At a standard
, Marlen Caemmerer wrote:
Hello,
which one is it exactly?
Cheers nosy
On Fri, 15 Jun 2012, Dr. Trigon wrote:
Date: Fri, 15 Jun 2012 10:57:43 From: Dr. Trigon
dr.tri...@surfeu.ch Reply-To: toolserver-l@lists.wikimedia.org
To: Toolserver-l@lists.wikimedia.org Subject: [Toolserver-l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all!
I have a bunch of cronie jobs calling qcronsub for several times
with very similar settings (just the language of the wiki used
changes). In total there are 5 jobs - regurarly (about ever 2nd
day) one of those jobs does not get executed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Open a bug in https://bugzilla.wikimedia.org/ with the ops
keyword.
Done: https://bugzilla.wikimedia.org/show_bug.cgi?id=37536
Thanks for the hint!
DrTrigon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is this also supposed to solve TS-1317 [1]??
[1] https://jira.toolserver.org/browse/TS-1317
Thanks and greetings!
DrTrigon
On 16.05.2012 21:31, DaB. wrote:
Hello At Wednesday 16 May 2012 21:28:30 DaB. wrote:
There have been arrangements with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I did not open an JIRA bug because it vanished again... so; SOLVED.
But if someone is interessted in details:
http://toolserver.org/~drtrigon/DrTrigonBot/mainbot.log.2012-03-11
http://toolserver.org/~drtrigon/DrTrigonBot/mainbot.log.2012-03-12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13.03.2012 17:05, Tim Landscheidt wrote:
Even if only for PHP there would be a critical mass, it'd be still
useful to Perl, Python and other developers. For example, I think
it is a common problem to normalize links - e. g., are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is it now usual behaviour that qcronsub adds all command-line
options to following calls too?
qcronsub [some options] script.py [other options]
used to call
script.py [other options]
but now it calls
script.py [some options] script.py [other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.03.2012 01:06, Merlissimo wrote:
In both cases the old behavior was without -m a -b y, so
'cronsub [jobname] [command]' has become 'qcronsub -l h_rt=06:00:00
-l virtual_free=100M -N [jobname] [command]
'cronsub -l [jobname] [command]'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.03.2012 01:21, Platonides wrote:
On 04/03/12 00:17, Dr. Trigon wrote:
And here my key question arises; you mentioned 'qacct' to get
more info (thanks for this hint) and this is one of the biggest
problem I had with the whole SGE stuff; I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.03.2012 01:06, Merlissimo wrote:
Some weeks ago i installed a script that removes empty log files
for standard error/output stream after job execution. Many people
used this option to prevent that their homedir contain so many
empty error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.03.2012 16:25, Platonides wrote:
On 04/03/12 01:06, Merlissimo wrote:
In both cases the old behavior was without -m a -b y, so
(...)
The -b y option is mostly useful for binaries, e.g. if you don't
submit the python script itself, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yes, e.g. SGE job are not even sent to queue, they go into 'qw' directly
after starting... So my bot is down...
Greetings
DrTrigon
On 03.03.2012 05:17, Matthew Bowker wrote:
Hi, all:
The login server Willow seems to be having load issues.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That's the right thing to do. If the server is so overloaded it
can't even fork, it makes no sense for SGE to create more processes
there. They should be scheduled in some other host.
I thought SGE does itself load balance it and use another
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Meanwhile you can use
ssh drtri...@login.toolserver.org
or login to 'willow' instead of 'nightshade' directly.
And for running bots you should use SGE, e.g from
ssh drtri...@submit.toolserver.org
But recently I do also have issues with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
and the 'subster_en' does not run anymore now... can someone explain me
why??? I did not change any config or settings (as I am aware)...
...honestly ;)
Greetings
On 12.02.2012 13:45, Dr. Trigon wrote:
Hello all
I got some strange info by mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all
I got some strange info by mail tonight, first:
Unable to run job: error: no suitable queues. Exiting.
then later
Job 1601224 (subster_ar) Set in error state Exit Status = -1
Signal = unknown signal User
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Try to sleep well and focus on exams (it is an fact the same I am doing
at the moment ;) - thus; I wish you success!
Greetings
DrTrigon
ps.: Thanks for the support and service anyway!
On 09.02.2012 00:55, DaB. wrote:
Hello all,
the dumping of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
May be late - had no time - but:
HELLO 'nosy'! Nice to have a new admin here! :)
Greetings and have fun!
DrTrigon
Am 24.10.2011 23:47, schrieb DaB.:
Hello all,
how Daniel Kinzler told you in his mail of 5. October already, the
german chapter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 14.09.2011 00:08, schrieb Platonides:
Heh, you could have added - and _ to the list of allowed characters
(that's why I pointed out *what* I wanted to protect from).
Because you mentioned alphanumeric I thought of using str.isalnum()
but there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I extracted all files that are not there (there are also some i18n
differences).
bot_control.py clean_user_sandbox.py Doxyfile dtbext
dtbext/dtbext_pywikibot
dtbext/dtbext_pywikibot/dtbext_exceptions.py
dtbext/dtbext_pywikibot/__init__.py
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 12.09.2011 14:21, schrieb DaB.:
Hello, At Monday 12 September 2011 14:21:05 DaB. wrote:
/home/drtrigon/xslt/../../dab/text.xml as path, it returns an
IOError: [Errno 2] No such file or directory: ...
which is true. There is no text.xml-file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello TS users!
To close the topic [1] I finally decided to follow the hints given by
Maciej Jaros and Merlissimo and created (since it seams nobody did this
already - please correct me, if I am wrong)
XSaLT: XSL/XSLT Simple and Lightweight Tool [2]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...but I need exact the outdated pywikipedia checkout... ;))
(ok in fact it's a drtrigobot checkout which is based on
pywikipedia)
Greetings
DrTrigon
Am 05.09.2011 22:56, schrieb Platonides:
Marcin Cieslak wrote:
4.8Gsaper
now:
238.8M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all!
Just wanted to ask the short question: Do we have a tool able to convert
RSS2HTML like e.g. [1] (which needs [2]) installed on the toolserver?
Does someone operate such a tool?
Currently I am using [3] to convert RSS2HTML for dewiki. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for that!
Am 30.08.2011 20:46, schrieb DaB.:
Hello all,
today we repaired Fisheye (our viewer for Subversion). If you see
that a repository there is not updating for more then 1h, then
please (re-)open a Bugreport at JIRA.
Sincerly,
... ;)
Greetings
Dr. Trigon
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wiki.toolserver.org/view/Mailing_list_etiquette
Dr. Trigon:
Hello Everybody!
I have a question regarding FishEye and SVN. My FishEye is not updating
anymore, look at TS-1102 [1]. May be this is due the change to https
for svn? May be not... Any ideas?
The other question but not that important would be related with JIRA
and FishEye
Regardless of what login server I use, or if I try to commit files
through SSH or through Eclipse's Subversion plugin, I get this error:
Did you try manual commit with the command: 'svn ci' ? Does this works?
___
Toolserver-l mailing list
Makes sense and means I should redirect output from 'cronsub' to stdout
(or maybe stderr) to have 'cronie' make mail this to me... ;)
Greetings
Am 13.02.2011 01:33, schrieb River Tarnell:
In article 4d56a4cd.6020...@surfeu.ch,
Dr. Trigon dr.tri...@surfeu.ch wrote:
But I was wondering how SGE
First I have to thank you all very much for the numerous answers I got
to this question!! Some remarks from my side:
Am 09.02.2011 22:47, schrieb Platonides:
Ilmari Karonen wrote:
I remember being disappointed by the lack of stderr output in the mail I
got after switching my Commons MIME type
Hello all
Just a short question in [1] is mentioned how to trigger a mail in case
* the job starts
* the job finishes
what about
* the job print something to stdout like for CRON jobs (in the early
days... ;))
Thanks a lot for answering
Greetings
Dr. Trigon
[1]
https://wiki.toolserver.org
Hello all!
[Toolserver-l] Internally calling the MediaWiki API on Toolserver is
a very good idea!!
What about doing the same e.g. with the actual pywikipedia bot framework
to have some API for python script as well?
Greetings
Dr. Trigon
Am 05.02.2011 23:42, schrieb Krinkle:
Hi all,
I'm
Hello all
Has anybody ever used rrdtool on TS through python? Anyone recently?
I am trying to get this working, but I always get:
(process:26600): Pango-CRITICAL **: No modules found:
No builtin or dynamically loaded modules were found.
PangoFc will not work correctly.
This probably means
I am willing to use it... ;)
Am 23.01.2011 15:35, schrieb DaB.:
Hello,
At Sunday 23 January 2011 15:28:52 DaB. wrote:
Whatever happened to that global sitenotice file that was mentioned here:
[0]? Running a ls -l on the file indicates it's been almost 7 months
without an update. Is it still
://wiki.toolserver.org/view/Job_scheduling#Converting_a_Phoenix_tool_to_use_the_scheduler
Am 14.01.2011 10:05, schrieb Alex Brollo:
2011/1/14 Dr. Trigon dr.tri...@surfeu.ch mailto:dr.tri...@surfeu.ch
It should be (rather) simple once you got how 'crontab'/'cronjob's work.
This is my trouble. I
It should be (rather) simple once you got how 'crontab'/'cronjob's work.
Then it' simple a fact of using it - preferrably - through 'cronie' and
toghether with 'cronsub' to start the batch job...
Best is you install your crontab on 'submit.toolserver.org' as I
understood from River's last mail
You can run cronsub from the command-line for testing.
;))) easy, simple and straight forward... should be kind
of obvious... :))
Thanks a lot! ;)
- river.
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
Hello Admins!
I've created a little problem for me, I did a 'svn remove' on the wrong
directory and thus lost my bot code... :( or ;) (can't decide...)
Can you maybe give me the most recent data from backup of
.../drtrigon/pywikipeda back?!? If not I think I can restore the code
myself, but the
yet... :(
But yes, we also have backups. please open a jira ticket if you
really need this.
Thanks, will be done in an instant... Do you have an idea from which
time/date the backup is? ;)
Greetings and thanks for the fast reply!!
DrTrigon
Am 03.08.2010 15:06, schrieb Daniel Kinzler:
Dr
I have the same problem: may be your account is expired?!
Greetings
Am 04.12.2009 11:47, schrieb Andrew Dunbar:
2009/12/4 JamesRe.wikipe...@gmail.com:
My cron appears to be working fine.
Mine too.
Andrew Dunbar (hippietrail)
- James
On Fri, Dec 4, 2009 at 6:15 PM, Osama
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hallo Daniel
If you need help for 1) you can contact me, I would be glad to help you,
if needed and
wanded... ;)
Greetings!
Ursin (DrTrigon)
Daniel Kinzler schrieb:
Hi all
during wikimedia germany's brithday party yesterday, I was asked to look
100 matches
Mail list logo