Beiträge von nzbanon

    I found something.
    During the installation, the script /var/lib/dpkg/info/openmediavault-sabnzbd.postinst download a file and with a grep and sed get the last version of sabnzbd. the line containing the version is correctly found by the sed command seems non tu extract the string matching the version.
    To make my install working I edited the /var/lib/dpkg/info/openmediavault-sabnzbd.postinst, and I forced the version number :



    Code
    STABLE=1.1.0
    wget -q -nv http://downloads.sourceforge.net/project/sabnzbdplus/sabnzbdplus/${STABLE}/SABnzbd-${STABLE}-src.tar.gz -O /tmp/sabnzbdplus.tar.gz

    I'll send a message to the package maintainer

    I've been stuck on 1.0.3 for quite some time. Would this workaround resolve my issue? If so, would updating work as expected going forward? Also, is it important to paste that code into any particular section of openmediavault-sabnzbd.postinst or does it not matter? Thanks!

    Hi. Having a couple issue with a new SickRage install using https://github.com/SickRage/SickRage.git. What happens is that I get the following errors starting with the second launch of SickRage (everything is normal on the initial launch):


    Code
    2016-04-09 10:25:29 MAIN :: Unable to setup GitHub properly. GitHub will not be available. Error: [Errno -2] Name or service not known
    2016-04-09 10:25:29 MAIN :: Updating network timezones failed, this can happen from time to time. URL: http://sickrage.github.io/sb_network_timezones/network_timezones.txt


    When I go to General --> Advanced Settings --> GitHub, I see that there is no branch selected any longer (master is displayed and works fine at initial launch) and "Error: No branches found." displayed in red text beneath the dropdown box which is empty.


    I have another install or SickRage which was initially switched over to SickRage from the SickRageTV git that is not having any of these issues.


    I've tried reinstalling Sickbeard(Rage) a few times to no avail. Any help would be greatly appreciated. Thanks


    UPDATE: Turned out it was a VMWare issue that had nothing to do with OMV. Sorry about that.