Hello,
This is a reminder that Debian Bullseye will reach the end of its Long Term Support (LTS) on August 31, 2026[0]
If your Cloud VPS project still has instances running Debian Bullseye, now is the time to migrate them to **Debian Bookworm or Debian Trixie**.
We have published a migration guide to help with the process.[1]
As part of this migration, it may also be worth evaluating whether your workload is a good fit for Toolforge.
If feasible, migrating to Toolforge can reduce future maintenance burden, as operating system upgrades are much simpler.
Our goal is to complete these migrations before Bullseye reaches end of support. After the upstream LTS deadline,
Bullseye instances may become subject to shutdown or cleanup as part of the deprecation process.
If you are unable to complete your migration before August 31, or need assistance, please let us know as soon as possible.
In addition to replying on this mailing list or contacting the Tools Platform team[2], please file a Phabricator task
tagged **Cloud-VPS (Debian Bullseye Deprecation[3])** so we can track your project and work with you on a migration plan.
[0]: https://phabricator.wikimedia.org/T401804
[1]: https://wikitech.wikimedia.org/wiki/Help:Cloud_VPS_instance_operating_system...
[2]: https://wikitech.wikimedia.org/wiki/Help:Cloud_VPS#Communication_and_support
[3]: https://phabricator.wikimedia.org/project/view/8107/
Thanks!
Hello,
Following up on the Debian Bullseye migration reminder, below is the current list of Cloud VPS projects that still have instances running on Bullseye:
account-creation-assistance bub2 capacity-exchange cvn deployment-prep devtools discourse dumps etytree extdist fastcci foundationmemory iiab imagebulk incubator integration isa maps matrix mwcli ocrtoy onfire reading-web-staging signwriting spi-tools statanalyser swift text-to-speech teyora tools utrs webperf wikidocumentaries wikifunctions wildcat wmcs-uptime
If you recognize any of these projects, please help us reach the project maintainers or anyone else who may be able to help with the migration. In particular, if you know that a project is no longer actively maintained, any additional context would also be helpful.
As a reminder, Debian Bullseye reaches the end of its Long Term Support (LTS) on August 31, 2026.
If you maintain one of these projects and don't expect to complete the migration by the deadline, please reach out to us and file a Phabricator task tagged *Cloud-VPS (Debian Bullseye Deprecation)* so that we know the project's status and can coordinate with you.
Please find the Migration guide here[0].
Current Bullseye deprecation report[1].
Thank you to everyone who has already migrated or helped other project maintainers with their migrations.
[0]: https://wikitech.wikimedia.org/wiki/Help:Cloud_VPS_instance_operating_system... [1]: https://os-deprecation.toolforge.org/
On Thu, Aug 6, 2026 at 10:03 PM Seyram Komla Sapaty ssapaty@wikimedia.org wrote:
Hello,
This is a reminder that Debian Bullseye will reach the end of its Long Term Support (LTS) on August 31, 2026[0]
If your Cloud VPS project still has instances running Debian Bullseye, now is the time to migrate them to **Debian Bookworm or Debian Trixie**.
We have published a migration guide to help with the process.[1]
As part of this migration, it may also be worth evaluating whether your workload is a good fit for Toolforge.
If feasible, migrating to Toolforge can reduce future maintenance burden, as operating system upgrades are much simpler.
Our goal is to complete these migrations before Bullseye reaches end of support. After the upstream LTS deadline,
Bullseye instances may become subject to shutdown or cleanup as part of the deprecation process.
If you are unable to complete your migration before August 31, or need assistance, please let us know as soon as possible.
In addition to replying on this mailing list or contacting the Tools Platform team[2], please file a Phabricator task
tagged **Cloud-VPS (Debian Bullseye Deprecation[3])** so we can track your project and work with you on a migration plan.
Thanks!
Seyram Komla Sapaty Developer Advocate Wikimedia Cloud Services
_______________________________________________ Cloud-announce mailing list -- cloud-announce@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.o...
iiab has a bullseye instance that is shut down. are we required to delete it?
On Mon, Aug 17, 2026 at 4:07 PM Seyram Komla Sapaty via Cloud-announce via Cloud cloud@lists.wikimedia.org wrote:
Hello,
Following up on the Debian Bullseye migration reminder, below is the current list of Cloud VPS projects that still have instances running on Bullseye:
account-creation-assistance bub2 capacity-exchange cvn deployment-prep devtools discourse dumps etytree extdist fastcci foundationmemory iiab imagebulk incubator integration isa maps matrix mwcli ocrtoy onfire reading-web-staging signwriting spi-tools statanalyser swift text-to-speech teyora tools utrs webperf wikidocumentaries wikifunctions wildcat wmcs-uptime
If you recognize any of these projects, please help us reach the project maintainers or anyone else who may be able to help with the migration. In particular, if you know that a project is no longer actively maintained, any additional context would also be helpful.
As a reminder, Debian Bullseye reaches the end of its Long Term Support (LTS) on August 31, 2026.
If you maintain one of these projects and don't expect to complete the migration by the deadline, please reach out to us and file a Phabricator task tagged *Cloud-VPS (Debian Bullseye Deprecation)* so that we know the project's status and can coordinate with you.
Please find the Migration guide here[0].
Current Bullseye deprecation report[1].
Thank you to everyone who has already migrated or helped other project maintainers with their migrations.
On Thu, Aug 6, 2026 at 10:03 PM Seyram Komla Sapaty ssapaty@wikimedia.org wrote:
Hello,
This is a reminder that Debian Bullseye will reach the end of its Long Term Support (LTS) on August 31, 2026[0]
If your Cloud VPS project still has instances running Debian Bullseye, now is the time to migrate them to **Debian Bookworm or Debian Trixie**.
We have published a migration guide to help with the process.[1]
As part of this migration, it may also be worth evaluating whether your workload is a good fit for Toolforge.
If feasible, migrating to Toolforge can reduce future maintenance burden, as operating system upgrades are much simpler.
Our goal is to complete these migrations before Bullseye reaches end of support. After the upstream LTS deadline,
Bullseye instances may become subject to shutdown or cleanup as part of the deprecation process.
If you are unable to complete your migration before August 31, or need assistance, please let us know as soon as possible.
In addition to replying on this mailing list or contacting the Tools Platform team[2], please file a Phabricator task
tagged **Cloud-VPS (Debian Bullseye Deprecation[3])** so we can track your project and work with you on a migration plan.
Thanks!
Seyram Komla Sapaty Developer Advocate Wikimedia Cloud Services
Cloud-announce mailing list -- cloud-announce@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.o... _______________________________________________ Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
It's still showing on the tracker: https://os-deprecation.toolforge.org/
I will manually update the sheet we are using to track this.
Thanks!
On Mon, Aug 17, 2026 at 3:51 PM Tim Moody via Cloud < cloud@lists.wikimedia.org> wrote:
iiab has a bullseye instance that is shut down. are we required to delete it?
On Mon, Aug 17, 2026 at 4:07 PM Seyram Komla Sapaty via Cloud-announce via Cloud cloud@lists.wikimedia.org wrote:
Hello,
Following up on the Debian Bullseye migration reminder, below is the current list of Cloud VPS projects that still have instances running on Bullseye:
account-creation-assistance bub2 capacity-exchange cvn deployment-prep devtools discourse dumps etytree extdist fastcci foundationmemory iiab imagebulk incubator integration isa maps matrix mwcli ocrtoy onfire reading-web-staging signwriting spi-tools statanalyser swift text-to-speech teyora tools utrs webperf wikidocumentaries wikifunctions wildcat wmcs-uptime
If you recognize any of these projects, please help us reach the project maintainers or anyone else who may be able to help with the migration. In particular, if you know that a project is no longer actively maintained, any additional context would also be helpful.
As a reminder, Debian Bullseye reaches the end of its Long Term Support (LTS) on August 31, 2026.
If you maintain one of these projects and don't expect to complete the migration by the deadline, please reach out to us and file a Phabricator task tagged *Cloud-VPS (Debian Bullseye Deprecation)* so that we know the project's status and can coordinate with you.
Please find the Migration guide here[0].
Current Bullseye deprecation report[1].
Thank you to everyone who has already migrated or helped other project maintainers with their migrations.
On Thu, Aug 6, 2026 at 10:03 PM Seyram Komla Sapaty < ssapaty@wikimedia.org> wrote:
Hello,
This is a reminder that Debian Bullseye will reach the end of its Long Term Support (LTS) on August 31, 2026[0]
If your Cloud VPS project still has instances running Debian Bullseye, now is the time to migrate them to **Debian Bookworm or Debian Trixie**.
We have published a migration guide to help with the process.[1]
As part of this migration, it may also be worth evaluating whether your workload is a good fit for Toolforge.
If feasible, migrating to Toolforge can reduce future maintenance burden, as operating system upgrades are much simpler.
Our goal is to complete these migrations before Bullseye reaches end of support. After the upstream LTS deadline,
Bullseye instances may become subject to shutdown or cleanup as part of the deprecation process.
If you are unable to complete your migration before August 31, or need assistance, please let us know as soon as possible.
In addition to replying on this mailing list or contacting the Tools Platform team[2], please file a Phabricator task
tagged **Cloud-VPS (Debian Bullseye Deprecation[3])** so we can track your project and work with you on a migration plan.
Thanks!
Seyram Komla Sapaty Developer Advocate Wikimedia Cloud Services
Cloud-announce mailing list -- cloud-announce@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.o... _______________________________________________ Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
On Mon, 17 Aug 2026, Seyram Komla Sapaty via Cloud-announce via Cloud wrote:
maps
Working on those. I have noticed that the current debian-13.0-trixie image
https://horizon.wikimedia.org/ngdetails/OS::Glance::Image/09ac7914-8b26-41c2...
produces a system with an "accton" service installed and failing. Not a very nice thing when systemctl status reports failures on a brand new instance.
Can we have the "accton" package removed?
To keep the image size consistent, can we have "ed" installed? (Not a joke, I use it a lot).
Thank you, Marcin User:Saper
On Tue, 18 Aug 2026 at 21:58, Marcin Cieslak via Cloud cloud@lists.wikimedia.org wrote:
On Mon, 17 Aug 2026, Seyram Komla Sapaty via Cloud-announce via Cloud wrote:
maps
Working on those. I have noticed that the current debian-13.0-trixie image
https://horizon.wikimedia.org/ngdetails/OS::Glance::Image/09ac7914-8b26-41c2...
produces a system with an "accton" service installed and failing. Not a very nice thing when systemctl status reports failures on a brand new instance.
Can we have the "accton" package removed?
The issue with the service has been fixed instead. Thank you for the poke relating to that.
To keep the image size consistent, can we have "ed" installed? (Not a joke, I use it a lot).
You can install ed on the instances you are using. My first instict would be that these days ed is niche enough to not warrant inclusion in the base images, unfortunately.
Not having ed available by default seems like a mistake. I don't use it often, but when I do use it, it's because things have gotten into such a bad state that I can't get emacs to run. And when you get to that state, that's not when you want to be futzing with trying to install something. The added cost of having it there all the time is trivial.
On Aug 19, 2026, at 8:40 AM, Taavi Väänänen via Cloud cloud@lists.wikimedia.org wrote:
You can install ed on the instances you are using. My first instict would be that these days ed is niche enough to not warrant inclusion in the base images, unfortunately.