Hello,
I am currently unable to provide the amount of work required for fully maintaining matrix-synapse. Could somebody please help with getting Synapse’s latest version to build on F44 and below?
Thank you Kai
I'll take a look.
-- Gwyn Ciesla she/her/hers ------------------------------------------------ in your fear, seek only peace in your fear, seek only love -d. bowie
Sent with Proton Mail secure email.
On Monday, May 18th, 2026 at 5:04 AM, Kai A. Hiller fedora@kaialexhiller.de wrote:
Hello,
I am currently unable to provide the amount of work required for fully maintaining matrix-synapse. Could somebody please help with getting Synapse’s latest version to build on F44 and below?
Thank you Kai -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
On Tue, May 19, 2026 at 05:20:41PM +0000, Gwyn Ciesla via devel wrote:
I'll take a look.
I'm happy to help too, but the last time I looked it was not at all easy. There's a lot of python/rust interaction and upstream aggressively pinning to specific versions (and needing them)... ;(
kevin
On Tue, May 19, 2026 at 8:01 PM Kevin Fenzi kevin@scrye.com wrote:
On Tue, May 19, 2026 at 05:20:41PM +0000, Gwyn Ciesla via devel wrote:
I'll take a look.
I'm happy to help too, but the last time I looked it was not at all easy. There's a lot of python/rust interaction and upstream aggressively pinning to specific versions (and needing them)... ;(
If there's anything I can do to help with the Rust dependencies, let me know. All of matrix-synapse's Rust dependencies (that are already in Fedora) should be in good shape, but I don't know if there's any missing updates or missing new dependencies.
Fabio
On 5/19/26 1:01 PM, Kevin Fenzi wrote:
On Tue, May 19, 2026 at 05:20:41PM +0000, Gwyn Ciesla via devel wrote:
I'll take a look.
I'm happy to help too, but the last time I looked it was not at all easy. There's a lot of python/rust interaction and upstream aggressively pinning to specific versions (and needing them)... ;(
We do have tooling now in the pyproject macros to make it easier to relax overly aggressive upstream dependency constraints, but yeah, the dep pinning and python + rust combination definitely does complicate things.
I contributed to this package as part of the Pydantic v2 Change I worked on, and the upstream was pretty friendly, so maybe they'd be willing to accept changes to make this easier to package, dependency pinning less aggressive, etc.
This is the current batch of pins causing failures after I refactored the pyo3 patch:
DEBUG util.py:461: Problem 1: nothing provides requested (crate(pyo3-log/default) >= 0.13.3 with crate(pyo3-log/default) < 0.14.0~) DEBUG util.py:461: Problem 2: nothing provides requested (crate(pythonize/arbitrary_precision) >= 0.28.0 with crate(pythonize/arbitrary_precision) < 0.29.0~) DEBUG util.py:461: Problem 3: nothing provides requested (crate(pythonize/default) >= 0.28.0 with crate(pythonize/default) < 0.29.0~)
-- Gwyn Ciesla she/her/hers ------------------------------------------------ in your fear, seek only peace in your fear, seek only love -d. bowie
Sent with Proton Mail secure email.
On Tuesday, May 19th, 2026 at 1:07 PM, Maxwell G maxwell@gtmx.me wrote:
On 5/19/26 1:01 PM, Kevin Fenzi wrote:
On Tue, May 19, 2026 at 05:20:41PM +0000, Gwyn Ciesla via devel wrote:
I'll take a look.
I'm happy to help too, but the last time I looked it was not at all easy. There's a lot of python/rust interaction and upstream aggressively pinning to specific versions (and needing them)... ;(
We do have tooling now in the pyproject macros to make it easier to relax overly aggressive upstream dependency constraints, but yeah, the dep pinning and python + rust combination definitely does complicate things.
I contributed to this package as part of the Pydantic v2 Change I worked on, and the upstream was pretty friendly, so maybe they'd be willing to accept changes to make this easier to package, dependency pinning less aggressive, etc. -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
I just submitted PRs to update both "pyo3-log" and "pythonize" to their latest versions.
"pyo3-log" requires only a patch version update.
"pythonize" was a leaf package (no other package depends on it).
Am 19.05.26 um 8:26 PM schrieb Gwyn Ciesla via devel:
This is the current batch of pins causing failures after I refactored the pyo3 patch:
DEBUG util.py:461: Problem 1: nothing provides requested (crate(pyo3-log/default) >= 0.13.3 with crate(pyo3-log/default) < 0.14.0~) DEBUG util.py:461: Problem 2: nothing provides requested (crate(pythonize/arbitrary_precision) >= 0.28.0 with crate(pythonize/arbitrary_precision) < 0.29.0~) DEBUG util.py:461: Problem 3: nothing provides requested (crate(pythonize/default) >= 0.28.0 with crate(pythonize/default) < 0.29.0~)
-- Gwyn Ciesla she/her/hers
in your fear, seek only peace in your fear, seek only love -d. bowie
Sent with Proton Mail secure email.
On Tuesday, May 19th, 2026 at 1:07 PM, Maxwell G maxwell@gtmx.me wrote:
On 5/19/26 1:01 PM, Kevin Fenzi wrote:
On Tue, May 19, 2026 at 05:20:41PM +0000, Gwyn Ciesla via devel wrote:
I'll take a look.
I'm happy to help too, but the last time I looked it was not at all easy. There's a lot of python/rust interaction and upstream aggressively pinning to specific versions (and needing them)... ;(
We do have tooling now in the pyproject macros to make it easier to relax overly aggressive upstream dependency constraints, but yeah, the dep pinning and python + rust combination definitely does complicate things.
I contributed to this package as part of the Pydantic v2 Change I worked on, and the upstream was pretty friendly, so maybe they'd be willing to accept changes to make this easier to package, dependency pinning less aggressive, etc. -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new