Support Forum

That's because File Station only shows files in directories for recognised shares. Anything else is not accessible. An example is (/share/Download) which points to (/share/CACHEDEV1_DATA/Download). File Station will show you (/share/Download) as (Download) but you won't see (/share) or anything else...

Ah, no worries. Thank you.

Odd that it defaults to 'develop' if a branch is not specified. Is that supposed to happen?

Then today, I find that it's possible to specify the required branch when cloning: [/share/Public] # git clone -b master --depth 1 https://git@github.com/sabnzbd/sabnzbd.git Cloning into 'sabnzbd'... remote: Counting objects: 503, done. remote: Compressing objects: 100% (446/446), done. remote: Tota...

Thanks @safihre, nicely done.

As a bit of a feature request, only the DEBUG log showed the error: And the thing I can now see is: 2017-06-09 20:25:02,157::DEBUG::[newsunpack:1565] PAR2 output was Invalid thread option: -t+ But this was not shown in the SAB GUI processing log. So, to the user, the repair process appeared to have ...

I think I might have worked it out (in my stumbling-around-in-the-dark fashion). ;) [/share/MD0_DATA/.qpkg/SABnzbdplus/SABnzbdplus] # git branch * develop [/share/MD0_DATA/.qpkg/SABnzbdplus/SABnzbdplus] # git fetch [/share/MD0_DATA/.qpkg/SABnzbdplus/SABnzbdplus] # cd .git [/share/MD0_DATA/.qpkg/SABn...

Agreed, it shows here too: [/share/MD0_DATA/.qpkg/SABnzbdplus/SABnzbdplus] # git ls-remote --heads origin 5ecbf795afffeae9b722c2e3af19db5a4e8ad051 refs/heads/0.6.x 1df2943d05d64915a166e2c97e1eef86f72e3ff3 refs/heads/0.7.x 927ba3cd9d330a74fbdfc8d926f9cbc6aee764af refs/heads/1.0.x 527a03ee973d1deabd16...

More info: I did some mucking about after that last re-install - which seems to have resulted in the master message in my OP. Here's a new install only completed a couple of minutes ago: [/share/MD0_DATA/.qpkg/SABnzbdplus/SABnzbdplus] # git branch * develop ... which now looks accurate, but is still...

Thanks @safihre.

I stopped SAB then ran: ... then restarted SAB. No change.

Also tried a complete reinstall. Same thing. SAB says develop, but Git says master.

Hi all, Upgraded from 2.0.1 to 2.1.0 earlier today, and now I seem to be on the 'develop' branch. 2017-06-10 17:14:55,891::INFO::[SABnzbd:1170] -------------------------------- 2017-06-10 17:14:55,892::INFO::[SABnzbd:1171] SABnzbd.py-2.1.0-develop (rev=unknown) 2017-06-10 17:14:55,893::INFO::[SABnzb...

Here it is: 2017-06-09 20:25:01,451::DEBUG::[newsunpack:1188] Par2-classic/cmdline = True 2017-06-09 20:25:01,786::INFO::[newsunpack:1215] Detected par2cmdline version that needs basepath, adding -B<path> parameter 2017-06-09 20:25:01,788::DEBUG::[newsunpack:1231] Starting par2: ['/usr/bin/par2', 'r...

Hi all, I'm not sure if I'm missing something really obvious here, but it seems my SAB does not feel like repairing my downloads. ;D If a download was OK, it moves through each post-processing step correctly, and unpacks fine. If a download was in need of repair, it doesn't perform the repair, and i...

At the time I first reported it, I was testing an installation script for SAB. It would sometimes go wrong, and that meant I had to re-add all my queue items. It wasn't due to any problem with SAB though. ;D Thank you - I'll ignore it now. Should anything be done about the "&quot:Repair&quo...

A couple of months later: time to add some info to this thread. ;) I have a different configuration now, but the same problems. SABnzbd installation: device: QNAP NAS device OS: QTS 4.2.5 #20170413 (heavily modded Ubuntu) SABnzbd version: 2.0.0 [55c4bef] Python: 2.7.13 Accessed by: Web Browser: Fire...