Gem sources configured with .gemrc

Matt_Juszczak · March 6, 2015, 8:13pm

Referencing this thread:

http://lists.opscode.com/sympa/arc/chef/2013-12/msg00236.html

I’m having the exact same issue. Tyler, if you’re on this list, did you ever find a resolution to it? Alternatively, has anyone encountered a way to resolve it? Attempts to refresh the Gem.configuration do not work for us per:

https://docs.chef.io/resource_gem_package.html

Thanks for any help!

-Matt

Chip · March 6, 2015, 11:12pm

This should do what you’re looking for:

Thanks,
–Charles

Charles Johnson — Product Engineer
(510) 545-9485 – charles@chef.io – my: Linkedin Twitter

CHEF

TM
chef.io Blog Facebook Twitter Youtube

On March 6, 2015 at 12:15:00 PM, Matt Juszczak (matt@atopia.net) wrote:

Referencing this thread:

http://lists.opscode.com/sympa/arc/chef/2013-12/msg00236.html

I’m having the exact same issue. Tyler, if you’re on this list, did you ever find a resolution to it? Alternatively, has anyone encountered a way to resolve it? Attempts to refresh the Gem.configuration do not work for us per:

https://docs.chef.io/resource_gem_package.html

Thanks for any help!

-Matt

Matt_Juszczak · March 7, 2015, 7:05pm

It doesn't seem to work. In looking at the source, it seems to hard-code rubygems as the gem source when you specify a gem binary. Kind of confused.

github.com

chef/chef/blob/6eae70225008c8b06601a8343a3f57cb10f3c065/lib/chef/provider/package/rubygems.rb#L537


      
          end
          
          def gem_binary_path
            @new_resource.gem_binary || 'gem'
          end
          
          def install_via_gem_command(name, version)
            if @new_resource.source =~ /\.gem$/i
              name = @new_resource.source
            else
              src = @new_resource.source && "  --source=#{@new_resource.source} --source=https://rubygems.org"
            end
            if !version.nil? && version.length > 0
              shell_out!("#{gem_binary_path} install #{name} -q --no-rdoc --no-ri -v \"#{version}\"#{src}#{opts}", :env=>nil)
            else
              shell_out!("#{gem_binary_path} install \"#{name}\" -q --no-rdoc --no-ri #{src}#{opts}", :env=>nil)
            end
          end
          
          def upgrade_package(name, version)
            install_package(name, version)

On Mar 6, 2015, at 6:12 PM, Charles Johnson charles@chef.io wrote:

This should do what you're looking for:

Use a .gemrc file with Omnibus chef-client · GitHub

Thanks,
--Charles

Charles Johnson — Product Engineer
(510) 545-9485 – charles@chef.io – my: Linkedin Twitter

CHEF
CHEF.IO

TM
chef.io Blog Facebook Twitter Youtube

On March 6, 2015 at 12:15:00 PM, Matt Juszczak (matt@atopia.net) wrote:

Referencing this thread:

chef - [chef] Gem Sources configured with .gemrc

I’m having the exact same issue. Tyler, if you’re on this list, did you ever find a resolution to it? Alternatively, has anyone encountered a way to resolve it? Attempts to refresh the Gem.configuration do not work for us per:

gem_package Resource

Thanks for any help!

-Matt

Lamont_Granquist · March 8, 2015, 5:23am

Pretty certain I've seen a PR to fix that recently. If its the same
issue, its either merged or close to merged.

On 3/7/15 11:05 AM, Matt Juszczak wrote:

It doesn't seem to work. In looking at the source, it seems to
hard-code rubygems as the gem source when you specify a gem binary.
Kind of confused.

https://github.com/chef/chef/blob/6eae70225008c8b06601a8343a3f57cb10f3c065/lib/chef/provider/package/rubygems.rb#L537

On Mar 6, 2015, at 6:12 PM, Charles Johnson <charles@chef.io
mailto:charles@chef.io> wrote:

This should do what you're looking for:

Use a .gemrc file with Omnibus chef-client · GitHub

Thanks,
--Charles

Charles Johnson — Product Engineer

(510) 545-9485 tel://(510)%20545-9485 – charles@chef.io
mailto:charles@opscode.com – *my: *Linkedin
http://www.linkedin.com/pub/charles-johnson/1/b38/6a5 Twitter
https://twitter.com/chipadeedoodah

CHEF

CHEF.IO http://www.getchef.com/

TM

chef.io http://www.getchef.com/ Blog
http://www.opscode.com/blog/ Facebook
https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/getchefdotcom Youtube
https://www.youtube.com/getchef

On March 6, 2015 at 12:15:00 PM, Matt Juszczak (matt@atopia.net
mailto:matt@atopia.net) wrote:

Referencing this thread:

chef - [chef] Gem Sources configured with .gemrc

I’m having the exact same issue. Tyler, if you’re on this list, did
you ever find a resolution to it? Alternatively, has anyone
encountered a way to resolve it? Attempts to refresh the
Gem.configuration do not work for us per:

gem_package Resource

Thanks for any help!

-Matt

Matt_Juszczak · March 8, 2015, 6:28pm

Referring to this?

github.com/chef/chef

gem_package, chef_gem should not shell out to using https://rubygems.org

chef:master ← chef:pdb/gemserver

opened 04:07PM - 05 Feb 15 UTC

pburkholder

+28 -1

Some users will not be able to use rubygems.org and will specify the remote sour…ce. If their source doesn't have the gem, then `gem` will try the next source. If DNS resolves, then you'll get timeouts. Or even if they are able to use rubygems.org, they may be unpleasantly surprised when the 'rubygems.org' version of a gem appears unexpectedly. I've not added any specs for this, pending discussion, but I will if this seems like the right way to go. Also, given that Hash options provides better control of gem_package options, should we issue a warning when shelling out? --Peter

On Mar 8, 2015, at 12:23 AM, Lamont Granquist lamont@chef.io wrote:

Pretty certain I've seen a PR to fix that recently. If its the same issue, its either merged or close to merged.

On 3/7/15 11:05 AM, Matt Juszczak wrote:
It doesn't seem to work. In looking at the source, it seems to hard-code rubygems as the gem source when you specify a gem binary. Kind of confused.

https://github.com/chef/chef/blob/6eae70225008c8b06601a8343a3f57cb10f3c065/lib/chef/provider/package/rubygems.rb#L537

On Mar 6, 2015, at 6:12 PM, Charles Johnson charles@chef.io wrote:

This should do what you're looking for:

Use a .gemrc file with Omnibus chef-client · GitHub

Thanks,
--Charles

Charles Johnson — Product Engineer
(510) 545-9485 – charles@chef.io – my: Linkedin Twitter

CHEF
CHEF.IO

TM
chef.io Blog Facebook Twitter Youtube

On March 6, 2015 at 12:15:00 PM, Matt Juszczak (matt@atopia.net) wrote:

Referencing this thread:

chef - [chef] Gem Sources configured with .gemrc

I’m having the exact same issue. Tyler, if you’re on this list, did you ever find a resolution to it? Alternatively, has anyone encountered a way to resolve it? Attempts to refresh the Gem.configuration do not work for us per:

gem_package Resource

Thanks for any help!

-Matt

Lamont_Granquist · March 8, 2015, 9:35pm

That is the one.

On 3/8/15 11:28 AM, Matt Juszczak wrote:

Referring to this?

gem_package, chef_gem should not shell out to using https://rubygems.org by pburkholder · Pull Request #2867 · chef/chef · GitHub

On Mar 8, 2015, at 12:23 AM, Lamont Granquist <lamont@chef.io
mailto:lamont@chef.io> wrote:

Pretty certain I've seen a PR to fix that recently. If its the same
issue, its either merged or close to merged.

On 3/7/15 11:05 AM, Matt Juszczak wrote:

It doesn't seem to work. In looking at the source, it seems to
hard-code rubygems as the gem source when you specify a gem binary.
Kind of confused.

https://github.com/chef/chef/blob/6eae70225008c8b06601a8343a3f57cb10f3c065/lib/chef/provider/package/rubygems.rb#L537

On Mar 6, 2015, at 6:12 PM, Charles Johnson <charles@chef.io
mailto:charles@chef.io> wrote:

This should do what you're looking for:

Use a .gemrc file with Omnibus chef-client · GitHub

Thanks,
--Charles

Charles Johnson — Product Engineer

(510) 545-9485 tel://(510)%20545-9485 – charles@chef.io
mailto:charles@opscode.com – *my: *Linkedin
http://www.linkedin.com/pub/charles-johnson/1/b38/6a5 Twitter
https://twitter.com/chipadeedoodah

CHEF

CHEF.IO http://www.getchef.com/

TM

chef.io http://www.getchef.com/ Blog
http://www.opscode.com/blog/ Facebook
https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/getchefdotcom Youtube
https://www.youtube.com/getchef

On March 6, 2015 at 12:15:00 PM, Matt Juszczak (matt@atopia.net
mailto:matt@atopia.net) wrote:

Referencing this thread:

chef - [chef] Gem Sources configured with .gemrc

I’m having the exact same issue. Tyler, if you’re on this list,
did you ever find a resolution to it? Alternatively, has anyone
encountered a way to resolve it? Attempts to refresh the
Gem.configuration do not work for us per:

gem_package Resource

Thanks for any help!

-Matt

Peter_Burkholder3 · March 10, 2015, 4:09pm

Yeah, that's on me. I hope to get to that yet this week.

On Sun, Mar 8, 2015 at 5:35 PM, Lamont Granquist lamont@chef.io wrote:

That is the one.

On 3/8/15 11:28 AM, Matt Juszczak wrote:

Referring to this?

gem_package, chef_gem should not shell out to using https://rubygems.org by pburkholder · Pull Request #2867 · chef/chef · GitHub

On Mar 8, 2015, at 12:23 AM, Lamont Granquist lamont@chef.io wrote:

Pretty certain I've seen a PR to fix that recently. If its the same
issue, its either merged or close to merged.

On 3/7/15 11:05 AM, Matt Juszczak wrote:

It doesn't seem to work. In looking at the source, it seems to hard-code
rubygems as the gem source when you specify a gem binary. Kind of confused.

https://github.com/chef/chef/blob/6eae70225008c8b06601a8343a3f57cb10f3c065/lib/chef/provider/package/rubygems.rb#L537

On Mar 6, 2015, at 6:12 PM, Charles Johnson charles@chef.io wrote:

This should do what you're looking for:

Use a .gemrc file with Omnibus chef-client · GitHub

Thanks,
--Charles

Charles Johnson — Product Engineer

(510) 545-9485 <//%28510%29%20545-9485> – charles@chef.io
charles@opscode.com – *my: *Linkedin
http://www.linkedin.com/pub/charles-johnson/1/b38/6a5 Twitter
https://twitter.com/chipadeedoodah

CHEF

CHEF.IO http://www.getchef.com/

TM

chef.io http://www.getchef.com/ Blog http://www.opscode.com/blog/
Facebook https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/getchefdotcom Youtube
https://www.youtube.com/getchef

On March 6, 2015 at 12:15:00 PM, Matt Juszczak (matt@atopia.net) wrote:

Referencing this thread:

chef - [chef] Gem Sources configured with .gemrc

I’m having the exact same issue. Tyler, if you’re on this list, did you
ever find a resolution to it? Alternatively, has anyone encountered a way
to resolve it? Attempts to refresh the Gem.configuration do not work for us
per:

gem_package Resource

Thanks for any help!

-Matt

--

Peter Burkholder — Customer Success Engineer

Unavailability: Travel March 2-3; Vacation March 16-20; ChefConf March
30-April 3

301-204-5767 – pburkholder@chef.io – *my: *Linkedin
http://www.linkedin.com/in/pburkholder Twitter
http://www.twitter.com/pburkholder Cal
https://www.google.com/calendar/embed?src=pburkholder%40chef.io&mode=WEEK
endar

CHEF

CHEF.IO http://www.chef.io/

TM

chef.io http://www.chef.io/ Blog http://www.chef.io/blog/ Facebook
https://www.facebook.com/getchefdotcom Twitter
https://twitter.com/chef Youtube https://www.youtube.com/getchef

Topic		Replies	Views
[Pre-Release Announcement] Chef 13.0 Chef Infra (archive)	0	941	April 6, 2017
Specifying a remote source with gem_package Chef Infra (archive)	1	381	November 20, 2013
Rubygems source Chef Infra (archive)	2	294	September 11, 2013
chef_gem vs. gem_package Chef Infra (archive)	3	1437	August 6, 2013
chef_gem vs gem_package vs the conundrum Chef Infra (archive)	3	432	August 24, 2012

Gem sources configured with .gemrc

Related topics