jiebi/CodeConvo huggingface dataset:
Change:
( name: instance: { name = "btrbk/${name}.conf"; <del> value.source = mkTestedConfigFile name instance.settings; </del> <ins> value.source = mkConfigFile name instance.settings; </ins> } ) cfg.instances;

Discussion:
in btrbk's example configuration. This information can be found in too. The structure of in the NixOS module should conform to the way that the configuration actually works. In this case, the configuration is an ordered list of pairs, but since Nix does not really have this data type, probably a text block like s elsewhere would be most appropriate. The current attribute should be deprecated. I can make a PR for this if the above changes look appropriate.
are always generated under a section. So any settings inside will actually belong to that volume, according to btrbk's "applying to last volume" behavior. This makes the setting generation is truely order independent, and prevent the footgun of btrbk's handling of configurations. The current impl should prevent but not cause the cross-interaction. Is there any practical bug you have met with the current config generation? No. In module system, options are merged by some implicit order when there is no explicit or . This makes approach have a surprising interaction with other definitions of the same option, contradicting your intention.
there is sorting in place so the order is deterministic: for each nesting level, key value pairs go first and nested attributes go last. this makes the nix -btrbk mapping deterministic and conforming to the note you linked: global values go first.
Thanks for explaining this -- I probably should have taken more time to look the implementation already in place. That being said, I did experience a bug when migrating from a working to the NixOS module (or at least it seems like a bug to me). Under , I have: which generates The above Nix config seems to imply that should be applied to whole not just , but this is, in fact, what the generated config produces. I might be missing something here.
Could it be that is the culprit? is being treated like a subsection, which it is, but it is not subsection like /.
:thinking: So can be both a section and a child of section . I think modifying the sorting order to other options ---could fix it. Generally it's better to make the whole typed. But maybe it would take much effort.
Fixing the sort order would be a good occasion to make it clear in the description of the option.

About making settings typed: did it but it would be better with a free-form module so that we do not need to adapt the module when new options are to btrbk like rfc 42 advises. (note that I didn't know about free-form modules when I rejected this PR)
The issue here is that whether an option is a "section" or "subsection" matters. We need special cases to give them priority, or it would break silently. That may be worse than "need to adapt for new options".
we can have both with a free-form module
Do you have interest to fix the field sorting and maybe port with free-form modules? If no one claims it in 24h, I'll try it tomorrow.
Change:
pytest-mock pytestCheckHook setuptools <del> tomlkit </del> virtualenv ];

Discussion:
changed behaviour between nixos 22.11 and NixOS 23.05, apparently producing semantically different outputs (which broke our telegraf module) Bisect implies this is the commit that broke(?) remarshal: Was this intentional?
cc as maintainer of remarshal cc as author (I think?) of
Oh yeah that's definitely not intentional, at least from Nixpkgs side. It's unfortunate that we depend on a third-party for this.. We could pin to prevent such breakages, but we should definitely have a test case that covers this breakage.
Change:
in buildPythonPackage rec { pname = "pyopencl"; <del> version = "2024.2.6"; format = "pyproject"; </del> <ins> version = "2024.2.7"; pyproject = true; </ins> src = fetchFromGitHub { owner = "inducer"; repo = "pyopencl"; rev = "refs/tags/v${version}"; <del> hash = "sha256-nP7ZAGeRXrjqDRWlc2SDP1hk1fseGeu9Zx0lOp9Pchs="; </del> <ins> fetchSubmodules = true; hash = "sha256-VeaEDYnGfMYf9/WqMIZ9g4KounD48eWF3Romt79RMEQ="; </ins> }; <del> nativeBuildInputs = [ </del> <ins> build-system = [ </ins> cmake nanobind ninja numpy <del> oldest-supported-numpy </del> pathspec scikit-build-core ];

Discussion:
The pyopencl library module that is installed is nonfunctional. While works, importing submodules like doesn't, and the package that gets imported doesn't seem to have any pertinent fields. The directory tree in the store also looks very suspiciously empty: I don't know exactly what it's supposed to contain, but the older versions of this derivation in my store are full of files. should work. (a bit arbitrary as the last one to touch the derivation). Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The culprit is the commit (a version bump).
Change:
buildGoModule rec { pname = "consul"; <del> version = "1.10.3"; </del> <ins> version = "1.10.10"; </ins> rev = "v${version}"; # Note: Currently only release tags are supported, because they have the Consul UI

Discussion:
, CVSSv3=6.5 (nixos-21.11) HashiCorp Consul and Consul Enterprise 1.8.0 through 1.9.14, 1.10.7, and 1.11.2 has Uncontrolled Resource Consumption. Scanned versions: nixos-21.11: . Cc Cc Cc Cc
PR
Change:
platforms = []; source = { remotes = ["https://rubygems.org"]; <del> sha256 = "19ynyc7wzl71hn7jw467xr188v0az679l54167slm3jh5mx6rijf"; </del> <ins> sha256 = "03qiz6kbk260v3613z4wrk8iy1mi06j631fglcskfxyhf18lpy05"; </ins> type = "gem"; }; <del> version = "6.0.7"; </del> <ins> version = "6.0.8"; </ins> }; hashie = { groups = ["default"];

Discussion:
Project description Metadata license: MIT platforms: Any
I guess the issue can be closed due to . Reopen if I am incorrect
Oh, weird. The " in wasn't applied automatically. Thank you!
Change:
sqlalchemy ]; "myq" = ps: with ps; [ <del> ]; # missing inputs: python-myq </del> <ins> python-myq ]; </ins> "mysensors" = ps: with ps; [ aiohttp-cors janus

Discussion:
The home-assistant component currently declares that it's missing the input However the package actually exists, it's just called . This appears to be the old name of the package, it looks as though it got renamed at some point, although the nixpkgs packge for it wasn't updated for the name change.
Note that merely setting restores the component's functionality.
Change:
src = fetchurl { url = "https://www.renpy.org/dl/${renpy_version}/pygame_sdl2-${version}+renpy${renpy_version}.tar.gz"; <del> hash = "sha256-Zib39NyQ1pGVCWPrK5/Tl3dAylUlmKZKxU8pf+OpAdY="; </del> <ins> hash = "sha256-bcTrdXWLTCnZQ/fP5crKIPoqJiyz+o6s0PzRChV7TQE="; </ins> }; # force rebuild of headers needed for install

Discussion:
Package name: renpy Latest released version: 8.3.2 <!-- Search your package here: --- Current version on the unstable channel: 8.2.1. Current version on the stable/release channel: 8.2.1. <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<del> { lib, fetchFromGitHub, python3Packages }: </del> <ins> { lib, fetchFromGitHub, python3Packages, gobject-introspection, wrapGAppsNoGuiHook }: </ins> python3Packages.buildPythonPackage rec { pname = "open-fprintd";

Discussion:
Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
minijail-tools = python3.pkgs.callPackage ../tools/system/minijail/tools.nix { }; <ins> minilibx = callPackage ../development/libraries/minilibx { }; </ins> minixml = callPackage ../development/libraries/minixml { }; mir-qualia = callPackage ../tools/text/mir-qualia {

Discussion:
a simple X-Window (X11R6) programming API in C, designed for students, suitable for X-beginners homepage URL: source URL: license: BSD-2-Clause license platforms: linux
Change:
}; nativeBuildInputs = [ <ins> appstream-glib </ins> desktop-file-utils # for update-desktop-database glib gobject-introspection

Discussion:
(init 0.4 version) cannot start, shows log and exit with code 1. Here is the full log: (): Gjs-CRITICAL : 10:24:13.181: JS ERROR: Error: Requiring Soup, version 2.4: Typelib file for namespace 'Soup', version '2.4' not found (): Gjs-CRITICAL : 10:24:13.181: Script /nix/store/x9fvn8b614lg6xmdc259q6cx9crbrqpx-clapper- threw an exception Steps to reproduce the behavior: the package. (nix-shell -p clapper) to start it. (clapper) shows error and exit with code 1. I checkout the package in nixpkgs: It seems missing a build deps & a runtime deps libsoup. Add them together to buildInputs fixes this issues. If the mantainer agrees, I can do a PR : ) Maintainer information:
works fine for me on my amd64 desktop, but I can reproduce your error on my Pinephone. Sounds good to me! :)
To try to reproduce this problem, I make these files to build-vm: It cannot start on the QEMU VM too. I'll make a PR right now.
Change:
}; }; <del> flake8 = buildPythonPackage rec { name = "flake8-${version}"; version = "3.2.1"; src = pkgs.fetchurl { url = "mirror://pypi/f/flake8/${name}.tar.gz"; sha256 = "c7c460b5aff3a2063c798a77af18ec70af3941d35a22e2e76965e3c0e0b36055"; }; buildInputs = with self; [ pytest mock pytestrunner ]; propagatedBuildInputs = with self; [ pyflakes pycodestyle mccabe ] ++ optionals (pythonOlder "3.4") [ enum34 ] ++ optionals (pythonOlder "3.2") [ configparser ]; meta = { description = "Code checking using pep8 and pyflakes"; homepage = http://pypi.python.org/pypi/flake8; license = licenses.mit; maintainers = with maintainers; [ garbas ]; }; }; </del> <ins> flake8 = callPackage ../development/python-modules/flake8 { }; </ins> flake8-blind-except = callPackage ../development/python-modules/flake8-blind-except { };

Discussion:
Flake8 with Python 3.6 fails to build with System: 17.09pre106916. (Hummingbird) Nix version: nix-env (Nix) 1.11.9 Nixpkgs version: 17.09pre106916. Sandboxing enabled: build-use-sandbox = false
Try upgrading the pyflakes expression to the latest version
I can produce this same problem using nixpkgs commit (latest master as of this writing).
Change:
rustPlatform.buildRustPackage rec { pname = "sequoia-sqv"; <del> version = "1.1.0"; </del> <ins> version = "1.2.1"; </ins> src = fetchFromGitLab { owner = "sequoia-pgp"; repo = "sequoia-sqv"; rev = "v${version}"; <del> hash = "sha256-KoB9YnPNE2aB5MW5G9r6Bk+1QnANVSKA2dp3ufSJ44M="; </del> <ins> hash = "sha256-frGukJDsxq+BWLPC/4imfc42lDKVF8BPIQQDazaLaQ0="; </ins> }; <del> cargoPatches = [ ./Cargo.lock.patch ]; cargoHash = "sha256-E6tNOc3omg6yLwCP+MdyBF/HmFTBFCiXd5r+jflfs4k="; </del> <ins> cargoHash = "sha256-1h1nXtXMTwL8ICxWTV8My0IdE+6w0L7xXZD012Cv5U8="; </ins> nativeBuildInputs = [ pkg-config

Discussion:
Steps to reproduce the behavior: Observed: Full checkPhase log (copied from Garnix): Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --- system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The checkPhase still fails with this PR applied, but it is a different error: Error: While creating /homeless- Caused by: Permission denied (os error 13)
Thanks for the report (I thought I rebuilt it successfully before I opened the PR). Now should be ready now (the failing test is skipped, and an upstream issue was created).
Change:
chmod -R a+w externals/zstd ''; <del> # Todo: cubeb audio backend (the default one) doesn't work on the SDL interface. # This seems to be a problem with libpulseaudio, other applications have similar problems (e.g Duckstation). # Note that the two interfaces have two separate configuration files. </del> <ins> # Fixes https://github.com/NixOS/nixpkgs/issues/171173 postInstall = lib.optionalString (enableCubeb && enableSdl2) '' wrapProgram "$out/bin/citra"  --prefix LD_LIBRARY_PATH : ${lib.makeLibraryPath [ libpulseaudio ]} ''; </ins> meta = with lib; { homepage = "https://citra-emu.org";

Discussion:
Cubeb is an audio backend often used in emulators, and it doesn't work on two specific emulators: Citra and Duckstation. Launch a game with this backend, and there will be no audio. Both emulators also have an SDL audio backend that works, but Cubeb is the default one. Strangely, this issue affects only the SDL interface: the emulators also have a Qt interface, and there is no issue there. (Do not confuse the SDL interface with the SDL audio backend!) Steps to reproduce the behavior: Citra or Duckstation; don't have to change any settings, the audio backend is already Cubeb; a game from the SDL interface ( or ); audio. There is audio when playing the game. The issue isn't new, it's probably there from the very beginning. On Duckstation the problem was even worse, the Cubeb audio backend didn't work on the Qt interface either. I have no idea what happened that made it work. There are comments on both their respective about this issue. They should be removed when this is solved (and Duckstation's one is outdated). Dolphin should experience the same issue, but it doesn't. Cubeb initializes just fine (logs say it uses the pulse backend). By the way, are there any other emulators with an SDL interface other than these three to test? Citra says: And Duckstation: Which is logged from here: Citra: Duckstation: I'm using Pipewire with Wireplumber (and used media-session in the past).
likely needs to be populated. libcubeb is also used in Firefox and you can see an example of populating in the wrapper.
I gave a look at Firefox's derivation, and Cubeb isn't in . Cubeb is vendored in all of these applications (Citra, Duckstation, Dolphin and Firefox) and I guess statically linked too, so I doubt that's the problem.
Sorry I should have clarified. libcubeb uses , you need libpulse, sndio, jack and friends in .
Change:
, nginx-doc , nixosTests <del> , substituteAll, removeReferencesTo, gd, geoip, perl </del> <ins> , installShellFiles, substituteAll, removeReferencesTo, gd, geoip, perl </ins> , withDebug ? false , withKTLS ? false , withStream ? true

Discussion:
I would prefer package to install man pages in some form. The command should show manpage from shipped in release tarball. I tried a trivial implementation, but it seems to be entangled with : . Would be nice to make derivation more amenable to such changes without the breakage.
Change:
<ins> { lib , rustPlatform , fetchFromGitHub , kclvm }: rustPlatform.buildRustPackage rec { pname = "kclvm_cli"; version = "0.8.7"; src = fetchFromGitHub { owner = "kcl-lang"; repo = "kcl"; rev = "v${version}"; hash = "sha256-ieGpuNkzT6AODZYUcEanb7Jpb+PXclnQ9KkdmlehK0o="; }; sourceRoot = "source/cli"; cargoLock.lockFile = ./Cargo.lock; cargoPatches = [ ./cargo_lock.patch ]; buildInputs = [ kclvm ]; meta = with lib; { description = "A high-performance implementation of KCL written in Rust that uses LLVM as the compiler backend"; homepage = "https://github.com/kcl-lang/kcl"; license = licenses.asl20; platforms = platforms.linux; maintainers = with maintainers; [ selfuryon peefy ]; mainProgram = "kclvm_cli"; }; } </ins>

Discussion:
After installation kcl-cli shell completion is not available. Steps to reproduce the behavior: kcl-cli completion Shell completion should be installed. N/A N/A <!-- 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]:
Change:
githubId = 5561189; name = "Cody Opel"; }; <ins> cofob = { name = "Egor Ternovoy"; email = "cofob@riseup.net"; matrix = "@cofob:matrix.org"; github = "cofob"; githubId = 49928332; keys = [{ fingerprint = "5F3D 9D3D ECE0 8651 DE14  D29F ACAD 4265 E193 794D"; }]; }; </ins> Cogitri = { email = "oss@cogitri.dev"; github = "Cogitri";

Discussion:
Project description Client for proxmox backup server written in Rust. Metadata homepage URL: source URL: ;a=summary license: aGPLv3. platforms: unix, linux
It would also be nice if some sort of service that backups certain folders on a CRON timer to the server. Like:
I have built a derivation for in 2020 (but currently only at version ) that I'm using on some machines and my phone (via nix-on-droid). I'll see if I can update that derivation to the latest release and clean it up for inclusion in nixpkgs.
any updates?
Hello, I packaged 2.2.1:
I moved this version to PR, thanks.
Change:
$hass->succeed("curl http://localhost:8123/api/states/binary_sensor.mqtt_binary_sensor -H 'x-ha-access: ${apiPassword}' | grep -qF '"state": "on"'"); # Toggle a binary sensor using hass-cli <del> $hass->succeed("${hassCli} entity get binary_sensor.mqtt_binary_sensor | grep -qF '"state": "on"'"); </del> <ins> $hass->succeed("${hassCli} --output json entity get binary_sensor.mqtt_binary_sensor | grep -qF '"state": "on"'"); </ins> $hass->succeed("${hassCli} entity edit binary_sensor.mqtt_binary_sensor --json='{"state": "off"}'"); $hass->succeed("curl http://localhost:8123/api/states/binary_sensor.mqtt_binary_sensor -H 'x-ha-access: ${apiPassword}' | grep -qF '"state": "off"'");

Discussion:
tests pass, while tests fail with: Official Hydra sees the same thing: with their Travis setup. (That is a build of a recent commit, but I still see the same failures after pointing at a checkout of ) Does anyone have any ideas? With nixpkgs master,
See scrapinghub/dateparser, scrapinghub/dateparser and scrapinghub/dateparser.
As long as this problem remains, the best thing to do is using for affected application. Switching to should be done in commits that don't change anything else and that reference this issue in their commit message so that they can easily be reverted. Simply skipping the tests does not make much sense since these are real incompatibilities.
Change:
<ins> { lib , stdenvNoCC , fetchurl , undmg , pname , version , hash , isAarch64 , metaCommon ? { } }: let pname = "losslesscut"; src = fetchurl { url = "https://github.com/mifi/lossless-cut/releases/download/v${version}/LosslessCut-mac-${if isAarch64 then "arm64" else "x64"}.dmg"; inherit hash; }; in stdenvNoCC.mkDerivation { inherit pname version src; nativeBuildInputs = [ undmg ]; sourceRoot = "LosslessCut.app"; installPhase = '' mkdir -p "$out/Applications/LosslessCut.app" cp -R . "$out/Applications/LosslessCut.app" mkdir -p "$out/bin" ln -s "$out/Applications/LosslessCut.app/Contents/MacOS/LosslessCut" "$out/bin/losslesscut" ''; meta = metaCommon // (with lib; { platforms = singleton (if isAarch64 then "aarch64-darwin" else "x86_64-darwin"); mainProgram = "losslesscut"; }); } </ins>

Discussion:
Losslesscut crashes at startup due to missing Steps to reproduce the behavior: # crash # works Losslesscut works out-of-the-box. probably just needs a in .
It seems to come from a sandboxing feature of Chromium. (LosslessCut is an Electron app, and Electron uses Chromium, IIUC.) I'll add the flag when I'm available. Should it be to both the Linux and the Darwin binary, or just to the former?
I was only able to test on Linux. While you're at it: When bumping the version, filenames need a change (only tested for Linux): and is still open.
Thank you for reminding! After a quick test, 3.43.0 does run out-of-the-box on my machine Does it crash because the user namespaces is unavailable? Does the same problem happen to , it is another electron app packaged the same way. Does it happen to itself?
I can confirm that it works ootb on NixOS 21.11, but not on 22.05. Caprine crashes in a similar way on NixOS 22.05: Chromium works on both.
How about onlyoffice-bin? If does work, it might have something to do with .
works on 22.05
I'm working on it, but couldn't find a way to call in . To be exact, I don't know how to inject the dependency , a setup hook, into the builder. How should I do it? Thanks a lot for your patience.
Is this issue still relevant?
Last time I checked: Yes. I've got this still on my list and will close in case it is resolved.
It should now be fixed in .
Confirmed.
Change:
, cacert , openssl , darwin <ins> , nix-update-script </ins> , testers , dioxus-cli }: rustPlatform.buildRustPackage rec { pname = "dioxus-cli"; <del> version = "0.5.6"; </del> <ins> version = "0.5.7"; </ins> src = fetchCrate { inherit pname version; <del> hash = "sha256-cOd8OGkmebUYw6fNLO/kja81qKwqBuVpJqCix1Izf64="; </del> <ins> hash = "sha256-/LeMh5WX4dvkveu5w6qBQLbtoi5yUW6iad0YatA/tMQ="; </ins> }; <del> cargoHash = "sha256-shllaNdg9g6fD8qRyCKpN47keFUTu0g96MzVX4BrhXI="; </del> <ins> cargoHash = "sha256-D6y2NiFqSf0u6icSKCRZK7ycR+GswOX627M7PEy/D6U="; </ins> nativeBuildInputs = [ pkg-config cacert ]; buildInputs = [ openssl ] ++ lib.optionals stdenv.hostPlatform.isDarwin [

Discussion:
Package name: Latest released version: 0.5.7 <!-- Search your package here: --- Current version on the unstable channel: 0.5.6 Current version on the stable/release channel: 0.5.4 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
installPhase = '' install -D pipework $out/bin/pipework wrapProgram $out/bin/pipework --prefix PATH :  <del> ${lib.makeBinPath [ bridge-utils iproute2 lxc openvswitch docker busybox dhcpcd dhcp ]}; </del> <ins> ${lib.makeBinPath [ bridge-utils iproute2 lxc openvswitch docker busybox dhcpcd ]}; </ins> ''; meta = with lib; { description = "Software-Defined Networking tools for LXC";

Discussion:
Was announced multiple times, now it is EOL with release 4.2.3 We should remove it before branching 22.05.
Change:
}; }; <ins> serial = buildPythonPackage rec { name = "pyserial-2.5"; doCheck = false; src = fetchurl { url = http://heanet.dl.sourceforge.net/project/pyserial/pyserial/2.5/pyserial-2.5.tar.gz; sha256 = "04gmpfb43ppc8cf1bvkz8r1gl0nrxc38kpfdqs40ib0d1ql25pgd"; }; }; </ins> tracing = buildPythonPackage rec { name = "tracing-0.6";

Discussion:
Presumably since , 's makes use of the new section which our binutils 2.35 doesn't understand, leading to warnings such as this one: More context can be found here: which describes the section Since binutils 2.36, supports the new note section. However we have been hesitant to update binutils so far (since it usually introduces a lot of breakage, e. g. see ). Open question: Is this a serious problem? Should we apply the patch from 2.36? Should we disable in the meantime where we use it? Build any haskell package on a platform that supports (with if necessary). <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Maintainer information:
I'd expect this would get fixed by PR
I've tried but that doesn't seem to fix it for me. It leads to a lot of warnings when building some custom packages so curious about a solution.
All warnings I've experienced so far have been fixed by this (or some other change).
I think this is fixed now? Haven't seen the warning for a long time now.
Change:
dependencies = [ bleak dotmap <ins> packaging </ins> pexpect protobuf pygatt

Discussion:
Running the meshtastic CLI (python3Packages.meshtastic) fails with this error: It works if you run it using . Steps to reproduce the behavior: . The program runs correctly. <!-- 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]:
Seems like just adding to the dependencies works