Development and Production support for Debian's `Bullseye`.
See original GitHub issueThe release of Debian’s newer version Bullseye is about to take place in 3 months or so. It is certain we should extend Zulip’s development and production environments to support Bullseye as well (considering that this is the first platform with python 3.9).
Related chat.zulip.org chat: https://chat.zulip.org/#narrow/stream/49-development-help/topic/Dev.20setup.20on.20Manjaro/near/1146056
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Debian -- Software Packages in "bullseye", Subsection devel
Software Packages in "bullseye", Subsection devel ... (2.35.2-2): GNU binary utilities that support multi-arch targets (BFD development files) ...
Read more >Debian 11 "bullseye" released
After 2 years, 1 month, and 9 days of development, the Debian project is proud to present its new stable version 11 (code...
Read more >DebianReleases - Debian Wiki
Debian is under continual development. The latest release is Debian 11.6. It is also (currently) known as stable or by its codename "Bullseye"....
Read more >Debian -- Details of package dpkg-dev in bullseye
This package provides the development tools (including dpkg-source) required to unpack, build and upload Debian source packages.
Read more >Debian -- Software Packages in "bullseye", Subsection web
acmetool (0.2.1-4+b5): automatic certificate acquisition tool for Let's Encrypt ; adminer (4.7.9-2): Web-based database administration tool ; akregator (4:20.08.3 ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thanks for flagging!
We should remember to backport the documentation change to 4.x as well. We’re planning to do a 4.6 release in the next week, so it’d be good to address this there.
(I think Bullseye wasn’t frozen enough to have
/etc/os-releasebe final at the time we merged the above; we should have been able to do this documentation change as soon as that happened, though).Yeah, I’ll open a PR soon.