A simple question,
I want to upgrade an existing GIT installation onto my VPS server. The thing is that, when I'm writting into the command line:
apt-get install git-core
I can get only 1.5.6.5 version which is depricated. How to upgrade / reinstall GIT to get 1.7.3 or newer?
You are running a very old version of Debian (version 5). It is not even supported, so maybe consider upgrading it. Otherwise, you may get away with just building a later git version yourself.
Related
I have a requirement to upgrade the GNU Privacy Guard(GPG) package installed on AWS EC2 instance. The OS installed on EC2 is Linux(Not Ubuntu).
The current version installed is 2.0.22-5.amzn2.0.4,which is depricated as per GPG website. https://gnupg.org/download/index.html
Hence, I wish to upgrade it to version 2.3
I tried the below commands for the purpose.
$ sudo yum update-minimal gnupg
$ sudo yum reinstall gnupg
$ sudo yum update gpg
Everytime, I get a message saying NO PACKAGEs MARKED FOR UPDATE
When tried to reinstall using command number 2, the same version 2.0.22-5.amzn2.0.4 is reinstaled again, which actually isn't the latest version.
Can anyone suggest the process to upgrade to latest version?
Updated remark:
The package name on Amazon Linux 2 should be gnupg2.
You should be using Amazon Linux 2, you are using the latest package version provided by Amazon Linux 2.
By the time I write this answer, most distribution are still using gnupg 2.2, the only common distribution providing gnupg 2.3 is Fedora, you can find it at https://fedora.pkgs.org/35/fedora-x86_64/gnupg2-2.3.2-2.fc35.x86_64.rpm.html
In case you really need it now, you may either:
Build it by yourself
Install the rpm package from Fedora via dnf install <rpm-url>
Is there any way to install latest Maven specific version without using wget command in ubuntu 16.
You could try doing what my link below recommends, but add references to Bionic instead of Xenial. Then all you need to do is sudo apt install maven.
Note the current version of support Maven for Ubuntu 18.04 (Bionic) is 3.6.0-1, so if that isn't new enough for you (the latest Maven release is 3.6.2), you'll have to find another way.
https://medium.com/#george.shuklin/how-to-install-packages-from-a-newer-distribution-without-installing-unwanted-6584fa93208f
you could install sdkman on the machine 1st and then use it to install and manage various java-related tools (maven among them), but installing sdkman itself likely involves a wget
I tried to update my gitlab-CE from 10.3.2 to the latest one (currently the 11.4). And it gives me this honestly safe error.
[...]
gitlab preinstall: It seems you are upgrading from 10.x version series
gitlab preinstall: to 11.x series. It is recommended to upgrade
gitlab preinstall: to the last minor version in a major version series first before
gitlab preinstall: jumping to the next major version.
gitlab preinstall: Please follow the upgrade documentation at https://docs.gitlab.com/ee/policy/maintenance.html#upgrade-recommendations
gitlab preinstall: and upgrade to 10.8 first.
dpkg: error processing archive /var/cache/apt/archives/gitlab-ce_11.2.3-ce.0_amd64.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/gitlab-ce_11.2.3-ce.0_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root#this-vm# apt-cache policy gitlab-ce | grep Installed
Installed: 10.3.2-ce.0
But how to install to the latest minor version ? The documentation they are referring to, doesn't say how to do it.
Do you guys encounter any problem like this ?
Try to update to the latest minor version as suggested here:
apt-get update
apt-get install gitlab-ce=<YOUR-LATEST-MINOR-VERSION>-ce.0
gitlab-ctl reconfigure
gitlab-ctl restart
In your case latest minor is: 10.8.6 [as of today].
You can check the release list.
Remember to check the changes between your initial and target versions.
For CentOS/RHEL reference:
To install minor version on (CentOS/RHEL). Follow below steps.
To update minor version on 11.xx to latest version of 11.11.5:
sudo yum install gitlab-ce-11.11.5-ce.0.el6.x86_64
Similarly for all other version, You can find the specific version/install command you need to use at https://packages.gitlab.com/gitlab/gitlab-ce. Search for a version string such as gitlab-ce-11. Click on the RPM or Deb package for your OS version, then you will see all version of gitlab where you can findout latest version name and install it as stated above but just replace it with your minor version name i,e. gitlab-ce-11.11.5-ce.0.el6.x86_64
Upgrading from one version to another version should be followed as per the recommendation below or official page here.
12.7.5 -> 12.10.5
11.3.4 -> 11.11.1
10.6.6 -> 10.8.3
11.3.4 -> 11.11.8
10.6.6 -> 10.8.7
9.2.3 -> 9.5.5
8.9.4 -> 8.12.3
Always recommended that first upgrade to the latest available minor version within your major version and then upgrade it next stable version.
I was trying to update our existing gitlab-ce version 11.2.1 to latest gitlab-ce 12.2.0. After installing the 12.2.0 using yum update when I tried gitlab-ctl reconfigure. I got the error saying you need to install gitlab 11.0.0 first.
So, I removed the gitlab 12.2.0 and installed the 11.0.0 version using
yum remove gitlab-ce-12.2.0-ce.0.el7.x86_64.rpm
wget https://ftp.sjtu.edu.cn/sites/gitlab-ce/yum/el7/gitlab-ce-11.11.0-ce.0.el7.x86_64.rpm
rpm -Uvh gitlab-ce-11.11.0-ce.0.el7.x86_64.rpm
gitlab-ctl reconfigure
sudo gitlab-ctl restart
The process was successful, My old data was there and I could login with my old credentials. The version in front-end was showing 11.0.0. Now to get to latest version I did
gitlab-ctl stop
yum remove gitlab-ce-11.11.0-ce.0.el7.x86_64.rpm
wget https://ftp.sjtu.edu.cn/sites/gitlab-ce/yum/el7/gitlab-ce-12.2.0-ce.0.el7.x86_64.rpm
rpm -Uvh gitlab-ce-12.2.0-ce.0.el7.x86_64.rpm
gitlab-ctl reconfigure
gitlab-ctl restart
I got on version 12 but then I got another error the alermanager service was not starting so I added the following block to /etc/gitlab/gitlab.rb
alertmanager['flags'] = {
'cluster.advertise-address' => "127.0.0.1:9093",
}
I restarted the gitlab and everything was running.
gitlab-ctl restart
`enter code here`Check the latest version
1.sudo gitlab-rake gitlab:env:info:If it is above 13.12.0 then proceed with step 3.If its below please follow serially.
2."sudo apt upgrade gitlab-ee=13.12.5-ee.0": Update to any version of 13.12.x.
3.sudo apt-get update
4.sudo apt-get install gitlab-ee
Improving this answer, if you need to install/update manually, all you have to do is:
Download the required package here https://packages.gitlab.com/gitlab/gitlab-ee/
Run rpm -Uvh packageName.rpm
gitlab-ctl reconfigure
gitlab-ctl restart
You are good to go.
A useful tool now exists that a allows you to set the current and desired version. The tool then tells you the intervening versions you need to install in order to upgrade (please note that you Must apply the versions in a specific order as some updates make database changes later updates rely upon)
Link to Gitlab upgrade path
I have patched and recompiled a debian package. By default when I upgrade, apt wants to upgrade it with the SAME version from the repository instead.
Now, I want to convince it (by using apt-pinning, and not hold) to keep the local package if the version is the same, and try to upgrade only if the remote version is newer.
How can I do that?
Just make a local revision and upgrade the version, something like:
dch -v 1.0-1local1
Then pin that version.
So basically I'm trying to install APC, but I can't get pecl to work on Centos 5.8 i686
I have the latest stable releases of php-fpm, mysql, and nginx. Everything is working at 100%, everything is smooth. I'm running a live website with no problems. I just can't pecl to work.
yum install php-pear:
Most of the packages I'm trying to instal have dependency issues with php-common (whatever that is).
php-common = 5.1.6-32.el5 is needed
Much help is appreciated!
/usr/bin/pecl is available from php-pear package.
The dependency failures you got are stange. Probably because you have mixed installation of php-* 5.1 RPMs and php53-* 5.3 RPMs and get conflicts on devel files. You should do some clean up to keep only one set of RPMs for your target version, either 5.1 or 5.3.
You also have to install gcc, httpd-devel, php(53)-devel and finally php-pear to get phpize working.
Then you should be able to run pecl install apc
First of all assure you have your distro updated, you can do it with
yum update
Then check if you are not using any third-party repo, that contains this packages.
If you can, remove all the php packages with
yum remove php*
and try to install them again.
If you can't solve it, try the Fedora EPEL repositories which provides some updated packages.
All the commands needs be run by root.