It is possible to upgrade easily from 6.2 > the latest stable version? Seems like you cannot skip versions, and have to upgrade as 6.3 > 6.4 > 6.5 etc..
This seems like a massive task!
We considered installing a separate VM with the latest version on running alongside, and cloning repo > new repo.
You can certainly skip most versions. Though there are only documented steps for certain jumps. You should be fine in your case though.
For source installs: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/6.x-or-7.x-to-7.14.md
Once you have updated to the 7.14 you can switch to using the omnibus packages to make upgrading easier going forward:
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/update/README.md#upgrading-from-a-non-omnibus-installation-to-an-omnibus-installation
And then you will be able to upgrade to the latest stable which is 8.0.
Alternatively if you want to stick with the source install you can do the following after getting to 7.14: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/7.14-to-8.0.md
Related
There is elevate tool that allows you to upgrade from CentOS 7.9 to AlmaLinuŃ… 8.x (the latest 8.x)
https://wiki.almalinux.org/elevate/ELevate-quickstart-guide.html
While for various reasons I need to upgrade to a specific version of AlmaLinux (not the latest one) - i.e. to 8.3. Is it possible?
It seems there is the following option:
leapp preupgrade --target <target_os_version>
Described here:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/upgrading_from_rhel_7_to_rhel_8/reviewing-the-pre-upgrade-report_upgrading-from-rhel-7-to-rhel-8
At present we are on Apache/2.2.15 (UNIX) version. To fix the vulnerabilities we are suggested to upgrade to new version. I got new version from online using "wget" command and followed steps mentioned on this link http://httpd.apache.org/docs/2.2/install.html#download.
Once I am done, checked version using httpd -v. It gives me old version Apache/2.2.15 (UNIX). If I check using /usr/local/apache2/bin/httpd - v. It gives me new version. Did I successfully upgraded the version or not? If not what should I do?
I tried "yum install httpd" - It says "Nothing to do".
You now have two versions of Apache installed. You have the one installed with the system package manager (yum) in /usr/sbin/httpd. You have one installed manually in /usr/local/apache2/....
Which one you get will be determined entirely by which path you use.
In general, mixing system-managed packages with manually installed packages is a recipe for trouble. If you want to stick with the newer version in /usr/local, you should remove the system version, and realize that you will lose some manageability. For example, you will no longer be able to use yum install ... to install new Apache modules, and you will not be able to verify the installed files using tools like rpmverify.
If your distribution currently has Apache 2.2.x, that suggests your distribution is fairly old. For example, RHEL (and CentOS) 7 (and similar variants) have version 2.4.6 packaged, so you may want to update your host to something newer than whatever you're running now.
Yes, its successfully upgraded as per the screenshot.
httpd 2.2.15 is the version with RHEL 6 repository, here HTTPD_HOME is /etc/httpd (Highest version provided for HTTPD via RPM RHEL 6 is 2.2.15)
httpd 2.4.6 is the version with EPEL-HTTPD24 repository, here HTTPD_HOME is /usr/local/apache2/
We have gitlab ver 7.13.1 on linux red hat 6.3 vm . We need the feature of reverting merge request . To which version should we upgrade our gitlab ?
Regards, Nir
The latest, there are lots of security issues that need to be addresses in even the newer versions.
The latest would be best.
But there are a few caveats to look for when upgrading from pre 8.0 :
If you're using Gitlab CI upgrade to 8.0 first (see this)
If you're using Gilab GEO then upgrade to 8.17 (see this)
If you're using both, upgrade to 8.0 first, then to 8.17
Finally upgrade to 9.0.2 (latest version at this date).
I'm attempting to migrate from a GitLab 7.1.0 (Source) installation (on Centos6) to latest omnibus (on Centos7) using these instructions:
https://docs.gitlab.com/omnibus/update/README.html#upgrading-from-non-omnibus-postgresql-to-an-omnibus-installation-using-a-backup
Essentially it boils down to:
Set up a new machine,
Install the omnibus version on the new machine that matches your source version,
Do an "backup" from the source version,
Restore that backup into the omnibus version,
update the omnibus version to latest.
I'm stuck on #2. I've added the GitLab repo, but the oldest version of the "gitlab-ce" package available is 7.10.0. Also they're named weirdly, e.g. "7.10.0~omnibus-1", "7.10.0~omnibus.1-1", etc. instead of simply "7.13.0-ce.0.el7".
What are my options? If I install 7.13.0 Omnibus from the repo then try to restore a backup from 7.1.0 into it, should I expect that to work? Will I lose data?
Is there a 7.1.0 omnibus RPM available somewhere?
If the new machine needs to be Centos6 in order to install a 7.1.0 omnibus package then I can reimage.
If you look in the official RPM repo it looks like 7.10 is the oldest version of the omnibus available for CentOS.
I think your best option is to perform the source upgrade outlined in 6.x-or-7.x-to-7.14.md which should let you upgrade to v7.14. Then you can resume the normal "upgrade source installation to omnibus installation" method you found.
Also, in case it's helpful, the docs repo has incremental source upgrade procedures for many more versions.
Requirement is to download software from Centos 5.4. When I do yum install , I get the latest version and not the one available for Centos 5.4.
How do I configure yum to download only from 5.4 repo?
As I said in my answer to your other question you need to find a repository that has a maintained, static entry for 5.4.
Most repositories have just one repository for each major version and upgrade it as new minor versions are released. But some keep specific repositories for each version independently (at least for a little while).
I would start with checking whether your current repository has an explicitly 5.4 repository (by using the URL in the yum.conf or /etc/yum.repos.d/*.repo file for the repository).
If that doesn't work out you get to try other mirrors as listed on the CentOS mirrors website.
As a fallback, and I encourage you to try to find a valid mirror first, you can find this sort of minor version specific repository on http://vault.centos.org.