You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to update to v1.11.7 on Windows I get the following error:
PS C:\Users\Landon Abney> gem updateUpdating installed gemsUpdating github_changelog_generatorTemporarily enhancing PATH to include DevKit...Building native extensions. This could take a while...ERROR: Error installing github_changelog_generator: ERROR: Failed to build gem native extension. C:/Ruby22-x64/bin/ruby.exe -rubygems C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/rake-10.5.0/bin/rake RUBYARCHDIR=C:/Ruby22-x64/lib/ruby/gems/2.2.0/extensions/x64-mingw32/2.2.0/github_changelog_generator-1.11.7 RUBYLIBDIR=C:/Ruby22-x64/lib/ruby/gems/2.2.0/extensions/x64-mingw32/2.2.0/github_changelog_generator-1.11.7rake aborted!Bundler::GemspecError: There was a Errno::ENOENT while loading github_changelog_generator.gemspec:No such file or directory - git ls-files -z from C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/github_changelog_generator-1.11.7/github_changelog_generator.gemspec:21:in ``'Errno::ENOENT: No such file or directory - git ls-files -z(See full trace by running task with --trace)rake failed, exit code 1Gem files will remain installed in C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/github_changelog_generator-1.11.7 for inspection.Results logged to C:/Ruby22-x64/lib/ruby/gems/2.2.0/extensions/x64-mingw32/2.2.0/github_changelog_generator-1.11.7/gem_make.outGems updated: github_changelog_generator
It looks like this is assuming the git command is available when installing, which is a bit odd as no other gem has required that so far...
The text was updated successfully, but these errors were encountered:
When attempting to update to v1.11.7 on Windows I get the following error:
It looks like this is assuming the
git
command is available when installing, which is a bit odd as no other gem has required that so far...The text was updated successfully, but these errors were encountered: