Closed jaredledvina closed 7 years ago
Thanks for the report! :star:
I've seen this happen prior to the release of mac OS sierra so I don't think this is anything new however I still don't know exactly why it happens though.
Yup - also getting this since updating to boxen 2.9.0 (el capitan pre-sierra)
I couldn't work it out, but my state was stuffed in someway, so a full boxen nuke then rebuild on 2.8, then update to 2.9 worked flawlessly.
Went from El Capitan (with boxen) to Sierra and tried the latest boxen again, works fine, but when I tried a fresh install of macOS Sierra and run script/boxen
it produces error something like json 1.8.3 missing. Still trying some ways on how to resolve this missing gem.
Hey there, so from what I understand Boxen caches all of the gems in the repo in order to make the initial bootstrap process as quick as possible. When the boxen gem was updated to 2.9.0 in #826, the Gemfile and lockfile were updated, and the older versions of boxen and faraday were removed from the cache, but the new versions weren't included.
@spacepants while the gems were missed, this is a longer standing issue and as I mentioned, has been present for a while prior to these updates.
I've merged the change to get the gems re-added however I'll need to find some time to investigate why this randomly happens with installations.
OS: macOS Sierra Fresh Install Xcode Command line Tools (not full install)
Was simply following the bootstrapping section on the README, https://github.com/boxen/our-boxen/blob/master/README.md#L54 but when running boxen it'd error:
From there everything worked without an issue.