| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| toolforge: remove pinning from the services node | operations/puppet | production | +0 -1 |
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T360699 Toolsbeta: migrate to Debian Bullseye or later | |||
| Resolved | taavi | T311897 [infra] Toolforge: migrate to Debian Bullseye or later | |||
| Resolved | dcaro | T311914 Upgrade Toolforge apt repository (tools-services hosts) to Debian Bullseye or later |
Event Timeline
I think that would be a big change and we don't have much leeway before having to upgrade.
I would be curious also about the process, as a first look seems to make it way more complicated and way less flexible (ex. there would be no easy way to test ad-hoc changes). Might be more interesting to try to go the "single binary installation" way we have been discussing for ages, and provide just that instead of packages + repository.
Change #1055976 had a related patch set uploaded (by David Caro; author: David Caro):
[operations/puppet@production] toolforge: add pinning versions for bookworm
VM up and running, and apt pulling correctly:
dcaro@tools-bastion-12:~$ sudo apt update Hit:1 http://mirrors.wikimedia.org/debian bookworm-backports InRelease Hit:2 http://mirrors.wikimedia.org/debian bookworm InRelease Hit:3 http://mirrors.wikimedia.org/debian bookworm-updates InRelease Hit:4 http://mirrors.wikimedia.org/osbpo bookworm-bobcat-backports-nochange InRelease Hit:5 http://mirrors.wikimedia.org/osbpo bookworm-bobcat-backports InRelease Hit:6 http://apt.wikimedia.org/wikimedia bookworm-wikimedia InRelease Ign:7 http://tools-services-06.tools.eqiad1.wikimedia.cloud/repo bookworm-tools InRelease Hit:8 http://tools-services-06.tools.eqiad1.wikimedia.cloud/repo bookworm-tools Release Ign:9 http://tools-services-06.tools.eqiad1.wikimedia.cloud/repo bookworm-tools Release.gpg Hit:10 http://deb.debian.org/debian-debug bookworm-debug InRelease Hit:11 http://security.debian.org/debian-security bookworm-security InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date.
Change #1055976 merged by David Caro:
[operations/puppet@production] toolforge: remove pinning from the services node
I had to restore the packages from the snapshot for some reason, now all of them are there on the right versions. Tested by uninstalling/installing a few of them.