Update sabnzbd to 0.7.17

Also fix init.d script and provide reasonable sabnzbd.ini
sync with OE-core

Sync with up to date openembedded-core, bitbake and meta-openembedded.
To be decided what to do with all the now obsolete PRINC numbers.
Revert "openssl: backport fix for CVE-2014-0160"

This reverts commit c5a1a6ae65f64fc22a3535ada789087dd57040d8.
Remove PRINC from upgraded packages

Packages that already were updated to new versions need not bump the PR again,
so simply remove the PRINC from these as the build will create a newer package
regardless.
opkg_0.%.bbappend: Remove PRINC

Package PV was updated, so PR can be reset to default.
udev, git, libav, zeroconf: Remove PRINC

These packages are rarely, if ever, installed on target. Remove the PRINC,
as the upgrade path is of little concern for these.
Replace PRINC with PR for upgradability

To make the image "upgradable" set all PR values to what they were
bofore the PRINC was deprecated. This should allow clean upgrades.
Rename bbappends with a wildcard to help remember to remove the PR
when the package itself is updated upstream.
orc: Remove PRINC
mtd-utils: Remove "different device" patch

As far as I can see, this has been implemented in the upstream code now, though
just implemented differently. The patch no longer applies.
vuplus dlna server: update

- update plugin to current vuplus version
- update minidlna daemon to current version (called "ReadyMedia" now)
- don't start the daemon from the init scripts, date is not yet set
  and mounts are not yet active
- use starting by the dlnaserver plugin instead
- change a few phrasings, interpunction etc. in the plugin
Merge remote-tracking branch 'origin/master-next'
vuplus dlna browser: update

Update plugin to current vuplus git.
vuplus dlna browser/server: cosmetic

Remove "experimental" from the version as it suggest
state of flux which isn't applicable (anymore).

New version name (git-*) should be considered newer
by opkg than old version name (experimental-*).
mjpegtools: upgrade to 2.1.0 for build compatibility

Release 2.0.0 failed to build with new OE, 2.1.0 built fine so use that.
Update git submodule tags to what is actually to be used

Something got borked in the commit. The build server had the correct
tags that would build fine, so I copied those into this commit.
readymedia: add missing DEPEND on libexif

Apparently this is only actual on a clean, new build,
which I happened to run today.
vuplus hbbtv: cosmetics, no functional changes.

Adhere to common layout practise.
vuplus transcoding: cleanup

Remove support for the vuplus filestreamproxy and the livestreamproxy,
which we're not using anyway. Leaves less packages that are dependent
on vuplus git, that may halt the build.
vuplus hbbtv/dumpait: cleanup (mostly cosmetic, no functional changes)

- remove PACKAGES= from bbfiles. It's not necessary and saves
  us another few QA warnings about files not being packaged
- add a few stray debugfiles to the -dbg package, more QA warnings
- remove "experimental" from package versions
- replace package version (meaningless for versionless git)
  by git commit sequence/commit
- pin git head, less risk for failed builds
- remove patch for hbbtv-ait that was already incorporated upstream
  and failed the build
- remove inherit pkgconfig that wasn't used
- remove post install build cleanup from bbfile
vuplus hbbtv/dumpait: fix vuplus-hbbtv-dumpait dependency
(no functional changes).

Until now this package (depended on by the hbbtv browser) was included
in the vuplus 3rd party feed. There is no need though, it can
build just fine. Removed the package from 3rd party feed and added a
dependency for VU+ images so they get built/installed from OE now.