-
-
Notifications
You must be signed in to change notification settings - Fork 14.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
[23.11] nextcloud29: init at 29.0.0, nextcloud28: 28.0.4 -> 28.0.5, nextcloud27: 27.1.8 -> 27.1.9 #308261
Conversation
ChangeLog: https://nextcloud.com/changelog/#27-1-9 (cherry picked from commit 5a3bc43)
ChangeLog: https://nextcloud.com/changelog/#28-0-5 (cherry picked from commit acd2192)
Signed-off-by: Raito Bezarius <[email protected]> (cherry picked from commit 3ebf8d0)
Seems to fix the phonetrack issue. (cherry picked from commit f082e0d)
I'm a bit surprised to see NC 29 in the backport. Is that normal procedure for nixpkgs? |
It gives people a longer window to upgrade. |
Check-cherry-picks "failure" understandable. |
This seems to solve the problem with the warning about carddav/caldav redirects being broken.
@risicle yeah only a portion is reasonable to backport. Do you prefer to remove the 'cherry picked from'-part of the commit? |
No I think it's fine. I have a PR #305628 to suppress hard-failures on warnings, but it has some issues of its own due to github jankiness. |
Which nixpkgs rev? |
So I've just checked the data dir and it was indeed owned by my user instead of nextcloud, chown-ing the entire thing to nextcloud fixed it. |
Description of changes
Backport of #306595 minus breaking changes.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.