-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
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
nextcloud: 19.0.3 -> 19.0.4, 18.0.9 -> 18.0.10 #101923
Conversation
@ofborg test nextcloud.basic nextcloud.with-postgresql-and-redis nextcloud.with-mysql-and-memcached |
Ran an update to Nextcloud 20.0.1 in production on my server: https://gitlab.com/KonradBorowski/xfix.pw/-/commit/287977e9f9957ebcec9e8067257e0b5b5a951cb4, no issues, everything works as it should. |
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.
19.0.4 update is working without issues
The 20.0.1 update is already in |
dd28223
to
7a36e41
Compare
Sure, not like it matters either way, but may as well rebase newest master. I think git would remove already merged-in commits during merge process. |
Just verified with git 2.28 that it would cause a merge conflict when using a trivial |
Motivation for this change
Getting Nextcloud to stop informing me about updates.
Please backport this to 20.09 as Nextcloud doesn't support downgrades.
20.0.1 makes dashboard load faster and fixes a deadlock: https://nextcloud.com/blog/20-0-1-is-here-with-about-60-changes-get-your-update/
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)