Question: export TZ="$new_TZ" fi fi <ins> # udev event notifications don't work reliably inside containers. # SDL2 already tries to automatically detect flatpak and pressure-vessel # and falls back to inotify-based discovery [1]. We make SDL2 do the # same by telling it explicitly. # # [1] <https://github.com/libsdl-org/SDL/commit/8e2746cfb6e1f1a1da5088241a1440fd2535e321> export SDL_JOYSTICK_DISABLE_UDEV=1 </ins> '' + extraProfile; runScript = writeScript "steam-wrapper.sh" ''

→
I still have this issue, with both an xbox 360 controller with the wireless adapter as well with an 8Bitdo SN30+ in both wired and wireless mode. Starting steam with any of these already connected works, but if one gets connected after starting steam (or worse - shortly disconnects while playing) it will not be reconnected until a Steam restart. However, with a Steam Controller hotplugging works just fine! This happens with Steam Big Picture mode (and also in games, but I guess Big Picture mode is more readily reproducable). I assume I am doing something wrong as others have it fixed, is this really no longer an issue for others? Happy for any pointers and to assist in debugging. (my config is at in case it is needed, i am currently on )
I assume I am doing something wrong as others have it fixed, is this really no longer an issue for others? I have the same issue, with PS5 DualSense controllers. I debugged a bit during the christmas holiday, based on some info in either this issue or some other... By applying a patch (linked from the issue) I was able to see udev starting to detect hotplugging the controller in the Steam FHS env (it didn't detect these events by default), but still Steam wouldn't pick up the hotplugged controller.
I found my experimental config snippet from back then: AFAIR, I was worried that steam itself didn't use the patched libudev, but I'm pretty sure I looked up the process map and found it had (only) loaded the patched libudev, so I'm not sure what's going on. Didn't look at it since.
If anyone just wants to throw money at this problem I highly suggest the to solve it. The real win with this gamepad is that it always shows up as connected to your PC, even when it is powered off. It achieves this by coming with a usb dongle that shows up effectively as a wired joystick regardless if the gamepad is being used or not. Perfect solution for this problem... I have 3.


Question: export TZ="$new_TZ" fi fi <ins> # udev event notifications don't work reliably inside containers. # SDL2 already tries to automatically detect flatpak and pressure-vessel # and falls back to inotify-based discovery [1]. We make SDL2 do the # same by telling it explicitly. # # [1] <https://github.com/libsdl-org/SDL/commit/8e2746cfb6e1f1a1da5088241a1440fd2535e321> export SDL_JOYSTICK_DISABLE_UDEV=1 </ins> '' + extraProfile; runScript = writeScript "steam-wrapper.sh" ''

I'll mention a potential con, though: Make sure you have good line of sight between the usb dongle and the gamepad (don't worry, it comes with a ~1m usb extension cable to allow good line of sight) and aren't too far away (3-4 m I would guess) or else the signal is really spotty. In my last setup I used this through the wall and it absolutely wouldn't work for any serious gaming, but now I have the pc in the same room as the gamepads with direct line of sight and it is perfect. But yeah... a real solution would be better and still appreciated by me. Just thought I'd post this in case anyone could benefit from it. :man_shrugging:
Another alternative is to use : in the config: then install and run it: I didn't have any issues since doing it since flatpak was updated to = 1.12
I still have this issue on Nix's version of steam using nixos-unstable. Enabling xpadneo did not fix it either.
may have fixed this
Seems like didn't fix it. I see that it is in nixos-unstable and it seems like Steam still displays the same issue with my DualSense controller. I need to restart Steam before it detects it
I am having this issue on every controller I have: Steam Controller Nintendo Switch Pro Controller PS3 Controller Gulikit King Kong Pro 2 Controller in all 4 modes (Switch, XInput, DInput, Android/iOS) USB adapters for NES, SNES, and Gamecube controllers It occurs when using both Bluetooth and USB, so I am 90% certain it has nothing to do with which controller you are using. The behavior is the same for all of them; when I connect any USB/Bluetooth controller it is not recognized or noticed by Steam if it is already running, but only when Steam is starting up while the controller is currently plugged in. Here's some information on what happens when I use the Gulikit controller (XInput mode via bluetooth): Controller connected and Steam is not started At this point, and are now created Now I start Steam And reports: And now and are created (???)


Question: export TZ="$new_TZ" fi fi <ins> # udev event notifications don't work reliably inside containers. # SDL2 already tries to automatically detect flatpak and pressure-vessel # and falls back to inotify-based discovery [1]. We make SDL2 do the # same by telling it explicitly. # # [1] <https://github.com/libsdl-org/SDL/commit/8e2746cfb6e1f1a1da5088241a1440fd2535e321> export SDL_JOYSTICK_DISABLE_UDEV=1 </ins> '' + extraProfile; runScript = writeScript "steam-wrapper.sh" ''

Disconnected the controller with Steam running Nothing new in I reconnect the controller with Steam running* And and is back TL;DR - So it looks like Steam will normally start up and find the controller and then it will create the virtual input devices and . However, it won't create these devices when they are connected after Steam is already running. The question I have is why this happens and what can be done to fix it. It looks to be a NixOS specific issue as the problem doesn't appear to be on other Linux distributions like Arch (just reading off of what's in this thread, I haven't tried myself). If anyone wants me to try anything and test it on a fair variety of USB/Bluetooth controllers please let me know. I think something might be wrong with how the FHS wrapper () seems to be binding the devices that prevents new devices from being seen. EDIT: I just confirmed the and device files are appearing and disappearing in the environment that Steam runs in, so the FHS is actually properly creating those devices. The only difference I can see is that they are owned by in the FHS environment (versus in the normal environment). I can still properly access both. I did see : However, that would imply this is not NixOS specific and instead is default Steam behavior. No indication of how to change that default behavior though, so I can't find a way to confirm it.
This seems related:
Just as an datapoint: The Steam Controller is actually one that does not exhibit this issue for me, at least not when wirelessly connected with the Dongle that came with it. If I connect it via cable then it is the same as usual, only recognized when restarting steam. Also if connected via dongle and I replug the dongle, the controller only gets recognized when restarting steam. But if the dongle stays put and I shutdown the controller (by holding the Steam button for a few seconds) and start it again it works just fine with steam running. I guess it might be similar to the controller described in
I was surprised as well, and a little bit of digging reveals that SDL2 being inside flatpak and disables the unreliable udev-based discovery. And disabling it manually ! I opened to fix this.
Can confirm that it fixed the issue for me. Good job in discovering this
This is resolved for me now as well.


Question: <ins> { lib , stdenv , fetchFromGitHub , meson , ninja , pkg-config , wine , boost , libxcb }: let # Derived from subprojects/bitsery.wrap bitsery = rec { version = "5.2.0"; src = fetchFromGitHub { owner = "fraillt"; repo = "bitsery"; rev = "v${version}"; sha256 = "132b0n0xlpcv97l6bhk9n57hg95pkhwqzvr9jkv57nmggn76s5q7"; }; }; # Derived from subprojects/function2.wrap function2 = rec { version = "4.1.0"; src = fetchFromGitHub { owner = "Naios"; repo = "function2"; rev = version; sha256 = "0abrz2as62725g212qswi35nsdlf5wrhcz78hm2qidbgqr9rkir5"; }; }; # Derived from subprojects/tomlplusplus.wrap tomlplusplus = rec { version = "2.1.0"; src = fetchFromGitHub { owner = "marzer"; repo = "tomlplusplus"; rev = "v${version}"; sha256 = "0fspinnpyk1c9ay0h3wl8d4bbm6aswlypnrw2c7pk2i4mh981b4b"; }; }; # Derived from vst3.wrap vst3 = rec { version = "e2fbb41f28a4b311f2fc7d28e9b4330eec1802b6"; src = fetchFromGitHub { owner = "robbert-vdh"; repo = "vst3sdk"; rev = version; fetchSubmodules = true; sha256 = "1fqpylkbljifwdw2z75agc0yxnhmv4b09fxs3rvlw1qmm5mwx0p2"; }; }; in stdenv.mkDerivation rec { pname = "yabridge"; version = "3.0.0"; # NOTE: Also update yabridgectl's cargoSha256 when this is updated src = fetchFromGitHub { owner = "robbert-vdh"; repo = pname; rev = version; sha256 = "0ha7jhnkd2i49q5rz2hp7sq6hv19bir99x51hs6nvvcf16hlf2bp"; }; # Unpack subproject sources postUnpack = ''( cd "$sourceRoot/subprojects" cp -R --no-preserve=mode,ownership ${bitsery.src} bitsery-${bitsery.version} tar -xf bitsery-patch-${bitsery.version}.tar.xz cp -R --no-preserve=mode,ownership ${function2.src} function2-${function2.version} tar -xf function2-patch-${function2.version}.tar.xz cp -R --no-preserve=mode,ownership ${tomlplusplus.src} tomlplusplus cp -R --no-preserve=mode,ownership ${vst3.src} vst3 )''; postPatch = '' patchShebangs . ''; nativeBuildInputs = [ meson ninja pkg-config wine ]; buildInputs = [ boost libxcb ]; # Meson is no longer able to pick up Boost automatically. # https://github.com/NixOS/nixpkgs/issues/86131 BOOST_INCLUDEDIR = "${lib.getDev boost}/include"; BOOST_LIBRARYDIR = "${lib.getLib boost}/lib"; mesonFlags = [ "--cross-file" "cross-wine.conf" # Requires CMake and is unnecessary "-Dtomlplusplus:GENERATE_CMAKE_CONFIG=disabled" # tomlplusplus examples and tests don't build with winegcc "-Dtomlplusplus:BUILD_EXAMPLES=disabled" "-Dtomlplusplus:BUILD_TESTS=disabled" ]; installPhase = '' mkdir -p "$out/bin" "$out/lib" cp yabridge-group.exe{,.so} "$out/bin" cp yabridge-host.exe{,.so} "$out/bin" cp libyabridge-vst2.so "$out/lib" cp libyabridge-vst3.so "$out/lib" ''; meta = with lib; { description = "Yet Another VST bridge, run Windows VST2 plugins under Linux"; homepage = "https://github.com/robbert-vdh/yabridge"; license = licenses.gpl3Plus; maintainers = with maintainers; [ metadark ]; platforms = [ "x86_64-linux" ]; }; } </ins>

Project description Yet Another way to use Windows VST plugins on Linux. Yabridge seamlessly supports using both 32-bit and 64-bit Windows VST2 and VST3 plugins in a 64-bit Linux VST host as if they were native VST2 and VST3 plugins, with optional support for plugin groups to enable inter-plugin communication for VST2 plugins and quick startup times. Its modern concurrent architecture and focus on transparency allows yabridge to be both fast and highly compatible, while also staying easy to debug and maintain. If I understand correctly, this provides similar functionality to the airwave package. I think the big plus to this package though is that it emulates as if they were native which means the build process doesn't need to require the user to go to the steinberg site and download the VST SDK (as airwave currently does). I used this on Arch with Reaper and it was extremely easy to get going. I had a much easier time using yabridge than trying to get carla set up and running. There are multiple AUR packages for installing from source or just pulling in the binaries. I've tried to package this myself but it's just a bit beyond my means. I think that if someone is more familiar with packaging wine related binaries or compiling with meson from source this would be a quick win. homepage URL: source URL: license: GPL 3.0 platforms: linux
I probably won't have time today, but I can take a look at this later. I'm pretty familiar with the nixpkgs wine build, and I've worked with the ZynAddSubFx build to add support for the Zyn-Fusion ui.
Amazing. I was able to take your PR and get Upright Piano working with Reaper as well. Thank you so much for the quick turn around, I really appreciate it.
Hi! I don't use NixOS myself, but if it helps, there's one person in the yabridge Discord currently using yabridge's master branch with NixOS. And I've also ran into another Nix build definition on GitHub in the past (but that one's pretty outdated by now).
I've just released with a lot of important new features, fixes and improvements including the first ever Linux <-Windows VST3 plugin bridge.


Question: <ins> { lib , stdenv , fetchFromGitHub , meson , ninja , pkg-config , wine , boost , libxcb }: let # Derived from subprojects/bitsery.wrap bitsery = rec { version = "5.2.0"; src = fetchFromGitHub { owner = "fraillt"; repo = "bitsery"; rev = "v${version}"; sha256 = "132b0n0xlpcv97l6bhk9n57hg95pkhwqzvr9jkv57nmggn76s5q7"; }; }; # Derived from subprojects/function2.wrap function2 = rec { version = "4.1.0"; src = fetchFromGitHub { owner = "Naios"; repo = "function2"; rev = version; sha256 = "0abrz2as62725g212qswi35nsdlf5wrhcz78hm2qidbgqr9rkir5"; }; }; # Derived from subprojects/tomlplusplus.wrap tomlplusplus = rec { version = "2.1.0"; src = fetchFromGitHub { owner = "marzer"; repo = "tomlplusplus"; rev = "v${version}"; sha256 = "0fspinnpyk1c9ay0h3wl8d4bbm6aswlypnrw2c7pk2i4mh981b4b"; }; }; # Derived from vst3.wrap vst3 = rec { version = "e2fbb41f28a4b311f2fc7d28e9b4330eec1802b6"; src = fetchFromGitHub { owner = "robbert-vdh"; repo = "vst3sdk"; rev = version; fetchSubmodules = true; sha256 = "1fqpylkbljifwdw2z75agc0yxnhmv4b09fxs3rvlw1qmm5mwx0p2"; }; }; in stdenv.mkDerivation rec { pname = "yabridge"; version = "3.0.0"; # NOTE: Also update yabridgectl's cargoSha256 when this is updated src = fetchFromGitHub { owner = "robbert-vdh"; repo = pname; rev = version; sha256 = "0ha7jhnkd2i49q5rz2hp7sq6hv19bir99x51hs6nvvcf16hlf2bp"; }; # Unpack subproject sources postUnpack = ''( cd "$sourceRoot/subprojects" cp -R --no-preserve=mode,ownership ${bitsery.src} bitsery-${bitsery.version} tar -xf bitsery-patch-${bitsery.version}.tar.xz cp -R --no-preserve=mode,ownership ${function2.src} function2-${function2.version} tar -xf function2-patch-${function2.version}.tar.xz cp -R --no-preserve=mode,ownership ${tomlplusplus.src} tomlplusplus cp -R --no-preserve=mode,ownership ${vst3.src} vst3 )''; postPatch = '' patchShebangs . ''; nativeBuildInputs = [ meson ninja pkg-config wine ]; buildInputs = [ boost libxcb ]; # Meson is no longer able to pick up Boost automatically. # https://github.com/NixOS/nixpkgs/issues/86131 BOOST_INCLUDEDIR = "${lib.getDev boost}/include"; BOOST_LIBRARYDIR = "${lib.getLib boost}/lib"; mesonFlags = [ "--cross-file" "cross-wine.conf" # Requires CMake and is unnecessary "-Dtomlplusplus:GENERATE_CMAKE_CONFIG=disabled" # tomlplusplus examples and tests don't build with winegcc "-Dtomlplusplus:BUILD_EXAMPLES=disabled" "-Dtomlplusplus:BUILD_TESTS=disabled" ]; installPhase = '' mkdir -p "$out/bin" "$out/lib" cp yabridge-group.exe{,.so} "$out/bin" cp yabridge-host.exe{,.so} "$out/bin" cp libyabridge-vst2.so "$out/lib" cp libyabridge-vst3.so "$out/lib" ''; meta = with lib; { description = "Yet Another VST bridge, run Windows VST2 plugins under Linux"; homepage = "https://github.com/robbert-vdh/yabridge"; license = licenses.gpl3Plus; maintainers = with maintainers; [ metadark ]; platforms = [ "x86_64-linux" ]; }; } </ins>

I saw that the package created by for yabridge 2.2.1 has not been merged yet, but please let me know if you want to update the yabridge and yabridgectl packages for yabridge 3.0.0 and need any help! One additional dependency is now a patched version of the VST3 SDK which is patched to compile under winegcc and with support for Meson. I'm not quite sure how Nix packaging handles those things.
Thanks, I have it building right now. I'm just testing out vst3 plugins right now :smile:
:cry: For some reason neither the vst2 or vst3 plugins are working, even though they get synced. I think it might be an issue with my system installed wine. I'll submit my changes anyway so other people can test it out.
So they are found but yabridge fails to load them? Which Wine are your derivations using?
You can try running manually to see if that is the issue. A plain call should print: And should print:
I'm able to sync them with yabridgectl, but they fail to load in Reaper. I'm using (currently version 6.0) to build yabridge, but I have a custom build of wine staging 6.0 currently installed. seems to be working fine:
That indeed seems to work as expected, that's great news! If you start REAPER with and then take a look at after trying to scan/load a plugin then you'll probably be able to figure out what's wrong very quickly.
Hmm, apparently the path to the VST host is too long :stuckouttongue:
Huh I can't think of from the top of my head what would be throwing such an exception. That message printed after comes from a try-catch around the entire plugin startup that catches and prints any . Windows (and thus Wine, because it has to be compatible haha) has a path name limit of 255 characters, but none of those paths sound like they should come close to that.
Yeah, sorry. It was just a problem with my home environment. I was trying to test it without installing because I lost the nixpkgs commit I used to generate my home-manager environment.


Question: <ins> { lib , stdenv , fetchFromGitHub , meson , ninja , pkg-config , wine , boost , libxcb }: let # Derived from subprojects/bitsery.wrap bitsery = rec { version = "5.2.0"; src = fetchFromGitHub { owner = "fraillt"; repo = "bitsery"; rev = "v${version}"; sha256 = "132b0n0xlpcv97l6bhk9n57hg95pkhwqzvr9jkv57nmggn76s5q7"; }; }; # Derived from subprojects/function2.wrap function2 = rec { version = "4.1.0"; src = fetchFromGitHub { owner = "Naios"; repo = "function2"; rev = version; sha256 = "0abrz2as62725g212qswi35nsdlf5wrhcz78hm2qidbgqr9rkir5"; }; }; # Derived from subprojects/tomlplusplus.wrap tomlplusplus = rec { version = "2.1.0"; src = fetchFromGitHub { owner = "marzer"; repo = "tomlplusplus"; rev = "v${version}"; sha256 = "0fspinnpyk1c9ay0h3wl8d4bbm6aswlypnrw2c7pk2i4mh981b4b"; }; }; # Derived from vst3.wrap vst3 = rec { version = "e2fbb41f28a4b311f2fc7d28e9b4330eec1802b6"; src = fetchFromGitHub { owner = "robbert-vdh"; repo = "vst3sdk"; rev = version; fetchSubmodules = true; sha256 = "1fqpylkbljifwdw2z75agc0yxnhmv4b09fxs3rvlw1qmm5mwx0p2"; }; }; in stdenv.mkDerivation rec { pname = "yabridge"; version = "3.0.0"; # NOTE: Also update yabridgectl's cargoSha256 when this is updated src = fetchFromGitHub { owner = "robbert-vdh"; repo = pname; rev = version; sha256 = "0ha7jhnkd2i49q5rz2hp7sq6hv19bir99x51hs6nvvcf16hlf2bp"; }; # Unpack subproject sources postUnpack = ''( cd "$sourceRoot/subprojects" cp -R --no-preserve=mode,ownership ${bitsery.src} bitsery-${bitsery.version} tar -xf bitsery-patch-${bitsery.version}.tar.xz cp -R --no-preserve=mode,ownership ${function2.src} function2-${function2.version} tar -xf function2-patch-${function2.version}.tar.xz cp -R --no-preserve=mode,ownership ${tomlplusplus.src} tomlplusplus cp -R --no-preserve=mode,ownership ${vst3.src} vst3 )''; postPatch = '' patchShebangs . ''; nativeBuildInputs = [ meson ninja pkg-config wine ]; buildInputs = [ boost libxcb ]; # Meson is no longer able to pick up Boost automatically. # https://github.com/NixOS/nixpkgs/issues/86131 BOOST_INCLUDEDIR = "${lib.getDev boost}/include"; BOOST_LIBRARYDIR = "${lib.getLib boost}/lib"; mesonFlags = [ "--cross-file" "cross-wine.conf" # Requires CMake and is unnecessary "-Dtomlplusplus:GENERATE_CMAKE_CONFIG=disabled" # tomlplusplus examples and tests don't build with winegcc "-Dtomlplusplus:BUILD_EXAMPLES=disabled" "-Dtomlplusplus:BUILD_TESTS=disabled" ]; installPhase = '' mkdir -p "$out/bin" "$out/lib" cp yabridge-group.exe{,.so} "$out/bin" cp yabridge-host.exe{,.so} "$out/bin" cp libyabridge-vst2.so "$out/lib" cp libyabridge-vst3.so "$out/lib" ''; meta = with lib; { description = "Yet Another VST bridge, run Windows VST2 plugins under Linux"; homepage = "https://github.com/robbert-vdh/yabridge"; license = licenses.gpl3Plus; maintainers = with maintainers; [ metadark ]; platforms = [ "x86_64-linux" ]; }; } </ins>

REAPER was just loading the old 2.2.1 yabridge- :woman_facepalming: I just finished rebuilding my home environment with a new nixpkgs commit, and it's working now :smile: .


Question: let common = { name, npmBuildScript, installPhase }: buildNpmPackage rec { pname = name; <del> version = "2024.3.1"; </del> <ins> version = "2024.3.2"; </ins> nodejs = nodejs_18; src = fetchFromGitHub { owner = "bitwarden"; repo = "directory-connector"; rev = "v${version}"; <del> hash = "sha256-NbyjL6x/Ij5waYlIDNKrg7fDT+co/EcdCW4ZBJ6KV34="; </del> <ins> hash = "sha256-CB5HrT+p63zANg1SEoynk6hPPW5DcC9Qfo2+QDy2iwc="; </ins> }; postPatch = ''

This link is invalid: It is used to download the build Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: lockFile = ./Cargo.lock; outputHashes = { "edgedb-derive-0.5.0" = "sha256-y/mN0XuJtQBtkLmbk2s7hK5joGEH5Ge6sLCD88WyL9o="; <ins> "edgeql-parser-0.1.0" = "sha256-Y3gXxPuR7qnTL4fu2nZIa3e20YV1fLvm2jHAng+Ke2Q="; </ins> "indexmap-2.0.0-pre" = "sha256-QMOmoUHE1F/sp+NeDpgRGqqacWLHWG02YgZc5vAdXZY="; "rexpect-0.5.0" = "sha256-vstAL/fJWWx7WbmRxNItKpzvgGF3SvJDs5isq9ym/OA="; <del> "edgeql-parser-0.1.0" = "sha256-Y3gXxPuR7qnTL4fu2nZIa3e20YV1fLvm2jHAng+Ke2Q="; </del> "rustyline-8.0.0" = "sha256-CrICwQbHPzS4QdVIEHxt2euX+g+0pFYe84NfMp1daEc="; "serde_str-1.0.0" = "sha256-CMBh5lxdQb2085y0jc/DrV6B8iiXvVO2aoZH/lFFjak="; };

Package name: edgedb Latest released version: 3.2.0 Current version on the unstable channel: 2.3.1 Current version on the stable/release channel: 2.3.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.


Question: }: let <del> generator = pkgsBuildBuild.buildGoModule { </del> <ins> generator = pkgsBuildBuild.buildGo120Module { </ins> pname = "v2ray-geoip"; <del> version = "unstable-2023-03-27"; </del> <ins> version = "unstable-2023-10-11"; </ins> src = fetchFromGitHub { owner = "v2fly"; repo = "geoip"; <del> rev = "9321a7f5e301a957228eba44845144b4555b6658"; hash = "sha256-S30XEgzA9Vrq7I7REfO/WN/PKpcjcI7KZnrL4uw/Chs="; </del> <ins> rev = "3182dda7b38c900f28505b91a44b09ec486e6f36"; hash = "sha256-KSRgof78jScwnUeMtryj34J0mBsM/x9hFE4H9WtZUuM="; </ins> }; <del> vendorHash = "sha256-bAXeA1pDIUuEvzTLydUIX6S6fm6j7CUQmBG+7xvxUcc="; </del> <ins> vendorHash = "sha256-rlRazevKnWy/Ig143s8TZgV3JlQMlHID9rnncLYhQDc="; </ins> meta = with lib; { description = "GeoIP for V2Ray";

Steps to reproduce the behavior: , build v2ray-geoip Probably we can pin to buildGo120Module?


Question: <del> { stdenv, fetchurl, meson, ninja, gettext, pkgconfig, spidermonkey_52, glib, gnome3 }: </del> <ins> { stdenv, fetchurl, meson, ninja, gettext, pkgconfig, spidermonkey_52, glib , gnome3, substituteAll }: </ins> stdenv.mkDerivation rec { name = "gnome-shell-extensions-${version}";

The meson build doesn't compile the schemas, opting to do it instead in a package shell script. Unfortunately it seems that compiling the schemas aren't enough to make all the extensions work. In particular at least and still won't work (seems to fix though). With the schemas installed Tweaks simply complains that the extension is incorrectly installed. complains about lacking any typelib file for . I'm not sure how well these extensions worked before 3.28, but a report on irc indicated that at least worked before. cc Run Tweaks on nixos-unstable, try to enable eg. the extension under or . Running a schema fix on top of system: host os: multi-user?: sandbox: version: channels(hed): channels(root): nixpkgs:
The extension works for me when I manually change the directory structure to: As for the , I removed from dependencies so that might explain this failure. The extension should probably be fixed like .
You're able to switch switch themes in in Tweaks? Might be something wrong on my end. I'll submit a PR fixing the schemas at least.
Testing out a fix for .
Hmm, I can enable it but the theme switching does not work. I seems to require the extension schemas in when running Tweaks. Maybe it got picked up from global for bash users, but the option was always disabled for me with fish.
We might want to add as a dependency to Tweaks so that it could work for non-bash users. Then we will need to fix the schemas: the schemas in and find a hack similar to to add the schemas path to the extension. like the following to put the schemas where extensions can find them and add symlink for Tweaks. same thing as the second point but accomplished by patching files.
Your suggested fix worked for at least :) I went with basically adding the code from to to fix the schema problem. Generating the directory structure you quoted above seems the most sane and keeping with upstream. Tested things out in a vm with bash, and didn't seem to work there either. So not sure if the problem is non bash. Anyway, adding to fixes , so I think that's appropriate. I should've got everything now, will submit a PR :)
I think it only works in bash and globally installed packages or something.


Question: <del> { stdenv, fetchurl, meson, ninja, gettext, pkgconfig, spidermonkey_52, glib, gnome3 }: </del> <ins> { stdenv, fetchurl, meson, ninja, gettext, pkgconfig, spidermonkey_52, glib , gnome3, substituteAll }: </ins> stdenv.mkDerivation rec { name = "gnome-shell-extensions-${version}";

I would not rely on it since I consider it an ugly impurity. I would prefer the first solution since it will be the cleanest and could be possibly automated in the future, but number two is fine too.


Question: nativeBuildInputs = [ xz.bin ]; <del> makeFlags = [ "SHELL=/bin/sh" "GREP=grep" ]; </del> <ins> makeFlags = [ "SHELL=/bin/sh" "GREP=grep" # gzip 1.12 doesn't build `zless` unless it can find `less`, but we # can avoid having `less` as a build input if we just override these. "ZLESS_MAN=zless.1" "ZLESS_PROG=zless" ]; </ins> # Many gzip executables are shell scripts that depend upon other gzip # executables being in $PATH.  Rather than try to re-write all the

NixOS's gzip 1.11 contained , but gzip 1.12 does not. This was probably caused by Please run and paste the result.


Question: pushd packages/bruno-electron <del> ${if stdenv.isDarwin then '' cp -r ${electron}/Applications/Electron.app ./ find ./Electron.app -name 'Info.plist' | xargs -d 'n' chmod +rw substituteInPlace electron-builder-config.js  --replace-fail "identity: 'Anoop MD (W7LPPWA48L)'" 'identity: null'  --replace-fail "afterSign: 'notarize.js'," "" npm exec electron-builder --  --dir  --config electron-builder-config.js  -c.electronDist=./  -c.electronVersion=${electron.version}  -c.npmRebuild=false '' else '' npm exec electron-builder --  --dir  -c.electronDist=${electron}/libexec/electron  -c.electronVersion=${electron.version}  -c.npmRebuild=false ''} </del> <ins> ${ if stdenv.isDarwin then '' cp -r ${electron}/Applications/Electron.app ./ find ./Electron.app -name 'Info.plist' | xargs -d 'n' chmod +rw substituteInPlace electron-builder-config.js  --replace-fail "identity: 'Anoop MD (W7LPPWA48L)'" 'identity: null'  --replace-fail "afterSign: 'notarize.js'," "" npm exec electron-builder --  --dir  --config electron-builder-config.js  -c.electronDist=./  -c.electronVersion=${electron.version}  -c.npmRebuild=false '' else '' npm exec electron-builder --  --dir  -c.electronDist=${electron}/libexec/electron  -c.electronVersion=${electron.version}  -c.npmRebuild=false '' } </ins> popd '';

Attempt to build on Sample This is on an M2 chip, and it seems the issue is with node-canvas not being able to install due to missing giflib. Building with: Fixes this. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: , texinfo , zlib <del> , enableGold ? execFormatIsELF stdenv.targetPlatform </del> <ins> , enableGold ? withGold stdenv.targetPlatform </ins> , enableShared ? !stdenv.hostPlatform.isStatic # WARN: Enabling all targets increases output size to a multiple. , withAllTargets ? false

Despite the bintools for riscv64-linux advertises the existence of , it is actually missing. Steps to reproduce the behavior: , returns the output, there is only , no the same process for , is both advertised and available. Either evaluates to , or is available in <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Looking at ;a=blob;;h=;hb=HEAD is not supported on riscv64. tracks it upstream. I don't expect progress implementing the support any time soon.
Then we should accept the second solution: mark as false, we should also double check the availability of gold on other ELF platforms.


Question: <ins> diff -ru gfan0.6.2.orig/src/app_librarytest.cpp gfan0.6.2/src/app_librarytest.cpp --- gfan0.6.2.orig/src/app_librarytest.cpp	2020-10-19 08:41:27.981863500 +0900 +++ gfan0.6.2/src/app_librarytest.cpp	2020-10-19 08:42:44.551863500 +0900 @@ -12,8 +12,8 @@ #include "setoper.h" #include "cdd.h" #else -#include "cdd/setoper.h" -#include "cdd/cdd.h" +#include "cddlib/setoper.h" +#include "cddlib/cdd.h" #endif #include <iostream> #include <fstream> diff -ru gfan0.6.2.orig/src/gfanlib_zcone.cpp gfan0.6.2/src/gfanlib_zcone.cpp --- gfan0.6.2.orig/src/gfanlib_zcone.cpp	2020-10-19 08:41:27.981863500 +0900 +++ gfan0.6.2/src/gfanlib_zcone.cpp	2020-10-19 08:42:44.571863500 +0900 @@ -16,8 +16,8 @@ #include "setoper.h" #include "cdd.h" #else -#include "cdd/setoper.h" -#include "cdd/cdd.h" +#include "cddlib/setoper.h" +#include "cddlib/cdd.h" #endif //} @@ -52,8 +52,8 @@ "dd_free_global_constants()n" "in your deinitialisation code (only available for cddlib version>=094d).n" "This requires the header includes:n" -				  "#include "cdd/setoper.h"n" -				  "#include "cdd/cdd.h"n" +				  "#include "cddlib/setoper.h"n" +				  "#include "cddlib/cdd.h"n" "n" "Alternatively, you may call gfan:initializeCddlibIfRequired() and deinitializeCddlibIfRequired()n" "if gfanlib is the only code using cddlib. If at some point cddlib is no longer required by gfanlibn" diff -ru gfan0.6.2.orig/src/lp_cdd.cpp gfan0.6.2/src/lp_cdd.cpp --- gfan0.6.2.orig/src/lp_cdd.cpp	2020-10-19 08:41:27.991863500 +0900 +++ gfan0.6.2/src/lp_cdd.cpp	2020-10-19 08:42:44.571863500 +0900 @@ -5,9 +5,9 @@ #include "cdd.h" #include "cdd_f.h" #else -#include "cdd/setoper.h" -#include "cdd/cdd.h" -#include "cdd/cdd_f.h" +#include "cddlib/setoper.h" +#include "cddlib/cdd.h" +#include "cddlib/cdd_f.h" #endif //} #include "termorder.h" </ins>

Describe the bug Building fails with the following messages: Note that points to which updates . To Reproduce Steps to reproduce the behavior: Expected behavior The package is built successfully. Notify maintainers (gfan, cddlib), (cddlib) Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(omasanori): nixpkgs: Maintainer information:
cddlib put its .h file in <hash-cddlib-0.94l/include/cddlib/ rather than the old version of the library placing it .h headers in the root. <hash-cddlib-0.94j/include/ So options are get upstream to #include "cddlib/setoper.h" (and the rest of the directly pathed includes) Patch it in the derivation Take a look at the library is being why it differs from 0.94j to 0.94l ...... and see if can be symlinked (botched). not sure why it's subpathing these .h file now?
v0.94k header files are now installed to PREFIX/include/cddlib to avoid clashes with other libraries. configuration file for pkg-config : assuming cddlib installed in <prefixknown to pkg-config, "pkg-config --cflags cddlib" etc will work. (Otherwise, one would need PKGCONFIGPATH=<prefix/lib/pkgconfig). this is the source of the breakage. this probably breaks everything that uses this library.... lovely! So, options are fix it gfan upstream, or patch it in nix?????? has a 41 length thread, where the developers are trying to workout how not to break any application that uses this library and which distro's they want to break.
Thank you for your survey, The long-term solution would be fixing gfan upstream, given that this is not Nix-specific. The current Makefile assumes that, if cddlib headers are prefixed, the prefix is instead of . A variable to change the prefix will help every package maintainer IMHO. However, adding a patch to gfan just altering with into nixpkg may be fine for now. I will try to address it next week but feel free to make a PR if it is urgent for anyone.


Question: buildPythonApplication rec { pname = "glances"; <del> version = "3.1.7"; </del> <ins> version = "3.2.3"; </ins> disabled = isPyPy; src = fetchFromGitHub { owner = "nicolargo"; repo = "glances"; rev = "v${version}"; <del> sha256 = "sha256-82ZD32dqRYGbGM/uyaJ5VqVZbhDZthiEcTihkV43JOU="; </del> <ins> sha256 = "1nc8bdzzrzaircq3myd32w6arpy2prn739886cq2h47cpinxmvpr"; </ins> }; # Some tests fail in the sandbox (they e.g. require access to /sys/class/power_supply):

, CVSSv3=9.8 (nixos-21.05) The package glances before 3.2.1 are vulnerable to XML External Entity (XXE) Injection via the use of Fault to parse untrusted XML data, which is known to be vulnerable to XML attacks. Scanned versions: nixos-21.05: . Cc Cc Cc
This was resolved by


Question: outputs = [ "out" "dev" ]; <ins> patches = [ # To use split outputs, we need this so double prefix won't be used in the # pkg-config files. Hopefully, this won't be needed on the next release, # _if_ # https://gitlab.freedesktop.org/gstreamer/gst-rtsp-server/merge_requests/1 # will be merged. For the current release, this merge request won't apply. ./fix_pkgconfig_includedir.patch ]; </ins> nativeBuildInputs = [ meson ninja

Describe the bug When trying to use this package, I'm getting: To Reproduce Additional context I'm currently disabling gst-rtsp-server's split outputs in order to actually use it. Notify maintainers Maintainer information:
We should probably apply
That patch won't apply. But I managed to apply a different fix based on a common fix to other gst plugins, at .


Question: buildInputs = lib.optionals stdenv.isDarwin [ CoreServices ApplicationServices ] ++ [ zlib libuv openssl http-parser icu bash ]; <del> nativeBuildInputs = [ which pkg-config python ] </del> <ins> nativeBuildInputs = [ installShellFiles pkg-config python which ] </ins> ++ lib.optionals stdenv.isDarwin [ xcbuild ]; outputs = [ "out" "libv8" ];

The package (and the related ones) don't offer completions, only Npm's. At least for bash Node offers it through . I'd like this bash completion to be . Install Node, see that there is no completion in the completions dir (I'm using home-manager, so that'd be ).
Fixed by


Question: # Create missing swapfiles. systemd.services = let createSwapDevice = sw: <del> assert sw.device != ""; assert !(sw.randomEncryption.enable && lib.hasPrefix "/dev/disk/by-uuid"  sw.device); assert !(sw.randomEncryption.enable && lib.hasPrefix "/dev/disk/by-label" sw.device); </del> let realDevice' = escapeSystemdPath sw.realDevice; in nameValuePair "mkswap-${sw.deviceName}" { description = "Initialisation of swap device ${sw.device}"; wantedBy = [ "${realDevice'}.swap" ]; before = [ "${realDevice'}.swap" ]; <del> path = [ pkgs.util-linux ] ++ optional sw.randomEncryption.enable pkgs.cryptsetup; </del> <ins> path = [ pkgs.util-linux pkgs.e2fsprogs ] ++ optional sw.randomEncryption.enable pkgs.cryptsetup; environment.DEVICE = sw.device; </ins> script = '' ${optionalString (sw.size != null) '' <del> currentSize=$(( $(stat -c "%s" "${sw.device}" 2>/dev/null || echo 0) / 1024 / 1024 )) if [ "${toString sw.size}" != "$currentSize" ]; then dd if=/dev/zero of="${sw.device}" bs=1M count=${toString sw.size} </del> <ins> currentSize=$(( $(stat -c "%s" "$DEVICE" 2>/dev/null || echo 0) / 1024 / 1024 )) if [[ ! -b "$DEVICE" && "${toString sw.size}" != "$currentSize" ]]; then # Disable CoW for CoW based filesystems like BTRFS. truncate --size 0 "$DEVICE" chattr +C "$DEVICE" 2>/dev/null || true dd if=/dev/zero of="$DEVICE" bs=1M count=${toString sw.size} </ins> chmod 0600 ${sw.device} ${optionalString (!sw.randomEncryption.enable) "mkswap ${sw.realDevice}"} fi

When using to create and activate a swapfile on btrfs, it fails with messages like this: The kernel says: I am not very familiar with Nix, but after reading the corresponding and , it seems that creating a swapfile on btrfs requires disabling copy-on-write for that file (via ) as well. However, doesn't do it currently. BTW, manually creating the swapfile and letting NixOS activating it works fine for me. to ( is supposed to be mounted as btrfs). . Swapfile is created and activated without any issue. There is a workaround on NixOS Discourse: system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
I have the same issue. I already tried disabling copy-on-write for the partition but it still fails: I also still get the warning like even though I the attribute to my mount options (afterwards). My current swap configuration can be found .
Mounting with attribute won't work because: [^1]:
I came up with this yesterday, which seems to work (or at least you can follow the general pattern): I have as a separate subvolume, nothing else on it. Once you've run this to create the swapfile, it seems to mount and function properly from there on out. But yes, it would be nice if this were taken care of automatically. EDIT: Fix link
brilliant, that helped me solve my issue. While your script didn't work out for me, I was able to adjust it so it did. I noticed the following warning when running your script: So, I searched for this and found the following note on ArchWiki: — Replacing with made the warning disappear for me but running still failed with . Then I compared the script to what I've used in and noticed that I used instead of to create the empty swapfile. The full script I ended up with:
Thanks for the update. I originally used , but switched after reading that should be much faster (and have to admit I can't remember if I tested that change yet -- thank you for the feedback). I've switched it back to .


Question: <ins> --- a/subversion/bindings/swig/perl/native/Makefile.PL.in +++ b/subversion/bindings/swig/perl/native/Makefile.PL.in @@ -72,7 +72,7 @@ # According to the log of r7937, the flags guarded by the conditional break # the build on FreeBSD if not conditionalized. my $apr_ldflags = '@SVN_APR_LIBS@' -   if $^O eq 'darwin' or $^O eq 'cygwin'; +   if $^O eq 'darwin' or $^O eq 'cygwin' or $^O eq 'linux'; chomp $apr_shlib_path_var; </ins>

When is installed with , works fine. When is installed with , then prints an error message. When installing with , I get this log: So, it might be that git-with-svn-2.6.3 is fine but not . System: NixOS: = () Nix: = Nixpkgs version: () /cc
I think you have nixpkgs and nixos channel. One might be coming from root. So on one channel it works, on the other it doesn't.
This is a bug in the Perl bindings generated as a part of our Subversion build. The library depends on , but it has no RPATH set that allows it to find library. Curiously enough, is the only dependency with that problem: other library like are found properly using a full path into the Nix store. Cc: and
and it was working fine in :
As I said, this as nothing to do with Git. It's that provides broken Perl bindings.
Ran into same problem. git bisect log of checking ldd /nix/store/-subversion-1.9.3/lib/perl5/siteperl//x8664-linux-thread- follows. there's some big binutils related changes in the middle yet.


Question: ''; patches = [ # Not accepted upstream, see https://github.com/gnuradio/gnuradio/pull/5227 <del> ./modtool-newmod-permissions.patch </del> <ins> ./modtool-newmod-permissions.3_9.patch </ins> ]; passthru = shared.passthru // { # Deps that are potentially overridden and are used inside GR plugins - the same version must

Package name: gnuradio Latest released version: 3.10.8.0 <!-- Search your package here: --- Current version on the unstable channel: 3.10.7.0 Current version on the stable/release channel:3.10.7.0 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]:
Tnx. Update is proposed at


Question: owner = "pdm-project"; repo = "pdm"; rev = "refs/tags/${version}"; <del> hash = "sha256-R3oeu8HvPWAQoO0FHHx9lSKmB/riPtQ9gq4qKtQCeiA="; </del> <ins> hash = "sha256-V2ZcXgRtL8zkCx5/d+L+3o0QQHVrPpFyjvjsc2auWDI="; </ins> }; nativeBuildInputs = [ installShellFiles ];

Package name: pdm Latest released version: 2.19.1 <!-- Search your package here: --- Current version on the unstable channel: 2.18.2 Current version on the stable/release channel: 2.15.3 <!-- 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]:


Question: cmakeFlags = [ "-DUSE_SYSTEM_GTEST=ON" "-DBUILD_STATIC_LIBS=${if stdenv.hostPlatform.isStatic then "ON" else "OFF"}" <ins> ] ++ lib.optionals (!stdenv.isDarwin) [ </ins> "-DBUILD_SHARED_BINARIES=${if stdenv.hostPlatform.isStatic then "OFF" else "ON"}" ];

I cannot install on my Apple M1 PowerBook any more (potentially due to ?) I'm tracking (commit ) Steps to reproduce the behavior: Here's the output of
I'm afraid I don't have a Mac around to test with, but from glancing at the build log it appears the problem may go away if you remove from in the jsonnet derivation, or make it conditional on stdenv.hostPlatform.isStatic as suggested in .
I can confirm this issue. We worked around this in our own overlay by reverting to the last known (to us) NixPkgs version for the Jsonnet package only (i.e. we overlayed the derivation with one that is basically . No idea what exactly causes the problem, though.
didn't fix this, I still can't build jsonnet on Darwin.
This is fixed in , PTAL.


Question: services.dbus.enable = true; <ins> users.users.systemd-coredump.uid = config.ids.uids.systemd-coredump; </ins> users.users.systemd-network.uid = config.ids.uids.systemd-network; users.groups.systemd-network.gid = config.ids.gids.systemd-network; users.users.systemd-resolve.uid = config.ids.uids.systemd-resolve;

Describe the bug when a root-owned process dumps core (eg recent sshd, due to a known bug) and coredumps are enabled, systemd-coredump warns (but proceeds successfully). To Reproduce Steps to reproduce the behavior: systemd coredumps enabled a SIGABRT to any root-owned process (eg by running ) Expected behavior coredumps succeeds with proper privsep Screenshots Additional context Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Can you reproduce this with a simple c binary you interactively run as root user?
yes, as root does it. amended the original post addendum: if you want a minimal C example that causes it:
still happening regularly due to a bug in openssh (race conditions in process shutdown can cause seccomp filters to trigger)
I am also observing this problem, both sshd dumping core and the systemd-coredump error when it happens. I can also reproduce it with as root.
I can confirm I see the log messages: I looked at . It seems systemd-coredump wants to drop privileges to a user (but falls back to root if it can't find it). suggests we should create it (like we create one for ). I opened , which does that.


Question: <ins> --- a/main.cpp +++ b/main.cpp @@ -91,14 +91,5 @@ int main(int argc, char *argv[]) w.show(); } -    QTimer::singleShot(0, [=] { -       cg->getUpdateInfo(); -       QObject::connect(cg, &ClipGrab::updateInfoProcessed, [cg] { -           bool force = QSettings().value("forceYoutubeDlDownload", false).toBool(); -           if (force) QSettings().setValue("forceYoutubeDlDownload", false); -           cg->downloadYoutubeDl(force); -       }); -    }); - return app.exec(); } --- a/youtube_dl.cpp +++ b/youtube_dl.cpp @@ -8,52 +8,16 @@ YoutubeDl::YoutubeDl() QString YoutubeDl::path = QString(); QString YoutubeDl::find(bool force) { -    if (!force && !path.isEmpty()) return path; - -    // Prefer downloaded youtube-dl -    QString localPath = QStandardPaths::locate(QStandardPaths::AppDataLocation, "yt-dlp"); -    QProcess* process = instance(localPath, QStringList() << "--version"); -    process->start(); -    process->waitForFinished(); -    process->deleteLater(); -    if (process->state() != QProcess::NotRunning) process->kill(); -    if (process->exitCode() == QProcess::ExitStatus::NormalExit) { -        path = localPath; -        return path; -    } - -    // Try system-wide youtube-dlp installation -    QString globalPath = QStandardPaths::findExecutable("yt-dlp"); -    process = instance(globalPath, QStringList() << "--version"); -    process->start(); -    process->waitForFinished(); -    process->deleteLater(); -    if (process->state() != QProcess::NotRunning) process->kill(); -    if (process->exitCode() == QProcess::ExitStatus::NormalExit) { -        path = globalPath; -        return path; -    } - -    return ""; +    // We supply yt-dlp from nixpkgs, so the downloading +    // machinery is not needed anymore. +    (void)force; +    return path; } QProcess* YoutubeDl::instance(QStringList arguments) { -    return instance(find(), arguments); -} - -QProcess* YoutubeDl::instance(QString path, QStringList arguments) { QProcess *process = new QProcess(); -    QString execPath = QCoreApplication::applicationDirPath(); -    QProcessEnvironment env = QProcessEnvironment::systemEnvironment(); -    env.insert("PATH", execPath + ":" + env.value("PATH")); -    process->setEnvironment(env.toStringList()); - -    #if defined Q_OS_WIN -        process->setProgram(execPath + "/python/python.exe"); -    #else -        process->setProgram(QStandardPaths::findExecutable("python3")); -    #endif +    process->setProgram(path); QSettings settings; QStringList proxyArguments; @@ -81,7 +45,7 @@ QProcess* YoutubeDl::instance(QString path, QStringList arguments) { networkArguments << "--force-ipv4"; } -    process->setArguments(QStringList() << path << arguments << proxyArguments << networkArguments); +    process->setArguments(QStringList() << arguments << proxyArguments << networkArguments); return process; } </ins>

When started, ClipGrab always want to download youtube-dl. When after that, ClipGrab never finds the video and stays stuck on «please wait while ClipGrab downloads video info» (translated from french). Steps to reproduce the behavior: ... or ... Start ClipGrab ... youtube-dl dependency should be accessible, and video info should be fetched ! !


Question: { lib, stdenv, fetchFromGitHub, cmake, pkg-config, vala, gtk3, libgee , poppler, libpthreadstubs, gstreamer, gst-plugins-base, gst-plugins-good, gst-libav, gobject-introspection, wrapGAppsHook <del> , qrencode, webkitgtk, discount, json-glib }: </del> <ins> , qrencode, webkitgtk, discount, json-glib, fetchpatch }: </ins> stdenv.mkDerivation rec { pname = "pdfpc";

none Please run and paste the result.
I started to bisect this with at nix started to download ~4GB of derivations and I aborted the process. The is
it seems like the issue already got fixed upstream in but there is no new release yet. We either have to target commit which contains the fix, or wait for the new release.
you are right, pdfpc/pdfpc fixes this. I tried it with this patch on nixpkgs:


Question: buildInputs = [ nodejs_22 ]; <del> pnpmWorkspace = "@astrojs/language-server"; </del> <ins> # Must specify to download "@astrojs/yaml2ts" depencendies # https://pnpm.io/filtering#--filter-package_name-1 pnpmWorkspace = "@astrojs/language-server..."; </ins> prePnpmInstall = '' <ins> # Warning section for "pnpm@v8" # https://pnpm.io/cli/install#--filter-package_selector </ins> pnpm config set dedupe-peer-dependents false ''; buildPhase = '' runHook preBuild <del> pnpm --filter=@astrojs/language-server build </del> <ins> # Must build the "@astrojs/yaml2ts" package. Dependency is linked via workspace by "pnpm" # (https://github.com/withastro/language-tools/blob/%40astrojs/language-server%402.14.2/pnpm-lock.yaml#L78-L80) pnpm --filter "@astrojs/language-server..." build </ins> runHook postBuild '';

Package name: astro-language-server Latest released version: 2.14.2 <!-- Search your package here: --- Current version on the unstable channel: 2.10.0 Current version on the stable/release channel: None <!-- 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]:
I'm on it ^^. I've got a working version. Gonna soon open a PR :+1:


Question: <del> { lib, stdenv , fetchFromGitHub , fetchpatch , pkg-config , cmake , argtable , catch2 , curl , doxygen , hiredis , jsoncpp , libmicrohttpd }: </del> <ins> { lib, stdenv, fetchFromGitHub, pkg-config, cmake, argtable, catch2 , curl, doxygen, hiredis, jsoncpp, libmicrohttpd }: </ins> stdenv.mkDerivation rec { pname = "libjson-rpc-cpp"; <del> version = "1.3.0"; </del> <ins> version = "1.4.1"; </ins> src = fetchFromGitHub { owner = "cinemast"; repo = "libjson-rpc-cpp"; <del> sha256 = "sha256-EAakiqlfMprwLjloDekOssaB/EnAmn5njcwHGZtYs9w="; </del> <ins> sha256 = "sha256-YCCZN4y88AixQeo24pk6YHfSCsJz8jJ97Dg40KM08cQ="; </ins> rev = "v${version}"; }; env.NIX_CFLAGS_COMPILE = "-I${catch2}/include/catch2"; <del> patches = [ (fetchpatch { name = "int-to-MHD_Result.patch"; url = "https://patch-diff.githubusercontent.com/raw/cinemast/libjson-rpc-cpp/pull/299.patch"; sha256 = "sha256-hiey6etzbOxhMElTMX7offKbey7c2OO/UWeN03k0AaM="; }) ]; </del> nativeBuildInputs = [ pkg-config cmake doxygen ]; <del> buildInputs = [ argtable catch2 curl hiredis jsoncpp libmicrohttpd ]; </del> <ins> buildInputs = [ argtable catch2 curl hiredis jsoncpp libmicrohttpd ]; </ins> postPatch = '' for f in cmake/FindArgtable.cmake

Package name: libjson-rpc-cpp Latest released version: 1.3.0 <!-- Search your package here: --- Current version on the unstable channel: 1.3.0 Current version on the stable/release channel: 1.3.0 <!-- 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 no 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]:


Question: # Value is `"unsupported"` if the platform is not supported. redistArch = flags.getRedistArch hostPlatform.system; <del> allReleases = lists.flatten (builtins.attrValues releaseSets); </del> <ins> preferable = p1: p2: (isSupported p2 -> isSupported p1) && (strings.versionAtLeast p1.version p2.version); </ins> # All the supported packages we can build for our platform. # perSystemReleases :: List Package <del> perSystemReleases = releaseSets.${redistArch} or [ ]; </del> <ins> allReleases = lib.pipe releaseSets [ (builtins.attrValues) (lists.flatten) (builtins.groupBy (p: lib.versions.majorMinor p.version)) (builtins.mapAttrs (_: builtins.sort preferable)) (builtins.mapAttrs (_: lib.take 1)) (builtins.attrValues) (builtins.concatMap lib.trivial.id) ]; </ins> <del> preferable = p1: p2: (isSupported p2 -> isSupported p1) && (strings.versionAtLeast p1.version p2.version); </del> newest = builtins.head (builtins.sort preferable allReleases); # A function which takes the `final` overlay and the `package` being built and returns

should have only eliminated the s and removed some of the platform-based (adding new broken/non-buildable attrs), but instead has changed the actual logic. Since that commit, no longer resolves into but into (note the wrong cuda release), later leading to evaluation errors This currently breaks on Steps to reproduce the behavior: We should probably add some tests for the selection logic as well... A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. 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. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: meta.maintainers = with lib.maintainers; [ obreitwi ]; }; <ins> storage-preview = mkAzExtension rec { pname = "storage-preview"; version = "1.0.0b2"; url = "https://azcliprod.blob.core.windows.net/cli-extensions/storage_preview-${version}-py2.py3-none-any.whl"; sha256 = "2de8fa421622928a308bb70048c3fdf40400bad3b34afd601d0b3afcd8b82764"; description = "Provides a preview for upcoming storage features"; propagatedBuildInputs = with python3Packages; [ azure-core ]; meta.maintainers = with lib.maintainers; [ katexochen ]; }; </ins> # Removed extensions blockchain = throw "The 'blockchain' extension for azure-cli was deprecated upstream"; # Added 2024-04-26 vm-repair = throw "The 'vm-repair' extension for azure-cli was deprecated upstream"; # Added 2024-08-06

Project description Microsoft Azure Command-Line Tools Storage-preview Extension Metadata homepage URL: source URL: license: mit platforms: unix, linux, windows This package is distinct from the package that is already in 24.05 and unstable. It enables azcopy utility in the azure-cli, which is useful for interacting with large storage accounts in Azure.
Code for extension
please give a try and leave some feedback. :)


Question: pytestCheckHook ]; <del> # Don't run tests for Python 2.7 doCheck = !isPy27; </del> <ins> # Don't run tests for Python 2.7 or Darwin # Nearly 50% of the test suite requires local network access # which isn't allowed on sandboxed Darwin builds doCheck = !(isPy27 || stdenv.isDarwin); </ins> pytestFlagsArray = [ "--ignore python2" ]; pythonImportsCheck = [ "httplib2" ];

Describe the bug Tensorflow binary builds don't work on mac os. (neither do the source build, but that's a separate issue) To Reproduce $ nix-build '<nixpkgs' --show-trace -A python37Packages.tensorflow-bin_2 this derivation will be built: /nix/store/cc5p6r864smaf5mm8bqb9dbp6d7jkb3x-python3.7-tensorflow- building '/nix/store/cc5p6r864smaf5mm8bqb9dbp6d7jkb3x-python3.7-tensorflow-'... Sourcing python-recompile-bytecode- Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts- Sourcing python-remove-bin-bytecode- Sourcing wheel setup hook Using wheelUnpackPhase Sourcing pip-install-hook Using pipInstallPhase Sourcing python-imports-check- Using pythonImportsCheckPhase Sourcing python-namespaces-hook unpacking sources Executing wheelUnpackPhase Finished executing wheelUnpackPhase patching sources configuring /private/tmp/nix-build-python3.7-tensorflow- /private/tmp/nix-build-python3.7-tensorflow- Unpacking to: unpacked/tensorflow-2.1.0...OK substitute(): ERROR: file '--replace' does not exist error: --- Error
--------------------------------------------------------------------------- nix-build builder for '/nix/store/cc5p6r864smaf5mm8bqb9dbp6d7jkb3x-python3.7-tensorflow-' failed with exit code 1 host os: multi-user?: sandbox: version: channels(noah): nixpkgs: yaml attribute: module:


Question: pytestCheckHook ]; <del> # Don't run tests for Python 2.7 doCheck = !isPy27; </del> <ins> # Don't run tests for Python 2.7 or Darwin # Nearly 50% of the test suite requires local network access # which isn't allowed on sandboxed Darwin builds doCheck = !(isPy27 || stdenv.isDarwin); </ins> pytestFlagsArray = [ "--ignore python2" ]; pythonImportsCheck = [ "httplib2" ];

Describe the bug tensorflow-bin_2 wants gast-3.2.0 due to but gast has been updated to 3.3.0 so tensorflow refuses to install: To Reproduce Notify maintainers Metadata Maintainer information:
There are also other dependencies that fail the version checks: scipy==1.4.1 and tensorflow-estimator<2.2.0,=2.1.0rc0.
This compiles i'll test it, any feedback appreciated
Got some issues
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Related .
It looks like fixes this.


Question: ] ++ stdenv.lib.optionals (targetPlatform.isDarwin && targetPlatform.isAarch64) [ # fix for iOS: https://www.reddit.com/r/haskell/comments/4ttdz1/building_an_osxi386_to_iosarm64_cross_compiler/d5qvd67/ "--disable-large-address-space" <del> ] ++ stdenv.lib.optional enableDwarf [ "--enable-dwarf-unwind" </del> ]; # Don’t add -liconv to LDFLAGS automatically so that GHC will add it itself.

Our can no longer link executables. For example: This issue is present in current versions of . Compiling and linking works fine with an older revision, say . It looks like this might be related to some change in binutils, maybe?
This is probably from
Yes, it is. came to the same conclusion.
This probably is GHC bug though. Things like gmp and libiconv get their paths hardcoded so this isn't a problem. I would expect the same treatment for elfutils. should provide a arg.
/cc
I guess now I know why there's a patch in branch.
I'll reopen the PR fixing the linking issues.
I opened while we wait on upstream fix.
Which one, from
Yes, although it doesn't help. See
Yes, it would have surprised me a bit if it helped against that symptom -- my patch fixes that DWARF-enabling is skipped completely.
I'm surprised this worked for you back then and now there are linking errors.


Question: doCheck = true; patches = [ <ins> # Remove unrecognized clang debug flags (fetchpatch { url = "https://raw.githubusercontent.com/saiarcot895/chromium-ubuntu-build/663dbfc492fd2f8ba28d9af40fb3b1327e6aa56e/debian/patches/revert-Xclang-instcombine-lower-dbg-declare.patch"; sha256 = "07qp4bjgbwbdrzqslvl2bgbzr3v97b9isbp0539x3lc8cy3h02g1"; }) </ins> ./darwin.patch ./gcc_arm.patch  # Fix building zlib with gcc on aarch64, from https://gist.github.com/Adenilson/d973b6fd96c7709d33ddf08cf1dcb149 ];

Describe the bug Since upgrading v8 to 8.4 () it no longer builds on darwin (at least on my 11.2.3 machine) To Reproduce Steps to reproduce the behavior: Expected behavior A successful v8 build Additional context By default it fails when trying to find the macos sdk, which I patched around with: This then gets as far as , which is avoidable with: which then produces ... and I had to admit defeat. Notify maintainers Metadata Maintainer information:
Hi! Thanks for reporting this! I've opened which I hope fixes this - at least it builds fine for me on 10.15. Please give it a try on your machine too.
Yep, looks good!


Question: <ins> diff --git a/src/qml/qml/qqmlimport.cpp b/src/qml/qml/qqmlimport.cpp index 005db4248..685c5b1b2 100644 --- a/src/qml/qml/qqmlimport.cpp +++ b/src/qml/qml/qqmlimport.cpp @@ -1760,6 +1760,15 @@ QQmlImportDatabase::QQmlImportDatabase(QQmlEngine *e) QString installImportsPath =  QLibraryInfo::location(QLibraryInfo::Qml2ImportsPath); addImportPath(installImportsPath); +    // Add import paths derived from PATH +    const QStringList paths = QFile::decodeName(qgetenv("PATH")).split(':'); +    const QString qmldir = QStringLiteral("../" NIXPKGS_QML2_IMPORT_PREFIX); +    for (const QString &path: paths) { +        if (!path.isEmpty()) { +            addImportPath(QDir::cleanPath(path + QDir::separator() + qmldir)); +        } +    } + // env import paths if (Q_UNLIKELY(!qEnvironmentVariableIsEmpty("QML2_IMPORT_PATH"))) { const QString envImportPath = qEnvironmentVariable("QML2_IMPORT_PATH"); </ins> diff --git a/tools/qmlcachegen/qmlcache.prf b/tools/qmlcachegen/qmlcache.prf index 537eaf62e..e21de58f6 100644 --- a/tools/qmlcachegen/qmlcache.prf

Describe the bug A lot of kde widgets and functions broke after recent updates on the unstable channel (nixos-unstable). Opening the bluetooth widget shows this error message: Other broken widgets/functions includes bluetooth widget, printer widget and desktop (the desktop disappeared resulting in a black background) xsession log: To Reproduce Steps to reproduce the behavior: plasma plasma Expected behavior Plasma widgets should work normally Screenshots A broken widget: ! Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
cc I believe Qt was updated on unstable.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
That was just me asking if it was broken. In my case, The activities and taskbar went down. I am also having the black screen as background. The errors messages I've noticed are: Ocorreu um erro ao carregar o arquivo QML: file:///nix/store/aril5n1mllyyfdgjp23va4wh8d8mbl13-plasma-desktop- module "" is not installed system: host os: multi-user?: sandbox: version: channels(wjjunyor): channels(root): nixpkgs:
The likely culprit (though I'm not super familiar with QML) is that these lines: Are not present in the 5.14 version of the patch:
That sounds about correct to me. All the patches had to be redone for 5.14 so I guess that hunk got dropped
30 minutes into rebuild with it readded, will report if it works :)
Just a recommendation, not sure if it will be helpful to you specifically, but the time to rebuild should be relatively short, and it could be even shorter if you test via running the nixos test interactively
Yeah, that's exactly the command I've been waiting for... it seems to rebuild all dependencies of qt; I'm currently on qtwebengine, which hydra says takes 5 hours :/
It works :)
What do I do now?
the fix was merged into master, so wait for the next update of nixos-unstable (or switch your system to master :)


Question: <del> { stdenv, fetchFromBitbucket, python2Packages }: python2Packages.buildPythonApplication rec { pname = "pygmentex"; version = "0.8"; tlType = "run"; src = fetchFromBitbucket { owner = "romildo"; repo = pname; rev = version; sha256 = "07dnv7hgppy15bda2kcbrlvfqzl6lhza80klc7133dwg8q92hm6m"; }; pythonPath = with python2Packages; [ pygments chardet ]; dontBuild = true; doCheck = false; installPhase = '' mkdir -p $out/bin cp -a pygmentex.py $out/bin mkdir -p $out/scripts/pygmentex ln -s $out/bin/pygmentex.py $out/scripts/pygmentex mkdir -p $out/tex/latex/pygmentex cp -a pygmentex.sty $out/tex/latex/pygmentex mkdir -p $out/doc/latex/pygmentex cp -a README demo.* blueshade.png Factorial.java $out/doc/latex/pygmentex ''; meta = with stdenv.lib; { homepage = https://www.ctan.org/pkg/pygmentex; description = "Auxiliary tool for typesetting code listings in LaTeX documents using Pygments"; longDescription = '' PygmenTeX is a Python-based LaTeX package that can be used for typesetting code listings in a LaTeX document using Pygments. Pygments is a generic syntax highlighter for general use in all kinds of software such as forum systems, wikis or other applications that need to prettify source code. This package installs just the script needed to process code listings snippets extracted from the a LaTeX document by the pygmentex LaTeX package. In order to use it effectivelly the texlive package pygmentex also has to be installed. This can be done by adding pygmentex to texlive.combine. ''; license = licenses.lppl13c; platforms = platforms.unix; maintainers = with maintainers; [ romildo ]; }; } </del>

I have installed the TeXLive package on my system, but its binary script fails to run because: its directory is not found in it does not have an explicitly dependency on it does not have an explicitly dependency on the module for Python 2 cannot be found. Please fix this issues so that the script can be run. (Maybe can take a look at this.)
cc
Well, the first two bullets would be fixed very simply by but I don't yet have framework to add external python dependencies to the scripts.
Nothing new here? A similar problem happens with :
cc Maybe while a good solution is not engineered, a package for without the TeX stuff can be to . It would contain the binary with support for the needed Python dependencies. What do you think?
There aren't any true binaries, are there? It's just python scripts IIRC. But still, what you propose is probably the easiest way to resolve this somehow.
It is just a Python script that depends on the module.
My attempt at it:
So pygmentex works as expected now?
It works! It can be tested by downloading the example document from the distribution on , unzipping the downloaded files, removing the Python script and the LaTeX style class, and than compiling : The result is , with many examples of code listings typeset by Pygments.
OK, then I think we can close this.
Sorry for necromancing this (should I have opened a new issue instead?), but it doesn't "just work" – or needs further documentation on how to use it: The created by building the pygmentex texlive package can not find the module. gives us such an environment, just try running the command from there -The package though provides a executable which works just fine and finds the needed pygments python module. So how to combine these both packages? In particular I ran into this when trying to use the texlive package, as that seems to directly invoke the executable during build. Issue appears on release-18.09
I encountered the same issue, the latex package seems to be working fine tough (and can be used as a replacement)
I have in both with (which provides the style file and a non-functional Python script, because of missing Python dependencies) and (which provides the script). This setup works for me.
I still do not know a way of allowing Python module dependencies for Python scripts installed through .
This is to be fixed in


Question: <del> [ "add-widget-after-content" , "akismet" , "antispam-bee" , "async-javascript" , "breeze" , "code-syntax-block" , "cookie-notice" , "co-authors-plus" , "disable-xml-rpc" , "embed-extended" , "gutenberg" , "hello-dolly" , "hkdev-maintenance-mode" , "jetpack" , "jetpack-lite" , "lightbox-photoswipe" , "login-lockdown" , "mailpoet" , "merge-minify-refresh" , "opengraph" , "simple-login-captcha" , "simple-mastodon-verification" , "static-mail-sender-configurator" , "tc-custom-javascript" , "webp-converter-for-media" , "webp-express" , "wordpress-seo" , "worker" , "wp-change-email-sender" , "wp-fastest-cache" , "wp-gdpr-compliance" , "wp-mail-smtp" , "wp-statistics" , "wp-swiper" , "wp-user-avatars" , "wpforms-lite" ] </del> <ins> { "add-widget-after-content": "gpl3Plus" , "akismet": "gpl2Plus" , "antispam-bee": "gpl2Plus" , "async-javascript": "gpl2Plus" , "breeze": "gpl2Plus" , "code-syntax-block": "gpl2Plus" , "cookie-notice": "mit" , "co-authors-plus": "gpl2Plus" , "disable-xml-rpc": "gpl2Plus" , "embed-extended": "gpl2Plus" , "gutenberg": "gpl2Plus" , "hello-dolly": "gpl2Plus" , "hkdev-maintenance-mode": "gpl2Plus" , "jetpack": "gpl2Plus" , "jetpack-lite": "gpl2Only" , "lightbox-photoswipe": "gpl2Only" , "login-lockdown": "gpl2Plus" , "mailpoet": "gpl3Only" , "merge-minify-refresh": "gpl2Plus" , "opengraph": "asl20" , "simple-login-captcha": "gpl2Plus" , "simple-mastodon-verification": "gpl2Plus" , "static-mail-sender-configurator": "mit" , "tc-custom-javascript": "gpl2Plus" , "webp-converter-for-media": "gpl2Plus" , "webp-express": "gpl3Only" , "wordpress-seo": "gpl3Only" , "worker": "gpl3Plus" , "wp-change-email-sender": "gpl2Plus" , "wp-fastest-cache": "gpl2Plus" , "wp-gdpr-compliance": "gpl2Plus" , "wp-mail-smtp": "gpl3Plus" , "wp-statistics": "gpl3Only" , "wp-swiper": "gpl2Plus" , "wp-user-avatars": "gpl2Plus" , "wpforms-lite": "gpl2Plus" } </ins>

The package with that are automatically fetched carry no license. ` cc
Poking upstream does not seem to yield anything. They did indicate they wouldn't support this use case, so what are you expecting from them?
I talked to the authors of wp4nix and they are happy for new contributions. It would be nice if the wp4nix script would somehow handle license informations, for example by manually defining them. Not quite sure yet how to implement it
If we don't know the licenses to these packages we honestly cannot keep them around. For example, it is absolutely unclear, whether we have a license to even redistribute them. Of course upstream will take patches, but they're not exactly in the same boat we are. I think your attitude towards the whole licensing situation around wp4nix/nc4nix and its resulting packages is alarming.
As written : Fixing this for Wordpress packages and themes (wp4nix) and Nextcloud apps (nc4nix) in a foreseeable time exceeds my skills and competence. Therefore I would like to offer to add a flag to these package sets and remove them for the next release 23.11 if it's not resolved by then.
Couldn't we mark them as unfree so they don't get cached on hydra but people can still use them if they want? Unfortunately it seems like the wordpress plugins repository doesn't seem to provide the license information in an easy manner. And I don't know whether it is stored somewhere else or can even be extracted from the derivation without import-from-derivation.
Actuallly we seem to be safe in theory. claims
In an ideal world, that would hold true, but it is up to the user and distributor to validate the final outcome. I therefore think this situation remains unresolved.


Question: # the wrappers: preFixup = '' gappsWrapperArgs+=( <del> --prefix LD_LIBRARY_PATH ":" "$out/lib/darktable" </del> <ins> --prefix LD_LIBRARY_PATH ":" "$out/lib/darktable:${ocl-icd}/lib" </ins> ) '';

Darktable can make use of OpenCL, but the nix package apparently isn't set up properly to allow this. Run : system: host os: multi-user?: sandbox: version: channels(root): channels(lukas): nixpkgs: OpenCL is set up properly on my system: cc darktable maintainers:
I'd been meaning to fix this for myself for awhile. Should be good now, pending review.
Thanks!
Sorry to revive this, but I am still having this problem in dartable 2.4.4 using intel OpenCL Neo driver. Should ti be already solved? Or the fix is still not present in 2.4.4? Thanks
Disregard (at least partially) my last comment. I was using the snap version in Ubuntu 18.10. Using the deb, OpenCl works. Where should I submit the bug for the snap version?


Question: "tomorrowio" "toon" "totalconnect" <ins> "tplink" </ins> "tplink_omada" "traccar" "trace"

python-kasa recently updated to 0.6.x from 0.5.x. The home-assistant project does not yet support 0.6.x, as a result kasa functionality is degraded. Using HomeAsisstant from latest nixpkgs, attempt to get emeter data from kasa devices. I reported this issue upstream and they advised on the version issue. There are more logs visible there. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I guess that if we would run the unit tests then the issue with 0.6.0 would have been detected.


Question: maintainers = with lib.maintainers; [ qyliss ]; }; <del> } </del> <ins> } // (args.argsOverride or { }) </ins>

Mainline / hardened / testing / ... kernels can be painlessly modified via : Sadly, this does not work with a bunch of other kernel variants: All kernels should honor I am not entirely sure how dynamic binding is implemented in kernel stuff, however slightly changing xanmod parts this way seems to fix : zen and lqx look similar to xanmod, no idea about libre Pinging people who seem to update affected packages often Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
same underlying issue as it seems
Can confirm that this patch fix the issue for zen and lqx kernels:
have you submitted these changes as a PR that I can review?
sorry for the late response. I created a new PR with this changes.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:


Question: metapixel = callPackage ../tools/graphics/metapixel { }; <ins> yabridge = callPackage ../tools/audio/yabridge { wine = wineWowPackages.minimal; }; yabridgectl = callPackage ../tools/audio/yabridgectl { }; </ins> ### APPLICATIONS/TERMINAL-EMULATORS alacritty = callPackage ../applications/terminal-emulators/alacritty {

Project description Yet Another way to use Windows VST plugins on Linux. Yabridge seamlessly supports using both 32-bit and 64-bit Windows VST2 and VST3 plugins in a 64-bit Linux VST host as if they were native VST2 and VST3 plugins, with optional support for plugin groups to enable inter-plugin communication for VST2 plugins and quick startup times. Its modern concurrent architecture and focus on transparency allows yabridge to be both fast and highly compatible, while also staying easy to debug and maintain. If I understand correctly, this provides similar functionality to the airwave package. I think the big plus to this package though is that it emulates as if they were native which means the build process doesn't need to require the user to go to the steinberg site and download the VST SDK (as airwave currently does). I used this on Arch with Reaper and it was extremely easy to get going. I had a much easier time using yabridge than trying to get carla set up and running. There are multiple AUR packages for installing from source or just pulling in the binaries. I've tried to package this myself but it's just a bit beyond my means. I think that if someone is more familiar with packaging wine related binaries or compiling with meson from source this would be a quick win. homepage URL: source URL: license: GPL 3.0 platforms: linux
I probably won't have time today, but I can take a look at this later. I'm pretty familiar with the nixpkgs wine build, and I've worked with the ZynAddSubFx build to add support for the Zyn-Fusion ui.
Amazing. I was able to take your PR and get Upright Piano working with Reaper as well. Thank you so much for the quick turn around, I really appreciate it.
Hi! I don't use NixOS myself, but if it helps, there's one person in the yabridge Discord currently using yabridge's master branch with NixOS. And I've also ran into another Nix build definition on GitHub in the past (but that one's pretty outdated by now).
I've just released with a lot of important new features, fixes and improvements including the first ever Linux <-Windows VST3 plugin bridge.


Question: metapixel = callPackage ../tools/graphics/metapixel { }; <ins> yabridge = callPackage ../tools/audio/yabridge { wine = wineWowPackages.minimal; }; yabridgectl = callPackage ../tools/audio/yabridgectl { }; </ins> ### APPLICATIONS/TERMINAL-EMULATORS alacritty = callPackage ../applications/terminal-emulators/alacritty {

I saw that the package created by for yabridge 2.2.1 has not been merged yet, but please let me know if you want to update the yabridge and yabridgectl packages for yabridge 3.0.0 and need any help! One additional dependency is now a patched version of the VST3 SDK which is patched to compile under winegcc and with support for Meson. I'm not quite sure how Nix packaging handles those things.
Thanks, I have it building right now. I'm just testing out vst3 plugins right now :smile:
:cry: For some reason neither the vst2 or vst3 plugins are working, even though they get synced. I think it might be an issue with my system installed wine. I'll submit my changes anyway so other people can test it out.
So they are found but yabridge fails to load them? Which Wine are your derivations using?
You can try running manually to see if that is the issue. A plain call should print: And should print:
I'm able to sync them with yabridgectl, but they fail to load in Reaper. I'm using (currently version 6.0) to build yabridge, but I have a custom build of wine staging 6.0 currently installed. seems to be working fine:
That indeed seems to work as expected, that's great news! If you start REAPER with and then take a look at after trying to scan/load a plugin then you'll probably be able to figure out what's wrong very quickly.
Hmm, apparently the path to the VST host is too long :stuckouttongue:
Huh I can't think of from the top of my head what would be throwing such an exception. That message printed after comes from a try-catch around the entire plugin startup that catches and prints any . Windows (and thus Wine, because it has to be compatible haha) has a path name limit of 255 characters, but none of those paths sound like they should come close to that.
Yeah, sorry. It was just a problem with my home environment. I was trying to test it without installing because I lost the nixpkgs commit I used to generate my home-manager environment.


Question: metapixel = callPackage ../tools/graphics/metapixel { }; <ins> yabridge = callPackage ../tools/audio/yabridge { wine = wineWowPackages.minimal; }; yabridgectl = callPackage ../tools/audio/yabridgectl { }; </ins> ### APPLICATIONS/TERMINAL-EMULATORS alacritty = callPackage ../applications/terminal-emulators/alacritty {

REAPER was just loading the old 2.2.1 yabridge- :woman_facepalming: I just finished rebuilding my home environment with a new nixpkgs commit, and it's working now :smile: .


Question: stdenv.mkDerivation rec { name = "gnome-desktop-${version}"; <del> version = "3.30.2.1"; </del> <ins> version = "3.30.2.2"; </ins> outputs = [ "out" "dev" "devdoc" ]; src = fetchurl { url = "mirror://gnome/sources/gnome-desktop/${stdenv.lib.versions.majorMinor version}/${name}.tar.xz"; <del> sha256 = "07s95fpfl3kjq51yxbrx6q87w812pq6bl0xdn0zzyi6qvg33m00v"; </del> <ins> sha256 = "02ksmq2h4jjvjalp5x6d6v36qnp1h66qxwv2gl7kbx7dxqcp6ys3"; </ins> }; enableParallelBuilding = true;

, (nixos-19.03) Scanned versions: nixos-19.03: . May contain false positives.


Question: "--with-unsigned-addon-scopes=app,system" ]; <ins> extraPostPatch = '' # Fix .desktop files for PWAs generated by Floorp; they hardcode /usr/bin # https://github.com/NixOS/nixpkgs/issues/314115 substituteInPlace floorp/browser/base/content/modules/ssb/LinuxSupport.mjs  --replace-fail /usr/bin/floorp floorp ''; </ins> updateScript = ./update.sh; meta = {

Steps to reproduce the behavior: floorp Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi, Please elaborate - there does not seem to be any actual build failure here. What's the actual error? Are you sure your build machine has enough resources? A browser build is pretty demanding and can take even multiple hours on low-to-mid-end machines. Can you please also post the complete derivation log, as obtained using ?
I have the same problem (with floorp and floorp-unwrapped). Here’s the error: ! That feature was removed in February, so either update the qcms crate to 0.3 or downgrade the rust compiler version (1.76 could work).
is the log in the link not enough ?
Oh, I see, Github just truncated the file in the UI. That's what you get from hosting projects on crappy, proprietary software .. Pointing out the exact error too from the get-go would have been helpful in any case. Anyway - seems it broke with a recent rustc upgrade in nixpkgs. This is already fixed with 11.14.1, as it updates the firefox base source. See .
Okay, I will host my opengist instance for the next time ;) Thanks for your prompt response, waiting for your pr to be merged.
Any ETA on the PR merge?
Floorp is now in version 11.14.1 on unstable.


Question: "--with-unsigned-addon-scopes=app,system" ]; <ins> extraPostPatch = '' # Fix .desktop files for PWAs generated by Floorp; they hardcode /usr/bin # https://github.com/NixOS/nixpkgs/issues/314115 substituteInPlace floorp/browser/base/content/modules/ssb/LinuxSupport.mjs  --replace-fail /usr/bin/floorp floorp ''; </ins> updateScript = ./update.sh; meta = {

When installing a PWA using the Floorp browser (experimental toggle in settings), the installed desktop file uses /usr/bin/floorp as the path for the browser to run said PWA. Steps to reproduce the behavior: Floorp experimental PWAs in settings a PWA, e.g. Github or Excalidraw the newly spawned PWA window to launch the same PWA from your DE's application launcher The PWA opens. ! , using flakes, installed via <!-- 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 reporting! As well as the upstream report! I can look into it what we can do as I get time. But as I'm the only maintainer for Floorp and currently pretty much out of time due to university and $dayjob, I cannot promise any timeline unfortunately. But happy to review patches, of course, if you'd like to fix it yourself. Can you provide such a generated file for further investigation?
sure, one such generated desktop file with the example of excalidraw can be found (github doesn't allow for drag and drop of .desktop files)
Hello! I don't have experience maintaining and modifying large packages like Firefox (floorp), and I currently don't have much free time. However, I've discovered how floorp generates the .desktop file for PWA applications: Maybe it will be helpful to you.
Thanks, that is indeed helpful! Should be relatively easy patchable by us then, from the looks of it.
upstream has and now it will use the path it was in at the time of creating the PWA. It may not be too big of an issue if what they say about fixing it in the next version is true but now the patching will probably fail.


Question: ${attrsToSection def.bondConfig} ''} <ins> ${optionalString (def.wireguardConfig != { }) '' [WireGuard] ${attrsToSection def.wireguardConfig} ''} ${flip concatMapStrings def.wireguardPeers (x: '' [WireGuardPeer] ${attrsToSection x.wireguardPeerConfig} '')} </ins> ${def.extraConfig} ''; };

This configuration: If you poke around in the configuration I linked, you should see that I disable NetworkManager and use a static configuration for my main NIC. I can't think of anything special in my config or with this machine that would affect my usage of Wireguard, but I'm also new to using Wireguard. I'm currently on nixpkgs with a few of my own commits on top of . Please run and paste the results.
It doesn't seem happy when already exists... I have done two things, both of which were necessary, to resolve this: the link manually () sure the path to the private key exists (if not, you get a different failure in the journal, with failing). (It's possible that fixing the private key path and rebooting would have been sufficient). I'm leaving this open for two reasons: user should receive a better error message in both cases. that we're in NixOS, we should assume full control of the interface and just re-configure it, instead of failing in the setup script.
I ran into this issue after trying to debug my wireguard setup. My setup is essentialy identical and I get the same error message. Running the start script that is causing the error results in this output. The offending 2 lines are .
I had to go one step further than deleting the interface. I needed to stop the via then redeploy configuration. But this solved it for me. Nixos should handle this much more gracefully.
I had to remove the routes with etc.
The command is . You can build it in your conf as pre-setup command, but it has the nasty side effect that it possible interferes with other connections.
I am still running into this issue.


Question: GITOLITE_RC_DEFAULT = "${rcDir}/gitolite.rc.default"; }; <del> serviceConfig = { Type = "oneshot"; User = cfg.user; Group = cfg.group; WorkingDirectory = "~"; RemainAfterExit = true; }; </del> <ins> serviceConfig = mkMerge [ (mkIf (cfg.dataDir == "/var/lib/gitolite") { StateDirectory = "gitolite gitolite/.gitolite gitolite/.gitolite/logs"; StateDirectoryMode = "0750"; }) { Type = "oneshot"; User = cfg.user; Group = cfg.group; WorkingDirectory = "~"; RemainAfterExit = true; } ]; </ins> path = [ pkgs.gitolite pkgs.git pkgs.perl pkgs.bash pkgs.diffutils config.programs.ssh.package ]; script =

Describe the bug My server uses an encrypted filesystem /data that I have to mount manually after reboot. Gitolite is configured to use /data/gitolite. I have configured gitolite-init to only run once /data is mounted. Mounting of /data always fails, as gitolite uses to generate directories and thus the mountpoint is not empty. Manual cleanup is required every time. Expected behavior Gitolite should create its directories in gitolite-init.service. Additional context systemd-tmpfiles-setup.service runs before the system is fully initialized, so I cannot delay that service. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
I'll try to address this in the next few days.


Question: "-DENABLE_SYSTEM_GMIC:BOOL=ON" ]; <del> patches = [ # NOTE: this should be removed when a new version is released. (fetchpatch { name = "fix_filter_translation_scripts.patch"; url = "https://github.com/c-koi/gmic-qt/commit/ccb9f29eda239d0c80663593cd90a6548c935b39.patch"; sha256 = "sha256-OzuJ6yGuDJweQ+1uin/pmJqZV79bN9E1Zuo+0iciwzg="; }) ]; </del> postPatch = '' patchShebangs  translations/filters/csv2ts.sh

Steps to reproduce the behavior: gmic in a nix shell using the unstable channel Add any other context about the problem here.
Will be fixed by
Thanks! Note that it makes darktable fail to build.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:


Question: stdenv.mkDerivation rec { pname = "vulkan-loader"; <del> version = "1.2.189.1"; </del> <ins> version = "1.2.198.0"; </ins> src = (assert version == vulkan-headers.version; fetchFromGitHub { owner = "KhronosGroup"; repo = "Vulkan-Loader"; rev = "sdk-${version}"; <del> sha256 = "1745fdzi0n5qj2s41q6z1y52cq8pwswvh1a32d3n7kl6bhksagp6"; </del> <ins> sha256 = "sha256-k3eCdZqCjFxpKa0pZ0K4XcORxdSOlr1dFa7C3Qzi04Y="; </ins> }); nativeBuildInputs = [ cmake pkg-config ];

name: All packages in current version: 1.2.189.1 desired version: 1.2.200 maintainers: Please tag this issue in your PR.


Question: <del> source 'https://rubygems.org' gem 'chef-dk', '4.13.3' gem 'pry' gem 'test-kitchen' gem 'inspec' gem 'kitchen-inspec' gem 'kitchen-vagrant' gem 'berkshelf' gem 'chef-vault' gem 'foodcritic' gem 'ohai' gem 'rubocop' gem 'knife-spork' gem 'fauxhai-ng' gem 'chefspec' gem 'chef-provisioning' </del>

ChefDK is deprecated and no longer maintained by Chef. This package is currently maintained by and I believe ChefDK should be dropped and replaced by Chef Workstation (see issue ). This has been deprecated since 2021.


Question: free = true; }; <ins> fairsource09 = { fullName = "Fair Source License, version 0.9"; url = "https://fair.io/v0.9.txt"; free = false; redistributable = true; }; </ins> issl = { fullName = "Intel Simplified Software License"; url = "https://software.intel.com/en-us/license/intel-simplified-software-license";

Project description <!-- Describe the project a little: --Metadata homepage URL: source URL: license: platforms: darwin


Question: sha256 = "sha256-Ha0bIh3SYMhA28YXQ//Loaz9J1lTJAzjTx8eK3AqUjM="; }; <del> patches = [ ./option-debugging.patch ]; </del> <ins> patches = [ ./option-debugging.patch # ffmpeg 6 fix https://github.com/cmus/cmus/pull/1254/ (fetchpatch { url = "https://github.com/cmus/cmus/commit/07b368ff1500e1d2957cad61ced982fa10243fbc.patch"; hash = "sha256-5gsz3q8R9FPobHoLj8BQPsa9s4ULEA9w2VQR+gmpmgA="; }) ]; </ins> nativeBuildInputs = [ pkg-config ]; buildInputs = [ ncurses ]

Steps to reproduce the behavior: cmus on current (). Full logs: I haven't updated in a while, so I'm not sure where this failure starts. Nothing has changed in the cmus package; it must be a change in dependencies. system: host os: multi-user?: sandbox: version: channels(root): channels(jamesw): nixpkgs:
cmus started failing somewhere between (good) and (bad). I don't have the hundreds of gigabytes of RAM that would allow me to do a bisection between those, so I'll leave that to someone else.
Manually going through it suggests as a possible culprit. I have no idea what that commit does, though, yet.
the issue is bump of ffmpeg to 6, i am about to push a fix


Question: octoprint = callPackage ../applications/misc/octoprint { }; <ins> oculante = callPackage ../applications/graphics/oculante { }; </ins> ocr-a = callPackage ../data/fonts/ocr-a {}; ocrad = callPackage ../applications/graphics/ocrad { };

Project description Oculante's vision is to be a fast, unobtrusive, portable image viewer with wide image format support, offering image analysis and basic editing tools. Metadata homepage URL: source URL: license: MIT platforms: cross


Question: stdenv.mkDerivation rec { pname = "cardinal"; <del> version = "23.09"; </del> <ins> version = "23.10"; </ins> src = fetchurl { url = "https://github.com/DISTRHO/Cardinal/releases/download/${version}/cardinal+deps-${version}.tar.xz"; <del> hash = "sha256-q42ry47y4tTkUbejv6iN5jXcadXSSTPQ3omhMUevfqU="; </del> <ins> hash = "sha256-6Wt2sC7vdrz2Fkl08bNLfnGu+pAV7b5lZUmsx1wtJRE="; </ins> }; prePatch = ''

Package name: cardinal Latest released version: 23.10 Current version on the unstable channel: 23.09 Current version on the stable/release channel: 22.12 Notify maintainers Note for maintainers: Please tag this issue in your PR.


Question: inherit cc shell libc_bin libc_dev libc_lib binutils_bin coreutils_bin; gnugrep_bin = if nativeTools then "" else gnugrep; <ins> binPrefix = prefix; </ins> passthru = { inherit libc nativeTools nativeLibc nativePrefix isGNU isClang default_cxx_stdlib_compile

Optipng crashes with a segmentation fault on current as of . points to the library used to throw/catch exceptions. relevant source: Automatic points to being the first bad revision. However, I don't have enough knowledge of this piece of nix to understand why it causes optipng to fail in the . System: nixos-master Nix version: 1.11.11 Nixpkgs version: Sandboxing enabled: yes CC
Reading into the causing commit's comments made me try which seems to work around the issue. However, I'm hesitant to commit this as a fix without understanding the issue here.
So some packages use the C compiler instead of linker directly to link. Nixpkgs's cc-wrapper is aware of this, for example, with separate and environment variables. Classic make builtin rules however only have , , , and , so then either in a configure script or make itself they seem to default to , but manually specifying breaks this. Manually specifying , however, avoids that pitfall, and, unlike , will also work for cross compilation.
Here's a blurb from optipng's script: If I understand your comment, it looks like optipng's build system is doing precisely what you describe: So when isn't set, it defaults to configuring the such that it uses as the linker, and I suppose the theory is that they depend on behavior available when invoking through e.g. (though I don't know precisely what that may be). It would seem reasonable take the (on a per package basis) approach as a solution. I think this can safely be considered a bug in the upstream packages' build systems.
Probably the use of to pass actual ld flags, e.g. .
I implemented the workaround in . Feel free to reopen this if you don't think the fix to be adequate.


Question: inherit cc shell libc_bin libc_dev libc_lib binutils_bin coreutils_bin; gnugrep_bin = if nativeTools then "" else gnugrep; <ins> binPrefix = prefix; </ins> passthru = { inherit libc nativeTools nativeLibc nativePrefix isGNU isClang default_cxx_stdlib_compile

gcc5 and the dependant gfortran5 packages are failing as of 31 July Failures: ] ] Building either package using or fails. System: (MacOS 10.11.6 and MacOS 10.12.6, both nix-multiuser install) Nix version: (1.11.13) Nixpkgs version: (17.09pre-git) Sandboxing enabled: (relaxed)
has been looking into this but it seems pretty mysterious so far
git-bisect is pretty neat
cc
This is also needed to fix things that depend on gcc


Question: ${cfg.sleep.extraConfig} ''; <del> "systemd/system-generators" = { source = hooks "generators" cfg.generators; }; "systemd/system-shutdown" = { source = hooks "shutdown" cfg.shutdown; }; </del> <ins> "systemd/user-generators" = { source = hooks "user-generators" cfg.user.generators; }; "systemd/system-generators" = { source = hooks "system-generators" cfg.generators; }; "systemd/system-shutdown" = { source = hooks "system-shutdown" cfg.shutdown; }; </ins> }); services.dbus.enable = true;

Unable to use Podman's quadlets feature for a user, since the service unit files are not generated by systemd. Steps to reproduce the behavior: a quadlet file in (say, ) . Systemd says that no unit files were found. Caddy service should have been generated and its status displayed. This issue is caused by not symlinking the provided by the package to . Does not occur at the system level, since is already symlinked to Fix: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Confirmed the quadlet systemd user generator is not found in /etc/systemd. I'm gonna take this one and try to come up with a fix in NixOS module.


Question: buildGoModule rec { pname = "podman-tui"; <del> version = "0.18.0"; </del> <ins> version = "1.0.0"; </ins> src = fetchFromGitHub { owner = "containers"; repo = "podman-tui"; rev = "v${version}"; <del> hash = "sha256-T2hiCRoZqdbcB36Tpy597j7Hc1yeR2MijQbuheENfuA="; </del> <ins> hash = "sha256-sJaiZJeT0oUAnSg9Kv8uMp1XoumumC3LB77lelmwSgw="; </ins> }; vendorHash = null;

Package name: podman-tui Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.18.0 Current version on the stable/release channel: 0.12.0 <!-- 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. --I attempted to update this package myself and create a PR, however, there appears to be a major changes to how this package is built that are outside my ability to address. Attempting to build the package after a , both with and without the changes in , results in the following build log: Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: description = ".NET C# and Visual Basic compiler"; homepage = "https://github.com/dotnet/roslyn"; mainProgram = "csc"; <del> platforms = platforms.linux; </del> license = licenses.mit; maintainers = with maintainers; [ corngood ]; };

Steps to reproduce the behavior: msbuild Trying to build msbuild on a mac 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.


Question: <ins> { lib, fetchFromGitHub, rustPlatform, python3Packages, libiconv, }: python3Packages.buildPythonApplication rec { pname = "granian"; version = "1.5.2"; pyproject = true; src = fetchFromGitHub { owner = "emmett-framework"; repo = "granian"; rev = "v${version}"; hash = "sha256-3kwdPLOkKKSY1w42av3ejarrRKNtai8KB80ZrujSjPo="; }; cargoDeps = rustPlatform.importCargoLock { lockFile = ./Cargo.lock; outputHashes = { "pyo3-log-0.11.0" = "sha256-UU8064vM7cf20lwfifyPC205CY4tIgif0slDz/Pjf9Q="; }; }; nativeBuildInputs = with rustPlatform; [ cargoSetupHook maturinBuildHook ]; buildInputs = [ libiconv ]; dependencies = [ python3Packages.uvloop python3Packages.click ]; meta = { description = "Rust HTTP server for Python ASGI/WSGI/RSGI applications"; homepage = "https://github.com/emmett-framework/granian"; license = lib.licenses.bsd3; mainProgram = "granian"; maintainers = with lib.maintainers; [ lucastso10 ]; platforms = lib.platforms.unix; }; } </ins>

Project description Granian is a Rust HTTP server for Python ASGI/WSGI/RSGI applications. It fulfills a similar purpose as daphne, gunicorn, uvicorn or uwsgi, but . Metadata homepage URL: source URL: license: bsd3 platforms: unix Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: <del> { lib, stdenv, fetchFromGitHub, gettext, makeWrapper, tcl, which </del> <ins> { lib, stdenv, fetchFromGitHub, fetchpatch, gettext, makeWrapper, tcl, which </ins> , ncurses, perl , cyrus_sasl, gss, gpgme, libkrb5, libidn2, libxml2, notmuch, openssl , lua, lmdb, libxslt, docbook_xsl, docbook_xml_dtd_42, w3m, mailcap, sqlite, zlib, lndir , pkg-config, zstd, enableZstd ? true, enableMixmaster ? false, enableLua ? false

Steps to reproduce the behavior: on darwin aarch64 see Since neomutt is broken on darwin-aarch64. See the CI output: Tangent: is it normal that a failing CI build wasn't marked as a failed check, but rather just ignored? <!-- 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.
Broken on Darwin x86-64 as well.
seems to work — I can't tell whether they are running the tests, though, or not. Here are the failing tests.
Looking at the latest comment on the already closed issue here: This issue could use some love. Neomutt is broken on MacOS and it looks like it's the derivation, not upstream.
I can't install neomutt on MacOS with home-manager too
The failing tests were disabled upstream in . I tried simply upgrading to HEAD with the following patch, and the succeeded (darwin-aarch64):
( That's a different bug which you should probably raise separately.)
Unfortunately, the latest fix didn't work for my Intel Mac, some tests are failing for me. I tested using because I didn't know how to do overrides from the CLI
Yes, the failure on should be a separate bug (and could probably be fixed by putting into ).