Probably, all we need to do is make sure that our target machines have python3.4 installed. Our existing wheels are incompatible with python 3.5, which is the default python3 on stretch.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Bumps models and requirements for conversion to Debian Stretch. | mediawiki/services/ores/deploy | master | +5 -6 |
Event Timeline
I'm reconsidering my proposal to use python3.4. It's only available by adding jessie as an apt source, and causes some annoying dependency fu such as downgrading findutils and maybe other packages.
Slightly more sane plan "B" is that we rebuild the wheels to support both python3.4 and python3.5.
Change 404886 had a related patch set uploaded (by Halfak; owner: halfak):
[mediawiki/services/ores/deploy@master] Bumps models and requirements for conversion to Debian Stretch.
ORES is currently deployed in cloud VPS on Stretch machines. This is not an issue of ORES compatibility but rather a misunderstand about which branch to deploy from.
What about T184072 and T184135 which are direct subtasks of this task referring very specifically to stretch compatibility and are still open ? One would have expected those to be closed *before* this task is closed.
FWIW, the stretch_conversion branch had never been checked out on tin, nor have I seen any reference to it in any task/docs. I think that the misunderstanding was just waiting to happen.
Change 404886 abandoned by Awight:
Bumps models and requirements for conversion to Debian Stretch.
Reason:
Different patch was applied to the stretch_conversion branch, we'll merge back when finished migrating.