jiebi/CodeConvo huggingface dataset:
Code change:
Decent Sampler is supposed to have a standalone app, a VST2 plugin and a VST3 plugin. The package decent-sampler installs only the standalone app. The downloaded archive contains also which is the VST2 plugin and the directory which is the VST3 plugin. Steps to reproduce the behavior: decent-sampler. for the VST plugins 't find them. The VST3 plugin should be installed in of the package and the VST2 plugin too should be in the package, but I don't know where exactly. <!-- 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. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: runScript = "decent-sampler"; <ins> extraInstallCommands = '' cp -r ${decent-sampler}/lib $out/lib cp -r ${decent-sampler}/share $out/share ''; </ins> meta = with lib; { description = "An audio sample player"; longDescription = ''
Code change:
, it will fail when it can't find check hydra: works, but also generates deprecation warnings. 0.9.3 (as used by Hydra) isn't an official release at Github. 0.9.4 fixes the deprecation warnings (save for flagging a future dependency and one other future.) Bump to version 0.9.4 coming momentarily. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: { lib , buildPythonPackage , cairocffi <del> , cython </del> <ins> , cython_3 </ins> , fetchPypi , igraph , leidenalg
Code change:
, it will fail when it can't find check hydra: works, but also generates deprecation warnings. 0.9.3 (as used by Hydra) isn't an official release at Github. 0.9.4 fixes the deprecation warnings (save for flagging a future dependency and one other future.) Bump to version 0.9.4 coming momentarily. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: , poetry-core , pytestCheckHook , pythonOlder <ins> , pythonRelaxDepsHook </ins> , scipy , setuptools , spacy
Code change:
, it will fail when it can't find check hydra: works, but also generates deprecation warnings. 0.9.3 (as used by Hydra) isn't an official release at Github. 0.9.4 fixes the deprecation warnings (save for flagging a future dependency and one other future.) Bump to version 0.9.4 coming momentarily. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: buildPythonPackage rec { pname = "textnets"; <del> version = "0.9.3"; </del> <ins> version = "0.9.4"; </ins> format = "pyproject"; disabled = pythonOlder "3.8"; src = fetchPypi { inherit pname version; <del> hash = "sha256-fx2S43IqpSMsfJow26jB/D27dyUFQ1PlXP1rbUIZPPQ="; </del> <ins> hash = "sha256-4154ytzo1QpwhKA1BkVMss9fNIkysnClW/yfSVlX33M="; </ins> }; nativeBuildInputs = [ <del> cython </del> <ins> pythonRelaxDepsHook cython_3 </ins> poetry-core setuptools ]; <ins> pythonRelaxDeps = [ "igraph" "leidenalg" ]; </ins> propagatedBuildInputs = [ cairocffi igraph
Code change:
, it will fail when it can't find check hydra: works, but also generates deprecation warnings. 0.9.3 (as used by Hydra) isn't an official release at Github. 0.9.4 fixes the deprecation warnings (save for flagging a future dependency and one other future.) Bump to version 0.9.4 coming momentarily. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: "textnets" ]; <ins> # Enables the package to find the cythonized .so files during testing. See #255262 preCheck = '' rm -r textnets ''; </ins> disabledTests = [ <del> # Test fails: A warning is triggered because of a deprecation notice by pandas. # TODO: Try to re-enable it when pandas is updated to 2.1.1 "test_corpus_czech" </del> <ins> # Test fails: Throws a UserWarning asking the user to install `textnets[fca]`. "test_context" </ins> ]; meta = with lib; {
Code change:
The searx service is trying to start and it fails because the actual name is of the executable has been changed to Steps to reproduce the behavior: ... use newest unstable branch ... try to deploy searx service with ... searx service fails to start searx service should start without any issues The default searx package on Nixos is in Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for reporting, I just encountered this bug as well after I updated to the latest unstable branch. I believe that a general migration from to naming needs to be done to avoid these kind of issues in the future.

Related discussion:
text: serviceConfig = { User  = "searx"; Group = "searx"; <del> ExecStart = "${cfg.package}/bin/searx-run"; </del> <ins> ExecStart = lib.getExe cfg.package; </ins> } // optionalAttrs (cfg.environmentFile != null) { EnvironmentFile = builtins.toPath cfg.environmentFile; }; environment = {
Code change:
The searx service is trying to start and it fails because the actual name is of the executable has been changed to Steps to reproduce the behavior: ... use newest unstable branch ... try to deploy searx service with ... searx service fails to start searx service should start without any issues The default searx package on Nixos is in Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for reporting, I just encountered this bug as well after I updated to the latest unstable branch. I believe that a general migration from to naming needs to be done to avoid these kind of issues in the future.

Related discussion:
text: }; # fancy setup: run in uWSGI and use nginx as proxy <del> nodes.fancy = { ... }: { </del> <ins> nodes.fancy = { config, ... }: { </ins> imports = [ ../modules/profiles/minimal.nix ]; services.searx = {
Code change:
The searx service is trying to start and it fails because the actual name is of the executable has been changed to Steps to reproduce the behavior: ... use newest unstable branch ... try to deploy searx service with ... searx service fails to start searx service should start without any issues The default searx package on Nixos is in Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for reporting, I just encountered this bug as well after I updated to the latest unstable branch. I believe that a general migration from to naming needs to be done to avoid these kind of issues in the future.

Related discussion:
text: include ${pkgs.nginx}/conf/uwsgi_params; uwsgi_pass unix:/run/searx/uwsgi.sock; ''; <del> locations."/searx/static/".alias = "${pkgs.searx}/share/static/"; </del> <ins> locations."/searx/static/".alias = "${config.services.searx.package}/share/static/"; </ins> }; # allow nginx access to the searx socket
Code change:
The searx service is trying to start and it fails because the actual name is of the executable has been changed to Steps to reproduce the behavior: ... use newest unstable branch ... try to deploy searx service with ... searx service fails to start searx service should start without any issues The default searx package on Nixos is in Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for reporting, I just encountered this bug as well after I updated to the latest unstable branch. I believe that a general migration from to naming needs to be done to avoid these kind of issues in the future.

Related discussion:
text: "${pkgs.curl}/bin/curl --fail http://localhost/searx >&2" ) fancy.succeed( <del> "${pkgs.curl}/bin/curl --fail http://localhost/searx/static/themes/oscar/js/bootstrap.min.js >&2" </del> <ins> "${pkgs.curl}/bin/curl --fail http://localhost/searx/static/themes/simple/js/leaflet.js >&2" </ins> ) ''; })
Code change:
The searx service is trying to start and it fails because the actual name is of the executable has been changed to Steps to reproduce the behavior: ... use newest unstable branch ... try to deploy searx service with ... searx service fails to start searx service should start without any issues The default searx package on Nixos is in Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for reporting, I just encountered this bug as well after I updated to the latest unstable branch. I believe that a general migration from to naming needs to be done to avoid these kind of issues in the future.

Related discussion:
text: homepage = "https://github.com/searxng/searxng"; description = "A fork of Searx, a privacy-respecting, hackable metasearch engine"; license = licenses.agpl3Plus; <ins> mainProgram = "searxng-run"; </ins> maintainers = with maintainers; [ SuperSandro2000 _999eagle ]; }; })
Code change:
Some packages, e.g. requires nodejs16 (znck/grammarly), but I cannot override the nodejs version of the package to nodejs16 because it is EOF. Steps to reproduce the behavior: nodejs version of some nodejs package by doing the error message. Allow forcing the use of EOL packages, or maybe officially state that this is not supported and mark the package as broken. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Allow forcing the use of EOL packages, or maybe officially state that this is not supported If you run: , you'll get all the instructions on how to do this. This has been marked as broken:
Sorry, I was not aware that I can get instructions when doing directly. Will do. For marking the package as broken, I mean instead of . Sorry for the bad wording.

Related discussion:
text: ''; }; <ins> grammarly-languageserver = prev.grammarly-languageserver.override (old: { meta = old.meta // { # requires EOL Node.js 16 # https://github.com/znck/grammarly/issues/334 broken = true; }; }); </ins> graphql-language-service-cli = prev.graphql-language-service-cli.override { nativeBuildInputs = [ pkgs.buildPackages.makeWrapper ]; postInstall = ''
Code change:
the PR template points to instead of Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I kindly ask you to just create the PR the next time with this really trivial change instead of creating an issue.
it's only trivial if you have experience with how github works. i had no idea the template was controlled by a file within the repo and not some option in the settings.

Related discussion:
text: Thanks a lot if you do! List of open PRs: https://github.com/NixOS/nixpkgs/pulls <del> Reviewing guidelines: https://nixos.org/manual/nixpkgs/unstable/#chap-reviewing-contributions </del> <ins> Reviewing guidelines: https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#reviewing-contributions </ins> --> ---
Code change:
Project description <!-- Describe the project a little: --The hyprland cursor format, library and utilities. Metadata homepage URL: source URL: license: BSD3 platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Related discussion:
text: <ins> { lib , stdenv , fetchFromGitHub , cmake , pkg-config , cairo , hyprlang , librsvg , libzip , nix-update-script }: stdenv.mkDerivation (finalAttrs: { pname = "hyprcursor"; version = "0.1.4"; src = fetchFromGitHub { owner = "hyprwm"; repo = "hyprcursor"; rev = "refs/tags/v${finalAttrs.version}"; hash = "sha256-m5I69a5t+xXxNMQrFuzKgPR6nrFiWDEDnEqlVwTy4C4="; }; nativeBuildInputs = [ cmake pkg-config ]; buildInputs = [ cairo hyprlang librsvg libzip ]; outputs = [ "out" "dev" "lib" ]; passthru.updateScript = nix-update-script { }; meta = { homepage = "https://github.com/hyprwm/hyprcursor"; description = "The hyprland cursor format, library and utilities"; changelog = "https://github.com/hyprwm/hyprcursor/releases/tag/v${finalAttrs.version}"; license = lib.licenses.bsd3; maintainers = with lib.maintainers; [ iynaix ]; mainProgram = "hyprcursor-util"; platforms = lib.platforms.linux; }; }) </ins>
Code change:
Sessions are not restored on startup of Firefox 30.0. . firefox. the Preference. tab, select for . and . Ctrl-Q to quit the Firefox. firefox again. Firefox opens and Opens the start page. It works for Firefox 30.0 for Mac, 30.0 for Windows, or 29.0.1 for NixOS.
I can confirm that. The good news is that your session is not lost. It looks like the UI has some issue, but the session is kept fine. So if you re-install version 29.0.1 you will have your tabs (including groups and pinned tabs) back.
I have rollbacked to 29.0.1 and the session is restored.

Related discussion:
text: import ./generic.nix ( rec { <del> version = "3.4.2"; </del> <ins> version = "3.4.4"; </ins> testing = false; preConfigure = ''
Code change:
Sessions are not restored on startup of Firefox 30.0. . firefox. the Preference. tab, select for . and . Ctrl-Q to quit the Firefox. firefox again. Firefox opens and Opens the start page. It works for Firefox 30.0 for Mac, 30.0 for Windows, or 29.0.1 for NixOS.
I can confirm that. The good news is that your session is not lost. It looks like the UI has some issue, but the session is kept fine. So if you re-install version 29.0.1 you will have your tabs (including groups and pinned tabs) back.
I have rollbacked to 29.0.1 and the session is restored.

Related discussion:
text: src = fetchurl { url = "mirror://kernel/linux/kernel/v3.x/${if testing then "testing/" else ""}linux-${version}.tar.xz"; <del> sha256 = "0pd96g1qcp2wgdnvk79hljjrpr6xjk0159lks47n181a3yirzf4x"; </del> <ins> sha256 = "0l4h7amhsmgpnii8rgwi32nd7ajsifk2xckjd39pfzwdifacw5yw"; </ins> }; config = configWithPlatform stdenv.platform;
Code change:
Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…

Related discussion:
text: , gccForLibs ? if useCcForLibs then cc else null , fortify-headers ? null , includeFortifyHeaders ? null <ins> # https://github.com/NixOS/nixpkgs/issues/295322 # should -march flag be used , disableMarch ? false </ins> }: with lib;
Code change:
Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…

Related discussion:
text: # TODO: aarch64-darwin has mcpu incompatible with gcc + optionalString ((targetPlatform ? gcc.arch) && !isClang && !(stdenv.isDarwin && stdenv.isAarch64) && <del> isGccArchSupported targetPlatform.gcc.arch) '' </del> <ins> isGccArchSupported targetPlatform.gcc.arch && !disableMarch) '' </ins> echo "-march=${targetPlatform.gcc.arch}" >> $out/nix-support/cc-cflags-before ''
Code change:
Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…

Related discussion:
text: + optionalString isClang '' # Escape twice: once for this script, once for the one it gets substituted into. export march=${lib.escapeShellArg <del> (lib.optionalString (targetPlatform ? gcc.arch) </del> <ins> (lib.optionalString (targetPlatform ? gcc.arch && !disableMarch) </ins> (lib.escapeShellArg "-march=${targetPlatform.gcc.arch}"))} export defaultTarget=${targetPlatform.config} substituteAll ${./add-clang-cc-cflags-before.sh} $out/nix-support/add-local-cc-cflags-before.sh
Code change:
Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…

Related discussion:
text: # # The following selects the correct Clang version, matching the version # used in Swift, and applies the same libc overrides as `apple_sdk.stdenv`. <del> clang = if pkgs.stdenv.isDarwin </del> <ins> clang = let # https://github.com/NixOS/nixpkgs/issues/295322 clangNoMarch = swiftLlvmPackages.clang.override { disableMarch = true; }; in if pkgs.stdenv.isDarwin </ins> then <del> swiftLlvmPackages.clang.override rec { </del> <ins> clangNoMarch.override rec { </ins> libc = apple_sdk.Libsystem; bintools = pkgs.bintools.override { inherit libc; }; # Ensure that Swift’s internal clang uses the same libc++ and libc++abi as the
Code change:
Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…

Related discussion:
text: ]; } else <del> swiftLlvmPackages.clang; </del> <ins> clangNoMarch; </ins> # Overrides that create a useful environment for swift packages, allowing # packaging with `swiftPackages.callPackage`. These are similar to
Code change:
Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…

Related discussion:
text: , gccForLibs ? if useCcForLibs then cc else null , fortify-headers ? null , includeFortifyHeaders ? null <del> # https://github.com/NixOS/nixpkgs/issues/295322 # should -march flag be used , disableMarch ? false </del> }: assert nativeTools -> !propagateDoc && nativePrefix != "";
Code change:
Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…

Related discussion:
text: # TODO: aarch64-darwin has mcpu incompatible with gcc + optionalString ((targetPlatform ? gcc.arch) && !isClang && !(stdenv.isDarwin && stdenv.isAarch64) && <del> isGccArchSupported targetPlatform.gcc.arch && !disableMarch) '' </del> <ins> isGccArchSupported targetPlatform.gcc.arch) '' </ins> echo "-march=${targetPlatform.gcc.arch}" >> $out/nix-support/cc-cflags-before ''