jiebi/CodeConvo huggingface dataset:
Change:
nodes.machine = { services.keyd = { enable = true; <del> inherit settings; </del> <ins> keyboards.default = { inherit settings; }; </ins> }; };

Discussion:
Currently options of keyd service () allow for creating single configuration file (). I need to apply different configs to different keyboards (which is possible by creating multiple conf files in ). Could NixOS keyd module expose suitable option(s) for this?
I'll look into it. Can you provide an example of what these files should look like? Is it the same as "" but with a different "id" section?
Thanks very much! Exactly. The format of all conf files is the same. Each file specifies different to match different keyboards.
Ok, I will think how I can do it nicely soon
this patch is ready. If you are using unstable nixos, you can update the packages with with a flake switch (do you use flakes?). Can you confirm that the multi-file configuration is working now?
Hello, I am using keyd and NixOS unstable. I updated my to account for the changes related to this issue. I then ran and my built-in laptop keyboard, which I use keyd with, stopped responding to input. I plugged in an external keyboard, which worked fine, and had a look at the systemd logs for keyd.service and the new configuration files. I did not see anything unusual. I then ran and my keyboard started working again. I can consistently reproduce this by rebooting and re-running the above command. If anyone else has this issue and doesn't have an external keyboard handy, I suggest trying the following steps, as these also allowed me to update without disabling my keyboard: out the portion of your NixOS config. NixOS update command e.g. portion and run again As for the new configuration: I have not tested the multi-file configuration properly as I only use it for my laptop keyboard but the new file layout looks correct .
Hi unfortunately I also have this problem from time to time when the home manager restarts many services at once. I have an easier workaround - just press . The keyd docs say this command will stop keyd, but for me it restarts it and everything works like a charm. Also try using or instead of and you should probably run into this situation less often. I think because when you create a lock file from scratch, all services will be restarted, but with the only some of them. I'm not sure though, just a guess.
Change:
<ins> diff --git a/configure b/configure index e3e21e8..3d947b6 100755 --- a/configure +++ b/configure @@ -2859,6 +2859,7 @@ fi; echo "building the bundled hdf5 library..."; cd ${BASEPBNAME}; +sed -i 's#/bin/mv#mv#' configure ./configure  --with-pic --enable-shared=no CXX="${CXX}" CXXFLAGS="${CXXFLAGS}" CC="${CC}" CFLAGS="${CFLAGS}" F77="${F77}" $MAKE lib cd ../../ </ins>

Discussion:
Installation of fails using both my default channel and current branch of (18.03-beta--g8cf4a4725c1). <details<summaryFull output</summary<p</p</detailsI was able to track the main cause of the problem down to this line: A file that is dynamically created during installation contains a hard coded instead of plain . This causes the missing headers and subsequently the failing compilation. I created a patch for this and will submit a pull request shortly. system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs:
Change:
./services/misc/parsoid.nix ./services/misc/plex.nix ./services/misc/plikd.nix <ins> ./services/misc/podgrab.nix </ins> ./services/misc/tautulli.nix ./services/misc/pinnwand.nix ./services/misc/pykms.nix

Discussion:
Project description Podgrab is a is a self-hosted podcast manager which automatically downloads latest podcast episodes. It is a light-weight application built using GO. It works best if you already know which podcasts you want to monitor. However there is a podcast search system powered by iTunes built into Podgrab Metadata homepage URL: source URL: license: gpl3 (I think, see about a typo) platforms: unix, I think, it's a Go package
If I have some time this week-end, I might tackle this issue myself. The repo has and files so it should be pretty easy for a first contribution :-)
So I'm having issues with the package's tests, I have opened an upstream issue to discuss it.
Change:
kovirobi ]; platforms = platforms.unix; <ins> broken = stdenv.isDarwin; </ins> }; } # TODO: investigate the mouse chording support patch

Discussion:
The new scheme introduced in confuses the script. latest plan9port from unstable as of writing to use from within an environment spawned by gets moved from the front of to the back Here is a session using unmodified p9p: ylh ~ PATH ylh ~ $ 9 zsh ylh ~ PATH /nix/store/d4iwcgqwgk8whxjxgmhh20ykni7flkb2-plan9port-0.pre+date=2021-10- ylh ~ $ u zsh ylh ~ PATH /nix/store/d4iwcgqwgk8whxjxgmhh20ykni7flkb2-plan9port-0.pre+date=2021-10- After applying the following overlay: self: { lib, plan9port, ... }: let lastby = sep: x: (lib.splitString sep x); in { plan9port = plan9port.overrideAttrs (old pname, ... }: { version = lastby "=" (lastby "+" old.version); name = "{version}"; }); } the desired result is achieved: ylh ~ PATH ylh ~ $ 9 zsh ylh ~ PATH /nix/store/zh1iaayjg7baqvgh1g645k4wzxjrmfzx-plan9port-2021-10- ylh ~ $ u zsh ylh ~ PATH Amusingly, is left unaffected; the tool calls out to , which, in a environment (why else would you be calling ), is p9p sed, which interprets as a metacharacter without the need for . In any case, RFC 0107 clearly needs work, and this should hopefully demonstrate why enacting it (self-merging, no less) pre-approval is somewhat irresponsible. system: host os: multi-user?: sandbox: version: channels(root): channels(ylh): nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs Maintainer information:
This obsession with arbitrary versioning formatting standards is getting annoying.
Change:
python3Full = python3.override { self = python3Full; pythonAttr = "python3Full"; <del> bluezSupport = true; </del> <ins> bluezSupport = lib.meta.availableOn stdenv.hostPlatform bluez; </ins> x11Support = true; }; python38Full = python38.override { self = python38Full; pythonAttr = "python38Full"; <del> bluezSupport = true; </del> <ins> bluezSupport = lib.meta.availableOn stdenv.hostPlatform bluez; </ins> x11Support = true; }; python39Full = python39.override { self = python39Full; pythonAttr = "python39Full"; <del> bluezSupport = true; </del> <ins> bluezSupport = lib.meta.availableOn stdenv.hostPlatform bluez; </ins> x11Support = true; }; python310Full = python310.override { self = python310Full; pythonAttr = "python310Full"; <del> bluezSupport = true; </del> <ins> bluezSupport = lib.meta.availableOn stdenv.hostPlatform bluez; </ins> x11Support = true; }; python311Full = python311.override { self = python311Full; pythonAttr = "python311Full"; <del> bluezSupport = true; </del> <ins> bluezSupport = lib.meta.availableOn stdenv.hostPlatform bluez; </ins> x11Support = true; }; python312Full = python312.override { self = python312Full; pythonAttr = "python312Full"; <del> bluezSupport = true; </del> <ins> bluezSupport = lib.meta.availableOn stdenv.hostPlatform bluez; </ins> x11Support = true; }; python313Full = python313.override { self = python313Full; pythonAttr = "python313Full"; <del> bluezSupport = true; </del> <ins> bluezSupport = lib.meta.availableOn stdenv.hostPlatform bluez; </ins> x11Support = true; };

Discussion:
Can't install or run a shell with package on macOS. Same with and . Steps to reproduce the behavior: macOS run an error No error and a shell with python 3.12. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Assertion was introduced in , ping All the derivations override , regardless of platform. For example:
Has always been that way, only now the assertion is more verbose. There is no point in using the variant, since it gives you nothing that is supported on darwin anyway.
Ah right, fair. The cpython derivation has code for handling Darwin + X11 support, so I assume that combination could work at least. So maybe doing this would be fine?
Change:
<del> { stdenv, fetchurl, cmake, gl2ps, gsl, libX11, libXpm, libXft, libXext , libGLU, libGL, libxml2, lz4, lzma, pcre, pkgconfig, python, xxHash, zlib </del> <ins> { stdenv, fetchurl, makeWrapper, cmake, gl2ps, gsl, libX11, libXpm, libXft , libXext, libGLU, libGL, libxml2, lz4, lzma, pcre, pkgconfig, python, xxHash , zlib </ins> , Cocoa, OpenGL, noSplash ? false }: stdenv.mkDerivation rec {

Discussion:
Describe the bug I think this is another problem: After installing root (I'm using ), when I launch , I got the following error: I managed to find an improper workaround: First I located the installation directory of : Then I manually specify the location of the Python library that comes with : Now can launch properly. To Reproduce Steps to reproduce the behavior: in in terminal Expected behavior It should run without problem. Metadata Please run and paste the result. Maintainer information:
It is worth noting that if I manually source the supplied , can run without problem, and I can import in a Python 3 interpreter. I think a (not the) reasonable approach would be: globally usable, since it really is an utility the Python moduel as-is (not available unless explicitly sourced by user) Arch linux takes the approach above, and they copy the module to global Python library path. But I'm not sure on how to do this sanely in nix. For example, in my overlay, I have Python defined as: But I don't know how to include ---a Python library provided by package---globally.
Alternatively, I can just source in my login shell. Which is actually not too bad.
Yes, you are right about needing to source This is done automatically in our for , so everything works when is used in other nix builds and in nix-shell: nix-env does not run setupHook, so you would need to source it yourself, the way ROOT was intended to be used. In nixpkgs we usually make sure that all of the binaries are wrapped or patched to be able to find their libraries in any environment, so this is considered to be a bug.
Change:
wxGTK = wxGTK30; }; <del> railcar = callPackage ../applications/virtualization/railcar {}; </del> raiseorlaunch = callPackage ../applications/misc/raiseorlaunch {}; rapid-photo-downloader = libsForQt5.callPackage ../applications/graphics/rapid-photo-downloader { };

Discussion:
I was curious about railcar and noted that it's marked as so I decided to give it a try. The first attempt failed at an error over a missing in libseccomp: I gather this is Linux-only and could find at least one other PR that fixed a macOS build of a different project by just removing it as a buildInput () and the cargo build fell over on some issues with caps: Other notes: I looked to see if Hydra was building this for darwin and don't see any builds. I guess hydra is smart enough not to bother with darwin given the libseccomp input. I noticed that ofborg didn't bother with building darwin on the original PR, either. Also, I noticed that oracle has archived the railcar repo. I only see at the moment. They've done some work on the CI earlier this year, at least, which seems to be a good signal? Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(abathur): nixpkgs:
I marked this as stale due to inactivity. &rarr;
Change:
in majorIs == "9" || majorIs == "10" || majorIs == "11"; let <del> version = "2.5.4"; </del> <ins> version = "2.6.2"; </ins> # We define a specific set of CUDA compute capabilities here, # because CUDA 11 does not support compute capability 3.0. Also,

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . python3Packages.pytorchWithCuda maintainers cc: magma maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
This looks like another gcc11 failure. could you take a look?
Sure thing
Going to attempt to bump from 2.5.4 (2020) to 2.6.2 (2022)
Change:
then value else { executable = value; profile = null; extraArgs = []; }; args = lib.escapeShellArgs ( <del> (optional (opts.profile != null) "--profile=${toString opts.profile}") ++ opts.extraArgs </del> <ins> opts.extraArgs ++ (optional (opts.profile != null) "--profile=${toString opts.profile}") </ins> ); in ''

Discussion:
I would like to use the following option in in : When running the command I get following error: This is because are appended after the option. It would be better if we switch the order of these. Steps to reproduce the behavior: following configuration to execute the command will fail with following error: The program should be exectued with accepting all
Change:
libclxclient = callPackage ../development/libraries/libclxclient  { }; <ins> libco-canonical = callPackage ../development/libraries/libco-canonical { }; </ins> libconfuse = callPackage ../development/libraries/libconfuse { }; libcangjie = callPackage ../development/libraries/libcangjie { };

Discussion:
Describe the bug I'm not able to start any (freshly created) container in lxd. To Reproduce Steps to reproduce the behavior: Expected behavior Container starts without issues. Additional context Log gathered via Regarding the not enough space, I'm quiet sure that the report is wrong: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs: Maintainer information:
Maybe updating helps? I started working on a PR, though I depend on a which fails to build.
tested with merged on top inside a nogui VM
Wrong commit?
yip
Change:
, ghostscript , aalib , shared-mime-info <del> , python2Packages </del> <ins> , python2 </ins> , libexif , gettext <ins> , makeWrapper </ins> , xorg , glib-networking , libmypaint

Discussion:
Describe the bug GIMP uses Python and GTK+ for e.g. plugins. But GIMP in the NixOS-GIMP-package cannot find the Python-gtk-module: GIMP itself starts, but e.g. some plugins cannot be used, e.g. . When selecting this plugin, nothing happens, and the following error is shown in the console (again): To Reproduce Steps to reproduce the behavior: GIMP. GIMP. at the error-messages. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Can confirm this still doesn't work. Of note is that installing will allow when used from the REPL, but GIMP will still not recognize it. Tagging since they are tagged as the maintainer.

I see the following warnings when running gimp: Not sure if they are critical or not. I do have problems with one Python plugin, not sure if this could be related. Run gimp from the terminal. I'm running it from i3+none desktop environment, if that matters. Please run and paste the results.
I can see the warning too. This is what the file looks like on Arch: nothing special compared to ours: The file exists and is executable Not really sure what is wrong. Also the Python scripts seem to work, at least does.
For me, resynthesizer runs but it doesn't produce correct results:
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 .
Still important to me. This is the current console output:
I have found this issue can be fixed by installing the python package by yourself (which is weird: it looks like GIMP may be trying to use the command from your ). I have it in my systemPackages and I got past that stage. However, is still blocking the usage of some plugins.
Spent some time in and it looks like the extension mapping from file only searches in path, not in the mapping described on previous lines and registered in : : The extension is so some other mechanism than extension matching must be involved – perhaps shebangs are applied. We will still want to hardcode the path to ensure purity.
Change:
with ( { <ins> "3.11" = { minorVersion = "2"; sha256 = "0j2jpx94lnqx5w59i9xihl56hf6ghk04438rqhh7lk1bryxj5g2y"; }; </ins> "3.10" = { minorVersion = "2"; sha256 = "80d0faad4ab56de07aa21a7fc692c88c4ce6156d42b0579c6962004a70a3218b";

Discussion:
cmake in nixpkgs is 3.10.2. This is over 2 months old. The current version is 3.11.2. This is a problem for me as I'm trying to use cmake to build something that requires 3.11.0 or later. /cc
was merged a day ago, but isn't showing up on nixpkgs-unstable yet. It looks like it was merged into staging rather than trunk. How long does it normally take for package updates like this to make it to trunk?
I merged it into rather than because it causes ~1,000 rebuilds, so if it was merged into it would block the unstable channel from updating. After rebuilds, I will merge it into and then after a small rebuild, it will appear automatically in the unstable channel. This process could take a week if there are many other changes queued in , or a few days otherwise.
Thanks for the explanation!
Change:
<ins> { lib , stdenv , fetchFromGitHub , cmake , SDL2 , SDL2_mixer , SDL2_image , fluidsynth , soundfont-fluid , portmidi , dumb , libvorbis , libmad , libGLU , libzip }: stdenv.mkDerivation rec { pname = "dsda-doom"; version = "0.27.5"; src = fetchFromGitHub { owner = "kraflab"; repo = "dsda-doom"; rev = "v${version}"; hash = "sha256-+rvRj6RbJ/RaKmlDZdB2oBm/U6SuHNxye8TdpEOZwQw="; }; sourceRoot = "${src.name}/prboom2"; nativeBuildInputs = [ cmake ]; buildInputs = [ SDL2 SDL2_mixer SDL2_image fluidsynth portmidi dumb libvorbis libmad libGLU libzip ]; # Fixes impure path to soundfont prePatch = '' substituteInPlace src/m_misc.c --replace  "/usr/share/sounds/sf3/default-GM.sf3"  "${soundfont-fluid}/share/soundfonts/FluidR3_GM2-2.sf2" ''; meta = with lib; { homepage = "https://github.com/kraflab/dsda-doom"; description = "An advanced Doom source port with a focus on speedrunning, successor of PrBoom+"; license = licenses.gpl2Plus; platforms = platforms.linux; maintainers = [ maintainers.Gliczy ]; }; } </ins>

Discussion:
Project description Doom source port. Fork of prboom+ with extra tooling for demo recording and playback, with a focus on speedrunning. Metadata homepage URL: source URL: license: gpl2 platforms: linux
Change:
"gateway": { "update-channel": "Gateway RELEASE", "url-template": "https://download.jetbrains.com/idea/gateway/JetBrainsGateway-{version}.dmg", <del> "version": "2023.1.1", "sha256": "e580bf5bd657b721677fec0250ce582adb1cf92daa1ac065b56fc2d8148fac97", "url": "https://download.jetbrains.com/idea/gateway/JetBrainsGateway-2023.1.1.dmg", "build_number": "231.8770.69" </del> <ins> "version": "2023.1.2", "sha256": "320beadb9eb50f48eb431bcd2c88ec1c2e7e0ef2f1f2414aa3842de5930d79ff", "url": "https://download.jetbrains.com/idea/gateway/JetBrainsGateway-2023.1.2.dmg", "build_number": "231.9011.34" </ins> }, "goland": { "update-channel": "GoLand RELEASE",

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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! --- There is , which mentions that the "script still has issues with Gateway". A manual download of the updated Gateway does work. Updating this myself is a bit over the top of my head. There is an script involved, etc. If you prefer, please fill me in on how the pipeline works! 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.
Change:
<ins> #!/usr/bin/env nix-shell #!nix-shell -I nixpkgs=./. -i bash -p nix-update #shellcheck shell=bash set -o errexit -o nounset -o pipefail package=nexusmods-app nix-update "$package" "$(nix-build --attr "$package".fetch-deps --no-out-link)" </ins>

Discussion:
Project description From the : Metadata homepage URL: source URL: license: gpl3 platforms: linux (the says tests run on OSX, but I can't find the build instructions) Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
wget = callPackage ../development/python-modules/wget { }; runway-python = callPackage ../development/python-modules/runway-python { }; <ins> pyprof2calltree = callPackage ../development/python-modules/pyprof2calltree { }; </ins> }); in fix' (extends overrides packages)

Discussion:
Describe the bug Not really a "bug", but pyprof2calltree is hard-coded to and fails for Python 3 profile results with This can be fixed by changing the expression to . Not sure what to do here, move the program to since Python 2 will be EOL anyway?
Pinging the maintainer,
As can also be used as a library it would make sense to move it into and let the default attribute be Python 3.
My PR has been merged, does this solve the issue for you?
Change:
youtubeDL = throw "'youtubeDL' has been renamed to/replaced by 'youtube-dl'"; # Converted to throw 2022-02-22 ytop = throw "ytop has been abandoned by upstream. Consider switching to bottom instead"; yubikey-neo-manager = throw "yubikey-neo-manager has been removed because it was broken. Use yubikey-manager-qt instead"; # Added 2021-03-08 <ins> yubioath-desktop = throw "yubioath-desktop has been deprecated by upstream in favor of https://github.com/Yubico/yubioath-flutter"; # Added 2022-11-22 </ins> yuzu-ea = yuzu-early-access; # Added 2022-08-18 yuzu = yuzu-mainline; # Added 2021-01-25

Discussion:
yubioath-desktop is unable to talk to YubiKey devices, seemingly because it is unable to import the python module. Steps to reproduce the behavior: from a terminal No Python errors, and the TOTP tokens to show up in the UI. This is what the UI displays, indefinitely. ! The behaviour is the same regardless of whether a YubiKey device is present. is installed via , using a flake-based config.
It's not clear to me, which python package they want here.
It looks like upstream has deprecated this package in favor of:
See
Hi! The error is caused by a dependency on yubikey-manager5, while yubioath-desktop still needs yubikey-manager4, because the python libs had breaking changes (see ). By dropping the dependency to , this can be fixed. A workaround: A suggested fix: Change and I know that this package is dropped in master () but this could be a relatively simple fix for 22.11, before changing to the new flutter-based gui. Thanks!
Thanks for the suggested fix, Submitted a PR: it gets picked up.
Change:
, cmake, pkgconfig , boost, miniupnpc, openssl, unbound, cppzmq , zeromq, pcsclite, readline, libsodium, hidapi <del> , python3Packages, randomx, rapidjson </del> <ins> , pythonProtobuf, randomx, rapidjson, libusb </ins> , CoreData, IOKit, PCSC }:

Discussion:
Describe the bug monero-gui fails to build, it was part of my . I am on nixos-unstable. To Reproduce Steps to reproduce the behavior: Expected behavior Build success. Metadata
Change:
cmakeFlags = [ "-DBUILD_SHARED_LIBS=ON" ]; <ins> preConfigure  = lib.optional (!stdenv.isDarwin) '' substituteInPlace src/glx_context.c --replace "libGL.so.1" "${lib.getLib libGL}/lib/libGL.so.1" ''; </ins> meta = with stdenv.lib; { description = "Multi-platform library for creating OpenGL contexts and managing input, including keyboard, mouse, joystick and time"; homepage = http://www.glfw.org/;

Discussion:
Attempt to use libepoxy gives See
Repro: Expected: the game window pops up Actual:
That's not epoxy, but glfw problem. ALthough I would like to make PR with fixing glfw, and bump epoxy version as well.
Do we need this in 18.09 as well?
I feel it good idea (is a minor version update, no major bump), and looks no breakages from it (At least firefox built ok and runs on it. I tested only switch on my test host, not full reboot after switch). But I can't prove, if it still need full paths everywhere or not. (I have some doubts about vs hardwire full paths to libraries). Need find something, using epoxy and not glfw as test subject.
I just updated to and the problem persists.