Improve: SABnzbd installation on Debian

[thezoggy]

URL: /wiki/installation/install-debian.html

Improvement:

spun up debian vm,

added deb http://deb.debian.org/debian bookworm-backports main contrib non-free to sources, but:

$ sudo apt install -t bookworm-backports sabnzbdplus
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sabnzbdplus : Depends: unrar but it is not installable or
                        rar but it is not installable
               Recommends: gir1.2-xapp-1.0 but it is not going to be installed
               Recommends: libavahi-compat-libdnssd1 but it is not going to be installed
               Recommends: python3-notify2 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

To get sab to actually installed I had to make all the sources have:
main contrib non-free non-free-firmware

We might be able to make this more noob friendly be doing:
sudo apt-add-repository contrib non-free

However, while this does get sab going it does come with outdated par2 and unrar get installed:

$ par2 -V
par2cmdline version 0.8.1

But at least we have:
https://sabnzbd.org/wiki/installation/par2cmdline-turbo

which can basically do in one glorified line:

$ par2 -V
par2cmdline version 0.8.1


PAR2TURBO=$(wget -qO- https://api.github.com/repos/animetosho/par2cmdline-turbo/releases/latest | grep tag_name | cut -d '"' -f4) && cd /tmp && wget -O par2turbo.zip "https://github.com/animetosho/par2cmdline-turbo/releases/download/${PAR2TURBO}/par2cmdline-turbo-${PAR2TURBO#v}-linux-amd64.zip" && unzip par2turbo.zip && sudo install -v -m755 par2 /usr/bin

$ par2 -V
par2cmdline-turbo version 1.3.0

Unrar pretty old, but will at least be on 7.x on trixie..

$ unrar -V

UNRAR 6.21 freeware      Copyright (c) 1993-2023 Alexander Roshal

With unrar should be easy for most to just grab from site and replace existing, at the time of this writing unrar 7.12:

mkdir /tmp/unrar
wget -O /tmp/unrar.tar.gz "https://www.rarlab.com/rar/rarlinux-x64-712.tar.gz"
tar xf /tmp/unrar.tar.gz -C /tmp/unrar --strip-components=1
cd /tmp/unrar
sudo install -v -m755 unrar /usr/bin

example:

debian:/tmp/unrar$ sudo install -v -m755 unrar /usr/bin
removed '/usr/bin/unrar'
'unrar' -> '/usr/bin/unrar'

debian:/tmp/unrar$ unrar |head

UNRAR 7.12 freeware      Copyright (c) 1993-2025 Alexander Roshal

[thezoggy]

unrelated to our docs but was looking at stuff as Trixie is about to come out this week (and then the whole libssl3 issue).

libssl3 on older debian (12 and older) while on debian 13 you now use libssl3t64

The reason for the different package name is part of the Debian project to transition to 64-bit time_t, which is required to fix the Year 2038 problem.

looks like new apt 3.0 is going to have stuff to help deal with transition so should be less of a thing for users to even worry about:
https://blog.jak-linux.org/2024/05/14/solver3/

[Safihre]

Why do you expect the name to be a problem? For sabctools?
There we use the one Python provides so it's dynamic.

[thezoggy]

Why do you expect the name to be a problem? For sabctools?
There we use the one Python provides so it's dynamic.

This would have nothing to do with sabctools, the package name change would be more for ppa. I was just noting the finding since I was talking to someone about the libssl3 issue as they just upgraded proxmox 9 (which uses Debian 13) and had him check what version of libssl3 it came with and discovered that there is no libssl3 but now libssl3t64 and then went looking at why there was a new name.