jiebi/CodeConvo huggingface dataset:
Change:
gsettings-desktop-schemas gtk3 gnome3.gnome-desktop <ins> gnome3.gnome-settings-daemon # schemas needed for settings api (fonts, etc) </ins> ]; meta = with stdenv.lib; {

Discussion:
Describe the bug I noticed that enabling some XDG options, it breaks my GTK fonts: Then when working on firefox and pipewire-0.3 patching today, I noticed this in repo: It looks like we might want to fix this in nixpkgs.
Right, looks like it is required since at least 1.5.0:
I still experience font hinting issues when enabling on . I'm using sway. Is the option only supported when actually running a GNOME environment?
I haven't had issues in Sway since this was merged:
Ah, I was missing in extraPortals, after I that the hinting went back to being fine. Screensharing also work now o/
I do not know if my config has anything special, but with current nixos-unstable (21.03pre259928. (Okapi)) I do experience the issue. Even stranger: show no nor portal running, only plain processes. I am a bit lost here. Just reverted for now, but I am far from making work.
Sorry to read that Since September 2020 the overlay is obsolete, that is, all patches that i had copied in there, are present and meanwhile updated/outdated in master. I updated the to reflect that, also links to the resources i use to debug problems with the setup. Also, it to add to
Investigating further. It seems that if I and restart dbus afterwards it works correctly. AFAIU the challenge is to get xdg-desktop-portal and co. to have access to env vars defined by sway. Adding does not work because at that time dbus is already started when sway starts. My workflow is to tty and get a zsh login shell in that shell. logind starts dbus on login. Too early for me. Another option seems to use . This should work for the portals that have not yet been activated. But if your sway config starts applications (mine starts firefox and waybar) then it gets racy. Will report here my attempts. Could you explain how you are running sway ? I cannot believe it only fails for me.
sure. It is nearly the same as you do manually, with the difference that i do and so replace the shell, if i understand correctly.
Hmmm. I do not see what it could possibly change.

Still, yet another thing to test :-D
I don't know maybe you need both of those at the end of your like stated in I just did not mention it because for it did not seem to be required.
Well, I have discovered that my setup was "polluted" by the gdm display-manager that I kept in another tty for easy switching to X11 when I needed advanced screencasting in Teams :-). This gdm spawned its own dbus, and mingled in various ways with nixos config. I have to test again everything. I guess it was also responsible for starting the graphical- I wonder who is responsible for starting dbus in your setup. I guess it is socket-activated. Just checked. It is indeed. That also explains why exec systemctl --user import-environment works. It is a bit unfortunate that you cannot start gdm besides sway. I will have to figure out how to install it without starting it at boot. Or just make screencasting work in sway and forget X11 forever :tada:
Change:
, rustPlatform , stdenv , stdenvNoCC <del> , webkitgtk </del> <ins> , webkitgtk_4_1 </ins> }: let <del> esbuild-20-2 = let version = "0.20.2"; </del> <ins> cargo-tauri_2 = let version = "2.0.0-rc.3"; src = fetchFromGitHub { owner = "tauri-apps"; repo = "tauri"; rev = "tauri-v${version}"; hash = "sha256-PV8m/MzYgbY4Hv71dZrqVbrxmxrwFfOAraLJIaQk6FQ="; }; in cargo-tauri.overrideAttrs (drv: { inherit src version; cargoDeps = drv.cargoDeps.overrideAttrs (lib.const { inherit src; name = "tauri-${version}-vendor.tar.gz"; outputHash = "sha256-BrIH0JkGMp68O+4B+0g7X3lSdNSPXo+otlBgslCzPZE="; }); }); esbuild_21-5 = let version = "0.21.5"; </ins> in esbuild.override { buildGoModule = args: buildGoModule (args // {

Discussion:
Steps to reproduce the behavior: Attempt to build surrealist version 2.0.6 on NixOS 24.11. The build fails during the build phase. I reported a similar issue here: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
another failure
Change:
<ins> --- a/tools/Makefile.in +++ b/tools/Makefile.in @@ -586,7 +586,7 @@ gamma4scanimage$(EXEEXT): $(gamma4scanimage_OBJECTS) $(gamma4scanimage_DEPENDENC sane-desc$(EXEEXT): $(sane_desc_OBJECTS) $(sane_desc_DEPENDENCIES) $(EXTRA_sane_desc_DEPENDENCIES) @rm -f sane-desc$(EXEEXT) -	$(AM_V_CCLD)$(LINK) $(sane_desc_OBJECTS) $(sane_desc_LDADD) $(LIBS) +	cc -I. sane-desc.c -I../include ../sanei/sanei_config.c ../sanei/sanei_init_debug.c ../sanei/sanei_constrain_value.c -o $@ sane-find-scanner$(EXEEXT): $(sane_find_scanner_OBJECTS) $(sane_find_scanner_DEPENDENCIES) $(EXTRA_sane_find_scanner_DEPENDENCIES) @rm -f sane-find-scanner$(EXEEXT) </ins>

Discussion:
My Canon CanoScan LiDE 20 does not work on NixOS. I wrote a minimal SANE config dir to reproduce: Invocation: ` Reveals: <details</detailsImportant part: It's failing because it's trying to write a lock file into .
I suspect the code involved is this: Looks like the packaging overrode the string, putting the nix output store path prefix in front; that seems wrong.
Grepping further: Indeed, the build logs show the wrong path:
Probably the nix build sets to a store path. Fixing it via: Other nixpkgs packages also set . Maybe nixpkgs should do this automatically for all packages? Probably is what puts the nix store path in. However, trying the workaround fails the build at step:
In PR I made an option to set the package without mass rebuilds. With that, the following workarounds make the scanner work: Now I can scan.
I'd be happy if somebody could pick up the task to pass a proper lock dir and ensure it exists in NixOS.
Another option is to disable locking entirely. Putting this in my nixos config is working for me:
Yes, that's what's mentioned in the comment just above:
It seems only scanners covered by SANE's driver are affected by this, as only those use locks as per : Note this driver, even though called , handles also many other vendors' scanners, including some Canon, Epson, HP, and others.
I think that's the reason it isn't being done by default, because upstream build systems try to create directories inside the runtime state directory at install time. So we're trading build time successes for runtime failures. A similar situation exists with /etc (sysconfdir), where I think the default should be /etc, but nixpkgs uses $prefix/etc because it has a higher success rate at build time.
With the workaround mentioned in I'm able to scan on a CanonScan Lide 25 using the sane-plustek backend. Would be great to have this properly fixed.
Using a Canon N670U (also covered by ) I ran into the same issue and resolved it with workaround Proper fix would be highly appreciated though.
Please give a try, it should fix the issue
Change:
let perlPackages = perl538Packages; <ins> binPath = lib.makeBinPath ([ lame flac faad2 sox wavpack ] ++ (lib.optional stdenv.isLinux monkeysAudio)); libPath = lib.makeLibraryPath [ zlib stdenv.cc.cc.lib ]; </ins> in perlPackages.buildPerlPackage rec { pname = "slimserver";

Discussion:
I try to use slimserver with the tidal plugin. Slimserver looks normally (e.g the webui works), but it spams the log with and squeezelite isn't outputting any audio when i try to play something (without any error logs) Steps to reproduce the behavior: and run slimserver the tidal plugin and run squeezelite to play something I expect listening to audio but it just keeps silent. The logspam only starts as soon as i try to play something. But then it never stops even if i disconnect all players. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Which nixos release or branch are you on? Can you try using a radio station or local media as an alternative to the tidal plugin?
I'm on unstable from today. Radio and local media work fine.
I am also encountering this issue with the qobuz plugin. Also I haven't figured out why, but indexing doesn't work for me, but if i try to play a local file (finding it via the file system option) I also get similar errors complaining about not being found etc.
When I went to spin this up I discovered that library importing was failing with the same error. After some troubleshooting another vendored version of this library was found. Cleaning this up and upgrading AudioScan to the slimserver fork resolved library importing, and I verified Qobuz is also playing. and can you test this PR to see if it fixes your issues? Thanks! Feel free to comment or reopen if still having this issue.
i just tested the pr and can confirm that the tidal works fine now. Thank you very much!
Change:
# and upstream has stopped tagging releases since 3.41.0 src = fetchPypi { inherit pname version; <del> hash = "sha256-617zutFhS8NGO4+fcALH8aKbk+reGC65DNWKVVKiWEw="; </del> <ins> hash = "sha256-17KT0b9kBO+xLgIgxfpwjETDoRM4aTJPlJv7HjkJXjo="; </ins> }; # fix packaging.ParserSyntaxError, which can't handle comments

Discussion:
Steps to reproduce the behavior: Gradio / Gradio Client <!-- 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]:
fix for py311
Change:
, buildEnv, bundler, bundix , libiconv, libobjc, libunwind, Foundation , makeBinaryWrapper, buildRubyGem, defaultGemConfig <del> , baseRuby ? buildPackages.ruby_3_1.override { </del> <ins> , baseRuby ? buildPackages.ruby.override { </ins> docSupport = false; rubygemsSupport = false; }

Discussion:
So we'll have an EOL for a few months on 22.11, which isn't ideal, but we really shouldn't go into 23.05 like that. Also, does not support , which is why I noticed this when looking into stuff for
Ruby 2.7 support status ended yesterday.
The default is with the merge of :partyingface: Thanks for taking care of this Now… do we want to mark as EOL e.g. through ?
Change:
type = types.lines; default = ""; description = '' <del> Extra configuration text appended to <filename>ssh_config</filename>. </del> <ins> Extra configuration text prepended to <filename>ssh_config</filename>. Other generated options will be added after a <code>Host *</code> pattern. </ins> See <citerefentry><refentrytitle>ssh_config</refentrytitle><manvolnum>5</manvolnum></citerefentry> for help. '';

Discussion:
The following setting has no effect: This is because the is set globally depending on whether the host is IPv6 capable . This line should be set after , otherwise it is not possible to override it for a specific host (first match wins). Perhaps the other options should be moved as well? Alternatively, the line could only be set if it is not , as that is the default. However, I don't think that is the right solution. Insert the above snippet into , and try to connect to an IPv4 only server from an IPv6-capable client. Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): channels(kai): nixpkgs:
This server is probably a bit weird in that it has both IPv6/4 DNS entries, but only accepts SSH connections over IPv4, so it's an odd edge case.
Change:
url = "mirror://apache/cassandra/${version}/apache-cassandra-${version}-bin.tar.gz"; }; <del> nativeBuildInputs = [ makeWrapper ]; </del> <ins> pythonPath = with python311Packages; [ cassandra-driver ]; nativeBuildInputs = [ python311Packages.wrapPython ]; buildInputs = [ python311Packages.python ] ++ pythonPath; </ins> installPhase = '' runHook preInstall

Discussion:
The CLI tool provided by the package throws a Python related error when executed. Steps to reproduce the behavior: I expect the CLI tool to run without throwing a Python error I'm testing with nixpkgs unstable. <!-- 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]:
any chance you could have a look at the problem?
CC
Suggest you use for instead of plain , and supply the in its pythonpath - grep nixpkgs to see usage examples. Though I suggest taking note of the dependency footprint the package will add to this.
Thanks. I have created a PR with a fix that work locally for me. I won't be available for the next weeks so feel free to improve and merge it without me if you have time.
Change:
sha256 = "fe046481b793b592334749249620fce8a463f4c46b394ff744645975465d677b"; }; <ins> postPatch = '' substituteInPlace setup.py  --replace "opencv-python" "" ''; </ins> propagatedBuildInputs = [ matplotlib numpy

Discussion:
Describe the bug wxPython40, , does not build there likely because it uses wxGTK rather than this prevents kicad from being built on darwin To Reproduce Steps to reproduce the behavior: darwin, Expected behavior wxPython40 to build on darwin and be usable by kicad there Additional context i maintain the kicad package and Notify maintainers while there are no listed maintainers for this package it was initially contributed by (if you already investigated after the kicad PR ping, nothing relevant changed since) and has a fair amount of contributions by Maintainer information:
Hi I don't have/use mac but happy to answer any wxPython questions as I can
I'm experiencing the same issue with Linux, using .
likely a different issue. Stacktrace? What nixpkgs version / commit?
The as of this writing. Here's the output I'm seeing. <details<summarybuild log</summary</detailsIt looks like pkg-config is giving an old version of GTK+?
please use your failure seems the same as which i closed because it's fixed in the branch by and i can confirm at least starts building there (it's still going...) i'm not sure when this fix will get to ...
nice! didn't know about the details tag. Ok yeah that looks like my issue, thanks for pointing me in that direction.
I can reproduce this on 10.14.6. My best take so far was to use and adapt other Darwin requirements. <details<summarydiff against master</summary</detailsUnfortunately it does not build with the same errors as for the .
Bumped to 3.0.5.1, to its , and it builds! was set, but no dependency specified. That's what caused the missing symbols. <details<summaryworking diff</summary</detailsI'm not even sure why this works at all. claims they build from a submodule, but obviously in this setup we take whatever is supplied through . To be pedantic, 4.0.7 is supposed use some specific instead of a release, as you can . That commit is after* 3.0.4 and shortly before 3.0.5. I only skimmed the , but it sounds and looks like backwards-compatible bug fixes. Opinions on how to proceed?

If we follow upstream and choose the intermediate revision, what to specify as the package version?
i've kinda given up on stuff, at least until the next release which i hope will either be built based on a release or be compatible with the latest release (i have no reason to believe this would be the case though) if you have a diff that fixes a package, i recommend you make a PR 4.0.7 seems to work with the 3.0.4, it seems reasonable to assume the same would be true for 3.0.4
Change:
inherit (darwin.apple_sdk.frameworks) Carbon; }; <ins> tageditor = libsForQt5.callPackage ../applications/audio/tageditor { }; </ins> taglib = callPackage ../development/libraries/taglib { }; taglib_extras = callPackage ../development/libraries/taglib-extras { };

Discussion:
Project description A tag editor with Qt GUI and command-line interface. Supports MP4 (iTunes), ID3, Vorbis, Opus, FLAC and Matroska. Metadata homepage URL: source URL: license: mit, GPLv2.0 platforms: linux
I am working on it. Progress:
Change:
, wine , boost , libxcb <ins> , pkgsi686Linux </ins> }: let

Discussion:
The current version of doesn't build support for the bitbridge that allows for running 32 bit VST plugins. Information on building that is on the . Basically, what's necessary is to make sure that the 32 bit versions of and are installed, and adding a meson flag. It didn't end up being that simple when I tried adding it myself by just adding the 32 bit dependencies to buildInputs and the meson flag; I got a vague error about meson being unable to find boost_filesystem. paging the maintainer of the package:
Attached are my modifications to the current yabridge definition. It is very hacky, but it seems to build... all up until it gets to the part where it links stuff. There, ld fails (see attached error log).
I spent a lot of time trying to get this to work, but I couldn't find any way to specify both the 32bit and 64bit version of boost in a build because of There probably is a hacky way to work around it, but I couldn't find how. I decided to give up on it until is fixed, but I would be happy to accept a workaround if you find one.
It looks like that linking error is the same problem I was running into. The build would only ever pick up either the 32bit boost or the 64bit one, but not both. I couldn't find a way to specify the right one per-architecture. I also thought of trying to combine the 32bit & 64bit builds after building them separately, but the project fails to compile as 32bit, because it makes the assumption that the default build will be 64bit.
Hmm. An idea i haven't tried yet is trying to patch one of the release binaries. Might be a little easier than trying to wrangle meson, at least until that issue gets fixed.
Complete crackpot idea; since the 32 bit stuff that gets built are just binaries that yabridgectl looks for in $PATH (i think), maybe it's possible to just take them from the prebuilt binaries and patch them? I'll try this when i get the chance.

EDIT: this idea was as terrible as it sounds, and the prebuilt binaries only worked through steam-run (presumably because they were compiled with hardcoded FHS paths)
Sorry to leave so many comments in a row, but I got it working and pretty much no ugly hacks too. I'll just paste my definition verbatim. Pretty much all i did was replace with (unsure if necessary, probably is), add the bitbridge flag, and replace all references to with (this was the reason for the linking issues at the end). Then i just a wildcard to the installPhase to get the 32 bit stuff in $out/bin. There are a few lines where I don't know if they're actually necessary; once it worked i stopped testing. I'm also unsure of how to handle referring to pkgsi686Linux, or if there's even a better/more specific way rather than just including pkgsi686Linux as an input. EDIT: I can also open a PR tomorrow if these changes look fine.
Change:
platforms = platforms.all; }; } <del> # Generated by: ./opam.nix.pl -v 2.0.0 -p opam-pull-3487.patch,opam-shebangs.patch,opam-mccs-darwin.patch </del> <ins> # Generated by: ./opam.nix.pl -v 2.0.2 -p opam-shebangs.patch </ins>

Discussion:
Currently nothing compiles from opam env. Need to add this patch for workaround using .
cc
Please don’t hesitate to sent a merge request.
Change:
postPatch = '' sed -i setup.py -e "/pip>=/c'pip'," substituteInPlace setup.py  <del> --replace 'typing==3.6.4' 'typing' </del> <ins> --replace "typing==3.6.4" "typing"  --replace "attrs>=19.3.0,<21.3.0" "attrs" </ins> ''; disabledTestPaths = [

Discussion:
As of , the build of is broken. This is currently breaking the build of other packages including and certainly many others... ~I suspect this was triggered by , , or one of the redis upgrades.~ I believe this was triggered by . Steps to reproduce the behavior: nixpkgs at failure The build to succeed. n/a n/a <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result.
I tried patching around the issue with but that gives me a test failure:
should fix that. Also please use postPatch.
Change:
hash = "sha256-GtXRzj+o+FClleh73kqelk0JrSyafZhf847lX1BiS9k="; }; <del> nativeBuildInputs = with python3.pkgs; [ poetry-core ]; </del> <ins> build-system = with python3.pkgs; [ poetry-core ]; </ins> pythonRelaxDeps = [ "textual"

Discussion:
Steps to reproduce the behavior: dooit I use nixos-unstable. NixVim and Helix with tree-sitter are not the cause of an issue, I can do a rebuild with them, error occurs then I add dooit. <!-- --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
If you do not ping listed maintainers for package (ie in ) they are not going to see this issue. Ping: Log with full chain: I assume from this fix for ( was with it in ): the intended way to fix it is to use for and not fix build for python 3.12.
Oh, sorry, I made a mistake with the formatting when I mentioned the package maintainer, I left it in the comment
Sorry, I forgot to come back to this... I was trying to see if I could fix textual/tree-sitter-languages/tree-sitter0_21 chain with python312. We can pin to 311 in the meantime.
That one seems to be relatively simple too ( had upstream pr - replacing with ). So something like this makes it build with python 3.12: <details<summarytree-sitter021 patch</summary</detailsIt was not accepted upstream, but they fully changed these parts around v0.23 so there is no used anymore. I am not sure if needs to be in this pinned state building with only python 3.11 for some reason.
Change:
<del> { fetchFromGitHub, stdenv, cmake, pkgconfig, python, alsaLib , libX11, libGLU, SDL2, lua5_3, zlib, freetype, wavpack </del> <ins> { fetchFromGitHub, stdenv, cmake, pkgconfig, python3, alsaLib , libX11, libGLU, SDL2, lua5_3, zlib, freetype, wavpack, icoutils </ins> }: stdenv.mkDerivation rec {

Discussion:
Describe the bug Teeworlds does not have a .desktop file so it doesn't show up in any menus. Maintainer information: