# TODO: Use packaged composer once Debian's #934104 is fixed. && git clone --depth 1 https://gerrit.wikimedia.org/r/integration/composer.git /srv/composer \
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934104 is fixed, but in 1.9.1, which isn't in debian stable
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Switch runner to bullseye, Python 3.9 and npm 7 | labs/libraryupgrader | master | +707 -1 K |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | hashar | T249949 Stop using integration/composer and then archive the repo | |||
| Resolved | Legoktm | T249525 Use packaged composer |
Debian provides:
| Stretch | 1.2.2 |
| Buster | 1.8.4 |
| testing | 1.10.5 |
| unstable | 1.10.5 |
We can fork import their 1.10.5 packaging and rebuild it for Stretch / Buster then upload that to apt.wikimedia.org.
I wonder if we need to bother now that we did T249464: Replace integration/composer with a composer.phar in CI usage
We do since integration/composer has to be phased out but is still used by other applications outside of CI :]
My plan right now is just to wait until the bullseye release and switch to the packaged version then. If we want to get rid of integration/composer sooner, we could look into switching to the phar.
For more fun and games... Buster (testing) now has composer 2.0 - https://packages.debian.org/bullseye/composer
Unstalling since Bullseye got released and come with composer 2.0.9. That should let us migrate toolforge and ext dist
Change 758105 had a related patch set uploaded (by Legoktm; author: Legoktm):
[labs/libraryupgrader@master] [WIP] Switch runner to bullseye, Python 3.9 and npm 7
Change 758105 merged by jenkins-bot:
[labs/libraryupgrader@master] Switch runner to bullseye, Python 3.9 and npm 7