On Monday, November 17, 2014 12:43:18 PM UTC+8, R N wrote:
> The installer didn't produce any errors, but when push something to
> a repo I get errors
>
> git push
> Counting objects: 14, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (10/10), done.
> Writing objects: 100% (11/11), 9.29 KiB | 0 bytes/s, done.
> Total 11 (delta 4), reused 0 (delta 0)
> remote:
> /opt/rubies/ruby-1.9.3-p484/lib/ruby/gems/1.9.1/gems/bundler-1.6.2/lib/bundler/spec_set.rb:92:in
> `block in materialize': Could not find rake-10.3.2 in any of the sources
> (Bundler::GemNotFound)
> remote: from
> /opt/rubies/ruby-1.9.3-p484/lib/ruby/gems/1.9.1/gems/bundler-1.6.2/lib/bundler/spec_set.rb:85:in
> `map!'
> remote: from
> /opt/rubies/ruby-1.9.3-p484/lib/ruby/gems/1.9.1/gems/bundler-1.6.2/lib/bundler/spec_set.rb:85:in
> `materialize'
> remote: from
> /opt/rubies/ruby-1.9.3-p484/lib/ruby/gems/1.9.1/gems/bundler-1.6.2/lib/bundler/definition.rb:133:in
> `specs'
> remote: from
> /opt/rubies/ruby-1.9.3-p484/lib/ruby/gems/1.9.1/gems/bundler-1.6.2/lib/bundler/definition.rb:178:in
> `specs_for'
> remote: from
> /opt/rubies/ruby-1.9.3-p484/lib/ruby/gems/1.9.1/gems/bundler-1.6.2/lib/bundler/runtime.rb:13:in
> `setup'
> remote: from
> /opt/rubies/ruby-1.9.3-p484/lib/ruby/gems/1.9.1/gems/bundler-1.6.2/lib/bundler.rb:127:in
> `setup'
> remote: from
> /opt/rubies/ruby-1.9.3-p484/lib/ruby/gems/1.9.1/gems/bundler-1.6.2/lib/bundler.rb:132:in
> `require'
> remote: from
> /var/www/gitorious/repositories/configs/configs.git/hooks/messaging.rb:49:in
> `<top (required)>'
> remote: from
> /opt/rubies/ruby-1.9.3-p484/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
> `require'
> remote: from
> /opt/rubies/ruby-1.9.3-p484/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
> `require'
> remote: from hooks/post-receive:26:in `<main>'
> remote: => Syncing Gitorious... To
> ssh://[email protected]:9422/configs/configs.git
> 5d1fe13..c67bbf4 master -> master
>
> This is what's in the ce-installer folder. I
>
> pwd
> /var/www/gitorious/ce-installer
> -bash-4.1$ git log | head
> commit f767849d3e7702eb0db7994a994dd6071b2c8564
> Author: Marcin Kulik <[email protected]>
> Date: Wed Oct 1 17:33:44 2014 +0200
>
> Remove buggy https configuration
>
> commit 4fed69a151dd652209d66d2e111281660b0cfac6
> Author: Marcin Kulik <[email protected]>
> Date: Wed Oct 1 13:10:07 2014 +0200
>
> I only fixed "git checkout $GITORIOUS_VERSION -f" according to
> http://comments.gmane.org/gmane.comp.version-control.gitorious/5382
>
> Web-interface doesn't show updates in activity or feeds, but repos seems to
> be updated fine, nor git client complains.
>
> Thanks,
> --Roman
Roman,
Noticed the same issue myself.
With 3.1, ruby is upgraded to 2.0.0...
install-ruby.sh in ce-installer has the following at the end:
if [ ! -f /etc/profile.d/chruby.sh ]; then
echo "Set up 2.0 as default ruby version"
echo "source /usr/local/share/chruby/chruby.sh && chruby
$FACTER_ruby_version" >> /etc/profile.d/chruby.sh
chmod a+x /etc/profile.d/chruby.sh
fi
echo "Ruby 2.0 installed, ready on next login/new shell."
If this is an upgrade, and you previously had ruby 1.9.3,
/etc/profile.d/chruby.sh is saying to set to that old version, install-ruby.sh
doesn't change that - it only sets 2.0.0 to default if there way nothing set
prior... Unfortunately upgrade.sh doesn't change this either.
A quick fix is to run chruby without options to get the 2.0 release string and
manually replace the 1.9 one in /etc/profile.d/chruby.sh and restart
services/reboot.
What probably needs to happen to prevent this happening is that either
install-ruby.sh or upgrade.sh need to replace /etc/profile.d/chruby.sh in the
event of an upgrade rather than leaving whatever was there before.
Thanks,
d
--
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
---
You received this message because you are subscribed to the Google Groups
"Gitorious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
