From: James Wells <james.wells@statseeker.com>
To: "Todd Zullinger" <tmz@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: upgarding GIT
Date: Mon, 7 Aug 2017 23:20:30 +0000 [thread overview]
Message-ID: <f5d92196d19a4029bb4e282837c53a46@statseeker.com> (raw)
In-Reply-To: <20170807170745.GG25542@zaya.teonanacatl.net>
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"
next prev parent reply other threads:[~2017-08-07 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 6:08 upgarding GIT James Wells
2017-08-07 11:09 ` Ævar Arnfjörð Bjarmason
2017-08-07 17:07 ` Todd Zullinger
2017-08-07 23:20 ` James Wells [this message]
2017-08-17 21:42 ` Bryan Turner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f5d92196d19a4029bb4e282837c53a46@statseeker.com \
--to=james.wells@statseeker.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=tmz@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).