E: Version for 'gitlab-ce' was not found

Hi can anyone help on this ? seems the package is not available

Sure it’s available:

all you need to do now is go through the list and find the one for the version of Linux you have installed. If the distro is not on the list, then I guess that means you have an old Linux install that you need to upgrade first. But you didn’t post very much info for which Linux version you are searching for.

Using debian version 8.
Gitlab is broken after upgrade Not sure what to do ?
/opt/gitlab/embedded/bin/ruby: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28’ not found (required by /opt/gitlab/embedded/lib/libruby.so.2.7)

And why did it break? What was done on your system that broke it? We need to know exactly what the state was before you started to do something, and what version of Gitlab was installed before upgrading or whatever it was you did.

13.8.8 doesn’t exist for Debian 8, only for Debian 9 and 10, so Stretch and Buster. 13.3.9 was last release for Debian 8 Jessie.

sure Thanks for the update. I tried to manually upgrade to 13.6 and then it broke. Seems OS doesnot support. I have just found from the link

Yes you will need to revert back to the version before your failed upgrade attempt and restore the backup under /var/opt/gitlab/backups. You will also need /etc/gitlab/gitlab.rb and /etc/gitlab/gitlab-secrets.json for successful restore.

Do you remember what version of gitlab was installed before your failed upgrade? If unsure you can check /var/log/apt/term.log or history.log should show this.

You can do this on a new server so as not to break your existing one anymore. Make a Debian 10 install and on this install the gitlab version that you had before failed upgrade. Then copy the gitlab.rb and gitlab-secrets.json files to this server as well as the backup made before failed upgrade. You can then run the commands from the gitlab restore docs to get it up and running again.

In short:

  1. Copy gitlab.rb and gitlab-secrets.json to /etc/gitlab on the new server.
  2. Run gitlab-ctl reconfigure to get the system configured using those two files. Postgresql will be configured now also.
  3. Copy the backup to /var/opt/gitlab/backups on the new server and make sure this file is owned by the git user, so chown git:git /var/opt/gitlab/backups/backup-file.tar replace backup-file.tar with the actual name of the file.
  4. Stop puma and sidekiq gitlab-ctl stop puma and gitlab-ctl stop sidekiq, and run restore gitlab-backup restore BACKUP=11493107454_2018_04_25_10.6.4-ce obviously replace the name of the backup file as per point 3.

Then after that:

gitlab-ctl reconfigure
gitlab-ctl restart
gitlab-rake gitlab:check SANITIZE=true

Once Debian 10 has restored for Gitlab 13.3.9 or whatever version you were on before the failed upgrade, you can then follow the Gitlab Upgrade docs and make sure to follow the upgrade path correctly to get to the latest Gitlab version 14.4.x. Upgrading GitLab | GitLab which means follow the documentation to get it to upgrade to 13.8.8 first, before then going to next version. You cannot do apt-get upgrade otherwise, it will try to upgrade from 13.3.9 to 14.4.x will not work and break your system again.

1 Like

Debian 8 (aka jessie) reached end of life on June 30, 2020, meaning it will no longer receive software updates.

Shortly afterward, GitLab stopped producing new GitLab packages for Debian 8 jessie.

The last version of GitLab available for Debian 8 is gitlab-ce_13.3.9-ce.0

gitlab/gitlab-ce - Results for '13' and debian/jessie in gitlab/gitlab-ce (Page 2).

To run 13.4 and newer, migrate your data to a server running a Supported Linux distribution.

Hi images with attachments went missing after the upgrade.

Hi @saga440 it sounds like one or more components didn’t restart successfully.

Can you try running the following commands on the server, waiting a minute for everything to come back up, and then verifying whether the image attachments show up again?

sudo gitlab-ctl reconfigure
sudo gitlab-ctl restart

Let us know how it goes!

Hi seems, missing images directory locations changed…when i check on the server, the images seems to be moved from one hashed path to the other, how to identify the images which has problems ?

See my reply here. Try not to repeat asking your question in new posts, it won’t help get your question answered any quicker.