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

hy: 0.11.1 -> 0.12.1 #24735

Merged
merged 1 commit into from Apr 8, 2017
Merged

hy: 0.11.1 -> 0.12.1 #24735

merged 1 commit into from Apr 8, 2017

Conversation

nixy
Copy link
Contributor

@nixy nixy commented Apr 8, 2017

Fixed build inputs up a little while bumping version

Motivation for this change

Hylang had a version bump and my original package was broken. appdirs is needed as a propogated build input. Honestly not sure how I messed that up last time, since I had a working version. I think I had done some work that I hadn't commited

Things done
  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • 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/)
  • Fits CONTRIBUTING.md.

Fixed build inputs up a little while bumping version
@mention-bot
Copy link

@nixy, thanks for your PR! By analyzing the history of the files in this pull request, we identified @globin to be a potential reviewer.

@Mic92
Copy link
Member

Mic92 commented Apr 8, 2017

So the appdir packages should be also in propagatedBuildInputs in release-17.03?

@Mic92 Mic92 merged commit 6c59393 into NixOS:master Apr 8, 2017
@nixy
Copy link
Contributor Author

nixy commented Apr 8, 2017

Yeah the appdirs package should be fixed in 17.03 as well. How would I go about updating/fixing that? Can I just submit a pull request against the release-17.03 branch? The path forward for making changes to a release branch isn't entirely clear to me.

@Mic92
Copy link
Member

Mic92 commented Apr 8, 2017

yes, just make a pull request against release-17.03 and refer to 106214a. Usually we just cherry-pick commits from master, but in this case the commit also contains a major version upgrade.

@nixy nixy mentioned this pull request Apr 8, 2017
7 tasks
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.

None yet

3 participants