antechinus55 0 Posted February 4, 2017 Posted February 4, 2017 I am trying to install emby on an xubuntu 16.04 lts instalation. I followed the instructions for aadding thee ppa but it is 'not authorised' and therefore apt install emby-server does not find a suitable package. I downloaded the binary directly but it wont install either, with a cryptic error message abourt errors being encountered while processing. Can someone offer advice as to what to do next please? The server is a headless NAS but running a full xubuntu installation and I am accessing it via nomachine. The content is/will be on the same server.
Luke 42077 Posted February 4, 2017 Posted February 4, 2017 Hi, can you please copy and paste the exact error message you received? thanks !
antechinus55 0 Posted February 4, 2017 Author Posted February 4, 2017 here is the error I get when I try to install the direct binary download sudo dpkg -i emby-server_3.1.5-15.1_all.deb dpkg: error processing archive emby-server_3.1.5-15.1_all.deb (--install): cannot access archive: No such file or directory Errors were encountered while processing: emby-server_3.1.5-15.1_all.deb
antechinus55 0 Posted February 4, 2017 Author Posted February 4, 2017 and here is the error I get trying to update after adding the ppa: W: GPG error: http://download.opensuse.org/repositories/home:/emby/xUbuntu_16.04 Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0A506F712A7D8A28 E: The repository 'http://download.opensuse.org/repositories/home:/emby/xUbuntu_16.04 Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.
antechinus55 0 Posted February 4, 2017 Author Posted February 4, 2017 OK, I did nothing other than go back through my history at the console and ran apt install to generate the previous error message and it is now installing correctly. Thank for the prompt response, but it now seems to be working.
antechinus55 0 Posted February 4, 2017 Author Posted February 4, 2017 any idea why it worked on the third try? I copied and pasted the commands from your website instructions, so it was not a typo.
Luke 42077 Posted February 4, 2017 Posted February 4, 2017 More than likely you missed the instruction that added the ppa key. Or it was not run with root permissions, since the error said not authorized
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