Re: [gitorious] How to find the which Gitorious version I am running on ?

549 views
Skip to first unread message

Thomas Kjeldahl Nilsson

unread,
Jan 15, 2013, 4:25:13 AM1/15/13
to gito...@googlegroups.com
Sure thing: if you're on an official version/release/tag, you can run the following command from the root of your Gitorious installation (ie. same dir as the Gemfile etc)

rake versioning:changelog 

The changelog command should output the available versions you've pulled down from the gitorious mainline repo, as well as the current version of your Gitorious installation.

If all else fails, you can check the version manually by finding the "VERSION = "X.Y.Z"" line near the start of the lib/gitorious.rb file.

--
Best regards,
Thomas Kjeldahl Nilsson,
Partner & Programmer,
Gitorious AS

On Monday, January 14, 2013 at 8:42 PM, Dinux6 wrote:

I installed Gitorious on my unix server from master(git://gitorious.org/gitorious/mainline.git) sometime last December. Is there a way to find which version of Gitorious I am running on ?

--
To post to this group, send email to gito...@googlegroups.com
To unsubscribe from this group, send email to
gitorious+...@googlegroups.com

Marius Mårnes Mathiesen

unread,
Jan 18, 2013, 2:34:04 AM1/18/13
to gito...@googlegroups.com

Thomas Kjeldahl Nilsson writes:

> Sure thing: if you're on an official version/release/tag, you can run
> the following command from the root of your Gitorious installation
> (ie. same dir as the Gemfile etc)
>
> rake versioning:changelog

<insert periodic reminder to use bin/rake wherever appropriate>

:-)
- Marius

Marius Mårnes Mathiesen

unread,
Apr 2, 2013, 8:30:47 AM4/2/13
to gito...@googlegroups.com

shn...@gmail.com writes:

> I followed those instructions and tried to upgrade from v2.3.2 to v2.4.9.
>
> Everything looked like it ran well, however, when I check the version it
> still shows v2.3.2. I checked lib/gitorious.rb and it confirmed the older
> version.
>
> Here is the output. Am I missing something pretty obvious? I am not a
> Ruby developer so it is possible it is something trivial. I don't
> understand the "it was installed into RAILS_ENV=production" line.
> Typically that represents an environment variable.
>
> ----------
>> script/upgrade_to 2.4.9

I think you'll need to specify the name of the tag for this to work, ie

script/upgrade_to v2.4.9

Cheers,
- Marius

> UPGRADE: About to attempt Gitorious upgrade. Please backup first. Proceed
> with upgrade? (y/n)
> y
> UPGRADE: Attempting upgrade to 2.4.9...
> UPGRADE: Fetching latest Gitorious code from the origin remote (should be
> gitorious.org)...
> remote: Counting objects: 287, done.
> remote: Compressing objects: 100% (111/111), done.
> remote: Total 164 (delta 126), reused 65 (delta 52)
> Receiving objects: 100% (164/164), 41.47 KiB, done.
> Resolving deltas: 100% (126/126), completed with 58 local objects.
> From git://gitorious.org/gitorious/mainline
> 1dc69a9..9416467 2.x-stable -> origin/2.x-stable
> * [new branch] feature/improved-snapshotting ->
> origin/feature/improved-snapshotting
> * [new branch] gitorious/2.x-stable -> origin/gitorious/2.x-stable
> * [new branch] gitorious/feature/improved-snapshotting ->
> origin/gitorious/feature/improved-snapshotting
> 6408eb5..37aa7fa master -> origin/master
> a1303c4..8e5826c next -> origin/next
> * [new tag] show -> show
> * [new tag] tmptag -> tmptag
> * [new tag] v2.4.12 -> v2.4.12
>
> UPGRADE: Preparing data needed by script/undo_last_upgrade...
>
>
> UPGRADE: Git checking out the '2.4.9' tag
> error: pathspec '2.4.9' did not match any file(s) known to git.
>
> UPGRADE: Updating submodules...
>
> UPGRADE: Upgrading gem dependencies via Bundler...
> Using rake (0.8.7)
> Using SystemTimer (1.2.3)
> Using activesupport (2.3.14)
> Using activemessaging (0.7.1)
> Using activerecord (2.3.14)
> Using acts-as-taggable-on (2.0.6)
> Using builder (3.0.0)
> Using json (1.5.4)
> Using capillary (1.0.1)
> Using chronic (0.3.0)
> Using cocaine (0.2.1)
> Using daemons (1.1.0)
> Using diff-lcs (1.1.2)
> Using gemcutter (0.6.1)
> Using json_pure (1.6.5)
> Using rubyforge (2.0.4)
> Using echoe (4.3.1)
> Using eventmachine (0.12.10)
> Using exception_notification (1.0.20090728)
> Using thor (0.14.6)
> Using foreman (0.41.0)
> Using geoip (0.8.9)
> Using hodel_3000_compliant_logger (0.1.0)
> Using hoe (2.8.0)
> Using just_paginate (0.0.6)
> Using kgio (2.7.4)
> Using mime-types (1.16)
> Using mysql (2.8.1)
> Using nokogiri (1.5.0)
> Using oauth (0.4.4)
> Using paperclip (2.4.5)
> Using proxymachine (1.2.4)
> Using rack (1.0.1)
> Using raindrops (0.10.0)
> Using rdiscount (1.3.1.1)
> Using redis (2.2.2)
> Using redis-namespace (0.7.0)
> Using sinatra (1.0)
> Using vegas (0.1.11)
> Using resque (1.9.8)
> Using revo-ssl_requirement (1.1.0)
> Using riddle (1.2.2)
> Using ruby-hmac (0.4.0)
> Using ruby-net-ldap (0.0.4)
> Using ruby-openid (2.1.8)
> Using ruby-yadis (0.3.4)
> Using state_machine (0.9.4)
> Using stomp (1.1)
> Using stompserver (0.9.9)
> Using thin (1.2.7)
> Using unicorn (4.3.1)
> Using validates_url_format_of (0.1.1)
> Using will_paginate (2.3.15)
> Using bundler (1.0.17)
> Your bundle is complete! It was installed into ./RAILS_ENV=production
> UPGRADE: Migrating database...
> (in /var/www/gitorious/app)
> UPGRADE: Clearing asset pipeline...
> (in /var/www/gitorious/app)
> Removed generated stylesheets and javascripts
> UPGRADE: Restarting Gitorious...
>
> UPGRADE: Done, upgraded to 2.4.9.
>
> ATTENTION: Please test and verify that your site works as expected. If any
> errors occur, rollback to the pre-upgrade state with
> script/undo_last_upgrade
>
> Thanks,
> Scott
>
> --
Reply all
Reply to author
Forward
0 new messages