Bug 1308738 - Unable to fetch remote gems
Summary: Unable to fetch remote gems
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-gem2rpm
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-15 22:11 UTC by Matt Spaulding
Modified: 2016-02-22 13:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-22 13:04:41 UTC
Type: Bug


Attachments (Terms of Use)

Description Matt Spaulding 2016-02-15 22:11:24 UTC
Description of problem:
gem2spec is not able to download gems when using the "--fetch" command line argument.  This is due to a redirect from http to https which is forbidden.

Version-Release number of selected component (if applicable):
0.11.2-1

How reproducible:
Every time

Steps to Reproduce:
1. Run command such as: gem2rpm --fetch -s librarian-puppet

Actual results:

/usr/share/ruby/open-uri.rb:224:in `open_loop': redirection forbidden: http://rubygems.org/api/v1/gems/librarian-puppet.json -> https://rubygems.org/api/v1/gems/librarian-puppet.json (RuntimeError)
	from /usr/share/ruby/open-uri.rb:150:in `open_uri'
	from /usr/share/ruby/open-uri.rb:716:in `open'
	from /usr/share/ruby/open-uri.rb:34:in `open'
	from /usr/share/gems/gems/gem2rpm-0.11.2/bin/gem2rpm:103:in `<top (required)>'
	from /usr/bin/gem2rpm:23:in `load'
	from /usr/bin/gem2rpm:23:in `<main>'


Expected results:

Gem file is downloaded and source rpm is built.

Additional info:

I edited the gem2rpm source to use https instead of http and that fixed the problem for me.

Comment 1 Vít Ondruch 2016-02-22 13:04:41 UTC
Hi and thanks for the report.

By coincidence, this was recently reported upstream:

https://github.com/fedora-ruby/gem2rpm/issues/55

If you don't mind, I am closing this ticket in favor of the upstream ticket. Feel free to reopen if you have any additional concerns.


Note You need to log in before you can comment on or make changes to this bug.