text:
libcef: 116.0.24 -> 117.1.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for libcef is: Simple framework for embedding Chromium-based browsers in other applications
meta.homepage for libcef is: https://cef-builds.spotifycdn.com/index.html
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 116.0.27 with grep in /nix/store/gkhg69wjngakwhrlamkyd7msa3x5ncdx-cef-binary-116.0.27
found 116.0.27 in filename of file in /nix/store/gkhg69wjngakwhrlamkyd7msa3x5ncdx-cef-binary-116.0.27

Rebuild report (if merged into master) (click to expand)

36 total rebuild path(s)

36 package rebuild(s)

First fifty rebuilds by attrpath
libcef
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-freeze-filter
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-hyperion
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gkhg69wjngakwhrlamkyd7msa3x5ncdx-cef-binary-116.0.27 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libcef https://github.com/r-ryantm/nixpkgs/archive/5854917174a299f07397a48af43e3a03c17255f6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5854917174a299f07397a48af43e3a03c17255f6#libcef

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gkhg69wjngakwhrlamkyd7msa3x5ncdx-cef-binary-116.0.27
ls -la /nix/store/gkhg69wjngakwhrlamkyd7msa3x5ncdx-cef-binary-116.0.27/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

obs-studio-plugins.obs-hyperion

1 package failed to build:

obs-studio-plugins.obs-ndi

35 packages built:

libcef
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-freeze-filter
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs

Maintainer pings
cc @puffnfresh for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for libcef is: Simple framework for embedding Chromium-based browsers in other applications
meta.homepage for libcef is: https://cef-builds.spotifycdn.com/index.html
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 117.1.4 with grep in /nix/store/lh0z2xa56hvryawnmbxw9xxwnws6wv9r-cef-binary-117.1.4
found 117.1.4 in filename of file in /nix/store/lh0z2xa56hvryawnmbxw9xxwnws6wv9r-cef-binary-117.1.4

Rebuild report (if merged into master) (click to expand)

36 total rebuild path(s)

36 package rebuild(s)

First fifty rebuilds by attrpath
libcef
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-freeze-filter
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-hyperion
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lh0z2xa56hvryawnmbxw9xxwnws6wv9r-cef-binary-117.1.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libcef https://github.com/r-ryantm/nixpkgs/archive/c0ad983ae0081574e15e3e7bf03f4ee70648561c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c0ad983ae0081574e15e3e7bf03f4ee70648561c#libcef

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lh0z2xa56hvryawnmbxw9xxwnws6wv9r-cef-binary-117.1.4
ls -la /nix/store/lh0z2xa56hvryawnmbxw9xxwnws6wv9r-cef-binary-117.1.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

obs-studio-plugins.obs-hyperion

1 package failed to build:

obs-studio-plugins.obs-ndi

35 packages built:

libcef
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-freeze-filter
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs

Maintainer pings
cc @puffnfresh for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for libcef is: Simple framework for embedding Chromium-based browsers in other applications
meta.homepage for libcef is: https://cef-builds.spotifycdn.com/index.html
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 117.1.5 with grep in /nix/store/5zg0ph48zx2bnc405mdhjj2pvwb6zn5h-cef-binary-117.1.5
found 117.1.5 in filename of file in /nix/store/5zg0ph48zx2bnc405mdhjj2pvwb6zn5h-cef-binary-117.1.5

Rebuild report (if merged into master) (click to expand)

36 total rebuild path(s)

36 package rebuild(s)

First fifty rebuilds by attrpath
libcef
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-freeze-filter
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-hyperion
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5zg0ph48zx2bnc405mdhjj2pvwb6zn5h-cef-binary-117.1.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libcef https://github.com/r-ryantm/nixpkgs/archive/a6759db47c1ad79f5441f0912035df271fa99008.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a6759db47c1ad79f5441f0912035df271fa99008#libcef

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5zg0ph48zx2bnc405mdhjj2pvwb6zn5h-cef-binary-117.1.5
ls -la /nix/store/5zg0ph48zx2bnc405mdhjj2pvwb6zn5h-cef-binary-117.1.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

obs-studio-plugins.obs-hyperion

1 package failed to build:

obs-studio-plugins.obs-ndi

35 packages built:

libcef
obs-studio
obs-studio-plugins.advanced-scene-switcher
obs-studio-plugins.droidcam-obs
obs-studio-plugins.input-overlay
obs-studio-plugins.looking-glass-obs
obs-studio-plugins.obs-3d-effect
obs-studio-plugins.obs-backgroundremoval
obs-studio-plugins.obs-command-source
obs-studio-plugins.obs-freeze-filter
obs-studio-plugins.obs-gradient-source
obs-studio-plugins.obs-gstreamer
obs-studio-plugins.obs-livesplit-one
obs-studio-plugins.obs-move-transition
obs-studio-plugins.obs-multi-rtmp
obs-studio-plugins.obs-mute-filter
obs-studio-plugins.obs-nvfbc
obs-studio-plugins.obs-pipewire-audio-capture
obs-studio-plugins.obs-rgb-levels-filter
obs-studio-plugins.obs-scale-to-sound
obs-studio-plugins.obs-shaderfilter
obs-studio-plugins.obs-source-clone
obs-studio-plugins.obs-source-record
obs-studio-plugins.obs-source-switcher
obs-studio-plugins.obs-teleport
obs-studio-plugins.obs-text-pthread
obs-studio-plugins.obs-transition-table
obs-studio-plugins.obs-tuna
obs-studio-plugins.obs-vaapi
obs-studio-plugins.obs-vertical-canvas
obs-studio-plugins.obs-vintage-filter
obs-studio-plugins.obs-vkcapture
obs-studio-plugins.obs-websocket
obs-studio-plugins.waveform
obs-studio-plugins.wlrobs

Maintainer pings
cc @puffnfresh for testing.


text:
stratovirt: 2.2.0 -> 2.3.0

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Thanks for the reminder! Attempting it thru the Github mirror now: https://github.com/openeuler-mirror/stratovirt/pull/1

Great news, the patch got merged: https://gitee.com/openeuler/stratovirt/pulls/1254
(I emailed one of the authors directly.)

Awesome!

source: gharchive/pull-request

authors: alyssais astro

repo: NixOS/nixpkgs

license: MIT

license_type: permissive

license_source: github-api


text:
nixos/waydroid: Replace requirement for ASHMEM with MEMFD_CREATE

Description of changes

fixes #250302
ASHMEM was removed in Linux 5.18 and waydroid can use MEMFD instead. MEMFD is enabled by default in 4.18 and later kernels while we already require this version for namespace support.

I'm not certain if the MEMFD_CREATE requirement should be added as it's set by default in kernels newer than 4.18 while it has been available since 4.14 .
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I don't use these anymore and haven't kept up with the kernel side of android; I can't comment on this.

This needs a rebase.

This needs a rebase.

Done

authors: Atemu CajuM


text:
[23.05]  vesktop: init at 0.3.3

Description of changes
backport of #261006
Adds vesktop

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Not sure if backports are supported for new programs? And more importantly, the last commit will introduce some merge conflicts during the release, I would be against this for that reason.

there's like. a lot that's been done on master since this. closing for now

authors: eclairevoyant vgskye


text:
lib.extendDerivation': init to fix overriding issues caused by lib.extendDerivation

Description of changes
Add function lib.extendDerivation' as an alternative to lib.extendDerivation that is aware of existing overriders (existing attributes that performs overriding), and use it to fix overriding problem caused by lib.extendDerivation when applying to packages build with stdenv.mkDerivaiton.
Centinuation of #266232

Things done

Built on platform(s)

[X] x86_64-linux (No derivations are rebuilt)
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Rebase to resolve merge conflicts.

Result of nixpkgs-review run on x86_64-linux 1

1 package blacklisted:

nixos-install-tools

Split the application of lib.extendDerivation' into another PR to make this one shorter.

@ofborg build tests.overriding

The extendDerivation' implementation is indeed too complex.
Instead of adding another version of the low-level extendDerivation that plays well with high-level overriding, we could encourage developers to use existing functionality such as the passthru attribute and the meta.broken attribute.


text:
rstudio: 2023.09.0+463 -> 2023.12.0+369

Description of changes
This is a draft PR because I trued upgrading to the latest version of RStudio, but there seems to be an issue with CMake.

Upgraded to current version (2023.12.0+369 "Ocean Storm"): commits https://github.com/b-rodrigues/nixpkgs/commit/6919a0a7295a6795c9ac0e20ec434b747fdba217 and https://github.com/b-rodrigues/nixpkgs/commit/1f1623bc18b9f946c0dcb7e0bd0d529c6909ccb5
Upgraded boost version (from 1.81 to 1.83): commits https://github.com/b-rodrigues/nixpkgs/commit/5a9439f74a50196f3cf256d9af176b202a3880ca and https://github.com/b-rodrigues/nixpkgs/commit/872395a585473a0415b0a74262e60af309ba4537

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Trying to build now results in following message:
-- Configuring incomplete, errors occurred!
error: builder for '/nix/store/jn4im93rx67cp0z2yzgdr6swyy8f9vwb-RStudio-2023.12.0+369.drv' failed with exit code 1;
       last 10 log lines:
       > -- Looking for group_member
       > -- Looking for group_member - found
       > -- Performing Test HAVE_EXECINFO
       > -- Performing Test HAVE_EXECINFO - Success
       > -- Configured to build DESKTOP
       > -- Found LibR: /nix/store/m3lp6c2vgb6lvznfn8ichz8di4r51s8m-R-4.3.2/lib/R
       > -- Found R: /nix/store/m3lp6c2vgb6lvznfn8ichz8di4r51s8m-R-4.3.2/lib/R
       > -- Found Qt: /nix/store/pq91ai5s5h7nn3l2pa9cbrniw1cszpvj-qmake-hook/bin/qmake
       > -- Packaging RStudio for
       > -- Configuring incomplete, errors occurred!
       For full logs, run 'nix log /nix/store/jn4im93rx67cp0z2yzgdr6swyy8f9vwb-RStudio-2023.12.0+369.drv'.
error: 1 dependencies of derivation '/nix/store/4ldy5gahsal3azl4z8gnyibdqdszzav6-nix-shell.drv' failed to build

This is the configuration steps that fails:
-- Looking for getpeereid - not found

no idea what this is though

getpeereid

could this maybe be related to this? https://github.com/rstudio/rstudio/issues/9600

Perhaps, but according to that thread it was an issue of gcc being too old: I don’t think we have this problem here?

Result of nixpkgs-review pr 275649 run on aarch64-darwin 1
$ /nix/store/fgp1c16hly3960pnw765ac11a1p0a39r-nix-2.18.1/bin/nix-shell /Users/philipp/.cache/nixpkgs-review/pr-275649/shell.nix --nix-path nixpkgs=/Users/philipp/.cache/nixpkgs-review/pr-275649/nixpkgs nixpkgs-overlays=/tmp/tmpsh0gpt9r

Perhaps, but according to that thread it was an issue of gcc being too old: I don’t think we have this problem here?

it is a bit strange though yes. Your current PR commit compiles on aarch64-darwin, so I wonder whether some specific gcc related imports in nativeBuildInputs could resolve on linux platforms. A wild guess because I am quite a nix beginner.

I've updated the source to use the latest rsconnect, and still get the same error message:
Looking for strtod_l - not found
Looking for getpeereid - not found

Closing this as @Kupac got it working over here
https://github.com/NixOS/nixpkgs/pull/289393

authors: b-rodrigues philipp-baumann


text:
python311Packages.boto3-stubs: 1.34.2 -> 1.34.7

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 276371 run on x86_64-linux 1

10 packages built:

aws-sam-cli
aws-sam-cli.dist
python310Packages.boto3-stubs
python310Packages.boto3-stubs.dist
python310Packages.dsnap
python310Packages.dsnap.dist
python311Packages.boto3-stubs
python311Packages.boto3-stubs.dist
python311Packages.dsnap
python311Packages.dsnap.dist


text:
stdenv-setup: fix substituteAll with set -eu

Motivation for this change
Environment variable filter in substituteAll was not precise and produced undefined and invalid variable names.  Vladimír Čunát tried to fix that in [1], but env -0 did not work during Darwin bootstrap, so [2] reverted this change and replaced an error due to invalid variables with a warning.  Recently in #28057 John Ericson added set -u to setup.sh and undefined variables made the setup fail during e.g. nix-build -A gnat with setup: line 519: !varName: unbound variable.
This patch fixes the cause of such warnings as [3]:
 WARNING: substitution variables should be valid bash names,
   "ccLDFlags+" isn't and therefore was skipped; it might be caused
   by multi-line phases in variables - see #14907 for details.

[1] https://github.com/NixOS/nixpkgs/commit/62fc8859c10dd18b005b9bcaa0b429103d7661d9
[2] https://github.com/NixOS/nixpkgs/commit/81df0354290389128077e00edfd2368eeeea0c24
[3] https://github.com/NixOS/nixpkgs/pull/14907#issuecomment-240309994
Things done
I'm going to test this soon.

[ ] 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 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/)
[x] Fits CONTRIBUTING.md.

Ugh, overriding a builtin feels dirty. Does env -0 work on Darwin? That should allow safe parsing even if the variables contain newlines.

This is what [1] above tried to do, but env -0 does not work on Darwin.

How about awk 'BEGIN { for (v in ENVIRON) print v }' then?

Good idea!

env -0 works fine on Darwin inside most Nix contexts, because we just use the standard Nix tooling (coreutils, bash) in any pure context. The only place to be worried is the occasional script that runs under /bin/sh, where we can no longer control the PATH and bash being used.

@copumpkin setup.sh is needed on Darwin before any bash from nixpkgs is available. See https://github.com/NixOS/nixpkgs/commit/81df0354290389128077e00edfd2368eeeea0c24.

@dezgeg

overriding a builtin feels dirty

Actually, overriding builtins with functions is well defined:
 2. If the name does not match a function, the shell searches for it in the list of shell builtins.

https://www.gnu.org/software/bash/manual/html_node/Command-Search-and-Execution.html
Nevertheless, I'm going to continue with awk for now.
Could someone test this on hydra? I have successfully built some packages on Linux and Darwin with this pull request, but I don't know how to test properly without hydra.

@orivej are you sure that's still true? I thought that was only true because nix-shell used the host bash, but now that we force it to use the Nix bash (and maybe coreutils?) we might be safer. If not, can we just force setup.sh to incorporate a fixed version of coreutils?

@copumpkin You are right, since 2bc7b4e134079cf72307538e57b8968cfb27d70c Darwin always uses Bash from nixpkgs for setup.sh. However, over programs from bootstrap-tools (including env and awk) are not in PATH during early stages (when the shell is ${bootstrapTools}/bin/bash), e.g. env or awk 'BEGIN {}' at the beginning of setup.sh will cause failure, so it is not quite safe to use them at the moment… Currently bootstrap succeeds because early stages do not call substituteAll

err in nix-shell, the impure bash will be used---I've certainly learned that! If any dependency has a setup hook or similar using substitute, it will be run when the nix-shell is entered.

Thanks @orivej!

authors: Ericson2314 copumpkin dezgeg orivej


text:
homepage-dashboard: support local icons

Description of changes
Integrate Dashboard Icons as the official documentation mentioned to allow homepage run offline with full icon support.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 291208 run on x86_64-linux 1

1 package built:

homepage-dashboard


text:
bpftop: 0.2.1 -> 0.2.2

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 291911 run on x86_64-linux 1

1 package built:

bpftop


text:
Add workaround for Cythonized code and pytest

Cython is a Python compiler that emits native .so modules. By default, python derivations run tests in the wrong directory to see these modules and tests fail.
Issue #255262 documents the root cause and solution for this problem.
This PR adds a description of the problem and the most common solution to the test troubleshooting list.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@natsukium FYI. Let's get this knowledge into the documentation.

Hi folks, this PR has been open for a while but I don't know enough about the cython-related stuff to know whether this is mergeable in its current state or if it needs any changes. I'd like to help merge documentation PRs quicker as long as they're mergeable, can you help me decide whether this is the case here already?

authors: DanielSidhion sarahec


text:
usbsdmux: install udev rules

This makes sure the udev rules shipped with the software are present in $out/lib/udev/rules.d, so it becomes possible to just set services.udev.packages = [ pkgs.usbsdmux ]; to get them picked up.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I opened a backport PR for this at https://github.com/NixOS/nixpkgs/pull/297399, PTAL.


text:
apptainer: 1.2.5 -> 1.3.0

Description of changes
Changelog: https://github.com/apptainer/apptainer/releases/tag/v1.3.0
cc @ShamrockLee
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 295632 run on x86_64-linux 1

2 packages built:

apptainer
apptainer-overriden-nixos

Result of nixpkgs-review pr 295632 run on aarch64-linux 1

2 packages built:

apptainer
apptainer-overriden-nixos

apptainer.tests builds fine on x86_64-linux but fails on aarch64-linux with:
Formatting '/nix/store/8n13anj6czhs9z4lkrmnymg7alb7fvyp-apptainer-image-hello-cowsay.img/disk-image.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off compression_type=zlib size=1>
loading kernel modules...
cat: can't open '/nix/store/jfhgjmjql2c583xrfifk3iidklbiapbl-linux-6.6.21-shrunk/insmod-list': No such file or directory
mounting Nix store...
mounting host's temporary directory...
starting stage 2 (/nix/store/fr2j5z16r322fgp4m43lvbfrsn2ajy1z-vm-run-stage2)
mke2fs 1.47.0 (5-Feb-2023)
Discarding device blocks: done
Creating filesystem with 262144 4k blocks and 65536 inodes
Filesystem UUID: 24e59101-451b-4655-9da0-b9104c691ff7
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376

Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

cp: cannot access '/nix/store/pd4vh1jf8yqmb4gpxynjg28phc1h918i-hello-2.12.1': Cannot allocate memory
[    5.107127] reboot: Power down


text:
Avoid top-level with ...; in pkgs/development/lisp*

Description of changes
Using with at a top-level scope is an anti-pattern. The tracking issue is #208242. This is a pure refactor: there is no functional change contained in this PR.
I tried out the other strategy of replacing top-level with in this PR. If symbol foo was pulled implicitly from attrset pkgs, I replaced foo with pkgs.foo. Prior to this change, this file was a mix of both styles (foo and pkgs.foo), and now it's just one.
There are no rebuilds when I run nixpkgs-review rev HEAD, so I've targeted master with this PR.
Things done

[x] Tested compilation of all packages that depend on this change using nixpkgs-review rev HEAD.
[x] Fits CONTRIBUTING.md.

I get that. I mean, you're doing a refactor, and I appreciate you're doing it conservatively, but in this case we could as well make an opinionated choice - the original motivation was increasing clarity and readability. And again, I think judicious use of with can help with that.

I'm sorry, I find a with scope going over 90% of the lines of the file, mixed in with use of pkgs. within that scope to not be code I wish to produce. I can't apply that opinionated feedback in this PR, as it's not an opinion I share.
The only place I find with to make sense is where the scope is minimal: a list, a small set like meta, the like. If it scrolls off the screen while reading the file, or won't be present in the diff because it's far away, it's effectively a top-level with. To me, that's a judicious use.
You can see evidence of that confusion when code authors introduce smaller with scopes that were already covered by some larger one. with lib at the top scope, followed by with lib in the meta section. Use of pkgs. in a list when there's a top-level with pkgs;.
The other possible use of with pkgs; that I could have transformed in this PR is landing with pkgs; in front of every nativeBuildInputs or buildInputs. I chose not to do that since virtually every one of these lists contain just one member, and adding pkgs. is shorter.

Yeah, fair.

This PR is obviated by #309696.

authors: fricklerhandwerk philiptaron


text:
git-town: 11.1.0 -> 13.0.0

Description of changes
https://github.com/git-town/git-town/releases/tag/v13.0.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[x] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@allonsy, @blaggaca: FYI, to review.

@NickCao : Added some release info due to breaking changes.

@SuperSandro2000 : Do you know somebody to talk to about the formatting/linting thing in the nixpkgs repo? I think this repo is central/important enough to really have something in place.

Please rebase after #298194 got merged.


text:
carp: mark broken

Description of changes
As per discussion on https://github.com/NixOS/nixpkgs/pull/300455, marking Carp package broken.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg eval

authors: jluttine wegank


text:
ocamlPackages.terminal: 0.2.2 -> 0.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/CraigFe/progress/releases.
meta.description for ocamlPackages.terminal is: Basic utilities for interacting with terminals
meta.homepage for ocamlPackages.terminal is: https://github.com/CraigFe/progress
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.3.0 with grep in /nix/store/vlqv8ly5s1z96gf81ndf11kx42nva4b5-ocaml5.1.1-terminal-0.3.0
found 0.3.0 in filename of file in /nix/store/vlqv8ly5s1z96gf81ndf11kx42nva4b5-ocaml5.1.1-terminal-0.3.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

ligo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vlqv8ly5s1z96gf81ndf11kx42nva4b5-ocaml5.1.1-terminal-0.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.terminal https://github.com/r-ryantm/nixpkgs/archive/417660859da4f36d4b0bd80df0bb202ce6f7323e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/417660859da4f36d4b0bd80df0bb202ce6f7323e#ocamlPackages.terminal

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vlqv8ly5s1z96gf81ndf11kx42nva4b5-ocaml5.1.1-terminal-0.3.0
ls -la /nix/store/vlqv8ly5s1z96gf81ndf11kx42nva4b5-ocaml5.1.1-terminal-0.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

6 packages built:

ligo
ocamlPackages.index
ocamlPackages.irmin-pack
ocamlPackages.irmin-tezos
ocamlPackages.progress
ocamlPackages.terminal

Maintainer pings
cc @vbgl for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/CraigFe/progress/releases.
meta.description for ocamlPackages.terminal is: Basic utilities for interacting with terminals
meta.homepage for ocamlPackages.terminal is: https://github.com/CraigFe/progress
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.0 with grep in /nix/store/ig86pfr3lrd39ll14k350wczva2zyb66-ocaml5.1.1-terminal-0.4.0
found 0.4.0 in filename of file in /nix/store/ig86pfr3lrd39ll14k350wczva2zyb66-ocaml5.1.1-terminal-0.4.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

ligo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ig86pfr3lrd39ll14k350wczva2zyb66-ocaml5.1.1-terminal-0.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.terminal https://github.com/r-ryantm/nixpkgs/archive/a0010c88d4294b9932ce9970eb9d040b85df5a8b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a0010c88d4294b9932ce9970eb9d040b85df5a8b#ocamlPackages.terminal

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ig86pfr3lrd39ll14k350wczva2zyb66-ocaml5.1.1-terminal-0.4.0
ls -la /nix/store/ig86pfr3lrd39ll14k350wczva2zyb66-ocaml5.1.1-terminal-0.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

6 packages built:

ligo
ocamlPackages.index
ocamlPackages.irmin-pack
ocamlPackages.irmin-tezos
ocamlPackages.progress
ocamlPackages.terminal

Maintainer pings
cc @vbgl for testing.


text:
python311Packages.awswrangler: 3.7.2 -> 3.7.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.awswrangler is: Pandas on AWS
meta.homepage for python311Packages.awswrangler is: https://github.com/aws/aws-sdk-pandas
meta.changelog for python311Packages.awswrangler is: https://github.com/aws/aws-sdk-pandas/releases/tag/3.7.3
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.7.3 with grep in /nix/store/b3qv2wz99j6rhvj82k7l8ahph3g3syix-python3.11-awswrangler-3.7.3
found 3.7.3 in filename of file in /nix/store/b3qv2wz99j6rhvj82k7l8ahph3g3syix-python3.11-awswrangler-3.7.3

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.awswrangler
python312Packages.awswrangler

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b3qv2wz99j6rhvj82k7l8ahph3g3syix-python3.11-awswrangler-3.7.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.awswrangler https://github.com/r-ryantm/nixpkgs/archive/facce1b815ad9415f35db4bfeacd10669eda163c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/facce1b815ad9415f35db4bfeacd10669eda163c#python311Packages.awswrangler

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b3qv2wz99j6rhvj82k7l8ahph3g3syix-python3.11-awswrangler-3.7.3
ls -la /nix/store/b3qv2wz99j6rhvj82k7l8ahph3g3syix-python3.11-awswrangler-3.7.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

4 packages built:

python311Packages.awswrangler
python311Packages.awswrangler.dist
python312Packages.awswrangler
python312Packages.awswrangler.dist

Maintainer pings
cc @mcwitt for testing.

Result of nixpkgs-review pr 306087 run on x86_64-linux 1

4 packages built:

python311Packages.awswrangler
python311Packages.awswrangler.dist
python312Packages.awswrangler
python312Packages.awswrangler.dist

authors: fabaff r-ryantm


text:
eid-mw: 5.1.16 -> 5.1.18

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/eid-mw/versions.
meta.description for eid-mw is: Belgian electronic identity card (eID) middleware
meta.homepage for eid-mw is: https://eid.belgium.be/en
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.1.18 with grep in /nix/store/w31lxhrw8ksznzz5jgw5sagg5mr5mpbn-eid-mw-5.1.18
found 5.1.18 in filename of file in /nix/store/w31lxhrw8ksznzz5jgw5sagg5mr5mpbn-eid-mw-5.1.18

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

eid-mw

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w31lxhrw8ksznzz5jgw5sagg5mr5mpbn-eid-mw-5.1.18 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A eid-mw https://github.com/r-ryantm/nixpkgs/archive/8ad1089e557128d5889aaba7237cbd4277d17787.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/8ad1089e557128d5889aaba7237cbd4277d17787#eid-mw

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/w31lxhrw8ksznzz5jgw5sagg5mr5mpbn-eid-mw-5.1.18
ls -la /nix/store/w31lxhrw8ksznzz5jgw5sagg5mr5mpbn-eid-mw-5.1.18/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

eid-mw

Maintainer pings
cc @bfortz @chvp for testing.

Result of nixpkgs-review pr 311402 run on x86_64-linux 1

1 package built:

eid-mw

authors: matthiasbeyer r-ryantm


text:
gap-full: 4.12.2 -> 4.13.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/gap-system/gap/releases.
meta.description for gap-full is: Computational discrete algebra system
meta.homepage for gap-full is: https://www.gap-system.org
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.13.1 with grep in /nix/store/rn56zgkxv71c7blp6mxrgi7g7jihmjan-gap-4.13.1
found 4.13.1 in filename of file in /nix/store/rn56zgkxv71c7blp6mxrgi7g7jihmjan-gap-4.13.1

Rebuild report (if merged into master) (click to expand)

10 total rebuild path(s)

10 package rebuild(s)

First fifty rebuilds by attrpath

cantor
gap
gap-full
gap-minimal
labplot
libsForQt5.cantor
plasma5Packages.cantor
sage
sageWithDoc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rn56zgkxv71c7blp6mxrgi7g7jihmjan-gap-4.13.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gap-full https://github.com/r-ryantm/nixpkgs/archive/02a84b1a2b6ce7008a62e69249f61f3349df7344.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/02a84b1a2b6ce7008a62e69249f61f3349df7344#gap-full

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rn56zgkxv71c7blp6mxrgi7g7jihmjan-gap-4.13.1
ls -la /nix/store/rn56zgkxv71c7blp6mxrgi7g7jihmjan-gap-4.13.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages failed to build:

sage
sageWithDoc

5 packages built:

cantor
gap
gap-full
gap-minimal
labplot

Maintainer pings
cc @timokau @omasanori @7c6f434c @collares for testing.

Done in #357335.

authors: collares r-ryantm


text:
ungoogled-chromium: 126.0.6478.114-1 -> 126.0.6478.126-1

Description of changes
Same underlying changes as #322441
https://chromereleases.googleblog.com/2024/06/stable-channel-update-for-desktop_24.html
This update includes 5 security fixes.
CVEs:
CVE-2024-6290 CVE-2024-6291 CVE-2024-6292 CVE-2024-6293
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 322550 run on x86_64-linux 1 2 packages built:  ungoogled-chromium ungoogled-chromium.sandbox

authors: emilylange networkException


text:
hello-cpp: init

Proposal: a trivial hello-cpp to complement gnu hello, testing C++ and cmake infrastructure.
This is intended to assist with testing exotic stdenvs such as the one used in pkgsLLVM, requiring no additional dependencies to get a quick test that the compiler, the C++ standard library and cmake are working as intended as a basic level.
There does already exist tests.cc-wrapper, but this does not produce any outputs, and sometimes it is useful to have a quick test that something builds. It's also useful to be able to inspect the outputs to look at references and so forth.
This complements nixpkgs.hello since that one tests autotools/make/c, and this one tests cmake/ninja/c++, so they are orthogonal.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Will look into this when I have a moment for resolving the pkgsLLVM issue.

I opted to put the files in ./src rather than having a union since that involves less code.

authors: RossComputerGuy pwaller


text:
piped: init

Description of changes
Depends on https://github.com/NixOS/nixpkgs/pull/272380/ and https://github.com/NixOS/nixpkgs/pull/326306
Closes https://github.com/NixOS/nixpkgs/issues/270008

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Sorry?


text:
rover: 0.23.0 -> 0.24.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for rover is: CLI for interacting with ApolloGraphQL's developer tooling, including managing self-hosted and GraphOS graphs
meta.homepage for rover is: https://www.apollographql.com/docs/rover
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.24.0 with grep in /nix/store/6379hyhbnygff37kgdzgvpiyjd03yx1c-rover-0.24.0
found 0.24.0 in filename of file in /nix/store/6379hyhbnygff37kgdzgvpiyjd03yx1c-rover-0.24.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

rover

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6379hyhbnygff37kgdzgvpiyjd03yx1c-rover-0.24.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rover https://github.com/r-ryantm/nixpkgs/archive/f36d36eebbb2dfd46eb970885b1284eb15be3312.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/f36d36eebbb2dfd46eb970885b1284eb15be3312#rover

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6379hyhbnygff37kgdzgvpiyjd03yx1c-rover-0.24.0
ls -la /nix/store/6379hyhbnygff37kgdzgvpiyjd03yx1c-rover-0.24.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

rover

Maintainer pings
cc @ivanbrennan @aaronArinder for testing.

Result of nixpkgs-review pr 327603 run on aarch64-darwin 1

1 package built:

rover

authors: r-ryantm wegank


text:
ananicy-cpp: make bpfSupport optional

Description of changes
ananicy-cpp compiled with bpfSupport does not work on hardened kernels
So we make it optional to allow users to disable it.
https://github.com/NixOS/nixpkgs/issues/327382
This is still enabled by default.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I already started working on that.

I think we can use stdenv instead of clangStdenv with bpfSupport set to false.

Haven't checked yet, but we can probably make hardeningDisable optional on bpfSupport.

I think we can use stdenv instead of clangStdenv with bpfSupport set to false.

According to the docs, we could use GCC if bpf is disabled. But let's not complicate it further, my motto is if its not broken don't fix it. Clang is better supported by ananicy-cpp anyway.

I think the option should be named withBpf instead of bpfSupport. It's not about ananicy-cpp supporting bpf or not, but whether bpf is enabled for ananicy-cpp.

authors: JohnRTitor MrQubo


text:
composer: sort paths

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Do you mind creating this patch against composer/composer so that it can be reviewed by the Composer team ?

Yes that's the plan. I'm not sure if I applied the patch to correct package here. I'm going to close it for now.

authors: drupol piotrkwiecinski


text:
mpris-notifier: 0.1.7 -> 0.1.9

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/l1na-forever/mpris-notifier/releases.
meta.description for mpris-notifier is: Dependency-light, highly-customizable, XDG desktop notification generator for MPRIS status changes
meta.homepage for mpris-notifier is: https://github.com/l1na-forever/mpris-notifier
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.1.9 with grep in /nix/store/y5mvjv9q8z5xzwr4vvqfwd6sam6ji7xv-mpris-notifier-0.1.9
found 0.1.9 in filename of file in /nix/store/y5mvjv9q8z5xzwr4vvqfwd6sam6ji7xv-mpris-notifier-0.1.9

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

mpris-notifier

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/y5mvjv9q8z5xzwr4vvqfwd6sam6ji7xv-mpris-notifier-0.1.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mpris-notifier https://github.com/r-ryantm/nixpkgs/archive/c751311f1015e58c833a0fe9971068aa3448231b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c751311f1015e58c833a0fe9971068aa3448231b#mpris-notifier

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/y5mvjv9q8z5xzwr4vvqfwd6sam6ji7xv-mpris-notifier-0.1.9
ls -la /nix/store/y5mvjv9q8z5xzwr4vvqfwd6sam6ji7xv-mpris-notifier-0.1.9/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

mpris-notifier

Maintainer pings
cc @Leixb for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge

authors: Leixb r-ryantm


text:
jbigkit: add patch to fix security issue CVE-2017-9937

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I imagine we should include the heap overflow fix, too?

Here you go.

authors: drupol emilazy


text:
rhash: 1.3.3 -> 2018-02-05

Motivation for this change
This tentatively looks good to me, although unfortunate to move away from a tagged release.
Replaces / builds on #34214 .
If nothing else I'd like to see if this works any better on Darwin :).
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
[ ] 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/)
[ ] Fits CONTRIBUTING.md.

Tested with x86_64-linux, x86_64-linux-musl, cross-aarch64-musl, cross-x86_64-linux-musl.

Whoops, wrong base sorry about that!
@GrahamcOfBorg build rhash cmake

Success on aarch64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/h25jh5wmf23mwl894chvx0blfm1an3l8-cmake-3.10.2/bin/cpack
shrinking /nix/store/h25jh5wmf23mwl894chvx0blfm1an3l8-cmake-3.10.2/bin/ctest
shrinking /nix/store/h25jh5wmf23mwl894chvx0blfm1an3l8-cmake-3.10.2/bin/cmake
strip is /nix/store/xmpjypwjmp2qi1chs5kr0hacnh161ls4-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/h25jh5wmf23mwl894chvx0blfm1an3l8-cmake-3.10.2/bin
patching script interpreter paths in /nix/store/h25jh5wmf23mwl894chvx0blfm1an3l8-cmake-3.10.2
/nix/store/h25jh5wmf23mwl894chvx0blfm1an3l8-cmake-3.10.2/share/cmake-3.10/Modules/CPack.STGZ_Header.sh.in: interpreter directive changed from "/bin/sh" to "/nix/store/7fxbh1yhagvwbdrmdyyy5ghcjhwjndhs-bash-4.4-p12/bin/sh"
/nix/store/h25jh5wmf23mwl894chvx0blfm1an3l8-cmake-3.10.2/share/cmake-3.10/Modules/Squish4RunTestCase.sh: interpreter directive changed from "/bin/sh" to "/nix/store/7fxbh1yhagvwbdrmdyyy5ghcjhwjndhs-bash-4.4-p12/bin/sh"
/nix/store/h25jh5wmf23mwl894chvx0blfm1an3l8-cmake-3.10.2/share/cmake-3.10/Modules/SquishRunTestCase.sh: interpreter directive changed from "/bin/sh" to "/nix/store/7fxbh1yhagvwbdrmdyyy5ghcjhwjndhs-bash-4.4-p12/bin/sh"
checking for references to /build in /nix/store/h25jh5wmf23mwl894chvx0blfm1an3l8-cmake-3.10.2...

Success on x86_64-darwin (full log)
Partial log (click to expand)
-- Installing: /nix/store/il04smvjvbggy3qww7lwwz4hdhqkjah1-cmake-3.10.2/share/cmake-3.10/completions/cmake
-- Installing: /nix/store/il04smvjvbggy3qww7lwwz4hdhqkjah1-cmake-3.10.2/share/cmake-3.10/completions/cpack
-- Installing: /nix/store/il04smvjvbggy3qww7lwwz4hdhqkjah1-cmake-3.10.2/share/cmake-3.10/completions/ctest
post-installation fixup
strip is /nix/store/5a88zk3jgimdmzg8rfhvm93kxib3njf9-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/il04smvjvbggy3qww7lwwz4hdhqkjah1-cmake-3.10.2/bin
patching script interpreter paths in /nix/store/il04smvjvbggy3qww7lwwz4hdhqkjah1-cmake-3.10.2
/nix/store/il04smvjvbggy3qww7lwwz4hdhqkjah1-cmake-3.10.2/share/cmake-3.10/Modules/CPack.STGZ_Header.sh.in: interpreter directive changed from "/bin/sh" to "/nix/store/s8mff1kmnc63b21ybdid2ni0fw7mzy7r-bash-4.4-p12/bin/sh"
/nix/store/il04smvjvbggy3qww7lwwz4hdhqkjah1-cmake-3.10.2/share/cmake-3.10/Modules/Squish4RunTestCase.sh: interpreter directive changed from "/bin/sh" to "/nix/store/s8mff1kmnc63b21ybdid2ni0fw7mzy7r-bash-4.4-p12/bin/sh"
/nix/store/il04smvjvbggy3qww7lwwz4hdhqkjah1-cmake-3.10.2/share/cmake-3.10/Modules/SquishRunTestCase.sh: interpreter directive changed from "/bin/sh" to "/nix/store/s8mff1kmnc63b21ybdid2ni0fw7mzy7r-bash-4.4-p12/bin/sh"

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/m17222iq8gp4zkzmxrwm2jkwcwnrfsls-cmake-3.10.2/bin/ctest
shrinking /nix/store/m17222iq8gp4zkzmxrwm2jkwcwnrfsls-cmake-3.10.2/bin/cpack
shrinking /nix/store/m17222iq8gp4zkzmxrwm2jkwcwnrfsls-cmake-3.10.2/bin/cmake
strip is /nix/store/5qj61lcvzlap87rf6blvf8p577d482bv-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/m17222iq8gp4zkzmxrwm2jkwcwnrfsls-cmake-3.10.2/bin
patching script interpreter paths in /nix/store/m17222iq8gp4zkzmxrwm2jkwcwnrfsls-cmake-3.10.2
/nix/store/m17222iq8gp4zkzmxrwm2jkwcwnrfsls-cmake-3.10.2/share/cmake-3.10/Modules/CPack.STGZ_Header.sh.in: interpreter directive changed from "/bin/sh" to "/nix/store/yq03c2ny43mc24j7dq5riznzb09ddhpq-bash-4.4-p12/bin/sh"
/nix/store/m17222iq8gp4zkzmxrwm2jkwcwnrfsls-cmake-3.10.2/share/cmake-3.10/Modules/SquishRunTestCase.sh: interpreter directive changed from "/bin/sh" to "/nix/store/yq03c2ny43mc24j7dq5riznzb09ddhpq-bash-4.4-p12/bin/sh"
/nix/store/m17222iq8gp4zkzmxrwm2jkwcwnrfsls-cmake-3.10.2/share/cmake-3.10/Modules/Squish4RunTestCase.sh: interpreter directive changed from "/bin/sh" to "/nix/store/yq03c2ny43mc24j7dq5riznzb09ddhpq-bash-4.4-p12/bin/sh"
checking for references to /tmp/nix-build-cmake-3.10.2.drv-0 in /nix/store/m17222iq8gp4zkzmxrwm2jkwcwnrfsls-cmake-3.10.2...

@GrahamcOfBorg eval

@GrahamcOfBorg eval

Success on x86_64-darwin (full log)
Partial log (click to expand)
/nix/store/j7wl5ab4yr6vnqnxf9kvlp0m8kz1zxf1-rhash-2018-02-05

Success on x86_64-linux (full log)
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/afz17cd2mzvvhw6czwqbdy3l01vrh2a2-rhash-2018-02-05
shrinking /nix/store/afz17cd2mzvvhw6czwqbdy3l01vrh2a2-rhash-2018-02-05/bin/rhash
shrinking /nix/store/afz17cd2mzvvhw6czwqbdy3l01vrh2a2-rhash-2018-02-05/lib/librhash.so.0
gzipping man pages under /nix/store/afz17cd2mzvvhw6czwqbdy3l01vrh2a2-rhash-2018-02-05/share/man/
strip is /nix/store/5qj61lcvzlap87rf6blvf8p577d482bv-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/afz17cd2mzvvhw6czwqbdy3l01vrh2a2-rhash-2018-02-05/lib  /nix/store/afz17cd2mzvvhw6czwqbdy3l01vrh2a2-rhash-2018-02-05/bin
patching script interpreter paths in /nix/store/afz17cd2mzvvhw6czwqbdy3l01vrh2a2-rhash-2018-02-05
checking for references to /tmp/nix-build-rhash-2018-02-05.drv-0 in /nix/store/afz17cd2mzvvhw6czwqbdy3l01vrh2a2-rhash-2018-02-05...
/nix/store/afz17cd2mzvvhw6czwqbdy3l01vrh2a2-rhash-2018-02-05

Success on aarch64-linux (full log)
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/1ljfm654s7klvbkmag392jz10yi1lnwh-rhash-2018-02-05
shrinking /nix/store/1ljfm654s7klvbkmag392jz10yi1lnwh-rhash-2018-02-05/lib/librhash.so.0
shrinking /nix/store/1ljfm654s7klvbkmag392jz10yi1lnwh-rhash-2018-02-05/bin/rhash
gzipping man pages under /nix/store/1ljfm654s7klvbkmag392jz10yi1lnwh-rhash-2018-02-05/share/man/
strip is /nix/store/xmpjypwjmp2qi1chs5kr0hacnh161ls4-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/1ljfm654s7klvbkmag392jz10yi1lnwh-rhash-2018-02-05/lib  /nix/store/1ljfm654s7klvbkmag392jz10yi1lnwh-rhash-2018-02-05/bin
patching script interpreter paths in /nix/store/1ljfm654s7klvbkmag392jz10yi1lnwh-rhash-2018-02-05
checking for references to /build in /nix/store/1ljfm654s7klvbkmag392jz10yi1lnwh-rhash-2018-02-05...
/nix/store/1ljfm654s7klvbkmag392jz10yi1lnwh-rhash-2018-02-05


text:
python312Packages.sensorpush-ble: 1.6.2 -> 1.7.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.sensorpush-ble is: Library for SensorPush BLE devices
meta.homepage for python312Packages.sensorpush-ble is: https://github.com/Bluetooth-Devices/sensorpush-ble
meta.changelog for python312Packages.sensorpush-ble is: https://github.com/Bluetooth-Devices/sensorpush-ble/releases/tag/v1.7.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.7.0 with grep in /nix/store/xmz0kjzcn1z9hpmp1xn79dmixd4q3qvd-python3.12-sensorpush-ble-1.7.0
found 1.7.0 in filename of file in /nix/store/xmz0kjzcn1z9hpmp1xn79dmixd4q3qvd-python3.12-sensorpush-ble-1.7.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.sensorpush
python311Packages.sensorpush-ble
python312Packages.sensorpush-ble

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xmz0kjzcn1z9hpmp1xn79dmixd4q3qvd-python3.12-sensorpush-ble-1.7.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.sensorpush-ble https://github.com/r-ryantm/nixpkgs/archive/a7f3eef2ed74c025b17497d6d82f02c66baf0540.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a7f3eef2ed74c025b17497d6d82f02c66baf0540#python312Packages.sensorpush-ble

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xmz0kjzcn1z9hpmp1xn79dmixd4q3qvd-python3.12-sensorpush-ble-1.7.0
ls -la /nix/store/xmz0kjzcn1z9hpmp1xn79dmixd4q3qvd-python3.12-sensorpush-ble-1.7.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.sensorpush
python311Packages.sensorpush-ble
python311Packages.sensorpush-ble.dist
python312Packages.sensorpush-ble
python312Packages.sensorpush-ble.dist

Maintainer pings
cc @fabaff for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 350412

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.sensorpush
python311Packages.sensorpush-ble
python311Packages.sensorpush-ble.dist
python312Packages.sensorpush-ble
python312Packages.sensorpush-ble.dist


text:
ivyterm: fix hash

Things done
cc @vcunat

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Any idea why the hash was wrong?

Any idea why the hash was wrong?

Not really... I'm wondering how I could have been tricked by the FOD, but I have no clue.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 352350

x86_64-linux

:white_check_mark: 1 package built:

ivyterm

aarch64-linux

:white_check_mark: 1 package built:

ivyterm

x86_64-darwin

:white_check_mark: 1 package built:

ivyterm

aarch64-darwin

:white_check_mark: 1 package built:

ivyterm

Weird, locally it builds with both hashes on my end.

You have it cached apparently.  But that would mean the FOD is non-deterministic.  I suggest to build ivyterm.src in both cases (i.e. find the paths) and find what differs.

Did a bit of garbage collection and seems like the hash changed, the new one is correct.

authors: GaetanLepage genga898 vcunat


text:
beszel-agent: init at 0.7.4; beszel: 0.6.2 -> 0.7.4

This updates beszel to 0.7.4 and splits the agent in a separate package.
The beszel binary (the "hub", you can think of it as prometheus) bundles a web ui and weights in at some 37MB. While that's not much disk space in the grand scheme of things, it seems unnecessary to have that and the agent (think, prometheus node exporter) in the same package.
Since the beszel package was first merged only a few hours ago (see https://github.com/NixOS/nixpkgs/pull/345444) and didn't make into the stable branch yet, I don't think we should worry about the removal of the beszel-agent binary from that package (but IDK if there are official policies about that).
Tagging the most recent contributors from https://github.com/NixOS/nixpkgs/pull/345444:  @Aleksanaa @Bot-wxt1221
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

You don't fit CONTRIBUTION.md. Please do following things then I will review it:

format with nixfmt
remove with lib
split maintaiers commit into another committer

Webui is too dirty.

Thanks @Bot-wxt1221, and apologies: it's been a while for me and CONTRIBUTION.md must have been updated in the meantime (at least, I don't remember it saying anything about formatting).
I'll review your comments in a while, after re-reading CONTRIBUTION.md :)

@giorgiga The only diffrence between them is subPackages. We should define something like generic.ix.

@giorgiga

I suggest you to modify based on my code.
Actually only subPackages should be modified. We can define generic.nix in beszel.passthru and call it in beszel-agent.

@Bot-wxt1221  about your https://github.com/NixOS/nixpkgs/pull/354978#issuecomment-2466711499

You don't fit CONTRIBUTION.md.

I re-read CONTRIBUTION.md but I didn't find what I am infringing specifically. Can you elaborate?
(if it's that the addition of a new maintainer should be in its own commit, I am already in maintainers.nix).

Please do following things then I will review it:
format with nixfmt

Apologies, that wasn't a requirement last time I contributed.
Done using nixfmt-rfc-style.

remove with lib

I don't mind doint that and will do in the next iteration).
For future reference/my own self improvement, could you explain what's wrong with it?

split maintaiers commit into another committer

(see above: I am already a maintainer)

I suggest you to modify based on my code.
Actually only subPackages should be modified. We can define generic.nix in beszel.passthru and call it in beszel-agent.

Subpackages IMHO make sense for stuff that is usually installed as a bundle (eg. coreutils), but I don't see any benefit in this case. Also, I doubt most nix/nixos users even know about subpackages... (search.nixos.org does not show them in any way)
Can you elaborate the benefit of having subpackages?
If it's to share version and hashes in order to make updating (marginally) less cumbersome, could we add a third beszel-common.nix file somewhere instead? (does the nixpkgs directory layout allow for such thing?)
In general... I don't think it's bad to have a modicum of replication for the sake of simplicity.

(just realized I had committed the files for 0.7.3 - fixed)
@Bot-wxt1221 can you elaborate on the reasons behind the changes you requested?

(actually, I won't post a new PR)


text:
pomerium: 0.27.1 -> 0.27.2

https://github.com/pomerium/pomerium/compare/v0.27.1...v0.27.2
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg eval

@ofborg eval


text:
nixos/installer: Allow setting a password on cmdline for pxe boot

Copied isoImage-functionality for setting a password on boot for the nixos-user to the pxe image.
The pxe images come without passwords for the nixos and root accounts. This works great when doing local installations, but it prevents you from using ssh into the live-system without setting a password first. Adding live.nixos.passwd=somesecretpassword to the cmdline in any pxe configuration eliminates this requirement. This change also eliminates the need to build own images to achive this goal.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

PR is caused by https://github.com/nix-community/nixos-images/issues/303

It would be great if you could add the new parameter to boot.kernelParams here: https://github.com/NixOS/nixpkgs/blob/d4b1fcdbe64eedd4829db68b208ff0bf81e34b13/nixos/tests/boot.nix#L91
And than check /etc/shadow if it also contains the generated password.

It would be great if you could add the new parameter to boot.kernelParams here:
https://github.com/NixOS/nixpkgs/blob/d4b1fcdbe64eedd4829db68b208ff0bf81e34b13/nixos/tests/boot.nix#L91

I'm not sure if that even works:
After adding machine.succeed("cat /proc/cmdline; grep 'serial' /proc/cmdline") to the test-script...
machine: must succeed: cat /proc/cmdline; grep 'serial' /proc/cmdline
machine: output: bzImage init=/nix/store/xskdcn0dpzslay1sz59gq8dmyjjdwh6g-nixos-system-nixos-25.05pre-git/init initrd=initrd console=ttyS0 console=tty0 panic=1 boot.panic_on_fail clocksource=acpi_pm loglevel=7 net.ifnames=0

(In other words: I have no clue how to fix that.)

@Mic92 I fixed the missing kernel parameters and added the live.nixos.passwordHash-Option as well for testing. I also replaced the first implementation with sed by usermod, less issues with characters in the password hash.
Please review and merge, if there's nothing else to do here.
Thanks alot!


text:
code-cursor: 0.43.0 -> 0.43.5

This is a bug fix only update, and the cursor team does not release changelogs for them. Main changelog is here: https://changelog.cursor.com/
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 360159

x86_64-linux

:white_check_mark: 1 package built:

code-cursor

Requested a committer on Matrix so we can close this out.

Replaced by #362556

Two quick follow-ups:
@LunNova You had a great idea and thankfully we will have a proper place to download updates (and rollbacks) soon. Unfortunately, the system treats open "suggestions" as mandatory -- all other approvals are ignored and this PR languished. In the future, an ordinary comment won't block a PR. (Please don't be discouraged.)
@fazo96 While I was trying to get a committer to merge this, the automatic update bot came through with a later version. It takes basically no time to review and get the update merged which is why I closed this PR. (It's no reflection on your work, just that we had all had a quicker path to getting cursor updated.)
Please don't hesitate to create and/or review PRs in the future. We all have a learning curve and you'll find yourself becoming an expert sooner than you think.

No worries at all, makes sense to close this. Thanks!