mirror of
https://github.com/zulip/zulip.git
synced 2026-06-12 21:00:58 +08:00
8ae167dc05
Installs which are upgrading to current `main`, and are upgrading for the very first time from an install which was originally from git, have a `/home/zulip/deployments/current` which, unlike all later upgrades, is not a `git worktree` of `/srv/zulip.git`, but rather a direct `git clone` of some arbitrary URL. As such, it does not have an `upstream` remote, nor a cached `zulip-git-version` file. This makes later attempts to determine the pre-upgrade revision of git (for pre-deploy hooks) fail, as without a `zulip-git-version` file, `ZULIP_VERSION` is insufficiently-specific (e.g. `6.1+git`), and there is no guarantee the necessary tags exist either. While we can make fresh git installs set up an `upstream` and run `./tools/cache-zulip-git-version` going forward (see subsequent commit), that does not address the issue for deploys which already exist. For those, we must configure and fetch a `remote` in the old checkout, followed by re-generating a cached `zulip-git-version`. Fixes: #25076. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| build-pgroonga | ||
| check_rabbitmq_queue.py | ||
| check-database-compatibility | ||
| clean_emoji_cache.py | ||
| clean_node_cache.py | ||
| clean_unused_caches.py | ||
| clean_venv_cache.py | ||
| create-production-venv | ||
| email-mirror-postfix | ||
| fix-standalone-certbot | ||
| hash_reqs.py | ||
| install | ||
| install-node | ||
| node_cache.py | ||
| puppet_cache.py | ||
| pythonrc.py | ||
| queue_workers.py | ||
| setup_path.py | ||
| setup_venv.py | ||
| setup-apt-repo | ||
| setup-yum-repo | ||
| sharding.py | ||
| supervisor.py | ||
| unpack-zulip | ||
| update-git-upstream | ||
| upgrade-zulip | ||
| upgrade-zulip-from-git | ||
| upgrade-zulip-stage-2 | ||
| warn-rabbitmq-nodename-change | ||
| zulip_tools.py | ||