jiebi/CodeConvo huggingface dataset:
Change:
github = "k3a"; githubId = 966992; }; <ins> k3yss = { email = "rsi.dev17@gmail.com"; name = "Rishi Kumar"; github = "k3yss"; githubId = 96657880; }; </ins> k900 = { name = "Ilya K."; email = "me@0upti.me";

Discussion:
Project description Bend is a massively parallel, high-level programming language. Metadata homepage URL: source URL: license: apache 2.0 platforms: unix, linux, darwin was able to get it compiling with this: but when i run it like ( exists) i get this: thought the hvm build input would fix that but no hopefully im just being stupid somehow Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
You're alllmost there. For runtime deps, you should use . Replace the line with:
ty :) ok this compiles but i have a different error now: using the example running . i was thinking i might have to wait till it gets a bit more stable but ive seen so i tried making a nix package as soon as possible :).
That error is caused by hvm being out of date. The version of hvm in nixpkgs is 1.0.9, but bend needs version 2.
I've created a PR to bump hvm to version 2:
Change:
libjack2 = jack2.override { prefix = "lib"; }; <ins> jack-example-tools = callPackage ../misc/jackaudio/tools.nix { libopus = libopus.override { withCustomModes = true; }; jack = jack2; }; </ins> jack-autoconnect = libsForQt5.callPackage ../applications/audio/jack-autoconnect { }; jack_autoconnect = jack-autoconnect;

Discussion:
jack2 as of 1.9.22 no longer ships with tools or examples, those now live in a separate repo (). it doesn't look like these have been packaged yet, removing a bunch of important utilities with no replacement. (approved the bot update) (merged & tested)
Ah semantic versioning, I knew ye well.
Change:
unicorn ]; <del> postPatch = '' substituteInPlace setup.py  --replace "pefile==2021.5.24" "pefile>=2021.5.24" ''; </del> # Tests are broken (attempt to import a file that tells you not to import it, # amongst other things) doCheck = false;

Discussion:
seems to be missing a dependency which was introduced in 1.4.1 (the current version in nixpkgs, 1.4.2 has already been released, so probably should be updated). The build fails: I am puzzled how this slipped past the checks. Steps to reproduce the behavior: A clear and concise description of what you expected to happen. I am building on Fedora. system: multi-user?: sandbox: version: channels(): nixpkgs:
Change:
<del> { pkgs , buildPythonPackage , fetchPypi , python , azure-mgmt-common }: buildPythonPackage rec { version = "0.20.0"; pname = "azure-mgmt-storage"; src = fetchPypi { inherit pname version; extension = "zip"; sha256 = "16iw7hqhq97vlzfwixarfnirc60l5mz951p57brpcwyylphl3yim"; }; preConfigure = '' # Patch to make this package work on requests >= 2.11.x # CAN BE REMOVED ON NEXT PACKAGE UPDATE sed -i 's|len(request_content)|str(len(request_content))|' azure/mgmt/storage/storagemanagement.py ''; postInstall = '' echo "__import__('pkg_resources').declare_namespace(__name__)" >> "$out/lib/${python.libPrefix}"/site-packages/azure/__init__.py echo "__import__('pkg_resources').declare_namespace(__name__)" >> "$out/lib/${python.libPrefix}"/site-packages/azure/mgmt/__init__.py ''; propagatedBuildInputs = [ azure-mgmt-common ]; meta = with pkgs.lib; { description = "Microsoft Azure SDK for Python"; homepage = "https://azure.microsoft.com/en-us/develop/python/"; license = licenses.asl20; maintainers = with maintainers; [ olcai ]; }; } </del>

Discussion:
After in nixops, we can remove the locally pinned version in nixpkgs.
Not yet, I would like to keep those for building nixops v1.6.1 for any users of the Azure backend.
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 .
Change:
<ins> GEM remote: https://rubygems.org/ specs: fusuma (3.5.0) fusuma-plugin-appmatcher (0.7.1) fusuma (>= 3.0) rexml ruby-dbus fusuma-plugin-keypress (0.11.0) fusuma (>= 3.1) fusuma-plugin-sendkey (0.10.1) fusuma (>= 3.1) revdev fusuma-plugin-wmctrl (1.3.1) fusuma (>= 3.1) revdev (0.2.1) rexml (3.2.8) strscan (>= 3.0.9) ruby-dbus (0.23.1) rexml strscan (3.1.0) PLATFORMS ruby DEPENDENCIES fusuma (>= 3.0.0) fusuma-plugin-appmatcher fusuma-plugin-keypress fusuma-plugin-sendkey fusuma-plugin-wmctrl BUNDLED WITH 2.5.9 </ins>

Discussion:
Package name: fusuma Latest released version: 3.5.0 <!-- Search your package here: --- Current version on the unstable channel: 3.3.1 Current version on the stable/release channel: 3.3.1 <!-- 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]. By the way, fusuma now use yml file instead of yaml file as config file. now when I use HM , it will generate a yaml file in .config, please update it to change it to a yml file. and when I use = true; it wont be installed. [reaction]: [issues you find important]:
I guess that this should be addressed at home-manager repository as nixpkgs does not offer a fusuma service, as far as I rembember
you are right
Already fixed in home-manager:
sorry, I don't understand. if it has been fixed, why I still have the same issue? I just installed yesterday.
Are you perhaps not on ?
ah, right. I use stable nixos and HM, install some new software with pkgs-unstable. But this is a service, how do I change the package to unstable version? I tried = pkgs- But the result is still same.
It's fixed on master branch of Home Manager and not have been backported to release-23.11. Home manager master always follows the NixOS unstable branch, so I won't suggest switching to master branch of HM unless you upgrade your system to nixos-unstable.
Change:
chmod +x "$out"/bin/wsrep_sst_common rm "$out"/bin/{mariadb-client-test,mariadb-test,mysql_client_test,mysqltest} rm -r "$out"/data # Don't need testing data <del> mv "$out"/OFF/suite/plugins/pam/pam_mariadb_mtr.so "$out"/share/pam/lib/security mv "$out"/OFF/suite/plugins/pam/mariadb_mtr "$out"/share/pam/etc/security rm -r "$out"/OFF </del> '' + optionalString withStorageMroonga '' mv "$out"/share/{groonga,groonga-normalizer-mysql} "$out"/share/doc/mysql '' + optionalString (!stdenv.hostPlatform.isDarwin) '' <ins> mv "$out"/OFF/suite/plugins/pam/pam_mariadb_mtr.so "$out"/share/pam/lib/security mv "$out"/OFF/suite/plugins/pam/mariadb_mtr "$out"/share/pam/etc/security rm -r "$out"/OFF </ins> sed -i 's/-mariadb/-mysql/' "$out"/bin/galera_new_cluster '';

Discussion:
Describe the bug All last builds on Hydra have failed because of (top level package). E.g. Nr Status -- -- 1 Cached failure (log, raw, tail) (propagated from build ) First broken build 2020-06-05 19:14:56: Nr Status -- -- 1 Failed (log, raw, tail) (propagated from build ) Log: To Reproduce I can't reproduce the issue locally though, does compile. Expected behavior Hydra job should not fail on mariadb. 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 $ nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(theo): channels(root): channels(arsleust): nixpkgs: Maintainer information:
Reproduction: are you sure you tried it on darwin? (That's what fails on Hydra.)
Probably caused by , Darwin doesn't have .so 's right? cc
Change:
--replace /usr/lib/open-fprintd "$out/lib/open-fprintd" ''; <ins> dontWrapGApps = true; makeWrapperArgs = [ "${gappsWrapperArgs[@]}" ]; </ins> postFixup = '' wrapPythonProgramsIn "$out/lib/open-fprintd" "$out $pythonPath" '';

Discussion:
Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
enableParallelBuilding = true; <ins> env = lib.optionalAttrs stdenv.cc.isClang { CXXFLAGS = "-std=c++14"; }; </ins> hardeningDisable = [ "format" ]; meta = with lib; {

Discussion:
build .#CoinMP (only fails for Darwin) log failures: aarch64-darwin: x86_64-darwin: No maintainer listed in package.
Change:
{ stdenv, lib, fetchFromGitHub, pkg-config, cmake , alsa-lib, glib, libjack2, libsndfile, libpulseaudio , AudioUnit, CoreAudio, CoreMIDI, CoreServices <del> , version ? "2" </del> }: <del> let versionMap = { "1" = { fluidsynthVersion = "1.1.11"; sha256 = "0n75jq3xgq46hfmjkaaxz3gic77shs4fzajq40c8gk043i84xbdh"; }; "2" = { fluidsynthVersion = "2.2.3"; sha256 = "0x5808d03ym23np17nl8gfbkx3c4y3d7jyyr2222wn2prswbb6x3"; }; }; in with versionMap.${version}; stdenv.mkDerivation  { name = "fluidsynth-${fluidsynthVersion}"; version = fluidsynthVersion; </del> <ins> stdenv.mkDerivation rec { pname = "fluidsynth"; version = "2.2.3"; </ins> src = fetchFromGitHub { owner = "FluidSynth"; repo = "fluidsynth"; <del> rev = "v${fluidsynthVersion}"; inherit sha256; </del> <ins> rev = "v${version}"; sha256 = "0x5808d03ym23np17nl8gfbkx3c4y3d7jyyr2222wn2prswbb6x3"; </ins> }; nativeBuildInputs = [ pkg-config cmake ];

Discussion:
no longer compiles with GLib 2.70: The failure looks patchable: We'd need to replace the use of in by an equivalent call to . However I'm not quite confident about the right place to call it, since we need to avoid calling it twice (which is UB according to the GLib documentation) and it looks like there are two different intialization routines that'd need to initialize the lock, and . Therefore I think should try to make an effort to finally get rid of this vulnerable version of fluidsynth (). Remaining uses: [x] , fixed in [x] (cc fixed in [x] (cc fixed in
Change:
"runtime.win-arm64.Microsoft.NETCore.DotNetHost"  "runtime.win-arm64.Microsoft.NETCore.DotNetHostPolicy"  "runtime.win-arm64.Microsoft.NETCore.DotNetHostResolver"  <del> "runtime.win-arm.Microsoft.NETCore.DotNetAppHost"  "runtime.win-arm.Microsoft.NETCore.DotNetHost"  "runtime.win-arm.Microsoft.NETCore.DotNetHostPolicy"  "runtime.win-arm.Microsoft.NETCore.DotNetHostResolver"  </del> "runtime.win-x64.Microsoft.NETCore.DotNetAppHost"  "runtime.win-x64.Microsoft.NETCore.DotNetHost"  "runtime.win-x64.Microsoft.NETCore.DotNetHostPolicy" 

Discussion:
Package name: , Latest released version: 8.0.100-preview.6..14 Current version on the unstable channel: 8.0.100-preview.5..2 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.
I have a PR for the other dotnet versions (), unfortunately the 8.0 version has problems with missing system nuget versions. Due to that I was planning on skipping this version (it's unstable and should not be dependended upon anyway). Are there any features in this new version that you consider important? I can try hacking up the update script in that case.
Change:
stdenv = stdenv; }); <del> kmetronome = libsForQt5.callPackage ../applications/audio/kmetronome { }; </del> <ins> kmetronome = qt6Packages.callPackage ../applications/audio/kmetronome { }; </ins> kmplayer = libsForQt5.callPackage ../applications/video/kmplayer { };

Discussion:
Package name: kmetronome Latest released version: 1.4.0 Current version on the unstable channel: 1.2.0 Current version on the stable/release channel: 1.2.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]:
Change:
# error: cast from ... to ... converts to incompatible function type [-Werror,-Wcast-function-type-strict] ++ lib.optionals (stdenv.cc.isClang && lib.versionAtLeast stdenv.cc.version "16") [ "-Wno-error=cast-function-type-strict" <ins> # Suppresses the most spammy warnings. # This is mainly to fix https://github.com/NixOS/nixpkgs/issues/266895. ] ++ lib.optionals rocmSupport [ "-Wno-#warnings" "-Wno-cpp" "-Wno-unknown-warning-option" "-Wno-ignored-attributes" "-Wno-deprecated-declarations" "-Wno-defaulted-function-deleted" "-Wno-pass-failed" ] ++ [ "-Wno-unused-command-line-argument" "-Wno-maybe-uninitialized" "-Wno-uninitialized" "-Wno-array-bounds" "-Wno-stringop-overflow" "-Wno-free-nonheap-object" "-Wno-unused-result" </ins> ])); nativeBuildInputs = [

Discussion:
torchWithRocm hydra build fails because of too many logs. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
How exactly do you fix this? Is there a hydra option we can put in the derivation? Otherwise, do we have to omit warnings?
I have a fix by omitting some warnings, but should we do that? Should we instead get hydra to allow bigger logs?
Change:
stdenv.mkDerivation (finalAttrs: { pname = "blastem"; <del> version = "0.6.2-unstable-2024-03-31"; </del> <ins> version = "0.6.2-unstable-2024-08-14"; </ins> src = fetchhg { url = "https://www.retrodev.com/repos/blastem"; <del> rev = "48ab1e3e5df5"; hash = "sha256-UZl5fIE7LJqxwS8kFJ3xr8BJyHF60dnRNeA5k7lAuxg="; </del> <ins> rev = "aa888682faa0"; hash = "sha256-0xw9O0o1pkJiXHyZer4nMJeLlRXS3Z4YYoLgfkrz3Yo="; </ins> }; # will probably be fixed in https://github.com/NixOS/nixpkgs/pull/302481

Discussion:
Package name: blastem Latest released version: 0.6.2-unstable-2024-08-14 <!-- Search your package here: --- Current version on the unstable channel: 0.6.2-unstable-2024-03-31 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]:
Change:
<del> { lib, stdenv, cmake, boost, bison, flex, fetchFromGitHub, perl , python3, python3Packages, zlib, minisat, cryptominisat }: </del> <ins> { lib , stdenv , cmake , boost , bison , flex , fetchFromGitHub , fetchpatch , perl , python3 , zlib , minisat , cryptominisat }: </ins> stdenv.mkDerivation rec { pname = "stp";

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:
grep = "${gnugrep}/bin/grep"; bash = "${bash}/bin/bash"; }) <ins> # Fixes 2 minute delay at poweroff. # https://gitlab.gnome.org/GNOME/gnome-session/issues/74 (fetchpatch { url = "https://gitlab.gnome.org/GNOME/gnome-session/-/commit/9de6e40f12e8878f524f8d429d85724c156a0517.diff"; sha256 = "19vrjdf7d6dfl7sqxvbc5h5lcgk1krgzg5rkssrdzd1h4ma6y8fz"; }) </ins> ]; mesonFlags = [ "-Dsystemd=true" "-Dsystemd_session=default" ];

Discussion:
Describe the bug In with , shutdown is delayed for 2 minutes at: To Reproduce This can be reproduced with a minimal VM. (It also happens with a real system, of course.) : (currently ). : Log In. the GNOME power menu and select Power Off; click Power Off. shutdown is delayed for 2 minutes: Expected behavior Shutdown should not be delayed. Additional context This was not an issue in . Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(anders): channels(root): nixpkgs: Maintainer information:
I can reproduce, indeed very annoying. A workaround can be to reduce the systemd timeout time. I've heard other people report this
I found the issue and fix from upstream: .
Change:
<del> { stdenv </del> <ins> { lib , stdenv </ins> , autoPatchelfHook , fetchurl , file

Discussion:
Carry over discussion from IRC #nixos-dev and . Inspired by the doc change in recommending top-level usage of over , we want to reduce confusion for newcomers and unnecessary complexity by making the canonical way to access the Nix library. We may still want to keep to not break external code, and place a or similar at its definition site. There are over files where occurs at least once. Beyond splitting this change across multiple PRs, in what ways can the change be automated? Pinging
In the short term, we could add this check in ofbrorg and , and update any examples in the documentation to reduce new usage of .
Don't forget things like and .
Ah. So 45K occurrences across 11.8K files.
toplevel is done
the xorg dep generator also doesn’t put it in its output anymore
trewide rewrite in
doc changes in
Graph of occurrences over time:
Nice! What scripts did you use to generate it?
There's a source code link now :)
Found another large source of s. Fixing cabal2nix should remove around 24k occurrences in .
Status report
Just found out that counts stuff like as well, so
Is it ok to rewrite to ?
That's the lib output of , so no.
an easy way to find out is to evaluate both in
Subfolders of with <10 changes needed in PR
Around + replacements out of 30k+ are concentrated in - should be trivial to regenerate the file with the new desired contents.
I'm working on it but it's a bit more complicated than I anticipated.
What problems are you running into?
Part of code generation of cabal2nix is in an external dependency, so I had to open two PRs. The dependency is itself on Hackage, so we may have to wait until the change propagates to Stackage LTS and then Nixpkgs, unless peti will use an override or something: I'm not familiar with the cabal2nix workflow.
I think the haskell-updates are mostly done from a local checkout of cabal2nix, so it depends mostly on what version peter is using. You can also probably just ask him, he is generally available for such things on his .
could you help here?
The Haskell infrastructure has switched to the new style with commit . It will land in this Friday.

I have also updated the generator code and released new versions to Hackage, so I guess the Haskell infrastructure can be considered done.
Thank you
More accurate regex: (the one above captures stuff like
When is merged, this will be the result Three Nix files remain that use directly.
The last usages of it can be found by commenting out where it is inherited in .
I just got this warning while doing a , but it doesn't give me any info as to which derivations are at fault. Is there any way we could improve the message to identify culprits?
With , you should get a hard error which will allow you to use . Or you can update Nixpkgs, since it has been removed in
Change:
npmRebuildFlags = [ "|| true" ]; makeCacheWritable = true; <del> npmDepsHash = "sha256-TeAuXJn07xCveoD5yaNLyULzhNZ8Mtdn4NNLfu2EwEg="; </del> <ins> npmDepsHash = "sha256-GTjL6cjYPoa1ohtqslxDskCN9tKuu1OP1ZWIWtFx+E0="; </ins> npmFlags = [ "--legacy-peer-deps" ]; npmBuildScript = if buildWebExtension then "buildWeb" else "build"; npmBuildFlags = [ "--" "--standalone" "--disable-updater" ];

Discussion:
Vencord settings at Discord doesn't appear when using the override on Steps to reproduce the behavior: Set up Discord with the override on Home Manager: Be able to access the Vencord options in the Discord settings. <img width="217" alt="image" src="" Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
What version of nixpkgs are you using? This was a Vencord bug that got fixed in recent versions of Vencord. The nixpkgs-unstable should work properly as far as I am aware.
As far as I know I've set up right the unstable in my flake:
I think it may be related with , this is how i'm setting it right now:
It is possible that it doesn't work on darwin :O
There is some sort of package that reports which nixpkgs channel was use to install it? Just to be sure is not an issue on my side, by the way works just fine so overriding is not the problem by itself. Edit: I tried to install a package only available at unstable and it work so it seems that the issue is with the package. I've also check if the commands that should run with the option activated worked and after extracting the ASAR file it's just like a vanilla discord install, I've tested it before letting Discord update itself so it seems it isn't related.
I just tested this on my work MacBook, and it seems to work fine. Is it possible that you still have a previous (non-Nix) Discord version that interferes here?
No luck so far, I've removed everything with Discord in its name that reported to not be in a nix related directory. The Discord logs doen't say anything related with Vencord. I'm in a Macbook Air M2 if this helps.
That could still be a locked before the fix. When was the last time you updated that Nixpkgs input in your flake lockfile, and/or what commit is listed in the lockfile entry for Nixpkgs?
I kinda have a similar issue with overriding Vencord, whenever I try to open the settings page it crashes with the following: ! I initially expected it to be an issue with openAsar but after disabling the open asar override the error persists.

It works as expected with the vencord override disabled.
With the latest Discord updates, Vencord is currently completely broken for reasons that are unrelated to Nix.
This is caused by a breaking change from upstream Discord — see This issue should be reserved for Nix-specific problems only. Also, has the issue ever been fixed on your end? If so, I think this issue could be closed
No luck so far installing the package through Home Manager using the nixpkgs master branch.
Change:
buildFlags = "setup.data build"; <del> preBuild = "mkdir -p $out/lib/ocaml/${ocaml.version}/site-lib/cryptokit"; </del> <ins> preBuild = "mkdir -p $out/lib/ocaml/${ocaml.version}/site-lib/stublibs"; </ins> meta = { homepage = http://pauillac.inria.fr/~xleroy/software.html;

Discussion:
Ocaml programs depending on cryptokit crash at runtime, because the linker can't find the shared object file (ie it's not in ). To Reproduce and run an ocaml project that depends on cryptokit (with ) Additional context I tried refactoring the package to use , but it didn't fix the issue. Metadata system: host os: multi-user?: sandbox: version: channels(endorphin): channels(root): nixpkgs: Maintainer information:
Could you please test ? Thanks.
Yep, fixes it. Thanks
Change:
cmakeFlags = with lib; [ "-DCMAKE_BUILD_TYPE=Release" "-DBUILD_TESTING=ON" <ins> "-DUSE_LIBUDEV_OVER_LIBSYSTEMD=ON" </ins> ] ++ optional nvidia "-DNVML_INCLUDE_DIRS=${cudatoolkit}/include" ++ optional nvidia "-DNVML_LIBRARIES=${cudatoolkit}/targets/x86_64-linux/lib/stubs/libnvidia-ml.so" ++ optional (!amd) "-DAMDGPU_SUPPORT=OFF"

Discussion:
When running , I get Restarting the system did not help. Steps to reproduce the behavior: The program should launch without crashing. If applicable, add screenshots to help explain your problem.
Hello Thanks for reporting this issue, and sorry for breaking the nvtop package! I made a pull-request to fix nvtop: What do you think about this fix?
Thank you for your fast reaction ! The PR looks good to me. I hope it will get merged soon :)