Marcos' House of Curios

#sysadmin

This is something I need to remember to do from now on since GitLab announced upgrade stops.

My installation ran 16.2 and I was reminded of a required update stop on apt-get upgrade

Preparing to unpack .../24-gitlab-ce_16.4.1-ce.0_amd64.deb ...
gitlab preinstall: It seems you are upgrading from 16.2 to 16.4.
gitlab preinstall: It is required to upgrade to the latest 16.3.x version first before proceeding.
gitlab preinstall: Please follow the upgrade documentation at https://docs.gitlab.com/ee/update/index.html#upgrade-paths

To do so I would have to get latest 16.3

root@toolkit:~# apt-cache policy gitlab-ce
gitlab-ce:
  Installed: 16.3.5-ce.0
  Candidate: 16.4.1-ce.0
  Version table:
     16.4.1-ce.0 500
        500 https://packages.gitlab.com/gitlab/gitlab-ce/debian bullseye/main amd64 Packages
     16.4.0-ce.0 500
        500 https://packages.gitlab.com/gitlab/gitlab-ce/debian bullseye/main amd64 Packages
 *** 16.3.5-ce.0 500
        500 https://packages.gitlab.com/gitlab/gitlab-ce/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status

Version 16.3.5-ce.0 was the latest minor version, so I used it as instructed

root@toolkit:~# apt-get install gitlab-ce=16.3.5-ce.0

Now I can let it rip to 16.4

root@toolkit:~# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  linux-image-amd64 postgresql postgresql-client postgresql-contrib
The following packages will be upgraded:
  gitlab-ce
1 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Need to get 0 B/1,301 MB of archives.
After this operation, 30.1 MB of additional disk space will be used.
Do you want to continue? [Y/n]

Thanks to GitLab for making it easy. It clearly takes a lot more effort to output a clear message than it looks at first glance.

Now to find a simple way to install and use bacula...