From: Michael Rohleder <mike@rohleder.de>
To: Zacchaeus Scheffer <zaccysc@gmail.com>
Cc: 56373@debbugs.gnu.org
Subject: bug#56373: Updating synapse (Matrix Homeserver) Because it is Broken
Date: Sun, 28 Aug 2022 05:24:04 +0200 [thread overview]
Message-ID: <8735dh125n.fsf@rohleder.de> (raw)
In-Reply-To: <CAJejy7mSpZ4Ba1rQA35FxCyM++7fn4=ZWbNRit8gSBN4Cwy=3w@mail.gmail.com> (Zacchaeus Scheffer's message of "Sun, 3 Jul 2022 18:15:30 -0400")
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Hi Zacchaeus!
Thanks for the report!
I think, synapse 1.30.1 changed the dependency of python-cryptography to
a newer version (which we currently have as python-cryptography-next).
But also python-pyopenssl and python-pysaml2 needs to be build with
cryptography-next [1] (or they fail in a byte2int() or similar at runtime
somewhere).
So we also need some more -next python packages to upgrade synapse from
1.29.
matrix-common is needed from version >=1.50.
Footnotes:
[1] http://www.rohleder.de/gitweb/?p=guix.git;a=blob;f=mroh/guix/packages/python.scm;h=13ce4e8dd9822f443633385af6203fef78e198aa;hb=HEAD#l79
--
There are two ways of constructing a software design.
One is to make it so simple that there are obviously no deficiencies;
the other is to make it so complicated that there are no obvious deficiencies.
The first method is far more difficult.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
prev parent reply other threads:[~2022-08-28 3:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 22:15 bug#56373: Updating synapse (Matrix Homeserver) Because it is Broken Zacchaeus Scheffer
2022-08-28 3:24 ` Michael Rohleder [this message]
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=8735dh125n.fsf@rohleder.de \
--to=mike@rohleder.de \
--cc=56373@debbugs.gnu.org \
--cc=zaccysc@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.