I have gitlab-ee installed on an Ubuntu 22.04 OS and every update I’ve done up to this point has worked fine. I run ‘sudo apt update’ and the gitlab repository isn’t updated. When I run sudo apt install gitlab-ee it tells me that I’m already at the most recent version (17.4.1) Any ideas?
When I’ve had a similar issue to this when the repositories didn’t show updated packages, I just refreshed the repositories by using the command that is normally used when installing the Gitlab repositories for the first time, so:
curl https://packages.gitlab.com/install/repositories/gitlab/gitlab-ee/script.deb.sh | sudo bash
then check again after this, and you should see the packages showing up.
I believe executing any command of the form curl | sh is a bad idea - you have no idea what you’re executing. The better way is downloading the script, read it, and then execute the downloaded version.
Does apt update list the gitlab repositories? (Show the full output if you’re not sure).
It can show it, and most likely will as he’s used it to upgrade so far. I also had them show up, but they wouldn’t refresh (I was on 12.9.3 at the time). But yes, whether you run the script as per the Gitlab documentation (like I quoted), or download it manually first and run it should at least completely refresh the repositories and at least solved it for me when I had the same situation.
Probably Gitlab should re-write the documentation to be more security conscious about downloading the script first and then running it.
It seems like my repositories got nuked… This is the output from apt update:
Last login: Fri Oct 11 19:48:14 2024 from 10.10.1.115
ryan@ies-subversion:~$ sudo apt update
[sudo] password for ryan:
Hit:1 http://security.ubuntu.com/ubuntu noble-security InRelease
Hit:2 http://archive.ubuntu.com/ubuntu noble InRelease
Get:3 http://archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
Hit:4 http://archive.ubuntu.com/ubuntu noble-backports InRelease
Fetched 126 kB in 1s (154 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
ryan@ies-subversion:~$
I ran the installation script again (Thanks @iwalker ) and that seemed to fix it.
1 Like
I did just update the kernel recently, could that have blown away my apt repositories??
Kernel shouldn’t do that, upgrade from one Ubuntu distro to another would do it though, for example upgrading from 20.04 to 22.04 using the Ubuntu upgrade process. I don’t use that do-release-upgrade script purely for that reason as been bitten by it before.
Easier is to manually change the repositories from focal to jammy for example and use the standard apt-get tools, at least repos don’t get nuked that way.
From your original post you mention Ubuntu 22.04 which is Jammy, however you have 24.04 as the repos show noble.
You’re right, I do see that the distro has been upgraded to 24.04. That explains it, thanks for your help.