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

Jump to bottom

neovim: Update ruby provider to 0.8.0 #56316

Merged
merged 1 commit into from Feb 25, 2019
Merged

neovim: Update ruby provider to 0.8.0 #56316

merged 1 commit into from Feb 25, 2019

Conversation

artemist
Copy link
Member

Motivation for this change

Neovim was warning about an outdated Ruby provider. This updates the provider to the latest version.

Things done

Update the Ruby lockfile with bundler and the gemset.nix with bundix

  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@xeji
Copy link
Contributor

xeji commented Feb 25, 2019

@GrahamcOfBorg build neovim-qt

@teto
Copy link
Member

teto commented Feb 25, 2019

(Not related but do you have some dotfiles with a custom ruby environment for neovim ?)

@xeji xeji merged commit 77cf0b0 into NixOS:master Feb 25, 2019
@artemist artemist deleted the neovim_update_ruby branch March 13, 2019 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
10.rebuild-darwin: 1-10 10.rebuild-linux: 1-10
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@artemist @xeji @teto @GrahamcOfBorg