Jump to content

Linux Package Changes


Luke

Recommended Posts

Hi Team,

 

We will be making changes to our Linux packages today. Here is a list of what will be changing. Beginning tomorrow, your feedback will be appreciated in helping us iron out any issues.

 

Changes across all distributions (excluding Arch):

  • embymagick package is now non-conflicting for all distros.
  • embymagick compiled options now synchronized across all distros, updated to latest 6.9 release.
  • libembysqlite3-0 now main sqlite3 library, non conflicting with system library.
  • sqlite3 library compiled options synchronized across all distros and updated to latest release.
  • Added umask option to emy-server wrapper, default set to 002. Default can be override by inserting `UMASK=` into /etc/emby-server.conf to openSUSE and debian based distros.
  • openSUSE and debian base repos now providing version 4.6.2.7 of mono.
  • Issues with dllmap in sqlite libraries resolved in beta and dev.
  • No more double logging to /var/log/. Look for logs in /var/lib/emby-server. (openSUSE and debian). Available in journalctl though.
  • Ubuntu Next repo enabled.
  • Debian Next (Debian 9) repo enabled.
  • Leap 42.2 enabled.

Docker changes:

  • Updates to latest version on restart.
  • UMASK environment variable sets umask for emby-server wrapper
  • New service file, logs directly to journalctl
  • Sensible docker logs limit set. Hopefully mitigates oversized docker containers due to large log files.
  • New templates for unRAID
Link to comment
Share on other sites

hurricanehrndz

More fixes:

  • Fedora 25 repo enabled.
  • arm64 for Ubunut 14.04 enabled.

 

Docker:

  • Pass EDGE=1 as env variable to enable updates on startup
  • Fixed systemd service included with docker image

 

Please Note: Some of these fixes are currently being implemented and will take a little while for them to propagate.

 

Happy Early X-Mas.

 

Repos should now be stabilized. All major changes have now been merged.

 

All distros now support umask.

Edited by hurricanehrndz
Link to comment
Share on other sites

For a little more info on the sqlite change, it means we'll always ensure Emby is running the latest and highest performing version. We've seen a lot of you report poor performance only to find out your system installed sqlite is very old, so now, that will no longer be a concern.

Link to comment
Share on other sites

sscheib

Using aptitude i dont get any changes .. 

dpkg -l | grep emby
ii  emby-server                                                      3.0.8500-89.1                     all          Emby Server is a home media server.
ii  libembymagickcore-6.q8-2:amd64                                   8:6.9.5-1                         amd64        low-level image manipulation library -- quantum depth Q8
ii  libembymagickwand-6.q8-2:amd64                                   8:6.9.5-1                         amd64        image manipulation library
 
 
... and while pasting it, I realize, I updated it yesterday. *facepalm*
I'm, sorry!
 
However, this release doesn't fix the issue addressed above from myself :/
Link to comment
Share on other sites

Hey guys, it looks like the recent changes are causing me to get an error on CentOS 6. I am still somewhat new to linux. Any suggestions on how to resolve?

 

 

Determining fastest mirrors
epel/metalink                                            |  14 kB     00:00
XXX
base                                                     | 3.7 kB     00:00
base/primary_db                                          | 4.7 MB     00:05
epel                                                     | 4.3 kB     00:00
epel/primary_db                                          | 5.9 MB     00:06
extras                                                   | 3.4 kB     00:00
extras/primary_db                                        |  37 kB     00:00
home_emby                                                | 1.2 kB     00:00
home_emby/primary                                        |  41 kB     00:00
home_emby                                                                 34/34
updates                                                  | 3.4 kB     00:00
updates/primary_db                                       | 3.7 MB     00:04
Resolving Dependencies
--> Running transaction check
---> Package embymagick.x86_64 0:6.9.6+6-1.1 will be updated
---> Package embymagick.x86_64 0:6.9.6+6-3.1 will be an update
---> Package embysqlite.x86_64 0:3.15.0-1.1 will be obsoleted
--> Processing Dependency: embysqlite for package: emby-server-3.0.8500-89.1.x86_64
---> Package libembysqlite3-0.x86_64 0:3.15.0+1-6.1 will be obsoleting
---> Package mono-core.x86_64 0:4.6.1.5-1.1 will be updated
---> Package mono-core.x86_64 0:4.6.2.7-1.1 will be an update
---> Package mono-data.x86_64 0:4.6.1.5-1.1 will be updated
---> Package mono-data.x86_64 0:4.6.2.7-1.1 will be an update
---> Package mono-data-sqlite.x86_64 0:4.6.1.5-1.1 will be updated
---> Package mono-data-sqlite.x86_64 0:4.6.2.7-1.1 will be an update
---> Package mono-extras.x86_64 0:4.6.1.5-1.1 will be updated
---> Package mono-extras.x86_64 0:4.6.2.7-1.1 will be an update
---> Package mono-mvc.x86_64 0:4.6.1.5-1.1 will be updated
---> Package mono-mvc.x86_64 0:4.6.2.7-1.1 will be an update
---> Package mono-wcf.x86_64 0:4.6.1.5-1.1 will be updated
---> Package mono-wcf.x86_64 0:4.6.2.7-1.1 will be an update
---> Package mono-web.x86_64 0:4.6.1.5-1.1 will be updated
---> Package mono-web.x86_64 0:4.6.2.7-1.1 will be an update
---> Package mono-winforms.x86_64 0:4.6.1.5-1.1 will be updated
---> Package mono-winforms.x86_64 0:4.6.2.7-1.1 will be an update
---> Package mono-winfxcore.x86_64 0:4.6.1.5-1.1 will be updated
---> Package mono-winfxcore.x86_64 0:4.6.2.7-1.1 will be an update
---> Package tzdata.noarch 0:2016i-1.el6 will be updated
---> Package tzdata.noarch 0:2016j-1.el6 will be an update
--> Finished Dependency Resolution
Error: Package: emby-server-3.0.8500-89.1.x86_64 (@home_emby)
           Requires: embysqlite
           Removing: embysqlite-3.15.0-1.1.x86_64 (@home_emby)
               embysqlite = 3.15.0-1.1
           Obsoleted By: libembysqlite3-0-3.15.0+1-6.1.x86_64 (home_emby)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
 

Edited by ajw12
Link to comment
Share on other sites

hurricanehrndz

Hey guys, it looks like the recent changes are causing me to get an error on CentOS 6. I am still somewhat new to linux. Any suggestions on how to resolve?

Sorry I have a fix. I have been waiting for feedback. I have not herd anything so I will start pushing the fixes. Sorry for the trouble.

Edited by hurricanehrndz
Link to comment
Share on other sites

Sorry I have a fix. I have been waiting for feedback. I have not herd anything so I will start pushing the fixes. Sorry for the trouble.

Thank you. I just tried updating, but it looks like the changes have not been pushed yet. I will try again later today.

Link to comment
Share on other sites

hurricanehrndz

Would you be willing to chage your repo to a test repo. I have one more idea that might fix the upgrade

 

Sent from my ONEPLUS A3000 using Tapatalk

Link to comment
Share on other sites

  • 2 weeks later...

Yeah, send me the details.

 

Would you be willing to chage your repo to a test repo. I have one more idea that might fix the upgrade

Sent from my ONEPLUS A3000 using Tapatalk

Link to comment
Share on other sites

hurricanehrndz

Should be fixed in the repo now. Let me know if you're still experiencing issues

 

Sent from my ONEPLUS A3000 using Tapatalk

Link to comment
Share on other sites

Should be fixed in the repo now. Let me know if you're still experiencing issues

 

Sent from my ONEPLUS A3000 using Tapatalk

 

I still have the same issue. Is there something else I have to do to get my box to notice that changes? I ran a yum clean all right before.

 

 

home_emby                                                | 1.2 kB     00:00

home_emby/primary                                        |  41 kB     00:00

home_emby                                                                 34/34

Resolving Dependencies

--> Running transaction check

---> Package embymagick.x86_64 0:6.9.6+6-1.1 will be updated

---> Package embymagick.x86_64 0:6.9.6+6-7.1 will be an update

---> Package embysqlite.x86_64 0:3.15.0-1.1 will be obsoleted

--> Processing Dependency: embysqlite for package: emby-server-3.0.8500-89.1.x86_64

---> Package libembysqlite3-0.x86_64 0:3.15.0+1-7.1 will be obsoleting

---> Package mono-core.x86_64 0:4.6.1.5-1.1 will be updated

---> Package mono-core.x86_64 0:4.6.2.7-1.1 will be an update

---> Package mono-data.x86_64 0:4.6.1.5-1.1 will be updated

---> Package mono-data.x86_64 0:4.6.2.7-1.1 will be an update

---> Package mono-data-sqlite.x86_64 0:4.6.1.5-1.1 will be updated

---> Package mono-data-sqlite.x86_64 0:4.6.2.7-1.1 will be an update

---> Package mono-extras.x86_64 0:4.6.1.5-1.1 will be updated

---> Package mono-extras.x86_64 0:4.6.2.7-1.1 will be an update

---> Package mono-mvc.x86_64 0:4.6.1.5-1.1 will be updated

---> Package mono-mvc.x86_64 0:4.6.2.7-1.1 will be an update

---> Package mono-wcf.x86_64 0:4.6.1.5-1.1 will be updated

---> Package mono-wcf.x86_64 0:4.6.2.7-1.1 will be an update

---> Package mono-web.x86_64 0:4.6.1.5-1.1 will be updated

---> Package mono-web.x86_64 0:4.6.2.7-1.1 will be an update

---> Package mono-winforms.x86_64 0:4.6.1.5-1.1 will be updated

---> Package mono-winforms.x86_64 0:4.6.2.7-1.1 will be an update

---> Package mono-winfxcore.x86_64 0:4.6.1.5-1.1 will be updated

---> Package mono-winfxcore.x86_64 0:4.6.2.7-1.1 will be an update

---> Package ncdu.x86_64 0:1.12-1.el6 will be updated

---> Package ncdu.x86_64 0:1.12-2.el6 will be an update

---> Package sudo.x86_64 0:1.8.6p3-24.el6 will be updated

---> Package sudo.x86_64 0:1.8.6p3-25.el6_8 will be an update

---> Package tzdata.noarch 0:2016i-1.el6 will be updated

---> Package tzdata.noarch 0:2016j-1.el6 will be an update

--> Finished Dependency Resolution

Error: Package: emby-server-3.0.8500-89.1.x86_64 (@home_emby)

           Requires: embysqlite

           Removing: embysqlite-3.15.0-1.1.x86_64 (@home_emby)

               embysqlite = 3.15.0-1.1

           Obsoleted By: libembysqlite3-0-3.15.0+1-7.1.x86_64 (home_emby)

               Not found

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

 

Link to comment
Share on other sites

hurricanehrndz

Hmm strange. There is definitely some weird things going on there. Just remove and reinstall emby. Please ensure you backup the folder in /var/lib

 

Sent from my ONEPLUS A3000 using Tapatalk

Link to comment
Share on other sites

  • 3 weeks later...
sunshine.emby

I have a Debian 8/armhf (Banana Pro) system and had successfully installed a previous version by adding some Raspberry Pi and Mono sources.

I thought I had also successfully updated to the latest version but now it looks like something went wrong at some point. (I don't have emby-server running all the time because there seems to be some memory problem and it gets killed by the OS at some point anyway.)

 

Anyway to get to the point, I have unmet dependencies on embymagick and libembysqlite3-0. The architecture for emby-server is "all" but for embymagick there are only "i386" or "amd64". It is the same for libembysqlite3-0. If I understand correctly, these are virtual packages. And I am guessing that means there should not be any binary code involved.

 

Is this an oversight? Thanks for any assistance.

Link to comment
Share on other sites

hurricanehrndz

I have a Debian 8/armhf (Banana Pro) system and had successfully installed a previous version by adding some Raspberry Pi and Mono sources.

I thought I had also successfully updated to the latest version but now it looks like something went wrong at some point. (I don't have emby-server running all the time because there seems to be some memory problem and it gets killed by the OS at some point anyway.)

 

Anyway to get to the point, I have unmet dependencies on embymagick and libembysqlite3-0. The architecture for emby-server is "all" but for embymagick there are only "i386" or "amd64". It is the same for libembysqlite3-0. If I understand correctly, these are virtual packages. And I am guessing that means there should not be any binary code involved.

 

Is this an oversight? Thanks for any assistance.

For arm devices please the Ubuntu 14.04 repo. 

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...