Correct permissions of Sonarr/Radarr backup upon upgrade #3190
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@ymartin59 I think the release of just Sonarr/Radarr is creating problems. Because SABnzbd/NZBGet/Deluge are not updated they still create files as
sabnzbd:users
and the new Sonarr/Radarr packages are no longer part ofusers
. I think this is the source of the problems described in #3185 . Now that you published Sonarr/Radarr, we need the downloaders to be updated ASAP.. ⏩⏩And it also means that also other processors like Sickrage/CouchPotato also need updates right away! This whole switch needs to happen at once, we can't do it one package at a time 😨
Regarding this upgrade problem:
While I first thought that removing these files would be an option, I now see that the Sonarr/Radarr Wiki actually refer to this
/tmp/
location as a valid source of recent backups. I inspected the backup and update process and these are the only folders created.Checklist
all-supported
completed successfully