-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add debug enabled rubygems to track down nil spec issue #439
Conversation
your debug steps LGTM |
Changes to rubygems thus far danielsdeleo/rubygems@a2089e4 Tried to make a PR against my fork, it's got a lot of extra crap in there from upstream, though: danielsdeleo/rubygems#1 |
Also, a similar bug report: https://bugs.ruby-lang.org/issues/9366 |
3e77357
to
b4f1454
Compare
a4848e9
to
2dad866
Compare
👍 |
LGTM |
@chef/omnibus-maintainers I originally said I didn't want to merge this but I haven't had any luck tracking down the rubygems problem with just ad-hoc builds, so I would like to use my patched version of rubygems in ChefDK until we can figure out what's going on. |
👍 |
2dad866
to
ccfe1e8
Compare
👍 |
This is a bunch of commits squashed because I was kinda sloppy in development: Add debug enabled rubygems to track down nil spec issue Use static tarball from github release Try to pull rubygems from git since we're not using an official release fix some issues with customized rubygems Omnibus doesn't seem to like overriding URL source w/ git Build rubygems from source on windows Fix building rubygems from source on windows
ccfe1e8
to
8d2a230
Compare
We've been having no success in tracking down this rubygems bug with just ad-hoc builds, so I would like to switch ChefDK to my patched branch until we can figure out what's going on.