Bugfix/update encryption state when server change #6841
Conversation
might be that the server previously supported e2ee and e2ee folders exist so we have to fetch the info to properly handle it on client Signed-off-by: Matthieu Gallien <[email protected]>
Signed-off-by: Matthieu Gallien <[email protected]>
when we know a folder should be encrypted but encryption client side app is disabled, ignore any items in the encrypted folders Signed-off-by: Matthieu Gallien <[email protected]>
|
/backport to stable-3.12 |
|
/backport to stable-3.13 |
|
The backport to # Switch to the target branch and update it
git checkout stable-3.12
git pull origin stable-3.12
# Create the new backport branch
git checkout -b backport/6841/stable-3.12
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 284823d1 a270dca3 863256fd
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/6841/stable-3.12Error: Failed to clone repository: Failed to checkout branches: error: Your local changes to the following files would be overwritten by checkout: Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
AppImage file: nextcloud-PR-6841-863256fd5503d73c140ba91f5cd2140de9c5f713-x86_64.AppImage |
|
No description provided.