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.
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
Update Sonarr to v3 #3803
Update Sonarr to v3 #3803
Changes from 3 commits
bfe06df
1f9cd66
0881fc8
ce1f414
190a81f
4d88fa9
6a22d1e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I propose to use
Sonarr
as package nameOnce we have to do the breaking change, why not now?
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.
When I looked into doing this previously there were some major issues that I didn't find an easy resolution for (at the time).
If I remember correctly a couple of the issues as a result of making this change were:
Perhaps there were more issues, I can't remember. However, I think this would be kind of nice to have if someone wants to make all of the above work. I don't know if another package has gone through this process before and might already have some of this scripting added to a package upgrade/rename. Another option is to make this a separate v3 package and force users to manually upgrade/migrate.
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.
Let's please not make this complicated just for a name that a regular users wouldn't see!
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.
That's what we decided last time and I agree
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.
I have to look at the documentation but in DSM7 there is a way to replace a package wich is exactly what we need to address these issues. We just need to wait until it's released
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.
Also agree that for this PR we should leave it as is. It's not worth to work on until DSM7 is released