Package apertium-apy package from upstream:
- apertium-apy: 0.11.4 -> 0.11.5
- Debian
Testing:
- Local and in Labs
Production deployment:
- Deployment
This will also fix, https://github.com/wikimedia/operations-debs-contenttranslation-apertium-apy/pull/1
Package apertium-apy package from upstream:
Testing:
Production deployment:
This will also fix, https://github.com/wikimedia/operations-debs-contenttranslation-apertium-apy/pull/1
Project | Branch | Lines +/- | Subject | |
---|---|---|---|---|
operations/debs/contenttranslation/apertium-apy | master | +116 -4 | apertium-apy: New upstream release |
Change 554849 had a related patch set uploaded (by KartikMistry; owner: KartikMistry):
[operations/debs/contenttranslation/apertium-apy@master] apertium-apy: New upstream release
CI still failing at: https://integration.wikimedia.org/ci/job/debian-glue/1632/console
14:43:01 File "setup.py", line 6, in <module> 14:43:01 from apertium_apy import apy 14:43:01 File "/build/apertium-apy-0.11.5/apertium_apy/apy.py", line 29, in <module> 14:43:01 from tornado.locks import Semaphore 14:43:01 ImportError: No module named 'tornado.locks'
Probably we need to backport python3-tornado to apt.wikimedia.org @akosiaris
Doubtful we can or want to do that. The goal is for full Jessie removal by April 1st (not a joke!). We should instead probably invest time into moving apertium to the pipeline.
Change 554849 abandoned by KartikMistry:
apertium-apy: New upstream release
Reason:
Not possible to build on Jessie.
@KartikMistry: Hi, the Due Date set for this open task is more than a month ago.
Can you please either update or reset the Due Date (by clicking ), or set the status of this task to resolved in case this task is done? Thanks.