tadeucruz 0 Posted August 9, 2015 Share Posted August 9, 2015 (edited) Hi, [root@masseffect ~]# yum install emby-server Plugins carregados: fastestmirror home_emby | 1.2 kB 00:00:00 home_emby/primary | 25 kB 00:00:00 Loading mirror speeds from cached hostfile * base: mirror.nbtelecom.com.br * epel: epel.gtdinternet.com * extras: mirror.nbtelecom.com.br * updates: mirrors.dcarsat.com.ar home_emby 65/65 Resolvendo dependências --> Executando verificação da transação ---> O pacote emby-server.noarch 0:3.0.5675.1-27.1 será instalado --> Processando dependência: sqlite >= 3.8.2 para o pacote: emby-server-3.0.5675.1-27.1.noarch --> Processando dependência: ImageMagick >= 6.9.0 para o pacote: emby-server-3.0.5675.1-27.1.noarch --> Processando dependência: mono-core >= 4.0.0 para o pacote: emby-server-3.0.5675.1-27.1.noarch --> Processando dependência: libmediainfo para o pacote: emby-server-3.0.5675.1-27.1.noarch --> Executando verificação da transação ---> O pacote ImageMagick.x86_64 0:6.9.1-13.1 será instalado --> Processando dependência: ImageMagick-libs = 6.9.1-13.1 para o pacote: ImageMagick-6.9.1-13.1.x86_64 --> Processando dependência: libMagickWand-6.Q8.so.2()(64bit) para o pacote: ImageMagick-6.9.1-13.1.x86_64 --> Processando dependência: libMagickCore-6.Q8.so.2()(64bit) para o pacote: ImageMagick-6.9.1-13.1.x86_64 ---> O pacote libmediainfo.x86_64 0:0.7.75-1.el7 será instalado ---> O pacote mono-core.x86_64 0:4.0.1.44-1.3 será instalado --> Processando dependência: mono(System.ServiceModel) = 4.0.0.0 para o pacote: mono-core-4.0.1.44-1.3.x86_64 --> Processando dependência: mono(System.ComponentModel.DataAnnotations) = 4.0.0.0 para o pacote: mono-core-4.0.1.44-1.3.x86_64 --> Processando dependência: mono(System.Data) = 4.0.0.0 para o pacote: mono-core-4.0.1.44-1.3.x86_64 --> Processando dependência: mono(System.Runtime.Serialization) = 4.0.0.0 para o pacote: mono-core-4.0.1.44-1.3.x86_64 --> Processando dependência: mono(System.ComponentModel.Composition) = 4.0.0.0 para o pacote: mono-core-4.0.1.44-1.3.x86_64 --> Processando dependência: libgdiplus0 para o pacote: mono-core-4.0.1.44-1.3.x86_64 ---> O pacote sqlite.x86_64 0:3.7.17-4.el7 será atualizado ---> O pacote sqlite.x86_64 0:3.8.2-4.1 será uma atualização --> Executando verificação da transação ---> O pacote ImageMagick-libs.x86_64 0:6.9.1-13.1 será instalado --> Processando dependência: libwebp.so.5()(64bit) para o pacote: ImageMagick-libs-6.9.1-13.1.x86_64 ---> O pacote libgdiplus0.x86_64 0:3.12-9.1 será instalado ---> O pacote mono-data.x86_64 0:4.0.1.44-1.3 será instalado ---> O pacote mono-wcf.x86_64 0:4.0.1.44-1.3 será instalado --> Processando dependência: mono(System.Messaging) = 4.0.0.0 para o pacote: mono-wcf-4.0.1.44-1.3.x86_64 --> Processando dependência: mono(System.Web.Extensions) = 4.0.0.0 para o pacote: mono-wcf-4.0.1.44-1.3.x86_64 --> Processando dependência: mono(System.Data.Services.Client) = 4.0.0.0 para o pacote: mono-wcf-4.0.1.44-1.3.x86_64 ---> O pacote mono-web.x86_64 0:4.0.1.44-1.3 será instalado --> Processando dependência: mono(Mono.Data.Sqlite) = 4.0.0.0 para o pacote: mono-web-4.0.1.44-1.3.x86_64 --> Executando verificação da transação ---> O pacote libwebp.x86_64 0:0.3.0-3.el7 será atualizado --> Processando dependência: libwebp.so.4()(64bit) para o pacote: python-pillow-2.0.0-17.gitd1c6db8.el7.x86_64 ---> O pacote libwebp.x86_64 0:0.4.3-9.3 será uma atualização ---> O pacote mono-data-sqlite.x86_64 0:4.0.1.44-1.3 será instalado ---> O pacote mono-extras.x86_64 0:4.0.1.44-1.3 será instalado --> Processando dependência: mono(System.Windows.Forms) = 4.0.0.0 para o pacote: mono-extras-4.0.1.44-1.3.x86_64 ---> O pacote mono-mvc.x86_64 0:4.0.1.44-1.3 será instalado ---> O pacote mono-winfxcore.x86_64 0:4.0.1.44-1.3 será instalado --> Executando verificação da transação ---> O pacote libwebp.x86_64 0:0.3.0-3.el7 será atualizado --> Processando dependência: libwebp.so.4()(64bit) para o pacote: python-pillow-2.0.0-17.gitd1c6db8.el7.x86_64 ---> O pacote mono-winforms.x86_64 0:4.0.1.44-1.3 será instalado --> Resolução de dependências finalizada Error: Pacote: python-pillow-2.0.0-17.gitd1c6db8.el7.x86_64 (@base) Requer: libwebp.so.4()(64bit) Removendo: libwebp-0.3.0-3.el7.x86_64 (@base) libwebp.so.4()(64bit) Atualizado por: libwebp-0.4.3-9.3.x86_64 (home_emby) ~libwebp.so.5()(64bit) Você pode tentar usar o parâmetro --skip-broken para contornar o problema Você pode tentar executar: rpm -Va --nofiles --nodigest [root@masseffect ~]# Edited August 9, 2015 by tadeucruz Link to comment Share on other sites More sharing options...
fc7 123 Posted August 9, 2015 Share Posted August 9, 2015 Is this a fresh install of Emby and CentOS 7? Are you upgrading? In the meantime I will try to reproduce the problem. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
fc7 123 Posted August 9, 2015 Share Posted August 9, 2015 (edited) I just checked and we don't requier python-pillow. So you must be using it for another installed software. Can you run: "rpm -q --whatrequires python-pillow" and share the output? Also please paste the output of the commands you run using code tags since it's easier to read. Thanks. Sent from my iPad using Tapatalk Edited August 9, 2015 by fc7 Link to comment Share on other sites More sharing options...
tadeucruz 0 Posted August 9, 2015 Author Share Posted August 9, 2015 (edited) Hi fc7, It is a fresh install. But in the past i installed the old pack but i removed. I have tried the upgrade process end have the same error. [root@masseffect ~]# rpm -q --whatrequires python-pillow nenhum pacote requer python-pillow [root@masseffect ~]# I have a cups server [root@masseffect ~]# yum remove python-pillow Plugins carregados: fastestmirror Resolvendo dependências --> Executando verificação da transação ---> O pacote python-pillow.x86_64 0:2.0.0-17.gitd1c6db8.el7 será removido --> Processando dependência: python-imaging para o pacote: hplip-3.13.7-6.el7.x86_64 --> Executando verificação da transação ---> O pacote hplip.x86_64 0:3.13.7-6.el7 será removido --> Resolução de dependências finalizada Dependências resolvidas ========================================================================================================================================================================================================== Package Arq. Versão Repo Tam. ========================================================================================================================================================================================================== Removendo: python-pillow x86_64 2.0.0-17.gitd1c6db8.el7 @base 1.5 M Removendo para as dependências: hplip x86_64 3.13.7-6.el7 @base 9.1 M Resumo da transação ========================================================================================================================================================================================================== Remove 1 Package (+1 Dependent package) Tamanho depois de instalado: 11 M Correto? [s/N]: PS: Sorry for output command in PT-BR Edited August 9, 2015 by tadeucruz Link to comment Share on other sites More sharing options...
fc7 123 Posted August 9, 2015 Share Posted August 9, 2015 (edited) No problem with PT-BR. I'm actually from Argentina so I can speak portuñol and read portuguese. Now regarding your problem, it's a package conflict issue that I don't know how to solve right now. python-pillow requires a library version of libwebp that we don't provide in our package. I will check later which package depends on libwebp. In the meantime the cleanest way to go is to remove python-pillow and install Emby but that may break your cups setup if you have a HP printer or any printer that uses the drivers provided by hplip. So it's really up to you. Sent from my iPhone using Tapatalk Edited August 9, 2015 by fc7 Link to comment Share on other sites More sharing options...
fc7 123 Posted August 9, 2015 Share Posted August 9, 2015 Just checked and libwebp is required by ImageMagick. Both libwebp and ImageMagick from our repo are newer than what is provided in CentOS. Not too much room to work here. One dirty solution that will likely work is to remove python-pillow and hplip, install Emby, symlink libwebp.so.4 to libwebp.so.5.0.3 that is provided by our libwebp package and the install again hplip and python-pillow (forced if needed). If you don't like this option and you really need cups+hplip AND Emby on the same server then you can always run Emby on docker. Docker is part of CentOS 7. Sent from my iPad using Tapatalk Link to comment Share on other sites More sharing options...
tadeucruz 0 Posted August 9, 2015 Author Share Posted August 9, 2015 Hi fc7, Thanks for replay. No problem, i still using the docker. I need cups for my family. Link to comment Share on other sites More sharing options...
ABotelho 3 Posted August 11, 2015 Share Posted August 11, 2015 Error: Package: webkitgtk3-2.0.4-6.el7_0.1.x86_64 (@anaconda) Requires: libwebp.so.4()(64bit) Removing: libwebp-0.3.0-3.el7.x86_64 (@anaconda) libwebp.so.4()(64bit) Updated By: libwebp-0.4.3-9.3.x86_64 (home_emby) ~libwebp.so.5()(64bit) Error: Package: libwebkit2gtk-2.0.4-6.el7_0.1.x86_64 (@base) Requires: libwebp.so.4()(64bit) Removing: libwebp-0.3.0-3.el7.x86_64 (@anaconda) libwebp.so.4()(64bit) Updated By: libwebp-0.4.3-9.3.x86_64 (home_emby) ~libwebp.so.5()(64bit)I got this... Tried following what I was seeing in this thread... But "webkitgtk3" seems kind of critical... Link to comment Share on other sites More sharing options...
fc7 123 Posted August 11, 2015 Share Posted August 11, 2015 You need to check which program needs webkit libraries (web browser?) and remove it. It's a package conflict you need to solve similar to what another user was having with cups+hplip. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
AndreasChen 0 Posted August 27, 2015 Share Posted August 27, 2015 libwebp-0.3.0-3.el7.x86_64 is a dependency of the gnome shell, but home_emby is trying to upgrade it to libwebp-0.4.3-9.3.x86_64. This basically means any CentOS with graphical installed cannot use Emby, which is kind of outlandish. Should this be considered as a bug and fixed? You need to check which program needs webkit libraries (web browser?) and remove it. It's a package conflict you need to solve similar to what another user was having with cups+hplip.Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
fc7 123 Posted August 27, 2015 Share Posted August 27, 2015 (edited) libwep is a requirement of another dep. To avoid the dep/library conflicts you can always use Docker instead which is part of CentOS 7. Sent from my iPhone using Tapatalk Edited August 27, 2015 by fc7 Link to comment Share on other sites More sharing options...
AndreasChen 0 Posted August 28, 2015 Share Posted August 28, 2015 Quite lost why a typical user should be burdened to learn concepts like Docker. Emby worked nicely out of box before, but is getting worse and worse, update after update. Ironically the contributors are not even aware of what is going on and are arrogantly sending this project to its death. libwep is a requirement of another dep. To avoid the dep/library conflicts you can always use Docker instead which is part of CentOS 7.Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Luke 37085 Posted August 28, 2015 Share Posted August 28, 2015 Our dependencies haven't changed in several months, although the packages have changed slightly. The reason why he is suggesting Docker is because in many ways it is a lot like installing an application on windows. everything is self-contained so you don't have to worry about conflicts such as these. With these packages, we are simply marking our dependencies but sometimes the dependencies fail to install because it might affect another application on your system. It's just the nature of the beast. App A wants version X, app B wants version Y. if there isn't a version that will make them both happy, then you end up having to choose. So that is why he is suggesting Docker because it takes all of that fuss away. We are looking into lowering our version requirements for some of the libraries we depend on, and if successful, that will help. Problem is, many of the library versions we depend on are already a couple years old, so for us to support going back even further is probably going to require some kind of sacrifice. But we are going to do what we can to try and make sure it installs easily on the first try. Link to comment Share on other sites More sharing options...
AndreasChen 0 Posted August 28, 2015 Share Posted August 28, 2015 Our dependencies haven't changed in several months, although the packages have changed slightly. The reason why he is suggesting Docker is because in many ways it is a lot like installing an application on windows. everything is self-contained so you don't have to worry about conflicts such as these. With these packages, we are simply marking our dependencies but sometimes the dependencies fail to install because it might affect another application on your system. It's just the nature of the beast. App A wants version X, app B wants version Y. if there isn't a version that will make them both happy, then you end up having to choose. So that is why he is suggesting Docker because it takes all of that fuss away. We are looking into lowering our version requirements for some of the libraries we depend on, and if successful, that will help. Problem is, many of the library versions we depend on are already a couple years old, so for us to support going back even further is probably going to require some kind of sacrifice. But we are going to do what we can to try and make sure it installs easily on the first try. Thank you very much for your efforts! Link to comment Share on other sites More sharing options...
AndreasChen 0 Posted August 28, 2015 Share Posted August 28, 2015 After rebooting the server with Docker, what is wrong with "Error response from daemon: Container EmbyServer is not running" after using "docker exec EmbyServer sv restart emby"? Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted August 28, 2015 Share Posted August 28, 2015 After rebooting the server with Docker, what is wrong with "Error response from daemon: Container EmbyServer is not running" after using "docker exec EmbyServer sv restart emby"?What is the exact docker run command you executed? Sent from my D6603 using Tapatalk Link to comment Share on other sites More sharing options...
AndreasChen 0 Posted August 28, 2015 Share Posted August 28, 2015 What is the exact docker run command you executed? Sent from my D6603 using Tapatalk docker run -d --net=host -v {DataPath}:/config -v {MediaPath}:/media -v /etc/localtime:/etc/localtime:ro --name=EmbyServer emby/embyserver with proper path substitutions. Worked before reboot. Don't know how to start after reboot. Link to comment Share on other sites More sharing options...
hurricanehrndz 149 Posted August 28, 2015 Share Posted August 28, 2015 Please issue a docker stop EmbyServer and docker start EmbyServer and going forward try using the the restart button within the interface Sent from my D6603 using Tapatalk Link to comment Share on other sites More sharing options...
zao 0 Posted October 11, 2015 Share Posted October 11, 2015 For future references: edit /etc/yum/pluginconf.d/priorities.conf and set enabled = 0. Link to comment Share on other sites More sharing options...
fc7 123 Posted October 11, 2015 Share Posted October 11, 2015 For future references: edit /etc/yum/pluginconf.d/priorities.conf and set enabled = 0. Why did you have to do that? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
zao 0 Posted October 13, 2015 Share Posted October 13, 2015 Why did you have to do that? Sent from my iPhone using Tapatalk I had protected dependencies that hold of the installation of emby-server. Link to comment Share on other sites More sharing options...
fc7 123 Posted October 13, 2015 Share Posted October 13, 2015 I had protected dependencies that hold of the installation of emby-server. Wouldn't be better to properly configure yum priorities plugin for evert repo you use instead of disabling it? I mean if you are disabling it, why not just uninstall it? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now