Jump to content

CentosOS 7 package sqlite 3.8.2 dependancy


jabuzzard

Recommended Posts

jabuzzard

Could someone explain to me why the packages for CentOS 7 are trying to replace sqlite? In general replacing core packages of a distribution is a bad bad thing. I can live with ImageMagick being replaced, but replacing the core sqlite packages is a MASSIVE and I mean really MASSIVE ask.

 

This is a core component of the distribution (its central to yum/rpm) and replacing it comes with huge risks to the ongoing stability of the system. It practically negates the point of running something like CentOS in the first place. Therefore the question is exactly how necessary is this?

 

The dependencies on the manual install of Emby just list sqlite3 with no specific mention that 3.8.2 (which is what the emby-server package is requiring.

 

My gut feeling is that the CentOS package has been based on a Fedora package and has picked the dependency up from their somehow. As such I could just edit the dependency in the package and rebuild, so I am not replacing a core component of the system, but I would like to get a proper handle on why the dependency exists in the first place before I go down that road.

Link to comment
Share on other sites

hurricanehrndz

The reason why was because of minimum version requirement. There were error and incompatibilities experienced with earlier versions in the past. Repackage and test if you experience no errors whatsoever we will be happy to fix the dependency. 

 

PS Previously the packages were based of Fedora, this time we took care to ensure each package for each distribution was taken care of and given some love. 

Link to comment
Share on other sites

The reason why was because of minimum version requirement. There were error and incompatibilities experienced with earlier versions in the past. Repackage and test if you experience no errors whatsoever we will be happy to fix the dependency. 

 

PS Previously the packages were based of Fedora, this time we took care to ensure each package for each distribution was taken care of and given some love. 

 

+1 @

 

I agree with @jbuzzard in that we should stick to the distros stock packages as much as possible but sometimes this is not really possible.

So far we don't have any issues reported related to sqlite 3.8.2 and system stability problems on CentOS.

Moreover, I'm running Emby on CentOS 7 too for months now and so far I didn't have any kind of problems at all. The system is rock solid.

Having said that and like @ said too, if you volunteer to test all of Emby functionalities, not only with the stock sqlite version in CentOS 7 (3.7) but also on CentOS 6 which is even older (3.6), I would be happy to change the dependencies in the beta packages so you can use them for testing. I you don't find any kind of issues then we can low down the sqlite requirements for the next stable release.

 

What do you say?

Link to comment
Share on other sites

jabuzzard

I didn't say you should never replace core distribution RPM's just that there needs to be really good reasons for doing so. I am quite relaxed about replacing ImageMagick for example its not core to the system. It's just sqlite that I am not keen on without good reason, and I am not entirely sure I have seen a compelling reason put forward.

 

From your idea of testing on CentOS6 as well I get the impression that you are using the same srpm for both CentOS 6 and 7 packages? That may explain why the emby repo has a whole bunch of apparently superfluous packages. Specifically the following packages exist as the same or as newer in epel

 
fdupes
timnyxml2
libzen
libmediainfo
 
I use priorities to protect my repos so I did have to add "exclude=mono* ibm-data-db2" to the epel repo to get mono installed because epel are carrying a doggy ancient 2.10 version for some reason. As a result my libgdiplus also came from epel. I also note that while the CentOS7 has libwebp in base and a bit older, that in the CentOS6 epel is the same in the emby repo.
 
My gut feeling is that emby should be deferring to epel where possible, and this means a bunch of the packages in the emby repo need to be culled.
 
I will have a stab a building the packages at the weekend, but the build-requires at first glance look to be lacking to me so it may take some time as I sort the actual build dependencies out. I don't propose testing CentOS6 mostly because I don't care. Besides which if 3.7.17 works for CentOS7 you could just lower the requires to this which will still cause CentOS6 to pull in 3.2.8.
 
I am not in a busting rush to get this all working.  Basically I am looking to migrate away from Plex primarily because their new Roku client is not being made available to side load on the NowTV box and I need a long term plan because replacing nine NowTV boxes with full Roku's is financially impossible (well it's possible but it is not happening). That said I was never very keen on the whole having to have accounts on Plex servers rather than my own either.
Edited by jabuzzard
Link to comment
Share on other sites

To be honest if your a not comfortable with how the packages handle dependencies you may want to try Emby docker container. This way you will only need to install docker (which is already part of CentOS) and forget about deps.

 

 

Sent from my iPad using Tapatalk

Link to comment
Share on other sites

  • 4 months later...
barrytuber

I have run into this problem when trying to install emby server on a new CentOS 7.2 system via yum. I am not completely clear on what to do to get around the dependency conflict and get emby-server installed.

 

The message I get from yum is: Protected multilib versions: sqlite-3.8.2-9.1.x86_64 != sqlite-3.7.17-8.el7.i686.

 

Am I supposed to tell yum to ignore the conflict, or am I supposed to remove the protection? And what would be the syntax of the comand to do the appropriate thing?

 

Thanks,

 

Barry

Link to comment
Share on other sites

Are you running CentOS 32-bit? If yes then we don't support it nor provide packages for it. Only for 64-bit.

 

 

Sent from my iPad using Tapatalk

Link to comment
Share on other sites

barrytuber

Are you running CentOS 32-bit? If yes then we don't support it nor provide packages for it. Only for 64-bit.

 

 

Sent from my iPad using Tapatalk

Running 64 bit.

Link to comment
Share on other sites

Did you check which package needs sqlite 32-bit? If you can't workaround that try the official docker container.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

barrytuber

Did you check which package needs sqlite 32-bit? If you can't workaround that try the official docker container.

 

 

Sent from my iPhone using Tapatalk

 

I think the issue is that my system has both 32 bit and 64 bit versions of sqlite 3.7.17-8.el7 (the 64 bit version is used by lots of packages). emby-server is trying to install the 3.8.2-9.1 version of the 64 bit package only, which is causing yum to complain about the version mis-match between the 32 bit and 64 bit versions. Or at least that's what it looked like.

 

Only Skype and qt and qt-x11 needed the 32 bit. I removed Skype but am not sure what the others are used by.

 

I guess the question is why emby-server needs a newer version of sqlite than came with Centos 7.2.

 

I have no idea what docker is or how to use it.

Link to comment
Share on other sites

Qt and qt-x11 are probably Skype deps. Try to remove them now that you removed Skype and you should be good. We need sqlite 3.8. Read above.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...