[arch-commits] Commit in matrix-synapse/trunk (PKGBUILD synapse.install)
Johannes Löthberg
demize at gemini.archlinux.org
Sat Jul 31 12:33:50 UTC 2021
Date: Saturday, July 31, 2021 @ 12:33:50
Author: demize
Revision: 991104
upgpkg: matrix-synapse 1.39.0-2
Modified:
matrix-synapse/trunk/PKGBUILD
matrix-synapse/trunk/synapse.install
-----------------+
PKGBUILD | 2 +-
synapse.install | 12 ++++++------
2 files changed, 7 insertions(+), 7 deletions(-)
Modified: PKGBUILD
===================================================================
--- PKGBUILD 2021-07-31 12:24:33 UTC (rev 991103)
+++ PKGBUILD 2021-07-31 12:33:50 UTC (rev 991104)
@@ -3,7 +3,7 @@
pkgname=matrix-synapse
pkgver=1.39.0
-pkgrel=1
+pkgrel=2
pkgdesc="Matrix reference homeserver"
url="https://github.com/matrix-org/synapse"
Modified: synapse.install
===================================================================
--- synapse.install 2021-07-31 12:24:33 UTC (rev 991103)
+++ synapse.install 2021-07-31 12:33:50 UTC (rev 991104)
@@ -47,13 +47,13 @@
if [[ "$(vercmp "$2" 1.38.0)" -lt 0 ]]; then
cat <<-EOF
- ==> Synapse 1.38.0 includes a new database schema version.
+ ==> Synapse 1.38.0 includes a database migration that re-indexes the events table.
- > This could result in increased disk I/O for several hours or days
- > after upgrading while the migration completes. Furthermore,
- > because we have to keep the old indexes until the new indexes are
- > ready, it could result in a significant, temporary, increase in
- > disk space.
+ > This could result in increased disk I/O for several hours or days
+ > after upgrading while the migration completes. Furthermore,
+ > because we have to keep the old indexes until the new indexes are
+ > ready, it could result in a significant, temporary, increase in
+ > disk space.
See https://matrix-org.github.io/synapse/develop/upgrade#upgrading-to-v1380
EOF
More information about the arch-commits
mailing list