Skip to content
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

[stable23] updateEncryptedVersion: cleanup on target if cache already got renamed #30695

Merged
merged 1 commit into from
Jan 15, 2022

Conversation

backportbot-nextcloud[bot]
Copy link

backport of #30631

When moving a file to trash with encryption enabled, the cache gets
moved before the actual file. According to @icewind1991 this is in order
to not break object storage.

When moving a file from an unencrypted storage (e.g. a collectives
storage) to the encrypted trashbin storage, this causes errors, see

This commit fixes it by doing `updateEncryptedVersion()` on the target
cache entry *if* the source cache entry doesn't exist anymore, but the
corresponding target cache entry does exist already.

Fixes: #26544

Signed-off-by: Jonas Meurer <jonas@freesources.org>
@MichaIng MichaIng merged commit 9f7c05c into stable23 Jan 15, 2022
@MichaIng MichaIng deleted the backport/30631/stable23 branch January 15, 2022 01:48
@blizzz blizzz mentioned this pull request Jan 17, 2022
This was referenced Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants