Qnap [ Bazarr ][ 1.1.4.0 ] companion application to Sonarr and Radarr. It manages and downloads subtitles

QoolBox a dit:
no prob, but will take few days.. QnapClub Repo is out of space and I cant upload anymore
Cris is will fix the problem in the next days
Thank you.
There is no hurry.

Regards
 
QoolBox a dit:
no prob, but will take few days.. QnapClub Repo is out of space and I cant upload anymore
Cris is will fix the problem in the next days
Hi, have you managed to fix the space issue with the repo ?

Thanks
 
Hi again and thank you for your excellent work.
Would it be possible to have an updated version?

Thanks
 
Hi, thanks again.
Version 0.8.4.1 in the Repo is actually 0.8.4.0, as you updated its internal version to accommodate for Python 3.8.1.
Am I missing something?

Regards
 
QoolBox a dit:
Many thanks!
Can you confirm that packages version is 0.8.4.1?
After updating I still get 0.8.4..
If you confirm I will do a complete reinstall.

Regards and thanks again.

 
Salut Stéphane,

j'ai "failed to install Bazarr due to data file error", même si je le télécharge en local. Qu'est ce que je dois regarder?

Merci!

giopas
 
Voilà l'erreur avec l'installation en SSH:

Code:
[~] # cd /share/Public
[/share/Public] # chmod +x QBazarr_0.8.4.2.0_x86_64.qpkg
[/share/Public] # ./QBazarr_0.8.4.2.0_x86_64.qpkg
Install QNAP package on TS-NAS...
./
./built_info
./qinstall.sh
./package_routines
./qpkg.cfg
18858+1 records in
18858+1 records out
462699237 bytes (441.3MB) copied, 11.773158 seconds, 37.5MB/s
451853+0 records in
451853+0 records out
462697472 bytes (441.3MB) copied, 11.773195 seconds, 37.5MB/s
QBazarr 0.8.4.0 is already installed. Setup will now perform package upgrading.
Firmware check is fine.
more: can't open '/var/run/qbazarr.pid': No such file or directory
Installation Abort.
[/share/Public] #

Sent from my ONEPLUS A5000 using Tapatalk

 
Voilà :

Code:
[~] # cd /share/Public
[/share/Public] # sh -x QBazarr_0.8.4.2.0_x86_64.qpkg
+ /bin/echo 'Install QNAP package on TS-NAS...'
Install QNAP package on TS-NAS...
+ /bin/grep /mnt/HDA_ROOT /proc/mounts
+ arch_ok
++ /bin/uname -m
+ local cpu_arch=x86_64
++ /sbin/getcfg '' Platform -f /etc/platform.conf
+ local reject_platform=X86_BRASWELL
++ /usr/bin/expr match X86_BRASWELL ''
+ '[' 0 == 0 ']'
++ /usr/bin/expr match x86_64 x86_64
+ '[' 6 -ne 0 ']'
+ find_base
++ /sbin/getcfg Public path -f /etc/config/smb.conf
+ HDD_MOUNT=/share/CACHEDEV1_DATA/Public
+ local 'log_tool=/sbin/log_tool -t2 -uSystem -p127.0.0.1 -mlocalhost -a'
+ '[' -e /share/CACHEDEV1_DATA/Public ']'
+ '[' -z '' ']'
+ BASE_GROUP='/share/HDA_DATA /share/HDB_DATA /share/HDC_DATA /share/HDD_DATA /share/HDE_DATA /share/HDF_DATA /share/HDG_DATA /share/HDH_DATA /share/HDI_DATA /share/HDJ_DATA /share/HDK_DATA /share/HDL_DATA /share/MD0_DATA /share/MD1_DATA /share/MD2_DATA /share/MD3_DATA'
++ /sbin/getcfg Public path -f /etc/config/smb.conf
+ publicdir=/share/CACHEDEV1_DATA/Public
+ '[' '!' -z /share/CACHEDEV1_DATA/Public ']'
+ '[' -d /share/CACHEDEV1_DATA/Public ']'
++ /bin/echo /share/CACHEDEV1_DATA/Public
++ /bin/cut -d / -f 2
+ publicdirp1=share
++ /bin/echo /share/CACHEDEV1_DATA/Public
++ /bin/cut -d / -f 3
+ publicdirp2=CACHEDEV1_DATA
++ /bin/echo /share/CACHEDEV1_DATA/Public
++ /bin/cut -d / -f 4
+ publicdirp3=Public
+ '[' '!' -z share ']'
+ '[' '!' -z CACHEDEV1_DATA ']'
+ '[' '!' -z Public ']'
+ '[' -d /share/CACHEDEV1_DATA/Public ']'
+ QPKG_BASE=/share/CACHEDEV1_DATA
+ '[' -z /share/CACHEDEV1_DATA ']'
+ '[' -z /share/CACHEDEV1_DATA ']'
+ QPKG_INSTALL_PATH=/share/CACHEDEV1_DATA/.qpkg
+ QPKG_DIR=/share/CACHEDEV1_DATA/.qpkg/
+ return 0
+ _EXTRACT_DIR=/share/CACHEDEV1_DATA/.qpkg/.tmp
+ /bin/mkdir -p /share/CACHEDEV1_DATA/.qpkg/.tmp
+ script_len=4055
+ /bin/dd if=QBazarr_0.8.4.2.0_x86_64.qpkg bs=4055 skip=1
+ /bin/tar -xO
+ /bin/tar -xzv -C /share/CACHEDEV1_DATA/.qpkg/.tmp
./
./built_info
./qinstall.sh
./package_routines
./qpkg.cfg
++ /usr/bin/expr 4055 + 20480
+ offset=24535
+ /bin/dd if=QBazarr_0.8.4.2.0_x86_64.qpkg bs=24535 skip=1
+ /bin/cat
+ /bin/dd bs=1024 count=451853 of=/share/CACHEDEV1_DATA/.qpkg/.tmp/data.tar.gz
18858+1 records in
18858+1 records out
462699237 bytes (441.3MB) copied, 15.555886 seconds, 28.4MB/s
451853+0 records in
451853+0 records out
462697472 bytes (441.3MB) copied, 15.563890 seconds, 28.4MB/s
+ '[' -f /usr/local/bin/python ']'
+ /usr/local/bin/python -c 'with open('\''/share/CACHEDEV1_DATA/.qpkg/.tmp/data.tar.gz'\'', '\''rw+'\'') as f: f.seek(462697023); f.truncate()'
++ /usr/bin/expr 24535 + 462697023
+ offset=462721558
+ cd /share/CACHEDEV1_DATA/.qpkg/.tmp
+ /bin/sh qinstall.sh
QBazarr 0.8.4.0 is already installed. Setup will now perform package upgrading.
Firmware check is fine.
more: can't open '/var/run/qbazarr.pid': No such file or directory
+ echo 'Installation Abort.'
Installation Abort.
+ /bin/rm -fr /share/CACHEDEV1_DATA/.qpkg/.tmp
+ exit 10
[/share/Public] #

Uhmmm

Sent from my ONEPLUS A5000 using Tapatalk

 
[~] # cd /share/Public
[/share/Public] # du -sk QBazarr_0.8.4.2.0_x86_64.qpkg
451888 QBazarr_0.8.4.2.0_x86_64.qpkg
[/share/Public] #
[~] # cd /share/Public
[/share/Public] # md5sum QBazarr_0.8.4.2.0_x86_64.qpkg
6df25554b89ba32ee70df6715f70d478 QBazarr_0.8.4.2.0_x86_64.qpkg
[/share/Public] #

Pour être plus précis

Sent from my ONEPLUS A5000 using Tapatalk


 
Est-ce qu'il y a une dépendance (qpkg) qu'il faut avoir? Je viens de mettre à jour QJDK8 à QJDK11, est-ce que l'erreur pourrait y être lié ? Merci!

Sent from my ONEPLUS A5000 using Tapatalk

 
I had a similar issue with a different package and only uninstall and reinstall did the trick.
I would recommend backup your data directory using SFTP.

In my case, the path is (check under BAzarr --> System --> Status:
Code:
Bazarr Config Directory:
/share/CACHEDEV1_DATA/.qpkg/QBazarr/bazarr/data

One thing I have noticed is that for Bazarr, Sonarr, Radarr and Jacket, there is only one quick access icon (shortcut) in the home page. And it is the last app installed or updated.
That is, if I have the Bazarr icon, and I update Sonarr, the icon gets replaced for Sonarr. I would like to have all of them for quick access.
It may be related to some ID in the QPackage description.

@QoolBox, could you please take a look to see if there is anything weird in the package metadata that result in such undesired behaviour?