{"thread":{"id":"46524","subject":"upgarding GIT","startedAt":"2017-08-07T06:08:37Z","lastAt":"2017-08-17T21:42:24Z","messageCount":5,"participants":["James Wells","Ævar Arnfjörð Bjarmason","Todd Zullinger","Bryan Turner"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"325668","messageId":"9a2576ed8b7146459585af4238613286@statseeker.com","threadId":"46524","inReplyTo":null,"subject":"upgarding GIT","fromName":"James Wells","fromEmail":"james.wells@statseeker.com","sentAt":"2017-08-07T06:08:32Z","receivedAt":"2017-08-07T06:08:37Z","isPatch":false,"sender":{"key":"james.wells@statseeker.com","avatar":null},"body":"Hi All\n\nI 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.\n\nI 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.\n\nHow 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.\n\nAny assistance is most welcome and I would appreciate your feedback or comments on how you would go about achieving this task.\n\nThanks\nJ\n\n\n\n\n\n\n\n\n"},{"id":"325678","messageId":"871sonzlar.fsf@gmail.com","threadId":"46524","inReplyTo":"9a2576ed8b7146459585af4238613286@statseeker.com","subject":"Re: upgarding GIT","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2017-08-07T11:09:32Z","receivedAt":"2017-08-07T11:09:40Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Mon, Aug 07 2017, James Wells jotted:\n\n> Hi All\n>\n> 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.\n>\n> 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.\n>\n> 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.\n>\n> Any assistance is most welcome and I would appreciate your feedback or comments on how you would go about achieving this task.\n>\n> Thanks\n> J\n\nThis is really a question of \"hey I ran 'make install' on this thing in\nthe past, how do I now upgrade it?\". There's nothing git-specific about\nthis, git doesn't do anything special that 99% of the software you run\non CentOS wouldn't do in this scenario.\n\nI'm not saying this to be an unhelpful smartass, but just to point out\nthat to look for a solution you don't need to search for e.g. \"how to\nreplace git package\" on Google, but just how to replace manually\ninstalled packages in general.\n\nYou're going to want to install git via RPM/yum. CentOS already has a\npackage for it.\n\nIt may fail because of existing files, you can likely force it or\nmanually remove the files first.\n\nBe careful not to end up with directories which contain some\nFrankensteinian combination of old tar.gz installed files & newly\ninstalled files. You can use RPM to list what package owns given files,\nyou should manually remove e.g. some git-whatever command that's not\nmanaged by rpm living alongside your newly installed stuff.\n"},{"id":"325697","messageId":"20170807170745.GG25542@zaya.teonanacatl.net","threadId":"46524","inReplyTo":"871sonzlar.fsf@gmail.com","subject":"Re: upgarding GIT","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2017-08-07T17:07:45Z","receivedAt":"2017-08-07T17:07:58Z","isPatch":false,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Ævar Arnfjörð Bjarmason wrote:\n> On Mon, Aug 07 2017, James Wells jotted:\n>> I am fairly new to git, however I have a challenge of upgrading git \n>> from 2.0.4 to 2.4.12 and my initial 2.0.4 install was done via TAR \n>> BALL on my server.\n>>\n>> I have a centos server running git and Atlassian STASH and my \n>> challenge is for me to upgrade the STASH application I need to move \n>> to a newer version of git.\n\nWhich release of CentOS are you using James?  And what git version is \nrequired for the Atlassian Stash (which is now called Bitbucket) \nrelease you're trying to use?  IIRC, they support as far back as git \n1.8?\n\n> You're going to want to install git via RPM/yum. CentOS already has a \n> package for it.\n\nIndeed.  (But I'm biased because I would never, ever install software \nvia 'sudo make install' on anything other than a throw-away test \ninstance.)\n\nThe one problem folks run into on CentOS/RHEL is that the versions may \nbe somewhat old.  CentOS/RHEL 6 ships with git 1.7.1, for instance. \nCentOS/RHEL 7 is only a little newer, with git 1.8.3.  There are \n\"software collections\" which provide git 1.9¹ and 2.9², but personally \nI've never liked using software collections for software that I need \nto integrate with other tools.\n\nFor users of CentOS/RHEL who want to run the current git release in a \npackaged form, the Fedora git package maintainers take care to ensure \nthat the Fedora packages can be built for the current supported \nreleases of CentOS/RHEL (6 & 7 at the moment).  Grabbing the current \ncode and/or srpm from Fedora should (almost³) always build cleanly \nusing the mock build tool for CentOS/RHEL.\n\nI also try to keep a semi-official COPR repo up to date, here:\n\n    https://copr.fedorainfracloud.org/coprs/g/git-maint/git/\n\n(Even as the primary maintainer of that repo, I'd still suggest that \nit's wise to either mirror it locally or rebuild the srpm's in your \nown infrastructure, to ensure that if the copr service is ever down \nyou can reinstall important systems.)\n\n¹ https://www.softwarecollections.org/en/scls/rhscl/git19/\n² https://www.softwarecollections.org/en/scls/rhscl/rh-git29/\n³ Right now, there's a slight issue building the current git for \n  CentOS 7 because RHEL 7.4 moved the pcre2 package from EPEL into \n  RHEL and CentOS 7.4 is not yet built.  The Fedora packages are \n  built against pcre2 now (thanks Ævar ;).  So for a few weeks it \n  won't be possible to build them for CentOS 7 without a minor change.\n\n-- \nTodd\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nOcean, n. A body of water occupying about two-thirds of a world made\nfor man -- who has no gills.\n    -- Ambrose Bierce, \"The Devil's Dictionary\"\n\n"},{"id":"325776","messageId":"f5d92196d19a4029bb4e282837c53a46@statseeker.com","threadId":"46524","inReplyTo":"20170807170745.GG25542@zaya.teonanacatl.net","subject":"RE: upgarding GIT","fromName":"James Wells","fromEmail":"james.wells@statseeker.com","sentAt":"2017-08-07T23:20:30Z","receivedAt":"2017-08-07T23:20:40Z","isPatch":false,"sender":{"key":"james.wells@statseeker.com","avatar":null},"body":"Hi Todd\n\nThanks for replying, below is my current install information\n\nCurrent ( STASH and GIT are installed on the same server ):\n\nSTASH ( BitBucket ) = 3.9.2\nGit = 2.0.4 ( installed from tar Ball and not from an RPM as the RPM was too old.\nCentos = 6.6\n\nRequired:\n\nBitBucket = 5.2\nGit = 2.2 + and above\n\nhttps://confluence.atlassian.com/bitbucketserver/supported-platforms-776640981.html\n\nAs 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.\n\nIs 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. \n\n\nKind regards,\n\nJames Wells | Operations and Regional Account Manager ANZ        \n\nwww.statseeker.com\n\nThis 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.\n\n\n-----Original Message-----\nFrom: Todd Zullinger [mailto:todd.zullinger@gmail.com] On Behalf Of Todd Zullinger\nSent: Tuesday, 8 August 2017 3:08 AM\nTo: Ævar Arnfjörð Bjarmason\nCc: James Wells; git@vger.kernel.org\nSubject: Re: upgarding GIT\n\nÆvar Arnfjörð Bjarmason wrote:\n> On Mon, Aug 07 2017, James Wells jotted:\n>> I am fairly new to git, however I have a challenge of upgrading git \n>> from 2.0.4 to 2.4.12 and my initial 2.0.4 install was done via TAR \n>> BALL on my server.\n>>\n>> I have a centos server running git and Atlassian STASH and my \n>> challenge is for me to upgrade the STASH application I need to move \n>> to a newer version of git.\n\nWhich 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?\n\n> You're going to want to install git via RPM/yum. CentOS already has a \n> package for it.\n\nIndeed.  (But I'm biased because I would never, ever install software via 'sudo make install' on anything other than a throw-away test\ninstance.)\n\nThe 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. \nCentOS/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.\n\nFor 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.\n\nI also try to keep a semi-official COPR repo up to date, here:\n\n    https://copr.fedorainfracloud.org/coprs/g/git-maint/git/\n\n(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.)\n\n¹ https://www.softwarecollections.org/en/scls/rhscl/git19/\n² https://www.softwarecollections.org/en/scls/rhscl/rh-git29/\n³ Right now, there's a slight issue building the current git for\n  CentOS 7 because RHEL 7.4 moved the pcre2 package from EPEL into\n  RHEL and CentOS 7.4 is not yet built.  The Fedora packages are\n  built against pcre2 now (thanks Ævar ;).  So for a few weeks it\n  won't be possible to build them for CentOS 7 without a minor change.\n\n-- \nTodd\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nOcean, n. A body of water occupying about two-thirds of a world made\nfor man -- who has no gills.\n    -- Ambrose Bierce, \"The Devil's Dictionary\"\n\n"},{"id":"326651","messageId":"CAGyf7-GkLj-kSiLJJYA4HkYpnMWLubXdL+h_Auo4jw9R=4_XLQ@mail.gmail.com","threadId":"46524","inReplyTo":"f5d92196d19a4029bb4e282837c53a46@statseeker.com","subject":"Re: upgarding GIT","fromName":"Bryan Turner","fromEmail":"bturner@atlassian.com","sentAt":"2017-08-17T21:42:15Z","receivedAt":"2017-08-17T21:42:24Z","isPatch":false,"sender":{"key":"bturner@atlassian.com","avatar":"https://gravatar.com/avatar/16bcf3167981c1ef7c804e502642366d888a35b0d0b0a4ca01fdc442aa1acb1e?d=mp&s=160"},"body":"On Mon, Aug 7, 2017 at 4:20 PM, James Wells <james.wells@statseeker.com> wrote:\n>\n> 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.\n>\n> 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.\n\nHey James, Bitbucket Server developer here. Sorry for not responding\nsooner. I just wanted to check in with you and see if you'd gotten\nthis all resolved? If not, feel free to message me directly; I'm happy\nto help you off the list. (Or on list, for that matter; I just figure\nthe general Git list isn't interested in this issue.)\n\nBest regards,\nBryan Turner\n"}]}