From: freshprince <freshprince@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: synapse 1.49.0 update deleted my productive server config
Date: Wed, 22 Dec 2021 11:05:00 +0100 [thread overview]
Message-ID: <20211222100500.epXLWKo49P12OSKS6GyjadxCZYhVNQ2JJZ3C5d3HpVQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34657@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]
New comment by freshprince on void-packages repository
https://github.com/void-linux/void-packages/issues/34657#issuecomment-999447082
Comment:
```
# cat /etc/synapse/homeserver.yaml
feoofdsofjsod
# xbps-install -R. -u synapse
Name Action Version New version Download size
synapse update 1.48.0_1 1.49.0_1 -
Size required on disk: 6889KB
Space available on disk: 6535MB
Do you want to continue? [Y/n]
[*] Verifying package integrity
synapse-1.49.0_1: verifying SHA256 hash...
[*] Collecting package files
synapse-1.49.0_1: collecting files...
synapse-1.48.0_1: collecting files...
[*] Unpacking packages
synapse-1.48.0_1: updating to 1.49.0_1 ...
Removing byte-compiled python3.10 code for module synapse...
Removing byte-compiled python3.10 code for module synmark...
Updating ldconfig(8) cache...
synapse-1.49.0_1: unpacking ...
synapse-1.49.0_1: file `./etc/sv/synapse/run' won't be extracted, it's preserved.
[*] Configuring unpacked packages
synapse-1.49.0_1: configuring ...
Updated synapse system user.
Byte-compiling python3.10 code for module synapse...
Byte-compiling python3.10 code for module synmark...
Updating ldconfig(8) cache...
synapse-1.49.0_1: updated successfully.
0 downloaded, 0 installed, 1 updated, 1 configured, 0 removed.
# head /etc/synapse/homeserver.yaml
# This file is maintained as an up-to-date snapshot of the default
# homeserver.yaml configuration generated by Synapse.
#
# It is intended to act as a reference for the default configuration,
# helping admins keep track of new options and other changes, and compare
# their configs with the current default. As such, many of the actual
# config values shown are placeholders.
#
# It is *not* intended to be copied and used as the basis for a real
# homeserver.yaml. Instead, if you are starting from scratch, please generate
```
next prev parent reply other threads:[~2021-12-22 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 9:47 [ISSUE] " freshprince
2021-12-22 9:51 ` paper42
2021-12-22 9:51 ` paper42
2021-12-22 9:53 ` freshprince
2021-12-22 9:55 ` paper42
2021-12-22 10:05 ` freshprince [this message]
2021-12-22 10:26 ` ArsenArsen
2021-12-22 10:40 ` freshprince
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211222100500.epXLWKo49P12OSKS6GyjadxCZYhVNQ2JJZ3C5d3HpVQ@z \
--to=freshprince@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).