-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Radarr: Update to v5.12.2.9335 #6310
Conversation
hey @hgy59, I've tried the build but it fails to run under DSM 6 from a clean install. I get in the service log:
|
@mreid-tt this fix is for all packages running under DSM < 7.2 not only for ARMv7. It is an issue for all systems running DSM 7.1 and there are evansport (i686), and some x64 models that do not get updates to DSM 7.2 DSM 7.2 has GLIBC 2.36 so the changelog should tell something like "fix for DSM < 7.2" |
@hgy59, I'll update the changelog but the solution you proposed by adding |
does it work on DSM 6 without cross/glibc? |
Yes it did previously. The log I supplied for an upgrade of the published package using the built in updater to the same version was successful. I can build a clean install to test but I don't expect the results will be different. I came across these but it's a bit beyond my expertise: |
If Radarr v5.14.0.9383 runs on DSM 6 without cross/glibc we should add glibc for DSM >= 7 only. But I doubt that it will run on DSM 7.1. If /var/packages/radarr/target/lib has any libc.* file (links and content) you might try to delete those to fix it. |
I guess my last proposal does not work and the radarr package has to be restricted to DSM 7.2. Unfortunately we do not have any chance to limit packages that use the package internal updater to limit updates to a specific version (the last version before it breaks). |
da94007
to
4cf564a
Compare
@mreid-tt and we do not have any package the needs cross/glibc* so far... So I guess it is not possible to bring your own version of glibc with a package. |
You're correct, I get a similar log when run under DSM 7.1:
I wouldn't suggest we build only for DSM 7.2 since the problem seems to only exist with ARMv7 platforms. My current course of action is working with the Radarr folks to press Microsoft to fix this upstream: dotnet/runtime#109739. Hopefully a future version of .NET will fix it and we can continue as we have done before.
If this is not fixed we can do a workaround like this:
|
7737007
to
e786aad
Compare
Description
This PR includes the following changes:
Fixes #
Checklist
all-supported
completed successfullyType of change