jiebi/CodeConvo huggingface dataset:
Change:
sha256 = "0njdxfmyk8smj8bbd6fs3lxjaq3lybivwgg16gpnbiyl984dpi9b"; }; <del> patches = stdenv.lib.optional (stdenv.hostPlatform.libc or null == "msvcrt") </del> <ins> # This is needed by freeimage patches = [ ./0001-Compile-transupp.c-as-part-of-the-library.patch ] ++ stdenv.lib.optional (stdenv.hostPlatform.libc or null == "msvcrt") </ins> ./mingw-boolean.patch; <del> outputs = [ "bin" "dev" "out" "man" "doc" ]; </del> <ins> outputs = [ "bin" "dev" "dev_private" "out" "man" "doc" ]; postFixup = '' moveToOutput include/transupp.h $dev_private ''; </ins> nativeBuildInputs = [ cmake nasm ];

Discussion:
Describe the bug I am trying to build for . is one giving me difficulty. Originally I filed an issue on : But the issue is instead with the libpng inside freeimage: Basically, libpng applies an incorrect ARM optimization to aarch64 that isn't actually available. From briefly looking at in nixpkgs, it seems that we patch with patches (and skimming that, it looks like it has a relevant aarch64 patch). So, my goal is to patch the vendored inside FreeImage, similar to how we patch itself. So far I've not had luck. I've tried with both the CRLF and LF patches from the 'apng' project and the regular patch used from the 'libpng-apng' project that is used in nixpkg's libpng. They all fail to apply and some complain about line endings, regardless of if I pipe the patch through dos2unix (or unix2dos) or not.
I seem to have fixed this by patching libpng inside of the freeimage source using the same patch as the derivation.. I'm just debating whether or not to allow it to be toggle-able as it is in the libpng derivation.
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
still important to me
I marked this as stale due to inactivity. &rarr;
still important to me
You can close this I think
Change:
buildInputs = [ glib gobject-introspection gtk3 gsettings-desktop-schemas upower <del> gnome-desktop cairo pango cogl clutter zenity libstartup_notification </del> <ins> gnome-desktop cairo pango cogl zenity libstartup_notification </ins> geocode-glib libinput libgudev libwacom libcanberra-gtk3 zenity xkeyboard_config libxkbfile libxkbcommon pipewire xwayland

Discussion:
Capability wrappers are somewhat limited. They require the capability be part of the ambient set for it to survive execv's, ie. when the wrapper executes the source binary (). This means any program spawned from a wrapped binary will also inherit the capabilities. We really don't want programs launched from gnome-shell to inherit capsysnice obviously. In particular bubblewrap fails to work if it possess any extra caps, breaking at least flatpaks and epiphany. So as far as I can see we have two options: Actually copy to wrapperDir and set capsysnic=+ep. This should be pretty easy, but also quite ugly (see for context). Patch mutter to drop inheritable, we could probably adopt . This should probably work as the ambient set only propagates if inheritable is set. cc
Patching mutter to drop inheritable works :tada:, will make a PR :)
Does the rationale for not merging it not apply to us?
No it shouldn't. We only drop inheritable to prevent the ambient set being passed on, while keeping effective and permitted for gnome-shell. (it might be possible to drop the ambient set with , but I went with just clearing inheritable):
Change:
pkgs.postgresql ]; <del> # Oracle's official package on npm is binary only (WHY?!) and doesn't provide binaries for aarch64. # This can supposedly be fixed by building a custom copy of the module from source, but that's way # too much complexity for a setup no one would ever actually run. # # NB: If you _are_ actually running n8n on Oracle on aarch64, feel free to submit a patch. </del> preRebuild = lib.optionalString stdenv.isAarch64 '' <ins> # Oracle's official package on npm is binary only (WHY?!) and doesn't provide binaries for aarch64. # This can supposedly be fixed by building a custom copy of the module from source, but that's way # too much complexity for a setup no one would ever actually run. # # NB: If you _are_ actually running n8n on Oracle on aarch64, feel free to submit a patch. </ins> rm -rf node_modules/oracledb <ins> # This package tries to load a prebuilt binary for a different arch, and it doesn't provide the binary for aarch64. # It is marked as an optional dependency in pnpm-lock.yaml and there are no other references to it n8n. rm -rf node_modules/@sap/hana-client </ins> ''; # makes libmongocrypt bindings not look for static libraries in completely wrong places

Discussion:
Steps to reproduce the behavior: the build ends with Builds fine on x86_64-linux <!-- 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]:
The npm package tries to load some and it chooses PowerPC architecture, there are no prebuilts for aarch64.
Removing the optional dependency fixes this issue. It is not used anywhere in the code, and basic functionality works without it.
Change:
, stdenv , fetchFromGitHub , callPackage <ins> , fetchpatch </ins> # Required build tools , cmake

Discussion:
I upgraded Zynaddsubfx (latest unstable), and was surprised to discover the new amazing interface (whooa)... and that I had no more loaded instrument (empty bank). I solved that problem by removing the user zynaddsubfx configuration and bank cache (I think the problem is the bank cache): and indeed, once you reload zynaddsubfx, you can see that the instruments are back. Also, a new file is created, and the bank path is hardcoded, like: I guess that in other distributions this path does not change when zynaddsubfx is updated, but with nix the bank path changes on upgrade, so the user needs to manually clear the cache on each upgrade. I'm not sure what's the best way to solve this problem. I was thinking that the best solution may be to add a small wrapper around zynaddsubfx which clears the cache if it detects in a path to another nix executable. The other possibility may be to use instead of the one, but it won't work outside of NixOs. If these options are not working, at least it would be nice to document that bank cache should be cleared on upgrades. Steps to reproduce the behavior: zynaddsubfx and potentially garbage collect the old version zynaddsubfx: instruments may disapear
Yeah it's really nice :blush: It was a lot of work to get it built. I'm not sure if any other distro even uses the new Zyn-Fusion interface, because it's not the default UI when building from source. I also noticed this problem before between upgrading & running . I tried working on a patch to avoid dumping the default paths into the config, but I never finished it. I'll try looking into it again!
I marked this as stale due to inactivity. &rarr;
still relevant, just haven't gotten around to fixing it
I think this issue should not be closed as for now it is based on a non-accepted PR , so I'll re-open waiting for the changes to be merged upstream.
Change:
cantarell-fonts dejavu_fonts source-code-pro # Default monospace font in 3.32 <del> source-sans-pro </del> <ins> source-sans </ins> ]; # Adapt from https://gitlab.gnome.org/GNOME/gnome-build-meta/blob/gnome-3-38/elements/core/meta-gnome-core-shell.bst

Discussion:
This is the same meaningless error message that’s bitten us . An attempt was made to replace it with a useful error message in NixOS/hydra, but that was reverted in NixOS/hydra. It looks like there’s another attempt pending in NixOS/hydra. I was able to locally reproduce the error with , and spent a day bisecting it to commit “source-sans-pro: 3.006 -3.046” (). Probably related: “nixos/gnome: remove alias reference to source-sans-pro”. Cc
Confirmed that patching with NixOS/hydra would have revealed the real error much more quickly.
Interesting - if I understand correctly, this eval failure is in a nixos module, which snuck by ofborg (it only checks packages). Also nixpkgs-unstable is chugging along happily, as the issue only affects nixos-unstable.
Change:
<ins> { buildGoModule, fetchFromGitHub, stdenv, bpftools, lib, nspr, libpcap, clang, fd, go-bindata, glibc, gnutls, bashInteractive, postgresql, mariadb, openssl, bash, }: buildGoModule rec { pname = "ecapture"; version = "0.8.6"; src = fetchFromGitHub { owner = "gojue"; repo = "ecapture"; rev = "refs/tags/v${version}"; hash = "sha256-xnUgsnz3zUkuLwqgdogEWQh0GMEmS/qmDqqmEQlHhfQ="; fetchSubmodules = true; }; nativeBuildInputs = [ clang fd bpftools go-bindata ]; newlibpcap = libpcap.overrideAttrs (previousAttrs: { configureFlags = previousAttrs.configureFlags ++ [ "--without-libnl" ]; }); buildInputs = [ newlibpcap glibc.static glibc ]; CGO_LDFLAGS = "-lpcap -lpthread -static"; ldflags = [ "-extldflags '-static'" "-linkmode=external" ]; hardeningDisable = [ "zerocallusedregs" ]; patchPhase = '' runHook prePatch substituteInPlace user/config/config_gnutls_linux.go  --replace-fail 'return errors.New("cant found Gnutls so load path")' 'gc.Gnutls = "${lib.getLib gnutls}/lib/libgnutls.so.30"'  --replace-fail '"errors"' ' ' substituteInPlace user/module/probe_bash.go  --replace-fail '/bin/bash' '${lib.getExe bashInteractive}' substituteInPlace user/config/config_bash.go  --replace-fail '/bin/bash' '${lib.getExe bashInteractive}' substituteInPlace user/config/config_nspr_linux.go  --replace-fail '/usr/lib/firefox/libnspr4.so' '${lib.getLib nspr}/lib/libnspr4.so' substituteInPlace cli/cmd/postgres.go  --replace-fail '/usr/bin/postgres' '${postgresql}/bin/postgres' substituteInPlace cli/cmd/mysqld.go  --replace-fail '/usr/sbin/mariadbd' '${mariadb}/bin/mariadbd' substituteInPlace user/module/probe_mysqld.go  --replace-fail '/usr/sbin/mariadbd' '${mariadb}/bin/mariadbd' substituteInPlace user/config/config_openssl_linux.go  --replace-fail 'return errors.New("cant found openssl so load path")' 'oc.Openssl = "${lib.getLib openssl}/lib/libssl.so.3"'  --replace-fail '"errors"' ' ' runHook postPatch ''; postConfigure = '' sed -i '/git/d' Makefile sed -i '/git/d' variables.mk substituteInPlace Makefile  --replace-fail '/bin/bash' '${lib.getExe bash}' make ebpf go-bindata -pkg assets -o "assets/ebpf_probe.go" $(find user/bytecode -name "*.o" -printf "./%p ") ''; vendorHash = "sha256-j5AXZqup0nPUlGWvb4PCLKJFoQx/c4I3PxZB99TTTWA="; meta = { description = "Capture SSL/TLS text content without CA certificate Using eBPF"; changelog = "https://github.com/gojue/ecapture/releases/tag/v${version}"; homepage = "https://ecapture.cc"; platforms = [ "x86_64-linux" "aarch64-linux" ]; license = lib.licenses.asl20; maintainers = with lib.maintainers; [ bot-wxt1221 ]; mainProgram = "ecapture"; }; } </ins>

Discussion:
Project description Capture SSL/TLS text content without CA certificate Using eBPF. Metadata homepage URL: source URL: license: apache-2.0 platforms: linux
Change:
] ++ lists.optionals cudaSupport [ "-DCMAKE_CUDA_ARCHITECTURES=${cudaArchitecturesString}" "-DMIN_ARCH=${minArch}" # Disarms magma's asserts <del> "-DCMAKE_C_COMPILER=${cudatoolkit.cc}/bin/cc" "-DCMAKE_CXX_COMPILER=${cudatoolkit.cc}/bin/c++" </del> <ins> "-DCMAKE_C_COMPILER=${backendStdenv.cc}/bin/cc" "-DCMAKE_CXX_COMPILER=${backendStdenv.cc}/bin/c++" </ins> "-DMAGMA_ENABLE_CUDA=ON" ] ++ lists.optionals rocmSupport [ "-DCMAKE_C_COMPILER=${hip}/bin/hipcc"

Discussion:
Per , assuming NVIDIA continues with its current compute capability naming scheme, will run into issues with the launch of Blackwell. This is a followup from <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
pyxdg pycairo requests <ins> semver </ins> websocket-client ];

Discussion:
When using the package , some extensions (like ) require the python package . When running without it, I get the error Steps to reproduce the behavior: package with plugin and run again with crashes and log report errors The extension doesn't crash Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
mit publicDomain ]; <ins> broken = stdenv.isDarwin; </ins> }; <del> } </del> <ins> }) </ins>

Discussion:
Package name: scribus Latest released version: 1.6.0 Current version on the unstable channel: 1.5.8 Current version on the stable/release channel: 1.4.8 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]:
The version on the stable channel is also 1.5.8, 1.4 existed only on the old NixOS 23.05 release and got removed since.
Change:
installFlags = [ "DESTDIR=$(out)" ]; postInstall = '' <del> for f in lesspipe.sh lesscomplete; do wrapProgram "$out/bin/$f" --prefix-each PATH : "${lib.makeBinPath [ binutils file gnused procps ]}" done </del> <ins> # resholve doesn't see strings in an array definition substituteInPlace $out/bin/lesspipe.sh --replace 'nodash strings' "nodash ${binutils-unwrapped}/bin/strings" ${resholve.phraseSolution "lesspipe.sh" { scripts = [ "bin/lesspipe.sh" ]; interpreter = "${bash}/bin/bash"; inputs = [ coreutils file gnugrep gnused gnutar iconv procps ncurses ]; keep = [ "$prog" "$c1" "$c2" "$c3" "$c4" "$c5" "$cmd" "$colorizer" "$HOME" ]; fake = { # script guards usage behind has_cmd test function, it's safe to leave these external and optional external = [ "cpio" "isoinfo" "cabextract" "bsdtar" "rpm2cpio" "bsdtar" "unzip" "ar" "unrar" "rar" "7zr" "7za" "isoinfo" "gzip" "bzip2" "lzip" "lzma" "xz" "brotli" "compress" "zstd" "lz4" "archive_color" "bat" "batcat" "pygmentize" "source-highlight" "vimcolor" "code2color" "w3m" "lynx" "elinks" "html2text" "dtc" "pdftotext" "pdftohtml" "pdfinfo" "ps2ascii" "procyon" "ccze" "mdcat" "pandoc" "docx2txt" "libreoffice" "pptx2md" "mdcat" "xlscat" "odt2txt" "wvText" "antiword" "catdoc" "broken_catppt" "sxw2txt" "groff" "mandoc" "unrtf" "dvi2tty" "pod2text" "perldoc" "h5dump" "ncdump" "matdump" "djvutxt" "openssl" "gpg" "plistutil" "plutil" "id3v2" "csvlook" "jq" "zlib-flate" "lessfilter" ] ++ lib.optional stdenv.isDarwin [ # resholve only identifies this on darwin # call site is gaurded by || so it's safe to leave dynamic "locale" ]; builtin = [ "setopt" ]; }; execer = [ "cannot:${iconv}/bin/iconv" ]; }} ${resholve.phraseSolution "lesscomplete" { scripts = [ "bin/lesscomplete" ]; interpreter = "${bash}/bin/bash"; inputs = [ coreutils file gnugrep gnused gnutar ]; keep = [ "$prog" "$c1" "$c2" "$c3" "$c4" "$c5" "$cmd" ]; fake = { # script guards usage behind has_cmd test function, it's safe to leave these external and optional external = [ "cpio" "isoinfo" "cabextract" "bsdtar" "rpm2cpio" "bsdtar" "unzip" "ar" "unrar" "rar" "7zr" "7za" "isoinfo" "gzip" "bzip2" "lzip" "lzma" "xz" "brotli" "compress" "zstd" "lz4" ]; builtin = [ "setopt" ]; }; }} </ins> ''; meta = with lib; {

Discussion:
According to documentation of the app: there's a dozen dependencies we don't explicitly have a dependency on, so there's multitude of bugs that might appear depending on what's on $PATH.
Do we need a new maintainer of to move this issue forward?
We should pull the package from NixOS core...absolutely no reason to have such a bloated less ship by default.
Change:
hardeningDisable = [ "format" ]; passthru.updateScript = directoryListingUpdater { <del> inherit pname version; </del> <ins> inherit (self) pname version; </ins> url = "https://lgames.sourceforge.io/LBreakoutHD/"; extraRegex = "(?!.*-win(32|64)).*"; }; <del> meta = with lib; { broken = stdenv.isDarwin; </del> <ins> meta = { </ins> homepage = "https://lgames.sourceforge.io/LBreakoutHD/"; description = "A widescreen Breakout clone"; <del> license = licenses.gpl2Plus; maintainers = with maintainers; [ AndersonTorres ]; </del> <ins> license = lib.licenses.gpl2Plus; maintainers = with lib.maintainers; [ AndersonTorres ]; </ins> inherit (SDL2.meta) platforms; <ins> broken = stdenv.isDarwin; </ins> }; <del> } </del> <ins> }) </ins>

Discussion:
lbreakouthd fails to launch with "libGL error: MESA-LOADER: failed to open iris" Steps to reproduce the behavior: lbreaouthd with lbreakouthd launches Framework laptop with intel graphics. Please run and paste the result.
keep an eye on the and tell me if anything goes wrong
Change:
<del> { lib, buildGoModule, fetchFromGitHub, installShellFiles }: </del> <ins> { lib, go, buildGoModule, fetchFromGitHub, installShellFiles }: </ins> buildGoModule rec { pname = "vcluster";

Discussion:
Expected this to show 0.15.6 instead of 0.0.1 <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- system: host os: multi-user?: sandbox: version: channels(root): channels(mauricio): nixpkgs:
Upon a cursory review this seems like an issue with upstream and not nixpkgs. See the search results for 0.0.1 in upstream @ .
Pretty sure it's controlled by the RELEASE_VERSION env var, which the nix package currently doesn't seem to set.
Change:
buildPythonPackage rec { inherit (openbabel) pname version; <del> src = "${openbabel}/lib/python${python.sourceVersion.major}.${python.sourceVersion.minor}/site-packages"; </del> <ins> src = "${openbabel}/${python.sitePackages}"; </ins> <del> nativeBuildInputs = [ openbabel ]; </del> <ins> buildInputs = [ openbabel ]; </ins> # these env variables are used by the bindings to find libraries # they need to be included explicitly in your nix-shell for

Discussion:
Steps to reproduce the behavior: openbabel or any package that depends on it, i.e Kalzium The issue seems to have appeared in the most recent push to nixos-unstable, it seems to be an issue with the openbabel dependency <!-- 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]:
Actually after properly inspecting this issue I realize that it is rather an issue with it's dependency, openbabel that fails to build
The problem is exactly this line and Python 3.12, which removed distutils: We can work around it by setting in CMake , but I didn't manage to get the Python bindings to build again, as the nix expression also crafts a custom like that:
Change:
urls ? [] , # Additional curl options needed for the download to succeed. <ins> # Warning: Each space (no matter the escaping) will start a new argument. # If you wish to pass arguments with spaces, use `curlOptsList` </ins> curlOpts ? "" <ins> , # Additional curl options needed for the download to succeed. curlOptsList ? [] </ins> , # Name of the file.  If empty, use the basename of `url' (or of the # first element of `urls'). name ? ""

Discussion:
I was trying to download something that required that I put a token to the header. That has to be quoted mind you. Then I got these errors: Then it tries to download what's in the url, but It can't because that token authorizes it. Clearly not what I wanted :) Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: cc
This seems difficult to support. You could use or (e.g. ) instead.
I honestly think someone would expect this to just work like that. Perhaps there should be a note somewhere, if no one is interested in supporting this, that you cannot use quoted args here. Either of those are a workaround for me at least :+1: . But there could be more complex times when this isn't enough.
Actually you can use such quoted args only in scripts (e.g. or ). This could be made to work with Nix 2 and its structured attributes feature (even while maintaining compatibility with Nix 1):
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
I believe this can still be implemented, and would be better than the current solution of writeText.
I just had this need in svanderburg/node2nix. The file workaround worked, but it took a very very long time to find this issue.
I marked this as stale due to inactivity. &rarr;
still an issue and why it is difficult to support? looks like a trivial bug
I marked this as stale due to inactivity. &rarr;
Change:
# symbolic name and `patch' is the actual patch.  The patch may # optionally be compressed with gzip or bzip2. kernelPatches ? [] <del> , ignoreConfigErrors ? stdenv.hostPlatform.linux-kernel.name or "" != "pc" </del> <ins> , ignoreConfigErrors ? stdenv.hostPlatform.linux-kernel.name != "pc" </ins> , extraMeta ? {} , isZen      ? false

Discussion:
Building powerpc kernels (I only tested pkgsCross.powernv, but examination of the kernel source code suggests to me that 32-bit powerpc, and well as big-endian 64-bit will be the same) is broken since This happens because on powerpc, the kernel target we install is vmlinux, rather than any derivative of it like zImage. The kernel build system will strip when creating such a derivative image, but because we install vmlinux directly, we get an unstripped image. This means the kernel contains references to its build directory, which since that PR will be the $dev output. AIUI, 64-bit POWER boots via kexec, and a zImage is a self-extracting kernel ELF image, so hopefully the fix would just be to switch the kernel target for powerpc to zImage, and things will work again, and POWER users will get smaller kernel images as a bonus. I'm not sure about 32-bit PowerPC, but this might be helpful. If we can't use an *Image target for any powerpc targets, there is also a target called that we could fall back to, but let's take the opportunity to evaluate whether anything else is more suitable first, when we're changing this stuff anyway. Apart from powerpc, the only we have that uses vmlinux as its kernel target is a MIPS machine called the Fuloong 2.0. I don't know how it boots.
I'll handle this. I don't have big-endian POWER hardware, but pointed out that qemu can probably boot a BE kernel under emulation at full hardware speeds. So if that works I can take care of the 32-bit POWER (which is mostly BE) too.
For reference, I managed to get a working kernel derivation for Power9 with Just setting building a zImage without fully stripping it afterwards wasn't enough. There still was a reference to in the debug info somewhere.
Yep, very plausible that there are other references as well. We had for x86 and RISC-V, although that specific issue didn't apply to other architectures.
I'll dig into this this evening. thank you for the tip! Also putting this link here so I don't lose it:
Verified (after fixing a bunch of other things) that is affected too. Thanks again for the heads up Working on a fix.
Edit: I meant to post this .
Fixed by