Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

[SHACK-304] Habitat build fails with bundler error #1636

Merged
merged 1 commit into from
Aug 1, 2018

Conversation

tyler-ball
Copy link
Contributor

@tyler-ball tyler-ball commented Jul 31, 2018

Description

Fetching chef-apply 0.1.18
Downloading chef-apply-0.1.18 revealed dependencies not in the API or the
lockfile (chef-dk (>= 3.0)).
Either installing with `--full-index` or running `bundle update chef-apply`
should fix the problem.

Hoping this fixes ☝️

Issues Resolved

SHACK-304

Check List

Signed-off-by: tyler-ball tball@chef.io

Fetching chef-apply 0.1.18
Downloading chef-apply-0.1.18 revealed dependencies not in the API or the
lockfile (chef-dk (>= 3.0)).
Either installing with `--full-index` or running `bundle update chef-apply`
should fix the problem.

Signed-off-by: tyler-ball <tball@chef.io>
@tyler-ball tyler-ball requested a review from a team July 31, 2018 22:10
@tas50
Copy link
Contributor

tas50 commented Jul 31, 2018

This a temp PR to check this fixes it right?

@@ -140,7 +140,7 @@ GEM
mime-types
chef-apply (0.1.18)
chef (>= 14.0)
chef-dk (3.1.6)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have no idea how 3.1.6 got in here because it is not in Rubygems yet. Maybe somehow it got pointed to the version I had checked out from master? The chef-apply gem description on Rubygems has the correct constraint (>= 3.0)

@tyler-ball
Copy link
Contributor Author

@tas50 Got a successful local Habitat build

@tyler-ball
Copy link
Contributor Author

We're going to need Chef 14.4.19 (or the changes from that) in order to finish fixing the ChefDK pipeline tests

@tyler-ball tyler-ball merged commit d12e020 into master Aug 1, 2018
@tyler-ball tyler-ball deleted the SHACK-304/missed_dep branch August 1, 2018 14:08
@lock
Copy link

lock bot commented Sep 30, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Sep 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants