-
-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
elixir_1_14: init at 1.14.0 #189355
elixir_1_14: init at 1.14.0 #189355
Conversation
Which packages break with 1.14? |
Sure, sorry for not including that info in the top post. With this additional change: diff --git a/pkgs/development/beam-modules/default.nix b/pkgs/development/beam-modules/default.nix
index 068e1da3313..66300e6bb2c 100644
--- a/pkgs/development/beam-modules/default.nix
+++ b/pkgs/development/beam-modules/default.nix
@@ -42,7 +42,7 @@ let
elvis-erlang = callPackage ./elvis-erlang { };
# BEAM-based languages.
- elixir = elixir_1_13;
+ elixir = elixir_1_14;
elixir_1_14 = lib'.callElixir ../interpreters/elixir/1.14.nix {
inherit erlang; I see compiler failures in
And this fails the build for |
Thanks! Will have a look That make me think we also need to fix the UTF8 problem, i keep having it. |
FWIW plemora is depending on their own fork of I tried pinging someone who I think is a maintainer of the fork here: deadtrickster/prometheus.ex#48 |
Can we just patch it to use mainline until upstream fixes it?
…On Sun, 4 Sep, 2022, 21:51 Max Veytsman, ***@***.***> wrote:
FWIW plemora is depending on their own fork
<https://git.pleroma.social/pleroma/elixir-libraries/prometheus.ex/> of
prometheus_ex. The mainline repo compiles fine in Elixir 1.14.0.
I tried pinging someone what I think is a maintainer of the fork here:
deadtrickster/prometheus.ex#48
<deadtrickster/prometheus.ex#48>
—
Reply to this email directly, view it on GitHub
<#189355 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFZBOULX7AIDI4QAYPCHPLLV4TEB5ANCNFSM6AAAAAAQCYENSE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
# How to obtain `sha256`: | ||
# nix-prefetch-url --unpack https://github.com/elixir-lang/elixir/archive/v${version}.tar.gz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# How to obtain `sha256`: | |
# nix-prefetch-url --unpack https://github.com/elixir-lang/elixir/archive/v${version}.tar.gz |
This is already in the contributing guide
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, this was added by me a while ago.
I do not often contribute and this way it was easier for me (lower the barrier).
So please remove.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PS: There are probably more of this comments across the code base from me - should I remove them all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review! Removed in the version committed as b73e0e9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PS: There are probably more of this comments across the code base from me - should I remove them all?
If the download link is not obvious then we can keep it but for github downloads at least we do not require them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok. Thanks Sandro. I'll remove theme step by step in the places where I left theme.
Isn't setting |
Nice to see you around here @shanesveller (I enjoyed quite enjoyed your blog when I was doing elixir)! Thank you for the contribution! I think this is fine to merge to make the update available to everyone. Regarding the UTF8 problem, I've never found how to fix it with nix as well. We are doing exactly what you pointed @cw789 but it seems it's not enough. (let me know of course if you disagree). |
Nah iirc there was a glibc patch a few years ago that broke it all and we need to patch it a bit. I have something somewhere. I never had time to dive in. |
Thank you for the work. I have a question/suggestion. If this contribution had been split into 2 commits and 2 pull requests such as:
Would that have allowed to backport the first commit/PR to |
it would have indeed made the backport easier, we can think about that for next time! Thank you for your input on this. |
Followed the example of #148619 since everything included still seems pertinent. However, some included packages do not build successfully on 1.14.0 yet, so I skipped the default (
elixir
) version change for purposes of this PR. Please let me know if the desired flow is instead to wait for such projects to become 1.14-compatible on their own.Description of changes
https://elixir-lang.org/blog/2022/09/01/elixir-v1-14-0-released/
https://hexdocs.pm/elixir/1.14.0/changelog.html
Things done
Extras:
Defaultelixir
version 1.13 -> 1.14Defaults:
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes