Cannot update Gitlab with Repo (Debian Stretch 9)
Summary
The command apt update
show errors using Gitlab oficial repository when I want to upgrade gitlab-ce package.
Steps to reproduce
In a OS Debian Stretch:
# curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | sudo bash
Detected operating system as debian/stretch.
Checking for curl...
Detected curl...
Checking for gpg...
Detected gpg...
Running apt-get update... done.
Installing debian-archive-keyring which is needed for installing
apt-transport-https on many Debian systems.
Installing apt-transport-https... done.
Installing /etc/apt/sources.list.d/gitlab_gitlab-ce.list...done.
Importing packagecloud gpg key... done.
Running apt-get update... done.
The repository is setup! You can now install packages.
# apt update
Hit:1 http://security.debian.org stable/updates InRelease
Ign:2 http://http.us.debian.org/debian stable InRelease
Hit:3 http://http.us.debian.org/debian stable Release
Ign:5 https://packages.gitlab.com/gitlab/gitlab-ce/debian stretch InRelease
Ign:6 https://packages.gitlab.com/gitlab/gitlab-ee/debian stretch InRelease
Err:7 https://packages.gitlab.com/gitlab/gitlab-ce/debian stretch Release
gnutls_handshake() failed: Public key signature verification has failed.
Err:8 https://packages.gitlab.com/gitlab/gitlab-ee/debian stretch Release
gnutls_handshake() failed: Public key signature verification has failed.
Reading package lists... Done
E: The repository 'https://packages.gitlab.com/gitlab/gitlab-ce/debian stretch Release' does not have a Release file.
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.
E: The repository 'https://packages.gitlab.com/gitlab/gitlab-ee/debian stretch Release' does not have a Release file.
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.
What is the current bug behavior?
I don't upgrade package version:
# apt-get install gitlab-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
gitlab-ce is already the newest version (10.3.2-ce.0).
What is the expected correct behavior?
Upgrade giltab-ce package to last version in the repository. (showing in package page)
Details of package version
# apt-cache policy gitlab-ce
gitlab-ce:
Installed: 10.3.2-ce.0
Candidate: 10.3.2-ce.0
Version table:
Environment details
- Operating System:
Debian 9 Stretch
- Installation Target, remove incorrect values:
- Bare Metal Machine
- Installation Type, remove incorrect values:
- Upgrade from version
10.3.2
- Upgrade from version
- Is this a single or multiple node installation? Single node.
- Resources
- CPU:
8 cores
- Memory total:
32 GB
- CPU: