app.emby.media forcing me to update Emby server

[biddy 0]

I've been holding off on upgrading Emby, hoping that some day the repo will be fixed. Everything was working fine until a few days ago when I began to get an error when accessing app.emby.media. I can't access my Emby server from app.media.emby until I upgrade according to the message. Is there a workaround for this?

 

I've ran a whole lot of Linux servers over the years and the current method Emby is using, unzipping a file you download every update, is a really poor practice. It can lead to a total package mess. Is there any way to get this update through a managed repository (the proper way of doing things!) or do I just have to suck it up, go against best Linux practices and try to do a totally messy upgrade and hope my Emby server comes out intact on the other side?

 

Thanks.

[Luke 39009]

Hi, what version of Emby Server are you running?

[biddy 0]

3.3.1.0

[Luke 39009]

@@biddy

What distro are you on?

[biddy 0]

Ubuntu 16.04

[Luke 39009]

Are you on the old repository based package that we were hosting on opensuse? Or did you originally install via the .deb file?

[biddy 0]

The OpenSUSE repository.

[Luke 39009]

Ok thanks. It should hopefully just be as simple as this:

https://emby.media/community/index.php?/topic/58532-emby-3400-opensuse-repositories/?p=635708

[biddy 0]

Ok thanks. It should hopefully just be as simple as this:

https://emby.media/community/index.php?/topic/58532-emby-3400-opensuse-repositories/?p=635708

Will this keep my current users & configurations etc intact? I will of course make a backup of my server as it is currently.

 

My thinking on making the upgrade path was.

0) Backup current Emby server

1) Purge current emby-server packages

2) Remove OpenSUSE Emby repo

3) Download current Emby release .deb

4) Dpkg current Emby release .deb

[Luke 39009]

Yes, but I think a backup is wise. Please let us know how you get on. Thanks.