Actually, we're working to reduce the number of custom-built packages on tool labs. In the case of wikitools, it's a pure python package, and the package can simply be pip installed in a virtualenv, so that would be the preferrable option.

The reason why we're not doing packaging anymore: I spent the last hour trying to build the new version of the python-wikitools package anyway, and it was basically a wasted hour.

• There is no v1.3 available in git; https://github.com/alexz-enwp/wikitools/commit/72a00c96e97c6d1017f607b9ebc8e1a520bd0d3e jumps from 1.2 to 1.4.
• I needed two hacks to build a package on trusty:
  • add a manual copyright file that conforms to debian specs (not the full GPLv3, refer to /usr/share/common-licenses/GPL-3, must have Copyright YYYY-ZZZZ in it
  • remove the embedded COPYING file in setup.py
• Building for precise still fails Lintian with
  • E data.tar.xz-member-without-dpkg-pre-depends
  • E bad-provided-package-name Python:any

So, basically, packaging for Ubuntu is overall a pain. If anyone else feels like building a package that works (and passes Lintian), we can deploy it, but I'm not going to spend any more time on this to work.

In T102862#1375938, @scfc wrote:

As I'm packaging this for Debian, assigning to myself.

Any updates on this?

Somewhat inadvertently, I'm using the globally installed version of wikitools on Tool Labs. It is indeed version 1.1.1:

mzmcbride@tools-bastion-03:~$ grep ^VERSION /usr/lib/python2.7/dist-packages/wikitools/wiki.py
VERSION = '1.1.1'

This is particularly problematic as the default end-point is http://en.wikipedia.org/w/api.php when it soon must be https://en.wikipedia.org/w/api.php.

In T102862#1375842, @valhallasw wrote:

• There is no v1.3 available in git; https://github.com/alexz-enwp/wikitools/commit/72a00c96e97c6d1017f607b9ebc8e1a520bd0d3e jumps from 1.2 to 1.4.

For what it's worth, PyPI has a version 1.3: https://pypi.python.org/pypi/wikitools/1.3. It installs just fine.

I started a new task related to this topic: T176109.