[Labs-l] List of packages that are supported by tool labs

Wed Nov 13 15:45:27 UTC 2013

On 11/12/13 5:34 PM, Alex Brollo wrote:
>
> Done: https://bugzilla.wikimedia.org/show_bug.cgi?id=56972
>
> You can't imagine how much I hate this kind of burocracy. Djvulibre is
> needed for djvu files management; djvu  files are absolutely needed for
> wikisource works; some busy and basic bot is working daily (IMHO) from
> Toolserver using that package, that has been simply forgotten while
> migrating from Toolserver into Labs (IMHO); I'm alerting you about this
> issue.... why is it not largely sufficient to go and install it (if my alert
> is right)?

"Going and installing it" correctly is more complicated than just
logging in and typing "sudo apt-get install djvulibre": it needs to be
added to that exec_environ list mentioned earlier in the email thread
so it gets installed on all the current and future exec nodes. And the
people who can take care of that from start to end (I'm not one of
them, BTW) aren't available constantly. Filing the bug means the
request is there when they have the opportunity, while just asking on
the mailing list or in IRC is liable to be missed or forgotten.

On Tue, Nov 12, 2013 at 9:43 PM, Andrew Bogott <abogott at wikimedia.org> wrote:
> We're generally pleased to accept puppet patches from volunteers.  The
> tool-labs equivalent of DIY is to submit a puppet patch that installs your
> package -- Coren and I try to be quick about reviewing such things.

I note that Coren has said in the past[1] that he has so many Gerrit
changes assigned to him for review that it's easy to miss them, while
bugs don't get missed so easily. So submitting a bug along with the
patch is a good idea.

 [1]: http://bots.wmflabs.org/~wm-bot/logs/%23wikimedia-labs/20131107.txt,
at around 15:17.

On Wed, Nov 13, 2013 at 3:44 AM, Merlijn van Deen <valhallasw at arctus.nl> wrote:
> It's not about puppet, it's about the response 'please jump through these
> hoops to get it done' instead of 'You're supposed to jump through these
> hoops, so I've done it for you this time', or (even better) 'It's done, and
> I have created a bug as reference'.

OTOH, the proverb "Give a man a fish and he eats for a day, teach a
man to fish and he eats for a lifetime" applies, even more so when
everyone can benefit from the mailing list post. That and I don't know
anything about djvulibre, so if any questions came up about it in the
bug I'd be unable to answer them.

> Sending a 'create a bug in this
> component' link to a mailing list is roughly as much work as just creating
> the bug directly...

Not really. Especially when I just copied the link from elsewhere.