upgarding GIT

upgarding GIT

[James Wells]

Hi All

I am fairly new to git, however I have a challenge of upgrading git from 2.0.4 to 2.4.12 and my initial 2.0.4 install was done via TAR BALL on my server.

I have a centos server running git and Atlassian STASH and my challenge is for me to upgrade the STASH application I need to move to a newer version of git.

How do I go about upgrading git from TAR BALL installs , is there an easy way as I would prefer not to have to create a new server and migrate everything across , I would like to perform the upgrade on the current local server if it is at all possible.

Any assistance is most welcome and I would appreciate your feedback or comments on how you would go about achieving this task.

Thanks
J

Re: upgarding GIT

[Ævar Arnfjörð Bjarmason]

On Mon, Aug 07 2017, James Wells jotted:

> Hi All
>
> I am fairly new to git, however I have a challenge of upgrading git from 2.0.4 to 2.4.12 and my initial 2.0.4 install was done via TAR BALL on my server.
>
> I have a centos server running git and Atlassian STASH and my challenge is for me to upgrade the STASH application I need to move to a newer version of git.
>
> How do I go about upgrading git from TAR BALL installs , is there an easy way as I would prefer not to have to create a new server and migrate everything across , I would like to perform the upgrade on the current local server if it is at all possible.
>
> Any assistance is most welcome and I would appreciate your feedback or comments on how you would go about achieving this task.
>
> Thanks
> J

This is really a question of "hey I ran 'make install' on this thing in
the past, how do I now upgrade it?". There's nothing git-specific about
this, git doesn't do anything special that 99% of the software you run
on CentOS wouldn't do in this scenario.

I'm not saying this to be an unhelpful smartass, but just to point out
that to look for a solution you don't need to search for e.g. "how to
replace git package" on Google, but just how to replace manually
installed packages in general.

You're going to want to install git via RPM/yum. CentOS already has a
package for it.

It may fail because of existing files, you can likely force it or
manually remove the files first.

Be careful not to end up with directories which contain some
Frankensteinian combination of old tar.gz installed files & newly
installed files. You can use RPM to list what package owns given files,
you should manually remove e.g. some git-whatever command that's not
managed by rpm living alongside your newly installed stuff.

Re: upgarding GIT

[Todd Zullinger]

Ævar Arnfjörð Bjarmason wrote:
> On Mon, Aug 07 2017, James Wells jotted:
>> I am fairly new to git, however I have a challenge of upgrading git 
>> from 2.0.4 to 2.4.12 and my initial 2.0.4 install was done via TAR 
>> BALL on my server.
>>
>> I have a centos server running git and Atlassian STASH and my 
>> challenge is for me to upgrade the STASH application I need to move 
>> to a newer version of git.

Which release of CentOS are you using James?  And what git version is 
required for the Atlassian Stash (which is now called Bitbucket) 
release you're trying to use?  IIRC, they support as far back as git 
1.8?

> You're going to want to install git via RPM/yum. CentOS already has a 
> package for it.

Indeed.  (But I'm biased because I would never, ever install software 
via 'sudo make install' on anything other than a throw-away test 
instance.)

The one problem folks run into on CentOS/RHEL is that the versions may 
be somewhat old.  CentOS/RHEL 6 ships with git 1.7.1, for instance. 
CentOS/RHEL 7 is only a little newer, with git 1.8.3.  There are 
"software collections" which provide git 1.9¹ and 2.9², but personally 
I've never liked using software collections for software that I need 
to integrate with other tools.

For users of CentOS/RHEL who want to run the current git release in a 
packaged form, the Fedora git package maintainers take care to ensure 
that the Fedora packages can be built for the current supported 
releases of CentOS/RHEL (6 & 7 at the moment).  Grabbing the current 
code and/or srpm from Fedora should (almost³) always build cleanly 
using the mock build tool for CentOS/RHEL.

I also try to keep a semi-official COPR repo up to date, here:

    https://copr.fedorainfracloud.org/coprs/g/git-maint/git/

(Even as the primary maintainer of that repo, I'd still suggest that 
it's wise to either mirror it locally or rebuild the srpm's in your 
own infrastructure, to ensure that if the copr service is ever down 
you can reinstall important systems.)

¹ https://www.softwarecollections.org/en/scls/rhscl/git19/
² https://www.softwarecollections.org/en/scls/rhscl/rh-git29/
³ Right now, there's a slight issue building the current git for 
  CentOS 7 because RHEL 7.4 moved the pcre2 package from EPEL into 
  RHEL and CentOS 7.4 is not yet built.  The Fedora packages are 
  built against pcre2 now (thanks Ævar ;).  So for a few weeks it 
  won't be possible to build them for CentOS 7 without a minor change.

-- 
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ocean, n. A body of water occupying about two-thirds of a world made
for man -- who has no gills.
    -- Ambrose Bierce, "The Devil's Dictionary"

RE: upgarding GIT

[James Wells]

Hi Todd

Thanks for replying, below is my current install information

Current ( STASH and GIT are installed on the same server ):

STASH ( BitBucket ) = 3.9.2
Git = 2.0.4 ( installed from tar Ball and not from an RPM as the RPM was too old.
Centos = 6.6

Required:

BitBucket = 5.2
Git = 2.2 + and above

https://confluence.atlassian.com/bitbucketserver/supported-platforms-776640981.html

As you can see my version of git is not supported with the current version of bitbucket. I will have to perform a two stage upgrade anyway as the version of STASH I am running cannot be upgraded directly to bitbucket 5.2 as well.

Is there an easy way just to install a higher support version of git like 2.9 on the same server and then move all the repos and basically everything across. Can you install another TAR ball later version on top of another git , so it's like overwriting it. 


Kind regards,

James Wells | Operations and Regional Account Manager ANZ        

www.statseeker.com

This email is intended only for the entity or individual to whom it is addressed and may contain information that is privileged or confidential. If you are not the intended recipient, you are hereby notified that distribution, copying or any form of dissemination of the content of this email is strictly prohibited. If you have received this email in error, please advise us immediately by return email and destroy the original message. Thank you.


-----Original Message-----
From: Todd Zullinger [mailto:todd.zullinger@gmail.com] On Behalf Of Todd Zullinger
Sent: Tuesday, 8 August 2017 3:08 AM
To: Ævar Arnfjörð Bjarmason
Cc: James Wells; git@vger.kernel.org
Subject: Re: upgarding GIT

Ævar Arnfjörð Bjarmason wrote:
> On Mon, Aug 07 2017, James Wells jotted:
>> I am fairly new to git, however I have a challenge of upgrading git 
>> from 2.0.4 to 2.4.12 and my initial 2.0.4 install was done via TAR 
>> BALL on my server.
>>
>> I have a centos server running git and Atlassian STASH and my 
>> challenge is for me to upgrade the STASH application I need to move 
>> to a newer version of git.

Which release of CentOS are you using James?  And what git version is required for the Atlassian Stash (which is now called Bitbucket) release you're trying to use?  IIRC, they support as far back as git 1.8?

> You're going to want to install git via RPM/yum. CentOS already has a 
> package for it.

Indeed.  (But I'm biased because I would never, ever install software via 'sudo make install' on anything other than a throw-away test
instance.)

The one problem folks run into on CentOS/RHEL is that the versions may be somewhat old.  CentOS/RHEL 6 ships with git 1.7.1, for instance. 
CentOS/RHEL 7 is only a little newer, with git 1.8.3.  There are "software collections" which provide git 1.9¹ and 2.9², but personally I've never liked using software collections for software that I need to integrate with other tools.

For users of CentOS/RHEL who want to run the current git release in a packaged form, the Fedora git package maintainers take care to ensure that the Fedora packages can be built for the current supported releases of CentOS/RHEL (6 & 7 at the moment).  Grabbing the current code and/or srpm from Fedora should (almost³) always build cleanly using the mock build tool for CentOS/RHEL.

I also try to keep a semi-official COPR repo up to date, here:

    https://copr.fedorainfracloud.org/coprs/g/git-maint/git/

(Even as the primary maintainer of that repo, I'd still suggest that it's wise to either mirror it locally or rebuild the srpm's in your own infrastructure, to ensure that if the copr service is ever down you can reinstall important systems.)

¹ https://www.softwarecollections.org/en/scls/rhscl/git19/
² https://www.softwarecollections.org/en/scls/rhscl/rh-git29/
³ Right now, there's a slight issue building the current git for
  CentOS 7 because RHEL 7.4 moved the pcre2 package from EPEL into
  RHEL and CentOS 7.4 is not yet built.  The Fedora packages are
  built against pcre2 now (thanks Ævar ;).  So for a few weeks it
  won't be possible to build them for CentOS 7 without a minor change.

-- 
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ocean, n. A body of water occupying about two-thirds of a world made
for man -- who has no gills.
    -- Ambrose Bierce, "The Devil's Dictionary"

Re: upgarding GIT

[Bryan Turner]

On Mon, Aug 7, 2017 at 4:20 PM, James Wells <james.wells@statseeker.com> wrote:
>
> As you can see my version of git is not supported with the current version of bitbucket. I will have to perform a two stage upgrade anyway as the version of STASH I am running cannot be upgraded directly to bitbucket 5.2 as well.
>
> Is there an easy way just to install a higher support version of git like 2.9 on the same server and then move all the repos and basically everything across. Can you install another TAR ball later version on top of another git , so it's like overwriting it.

Hey James, Bitbucket Server developer here. Sorry for not responding
sooner. I just wanted to check in with you and see if you'd gotten
this all resolved? If not, feel free to message me directly; I'm happy
to help you off the list. (Or on list, for that matter; I just figure
the general Git list isn't interested in this issue.)

Best regards,
Bryan Turner