jiebi/CodeConvo huggingface dataset:
Change:
nativeBuildInputs = [ cmake perl pkgconfig ]; <del> buildInputs = [ gtk3 vte pcre glib ]; </del> <ins> buildInputs = [ makeWrapper gtk3 vte pcre glib ]; # Wrapper sets path to gsettings-schemata so sakura knows where to find colorchooser, fontchooser ... postInstall = "wrapProgram $out/bin/sakura --suffix XDG_DATA_DIRS : ${gtk3}/share/gsettings-schemas/${gtk3.name}/"; </ins> meta = with stdenv.lib; { description = "A terminal emulator based on GTK and VTE";

Discussion:
sakura terminal emulator terminates when trying to change color by context menu with following error: GLib-GIO-ERROR *: No GSettings schemas are installed on the system [1] 9932 trace trap sakura run sakura, right click to popup context menu : options -select colors -(click on color field to open color chooser) Here is a thread that discusses the issue. it seems that the color-chooser gui description is missing that is needed by sakura. should include gsettings as runtime dependency. actually it has gtk3 package as dependency which provides those schemata, however it obvious doesn't look in the right path. this kind of error got fixed for System: (17.03pre98008. (Gorilla)) Nix version: (nix-env (Nix) 1.11.4) Nixpkgs version: ("17.03pre98008.")
Change:
"name": "element-desktop", "productName": "Element", "main": "lib/electron-main.js", <del> "version": "1.10.4", </del> <ins> "version": "1.10.6", </ins> "description": "A feature-rich client for Matrix.org", "author": "Element", "repository": {

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 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: element-web <!-- The current version can be found easily with the same process as 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: 1.10.4 desired version: 1.10.6 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Myself i am waiting for an , ... please keep an eye on the release.
Change:
flycheck-rtags = fix-rtags super.flycheck-rtags; <del> gnuplot = super.gnuplot.overrideAttrs (old: { nativeBuildInputs = (old.nativeBuildInputs or [ ]) ++ [ pkgs.autoreconfHook ]; }); </del> pdf-tools = super.pdf-tools.overrideAttrs (old: { nativeBuildInputs = [ external.pkgconfig ]; buildInputs = with external; old.buildInputs ++ [ autoconf automake libpng zlib poppler ];

Discussion:
Describe the bug A clear and concise description of what the bug is. According this , this package is built by only.
Thanks for reporting this, I just got the error myself.
Change:
dontDropIconThemeCache = true; <del> postPatch = '' patchShebangs meson/post_install.py ''; </del> <ins> # These fixup steps are slow and unnecessary for this package dontPatchELF = true; dontRewriteSymlinks = true; </ins> postInstall = '' # The cache for Paper-Mono-Dark is missing gtk-update-icon-cache "$out"/share/icons/Paper-Mono-Dark; <ins> # replace duplicate files with symlinks jdupes -l -r $out/share/icons </ins> ''; meta = with lib; {

Discussion:
paper-icon-theme last saw an official upstream release in 2018, but there are some fixes since then which are important for rendering of symbolic icons in e.g. rhythmbox and nemo (see e.g. snwh/paper-icon-theme). it would be useful if nixpkgs could use the latest upstream commit rather than the last release. name: paper-icon-theme current version: 2018-06-24 desired version: unstable-2020-03-12 <!-- 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.
Change:
strictDeps = true; <ins> # Make sure that the build timestamp is not included in the archive postFixup = '' strip-nondeterminism --type zip $out/share/fs-uae/fs-uae.dat ''; </ins> meta = { homepage = "https://fs-uae.net"; description = "An accurate, customizable Amiga Emulator";

Discussion:
Building this package multiple times does not yield bit-by-bit identical results, complicating the detection of Continuous Integration (CI) breaches. For more information on this issue, visit . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. This step will build the package. Specific arguments are passed to the command to keep the build artifacts so we can compare them in case of differences. Execute the following command: Or using the new command line style: If the previous command completes successfully, no differences were found and there's nothing to do, builds are reproducible. If it terminates with the error message error: derivation '&lt;X' may not be deterministic: output '&lt;Y' differs from '&lt;Z'diffoscope to investigate the discrepancies between the two build outputs. You may need to add the option to ignore files and directories metadata (e.g. timestamp) differences. To examine the build log, use: Or with the new command line style: After checking out and building , output of was: So it seems to just be some timestamps in the archive . ᵗʰᶦˢ ᵗᵉᵐᵖˡᵃᵗᵉ ᶦˢ ʷᵉᶦʳᵈ Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Recently, I learned, that there's a tool called , which can help get rid of timestamps in archives. I'll try to come up with a fix using that.
Change:
<ins> { lib, buildPythonPackage, fetchPypi, setuptools, pythonOlder, z3-solver, pythonRelaxDepsHook, }: buildPythonPackage rec { pname = "model-checker"; version = "0.3.13"; pyproject = true; disabled = pythonOlder "3.8"; src = fetchPypi { pname = "model_checker"; inherit version; hash = "sha256-3LVes+orRl8tNhhbUUDa1VM/tFf8Y1pAzKknmrjA6e4="; }; # z3 does not provide a dist-info, so python-runtime-deps-check will fail pythonRemoveDeps = [ "z3-solver" ]; build-system = [ setuptools ]; nativeBuildInputs = [ pythonRelaxDepsHook ]; dependencies = [ z3-solver ]; # Tests have multiple issues, ImportError, TypeError, etc. # Check with the next release > 0.3.13 doCheck = false; pythonImportsCheck = [ "model_checker" ]; meta = with lib; { description = "A hyperintensional theorem prover for counterfactual conditionals and modal operators"; homepage = "https://pypi.org/project/model-checker/"; license = licenses.mit; maintainers = with maintainers; [ fab ]; }; } </ins>

Discussion:
Project description A hyperintensional theorem prover for counterfactual conditionals and modal operators. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
- [microsocks](https://github.com/rofl0r/microsocks), a tiny, portable SOCKS5 server with very moderate resource usage. Available as [services.microsocks]($opt-services-microsocks.enable). <ins> - [inadyn](https://github.com/troglobit/inadyn), a Dynamic DNS client with built-in support for multiple providers. Available as [services.inadyn](#opt-services.inadyn.enable). </ins> - [Clevis](https://github.com/latchset/clevis), a pluggable framework for automated decryption, used to unlock encrypted devices in initrd. Available as [boot.initrd.clevis.enable](#opt-boot.initrd.clevis.enable). - [fritz-exporter](https://github.com/pdreker/fritz_exporter), a Prometheus exporter for extracting metrics from [FRITZ!](https://avm.de/produkte/) devices. Available as [services.prometheus.exporters.fritz](#opt-services.prometheus.exporters.fritz.enable).

Discussion:
ddclient was removed in , with inadyn being the closest suggested replacement. inadyn is packaged in Nixpkgs, but does not have a NixOS module. An inadyn NixOS module would be useful as a replacement.
The first step is fixing inadyn itself, since it currently won't start due to a wrongly configured , see .
We will also need to decide if it's better to run as a systemd service, timer, or give the user the option to choose. I lean towards timer.
AFAICS inadyn does not contain additional logic to detect IP address changes. Because of this I would also lean towards the timer functionality.
I think it does. Looking at , inadyn will only update the ip if changed every seconds and always update it every seconds. I'm not clear on how those options behave in oneshot mode.
Well, so far I called ddclient with cron, since the machine running will not easil see altered public IP change. I tried to use inadyn but can't get it to work with /
I've had some time to poke around this a bit more, and it seems like inadyn cannot read credentials from the environment or a file separate to the config, so all your DDNS credentials will end up world-readable in the store.
I've made a pretty barebones module for my personal config here It runs inadyn in oneshot mode using a timer, and is configured entirely by specufying a .
Submitted a full NixOS module as , I would appreciate if inadyn users could test it :slightlysmilingface:.
Add a small example for how to use it?
Sure, here's a config to use namecheap:
Change:
githubId = 124545; name = "Anthony Cowley"; }; <ins> adamlwgriffiths = { email = "adam.lw.griffiths@gmail.com"; github = "adamlwgriffiths"; githubId = 1239156; name = "Adam Griffiths"; }; </ins> adamt = { email = "mail@adamtulinius.dk"; github = "adamtulinius";

Discussion:
Project description raylib is a simple and easy-to-use library to enjoy videogames programming. raylib is highly inspired by Borland BGI graphics lib and by XNA framework and it's specially well suited for prototyping, tooling, graphical applications, embedded systems and education. Metadata homepage URL: source URL: license: zlib platforms: unix, linux, darwin, android, webasm
I've got a PR I'm preparing which adds this.
Change:
nixnote2 = libsForQt5.callPackage ../applications/misc/nixnote2 { }; <del> nodejs = hiPrio nodejs-8_x; </del> <ins> nodejs = hiPrio nodejs-10_x; </ins> <del> nodejs-slim = nodejs-slim-8_x; </del> <ins> nodejs-slim = nodejs-slim-10_x; </ins> nodejs-8_x = callPackage ../development/web/nodejs/v8.nix {}; nodejs-slim-8_x = callPackage ../development/web/nodejs/v8.nix { enableNpm = false; };

Discussion:
The top-level and derivations refer to different versions of NodeJS: refers to v8x while refers to v10x. This is quite unexpected, resulting in different versions of being installed in the store, and any build steps executed under a different version of node than the version that's used by any app using . Expected: the same nodejs interpreter should be referenced in both cases. The two different declarations can be found at Ideally this is done like / , where merely refers to . system: host os: multi-user?: sandbox: version: channels(llunesu): nixpkgs:
Change:
-    remove cpufreqctl.auto-cpufreq script -    """ -    # detect if running on a SNAP <del> -    if os.getenv('PKG_MARKER') == "SNAP": </del> <ins> -    if os.getenv("PKG_MARKER") == "SNAP": </ins> -        pass -    else: -        if os.path.isfile("/usr/bin/cpufreqctl.auto-cpufreq"):

Discussion:
Describe the bug I believe the auto-cpufreq daemon should start on boot if enabled. To Reproduce auto-cpufreq daemon: . the system. . auto-cpufreq as dead/inactive. Expected behavior auto-cpufreq service should be started on boot. Additional context I was using the unstable service in 20.09 and it worked as expected. In 21.05 stable, the service starts dead/inactive and my system is very slow. I manually start the service and I'm back to the NixOS I know and love. I was able to fix this by adding the following to my configuration: Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(pnelson): channels(root): nixpkgs: Maintainer information:
Sorry for being late, should fix this.
I have the exact same issue now, on 23.11.
Same here, also facing this problem on 23.11...
Thought this might be caused due to some false overwrites in the module config, so I decided to try out rewriting the systemd service. Doesn't work either...
For others who might still be hitting this, I thought I was too. When checking the logs I saw that power-profiles-daemon was starting up, causing auto-cpufreq to shut down. I fixed this by adding: From looking at this code, and be kind with me here since I'm a nix beginner, it is .  I think the best action would be to add an assertion to give users a prompt like with tlp. If this looks correct I can open a PR for it
Change:
gst-plugins-bad gst-plugins-base gst-plugins-good <del> ]); </del> <ins> ]) ++ lib.optionals withOmemo [ qca-qt5 libomemo-c ]; </ins> cmakeFlags = [ "-DBUILD_EXAMPLES=false" "-DBUILD_TESTS=false" ] ++ lib.optionals withGstreamer [ "-DWITH_GSTREAMER=ON" <ins> ] ++ lib.optionals withOmemo [ "-DBUILD_OMEMO=ON" </ins> ]; meta = with lib; {

Discussion:
Steps to reproduce the behavior: kaidan <!-- 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]:
Thanks for notifying me!
Change:
checkConfigError 'infinite recursion encountered' config.foo ./freeform-attrsOf.nix ./freeform-unstr-dep-str.nix checkConfigError 'The option .* is used but not defined' config.foo ./freeform-lazyAttrsOf.nix ./freeform-unstr-dep-str.nix checkConfigOutput '^"24"$' config.foo ./freeform-lazyAttrsOf.nix ./freeform-unstr-dep-str.nix ./define-value-string.nix <ins> # submodules in freeformTypes should have their locations annotated checkConfigOutput '/freeform-submodules.nix"$' config.fooDeclarations.0 ./freeform-submodules.nix # freeformTypes can get merged using `types.type`, including submodules checkConfigOutput '^10$' config.free.xxx.foo ./freeform-submodules.nix checkConfigOutput '^10$' config.free.yyy.bar ./freeform-submodules.nix </ins> ## types.anything # Check that attribute sets are merged recursively

Discussion:
See the : the options aren't declared by any file (it's actually , but that's stripped at some point). I think this is most likely because they are declared inside a : but I don't know the module system well enough to troubleshoot this. This was causing the unstable channel import to because of an which should be fixed by This is an issue of the module system, so pinging
fixes this, thanks for the report!
Change:
{ stdenv, lib, fetchurl, pkgconfig, removeReferencesTo , libevent, readline, net-snmp, openssl <ins> , fetchpatch </ins> }: stdenv.mkDerivation rec {

Discussion:
, CVSSv3=7.5 (nixos-20.09) Scanned versions: nixos-20.09: . Cc
Is it still worth fixing now that 21.05 has been released?
Support for the last release should be provided at least for 2 months after release. Not all users are able to transition to the new release immediately. So if there is a patch or a point release available, an update for 20.09 would be appreciated. What we usually do not do for old releases is to introduce breaking changes or major updates.
Change:
-DEFI_FUNCTION_WRAPPER" CPPFLAGS_save="$CPPFLAGS" CPPFLAGS="$CPPFLAGS $EFI_CPPFLAGS" <del> @@ -90,5 +91,5 @@ </del> <ins> @@ -90,5 +91,5 @@ AC_SUBST(EFI_ARCH, $EFI_ARCH) </ins> AC_SUBST(CRTPATH, $CRTPATH) AC_CONFIG_FILES([Makefile src/Makefile lib/ccan/Makefile]

Discussion:
The systemd-boot image built in nixpkgs has gaps in the section table. This leads to signature verification failure with some UEFI Secure Boot implementations (e.g. Dell XPS 13 9310) Using NixOS 22.05 @ Using some old version from NixOS 21.11 that I still have in the store: N/A Allegedly something like this was fixed in systemd upstream and the commit is present in v250.4 but for some reason it still appears and Secure Boot fails. <!-- 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. system: host os: multi-user?: sandbox: version: nixpkgs:
Relevant:
This commit might be the culprit: I will try confirm this, but since it requires rebuilding systemd, it'll take a while.
It's more likely a problem of sbsigntools:
Does your hardware still correctly validate the signature with this patch applied?
Yes, signature verification works with this patch (and only with this patch). Hardware is Dell XPS 13 9310. See also
Change:
<ins> { fetchFromGitHub, python3Packages, lib, }: python3Packages.buildPythonApplication rec { pname = "zotify"; version = "0.6.13"; pyproject = true; src = fetchFromGitHub { owner = "zotify-dev"; repo = "zotify"; # repository has no version tags # https://github.com/zotify-dev/zotify/issues/124 rev = "5da27d32a1f522e80a3129c61f939b1934a0824a"; hash = "sha256-KA+Q4sk+riaFTybRQ3aO5lgPg4ECZE6G+By+x2uP/VM="; }; build-system = [ python3Packages.setuptools ]; nativeBuildInputs = [ python3Packages.pythonRelaxDepsHook ]; pythonRelaxDeps = [ "protobuf" ]; dependencies = with python3Packages; [ ffmpy music-tag pillow tabulate tqdm librespot pwinput protobuf ]; pythonImportsCheck = [ "zotify" ]; meta = { description = "Fast and customizable music and podcast downloader"; homepage = "https://github.com/zotify-dev/zotify"; license = lib.licenses.zlib; mainProgram = "zotify"; maintainers = with lib.maintainers; [ bwkam ]; }; } </ins>

Discussion:
Project description A fast and customizable music and podcast downloader. Metadata homepage URL: source URL: license: zlib platforms: linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
{ stdenv, lib, lndir, makeWrapper , fetchFromGitHub, cmake , libusb, pkgconfig <del> , python, swig2, numpy, ncurses </del> <ins> , usePython ? false , python, ncurses, swig2 </ins> , extraPackages ? [] } :

Discussion:
The soapysdr package contains a Python binding, but it is not possible to use it normally (e.g. via ) because it is not registered as a Python package in nixpkgs. I am not sure what is the proper way of handling this case, since soapysdr is both a regular library and a Python package, and nixpkgs makes a distinction between the two. A workaround is to add. Cc
See the section "15.17.2.2.4. toPythonModule function" in the Nixpkgs manual.
Change:
esac done <del> if $needsTarget; then </del> <ins> if $needsTarget && [[ $0 != *cpp ]]; then </ins> extraBefore+=(-target @defaultTarget@ @machineFlags@) fi

Discussion:
Steps to reproduce the behavior: Discovered via the Nixpkgs LLVM Workspace project. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --No maintainers, CC last person who touched Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
inherit version; src = fetchurl { <del> url = "https://developer.download.nvidia.com/compute/cutensor/${mostOfVersion}/local_installers/libcutensor-${stdenv.hostPlatform.parsed.kernel.name}-${stdenv.hostPlatform.parsed.cpu.name}-${version}.tar.gz"; </del> <ins> url = if lib.versionOlder mostOfVersion "1.3.3" then "https://developer.download.nvidia.com/compute/cutensor/${mostOfVersion}/local_installers/libcutensor-${platform}-${version}.tar.gz" else "https://developer.download.nvidia.com/compute/cutensor/redist/libcutensor/${platform}/libcutensor-${platform}-${version}-archive.tar.xz"; </ins> inherit hash; };

Discussion:
From what I could tell this was only mentioned in some comment of a closed PR. This is blocking me from wrapping up a flake for Invoke AI (a Stable Diffusion webui). Any help/advice would be appreciated. This was described on Discourse by :
What commit of nixpkgs are you using? I might have some cycles this weekend to spend on this.
Looks like the cause is an outdated version of cutensor. It appears cupy is the only dependent of that so hopefully an upgrade is simple. I am working on a patch now.
Change:
) config.boot.initrd.secrets) } <del> (cd "$tmp" && find . | cpio -H newc -o) | gzip >>"$1" </del> <ins> (cd "$tmp" && find . -print0 | sort -z | cpio -o -H newc -R +0:+0 --reproducible --null) |  ${config.boot.initrd.compressor} >> "$1" </ins> ''; in

Discussion:
Describe the bug It assumes the compressor is always gzip. To Reproduce Which results in a kernel panic, unable to mount root fs error. Expected behavior No kernel panic, it boots normally. Additional context I found this when moving to from removal of in . Digging into the files in I noticed that the file suffixed with was gzipped. Decompressing the () file and recompressing it using allowed me to then boot back into my machine. Notify maintainers According to : People who might have some related interest: Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(sna): nixpkgs:
Gzip should be replaced by in this line.
It probably would be a good idea to handle the non-determinism introduced by the host filesystem when using find. Seems to do that with piped to but it also has a lot more arguments to as well.
Do you mind open a pull request for this?
See
have you had a chance to see the pull request mentioned above? It works for me and I have been using it regularly for awhile now.