openmediavault-emby plugin (formerly mediabrowser)
-
- OMV 2.x
- Sergio
-
-
I am pretty sure this is just something with his prior install of mono.
Thanks for letting me know @happyreacer
-
Short time ago, I reinstalled openmediavault. The following things were installed after the installation:
1. backports kernel 4.4
2. openmediavault-extrasorg 3.0.11
3. openmediavault-zfs 3.0So, at the moment the only installed plugin is zfs.
Purging libmono* and cli-common-dev brings nothing to remove, but mono+ brings up the following message:
Code
Alles anzeigen.... Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass Sie eine unmögliche Situation angefordert haben oder, wenn Sie die Unstable-Distribution verwenden, dass einige erforderliche Pakete noch nicht erstellt wurden oder Incoming noch nicht verlassen haben. Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen: Die folgenden Pakete haben unerfüllte Abhängigkeiten: init : Hängt ab von (vorher): systemd-sysv soll aber nicht installiert werden oder sysvinit-core soll aber nicht installiert werden oder upstart soll aber nicht installiert werden E: Fehler: Unterbrechungen durch pkgProblemResolver::Resolve hervorgerufen; dies könnte durch zurückgehaltene Pakete verursacht worden sein.
Greetings Hoppel
-
-
@hoppel118
What do you get with these?apt-cache policy libnunit-cil-dev
apt-cache policy mono-develHave you done all your upgrades in the update manager???
-
Try purging and reinstalling...
apt-get purge openmediavault-emby
apt-get purge embyThen try reinstalling from the plugin section. Before you do do an "apt-get update" and make sure you don't have any errors.
no changes ...
everything runs fine on my OMV ... except emby
maybe it's due to the cpu ? It's a J1900 ... ASRock Q1900 ITX
Is ffmpeg downloaded from the emby-ressources?
Maybe a way to download it manually from there? -
@El Muchacho
The program automatically downloads ffmpeg. It could be issue with the library files too if arch command is not showing that cpu as x86_64. If it is issue with library files I can give you a quick fix. Intel Celeron J1900Give me results of:
archthis too:
ls -la /opt/emby/embylibs -
-
Emby is working great for me too in OMV 3.0.13 Happy....
El Muchacho... Mach schnell! Ich habe nicht ewig Zeit. Other things to do man!
-
@hoppel118
What do you get with these?apt-cache policy libnunit-cil-dev
apt-cache policy mono-develHave you done all your upgrades in the update manager???
Code
Alles anzeigenroot@mediatank:~# apt-cache policy libnunit-cil-dev libnunit-cil-dev: Installiert: (keine) Installationskandidat: 2.6.3+dfsg-1~xamarin2 Versionstabelle: 2.6.3+dfsg-1 0 400 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages 2.6.3+dfsg-1~xamarin2 0 500 http://download.mono-project.com/repo/debian/ wheezy/main amd64 Packages root@mediatank:~# apt-cache policy mono-devel mono-devel: Installiert: (keine) Installationskandidat: 4.2.3.4-0xamarin2 Versionstabelle: 4.2.3.4-0xamarin2 0 500 http://download.mono-project.com/repo/debian/ wheezy/main amd64 Packages 3.2.8+dfsg-10 0 400 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
Yes, everything is up to date, nothing to install. Under plugins I see the omvextrasorg 3.0.10 and not 3.0.11. But there are no updates in the update manager.
Thanks for your help.
-
@hoppel118
It may be some pinning issue... I'm going to get lunch.@ryecoaaron Any ideas on this? On these 2 packages I have 500 for both jessie and xamarin.
Need to see you:
/etc/apt/sources.listand results of:
ls -la /etc/apt/sources.list.d -
-
Holy shit.... wheezy jessie repos.. WTF? Just noticed. Should be all Jessie.
Code# mono-project repo deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus-mono jessie main deb http://download.mono-project.com/repo/debian wheezy main deb http://download.mono-project.com/repo/debian wheezy-libjpeg62-compat main
Be back in a while... Aaron needs to see. -
Code
Alles anzeigenroot@mediatank:~# cat /etc/apt/sources.list #deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20160102-11:44]/ jessie contrib main non-free # debian standard sources deb http://ftp.de.debian.org/debian/ jessie main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://ftp.de.debian.org/debian/ jessie main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free # debian backport sources deb http://ftp.de.debian.org/debian/ jessie-backports main
Coderoot@mediatank:~# ls -la /etc/apt/sources.list.d insgesamt 24 drwxr-xr-x 2 root root 4096 Apr 9 19:39 . drwxr-xr-x 11 root root 4096 Apr 9 19:39 .. -rw-rw-rw- 1 root root 15 Apr 9 19:39 omv-extras-org-custom.list -rw-rw-rw- 1 root root 502 Apr 9 19:39 omv-extras-org-erasmus.list -rw-r--r-- 1 root root 667 Jan 2 11:38 openmediavault.list -rw-r--r-- 1 root root 45 Jan 1 13:05 openmediavault-local.list
Guten Appetit!
-
i have a Asrock Q1900-ITX with a j19000 cpu and it work
-
-
Holy shit.... wheezy jessie repos.. WTF? Just noticed. Should be all Jessie.
Where did you notice this?
Edit: I found what you meant:
Coderoot@mediatank:~# cat /etc/apt/sources.list.d/omv-extras-org-erasmus.list # Regular omv-extras.org repo deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus jessie main # ZFS repo deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus-zfs jessie main deb http://archive.zfsonlinux.org/debian jessie main # mono-project repo deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus-mono jessie main deb http://download.mono-project.com/repo/debian wheezy main deb http://download.mono-project.com/repo/debian wheezy-libjpeg62-compat main
-
-
Yeah, I see all that.. On my vm same pinning value, 500, for jessie and wheezy/xamarin packages. If version number is the same jessie package installs. If not the xamarin package is installing.
@ryecoaaron
Any idea why his pinning values are different and the xamarin packages are not installing??? From his pinning values above it seems the xamarin packages have the higher value and it is not allowing him to install because they are wheezy or something. -
-
If the pinning is the same, the higher version number should install.
His Debian pinning is 400. The xamarin is 500. It should install the xamarin and the policy output says it is the candidate to install. No idea why it isn't. Maybe there is a conflicting mono package that has a different name.
Packages don't know they are from a wheezy repo. They may be in a repo but there is nothing in a .deb that tells the system what distro/repo it is from. It only looks at package dependencies.
-
maybe is it a problem when you activate a mono-testing? I have only the mono repro activate
-
maybe is it a problem when the mono-testing is activate, too?? I use only the mono repro.
-
-
Mono testing repo is not activated. Only the mono repo is used.
-
I am confused by this too. It looks to me as though it should install.
His sources.list looks a bit odd. I would try to replace it with standard repos at install and apt-get update. Then try again.
or fix these lines and comment out backports:
Codedeb http://ftp.de.debian.org/debian/ jessie main deb-src http://ftp.de.debian.org/debian/ jessie main
It has to be that he messed with his sources.list.
@hoppel118 if you want to add to your repos do it with the custom repos in OMV Extras. You don't need to mess with the sources.list file.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!