jiebi/CodeConvo huggingface dataset:
Change:
<del> { lib, buildPythonPackage, fetchPypi, pythonOlder, pytest, pytest-asyncio }: </del> <ins> { lib, buildPythonPackage, fetchPypi, pythonOlder, isPy35, pytest, pytest-asyncio }: </ins> buildPythonPackage rec { pname = "async_generator";

Discussion:
The derivation is available but cannot be built. I get the following error : I get the original package to work in a nix-shell with the following derivation:
I commented in the PR to address this issue. It is due to a circular dependency that and have on each other for testing. You may run into more similar issues since python 35 it not heavily tested in the community right now. If you can use 36 or 37. 37 will be the default soon.
Thanks!
Change:
<xi:include href="language-support.xml" /> <xi:include href="package-notes.xml" /> <xi:include href="coding-conventions.xml" /> <ins> <xi:include href="submitting-changes.xml" /> </ins> <xi:include href="haskell-users-guide.xml" /> <xi:include href="contributing.xml" />

Discussion:
Update the manual to include the policy about the branches such as staging: Instead of maintaining separate contribution guidelines in github and in the manual, we should link the to the relevant section in the manual.
I just did in for
(triage) does this suffice?
Change:
lottieconverter = callPackage ../tools/misc/lottieconverter { }; <ins> lpcnetfreedv = callPackage ../development/libraries/lpcnetfreedv { }; </ins> lsd = callPackage ../tools/misc/lsd { }; lsdvd = callPackage ../tools/cd-dvd/lsdvd {};

Discussion:
Project description Codec2 GUI for ham radio Metadata homepage URL: source URL: license: lgpl 2.1 platforms: unix, linux, darwin
Thanks!
Change:
KERN_DIR = "${kernel.dev}/lib/modules/${kernel.modDirVersion}/build"; KERN_INCL = "${kernel.dev}/lib/modules/${kernel.modDirVersion}/source/include"; <del> # If you add a patch you probably need this. #patchFlags = [ "-p1" "-d" "install/src/vboxguest-${version}" ]; </del> hardeningDisable = [ "pic" ]; NIX_CFLAGS_COMPILE = "-Wno-error=incompatible-pointer-types -Wno-error=implicit-function-declaration";

Discussion:
Describe the bug I am no longer able to build VirtualBox with guest additions when switching over to the lastest linux kernel: . The error complains that headers are missing/not found. This bug occurs consistently across all 3 of my machines. I am still able to build VirtualBox without guest additions. To Reproduce Here is the relevant snippet of my Additional context Here is the relevant errors from using Metadata Nix Info: Maintainer information:
Just hit the same thing myself too, very inconvenient to say the least.
Me too, is there any workaround?
No I never found a fix. In the end I had to remove VBox Guest.
It seems the only way to work around this is not to use boot.kernelPackages = pkgs.linuxPackages_latest;
Can you check whether this is still the case on the branch? I was able to build that with the same configuration as above:
I take that back - it's now failing at a later stage: This looks like we're missing a patch similar to the one in
agreed, that looks to be the exact same file that was patched in the host version of a VirtualBox. I did a quick search for an upstream bug for vboxguest but couldn't find anything. Perhaps it gets copied from the same source in the build process. I could try applying the same patch to vboxguest and alter the paths to see what happens. I won't have the opportunity to try that out until tonight (North America, west cost). So if you or someone else want to try it out sooner let me know.
Fix in , please test :-)
Change:
<ins> { lib, fetchFromGitHub, rustPlatform, pkg-config, openssl, stdenv, darwin, }: rustPlatform.buildRustPackage rec { pname = "code2prompt"; version = "1.1.0"; src = fetchFromGitHub { owner = "mufeedvh"; repo = "code2prompt"; rev = "v${version}"; hash = "sha256-KZqh0Vq4Mn56PhUO1JUzVpNBAGOZqUAsj31Cj5K+Lyk="; }; cargoLock = { lockFile = ./Cargo.lock; }; postPatch = '' # src is missing Cargo.lock ln -s ${./Cargo.lock} Cargo.lock ''; nativeBuildInputs = [ pkg-config ]; buildInputs = [ openssl ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.Security darwin.apple_sdk.frameworks.AppKit ]; meta = { description = "A CLI tool that converts your codebase into a single LLM prompt with a source tree, prompt templating, and token counting"; homepage = "https://github.com/mufeedvh/code2prompt"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ heisfer ]; mainProgram = "code2prompt"; }; } </ins>

Discussion:
Project description A command-line tool that converts your codebase into a single LLM prompt with a source tree, prompt templating, and token counting. See Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, windows
Change:
<del> { lib, buildDotnetModule, fetchFromGitHub, dotnetCorePackages, stdenv }: </del> <ins> { lib, buildDotnetModule, fetchFromGitHub, dotnetCorePackages }: </ins> let <del> inherit (dotnetCorePackages) combinePackages sdk_6_0 sdk_7_0; </del> <ins> inherit (dotnetCorePackages) sdk_7_0; </ins> in buildDotnetModule rec { pname = "fsautocomplete";

Discussion:
After the upgrade to 0.68.0 fsautocomplete no longer attach properly to NixVim (neovim). Steps to reproduce the behavior: a minimal NixVim config enable fsautocomplete and Ionide-vim a .fsx file the LspInfo command a see the missing id The clients get associated with an id as before. Version 0.67.0 ! Version 0.68.0 ! I haven't explored if the problem persists outside NixVim, but I would strongly suspect it does, as there haven't been any major changes in NixVim lately. <!-- 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]:
I can confirm you findings. It's an issue with 0.68.0. I'll do some more investigation before filing an issue upstream. for now, you can pin you fsautocomplete to 0.67.0
I've just been testing it a bit as well and came to the same conclusion that it is an upstream problem. I reconfigured my nixvim to build the from the nuget package and that one has the same issue. How do I pin in nixvim?
sorry I am not familiar with nixvim, my neovim just calls fsautocomplete from PATH. So I've just installed an old version via thats the commit just before 0.68.0 update
are you able to test ?
Working on it.
Change:
<ins> diff --git a/Makefile b/Makefile index 9048e45..0fb1f5a 100644 --- a/Makefile +++ b/Makefile @@ -26,7 +26,6 @@ site/index.html: darkman.1 mandoc -T html -O style=man-style.css < darkman.1 > site/index.html install: build -	@install -Dm755 darkman 	${DESTDIR}${PREFIX}/bin/darkman @install -Dm644 darkman.service	${DESTDIR}${PREFIX}/lib/systemd/user/darkman.service @install -Dm644 darkman.1	${DESTDIR}${PREFIX}/share/man/man1/darkman.1 @install -Dm644 LICENCE 	${DESTDIR}${PREFIX}/share/licenses/darkman/LICENCE </ins>

Discussion:
Package name: darkman Latest released version: 2.0.1 Current version on the unstable channel: 1.5.4 Current version on the stable/release channel: 1.5.4 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]:
Updating this package will resolve nix-community/home-manager too.
I've had a go at updating this but failed at the same point as . I don't know enough about nix or go to take it any further right now though. The part of the go language framework seems to be using a really old version of go (1.16) to try to build the package, which is not able to compile the code:
Change:
poppler poppler_data pythonEnv <del> qtbase qtimageformats qttools ]; cmakeFlags = [ # poppler uses std::optional "-DWANT_CPP17=ON" </del> <ins> qt5.qtbase qt5.qtimageformats qt5.qttools </ins> ]; meta = with lib; { maintainers = with maintainers; [ <del> erictapen </del> kiwi <ins> arthsmn </ins> ]; <del> platforms = platforms.linux; description = "Desktop Publishing (DTP) and Layout program for Linux"; </del> <ins> description = "Desktop Publishing (DTP) and Layout program"; </ins> homepage = "https://www.scribus.net"; # There are a lot of licenses... # https://github.com/scribusproject/scribus/blob/20508d69ca4fc7030477db8dee79fd1e012b52d2/COPYING#L15-L19

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:
cht-sh = callPackage ../tools/misc/cht.sh { }; <del> cinny-desktop = callPackage ../applications/networking/instant-messengers/cinny-desktop { }; </del> ckbcomp = callPackage ../tools/X11/ckbcomp { }; clac = callPackage ../tools/misc/clac { };

Discussion:
: Fails to load after logging in "Failed to load. WebAssembly.Module doesn't parse at byte 0: module doesn't start with '0asm'" Steps to reproduce the behavior: the package into a Matrix account fails to start with error mentioned before ! <!-- 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]:
! seems like the wasm file is missing outright for some reason
Fixed by
Change:
let pname = "electron-mail"; <del> version = "5.1.2"; </del> <ins> version = "5.1.6"; </ins> name = "ElectronMail-${version}"; src = fetchurl { url = "https://github.com/vladimiry/ElectronMail/releases/download/v${version}/electron-mail-${version}-linux-x86_64.AppImage"; <del> sha256 = "sha256-PLDzAtH7T7QMrLavvcF3zOVTayCqEA1IghIUAAxkbEE="; </del> <ins> sha256 = "sha256-lsXVsx7U43czWFWxAgwTUYTnUXSL4KPFnXLzUklieAo="; </ins> }; appimageContents = appimageTools.extract { inherit name src; };

Discussion:
Package name: electron-mail Latest released version: 5.1.6 <!-- Search your package here: --- Current version on the unstable channel: 5.1.2 Current version on the stable/release channel: 5.1.2 <!-- 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.
Change:
buildInputs = [ qt6.qtbase <ins> qt6.qtsvg </ins> ] ++ lib.optional stdenv.isLinux qt6.qtwayland; propagatedBuildInputs = with python3.pkgs; [

Discussion:
The anki package has some broken UI controls in 'preferences'. The core functionality works, but not all of the UX toggles do. Go to 'Tools -Preferences -Review' and try to click any of the checkboxes. Checkboxes should check. This occurs on the 2.1.65 package too: I've only tried to reproduce it on X, I'm unsure if it reproduces under wayland. oh hey that's me Please run and paste the result.
I had a feeling this might be a qt6 or pyqt6 issue since I believe that UX is a pyqt rendered thing. Switching it over to pyqt5 makes those checkboxes work on my machine, and the core functionality (studying) still works. The core functionality is all rust + javascript at this point I think, with basically no QT, so it makes sense this wouldn't impact it. I think the pragmatic thing is to package this with pyqt5 for now, and then once upstream stops supporting pyqt5, we can see if this bug is fixed, and if not properly understand it then.
I've found an even better workaround than using qt5 for this (fyi since you originally reported this). On my machine, if I go to: Tools -Preferences -Appearance (tab) -User Interface (section) -Style and select the 'Style' as 'Native' instead of 'Anki' in the dropdown, then all the other preference controls also start to work. It looks like this bug impacts the 'Anki' style, which is the default. Changing to the 'Native' style seems like an okay workaround for now since the style doesn't even influence that much of anki.
I stumbled upon this issue when bumping the Anki ebuild for Gentoo. In my case, PyQt6 was lacking support for the SVG image format. Compiling PyQt6 with fixed the issue. If you unzip the compiled you'll find several SVG checkbox icons under . Maybe this is the case here, too? Unfortunately, I'm not familiar with Nix, so I can't debug this yet.
Thanks so much for the pointer very much appreciated! Applying the following diff locally did seem to work! Within the anki theme, checkboxes seemed to toggle just fine after that, so it seems likely that's the culprit. I'll open a PR shortly after clicking around a bit more and making sure all seems well with the anki theme Edit: PR over here
Change:
, libgudev , pkg-config , glib <del> , python3 , gobject-introspection </del> <ins> , python3Packages </ins> }: <del> python3.pkgs.buildPythonApplication rec { </del> <ins> python3Packages.buildPythonApplication rec { </ins> pname = "switcheroo-control"; version = "2.6";

Discussion:
Steps to reproduce the behavior: update nixpkgs-unstable - -rebuild switch Package switcheroo-control-2.6 cannot find dependencies: cmake & glib-2.0 = 2.56.0 on nixos-unstable channel. <!-- 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]:
Change:
sed -e '1i #include <cstdint>' -i include/stp/AST/ASTNode.h ''; <del> buildInputs = [ boost zlib minisat cryptominisat python3 ]; </del> <ins> buildInputs = [ boost zlib minisat cryptominisat python3 ]; </ins> nativeBuildInputs = [ cmake bison flex perl ]; preConfigure = '' <del> python_install_dir=$out/${python3Packages.python.sitePackages} </del> <ins> python_install_dir=$out/${python3.sitePackages} </ins> mkdir -p $python_install_dir cmakeFlagsArray=( $cmakeFlagsArray

Discussion:
Klee installation returns the following error: Steps to reproduce the behavior: <!-- 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 the report; looking into it.
Looks like a STP issue on master/unstable; any ideas?
KLEE works on 24.05, try that in the meantime.
See also: , , and others. Seems like this is treewide.
It looks like there's an update to ; I'll bump it after gets merged but those two changes should fix klee.
Change:
++ lib.optional (gtkSupport == "gtk2") gtk2-x11 ++ lib.optional (gtkSupport == "gtk3") gtk3-x11 ++ lib.optionals stdenv.isDarwin [ Carbon CoreServices AppKit ] <del> ++ lib.optional stdenv.isLinux libcap </del> <ins> ++ lib.optionals stdenv.isLinux [ libcap systemd ] </ins> ++ lib.optional withAlsa alsa-lib; <del> configureFlags = [ "--disable-oss" ]; </del> <ins> configureFlags = [ "--disable-oss" ] ++ lib.optional stdenv.isLinux "--with-systemdsystemunitdir=${placeholder "out"}/lib/systemd/system"; </ins> patches = [ (fetchpatch {

Discussion:
, which is offered by most Linux distributions where is installed, is not present in NixOS. Its systemd services aren't available either. I'd like to be able to have an easy way to play sounds on boot and shutdown and this seems like the usual way to do it on other Linux distributions :grin: Steps to reproduce the behavior: (whether via , option, etc) should be available and executable. systemd services such as , , and should be available to enable. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Probably a NixOS module would be good so it'll be easy to customize.
That doesn't really have a bearing on the PR, as libcanberra would still need to be built with systemd support anyway.
woot! thank you for your work on this! i'm so excited to get this working on my PC
FYI it'll take a couple of weeks to end up in unstable (you can follow for the progress), and you'll then have to add it to as well, but it should work at that point.
Change:
pname = "gmic-qt${lib.optionalString (variant != "standalone") "-${variant}"}"; version = "3.2.1"; <del> src = fetchFromGitHub { owner = "c-koi"; repo = "gmic-qt"; rev = "v.${version}"; sha256 = "sha256-z+GtYLBcHVufXwdeSd8WKmPmU1+/EKMv26kNaEgyt5w="; </del> <ins> src = fetchzip { url = "https://gmic.eu/files/source/gmic_${version}.tar.gz"; hash = "sha256-2lMnn19FcFKnfIjSxOObqxIjqLMUoWgi0ADZBCBePY4="; </ins> }; <ins> patches = [ (fetchpatch { name = "gmic-qt-3.2.1-fix-system-gmic.patch"; url = "https://github.com/c-koi/gmic-qt/commit/e8d7a3523753ff592da63b1d54edf0921c54fe53.patch"; hash = "sha256-kBFZo2qvod4pH3oK8gvnmw39x6eMH9zjr4mMcY74mFo="; }) ]; sourceRoot = "source/gmic-qt"; </ins> nativeBuildInputs = [ cmake pkg-config

Discussion:
We broke gmic-qt during the bump. After contacting upstream, it seems like the cmake build is not maintained anymore: They migrated to . We should align with them and rewrite a qmake derivation for gmic-qt. Edit: jtojnar advise not to migrate to qmake but instead fix the cmake issue.
Any idea what I can do so I can build my system while this is a WIP?
Install the build from an older version of nixpkgs where the package you want still builds properly. The version in branch should be building properly. For Flakes: For Non-Flake:
Thank you so much!! That section of the wiki described exactly what I was trying to do!
I just posted an upstream PR to fix this:
I've opened with a proper fix if anyone here would like to do some testing (it works for me now)

Steps to reproduce the behavior: Full log: Package built successfully in . Package failed in . I assume package failed to built somewhere in between these two pull request. Please run and paste the result.
Possibly needs update like
tried but had a compilation issue: Error:
Change:
}: let <del> version = "2024.5.1"; </del> <ins> version = "2024.5.1b"; </ins> bw_web_builds = fetchFromGitHub { owner = "dani-garcia"; repo = "bw_web_builds"; rev = "v${version}"; <del> hash = "sha256-iNSkvQn3g64pI0uY7M4S7jEiRRDAc0wlPuJevzMJ+dc="; </del> <ins> hash = "sha256-5nlFt05ari9ovl+CaoyR/X9BzhsmsGyDt6eGLJ5ae/4="; </ins> }; in buildNpmPackage rec {

Discussion:
Package name: vaultwarden Latest released version: 1.31.0 (, ) <!-- Search your package here: --- Current version on the unstable channel: 1.30.5 Current version on the stable/release channel: 1.30.5 <!-- 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]:
Damn someone beat me to it lol
vaultwarden seems borken to me, at least in aarch builds. anyone else seeing this?
it should be fixed in
Change:
<ins> { lib, buildPythonPackage, pythonOlder, fetchPypi, setuptools, wheel, tkinter, darkdetect, }: let pname = "customtkinter"; version = "5.2.2"; in buildPythonPackage { inherit pname version; pyproject = true; disabled = pythonOlder "3.7"; src = fetchPypi { inherit pname version; hash = "sha256-/Y2zuvqWHJgu5gMNuoC0wuJYWGMHVrUTmG2xkRPY0gc="; }; nativeBuildInputs = [ setuptools wheel ]; buildInputs = [ tkinter ]; propagatedBuildInputs = [ darkdetect ]; # No tests doCheck = false; pythonImportsCheck = [ "customtkinter" ]; meta = { description = "A modern and customizable python UI-library based on Tkinter"; homepage = "https://github.com/TomSchimansky/CustomTkinter"; license = lib.licenses.mit; longDescription = '' CustomTkinter is a python UI-library based on Tkinter, which provides new, modern and fully customizable widgets. They are created and used like normal Tkinter widgets and can also be used in combination with normal Tkinter elements. The widgets and the window colors either adapt to the system appearance or the manually set mode ('light', 'dark'), and all CustomTkinter widgets and windows support HighDPI scaling (Windows, macOS). With CustomTkinter you'll get a consistent and modern look across all desktop platforms (Windows, macOS, Linux). ''; maintainers = with lib.maintainers; [ donteatoreo ]; }; } </ins>

Discussion:
Project description A modern and customizable python UI-library based on Tkinter <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit, platforms: unix, linux, darwin, ...
Change:
maintainers = with maintainers; [ raphaelr ]; }; }).overrideAttrs (attrs: { <del> postPatch = lib.optionalString (!stdenv.isDarwin) (attrs.postPatch + '' interp="$(cat $NIX_CC/nix-support/dynamic-linker)" patchelf --set-interpreter $interp  lib/ReSharperHost/linux-x64/Rider.Backend  plugins/dotCommon/DotFiles/linux-x64/JetBrains.Profiler.PdbServer rm -rf lib/ReSharperHost/linux-x64/dotnet ln -s ${dotnet-sdk_7} lib/ReSharperHost/linux-x64/dotnet ''); </del> <ins> nativeBuildInputs = (attrs.nativeBuildInputs or [ ]) ++ lib.optionals (stdenv.isLinux) [ autoPatchelfHook ]; buildInputs = (attrs.buildInputs or [ ]) ++ lib.optionals (stdenv.isLinux) [ stdenv.cc.cc zlib fontconfig  # plugins/dotTrace/DotFiles/linux-x64/libSkiaSharp.so ]; dontAutoPatchelf = true; postFixup = (attrs.postFixup or "") + lib.optionalString (stdenv.isLinux) '' ( cd $out/rider # Remove dotnet copy first so it's not considered by autoPatchElf rm -rf lib/ReSharperHost/linux-x64/dotnet autoPatchelf  lib/ReSharperHost/linux-x64/  plugins/dotCommon/DotFiles/linux-x64/  plugins/dotTrace/DotFiles/linux-x64/ ln -s ${dotnet-sdk_7} lib/ReSharperHost/linux-x64/dotnet ) ''; </ins> }); buildRubyMine = { pname, version, src, license, description, wmClass, buildNumber, ... }:

Discussion:
A clear and concise description of what the bug is. JetBrains editors run with which result in project built under the editors (i.e. in 's terminal) always picks up from . Even if the project is using for example . This result in ABI conflict when the build executable runs, because other components - which built using , outside clion - use from Steps to reproduce the behavior: well, this might be tricky to prepare a small project needed to support itself, should not leak into projects it edits  I suspect and in are problematic too introduced in
it seems that the fix should be to use command line switch instead of environment variable
And (or ), because JNA is looking for .so files there, so should be on one of them instead of
This is still a problem
Can confirm, this is an issue when using per-project environments which are on a different channel than my systems'. Shouldn't the "internals" be patched using e.g. instead?
For anyone else running into this: the workaround is to clear the environment variable in the IDE settings for the commands you want to run. Cumbersome, but it works.
The above workaround doesn't completely work. For instance, there is no way to remove when setting the project interpreter in PyCharm.
The following seems to work: I'll try to prepare a PR in the coming days. EDIT: It even discovered some missing dependencies and .
Has there been an update on this? I am trying to use prettier in Webstorm and all other tools to have needed the to be reset, if I want to run them. But this is not possible for prettier. I suspect that it would work with unset.
Just had this come up again trying to build a program with gcc 13 in CLion. Simply removing from in fixes the issue and doesn't appear to break clion, idea, or rider.