Skip to content

sieve-editor-gui: Pin nodejs to nodejs22#477694

Open
lzszt wants to merge 1 commit intoNixOS:masterfrom
lzszt:sieve-editor-gui-node_js
Open

sieve-editor-gui: Pin nodejs to nodejs22#477694
lzszt wants to merge 1 commit intoNixOS:masterfrom
lzszt:sieve-editor-gui-node_js

Conversation

@lzszt
Copy link
Copy Markdown
Contributor

@lzszt lzszt commented Jan 7, 2026

Fixes the build failure of sieve-editor-gui from #477693, by pinning nodejs to version 22.

Things done

  • Built on platform:
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • Tested, as applicable:
  • Ran nixpkgs-review on this PR. See nixpkgs-review usage.
  • Tested basic functionality of all binary files, usually in ./result/bin/.
  • Nixpkgs Release Notes
    • Package update: when the change is major or breaking.
  • NixOS Release Notes
    • Module addition: when adding a new NixOS module.
    • Module update: when the change is significant.
  • Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

Add a 👍 reaction to pull requests you find important.

@lzszt
Copy link
Copy Markdown
Contributor Author

lzszt commented Jan 7, 2026

@Silver-Golden could you have a look?

@nixpkgs-ci nixpkgs-ci Bot requested review from Silver-Golden and fugidev January 7, 2026 10:42
@nixpkgs-ci nixpkgs-ci Bot added 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux. labels Jan 7, 2026
Copy link
Copy Markdown
Member

@Silver-Golden Silver-Golden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank ye so much for doing this, I have an open PR upstream (thsmi/sieve#1128) which should fix it.
Had been meaning to patch it here but got too busy.

@nixpkgs-ci nixpkgs-ci Bot added 12.approvals: 1 This PR was reviewed and approved by one person. 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in any of the changed packages. labels Jan 8, 2026
@Silver-Golden
Copy link
Copy Markdown
Member

@NixOS/nixpkgs-merge-bot merge

@nixpkgs-ci
Copy link
Copy Markdown
Contributor

nixpkgs-ci Bot commented Jan 8, 2026

@Silver-Golden wants to merge this PR.

Requirements to merge this PR with @NixOS/nixpkgs-merge-bot merge:

  • ✅ PR targets a development branch.
  • ✅ PR touches only files of packages in pkgs/by-name/.
  • ❌ PR is at least one of:
    • ⬜ Approved by a committer.
    • ⬜ Backported via label.
    • ⬜ Opened by a committer.
    • ⬜ Opened by r-ryantm.
  • ✅ Silver-Golden is a member of @NixOS/nixpkgs-maintainers.
  • ✅ Silver-Golden is a maintainer of all touched packages.

❌ Pull Request could not be merged (#305350)

@Silver-Golden
Copy link
Copy Markdown
Member

Danm, had hoped that would work

in

buildNpmPackage {
buildNpmPackage.override { nodejs = nodejs_22; } {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
buildNpmPackage.override { nodejs = nodejs_22; } {
buildNpmPackage {

Doesn't need to be an override, just provide it as normal.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@khaneliman the override is absolutely required right now as recently the default node changed from v22 to v24 (#462407)

This package is failing because it is not playing nicely with node v24.
There is a patch for upstream in progress as mentioned earlier (#477694 (review))
This patch by lzszt is intended to mitigate the impact here in nixpkgs while we wait for it to get fixed upstream.

So unless ye have permission to actually merge in the PR would you kindly remove this review.

Copy link
Copy Markdown
Contributor

@khaneliman khaneliman Jan 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@khaneliman the override is absolutely required right now as recently the default node changed from v22 to v24 (#462407)

This package is failing because it is not playing nicely with node v24.
There is a patch for upstream in progress as mentioned earlier (#477694 (review))
This patch by lzszt is intended to mitigate the impact here in nixpkgs while we wait for it to get fixed upstream.

You completely misunderstand my review... I've merged a couple of these. It doesn't need this syntax. You can provide it as nodejs = nodejs_22 below... example of one https://github.com/NixOS/nixpkgs/pull/477638/changes

So unless ye have permission to actually merge in the PR would you kindly remove this review.

Not exactly an appropriate response, regardless of a person's privileges involved in a review.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The link to the other PR changes things because it is explicit.

In the diff for the review you basically undid the change that this PR is making while not supplying the alternative.
Which kinda makes it look as if ye were calling the PR pointless.
So with teh information provided there was no misunderstanding from my point of view.

Regardless of that I am not too keen of nodejs = nodejs_22; in this case, its too neat/tidy.
.override { nodejs = nodejs_22; } is uglier and far more likely to get me to come back and ensure the root cause gets fixed properly.
Thats personal preference though, in reality either work to get the package being built again.

Copy link
Copy Markdown
Contributor

@khaneliman khaneliman Jan 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the diff for the review you basically undid the change that this PR is making while not supplying the alternative.
Which kinda makes it look as if ye were calling the PR pointless.
So with teh information provided there was no misunderstanding from my point of view.

"Doesn't need to be an override, just provide it as normal."

Regardless of that I am not too keen of nodejs = nodejs_22; in this case, its too neat/tidy.
.override { nodejs = nodejs_22; } is uglier and far more likely to get me to come back and ensure the root cause gets fixed properly.
Thats personal preference though, in reality either work to get the package being built again.

Scroll through the list of https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+pin+nodejs+is%3Aclosed and try to follow the community standard. Not sure why PR feedback is being argued here for a single 1 line change suggestion from someone.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 for doing things via the intended interface. Adding a comment that it should be revisited might be a good idea?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've changed the PR to only set nodejs.

@lzszt lzszt force-pushed the sieve-editor-gui-node_js branch from 6114be6 to 1b339f2 Compare January 20, 2026 14:10
pname = "sieve-editor-gui";
version = "0.6.1-unstable-2025-03-12";

nodejs = nodejs_22;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned above, adding a comment would be nice.
This is especially good if you are concerned about having a workaround in the package for long term. When it's fixed, we can find redundand workarounds and remove these nodejs pins.

Suggested change
nodejs = nodejs_22;
# npm dependency install fails with nodejs_24: https://github.com/NixOS/nixpkgs/issues/474535
nodejs = nodejs_22;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

10.rebuild-darwin: 1-10 This PR causes between 1 and 10 packages to rebuild on Darwin. 10.rebuild-darwin: 1 This PR causes 1 package to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-linux: 1 This PR causes 1 package to rebuild on Linux. 12.approvals: 1 This PR was reviewed and approved by one person. 12.approved-by: package-maintainer This PR was reviewed and approved by a maintainer listed in any of the changed packages.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants