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
nodejs-11_x: remove #70256
nodejs-11_x: remove #70256
Conversation
@@ -16,7 +16,7 @@ buildPythonPackage rec { | |||
|
|||
node_modules = fetchNodeModules { | |||
src = "${src}/srht"; | |||
nodejs = nodejs-11_x; | |||
nodejs = nodejs; | |||
sha256 = "0axl50swhcw8llq8z2icwr4nkr5qsw2riih0a040f9wx4xiw4p6p"; |
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.
The hash probably changes with different Node.js versions so it would be better to pin it to a certain release and change it everytime the version reaches EOL.
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.
Nevermind it doesn't seem to have changed.
Will fix the merge conflict later that day :) |
The hash to the patch is broken, even with the original revision which adds asyncpg (ee2161c). As the downloaded patch seems fine, I guess that it was generated with `nix-prefetch-url` (the hashes for `fetchpatch` usually differ) and the issue wasn't found as the fixed-output-derivation was already in the contributor's store. See https://hydra.nixos.org/build/102495795 ZHF NixOS#68361
Package is EOLed by upstream: https://github.com/nodejs/Release Fixes NixOS#69008
There were several custom python dependencies broken. I decided to modify the `sourcehut` expression as it wouldn't even evaluate without nodejs-11_x I didn't manage to get it building.
Rebased onto latest master and resolved conflicts in the release notes. |
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.
nix-review
looks right
[1 built, 0.0 MiB DL]
https://github.com/NixOS/nixpkgs/pull/70256
9 package are marked as broken and were skipped:
sourcehut.buildsrht sourcehut.dispatchsrht sourcehut.gitsrht sourcehut.hgsrht sourcehut.listssrht sourcehut.mansrht sourcehut.metasrht sourcehut.pastesrht sourcehut.todosrht
1 package were build:
python37Packages.asyncpg
@GrahamcOfBorg build python3Packages.asyncpg |
@jonringer anything missing here? Otherwise this should be good to go, right? :) |
LGTM too ;) |
@@ -519,6 +519,11 @@ | |||
Please use the fork <literal>cawbird</literal> instead which has been adapted to the API changes and is still maintained. | |||
</para> | |||
</listitem> | |||
<listitem> | |||
<para> | |||
The <literal>nodejs-11_x</literal> package has been removed as it's EOLed by upstream. |
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.
This has to be updated for master. We should be targeting 20.03 now.
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.
So in your opinion this shouldn't land in 19.09? The thing is, NodeJS 11 is actually EOLed (see also #69008).
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.
No, entirely not my intention.
I just think we should deprecate on master first and then backport it to whever we want it to be. If those target branches then are an upcoming release those should receive an appropriate changelog entry.
If we would merge this now the changelog (from a master perspective) would not reflect the reality of 19.09. That is why I am saying we should update this PR to 20.03. After this has been accepted into 19.09 (by the RMs) then we should go ahead and remove the changelog entry from 20.03 since it would then no longer be true.
We could also drop the message here and only add it to the backport PR. I do not like that since we do not know ahead of time if the RMs would like this kind of change this late in the process.
That all being said. I think our RMs are very reasonable and will happily accept this even at this time.
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.
+1 for backporting right away, it sucks but shipping EOL software sucks more :)
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.
@andir as we should backport this to 19.09, I guess it should be fine to keep this in the 19.09 release notes, right? (Just talked to @lheckemann about this in person, so unless there are any further objections, I guess it should be fine to merge :))
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.
sigh, I wish I had nixos users to talk to :(. Sad times in the states :/
Motivation for this change
Drops NodeJS v11 as discussed in #69008.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @