Jump to content

emby-server_3.0.7100-71.1 Upgrade failed


Recommended Posts

Posted
I am kinda new to Emby been running it for almost if not a year after leaving Plex for poor performance etc, I am a systems engineer  VMWare VCP so I am not a noob never had any issues before with Emby I moved it from a Ubuntu 15 server to a total new build of 16 and I just went to upgrade to 7100 and I got this message, I am not good at using forums because I never really use them except for XDA so  not real good with Forum protocol I did a search for "upgrade failed" didn't find anything, you guys seem real helpful with my permissions question so maybe I can get some help with this and maybe help others if they are having a problem

 

BTW just like to say I have been using Emby and it works great it usually takes updates in seconds and never misses a beat I used to have plex and every time it took an update it would have to re enumerate everything and it was horrible so I shifted it to Linux and then it would just beat up the CPU even when no one was watching it Emby seems to be quiet until it has to transcode something or it is doing  a library scan  which is how it should be so kudos on the programming 

 

 

(Reading database ... 104820 files and directories currently installed.)

Preparing to unpack .../emby-server_3.0.7100-71.1_all.deb ...

/var/lib/dpkg/info/emby-server.prerm: line 26: syntax error near unexpected token `2'

dpkg: warning: subprocess old pre-removal script returned error exit status 2

dpkg: trying script from the new package instead ...

/var/lib/dpkg/tmp.ci/prerm: line 26: syntax error near unexpected token `2'

dpkg: error processing archive /var/cache/apt/archives/emby-server_3.0.7100-71.1_all.deb (--unpack):

 subprocess new pre-removal script returned error exit status 2

Errors were encountered while processing:

 /var/cache/apt/archives/emby-server_3.0.7100-71.1_all.deb

E: Sub-process /usr/bin/dpkg returned an error code (1)

 

Posted

Hi, sorry to hear about this. We are working on getting a fix out. Are you still able to run with the previous version?

hurricanehrndz
Posted

Issue has been fixed.

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