-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net-im/synapse: add 1.87.0, correct deps in 1.85.2, drop 1.8{2..4}* #31563
Conversation
arkamar
commented
Jun 21, 2023
•
edited
edited
- New ebuild is migrated to "optimized" cargo.eclass API.
- Drop old versions
- Restrict Pillow and pydantic deps, see commit message for more info
Pull request CI reportReport generated at: 2023-06-21 07:45 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
FP with additional cleanup after recent stabilization. |
Pull request CI reportReport generated at: 2023-06-28 14:40 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Bug: https://bugs.gentoo.org/907950 Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Pillow 10 removes some deprecated constatns that are used in synapse, the issue is already fixed in upstream, see [1,2]. Moreover, synapse is incompatible with pydantic 2.0 [3]. [1] matrix-org/synapse#15873 [2] matrix-org/synapse#15876 [3] matrix-org/synapse#15858 Closes: https://bugs.gentoo.org/909644 Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Ebuild is migrated to "optimized" cargo.eclass API. Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Pull Request assignmentSubmitter: @arkamar net-im/synapse: @arkamar, @gentoo/proxy-maint Linked bugsIn order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
FP with new version and fixed rdeps for pydantic and pillow. |
Pull request CI reportReport generated at: 2023-07-05 09:45 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |