Activity (RSS)

Dumb markdown/lighthouse - here is the config again (last try):

defaults:
  install_options: --source=http://gems.rubyforge.org --source=http://gems.github.com...

I can't reproduce this. Here's what I tried:

• Start a local gem server with dummy gems: http://github.com/thewoolleyman/...

• Create the following dummy confi...

also please attach the geminstaller.yml and a new failure message after you add the default sources (if it still fails).

You don't have all those sources specified in your geminstaller.yml: install options = '--no-ri --no-rdoc'. You should put them all listed as sources in your de...

we were trying to install fastthread through geminstaller, but our first mirror didn't have it. geminstaller fails, w/ stack trace below several times.

however,...

perhaps have a --gemspec [File | Gem::Specification] option. Could allow control of runtime vs. dev, or just install them all...

Thanks for the report.

This is a duplicate of http://thewoolleyweb.lighthousea...

It was a bug in RubyGems where these options were not handled properly when i...

I'm probably doing something wrong, but I can't seem to pass the build options when installing the mysql gem.

Here's my geminstaller.yml: - name: mysql version:...

Eric Hodel says this is because of the say Gem::GemRunner works - it stores the source. As a workaround, every install call to GemRunner can be prefixed with th...

Chad, patch attached. It's a simple one-liner as we discussed. Seems to do the trick for me. In addition to OSX + RubyGems 1.3.1 + 1.8.6-p114, I also verified i...

From Josh Susser "We should modify the rails command to take an option to work with GemInstaller instead of using config.gem. This would allow using the same DS...

AHA! This seems to only happen when the previous gem specified a different source. For example:

- name: mislav-will_paginate
  version: >= 2.3.6
  install_opti...

...because $stderr and STDERR are not the same. See geminstaller.rb.

Fixed in release 0.5.1

This message is printed: "GemInstaller is automatically requiring gems: geminstaller >= 0.5.1..."

...even if no_autogem: true is specified for the gem in gemins...

Update. Need to confirm from RubyGems dev team whether the default autoinstall to ~/.gem will stick around under Ruby 1.9...

Not sure if multiple retries would cause more problems, since this error can also occur if the gem or server actually doesn't exist.

As a compromise, a much mor...

Just tried this locally, and it worked fine. I don't think it has anything to do with the version, I think it is because sometimes gems just fail to install via...

For some reason, the following gems did not install.

• name: rr version: 0.7.1
• name: engineyard-eycap version: 0.3.11 install_options: --source=http://gems.githu...

Eric hodel has said that the default support for ~/.gem may not even be left in RubyGems, due to issues with 1.9 compatibility (Matz doesn't want to read the fi...

I haven't seen this for a while, and a quick search of the rubygems tracker turns up nothing (although that is hard to tell for sure from the rubyforge search i...

Whatever this problem was, I'm pretty sure you could overcome it with the gem-ordering patch in release 0.5.0:

http://thewoolleyweb.lighthousea...

Closing this...

I'm not sure this exactly fits the request here, but I finally got around to redoing my patch with some test coverage this time. It adds a -o option that acts m...

Fixed in release 0.5.0.

This is fixed in RubyGems trunk, just waiting for release...

I have a patch for this. It's mostly untested but it works really fast since it's only checking against the local gems (no remoteness involved). I've been meani...

@Jeff,

Is this for a top level gem (listed in geminstaller.yml) or a dependency of one of the top level gems (not listed in geminstaller.yml)?

If your problem i...

I'm running into this situation yet again because I've got multiple projects using geminstaller, but I need to be able to run different versions of the gems on ...

I agree, this would be really nice. Right now, I'm using script/runner under rails to run GemInstaller::autogem, and using that as a conditional in my shell scr...

This is a rubygems bug:

http://rubyforge.org/tracker/ind...

Lets try that second link again:

http://rubyforge.org/pipermail/r...

This looks like several errors. The first looks like a connection error - unless for some reason you don't have RubyGems 1.3.1 installed, which had cache errors...

Here is my geminstaller.yml file http://gist.github.com/raw/35183...

Here are my errors: http://gist.github.com/raw/35183...

From Steve Conover:

fyi changing that case statement in output_filter.rb from using :'s to then's makes it so gemisntaller runs under 1.9.1

Yes, but if another gem behaves badly and specifies explicit dependencies when it should not, you can still get these problems.

See these tickets for an example...

However, I would expect the following to work:

rails >= 1.5 rails >= 2.0

Yes, you can only activate exactly one version of a given gem at a time. You can't activate two different versions.

Never mind, thats what geminstaller does.

It looks like Gem.activate causes an error if the gem is activated again with a different version. This is true even w...

I think this has to do with geminstaller.yml invoking the gem method and requiring the gem in one shot. What should happen is geminstaller should invoke the gem...

It would be nice if there was an option similar to --print-rogue-gems which printed only the missing/outdated gems for your project.

The (arguable) root cause of this bug is reported here:

http://sod.lighthouseapp.com/pro...

Although there should still be a way to specify gem processing orde...

This is now the default under RubyGems >= 1.3.0, but there are some bugs if you have .gemrc point gemhome and gempath to only ~/.gem, at least on Leopard. See d...