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).
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/
Currently I have CVS version 1.11.17 installed on RHEL4 server in my workspace. Now, my company is planning to upgrade to RHEL5.
Is the CVS version compatible with RHEL5, or we'll need to upgrade that too?
CVS has not changed in years. Development stopped 10 years ago. The cvs versions in RHEL4,5,6,7 will all be compatible.
In general:
1.11.x = The latest stable version
1.12.x = A newer version that was never declared 'stable' and then development on CVS stopped. In RHEL you will not be given the 1.12.x version. In some other distributions you may be.
Which is the latest version of TortoiseSVN is compatible with Windows XP service pack 3?
I just installed its latest build 1.9.3 but unfortunately it's not supported in windows XP.
1.8.12 is the latest release in branch 1.8, 1.8.10 was released because 1.8.9
BUG: Fails to run on Windows XP.
and, btw, 1.8.11 had a lot of important bugfixes (contrary to minor corrections in 1.8.12)
TSVN 1.8.x are the latest versions that support Windows XP, because Subversion 1.9 removed XP support. So get the latest version 1.8.9 from sourceforge.
You have to download v 1.7
Here is the link:
https://sourceforge.net/projects/tortoisesvn/?source=typ_redirect
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