[QPKG] sherpa mini-package-manager (CLI)

[OneCD]

I had a Python3 qpkg (for some dependency I've forgotten about) -- ditched it.
Reinstalled Entware
Reinstalled OM and MY

Resolved. Groovy.

Good work!

I've just added a check for other installed Python3 packages to sherpa so we can identify this a bit sooner: https://github.com/OneCDOnly/sherpa/com ... 0a97cabc6c

[HermanW]

Hello OneCD,

Again great respect for the support you give to all members using sherpa. Recently I obtained a TS-832X to replace my old TS-859 and busy to tranfer most of the things. I installed sherpa again and tried to install SickChill and SABnzbd but without luck. Below you see the output of my session and I will try again with the debug option and provide the link: https://termbin.com/a9vw

Also I copied the backups (SABnzbd, SickChill and nzbToMedia) from the old NAS and placed them in the folder (manually created) Download. Would be nice if I can use them to get the config like it was before.

Hopefully you can help me with this.

Output first try to install apps:

Code: Select all

[~] # sherpa
sherpa 210122 • a mini-package-manager for QNAP NAS

Usage: sherpa [action] [multi-packages] [options]

   To list available [action]s, type:
      # sherpa list actions

   To list available [multi-packages], type:
      # sherpa list packages

   Or, for more [options], type:
      # sherpa list options

There's also the wiki: https://github.com/OneCDOnly/sherpa/wiki

[~] # sherpa install sickchill
sherpa 210122 • a mini-package-manager for QNAP NAS

proc: validating parameters ... /share/CACHEDEV1_DATA/.qpkg/sherpa/cache/sherpa.                                                                                                                                                             manager.sh: line 1404: ▒-▒': /share/CACHEDEV1_DATA/qpkg/sherpa/cache/sherpamanag                                                                                                                                                             ersh: line 1404: python3: command not found: syntax error: operand expected (err                                                                                                                                                             or token is "/share/CACHEDEV1_DATA/qpkg/sherpa/cache/sherpamanagersh: line 1404:                                                                                                                                                              python3: command not found")
done: updated cache with 2 QPKGs OK
done: installed essential IPKGs
done: installed 1 essential QPKG OK
done: downloaded & installed 58 IPKGs OK                                                                                                                                                                                                     eror: Download & install 'Python3' modules failed ! resultcode: [1]
done: downloaded & installed PIPs OK
done: installed 1 optional QPKG OK

[~] # sherpa install SABnzbd
sherpa 210122 • a mini-package-manager for QNAP NAS

done: updated cache with 3 QPKGs OK
done: installed 1 essential QPKG OK
done: downloaded & installed 23 IPKGs OK
eror: Download & install 'Python3' modules failed ! resultcode: [1]
done: downloaded & installed PIPs OK
done: installed 1 optional QPKG OK

[~] #

[OneCD]

Also I copied the backups (SABnzbd, SickChill and nzbToMedia) from the old NAS and placed them in the folder (manually created) Download. Would be nice if I can use them to get the config like it was before.

No problem, can do. Unfortunately, it's the end of my day here, so I'll need to continue this in the morning.

Let's see if we can work-out what went wrong during the PIP module install.

Please post the contents of the module installation log:

Code: Select all

cat $(getcfg sherpa Install_Path -f /etc/config/qpkg.conf)/logs/py3-modules.assorted.install.log

[HermanW]

I understand with the different timezones we are in, already happy you want to help.

Output module installation log:

Code: Select all

[~] # cat $(getcfg sherpa Install_Path -f /etc/config/qpkg.conf)/logs/py3-modules.assorted.install.log
= command: '/opt/bin/pip3 install apprise apscheduler beautifulsoup4 cfscrape cheetah3 cheroot!=8.4.4 cherrypy configobj feedparser portend pygithub python-levenshtein python-magic random_user_agent sabyenc3 simplejson slugify --disable-pip-version-check --cache-dir /share/CACHEDEV1_DATA/.qpkg/sherpa/cache/pips'
! resultcode: [1] ***** stdout/stderr begins below *****
Collecting apprise
  Downloading apprise-0.9.0-py2.py3-none-any.whl (950 kB)
Collecting apscheduler
  Downloading APScheduler-3.7.0-py2.py3-none-any.whl (59 kB)
Collecting beautifulsoup4
  Downloading beautifulsoup4-4.9.3-py3-none-any.whl (115 kB)
Collecting cfscrape
  Downloading cfscrape-2.1.1-py3-none-any.whl (12 kB)
Collecting cheetah3
  Downloading Cheetah3-3.2.6.tar.gz (295 kB)
Collecting cheroot!=8.4.4
  Downloading cheroot-8.5.2-py2.py3-none-any.whl (97 kB)
Collecting cherrypy
  Downloading CherryPy-18.6.0-py2.py3-none-any.whl (419 kB)
Collecting configobj
  Downloading configobj-5.0.6.tar.gz (33 kB)
Requirement already satisfied: feedparser in /share/CACHEDEV1_DATA/.qpkg/Entware/lib/python3.9/site-packages (6.0.2)
Collecting portend
  Downloading portend-2.7.0-py3-none-any.whl (5.3 kB)
Collecting pygithub
  Downloading PyGithub-1.54.1-py3-none-any.whl (289 kB)
Collecting python-levenshtein
  Downloading python-Levenshtein-0.12.1.tar.gz (50 kB)
Collecting python-magic
  Downloading python_magic-0.4.18-py2.py3-none-any.whl (8.6 kB)
Collecting random_user_agent
  Downloading random_user_agent-1.0.1-py3-none-any.whl (8.2 MB)
Requirement already satisfied: sabyenc3 in /share/CACHEDEV1_DATA/.qpkg/Entware/lib/python3.9/site-packages (4.0.2)
Collecting simplejson
  Downloading simplejson-3.17.2.tar.gz (83 kB)
Collecting slugify
  Downloading slugify-0.0.1.tar.gz (1.2 kB)
Collecting markdown
  Downloading Markdown-3.3.3-py3-none-any.whl (96 kB)
Collecting requests-oauthlib
  Downloading requests_oauthlib-1.3.0-py2.py3-none-any.whl (23 kB)
Requirement already satisfied: six in /share/CACHEDEV1_DATA/.qpkg/Entware/lib/python3.9/site-packages (from apprise) (1.15.0)
Collecting requests
  Downloading requests-2.25.1-py2.py3-none-any.whl (61 kB)
Collecting click>=5.0
  Downloading click-7.1.2-py2.py3-none-any.whl (82 kB)
Collecting PyYAML
  Downloading PyYAML-5.4.1.tar.gz (175 kB)
ERROR: Could not install packages due to an EnvironmentError: [Errno 28] No space left on device
= ***** stdout/stderr is complete *****

[HermanW]

Hello OneCD,

I have great news, just restarted the NAS and tried to install again and it went fine. After some investigation I moved/copied the old backup files to /share/CACHEDEV1_DATA/.qpkg_config_backup and tried to restore the config with success (some minor adjustments needed in config).

In the end my issue is fixed, no need help from you and keep up the good work with sherpa

[OneCD]

Code: Select all

ERROR: Could not install packages due to an EnvironmentError: [Errno 28] No space left on device

That's something for me to investigate.

I have great news, just restarted the NAS and tried to install again and it went fine. After some investigation I moved/copied the old backup files to /share/CACHEDEV1_DATA/.qpkg_config_backup and tried to restore the config with success (some minor adjustments needed in config).

Good work!

[OneCD]

After some investigation I moved/copied the old backup files to /share/CACHEDEV1_DATA/.qpkg_config_backup and tried to restore the config with success (some minor adjustments needed in config).

I've added a new operation to sherpa to assist with this. After you've copied the original backup files across and placed them in the correct location on the new NAS, this operation takes care of everything else:

Code: Select all

sherpa rebuild all

This examines the backup file list, automatically installs the QPKG associated with each backup (along with all dependencies like Entware, Par2, etc... ), then restores the configuration into each newly installed package. So, there's no-need to install each application first.

Too-late to help you, but it may help the next person.

[HermanW]

Too-late to help you, but it may help the next person.

No problem, I am glad it was fixed and sherpa gets more and more improved by sharing user experience. Just one question left, I couldn't find a list of commands/actions with sherpa because there was a moment I was not sure about "backup all" or "backup-all". Of course the help function of sherpa (once I am at the command prompt) is great.

Again keep on going, hopefully one day you can add (again) something for movies because the development of SickChill doesn't go fast as planned I guess.

[OneCD]

No problem, I am glad it was fixed and sherpa gets more and more improved by sharing user experience.

Just one question left, I couldn't find a list of commands/actions with sherpa because there was a moment I was not sure about "backup all" or "backup-all". Of course the help function of sherpa (once I am at the command prompt) is great.

Yes, you can see the possible action syntaxes with:

Code: Select all

sherpa help actions

... and sherpa will also keep an eye-out for a few previously acceptable commands (like 'backup-all') and advise on the current usage.

Again keep on going, hopefully one day you can add (again) something for movies because the development of SickChill doesn't go fast as planned I guess.

Agree. I'm hoping the Watcher devs will be able to make Watcher3 compatible with Python 3.9.0.

[Shadytree]

Hi OneCd,
I now have my shiny new NAS up and running and will be looking to replicate my current setup for it to run side-by-side for a while rather than do a straight migration of everything across.
So rather than backing up SHERPA and its apps and copying over, I'll be looking to do a fresh install of Sherpa and apps on the new NAS.
When I tried earlier, The QNAP Club install came up with a 'There is no digital signature error' on all the installs? Is the Club still having issues?
Next question was, if running two NAS side by side for a while, is it best to assign different ports to the two versions of SHERPA apps ?

[quassum]

Agree. I'm hoping the Watcher devs will be able to make Watcher3 compatible with Python 3.9.0.

Well, barbequesauce did just add a "research required" tag to this Watcher issue:
https://github.com/barbequesauce/Watcher3/issues/185

So fingers crossed.

[OneCD]

I now have my shiny new NAS up and running ...

When I tried earlier, The QNAP Club install came up with a 'There is no digital signature error' on all the installs? Is the Club still having issues?

I think so. You'll need to contact the QnapClub repo admin.

Next question was, if running two NAS side by side for a while, is it best to assign different ports to the two versions of SHERPA apps ?

This isn't necessary. Each NAS can use the same port numbers.

[OneCD]

Well, barbequesauce did just add a "research required" tag to this Watcher issue:
https://github.com/barbequesauce/Watcher3/issues/185

So fingers crossed.

[Shadytree]

I now have my shiny new NAS up and running ...

I just ran a quick buffer test. 4k 2160p film on the old TS569L, which buffered after 1 or 2 seconds, the dies. The new one, CPU didn't exceed 10% and Memory 15% smooth as silk.
!! MIND BLOWN (as well as my wallet) !!

Next question was, if running two NAS side by side for a while, is it best to assign different ports to the two versions of SHERPA apps ?

This isn't necessary. Each NAS can use the same port numbers.

That's cool. So just changing each apps route directories will be enough.

Does the no digital signal error , effect the apps performance at all. Just wondered as the Sherpa version from Club has it as well.

[OneCD]

Does the no digital signal error , effect the apps performance at all. Just wondered as the Sherpa version from Club has it as well.

Nope. As long as you've allowed unsigned apps to run on your new NAS, they'll work just fine.

QnapClub haven't signed the sherpa QPKG. No big deal, it will continue to work without a signature.

I'm still waiting (and have a support ticket open since September 2019) for QNAP to advise how they want "developers" to sign their QPKGs.