A packaging of Zulip server for NixOS
- Nix 94.3%
- Python 5.7%
|
All checks were successful
Check workflows / lints (x86_64-linux) (pull_request) Successful in 10s
Lints / lints (x86_64-linux) (pull_request) Successful in 7s
Nixos tests / zulip-backup (x86_64-linux) (pull_request) Successful in 6m8s
Nixos tests / zulip (x86_64-linux) (pull_request) Successful in 7m0s
Nixos tests / zulip-monitoring (x86_64-linux) (pull_request) Successful in 2m37s
Nixos tests / zulip-restart (x86_64-linux) (pull_request) Successful in 3m29s
Nixos tests / zulip-tornado (x86_64-linux) (pull_request) Successful in 2m48s
I have no clue how I managed to get this wrong. |
||
|---|---|---|
| .forgejo/workflows | ||
| LICENSES | ||
| nix | ||
| .envrc | ||
| .gitignore | ||
| engage.toml | ||
| README.md | ||
| REUSE.toml | ||
| shell.nix | ||
| treefmt.toml | ||
nix-zulip
This repository packages Zulip for Nix and NixOS.
Updating
-
Bump the version in the zulip-server package and the other dependencies (you can use
nix-updatefor that) -
Check if any dependency changed from the upstream
pyproject.toml -
[Optional] Compare version requirements from
uv.lockand -
Create a new patchset using
lappverk. A typical workflow looks like (for11.2 -> 11.4update):pushd nix/packages/zulip-server lappverk checkout @/patches-11.2 lappverk init patch-series @/patches-11.4 --base 11.4 pushd $(lappverk checkout nix/packages/zulip-server/patches-11.4) git cherry-pick lappverk/base/patches-11.2..lappverk/patches-11.2 # resolve (or --skip) any conflicts that come up, as per usual... # then, once the whole series has been cherry-picked lappverk export @/patches-11.4 popd popdThis workflow is encoded in the
lappverk-start-rebase OLD_TAG NEW_TAGandlappverk-finish-rebasebash functions exported by the shell. -
Run the tests with
engage