Home → Problems →

Gem sources in paths don't work

Admin Functions

• Remove

Chris Lloyd

08 Jan, 2011 11:57 AM

If I do "gem sources -a http://foo.com/abc" the command fails because Rubygems searches for http://foo.com/specs.4.8.gz instead of http://foo.com/abc/specs.4.8.gz`. Whilst I understand why it would do this, I believe the correct behaviour would be concat the path.

This boils down to line 239 of spec_fetcher.rb with the URI instance. + is really an alias for merge, which isn't really the behavior you want here.

1. Support Staff 2 Posted by Nick Quaranto on 18 Jan, 2011 03:51 AM

   

   Ugh :( The gem server code is such a pain. Patches are certainly welcome for this!

   Admin Functions

   • Remove

2. Support Staff 3 Posted by Nick Quaranto on 18 Jan, 2011 03:52 AM

   

   That being said, maybe geminabox or stickler will treat this right. Let me know if either of these work.

   https://github.com/cwninja/geminabox
   https://github.com/copiousfreetime/stickler

   Admin Functions

   • Remove

3. 4 Posted by Chris Lloyd on 18 Jan, 2011 05:03 AM

   

   The problem is with the Rubygems CLI not the server code (Phewf!). The offending code is pretty simple and the fix would probably look like:

   spec_path = source_uri.dup
   spec_path.path += "/#{file_name}.gz"
   

   Though that is totally untested. Probably would also have to check for the case where the source_uri ends in a slash. I would submit a patch but my laptop is in the mothership :(

   Admin Functions

   • Split
   • Remove

4. Support Staff 5 Posted by Nick Quaranto on 27 May, 2011 12:25 AM

   

   Wow, this ticket hasn't been updated in forever. That class has had a lot of changes but would still accept patches for this. Hit us with a pull request please! :)

   Admin Functions

   • Remove

5. Nick Quaranto closed this discussion on 27 May, 2011 12:25 AM.

Comments are currently closed for this discussion. You can start a new one.