Update Prowlarr v0.4.10.2111

[wkobiela]

Description

Update prowlarr - v0.4.10.2111

Checklist

• Build rule all-supported completed successfully
• New installation of package completed successfully
• Package upgrade completed successfully (Manually install the package again)
• Package functionality was tested

Type of change

• Package update

Tested on DSM7 on virtualDSM and both fresh install and upgrade works fine

[hgy59]

@wkobiela we don't create new packages for packages that use an internal updater. (SPK_VERS = $(shell date +%Y%m%d) shows that the package is not bound to a specific version, as it uses an internal updater).

Exceptions of this rule are:

• when the internal updater does not work anymore due to new dependencies
• when new archs are added that are not included in the released packages
• the DSM service integration needs an update (folders, user, port, etc.)

So my proposal for prowlarr:

• update unsupported archs (related to Framework: enhance unsupported archs handling #5383)
• update to use alternate TMP dir (related to Update Lidarr to use other TMP directory like Radarr #5081)

[wkobiela]

It seems that prowlarr is already using alternate TMP dir: https://github.com/SynoCommunity/spksrc/blame/master/spk/prowlarr/Makefile#L38

[wkobiela]

@hgy59 do I also need to add UNSUPPORTED_ARCHS line in spk/prowlarr/Makefile? I've seen it in Radarr files and also in Jellyfin

[bakerboy448]

we don't create new packages for packages that use an internal updater.

This doesn't make any sense for the *arrs.

So you're saying SynoComm policy is that the *arrs packages should never be updated? That means users will always have problems when they reinstall or uninstall and reinstall without purging existing app data.

the old versions that SynoComm provides are not compatible with the new databases and thus the apps will fail to function and users must manually purge their data which is a complicated task for some users

so are there no plans to land this PR then?

[bakerboy448]

OP - FYI PR is conflicted

[bakerboy448]

May as well update this to 0.4.7 rather than having it be an older version.
https://github.com/Prowlarr/Prowlarr/releases

[bakerboy448]

And may as well Bump to 0.4.8 as .2016 had Cardigann issues. Or just land as is and follow up with the updater rework and bump there

[hgy59]

@bakerboy448 the automatic update on service start does not work in Prowlarr (it does work in Lidarr).
I have created an issue there (Prowlarr/Prowlarr#1199)

[hgy59]

@wkobiela I did some rework. Except the automatic update after package installation or package update, everything seems to be ok.
Can you have a look at it?

[wkobiela]

On first install:

On upgrade:

After manual update inside Prowlarr:

[hgy59]

@wkobiela as we now have the latest version in the package, you cannot see any update in Powlarr.
You only see the file /var/packages/prowlarr/var/.config/Prowlarr/update_required that is not deleted as service start.

The automatic update at startup will only work, when there is a version available, that has fixed this and you manually updated to such a version (or we include the fixed version in the package).

But first we need the confirmation that this will be fixed.

[hgy59]

As Prowlarr/Prowlarr#1199 is fixed now, we only need to wait for a new release of Prowlarr.

[wkobiela]

Configured automatic update and updated package manually, still on last version

[hgy59]

@wkobiela as I explained in #5511 the automatic update will only work in the future, i.e. when you update the Version 0.4.10.2111 to a future Version.

But you can verfy that the update mechanism is working. When you install v0.4.10.2111 again (over 0.4.10.2111) and the update_required file in the config folder is gone after this "update" than it will work with future versions too.

[wkobiela]

Okay, verified and it is working as you said. Auto update mechanism looks to be working