How to compile/install a plugin from source?

Hi,

I have found this SickBeard fork called SickRage which in my opinion is much better and has features I need. I think I've read somewhere on this forum that plugins like openmediavault-sickbeard are not going to be updated until OMV 0.6 is release and I really didn't want to wait for that...

So, I've forked openmediavault-sickbeard (and uninstall the original plugin from OMV interface) and changed the main repository to the SickRage fork. What I need to know now is how can I compile my fork into a .deb file and install it into my system. I have no clue how to do that. I've compiled things from source before (like XBMC) but I never created a .deb package so I'm not sure how to do that.

Can anyone help me please?

That's it, thank you very much

For anyone that's interested, clone the plugin with:

git clone -b master https://github.com/rfgamaral/openmediavault-sickrage.git

Compile it like ryecoaaron said above and install with:

dpkg -i openmediavault-sickrage_0.6_all.deb

I changed the name and version to avoid any kind of conflicts and to be easily identified as a "different" plugin from the original one. But it's probably recommended that you uninstall the original plugin first. Backup your /home/sicbeard/.sickbeard folder first, or you might lose all your settings and database.

Also, if you change to this fork, the guys over at SickRage recommend you start the database from scratch instead of migrating it from Sick Beard. But please, read their website before migrating. I'm just installing this for the first time, so it's not a problem for me.

P.S: I did this because I needed it, of course. But I would really recommend for the original plugin to be updated with this SickRage forked repository, it's much nicer and I believe it actually replaces the functionality provided in the other 2 available repositories. Just a suggestion to whoever maintains these plugins and omv-extras.org

Thanks again

And it would be in conflict with the original one because the installation scripts, users, paths, are all the same (even the SickRage fork uses "sickbeard" everywhere, it didn't change the branding at all; in the end, it still is SickBeard). I'd say to update the original plugin, removing the other 2 forks and include this one instead.

Here's a few things that I like more on SickRage and a few are the reasons I've switched:

• Better torrent support (I don't use this)
• Subtitle download support
• Pushbullet notifications support (it was mostly for this, honestly :D)
• Cleaner UI (IMO)

And there's a ton of other features/improvements though... Beware that the developers of this state that this fork is still in beta stage.

Another thing, I'm getting this when starting this plugin service:

e$ sudo service sickbeard start
Starting sickbeard
/opt/sickbeard/lib/shove/__init__.py:15: UserWarning: Module html5lib was already imported from /opt/sickbeard/lib/html5lib/__init__.pyc, but /usr/local/lib/python2.7/dist-packages/html5lib-1.0b3-py2.7.egg is being added to sys.path
  import pkg_resources
/opt/sickbeard/lib/shove/__init__.py:15: UserWarning: Module enzyme was already imported from /opt/sickbeard/lib/enzyme/__init__.pyc, but /usr/local/lib/python2.7/dist-packages/enzyme-0.4.1-py2.7.egg is being added to sys.path
  import pkg_resources
/opt/sickbeard/lib/shove/__init__.py:15: UserWarning: Module requests was already imported from /opt/sickbeard/lib/requests/__init__.pyc, but /usr/local/lib/python2.7/dist-packages/requests-2.2.1-py2.7.egg is being added to sys.path
  import pkg_resources
/opt/sickbeard/lib/shove/__init__.py:15: UserWarning: Module bs4 was already imported from /opt/sickbeard/lib/bs4/__init__.pyc, but /usr/local/lib/python2.7/dist-packages/beautifulsoup4-4.3.2-py2.7.egg is being added to sys.path
  import pkg_resources
/opt/sickbeard/lib/shove/__init__.py:15: UserWarning: Module guessit was already imported from /opt/sickbeard/lib/guessit/__init__.pyc, but /usr/local/lib/python2.7/dist-packages/guessit-0.7-py2.7.egg is being added to sys.path
  import pkg_resources

And on the first run, there's an error in the log, which goes away after a service restart. Everything seems to be working just fine though...

Awesome

By the way, I just opened a new issue on that repo:
https://github.com/OpenMediaVa…avault-sickbeard/issues/2

No big deal, but it bothered me as I'm testing some stuff and need to restart the service

This is awesome, you guys work fast

I can get rid of my temporary package...

Zitat von "ryecoaaron"

In this case, it was a minor change though. It just added an addition repo as an option. Worst case, the sickrage repo doesn't work but the rest of the plugin and three other repos do.

Well, I got rid of my custom package, updated the plugin and I'm using the SickRage repo just fine. But I'm not sure the other 2 repos are really working. I believe the TPB one does not exist anymore, please check...

For the ones interested in the SickRage repo, I have it running on my system but not without it's issues:

• I just reported this issue that I believe it's a bug and not something wrong with the installation: https://github.com/echel0n/SickRage/issues/455 - I also tested this on Windows and followed the normal install procedure and gave me the same problem, so it's probably a bug on their end.
• If you use the sabToSickBeard.py script with SABnzbd to post-process your downloads, there's a little difference in the SickRage's script. It looks for a python2 executable, instead of a python one; that didn't exist on my system. Something like ln -s /usr/bin/python2.6 /usr/bin/python2 will do the trick to fix that.
• Subtitles downloading are not working and at first I believed this was a problem with Python 2.6 being installed instead of 2.7 because I had this working before.

As for the subtitles problem, like I said, I suspected of Python at first... But I'm researching the problem a little bit deeper and this might actually be another bug on SickRage... I'll do some more testing tomorrow and report back.

Zitat von "Cinhil"

Hi,
One more thing : after installing the compiled debian package with dpkg -i, it will usually fail the first time complaining about missing dependencies.
You just have to call "sudo apt-get -f install" to install them and fix the dpkg install.

It didn't on my case though, but thanks for the tip

About the subtitles issue I reported above... Well, now they are working just fine. Maybe the OpenSubtitles API was borked yesterday and only worked on some particular situations, I don't know... But it's working, for now at least.