Yup, because you also need the git-http package installed. But, you were on the right track. 
I recently discovered an issue where additional Entware IPKs like git were not being installed after Entware was reinstalled due to outdated IPKs (this was a sherpa bug, not an Entware bug).
Using sherpa fix will correct this by installing missing IPK dependencies. 
Also, if your NAS has QTS 5.2.0 or-later installed, you no-longer need SortMyQPKGs.
The Sherpa fix got me working.. thanks again
Eventually, the day will come when we won’t need it anymore.
I saw SABnzbd 5.0.0 has been released. Do you need to update Sherpa before restarting SAB or will it work fine without updating Sherpa?
I took the risk and tried it out. Seems to work without any problems.
@Andyvie, @jimpoison, I’ve just released a new SABnzbd QPKG to support SABnzbd 5.0.0. with updated Python wheels and module lists.
Thanks! A good time to update all QPKG’s 
I had major issues with my version of SABnzbd it was throwing a missing module in the debug as below. Long story short, I ran a sherpa clean, and now I get the issue further down
Not all required Python modules are available, please check requirements.txt
Missing module: sabctools
warn: Remote file download failed
bash: /share/CACHEDEV1_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: No such file or directory
[/share/CACHEDEV1_DATA/.qpkg/sherpa/cache] # ls -l
-rw-r–r-- 1 admin administ 0 May 3 19:19 sherpa-manager.tar.gz
I thought maybe I could reinstall, but I can’t figure that out now either 
Oops.
Please run a reset:
sherpa reset
… then a fix:
sherpa fix
[~] # sherpa reset
warn: Remote file download failed
bash: /share/CACHEDEV1_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: No such file or directory
Damn. Can you please reinstall the sherpa QPKG?
curl -skL https://tinyurl.com/get-sherpa > /share/Public/sherpa.qpkg;
sh /share/Public/sherpa.qpkg;
Yup did all that as well. the sherpa-manager.tar.gz file is 0 bytes in the folder
/share/CACHEDEV1_DATA/.qpkg/sherpa/cache/
[/share/CACHEDEV1_DATA/.qpkg/sherpa/cache] # curl -skL https://tinyurl.com/get-sherpa > /share/Public/sherpa.qpkg;
[/share/CACHEDEV1_DATA/.qpkg/sherpa/cache] # sh /share/Public/sherpa.qpkg;
Install QNAP package on TS-NAS…
./
./qinstall.sh
./package_routines
./built_info
./qpkg.cfg
2+1 records in
2+1 records out
64+1 records in
64+1 records out
sherpa 251212 is already installed. Setup will now perform package upgrading.
Firmware check is fine.
symlinks removed
Link service start/stop script: sherpa-service.sh
Set QPKG information in /etc/config/qpkg.conf
symlinks created
[/share/CACHEDEV1_DATA/.qpkg/sherpa/cache] # sherpa
warn: Remote file download failed
bash: /share/CACHEDEV1_DATA/.qpkg/sherpa/cache/sherpa-manager.sh: No such file or directory
[/share/CACHEDEV1_DATA/.qpkg/sherpa/cache] #
Can you try this next?
/sbin/curl 'https://raw.githubusercontent.com/OneCDOnly/sherpa/stable/sherpa-manager.tar.gz' > /share/Public/temp.tar.gz;
ll /share/Public/temp*
This may be relevant: I’ve been seeing GitHub delays all morning. This could affect sherpa’s ability to download its internal objects.
Hi OneCD,
Just got home from a short break and tried to upgrade SAB (and SickGear) by using
sudo sherpa upgrade all.
The installation went ok, but the last step fails:
• This package action failed (and why):
activate SABnzbd QPKG in 6 seconds (not-found)
activate SickGear QPKG in 10 seconds (not-found)
Can you help me?
Edit: Hmmm…I just logged in again via SSH and I got an error-message (didn’t see it last time, but perhaps I overlooked it):
Could not chdir to home directory /share/homes/Andy: no such file or directory
Perhaps this is related?
Hi Andy, can you run a fix please?
sudo sherpa fix
If Sickgear and SABnzbd were not started as part of the fix, please start them manually:
sudo sherpa start sab sg
The missing home directory is a QTS issue. You may need to recreate your user homes. In the QTS Control Panel, enable home folders for all users.
Control Panel → Privilege → Users → Advanced Settings → Home Folder → tick the “Enable home folder for all users” box → Apply
Yes! That worked! Everything is working fine again!
Was this a known issue which is solved by Sherpa Fix?
Kinda. I (nearly) always suggest a fix as the first-step, as it resolves several issues that can occur without me needing to double-up on repair code. But, we should need it less-and-less over time as I add code to prevent these issues occurring in the first place.
Next time something like this happens I’ll use fix.
Thanks for your quick solution.
Different question: I’m using Sherpa for years now and really appreciate your kind help with problems and the time you invest in maintaining Sherpa. Do you accept donations as an appreciation for the work you are doing?