• Community
  • Products
  • Bitbucket
  • Questions
  • Planning to migrate stash v3.11 to Bitbucket 4.11, stuck at git upgrade as the minimum version should be greater than 1.8 for BitBucket 4.11 but on Centos 6, latest that we get is 1.7.10. Tried to build it from source but again facing dependency issues wi

Planning to migrate stash v3.11 to Bitbucket 4.11, stuck at git upgrade as the minimum version should be greater than 1.8 for BitBucket 4.11 but on Centos 6, latest that we get is 1.7.10. Tried to build it from source but again facing dependency issues wi

swetha meti March 15, 2017

Planning to migrate stash v3.11 to Bitbucket 4.11, stuck at git upgrade as the minimum version should be greater than 1.8 for BitBucket 4.11 but on Centos 6.2, latest that we get is 1.7.10.

Tried to build it from source but again facing dependency issues with libssh2 which needs to be >= 1.4.2,Any suggestions as to how to take care of git upgrade on centos 6.2 or should i migrate the server to Centos 7 to resolve this?

2 answers

0 votes
G__Sylvie_Davies__bit-booster_com_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 15, 2017

Git itself is quite self-contained.   It might work to just install the Centos7 Git RPM, but otherwise leave everything else on Centos6.

Here's the Centos7 Git RPM:   http://mirror.centos.org/centos/7/os/x86_64/Packages/git-1.8.3.1-6.el7_2.1.x86_64.rpm

(Note:  you'd then need to carefully watch this RPM for any security updates, since your Centos6 package system won't receive them.)

 

p.s.  I invite you to try my add-on:  Bit-Booster for Bitbucket Server

swetha meti March 15, 2017

Hi Sylvie,Tried installing the rpm package but with no success.Below is the error

 

rpm -Uvh git-1.8.3.1-6.el7_2.1.x86_64.rpm
warning: git-1.8.3.1-6.el7_2.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
error: Failed dependencies:
    libc.so.6(GLIBC_2.14)(64bit) is needed by git-1.8.3.1-6.el7_2.1.x86_64
    libc.so.6(GLIBC_2.16)(64bit) is needed by git-1.8.3.1-6.el7_2.1.x86_64
    libgnome-keyring.so.0()(64bit) is needed by git-1.8.3.1-6.el7_2.1.x86_64
    libpcre.so.1()(64bit) is needed by git-1.8.3.1-6.el7_2.1.x86_64
    libz.so.1(ZLIB_1.2.0)(64bit) is needed by git-1.8.3.1-6.el7_2.1.x86_64
    perl(Term::ReadKey) is needed by git-1.8.3.1-6.el7_2.1.x86_64
    perl-Git = 1.8.3.1-6.el7_2.1 is needed by git-1.8.3.1-6.el7_2.1.x86_64
    git = 1.7.10.4-1.el6.rfx is needed by (installed) perl-Git-1.7.10.4-1.el6.rfx.x86_64

0 votes
Baskar Annamalai
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 15, 2017
swetha meti March 15, 2017

i tried all those and i get the below message when i try to install the dependent libraries

yum install curl-devel expat-devel gettext-devel openssl-devel zlib-devel gcc perl-ExtUtils

Error: Package: libcurl-7.19.7-37.el6_5.3.x86_64 (updates)

           Requires: libssh2(x86-64) >= 1.4.2

           Installed: libssh2-1.2.2-7.el6_1.1.x86_64 (@CentOS/6.2)

               libssh2(x86-64) = 1.2.2-7.el6_1.1

 

when i tried to compile and install libssh2(x86-64) >= 1.4.2 i get the below error saying there is again other dependency

# rpm -Uvh libssh2-1.4.3-10.el7_2.1.x86_64.rpm
warning: libssh2-1.4.3-10.el7_2.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
error: Failed dependencies:
    libc.so.6(GLIBC_2.14)(64bit) is needed by libssh2-1.4.3-10.el7_2.1.x86_64

 

seems like its getting into a loop of dependencies.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events