Jump to content
Luke

New FreeNAS Package for testing

Recommended Posts

Luke

Where did you submit a pull request to?

 

Also for the ffmpeg error make sure your environment is set to pull quarterly stable packages. If you have it set to latest that's not supported and ffmpeg will fail.

Share this post


Link to post
Share on other sites
makarai

Hmm, did you upgrade your existing jail or installed freshly?

 

Because that error sounds strangely Familiar to being on the latest pkgs train and not the quarterly.

Share this post


Link to post
Share on other sites
makarai

Where did you submit a pull request to?

 

Also for the ffmpeg error make sure your environment is set to pull quarterly stable packages. If you have it set to latest that's not supported and ffmpeg will fail.

He put out a pull request to my repository. It's not updated to 54 yet.

Share this post


Link to post
Share on other sites
tprelog

Clean install. I just confirmed the emby-server-beta.json is using the quarterly packages. I only changed the emby-download-link as seen in the pull request

 

Did you see my edit? I realize this only seems to be effecting me in google-chrome

Share this post


Link to post
Share on other sites
makarai

I'll check tomorrow and report back. Cheers.

Share this post


Link to post
Share on other sites
MRobi

 but otherwise the installation and database upgrade went off with out a hitch.

 

Curious on this. Did you simply mount your dataset to /var/db/emby-server or were there extra steps you took here? I ask as I follow the same practice of keeping all settings on a separate dataset, and the second I mounted my configs, emby-server would no longer boot.

Share this post


Link to post
Share on other sites
tprelog

Curious on this. Did you simply mount your dataset to /var/db/emby-server or were there extra steps you took here? I ask as I follow the same practice of keeping all settings on a separate dataset, and the second I mounted my configs, emby-server would no longer boot.

 

I made a snapshot first (just in case) but otherwise I just stopped emby -- remounted my datasets -- then restarted emby

Share this post


Link to post
Share on other sites
cherup

Have the official build installed, but get an error on h264 codec:

 

 

>Shared object "libx264.so.152" not found, required by "libavcodec.so.58"

 

Any ideas how to solve ?

Share this post


Link to post
Share on other sites
Luke

Make sure your freenas system is configured for stable packages and not latest.

Share this post


Link to post
Share on other sites
cherup

Make sure your freenas system is configured for stable packages and not latest.

hmmm haven't done anything special but upgrading freebsd. so normal 11.2 is installed, but system looks like

 

 

-rw-r--r--   1 root  wheel  2838854 Sep 13 03:29 libx264.a
lrwxr-xr-x   1 root  wheel       14 Sep 13 03:29 libx264.so -> libx264.so.155
-rwxr-xr-x   1 root  wheel  1988496 Sep 13 03:29 libx264.so.155
Edited by cherup

Share this post


Link to post
Share on other sites
sluggo45

Read back the last several pages of this thread. This problem has come up several times, and solved.

Share this post


Link to post
Share on other sites
Barlog9511

Yea sorry, like i said the previous beta was missing the fanart and moviedb features.

 

I try to install the latest beta v 3.6.0.54 and problem with background images is still here ...

Share this post


Link to post
Share on other sites
cherup

Ok, have fixed my problem with "Shared object "libx264.so.152" not found, required by "libavcodec.so.58""

 

had to remove the latest libx264 package and installed the version

 

/var/cache/pkg/libx264-0.152.2854.txt

 

After that I reinstalled the emby-server.

 

Two remaining questions:

 

- when will emby be updated to libx264.so.155 that I can run a pkg update ?

- how can I configure existing installation using only quartely updates ?

Share this post


Link to post
Share on other sites
makarai

Make sure your freenas system is configured for stable packages and not latest.

 

@@Luke, i just reinstalled emby-server and indeed the quarterly packages have been updated to libx264 155, and hence the current installation method for new systems will not work. So an update within emby needs to happen in order to support the version 155

 

Cheers 

  • Like 1

Share this post


Link to post
Share on other sites
Luke

What a pain in the neck. That essentially forces the developer to release an update following a quarterly packages release.

Share this post


Link to post
Share on other sites
makarai

What a pain in the neck. That essentially forces the developer to release an update following a quarterly packages release.

Luckily it's only once a quarter :D

On a serious note, Tha last update that was serious was Dec 2017, so almost a year ago.

Share this post


Link to post
Share on other sites
constrict

For those looking for a quick temp fix.

 

I guarantee no safety from using this but the internet always finds a way to have a backup. Can use this if you don't have a backup of the pkg.

fetch https://mirrors.xtom.com/freebsd-pkg/FreeBSD%3A11%3Aamd64/quarterly/All/libx264-0.152.2854.txz
pkg add libx264-0.152.2854.txz
Edited by constrict
  • Like 2

Share this post


Link to post
Share on other sites
makarai

This will work, if some people have issues with an error message such as libx264 is already installed do it in the following order

 

from within the emby-server-beta jail you get there via

iocage console emby-server-beta

type

pkg remove libx264
fetch https://mirrors.xtom.com/freebsd-pkg/FreeBSD%3A11%3Aamd64/quarterly/All/libx264-0.152.2854.txz
pkg add libx264-0.152.2854.txz

and while you are add it update to the newest beta it works flawelessly

service emby-server stop
pkg add -f https://github.com/MediaBrowser/Emby.Releases/releases/download/3.6.0.55/emby-server-freebsd_3.6.0.55_amd64.txz
service emby-server start

Thanks constrict

 

 

For those looking for a quick temp fix.

 

I guarantee no safety from using this but the internet always finds a way to have a backup. Can use this if you don't have a backup of the pkg.

fetch https://mirrors.xtom.com/freebsd-pkg/FreeBSD%3A11%3Aamd64/quarterly/All/libx264-0.152.2854.txz
pkg add libx264-0.152.2854.txz
Edited by makarai
  • Like 2

Share this post


Link to post
Share on other sites
tprelog

@@constrict and @@makarai

 

Thanks guys. Just wanted to confirm everything seems to be working with Emby Version 3.6.0.55 and the temporary download fix for libx264

Share this post


Link to post
Share on other sites
Luke

Thanks guys. We will update the package as soon as we can.

Share this post


Link to post
Share on other sites
embytal

What a pain in the neck. That essentially forces the developer to release an update following a quarterly packages release.

 

Only if the packages you depend upon are updated.

Don't you want to leverage the optimization of some of the libraries that your project leverages?

 

Without quarterly, I can tell you the number of threads you have (currently two) on broken dependencies would be a lot higher.

Edited by embytal

Share this post


Link to post
Share on other sites
Luke

I'd rather just bundle everything in the future and not have to deal with this. This essentially just blindesides us into releasing a new update when we weren't really planning on it. And it's just going to keep happening if we don't find a more permanent solution.

Share this post


Link to post
Share on other sites
makarai

I'd rather just bundle everything in the future and not have to deal with this. This essentially just blindesides us into releasing a new update when we weren't really planning on it. And it's just going to keep happening if we don't find a more permanent solution.

 

how do other development project deal with this?

I am a physicist, so i dont have any expertise, but is there no way to  just check for if libx264 is installed instead of checking if libx264.long_unknow_version_number is installed. (was the change so big from 152 -> 155?)

Share this post


Link to post
Share on other sites
embytal

how do other development project deal with this?

I am a physicist, so i dont have any expertise, but is there no way to  just check for if libx264 is installed instead of checking if libx264.long_unknow_version_number is installed. (was the change so big from 152 -> 155?)

 

It is related to the way some libraries are linked.

Share this post


Link to post
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...