Ace_Scorcher 2 Posted September 3, 2019 Share Posted September 3, 2019 (edited) While doing a manual install of 4.2.1.0 on a Freenas jail, I found that the emby package install would fail if ImageMagick6-nox11 was installed instead of ImageMagick6. Could this be resolved maybe in a future version. The nox11 versions of packages/ports are often preferable. Edited September 3, 2019 by Ace_Scorcher Link to comment Share on other sites More sharing options...
Luke 36999 Posted September 3, 2019 Share Posted September 3, 2019 Hi, fail how? What exactly happened? Link to comment Share on other sites More sharing options...
Ace_Scorcher 2 Posted September 3, 2019 Author Share Posted September 3, 2019 [Emby] Fetching emby-server-freebsd11_4.2.1.0_amd64.txz: 100% 26 MiB 803.8kB/s 00:34 [Emby] Installing emby-server-4.2.1.0_1... package emby-server is already installed, forced installpkg: Missing dependency 'ImageMagick6'Failed to install the following 1 package(s): https://github.com/MediaBrowser/Emby.Releases/releases/download/4.2.1.0/emby-server-freebsd11_4.2.1.0_amd64.txz Link to comment Share on other sites More sharing options...
Luke 36999 Posted September 3, 2019 Share Posted September 3, 2019 So i guess they both can't co-exist? 1 Link to comment Share on other sites More sharing options...
Ace_Scorcher 2 Posted September 3, 2019 Author Share Posted September 3, 2019 Not much point in having both. They are the same software package, but the "-nox11" has the x11 xwindows gui support removed. Since it's on freenas there is really no need to run a windowed gui. Link to comment Share on other sites More sharing options...
Luke 36999 Posted September 4, 2019 Share Posted September 4, 2019 Right I get it, but if they can coexist then I think that would make life easier for everyone. Have you tried to just install it? Link to comment Share on other sites More sharing options...
Ace_Scorcher 2 Posted September 4, 2019 Author Share Posted September 4, 2019 Sure, I ended up uninstalling the "-nox11" and installing the standard ImageMagick6 pkg. I have a working emby server on 4.2.1.0. I was just hoping that in the future we could get it to recognize the "-nox11" version as well. Link to comment Share on other sites More sharing options...
Luke 36999 Posted September 4, 2019 Share Posted September 4, 2019 Ok, I'll pass this on to our freebsd package developer. Thanks. Link to comment Share on other sites More sharing options...
Duffyx 25 Posted September 7, 2019 Share Posted September 7, 2019 (edited) Hi Luke, just a heads-up for the package developer: you can't put that logic in a package as this is a build time option and dependency. You could but that would mean you would have to distribute two packages, one build against the normal ImageMagick and one build against the noX11 version. Ace_Scorcher, the FreeBSD port does allow for this flexibility though. So if you want emby-server installed with the noX11 version of ImageMagick: disable X11 in the port before building and installing. Edited September 7, 2019 by Duffyx Link to comment Share on other sites More sharing options...
Duffyx 25 Posted September 7, 2019 Share Posted September 7, 2019 (edited) So i guess they both can't co-exist? Correct, this is by definition as they have conflicting install paths. The only difference is that the nox11 version has a bit less dependecies on X11 stuff. The main binaries are still the same and installed in the same location as the normal ImageMagick (which is why they cannot coexist). Edited September 7, 2019 by Duffyx Link to comment Share on other sites More sharing options...
Luke 36999 Posted September 7, 2019 Share Posted September 7, 2019 Great, thanks for the info ! Link to comment Share on other sites More sharing options...
Ace_Scorcher 2 Posted September 7, 2019 Author Share Posted September 7, 2019 (edited) Ace_Scorcher, the FreeBSD port does allow for this flexibility though. So if you want emby-server installed with the noX11 version of ImageMagick: disable X11 in the port before building and installing. True, which is how I normally build. Unfortunately the port was still on 4.1.1.0_3 when I updated, so I had to use the package from github. If I remember correctly when I originally rebuilt the server in the spring, The ImageMagic port would fail, so it was a quick fix to install the package. BTW, emby also seems to complain if libva-2.5.0 is missing libva-x11.so.2. I gues a nox11 emby server is not to be. Edited September 7, 2019 by Ace_Scorcher Link to comment Share on other sites More sharing options...
Luke 36999 Posted September 7, 2019 Share Posted September 7, 2019 Just so that we can be realistic about this, FreeBSD is hard enough for us to support as it is. I think we will need to see more users wanting this before we're able to look at it. Link to comment Share on other sites More sharing options...
Ace_Scorcher 2 Posted September 7, 2019 Author Share Posted September 7, 2019 I completely understand. This was by no means a major issue. I appreciate the fact that all of you take the time to look at these issues. 1 Link to comment Share on other sites More sharing options...
Duffyx 25 Posted September 8, 2019 Share Posted September 8, 2019 (edited) BTW, emby also seems to complain if libva-2.5.0 is missing libva-x11.so.2. This should only happen if you use the binary package from Emby and specifically build libva without X11 support (because the port defaults to X11 on). I have been running emby-server since I updated the port together with OPTIONS_UNSET=X11 in my make.conf. Emby-server has been working fine forever, although I do use a package builder such as Poudriere or Synth. Edited September 8, 2019 by Duffyx Link to comment Share on other sites More sharing options...
Luke 36999 Posted September 30, 2019 Share Posted September 30, 2019 For non-beta users who wish to run the stable release, the suggested approach is installing the IOCage plugin: Link to comment Share on other sites More sharing options...
FreeBSD_Lover 13 Posted October 14, 2019 Share Posted October 14, 2019 .....Unfortunately the port was still on 4.1.1.0_3 when I updated, so I had to use the package from github. Maybe I am reading this wrong; but it sounds like you are using both ports and packages. This is a no no with FreeBSD; ports and packages are too very different systems, and using both is sure to cause trouble. https://emby.media/community/index.php?/topic/78414-do-not-mix-ports-and-packages-in-freebsd/ 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