Emby Installation Wants to Remove Mythtv

[obguy 0]

Hey Everybody,

 

I am trying to install Emby per the official instructions for Ubuntu on a 15.04 headless server, which includes sources for nzbget and sonarr.  The installation, however, wants to remove mythtv  as part of the installation:

Fetched 52.9 kB in 5s (9,793 B/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... The following packages were automatically installed and are no longer required:
  imagemagick-common libmono-accessibility2.0-cil libmono-cairo2.0-cil libmono-corlib2.0-cil libmono-corlib4.0-cil libmono-cscompmgd8.0-cil libmono-data-tds2.0-cil libmono-entityframework-sqlserver6.0-cil
  libmono-entityframework6.0-cil libmono-i18n-west2.0-cil libmono-ldap2.0-cil libmono-management2.0-cil libmono-messaging-rabbitmq2.0-cil libmono-messaging2.0-cil libmono-microsoft-build2.0-cil
  libmono-microsoft8.0-cil libmono-npgsql2.0-cil libmono-npgsql4.0-cil libmono-oracle2.0-cil libmono-peapi2.0a-cil libmono-posix2.0-cil libmono-rabbitmq2.0-cil libmono-relaxng2.0-cil
  libmono-security2.0-cil libmono-sharpzip2.6-cil libmono-sharpzip2.84-cil libmono-simd2.0-cil libmono-sqlite2.0-cil libmono-system-data-services2.0-cil libmono-system-data2.0-cil
  libmono-system-json2.0-cil libmono-system-ldap2.0-cil libmono-system-messaging2.0-cil libmono-system-net2.0-cil libmono-system2.0-cil libmono-webbrowser2.0-cil libmono-windowsbase3.0-cil
  libmono-xbuild-tasks2.0-cil
Use 'apt-get autoremove' to remove them.
Done
The following packages will be REMOVED:
  libmagickcore-6.q16-2 libmagickwand-6.q16-2 libmono-debugger-soft2.0a-cil libmono-i18n2.0-cil libmono-system-data-linq2.0-cil libmono-system-runtime2.0-cil libmono-system-web-mvc1.0-cil
  libmono-system-web-mvc2.0-cil libmono-system-web2.0-cil libmono-tasklets2.0-cil libmono-wcf3.0a-cil libmono-winforms2.0-cil libmono2.0-cil mythtv mythtv-frontend transcode
The following NEW packages will be installed:
  ca-certificates-mono libmono-system-data-entity4.0-cil
The following packages will be upgraded:
  imagemagick-common libmono-accessibility4.0-cil libmono-c5-1.1-cil libmono-cairo4.0-cil libmono-cecil-private-cil libmono-cil-dev libmono-codecontracts4.0-cil
  libmono-compilerservices-symbolwriter4.0-cil libmono-corlib2.0-cil libmono-corlib4.0-cil libmono-corlib4.5-cil libmono-cscompmgd0.0-cil libmono-csharp4.0c-cil libmono-custommarshalers4.0-cil
  libmono-data-tds4.0-cil libmono-db2-1.0-cil libmono-debugger-soft4.0a-cil libmono-http4.0-cil libmono-i18n-cjk4.0-cil libmono-i18n-mideast4.0-cil libmono-i18n-other4.0-cil libmono-i18n-rare4.0-cil
  libmono-i18n-west4.0-cil libmono-i18n4.0-all libmono-i18n4.0-cil libmono-ldap4.0-cil libmono-management4.0-cil libmono-messaging-rabbitmq4.0-cil libmono-messaging4.0-cil
  libmono-microsoft-build-engine4.0-cil libmono-microsoft-build-framework4.0-cil libmono-microsoft-build-tasks-v4.0-4.0-cil libmono-microsoft-build-utilities-v4.0-4.0-cil libmono-microsoft-build4.0-cil
  libmono-microsoft-csharp4.0-cil libmono-microsoft-visualc10.0-cil libmono-microsoft-web-infrastructure1.0-cil libmono-oracle4.0-cil libmono-parallel4.0-cil libmono-peapi4.0a-cil libmono-posix4.0-cil
  libmono-rabbitmq4.0-cil libmono-relaxng4.0-cil libmono-security4.0-cil libmono-sharpzip4.84-cil libmono-simd4.0-cil libmono-sqlite4.0-cil libmono-system-componentmodel-composition4.0-cil
  libmono-system-componentmodel-dataannotations4.0-cil libmono-system-configuration-install4.0-cil libmono-system-configuration4.0-cil libmono-system-core4.0-cil
  libmono-system-data-datasetextensions4.0-cil libmono-system-data-linq4.0-cil libmono-system-data-services-client4.0-cil libmono-system-data-services4.0-cil libmono-system-data4.0-cil
  libmono-system-design4.0-cil libmono-system-drawing-design4.0-cil libmono-system-drawing4.0-cil libmono-system-dynamic4.0-cil libmono-system-enterpriseservices4.0-cil
  libmono-system-identitymodel-selectors4.0-cil libmono-system-identitymodel4.0-cil libmono-system-io-compression-filesystem4.0-cil libmono-system-io-compression4.0-cil
  libmono-system-json-microsoft4.0-cil libmono-system-json4.0-cil libmono-system-ldap-protocols4.0-cil libmono-system-ldap4.0-cil libmono-system-management4.0-cil libmono-system-messaging4.0-cil
  libmono-system-net-http-formatting4.0-cil libmono-system-net-http-webrequest4.0-cil libmono-system-net-http4.0-cil libmono-system-net4.0-cil libmono-system-numerics4.0-cil
  libmono-system-reactive-core2.2-cil libmono-system-reactive-debugger2.2-cil libmono-system-reactive-experimental2.2-cil libmono-system-reactive-interfaces2.2-cil libmono-system-reactive-linq2.2-cil
  libmono-system-reactive-observable-aliases0.0-cil libmono-system-reactive-platformservices2.2-cil libmono-system-reactive-providers2.2-cil libmono-system-reactive-runtime-remoting2.2-cil
  libmono-system-reactive-windows-forms2.2-cil libmono-system-reactive-windows-threading2.2-cil libmono-system-runtime-caching4.0-cil libmono-system-runtime-durableinstancing4.0-cil
  libmono-system-runtime-serialization-formatters-soap4.0-cil libmono-system-runtime-serialization4.0-cil libmono-system-runtime4.0-cil libmono-system-security4.0-cil
  libmono-system-servicemodel-activation4.0-cil libmono-system-servicemodel-discovery4.0-cil libmono-system-servicemodel-routing4.0-cil libmono-system-servicemodel-web4.0-cil
  libmono-system-servicemodel4.0a-cil libmono-system-serviceprocess4.0-cil libmono-system-threading-tasks-dataflow4.0-cil libmono-system-transactions4.0-cil libmono-system-web-abstractions4.0-cil
  libmono-system-web-applicationservices4.0-cil libmono-system-web-dynamicdata4.0-cil libmono-system-web-extensions-design4.0-cil libmono-system-web-extensions4.0-cil
  libmono-system-web-http-selfhost4.0-cil libmono-system-web-http-webhost4.0-cil libmono-system-web-http4.0-cil libmono-system-web-mvc3.0-cil libmono-system-web-razor2.0-cil
  libmono-system-web-routing4.0-cil libmono-system-web-services4.0-cil libmono-system-web-webpages-deployment2.0-cil libmono-system-web-webpages-razor2.0-cil libmono-system-web-webpages2.0-cil
  libmono-system-web4.0-cil libmono-system-windows-forms-datavisualization4.0a-cil libmono-system-windows-forms4.0-cil libmono-system-windows4.0-cil libmono-system-xaml4.0-cil
  libmono-system-xml-linq4.0-cil libmono-system-xml-serialization4.0-cil libmono-system-xml4.0-cil libmono-system2.0-cil libmono-system4.0-cil libmono-tasklets4.0-cil libmono-webbrowser4.0-cil
  libmono-webmatrix-data4.0-cil libmono-windowsbase4.0-cil libmono-xbuild-tasks4.0-cil libwebp5 libwebpmux1 mono-4.0-gac mono-gac mono-runtime mono-runtime-common mono-runtime-sgen
139 upgraded, 2 newly installed, 16 to remove and 0 not upgraded.
Need to get 13.5 MB of archives.
After this operation, 78.1 MB disk space will be freed.
Do you want to continue? [Y/n] 

Is it possible for Emby and mythtv to coexist happily on the same box?

[fc7 123]

I'm not familiar with mythtv but the only way to know is to find mythtv package dependencies and see where they collide with Emby's deps.

 

I'm not an expert on debian package management but searching on the net I just found:

 

https://www.howtoforge.com/finding-out-package-dependencies-with-apt-rdepends-on-debian-ubuntu

 

Check it out and see if it helps to find the conflict between them, then we may be able to understand if they can or not live in the same box, happily.

[obguy 0]

Thanks for the reference, fc7.  I used it for mythtv and grep'd for mono, and nothing turned up (makes sense).  I then grep'd on "image":

 

 

obguy@server1:~$ apt-rdepends mythtv | grep image
Reading package lists... Done
Building dependency tree       
Reading state information... Done
  Depends: imagemagick-common (= 8:6.8.9.9-5)

 

which looks to conflict with emby-server:

 

obguy@server1:~$ apt-rdepends emby-server | grep image
Reading package lists... Done
Building dependency tree       
Reading state information... Done
  Depends: imagemagick-common (= 8:6.9.1-2)

The default mythtv installation is Version: 2:0.27.1+fixes.20140624.aa822f5-0ubuntu3.  Perhaps a version might work with emby.
 

[fc7 123]

Maybe, but chances are that you need to choose one or the other.

Another option is to use Docker instead of the distro packages. That way you can keep both.

 

Emby is available on Docker too, so maybe you want to give it a try.

Edited August 26, 2015 by fc7

[obguy 0]

I will check out the Docker method. Thanks for the help!