paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-01 12:33:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove Debian 10 support.

Browse Source 
As a consequence:

• Bump minimum supported Python version to 3.8.
• Move Vagrant environment to Ubuntu 20.04, which has Python 3.8.
• Move CI frontend tests to Ubuntu 20.04.
• Move production build test to Ubuntu 20.04.
• Move 3.4 upgrade test to Ubuntu 20.04.

Signed-off-by: Anders Kaseorg <anders@zulip.com>
This commit is contained in:
Anders Kaseorg
2022-04-18 18:18:48 -07:00
committed by Alex Vandiver
parent a7e6cb7705
commit a543dcc8e3
24 changed files with 93 additions and 196 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/development/setup-advanced.md
View File

@@ -12,8 +12,8 @@ Contents:
If you'd like to install a Zulip development environment on a computer
that's running one of:
- Ubuntu 20.04 Focal
- Debian 10 Buster, 11 Bullseye
- Ubuntu 20.04
- Debian 11
- CentOS 7 (beta)
- Fedora 33 and 34 (beta)
- RHEL 7 (beta)

35
docs/development/setup-vagrant.md
View File

@@ -18,7 +18,7 @@ Contents:
- [Step 3: Start the development environment](#step-3-start-the-development-environment)
- [Step 4: Developing](#step-4-developing)
- [Troubleshooting and common errors](#troubleshooting-and-common-errors)
- [Specifying a Debian mirror](#specifying-a-debian-mirror)
- [Specifying an Ubuntu mirror](#specifying-an-ubuntu-mirror)
- [Specifying a proxy](#specifying-a-proxy)
- [Customizing CPU and RAM allocation](#customizing-cpu-and-ram-allocation)
@@ -50,7 +50,7 @@ a proxy to access the internet.)
- **All**: 2GB available RAM, Active broadband internet connection, [GitHub account][set-up-git].
- **macOS**: macOS (10.11 El Capitan or newer recommended)
- **Ubuntu LTS**: 20.04
- or **Debian**: 10 "buster" or 11 "bullseye"
- **Debian**: 11
- **Windows**: Windows 64-bit (Win 10 recommended), hardware
virtualization enabled (VT-x or AMD-V), administrator access.
@@ -143,10 +143,7 @@ Now you are ready for [Step 2: Get Zulip code](#step-2-get-zulip-code).
#### Debian
The setup for Debian is very similar to that [for Ubuntu
above](#ubuntu), except that the `docker.io` package is only available
in Debian 10 and later; for Debian 9, see [Docker CE for
Debian](https://docs.docker.com/install/linux/docker-ce/debian/).
The setup for Debian is the same as that [for Ubuntu above](#ubuntu).
#### Windows 10
@@ -285,7 +282,7 @@ vagrant up --provider=docker
The first time you run this command it will take some time because vagrant
does the following:
- downloads the base Debian 10 virtual machine image (for macOS and Windows)
- downloads the base Ubuntu 20.04 virtual machine image (for macOS and Windows)
or container (for Linux)
- configures this virtual machine/container for use with Zulip,
- creates a shared directory mapping your clone of the Zulip code inside the
@@ -324,7 +321,7 @@ $ vagrant ssh
You should see output that starts like this:
```console
Linux debian-10 4.19.0-18-amd64 #1 SMP Debian 4.19.208-1 (2021-09-29) x86_64
Welcome to Ubuntu 20.04.4 LTS (GNU/Linux 5.4.0-107-generic x86_64)
```
Congrats, you're now inside the Zulip development environment!
@@ -337,7 +334,7 @@ provisioning failed and you should look at the
Next, start the Zulip server:
```console
(zulip-py3-venv) vagrant@debian-10:/srv/zulip
(zulip-py3-venv) vagrant@vagrant:/srv/zulip
$ ./tools/run-dev.py
```
@@ -485,7 +482,7 @@ From the window where run-dev.py is running:
2016-05-04 18:33:13,330 INFO 127.0.0.1 GET 200 92ms /register/ (unauth@zulip via ?)
^C
KeyboardInterrupt
(zulip-py3-venv) vagrant@debian-10:/srv/zulip$ exit
(zulip-py3-venv) vagrant@vagrant:/srv/zulip$ exit
logout
Connection to 127.0.0.1 closed.
christie@win10 ~/zulip
@@ -523,7 +520,7 @@ christie@win10 ~/zulip
$ vagrant up
$ vagrant ssh
(zulip-py3-venv) vagrant@debian-10:/srv/zulip
(zulip-py3-venv) vagrant@vagrant:/srv/zulip
$ ./tools/run-dev.py
```
@@ -788,8 +785,8 @@ by rebooting the guest via `vagrant halt; vagrant up`.
The `vagrant up` command basically does the following:
- Downloads a Debian image and starts it using a Vagrant provider.
- Uses `vagrant ssh` to connect to that Debian guest, and then runs
- Downloads an Ubuntu image and starts it using a Vagrant provider.
- Uses `vagrant ssh` to connect to that Ubuntu guest, and then runs
`tools/provision`, which has a lot of subcommands that are
executed via Python's `subprocess` module. These errors mean that
one of those subcommands failed.
@@ -903,11 +900,11 @@ vagrant ssh -- 'sudo modinfo -F version vboxsf'
The bug has not been fixed upstream as of this writing, but you may be
able to work around it by downgrading VirtualBox Guest Additions to
6.0.4. To do this, create a `~/.zulip-vagrant-config` file and add
5.2.44. To do this, create a `~/.zulip-vagrant-config` file and add
this line:
```text
VBOXADD_VERSION 6.0.4
VBOXADD_VERSION 5.2.44
```
Then run these commands (yes, reload is needed twice):
@@ -918,18 +915,18 @@ vagrant reload
vagrant reload --provision
```
### Specifying a Debian mirror
### Specifying an Ubuntu mirror
Bringing up a development environment for the first time involves
downloading many packages from the Debian archive. The Debian cloud
images use the global mirror `http://deb.debian.org/debian` by
downloading many packages from the Ubuntu archive. The Ubuntu cloud
images use the global mirror `http://archive.ubuntu.com/ubuntu/` by
default, but you may find that you can speed up the download by using
a local mirror closer to your location. To do this, create
`~/.zulip-vagrant-config` and add a line like this, replacing the URL
as appropriate:
```text
DEBIAN_MIRROR http://ftp.us.debian.org/debian
UBUNTU_MIRROR http://us.archive.ubuntu.com/ubuntu/
```
### Specifying a proxy