Installing WebMeetings from the Repositories

robertwbrandt

So I’m just starting off trying to install webmeetings, and I want everything to be based on repositories moving forward.
I’ve added the repositories into my sources.list.d directory and this is the output I get when trying to update:

zarafa-meetings:~# apt update
Hit:1 http://ie.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://ie.archive.ubuntu.com/ubuntu xenial-updates InRelease  
Hit:3 http://ie.archive.ubuntu.com/ubuntu xenial-backports InRelease
Get:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Hit:5 http://repo.saltstack.com/apt/ubuntu/16.04/amd64/latest xenial InRelease     
Ign:6 https://download.kopano.io/supported/core:/final/Ubuntu_16.04 ./ InRelease
Ign:7 https://download.kopano.io/supported/webmeetings:/master/Ubuntu_16.04 ./ InRelease
Hit:9 https://download.kopano.io/supported/webmeetings:/master/Ubuntu_16.04 ./ Release
Get:8 https://download.kopano.io/supported/core:/final/Ubuntu_16.04 ./ Release [994 B]
Get:10 https://download.kopano.io/supported/webmeetings:/master/Ubuntu_16.04 ./ Release.gpg [801 B]
Ign:10 https://download.kopano.io/supported/webmeetings:/master/Ubuntu_16.04 ./ Release.gpg
Get:11 https://download.kopano.io/supported/core:/final/Ubuntu_16.04 ./ Release.gpg [801 B]
Ign:11 https://download.kopano.io/supported/core:/final/Ubuntu_16.04 ./ Release.gpg
Reading package lists... Done  
W: GPG error: https://download.kopano.io/supported/webmeetings:/master/Ubuntu_16.04 ./ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5CB27E1358E2F2A7
E: The repository 'https://download.kopano.io/supported/webmeetings:/master/Ubuntu_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.
W: GPG error: https://download.kopano.io/supported/core:/final/Ubuntu_16.04 ./ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5CB27E1358E2F2A7
E: The repository 'https://download.kopano.io/supported/core:/final/Ubuntu_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.
zarafa-meetings:~# apt-key adv -v --keyserver keyserver.ubuntu.com --recv-keys 5CB27E1358E2F2A7
Executing: /tmp/tmp.P9sIJSrjQS/gpg.1.sh -v
--keyserver
keyserver.ubuntu.com
--recv-keys
5CB27E1358E2F2A7
gpg: requesting key 58E2F2A7 from hkp server keyserver.ubuntu.com
gpgkeys: key 5CB27E1358E2F2A7 not found on keyserver
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: key not found
gpg: keyserver communications error: bad public key
gpg: keyserver receive failed: bad public key

This is I have these same repositories on other servers (all made from the same VM template) and have imported the keys just fine on them. Any ideas?

Thanks
Bob

P.S. Sorry for all the edits, I’m still getting use to this interface…

fbartels

Hello Robert,

don’t worry about the edit, we won’t charge extra because of them ;-)

Btw. you can also wrap everything into block quotes in Markdown, for better readability I did so in your posting.

Are you sure you imported to correct key? what happens if you execute

curl https://<username>:<password>@download.kopano.io/supported/core:/final/Ubuntu_16.04/Release.key | apt-key add -

again?

robertwbrandt

Aah, so I see… 3 backquotes…

So I was able to run the command and now apt update works fine:

zarafa-meetings:~# curl https://USERNAME:PASSWORD@download.kopano.io/supported/core:/final/Ubuntu_16.04/Release.key | apt-key add -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3102  100  3102    0     0    507      0  0:00:06  0:00:06 --:--:--   675
OK

I’m betting the problem is that a username/password is required to get the key so the basic apt-key command won’t work.

Thanks
Bob