Skip to content
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

Remove rainbow dependency, fix duplicate rake gem #2374

Merged
merged 1 commit into from
Dec 7, 2017

Conversation

adamleff
Copy link
Contributor

@adamleff adamleff commented Dec 5, 2017

The version of Rainbow brought in as a direct dependency also depends directly on Rake, and our pin of Rake was inaccurate. This was causing Omnibus to build packages that contained two rake gems which would emit "Unresolved specs during Gem::Specification.reset" warnings when running InSpec.

Rainbow does not appear to be used anywhere in InSpec, so I'm removing it.

Fixes #2105

@adamleff
Copy link
Contributor Author

adamleff commented Dec 5, 2017

Manhattan ad-hoc build, version 1.47.3+20171205201338, tested on CentOS 7.3 and Ubuntu 16.04, and issue is resolved.

The version of Rainbow brought in as a direct dependency also depends
directly on Rake, and our pin of Rake was inaccurate. This was causing
Omnibus to build packages that contained two rake gems which would emit
"Unresolved specs during Gem::Specification.reset" warnings when
running InSpec.

Signed-off-by: Adam Leff <[email protected]>
@adamleff adamleff force-pushed the adamleff/duplicate-rake branch from 5697bda to 6540f65 Compare December 7, 2017 12:03
Copy link
Contributor

@arlimus arlimus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sweet thank you @adamleff !

@arlimus arlimus merged commit 5be9739 into master Dec 7, 2017
@arlimus arlimus deleted the adamleff/duplicate-rake branch December 7, 2017 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unresolved specs during Gem::Specification.reset (rake)
3 participants