Nice! Should keep you going for the next 10 years.
No worries, easy-to-do with the backup systems in place.
Nice! Should keep you going for the next 10 years.
No worries, easy-to-do with the backup systems in place.
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
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.
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
This should be fixed now. Can you please clean your current sherpa cache:rdeliege wrote: ↑Tue Jan 19, 2021 10:44 pmCode: Select all
fail: Unable to install 'Par2' (see log for more details)
Code: Select all
sherpa clean
Code: Select all
sherpa check all
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.
Hmm, can you please try re-cloning Mylar from GitHub? This should do the trick:
Code: Select all
/etc/init.d/mylar3.sh clean
OneCD, it's working again! Thanks so much for the quick support!This should be fixed now. Can you please clean your current sherpa cache:
... then check all packages again?
I opened an issuedirkonline 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.
No worries.
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).
Good work.
Can you please try refreshing your Entware installation?
Code: Select all
sherpa reinstall ew