jiebi/CodeConvo huggingface dataset:
Change:
emanote = haskell.lib.compose.justStaticExecutables haskellPackages.emanote; <del> enchant1 = callPackage ../development/libraries/enchant/1.x.nix { }; </del> enchant2 = callPackage ../development/libraries/enchant/2.x.nix { }; enchant = enchant2;

Discussion:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. &rarr;
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to
Change:
<ins> { lib , buildPythonPackage , fetchFromGitHub , rns , pythonOlder }: buildPythonPackage rec { pname = "lxmf"; version = "0.1.4"; format = "setuptools"; disabled = pythonOlder "3.7"; src = fetchFromGitHub { owner = "markqvist"; repo = "lxmf"; rev = version; hash = "sha256-kWawKlEAnn/uNjM2TT2aVW2V4M0+S/1Ysrw/muJhC0s="; }; propagatedBuildInputs = [ rns ]; # Module has no tests doCheck = false; pythonImportsCheck = [ "LXMF" ]; meta = with lib; { description = "Lightweight Extensible Message Format for Reticulum"; homepage = "https://github.com/markqvist/lxmf"; license = licenses.mit; maintainers = with maintainers; [ fab ]; }; } </ins>

Discussion:
Project description Reticulum is the cryptography-based networking stack for wide-area networks built on readily available hardware. It can operate even with very high latency and extremely low bandwidth. Reticulum allows you to build wide-area networks with off-the-shelf tools, and offers end-to-end encryption and connectivity, initiator anonymity, autoconfiguring cryptographically backed multi-hop transport, efficient addressing, unforgeable delivery acknowledgements and more. Reticulum is a complete networking stack, and does not need IP or higher layers, although it is easy to use IP (with TCP or UDP) as the underlying carrier for Reticulum. It is therefore trivial to tunnel Reticulum over the Internet or private IP networks. Having no dependencies on traditional networking stacks free up overhead that has been utilised to implement a networking stack built directly on cryptographic principles, allowing resilience and stable functionality in open and trustless networks. No kernel modules or drivers are required. Reticulum runs completely in userland, and can run on practically any system that runs Python 3. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin
Change:
riscv-pk = callPackage ../misc/riscv-pk { }; <ins> ristate = callPackage ../tools/misc/ristate { }; </ins> roccat-tools = callPackage ../os-specific/linux/roccat-tools { }; rtsp-simple-server = callPackage ../servers/rtsp-simple-server { };

Discussion:
Project description Provides status information for river. Useful for bars. Metadata source URL: license: mit platforms: linux
Change:
<ins> #!/usr/bin/env nix-shell #!nix-shell -i bash -p nix-update curl jq version=$(curl "https://download.wavebox.app/stable/linux/latest.json" | jq --raw-output '.["urls"]["tar"] | match("https://download.wavebox.app/stable/linux/tar/Wavebox_(.+).tar.gz").captures[0]["string"]') nix-update wavebox --version "$version" </ins>

Discussion:
Package name: wavebox Latest released version: Current version on the unstable channel: Current version on the stable/release channel: (doesn't seem like the has anything to do with Wavebox 114 to 116?) Notify maintainers Note for maintainers: Please tag this issue in your PR.
Change:
<ins> { stdenv , jq , hydrogen-web-unwrapped , conf ? { } }: if (conf == { }) then hydrogen-web-unwrapped else stdenv.mkDerivation { pname = "${hydrogen-web-unwrapped.pname}-wrapped"; inherit (hydrogen-web-unwrapped) version meta; dontUnpack = true; nativeBuildInputs = [ jq ]; installPhase = '' runHook preInstall mkdir -p $out ln -s ${hydrogen-web-unwrapped}/* $out rm $out/config.json jq -s '.[0] * $conf' "${hydrogen-web-unwrapped}/config.json" --argjson "conf" '${builtins.toJSON conf}' > "$out/config.json" runHook postInstall ''; } </ins>

Discussion:
Project description A minimal Matrix chat client, focused on performance, offline functionality, and broad browser support. Metadata homepage URL: source URL: license: Apache platforms: Browser Deer matrix-team maintainers:
I marked this as stale due to inactivity. &rarr;
No reaction, but still interresting for me.
ftfy:
Change:
undaemonize = callPackage ../tools/system/undaemonize {}; <ins> wtfis = callPackage ../tools/networking/wtfis { }; </ins> houdini = callPackage ../applications/misc/houdini {}; openfst = callPackage ../development/libraries/openfst {};

Discussion:
Project description As stated by the developer: Metadata homepage URL: source URL: license: MIT platforms: unix, linux, darwin
Change:
in py.pkgs.buildPythonApplication rec { pname = "salt"; <del> version = "3004"; </del> <ins> version = "3004.1"; </ins> src = py.pkgs.fetchPypi { inherit pname version; <del> sha256 = "PVNWG8huAU3KLsPcmBB5vgTVXqBHiQyr3iXlsQv6WxM="; </del> <ins> hash = "sha256-fzRKJDJkik8HjapazMaNzf/hCVzqE+wh5QQTVg8Ewpg="; </ins> }; propagatedBuildInputs = with py.pkgs; [

Discussion:
are you on top of this?
Thanks for the heads up, yeah, just waited for the GitHub releases to appear. I’ll create a PR soon.
Change:
}; vendorHash = "sha256-pYeHqYd2cCOVQlD1r2lh//KC+732H0lj1fPDBr+W8qA="; <del> patches = [ # Reverts "cmd/tailscaled/tailscaled.service: revert recent hardening" (fetchpatch { url = "https://github.com/tailscale/tailscale/commit/2889fabaefc50040507ead652d6d2b212f476c2b.patch"; hash = "sha256-DPBrv7kjSVXhmptUGGzOkaP4iXi/Bym3lvqy4otL9HE="; revert = true; }) ]; </del> nativeBuildInputs = lib.optionals stdenv.isLinux [ makeWrapper ]; CGO_ENABLED = 0;

Discussion:
On nixpkgs commit , running Tailscale with Tailscale SSH connected, then trying to connect to it, results in an error: . Steps to reproduce the behavior: the tailscale node service with (in my case, using a systemd service). to use Tailscale SSH to access the node (e.g. ). that no shell is opened and the connection is closed immediately. A shell opens (if the default SSH behavior is unchanged). This appears to the result of The underlying patch sets the systemd hardening option , along with an allowlist of devices. This prevents from accessing , which is needed to open a PTY for the shell. Please run and paste the result.
Change:
doCheck = false; <del> pythonImportChecks = [ "pyairports" ]; </del> <ins> pythonImportsCheck = [ "pyairports" ]; </ins> meta = with lib; { description = "pyairports is a package which enables airport lookup by 3-letter IATA code.";

Discussion:
4 packages have the attribute, which is a typo for Steps to reproduce the behavior: 4 packages: no result [ ] pyfunctional & geoparquet: [ ] python_ffmpeg: [ ] pyairports: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I do wish we used or such to warn about typos in derivation attrs
Change:
version = "1.9.8"; pyproject = true; <del> # Still uses distutils, https://github.com/tchellomello/python-amcrest/issues/234 disabled = pythonOlder "3.7" || pythonAtLeast "3.12"; </del> src = fetchFromGitHub { owner = "tchellomello"; repo = "python-amcrest";

Discussion:
Steps to reproduce the behavior: -rebuild switch Here is my config for home-assistant: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
]; }; }; <ins> users.groups.gamemode = { }; </ins> }; meta = {

Discussion:
gamemode is unable to change the processor scheduler Steps to reproduce the behavior: any (schedutil for example) CPU scheduler as default () and to true, set to different CPU scheduler (performance for example) any command with and check logs of service (), there will be pkexec "Not authorized" errors. Or run it will report that tests failing The CPU scheduler is changed to the one specified in for the duration of the execution of the gamemoderun command, and then returned to the default value If applicable, add screenshots to help explain your problem. tested on nixpkgs commit <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This can also be verified with :
This is an upstream change since 1.8, you need to add yourself to the group to change the processor scheduler. See:
Yes, it works if the group is present, but you need to create the group yourself, maybe it's a good idea to create the group if (in module)? Arch linux, for example, have file in gamemode package, that contains for creating gamemode group
Oh yep that makes sense! Will open a new PR for that.
I was also trying to add a NixOS test for it, but you can't set the governor of a CPU within a VM, so I just left it out:
Change:
{ pkgs, nixpkgs ? { }, libsets }: let <del> revision = pkgs.lib.trivial.revisionWithDefault (nixpkgs.revision or "master"); </del> <ins> revision = pkgs.lib.trivial.revisionWithDefault (nixpkgs.rev or "master"); </ins> libDefPos = prefix: set: builtins.concatMap

Discussion:
e.g. the documentation for at currently (22.11) points me to , which is not correct for that version of nixpkgs.
Change:
retry(instance_is_up) machine.succeed("incus exec container test -- -e /run/systemd/system/service.d/zzz-lxc-service.conf") <ins> check_sysctl("container") </ins> ''; })

Discussion:
not working in lxc containers. But sysctl command works fine and /proc/sys/ is writable. This nix option seems to finally take effect via . And the look like this: This looks fine, So I tried to manually run the command in , and it takes effect! But this looks even weirder. Through , I got: There is an unusual . It looks like this: Obviously, there is not is NixOS. So won't run at all. I looked it up on the internet and found out it's from distrobuilder: So maybe we should just patch it? Steps to reproduce the behavior: a privilege container with NixOS in it. something to and rebuild the system , and there is no effect should run and takes effect. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Are you able to you reproduce this with unstable? There are some improvements post 23.11 to the use of the lxc generator.
Yes, I'm already on latest unstable channel. The channel information in metadata tab is incorrect because I'm using flakes. There are many hard-coded FHS paths in distrobuilder. Such as this line, that causes this problem:
can you test this change?
It works fine for me. But I don’t know if there are any problems caused by other hard-coded paths in distrobuilder. And I don’t know whether using sysctl on an unprivileged container will cause the service to fail to start, and whether the startup failure will cause problems. But it seems that sets , so there should be no problem?
Thanks for testing! There shouldn't be, since we patch and wrap the distrobuilder lxc generator. I audited it again after updating the patch for this fix. You can always see the resulting file by building . The PR has tests which should cover unprivileged containers. I've just updated them to add a check verifying systemd-sysctl successfully started.
Change:
nativeBuildInputs = [ which <del> addOpenGLRunpath </del> <ins> autoAddOpenGLRunpathHook </ins> cuda_nvcc ]; buildInputs = [ cuda_cudart <del> ] ++ lib.optionals (lib.versionAtLeast cudaVersion "12.0.0") [ </del> <ins> ] # NOTE: CUDA versions in Nixpkgs only use a major and minor version. When we do comparisons # against other version, like below, it's important that we use the same format. Otherwise, # we'll get incorrect results. # For example, lib.versionAtLeast "12.0" "12.0.0" == false. ++ lib.optionals (lib.versionAtLeast cudaVersion "12.0") [ </ins> cuda_cccl ];

Discussion:
is only ever built with the default version of because the line which adds the derivation never changes the version of provided: I confirmed this by making this change to the derivation and trying to build it with two different versions of . Notice that the error is the same: <details</detailsIn the pattern seems to be passing . However, it is relatively rare that the derivation takes as an argument. Instead, it seems to be preferred to have the derivation take, as arguments, the actual python packages required. To bring the NCCL derivation in line with this pattern, it should take the CUDA packages it requires as arguments. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
We only expose nccl as . Let's change it to take cudaPackages' individual attributes as arguments, so that works properly. Nccl already uses solely the redist packages, so I guess we needn't worry about cuda10
Agreed -- WIP at Running a now :)
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Well, since gh pushed a notification anyway: that's one long nixpkgs-review:)

As proposed in , should switch to because invoking is manual and can easily cause breakages if files are missed. This is a followup from <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
<ins> { lib , rustPlatform , fetchFromGitHub , pkg-config , libGL , pipewire , xorg }: rustPlatform.buildRustPackage rec { pname = "pw-viz"; version = "0.1.0"; src = fetchFromGitHub { owner = "ax9d"; repo = pname; rev = "v${version}"; sha256 = "1d46m7w6rzzjpxc2fxwka9xbz49szbfrl63kxlv6kw4lknrladjn"; }; cargoSha256 = "sha256-jx1mUP6ezpwUhmDD9tCJBhHCHU8fEMlB738yYfB1psc="; nativeBuildInputs = [ pkg-config ]; buildInputs = [ libGL pipewire rustPlatform.bindgenHook xorg.libX11 xorg.libXcursor xorg.libXi xorg.libxcb ]; postFixup = '' patchelf $out/bin/pw-viz --add-rpath ${lib.makeLibraryPath [ libGL xorg.libXrandr ]} ''; meta = with lib; { description = "A simple and elegant pipewire graph editor "; homepage = "https://github.com/ax9d/pw-viz"; license = licenses.gpl3Only; maintainers = with maintainers; [ figsoda ]; platforms = platforms.linux; }; } </ins>

Discussion:
... in Rust! Project description Pipewire graph editor written in Rust. ( WIP warning ) Maybe it's too early? I'm not sure, it looks usable at least from the screenshot... Metadata homepage URL: source URL: license: gpl3 platforms: linux,
Change:
buildPythonPackage rec { pname = "SPARQLWrapper"; <del> version = "1.7.6"; </del> <ins> version = "1.8.2"; </ins> src = fetchPypi { inherit pname version; <del> sha256 = "1y12hpsfjd779yi29bhvl6g4vszadjvd8jw38z5rg77b034vxjnw"; </del> <ins> sha256 = "7f4c8d38ea1bfcffbc358c9a05de35a3fd7152cc3e8ea57963ee7a0a242f7a5e"; </ins> }; # break circular dependency loop

Discussion:
Ran . For some reason there are pylint tests running for ~8 minutes that eventually end up in a failure. <details<summaryPyLint test failures</summary</detailson pylint (indirectly?); running for ~10 minutes as part of package installation process.
This will need to be backported to 18.09 as the latest version released by Hydra is broken too
The tests still fails even after the above patch applied. <details<summaryHere is the log</summary</detailsHere is the patch I used: Edit: the original patch is working on the python-unstable branch so I guess it's OK
I pushed a fix to the branch: . The fix for is currently in the branch: .
Change:
<option>hardware.nvidia.prime.intelBusId</option>). ''; }; <ins> hardware.nvidia.nvidiaPersistenced = mkOption { default = false; type = types.bool; description = '' Update for NVIDA GPU headless mode, i.e. nvidia-persistenced. It ensures all GPUs stay awake even during headless mode. ''; }; </ins> }; config = mkIf enabled {

Discussion:
As described here it would be useful to add an option in to add a systemd entry which forces GPU's to always be online even in headless systems. Here is what the extracted systemd service would look like (taken from )
Change:
description = "Drop-down terminal for GNOME"; homepage = "http://guake-project.org"; license = licenses.gpl2Plus; <del> maintainers = [ maintainers.msteen ]; </del> <ins> maintainers = [ maintainers.msteen maintainers.heywoodlh ]; </ins> platforms = platforms.linux; }; }

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: lack of directory with executables In contrast this command works as expected: Create directory with executables to invoke Guake. Observe that nixpkgs 24.05 has and in the "Programs provided" section. <img width="989" alt="image" src=""And unstable does not despite both claiming to have version 3.10 of Guake: <img width="1201" alt="image" src=""And both branches provide the same package definition. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Seems like the cause is the below. Oddly the command fails but the build doesn't.
Change:
$GOPATH/bin/symfony-cli ''; <del> meta = with lib; { </del> <ins> meta = { </ins> description = "Symfony CLI"; homepage = "https://github.com/symfony-cli/symfony-cli"; <del> license = licenses.agpl3Plus; maintainers = with maintainers; [ drupol ]; </del> <ins> license = lib.licenses.agpl3Plus; </ins> mainProgram = "symfony"; <ins> maintainers = with lib.maintainers; [ drupol ]; </ins> }; }

Discussion:
Given you have PHP installed on your host and one installed in your Nix shell + symfony-cli, eg. with these packages , running will always prefer PHP installed by host. This is not an issue with Nix per se but symfony-cli, but I suggest here that symfony-cli package should be patched so that this does not happen. Steps to reproduce the behavior: Terminal 1 terminal 2 Curl statement should return PHP/8.2.5, as that's the one installed by Nix. Not 8.1.2. Current workaround is replacing symfony-cli with which strips out everything {php}/bin Please run and paste the result.
That does not make sense. Why does Symfony not use the correct PHP from PATH? I would expect any proper PATH respecting program to return the same thing as .
I agree after making a couple of tests, I believe that wrapping the binary with the PHP path is not necessary... Check the screenshot in
I don't know, but this is what they use for discovery of php versions I've not dig depeer than having a brief looks though. And I have to remind that this is about command. command does look to be honoring $PATH correctly.
Does this means that does not employ the same mechanism for locating in the and commands? which seems totally uncommon. It would be nice to have the confirmation from one of the maintainers ( ?)
I've prepared a patch at I hope they will merge it soon. Otherwise we should consider adding a patch for this here.
I think this issue can be closed now.
Yup, thanks again!
After thinking twice, the issue will be definitely fixed as soon as you publish a new tag and we provide an update in Nix, I'll leave it open in the meantime.
7 has been released now.
PR is made, I'll wait for the CI to be done before merging and closing this issue.
Change:
stdenv.mkDerivation rec { name = "uriparser-${version}"; <del> version = "0.9.0"; </del> <ins> version = "0.9.1"; </ins> # Release tarball differs from source tarball src = fetchurl { url = "https://github.com/uriparser/uriparser/releases/download/${name}/${name}.tar.bz2"; <del> sha256 = "0b2yagxzhq9ghpszci6a9xlqg0yl7vq9j5r8dwbar3nszqsfnrzc"; </del> <ins> sha256 = "1gisi7h8hd6mswbiaaa3s25bnb77xf37pzrmjy63rcdpwcyqy93m"; </ins> }; nativeBuildInputs = [ pkgconfig doxygen graphviz ];

Discussion:
Hi! Just a quick heads up that with security fixes has been released. Thanks for updating!
Thank you!
Change:
services.xserver.xkbDir = mkDefault "${pkgs.xkeyboard_config}/etc/X11/xkb"; <ins> system.extraDependencies = [ (pkgs.runCommand "xkb-layouts-exist" { layouts=cfg.layout; } '' missing=() while read -d , layout do [[ -f "${cfg.xkbDir}/symbols/$layout" ]] || missing+=($layout) done <<< "$layouts," if [[ ''${#missing[@]} -eq 0 ]] then touch $out exit 0 fi cat >&2 <<EOF Some of the selected keyboard layouts do not exist: ''${missing[@]} Set services.xserver.layout to the name of an existing keyboard layout (check ${cfg.xkbDir}/symbols for options). EOF exit -1 '') ]; </ins> services.xserver.config = '' Section "ServerFlags"

Discussion:
I just realized that the correct ISO 3166-1 country code for the united kingdom, is actualy . before then, I assumed that something in the interaction between nixoskde was broken and it was impossible to update the locale. weirdly enough, requires and not , but it notifies of an error if you select . Similarly, gives you an error if you select instead of instead silently fails and doesn't change the layout if you specify an incorrect code by mistake
Change:
feature = "build packages with CUDA support by default"; }; <ins> replaceBootstrapFiles = mkMassRebuild { type = types.functionTo (types.attrsOf types.package); default = lib.id; defaultText = literalExpression "lib.id"; description = '' Use the bootstrap files returned instead of the default bootstrap files. The default bootstrap files are passed as an argument. ''; example = literalExpression '' prevFiles: let replacements = { "sha256-YQlr088HPoVWBU2jpPhpIMyOyoEDZYDw1y60SGGbUM0=" = import <nix/fetchurl.nix> { url = "(custom glibc linux x86_64 bootstrap-tools.tar.xz)"; hash = "(...)"; }; "sha256-QrTEnQTBM1Y/qV9odq8irZkQSD9uOMbs2Q5NgCvKCNQ=" = import <nix/fetchurl.nix> { url = "(custom glibc linux x86_64 busybox)"; hash = "(...)"; executable = true; }; }; in builtins.mapAttrs (name: prev: replacements.''${prev.outputHash} or prev) prevFiles ''; }; </ins> rocmSupport = mkMassRebuild { type = types.bool; default = false;

Discussion:
Today provides an outdated set of : Specifically I keep hitting on any attempts to rebuild 32-bit packages. Currently I am patching the to provide the working tools built locally: I think it would be generally useful to be able to pass non-default tools for workaround purposes and testing purposes of new tools. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
people who want this, can you review