Page MenuHomePhabricator

Add python3.8 to buster-wikimedia pyall component
Open, Needs TriagePublic

Description

https://tools.wmflabs.org/apt-browser/stretch-wikimedia/component/pyall/

@faidon, could you add Python 3.8 so we can begin using it in CI?

Event Timeline

Legoktm created this task.Dec 20 2019, 1:19 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 20 2019, 1:19 AM
  • The canonical location is nowadays https://people.debian.org/~paravoid/python-all/ (which I maintain on my free time). We (Wikimedia) probably should set up a reprepro import for that.
  • The above repository has 3.8.0 beta4 for buster, I'll need to update that for a more recent version (currently looks like 3.8.1). I can do so soon-ish.
  • That said, I don't have any intentions to backport 3.8 to stretch.

I've updated the aforementioned apt repository with 3.8.1-2~buster1 packages Someone in SRE that's more familiar with how we do things these days (maybe @MoritzMuehlenhoff?) can update our reprepro to include that.

(As I said above, the cost/benefit tradeoff for a stretch backport is not one that makes the endeavour worth it IMHO, so I have no intentions of working on that right now)

I've updated the aforementioned apt repository with 3.8.1-2~buster1 packages Someone in SRE that's more familiar with how we do things these days (maybe @MoritzMuehlenhoff?) can update our reprepro to include that.

Ack, I'll take care of that.

(As I said above, the cost/benefit tradeoff for a stretch backport is not one that makes the endeavour worth it IMHO, so I have no intentions of working on that right now)

Could not agree more :-)

Legoktm renamed this task from Package python3.8 for stretch-wikimedia pyall component to Add python3.8 to buster-wikimedia pyall component.Feb 3 2020, 8:58 AM
  • That said, I don't have any intentions to backport 3.8 to stretch.

Seems reasonable. Retitled the task accordingly. For CI purposes if someone wants to run tests against 3.4 & 3.8 we can just use both stretch and buster.

I've updated the aforementioned apt repository with 3.8.1-2~buster1 packages Someone in SRE that's more familiar with how we do things these days (maybe @MoritzMuehlenhoff?) can update our reprepro to include that.

Ack, I'll take care of that.

Anything I/CI team can help with?

If it's not straightfoward, can we just add the python-all repo directly into the CI images, given the maintainer is extremely trusted? :)