jiebi/CodeConvo huggingface dataset:
Change:
''; }) enabledServers); <del> boot.kernel.sysctl = mkMerge [ { "vm.nr_hugepages" = "0"; } ( mkIf cfg.vmOverCommit { "vm.overcommit_memory" = "1"; } ) ]; </del> <ins> boot.kernel.sysctl = mkIf cfg.vmOverCommit { "vm.overcommit_memory" = "1"; }; </ins> networking.firewall.allowedTCPPorts = concatMap (conf: optional conf.openFirewall conf.port

Discussion:
Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: redis via: at the log and observe: Expected behavior No warnings or errors in log. Additional context I thought line was supposed to prevent such a warning... :thinking: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --ping Metadata Please run and paste the result. Maintainer information:
If the sysctl doesn't work, we can probably also put the suggested line into the script. :thinking: This should be relatively easy to test, given we have a NixOS vm test :-)
As long as another solution does not fail loudly in containers, i.e. reintroduce bug which we fixed by switching to sysctl. I’m game. But my question is: Is the broken since that "fix"? Can others reproduce this issue? Or is maybe running redis in a container where this line doesn’t take effect?
I'm just running on a regular NixOS install which happens to be running on VMWare.
Strange... when I add to the test I don't see the warning :thinking:
I marked this as stale due to inactivity. &rarr;
Change:
<ins> { stdenv , lib , fetchFromGitHub , gitUpdater }: stdenv.mkDerivation rec { pname = "layan-kde"; version = "2022-02-13"; src = fetchFromGitHub { owner = "vinceliuice"; repo = pname; rev = version; sha256 = "09z90g13l26v23nwr8n5bapwldp3hhdrdikynvm4vvb7qsvb4vrp"; }; postPatch = '' patchShebangs install.sh substituteInPlace install.sh  --replace '$HOME/.local' $out  --replace '$HOME/.config' $out/share ''; installPhase = '' runHook preInstall name= ./install.sh --dest $out/share/themes mkdir -p $out/share/sddm/themes cp -a sddm/Layan* $out/share/sddm/themes/ runHook postInstall ''; passthru.updateScript = gitUpdater {inherit pname version; }; meta = with lib; { description = "A flat Design theme for KDE Plasma desktop"; homepage = "https://github.com/vinceliuice/Layan-kde"; license = licenses.gpl3Only; platforms = platforms.all; maintainers = [ maintainers.romildo ]; }; } </ins>

Discussion:
Project description Layan kde is a flat Design theme for KDE Plasma desktop. In this repository you'll find: Aurorae Themes Kvantum Themes Plasma Color Schemes Plasma Desktop Themes Plasma Look-and-Feel Themes Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
stdenv.mkDerivation rec { pname = "opendmarc"; <del> version = "1.3.3"; </del> <ins> version = "1.4.2"; </ins> src = fetchFromGitHub { owner = "trusteddomainproject"; repo = "opendmarc"; rev = "rel-opendmarc-${builtins.replaceStrings [ "." ] [ "-" ] version}"; <del> sha256 = "sha256-SQH85FLfVEEtYhR1+A1XxCDMiTjDgLQX6zifbLxCa5c="; </del> <ins> hash = "sha256-vnWtTvHhzCed7P6rN3wAz6zfRvtV0cLn5GhDxLF8H3c="; </ins> }; outputs = [ "bin" "dev" "out" "doc" ];

Discussion:
Exim 4.97.1 has been released to fix CVE-2023-. This will also need a backport to the stable channel. Package name: exim Latest released version: 4.97.1 Current version on the unstable channel: 4.96.2 (vulnerable Current version on the stable/release channel: 4.96.2 (vulnerable) 4.96: Notify maintainers 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:
]; passthru = { <del> inherit sip; </del> <ins> inherit sip pyqt5_sip; </ins> multimediaEnabled = withMultimedia; webKitEnabled = withWebKit; WebSocketsEnabled = withWebSockets;

Discussion:
Describe the bug Running gives the following error message: To Reproduce Steps to reproduce the behavior: . . Notify maintainers Metadata
I marked this as stale due to inactivity. &rarr;
This is still an issue.
I can confirm the bug.
Change:
}; buildInputs = [ <del> alsaLib bzip2 cairo dbus dbus-glib file fontconfig freetype gst-plugins-base gstreamer gst_all_1.gst-plugins-base gtk2 hunspell icu libevent libjpeg libnotify libstartup_notification libvpx makeWrapper libGLU_combined nspr nss pango perl pkgconfig python libpulseaudio sqlite unzip which yasm zip zlib </del> <ins> alsaLib bzip2 cairo dbus dbus-glib ffmpeg file fontconfig freetype gnome2.GConf gnum4 gtk2 hunspell libevent libjpeg libnotify libstartup_notification makeWrapper libGLU_combined perl pkgconfig python libpulseaudio unzip wget which yasm zip zlib </ins> ] ++ (with xorg; [ libX11 libXext libXft libXi libXrender libXScrnSaver libXt pixman xorgproto

Discussion:
On November 13th Palemoon 28.2.0 was released with very important security updates: This browser has an integrated update checker which is complaining repeatedly about the security update (which is good!) Install palemoon, wait a few minutes, a pop-up window raises asking to update palemoon. system: host os: multi-user?: sandbox: version: channels(user): nixpkgs:
Change:
../virtualisation/nixos-containers.nix ../services/x11/desktop-managers/xterm.nix ]; <del> config = { }; </del> <ins> # swraid's default depends on stateVersion config.boot.swraid.enable = false; </ins> options.boot.isContainer = lib.mkOption { default = false; internal = true; }; } ];

Discussion:
Steps to reproduce the behavior: After , uses to determine its default value. That conflicts with the assumption of that no should be set. <!-- 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.
I was able to run the builder in the meantime with this command: the default SSH port in that version is . found it in these are the for reference.
Change:
}; nativeBuildInputs = [ <ins> makeWrapper </ins> pkg-config ];

Discussion:
I use hdajackretask from alsa-tools to reasign my laptop speakers to a certain pin layout. (I need to do this, because those speakers are not used at all by default, in this 4 speaker layout) In order to do this, hdajackretask needs fuser to perform this task. It seems not to be a dependency. Steps to reproduce the behavior: alsa-tools hdajackretask as root this setup, see the tick in the box on the top, then click on apply ! fuser is installed Please run and paste the result.
Note: fuser is part of psmisc and installing it solved this issue. Please add psmisc to alsa-tools as dependency.
Change:
"-DOPENMM_BUILD_SHARED_LIB=ON" ] ++ lib.optionals enablePython [ "-DOPENMM_BUILD_PYTHON_WRAPPERS=ON" <del> ] ++ lib.optionals enableClang [ "-DCMAKE_C_COMPILER=${clang}/bin/clang" "-DCMAKE_CXX_COMPILER=${clang}/bin/clang++" </del> ] ++ lib.optionals enableOpencl [ "-DOPENMM_BUILD_OPENCL_LIB=ON" "-DOPENMM_BUILD_AMOEBA_OPENCL_LIB=ON" "-DOPENMM_BUILD_DRUDE_OPENCL_LIB=ON" "-DOPENMM_BUILD_RPMD_OPENCL_LIB=ON" ] ++ lib.optionals enableCuda [ <del> "-DCUDA_SDK_ROOT_DIR=${cudatoolkit}" </del> <ins> "-DCUDA_SDK_ROOT_DIR=${cudaPackages.cudatoolkit}" </ins> "-DOPENMM_BUILD_AMOEBA_CUDA_LIB=ON" "-DOPENMM_BUILD_CUDA_LIB=ON" "-DOPENMM_BUILD_DRUDE_CUDA_LIB=ON" "-DOPENMM_BUILD_RPMD_CUDA_LIB=ON" <del> "-DCMAKE_LIBRARY_PATH=${cudatoolkit}/lib64/stubs" </del> <ins> "-DCMAKE_LIBRARY_PATH=${cudaPackages.cudatoolkit}/lib64/stubs" </ins> ]; postInstall = lib.strings.optionalString enablePython '' <del> export OPENMM_LIB_PATH=$out/lib export OPENMM_INCLUDE_PATH=$out/include cd python ${python3Packages.python.interpreter} setup.py build ${python3Packages.python.interpreter} setup.py install --prefix=$out </del> <ins> export OPENMM_LIB_PATH=$out/lib export OPENMM_INCLUDE_PATH=$out/include cd python ${python3Packages.python.interpreter} setup.py build ${python3Packages.python.interpreter} setup.py install --prefix=$out ''; postFixup = '' for lib in $out/lib/plugins/*CUDA.so $out/lib/plugins/*Cuda*.so; do addOpenGLRunpath "$lib" done </ins> ''; <del> doCheck = true; </del> <ins> # Couldn't get CUDA to run properly in the sandbox doCheck = !enableCuda && !enableOpencl; </ins> meta = with lib; { description = "Toolkit for molecular simulation using high performance GPU code";

Discussion:
The build fails in the test phase when CUDA is enabled with errors like this: Note that the did not have this problem. Steps to reproduce the behavior:
I've played around a little bit and couldn't get it working. The problems is that the CUDA drivers are available at runtime in but not in the cudatoolkit. I've symlinked and then the library is found but CUDA is not running properly in the sandbox (). I've looked around somewhat and neither Torch, nor Tensorflow, nor Numba, ... have CUDA tests running in their respective expressions. I would assume for exactly this reasons. I suggest to just disable the CUDA tests and have them running for CPU only.
That sounds reasonable.
Change:
nativeBuildInputs = [ pkgconfig python makeWrapper ]; <del> buildInputs = [ webkit pygtk ]; </del> <ins> buildInputs = [ gsettings_desktop_schemas webkit pygtk ]; </ins> }

Discussion:
After : Seems like missing deps for the first bit and some missing config for the other two.
Still no good: The only change I can see is that now starts a window rather than throwing a library error but this window keeps being grey and title bar stating . Perhaps this should be re-opened.
Ouch, GTK changes now requires us to set XDGDATADIRS everywhere… PATH="PATH" XDGDATADIRS=$(nix-build --no-out-link '<nixpkgs' -A gnome3.gsettingsdesktopschemas)/share/gsettings-schemas/gsettings-desktop-schemas-3.10.1/ uzbl-browser should work. Should we add the wrapping into setup-hooks of GTK? Or do we want to avoid such a big rebuild?
What version of nixpkgs are you using? Because that should have been fixed since months. , Michael Raskin :
I have (nearly) HEAD checkout and I did .
Ok it's indeed reproducible with . It works here probably because XDGDATADIRS from the system already has some gsettings etc.. Working on that.
Does the above PR work for you?
! Great stuff, thanks!
Change:
fi ''; <ins> lsColors = optionalString cfg.enableLsColors '' eval "$(${pkgs.coreutils}/bin/dircolors -b)" ''; </ins> bashAliases = concatStringsSep "n" ( mapAttrsFlatten (k: v: "alias ${k}=${escapeShellArg v}") (filterAttrs (k: v: v != null) cfg.shellAliases)

Discussion:
As in the title. At the moment ls colors orphaned symbolic links just as normal symbolic links per default. As symbolic links are really ubiquitous in nix or nixos, is it a good a idea to change that default setting? (From reading the comments in the source, the idea is not following symbolic links, if it isn't really necessary, to avoid the work. Coloring orphaned links different per default, all the effort not to follow symbolic links, wouldn't be used usually.) It's a one line change, I could happily provide a pr (or is it mr) for. In a directory without the files and . ln -s a b LS_COLORS="" ls --color=always
I like this idea. After playing with it a little bit I went ahead and created a PR, since I think it deserves more than a 1-liner. There are bound to be those who want it toggleable.
Change:
runtimeDependencies = [ (lib.getLib udev) libnotify gtk4 ]; <ins> desktopItems = [ (makeDesktopItem rec { name = "Wavebox"; exec = "wavebox"; icon = "wavebox"; desktopName = name; genericName = name; categories = [ "Network" "WebBrowser" ]; }) ]; </ins> installPhase = '' <ins> runHook preInstall </ins> mkdir -p $out/bin $out/opt/wavebox cp -r * $out/opt/wavebox <del> # provide desktop item and icon mkdir -p $out/share/applications $out/share/icons/hicolor/128x128/apps ln -s ${desktopItem}/share/applications/* $out/share/applications </del> <ins> # provide icon for desktop item mkdir -p $out/share/icons/hicolor/128x128/apps </ins> ln -s $out/opt/wavebox/product_logo_128.png $out/share/icons/hicolor/128x128/apps/wavebox.png <ins> runHook postInstall </ins> ''; postFixup = ''

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:
''; installPhase = '' <ins> runHook preInstall </ins> mkdir -p $out cp -r . $out mkdir -p $out/bin/cache/ ln -sf ${dart} $out/bin/cache/dart-sdk <ins> runHook postInstall ''; doInstallCheck = true; installCheckInputs = [ which ]; installCheckPhase = '' runHook preInstallCheck export HOME="$(mktemp -d)" $out/bin/flutter config --android-studio-dir $HOME $out/bin/flutter config --android-sdk $HOME $out/bin/flutter --version | fgrep -q '${version}' runHook postInstallCheck </ins> ''; };

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- 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! --- name: legacyPackages.x86_64-linux.flutter <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2.2.1 desired version: 2.5.1 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Besides updating it we could setup a to easily auto update it
I opened , it's not easy to create the updateScript though, I can try adding later in another PR
Change:
, gst-plugins-good , libunwind , orc <del> , libxslt </del> , cairo , libusb1 , libpulseaudio

Discussion:
I reported some flakey test in freerdp upstream and they hinted that maybe we could be building freerdp better: Filing this so I don't forget to look at it.
I use freerdp all the time, so I have patched things up on my side and will open a proper PR when I have been running with it for a while. FYI, we are in fact already building against ffmpeg.
Change:
hash = "sha256-+TCnVXcmAEpa7MiL0dyeoh2aUfIIO8eze9pEaHgKnME="; }; <ins> # `@electron/fuses` tries to run `codesign` and fails. Disable and use autoSignDarwinBinariesHook instead postPatch = '' sed -i -e 's/resetAdHocDarwinSignature:.*/resetAdHocDarwinSignature: false,/' build/fuses.js ''; </ins> offlineCache = fetchYarnDeps { yarnLock = src + "/yarn.lock"; hash = "sha256-QS0bkDDQq3sn79TQ+pTZsmbmXgMccyLmlPLTsko7eGg=";

Discussion:
Steps to reproduce the behavior: build drawio version 22.1.18 built successfully for me. This failure happens on drawio version 22.0.3. <!-- 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]:
Hello, could you please check if the issue is still occurring in the latest version (see or just run )?
Unfortunately, this fails with the same error: Logs: PS: Thanks for the tip with
Change:
jsduck = callPackage ../development/tools/jsduck { }; <ins> jtc = callPackage ../development/tools/jtc { }; </ins> jumpapp = callPackage ../tools/X11/jumpapp {}; jucipp = callPackage ../applications/editors/jucipp { };

Discussion:
Project description A CLI tool to extract, manipulate and transform source JSON. offers a powerful way to select one or multiple elements from a source JSON and apply various actions on the selected elements at once (wrap selected elements into a new JSON, filter in/out, update elements, insert new elements, remove, copy, move, compare, transform and swap around). Utility ideology: is a stateful processor with own DSL, variables, operations, control flow logic, IO system, etc., etc. is a Unix utility confining its functionality to operation types with its data model only (as per Unix ideology). performs one operation at a time and if successive operations required, then CLI to be daisy-chained over the pipe symbol . Metadata homepage URL: source URL: license: MIT platforms: Unix
I have never contributed a derivation before, but here is my attempt: It works on my machine.
Change:
steamback = python311.pkgs.callPackage ../tools/games/steamback { }; protontricks = python3Packages.callPackage ../tools/package-management/protontricks { <del> inherit winetricks steam-run yad; </del> <ins> steam-run = steam-run-free; inherit winetricks yad; </ins> }; protonup-ng = with python3Packages; toPythonApplication protonup-ng;

Discussion:
Package name: protontricks Latest released version: 1.12.0 <!-- Search your package here: --- Current version on the unstable channel: 1.11.1 Current version on the stable/release channel: 1.11.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. Solves the following bug / problem Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
hash = "sha256-TWaDRJQ695kjoKjWQeAO+uxSZGgQiHoWYIsS+XnYVOQ="; }; <ins> patches = [ (replaceVars ./unvendor-esptool.patch { esptool = lib.getExe esptool; }) ]; </ins> build-system = [ setuptools ]; dependencies = [

Discussion:
I want to use binaries from . I am able to install it and run it but once I get to the part of the program that requires ( ) it fails with this error: But I can see listed as dependency, so I am not sure what is going on. Steps to reproduce the behavior: to your packages and select correct values for your device it downloads the firmware and tries to flash it, it will fail with the error above is recognized as installed dependency Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Digging a bit deeper it seems like the program is generating some python script in my config folder which is executed outside of the context of the package. Any idea how to solve it?
It seems to download its own version of esptool. We should patch the code to use the esptool package from Nixpkgs.
I think this is what's happening: It's literally writing a script to file and then calling it. I thought about changing the shebang to use the Nixpkgs python3 version via , but I don't know how to also include the dependency as part of it.
You could probably replace it with something like this? (taken from ) Not sure if there are other dependencies that are needed or how to patch the code (I am so far only user of NixOS)
OK this are the imports from the file that gets decoded: no other imports in the rest of the file. So it seems like only the needs to be .
I sent a PR here: do you wanna test it out? You can build it locally by pulling down this PR and running this in the root of nixpkgs directory:
Look what I have found: Could this be the whole reason behind this?
Change:
{ pdfstudioviewer = callPackage ./common.nix rec { inherit desktopName pname program year; <del> version = "${year}.2.2"; </del> <ins> version = "${year}.2.4"; </ins> longDescription = '' PDF Studio Viewer is an easy to use, full-featured PDF editing software. This is the free edition. For the standard/pro edition, see the package pdfstudio. ''; src = fetchurl { url = "https://download.qoppa.com/pdfstudioviewer/PDFStudioViewer_linux64.deb"; <del> sha256 = "sha256-cc8YjrMsYZqgmwp5+AA+HsqzjxzFcTT/ga31NQz/OWc="; </del> <ins> sha256 = "sha256-QXNsH1T+ItV3s9r8CnwgRUo1mhVbe8LkEun9gUmlVQg="; </ins> }; <del> jdk = jdk11; broken = true; # Bad hash, probably unstable </del> <ins> jdk = jdk17; </ins> }; pdfstudio2021 = callPackage ./common.nix rec {

Discussion:
The package had been silently marked as broken. From what I can see, the developers now only provide a deb file for the latest version, see The deb link is I guess we should update the link instead of marking the package broken.
Change:
}).run; in '' substituteInPlace $out/bin/XIVLauncher.Core  <del> --replace 'exec' 'exec ${steam-run}/bin/steam-run' </del> <ins> --replace-fail 'exec' 'exec ${steam-run}/bin/steam-run' </ins> '') + '' wrapProgram $out/bin/XIVLauncher.Core --prefix GST_PLUGIN_SYSTEM_PATH_1_0 ":" "$GST_PLUGIN_SYSTEM_PATH_1_0" # the reference to aria2 gets mangled as UTF-16LE and isn't detectable by nix: https://github.com/NixOS/nixpkgs/issues/220065

Discussion:
Package name: xivlauncher Latest released version: Current version on the unstable channel: 1.0.8 Current version on the stable/release channel: 1.0.8 <!-- 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 Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
9 also released yesterday but I don't see a PR or issue for it. Quite likely there will be sever more releases as they work on fixes for the new expansion that dropped today.
9 (which is recent enough to successfully download and play Dawntrail) was merged to master yesterday, and 24.05 today; we're at the mercy of Hydra for that to show up in the release channels. Hopefully that will be fairly soon. I'll get around to 1.1.0 at some point – it fixes repair, but that's it, and I'm currently enjoying the new expansion.
Ah! I didn't see 1.0.9 got in when I search! Enjoy Dawntrail!
Change:
hash = "sha256-vL/CQdYcOP356EyRToviWylP1EBtxmeov6qkhfQNZ2Y="; }; <ins> pythonRelaxDeps = [ "loguru" ]; </ins> postPatch = '' patchShebangs tests ''; nativeBuildInputs = [ poetry-core <ins> pythonRelaxDepsHook </ins> ]; propagatedBuildInputs = [

Discussion:
Package name: loguru Latest released version: 0.7.0 <!-- Search your package here: --- Current version on the unstable channel: 2023-01-20 Current version on the stable/release channel: 2023-01-20 <!-- 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.