[QPKG] sherpa: a mini-package-manager (CLI) beta

This is the best place for community developers to publish their genius work. Your Apps enrich the QNAP Turbo NAS.
Post Reply
User avatar
OneCD
Guru
Posts: 12155
Joined: Sun Aug 21, 2016 10:48 am
Location: "... there, behind that sofa!"

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

Post by OneCD »

Shadytree wrote: Tue Jan 12, 2021 4:19 am :) On a completely separate note, just pulled the trigger on a 48TB TVS-872XT-32GB 'Beast' with 1GB NVMe SSD for caching. Happy but now poor !
Nice! Should keep you going for the next 10 years. Image
Shadytree wrote: Tue Jan 12, 2021 4:19 am OneCd, will be asking for a refresh on how to do a completely fresh install soon ;)
No worries, easy-to-do with the backup systems in place. :)

ImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImage
User avatar
dirkonline
Easy as a breeze
Posts: 305
Joined: Mon Oct 18, 2010 4:08 pm

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

Post by dirkonline »

Cheers! I just saw this in my log in Medusa, is this a general issue?

Code: Select all

2021-01-17 13:47:12 WARNING  CHECKVERSION :: [698ca1d] "/opt/bin/git" branch master --set-upstream-to origin/master returned : error: could not lock config file .git/config: File exists
error: Unable to write upstream branch configuration
hint: 
hint: After fixing the error cause you may try to fix up
hint: the remote tracking information by invoking
hint: "git branch --set-upstream-to=origin/master".. Treat as error for now
User avatar
OneCD
Guru
Posts: 12155
Joined: Sun Aug 21, 2016 10:48 am
Location: "... there, behind that sofa!"

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

Post by OneCD »

Hey Dirk. :)

It looks like a temporary lockfile error when checking the current Medusa version. Meh, it happens. Medusa may have already set a lockfile for another reason when the version check was started. And the version check appears to want to force-set the upstream branch. A bit odd, but OK.

You can ignore it, or ask the devs about it by creating a new issue on their GitHub repo: https://github.com/pymedusa/Medusa/issues

ImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImage
User avatar
dirkonline
Easy as a breeze
Posts: 305
Joined: Mon Oct 18, 2010 4:08 pm

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

Post by dirkonline »

Thanks for the evaluation. OneCD :) for some reason I assumed this was something local. I’ll check back later this week and if it persists I’ll open an issue and ask.
rdeliege
New here
Posts: 2
Joined: Tue Jan 25, 2011 4:29 am

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

Post by rdeliege »

I upgraded my SABnzbd via Sherpa from 3.1.0 to 3.1.1 and it's not working now:

Code: Select all

ERROR 19/01/2021 15:31 Essential modules are missing, downloading cannot start.
ERROR 19/01/2021 15:31 par2 binary... NOT found!
ERROR 19/01/2021 15:31 [N/A] The command in build_command is undefined.
Trying to update everything via Sherpa results in:

Code: Select all

[/share/Public] # sherpa  check all
sherpa 210110 ÔÇó a mini-package-manager for QNAP NAS

done: updated cache with 2 QPKGs OK
fail: Unable to install 'Par2' (see log for more details)
fail: Installed 1 essential QPKG failed
done: downloaded & installed PIPs OK
done: restarted 1 optional QPKG OK
Logs are here: https://termbin.com/37pj

I'm using a QNAP TS-219 PII
rs1001
Getting the hang of things
Posts: 72
Joined: Thu Jun 18, 2015 11:44 am

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

Post by rs1001 »

Having a little trouble with Mylar, won't startup.

start daemon: failed!
= ExecuteAndLog()
output: "Traceback (most recent call last):
File "/share/CACHEDEV1_DATA/.qpkg/Mylar3/Mylar3/Mylar.py", line 28, in <module>
from mylar import webstart, logger, filechecker, versioncheck, maintenance
File "/share/CACHEDEV1_DATA/.qpkg/Mylar3/Mylar3/mylar/webstart.py", line 26, in <module>
from mylar.webserve import WebInterface
File "/share/CACHEDEV1_DATA/.qpkg/Mylar3/Mylar3/mylar/webserve.py", line 30, in <module>
from mako.template import Template
ModuleNotFoundError: No module named 'mako'"
result: [1]
QNAP TS-653 Pro -- with 16Gb RAM
6 * Western Digital WD60EFRX WD Reds (RAID5) as a Single 27.1TB Volume
Firmware: QTS 5.0.1.2277
User avatar
OneCD
Guru
Posts: 12155
Joined: Sun Aug 21, 2016 10:48 am
Location: "... there, behind that sofa!"

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

Post by OneCD »

Hi and welcome to the forum. :)
rdeliege wrote: Tue Jan 19, 2021 10:44 pm

Code: Select all

fail: Unable to install 'Par2' (see log for more details)
This should be fixed now. Can you please clean your current sherpa cache:

Code: Select all

sherpa clean
... then check all packages again?

Code: Select all

sherpa check all
rdeliege wrote: Tue Jan 19, 2021 10:44 pm I'm using a QNAP TS-219 PII
This old unit is now EOL and no-longer supported by QNAP. Might be time for an upgrade? I can highly recommend the TS-230 as a cheap and capable replacement. ;)

ImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImage
User avatar
OneCD
Guru
Posts: 12155
Joined: Sun Aug 21, 2016 10:48 am
Location: "... there, behind that sofa!"

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

Post by OneCD »

rs1001 wrote: Wed Jan 20, 2021 4:43 am Having a little trouble with Mylar, won't startup.
Hmm, can you please try re-cloning Mylar from GitHub? This should do the trick:

Code: Select all

/etc/init.d/mylar3.sh clean
Your settings will be retained.

ImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImage
rdeliege
New here
Posts: 2
Joined: Tue Jan 25, 2011 4:29 am

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

Post by rdeliege »

This should be fixed now. Can you please clean your current sherpa cache:
... then check all packages again?
OneCD, it's working again! Thanks so much for the quick support!

However, Sherpa status still shows Par2 as not installed, so what has been changed now?
User avatar
dirkonline
Easy as a breeze
Posts: 305
Joined: Mon Oct 18, 2010 4:08 pm

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

Post by dirkonline »

dirkonline wrote: Tue Jan 19, 2021 3:14 pm Thanks for the evaluation. OneCD :) for some reason I assumed this was something local. I’ll check back later this week and if it persists I’ll open an issue and ask.
I opened an issue

https://github.com/pymedusa/Medusa/issues/9052

And it will be fixed in the next release.
rs1001
Getting the hang of things
Posts: 72
Joined: Thu Jun 18, 2015 11:44 am

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

Post by rs1001 »

No luck yet.

[~] # /etc/init.d/mylar3.sh clean
daemon: NOT active
clean local repository: OK

SUCCESS -- I think.

[~] # /etc/init.d/mylar3.sh clean
daemon: NOT active
clean local repository: failed!
= ExecuteAndLog()
output: "rm: can't remove '/share/CACHEDEV1_DATA/.qpkg/Mylar3/Mylar3': No such file or directory"
result: [1]

MY TRYING TOO HARD :-P

[~] # sherpa start my
sherpa 210110 • a mini-package-manager for QNAP NAS

done: updated cache with 2 QPKGs OK

[~] # sherpa restart my
sherpa 210110 • a mini-package-manager for QNAP NAS

done: updated cache with 2 QPKGs OK

No access though.
QNAP TS-653 Pro -- with 16Gb RAM
6 * Western Digital WD60EFRX WD Reds (RAID5) as a Single 27.1TB Volume
Firmware: QTS 5.0.1.2277
User avatar
OneCD
Guru
Posts: 12155
Joined: Sun Aug 21, 2016 10:48 am
Location: "... there, behind that sofa!"

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

Post by OneCD »

rdeliege wrote: Wed Jan 20, 2021 6:16 pm OneCD, it's working again! Thanks so much for the quick support!
No worries. :)
rdeliege wrote: Wed Jan 20, 2021 6:16 pm However, Sherpa status still shows Par2 as not installed, so what has been changed now?
Yup, that's OK. There isn't a Par2 QPKG to suit your model NAS, so instead sherpa installs the 'par2cmdline' IPKG via Entware. This allows SABnzbd to launch correctly and to perform repairs on downloads. It's not as fast as the one in the Par2 QPKG, but it's all we have. It also means you won't see a distinct Par2 QPKG in your App Center (or via sherpa). ;)

ImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImage
User avatar
OneCD
Guru
Posts: 12155
Joined: Sun Aug 21, 2016 10:48 am
Location: "... there, behind that sofa!"

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

Post by OneCD »

dirkonline wrote: Thu Jan 21, 2021 1:22 am And it will be fixed in the next release.
Good work. :geek:

ImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImage
User avatar
OneCD
Guru
Posts: 12155
Joined: Sun Aug 21, 2016 10:48 am
Location: "... there, behind that sofa!"

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

Post by OneCD »

rs1001 wrote: Thu Jan 21, 2021 1:37 am No access though.
Can you please try refreshing your Entware installation?

Code: Select all

sherpa reinstall ew

ImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImageImage
rs1001
Getting the hang of things
Posts: 72
Joined: Thu Jun 18, 2015 11:44 am

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

Post by rs1001 »

yep. re-installed entware.. fixed mylar.

eror: 'LazyLibrarian' service failed to start. Check (/var/log/LazyLibrarian.log) for more information
eror: 'OMedusa' service failed to start. Check (/var/log/OMedusa.log) for more information

LL fixed itself, was just a bit slow.
OM -- despite an uninstall reinstall is now hammering errors:


start daemon: failed!
= ExecuteAndLog()
output: "Traceback (most recent call last):
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/start.py", line 6, in <module>
from medusa.__main__ import main
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/medusa/__init__.py", line 24, in <module>
initialize()
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/medusa/init/__init__.py", line 37, in initialize
_configure_guessit()
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/medusa/init/__init__.py", line 202, in _configure_guessit
from medusa.name_parser.guessit_parser import (
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/medusa/name_parser/guessit_parser.py", line 12, in <module>
from medusa.logger.adapters.style import BraceAdapter
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/medusa/logger/__init__.py", line 44, in <module>
import knowit
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/ext/knowit/__init__.py", line 27, in <module>
from .api import KnowitException, know
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/ext/knowit/api.py", line 7, in <module>
from .config import Config
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/ext/knowit/config.py", line 9, in <module>
import yaml
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/ext3/yaml/__init__.py", line 13, in <module>
from .cyaml import *
File "/share/CACHEDEV1_DATA/.qpkg/OMedusa/OMedusa/ext3/yaml/cyaml.py", line 7, in <module>
from _yaml import CParser, CEmitter
File "/opt/lib/python3.9/site-packages/_yaml/__init__.py", line 8, in <module>
if not yaml.__with_libyaml__:
AttributeError: partially initialized module 'yaml' has no attribute '__with_libyaml__' (most likely due to a circular import)"
result: [1]
~
QNAP TS-653 Pro -- with 16Gb RAM
6 * Western Digital WD60EFRX WD Reds (RAID5) as a Single 27.1TB Volume
Firmware: QTS 5.0.1.2277
Post Reply

Return to “Community Apps”