Support Forum

Hmm, can you install any version? Maybe 0.6.13? I'll look into it. Could be they use the latest develop version which still is tagged as 0.6.14 since they never released a newer one. I bet that's it. Update: I manually applied your patch sabnzbd/commit/216d051 and it has resolved the issue! :D

I sent new logs which I don't believe have the "out of basepath" error (after I moved the Downloads folder back within the package's base path) . From the Entware wiki it looks like it's captured at least 2 releases of par2cmdline. From March: par2cmdline 0.6.14-20160327-1 and from June: p...

The par2cmdline on the QNAP is 0.6.14. I moved the Downloads folder back into the basepath at SAB_CONFIG/Downloads and the issue still happens.

The effect is that they just stay in the "complete" folder of Sab and don't get moved by the renamers of others.
It also indicates the the indexer that it's a successful download so it marks it as such too.

I've tried with and without "Post process only verified jobs" enabled and still run into the issue.

I've noticed that sometimes a download will be marked as "complete" https://cloud.githubusercontent.com/assets/4303/22180431/1e7cf806-e025-11e6-981a-9b00d3eea2b3.png but in the summary you'll see: https://cloud.githubusercontent.com/assets/4303/22180404/a49a58d0-e024-11e6-9cc0-b4be476514fa...