-
Notifications
You must be signed in to change notification settings - Fork 42
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
Testing : v1.59.0 #297
Testing : v1.59.0 #297
Conversation
!testme |
This comment was marked as outdated.
This comment was marked as outdated.
How is it going? |
!testme |
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM ¯\_(ツ)_/¯
(would be nice if somebody has time to take care of the linter warnings / recommendations at some point)
tested and approved |
!testme |
This comment was marked as outdated.
This comment was marked as outdated.
Upgraded from stable (1.47) ok. |
!testme |
This is fixed in 1.15.1, and 1.15.2 is out o/ |
!testme |
time to pull into the main branch! |
Upgrade synapse to 1.55.2 ok for me on Debian 10, x64. Thanks! |
I asked the question because I'm not sure that synapse is able to send correctly email actually. Normally synapse need to be authenticated to postfix to be able to send correctly the email |
Actually synapse as no email server config https://github.com/YunoHost-Apps/synapse_ynh/blob/testing/conf/homeserver.yaml#L1260-1268 Maybe it should be tested in another PR. For this PR with v 1.56 we might use this setting |
This reverts commit 5cf7d0f.
!testme |
Anything one could do to help with this? Not sure where to start, but if someone would point me I might try to help. Willing to wait, just wondering what kind of blocker it is... |
Let's bump it straight to 1.58.1 #308 ? |
Hi everyone, this PR was opened a long time ago, to upgrade synapse version. Since then many versions were released, this PR updated, but we did not merge to master. So actually the version provided by the app catalog is quite old. Would be it possible to merge this PR, and to open new PR per version, so that we could be more agile and have more often releases. (I know that at some points, the version provided by this PR was not stable enough to be merged, but I think we are good to go now). |
The issue here is upstream disabling open registrations. Is anyone using that feature in yunohost anyway? We could check if registrations are open at upgrade-time (at the very beginning), and abort if they are, while displaying a message to the users, and directing them to a wiki page or something. |
I thought the issue about open registrations was addressed in this commit 398d97b, wasn't it? |
We need to tackle the issues raised by the latest CI test with the backups first. |
@tituspijean so I looked at the logs but I'm not sure, what the actual problem is. I haven't been packaging apps yet though I intend to start on it.
Now I'm not sure, which of those are just warnings or irrelevant. Or a symptom of different problem. |
As there is this PR to update to v1.59, #310 , is there any reason to keep this PR open? |
Yes there is, this is the testing branch and will be merged to master. V1.59 -> testing -> master |
You might as well want to pull https://github.com/matrix-org/synapse/releases/tag/v1.59.1, which is supposed to only have a minor fix for a long-standing issue. |
Let's merge as the app is broken since a long time... |
Problem
PR Status
Automatic tests
Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)