DietPi-Software | Sonarr using master branch

[Joulinar]

Hi @MichaIng

not sure if there is a reason, but it might be good to install Sonarr from master branch and not from developer.

DietPi/dietpi/dietpi-software

Line 5396 in d29a5af

Download_Install 'https://download.sonarr.tv/v2/develop/mono/NzbDrone.develop.tar.gz' /opt

DietPi/dietpi/dietpi-software

Line 5404 in d29a5af

echo 'deb https://apt.sonarr.tv/ develop main' > /etc/apt/sources.list.d/sonarr.list

Basically users will be notified within Sonarr anyway about a new version available if they install from developer branch. I found this due to the discussion on the forum https://dietpi.com/phpbb/viewtopic.php?f=11&t=7598

[MichaIng]

Not sure why we used developer once, probably it solved a particular issue. However I actually planned to migrate to Sonarr v3 anyway with the next release, as v2 is not really developed anymore and v3 works around a nasty mono bug: #3179 #3529

[MichaIng]

Okay I switched the branch for now, makes totally sense. Sonarr v3 implementation is a larger task, so better to have this merged for now: 7a4350f

[Dr0bac]

@MichaIng sonarr 3 is out from beta, they released it few days ago.

[Joulinar]

means we would need to create a migration from v2 to v3 as they are moved to apt repository now

https://sonarr.tv/#downloads-v3-linux-debian

[MichaIng]

Thanks for the hint, so this is another task for the next release. Not sure if we should force the migration or integrate it into dietpi-software to be done manually? On the other hand from all I read it should be smooth without any data/configs lost or so.

[Joulinar]

Yes running apt install sonarr will transport you into new world. Maybe we could do that via re-install possibility?

[MichaIng]

The new package install automatically removes/replaces the old package (nzbdrone) right?

Jep, the simple reinstall should be enough since Sonarr v2 is also installed via their APT repository, so with a changed repo+key+package name all previous files are cleanly replaced.

... ah, if I remember right, the database RAM link does not work anymore with Sonarr v3. So if that is active, we need to move it back to disk and disable it first. I'll run some tests about that think and see if we can fix it in the Arr_to_RAM script or need to disable it. In case, since AFAIK with Radarr v3 it was the same, only for Lidarr it's not worth to keep that script and we should then disable it on all systems and remove it cleanly.

[Joulinar]

hmm I did a small test and for me whole config was gone after upgrading to V3. As well first time update failed

sonarr.service, stopping and disabling...
Failed to mask unit: File /etc/systemd/system/sonarr.service already exists.
dpkg: error processing archive /var/cache/apt/archives/sonarr_3.0.5_all.deb (--unpack):
 new sonarr package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/sonarr_3.0.5_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

it was needed to rerun. 2nd time it was working well. However some package configuration is needed as you need to specify user/group

yes it seems nzbdrone is going to be removed

The following package was automatically installed and is no longer required:
  mediainfo
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
  nzbdrone
The following NEW packages will be installed:
  sonarr
0 upgraded, 1 newly installed, 1 to remove and 4 not upgraded.

And finally our service hardening is removed

root@DietPi4:~# systemctl cat sonarr.service
# /lib/systemd/system/sonarr.service
[Unit]
Description=Sonarr Daemon
After=network.target

[Service]
User=sonarr
Group=dietpi
UMask=002

Type=simple
ExecStart=/usr/bin/mono --debug /usr/lib/sonarr/bin/Sonarr.exe -nobrowser -data=/var/lib/sonarr
TimeoutStopSec=20
KillMode=process
Restart=on-failure

[Install]
WantedBy=multi-user.target
root@DietPi4:~#