Investigating an issue (we run our own mirror, so servers don’t need to access the world), I just discovered that sudo apt-cache policy gitlab-ee | less
on our production servers (that don’t run 14.6. so it’s not terribly relevant) and a completely clean machine (that doesn’t use our mirror) doesn’t show 14.6.6 (the most recent release) being available.
Hi,
thanks for flagging. I can reproduce your problem in a Ubuntu 20.04 container. I’ll ping our delivery teams.
$ docker run -ti ubuntu:20.04 bash
root@b6e22d55ff83:/# apt update && apt -y install curl
root@b6e22d55ff83:/# curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.deb.sh | bash
root@b6e22d55ff83:/# apt-cache policy gitlab-ee | grep 14.6
14.6.5-ee.0 500
14.6.4-ee.0 500
14.6.3-ee.0 500
14.6.2-ee.0 500
14.6.1-ee.0 500
14.6.0-ee.0 500
root@b6e22d55ff83:/# curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.deb.sh | bash
root@b6e22d55ff83:/# apt-cache policy gitlab-ce | grep 14.6
14.6.5-ce.0 500
14.6.4-ce.0 500
14.6.3-ce.0 500
14.6.2-ce.0 500
14.6.1-ce.0 500
14.6.0-ce.0 500
Cheers,
Michael
1 Like
It wasn’t so much of a problem as something I discovered and thought looked weird (that’s also why I only posted here and didn’t make a support ticket).
2 Likes
Thanks! I think raising a support ticket for missing packages is fine Alternatively, an issue in the Omnibus project for packages can also be an option to get more eyes to investigate.
Update on the problem: Delivery and distribution teams are investigating, it seems to be a problem with the package index not adding 14.6.6 yet. More to follow.
1 Like
Package indexing has been fixed, and all 14.6.6 packages are available in the repository.
apt update
apt-cache policy gitlab-ee | grep 14.6
14.6.6-ee.0 500
14.6.5-ee.0 500
14.6.4-ee.0 500
14.6.3-ee.0 500
14.6.2-ee.0 500
14.6.1-ee.0 500
14.6.0-ee.0 500
1 Like