Problem with key when updating from 16.4.0 to 16.4.1

General
1

I cannot update from 16.4.0 to 16.4.1. System is complaining about the lack of a Public Key??? Please advise! I am running Ubuntu 22.04. When I try to use apt-key I get a message it has been deprecated. This is the messages I receive when trying to do the above mentioned update:

root@lxdy47ap08:~# apt-get update && apt-get install gitlab-ee
Hit:1 Index of /ubuntu jammy InRelease
Hit:2 Index of /ubuntu jammy-updates InRelease
Get:3 Index of /232905/apt/ubuntu jammy InRelease [20.3 kB]
Hit:4 Index of /ubuntu jammy-security InRelease
Hit:5 https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu jammy InRelease
Err:3 Index of /232905/apt/ubuntu jammy InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 467B942D3A79BD29
Reading package lists… Done
W: GPG error: Index of /232905/apt/ubuntu jammy InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 467B942D3A79BD29
E: The repository ‘Index of /232905/apt/ubuntu jammy InRelease’ 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.
root@lxdy47ap08:~#

I have no clue what to do from here. Any light (step by step procedure) would be appreciated. Thanks!

2

Hi,

The error is related to the MySQL repository that you are using as can be seen clearly by the output:

W: GPG error: Index of /232905/apt/ubuntu jammy InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 467B942D3A79BD29
E: The repository ‘Index of /232905/apt/ubuntu jammy InRelease’ is not signed.

This is a MySQL problem, nothing related to Gitlab. You need to be asking on the MySQL forums about this. Obviously there is a problem with that repository, either it has an expired or missing pubkey, the mirror is not updated, or has been removed.

Alternatively, remove the MySQL repository from the server, and it will solve your problems. You don’t need MySQL anyway on a Gitlab server.

If you are already using this server for something else, like a website with Apache/Nginx and MySQL, then you should not be installing Gitlab on it since it will conflict. Gitlab should have it’s own server, and not be shared with a server that has other apps on it.

3

Hello, iwalker,

Thanks for pointing that out to me. GitLab is alone in this server. Someone tried to install MySQL into the server and caused this problem. Removing MySQL from it solved the issue.

Stay safe!

Best Regards,

Roberto

1 Like