jiebi/CodeConvo huggingface dataset:
Change:
substituteInPlace main.go --replace 'notify-send' ${libnotify}/bin/notify-send ''; <del> vendorSha256 = "1v4ccn7ysh8ax1nkf1v9fcgsdnz6zjyh6j6ivyljyfvma1lmcrmk"; </del> <ins> vendorSha256 = "sha256-SnjbkDPVjAnCbM2nLqBsuaPZwOmvDTKiUbi/93BlWVQ="; </ins> doCheck = false;

Discussion:
The new change to yubikey-agent breaks yubikey-agent on NixOS. The upstream library used to be and switched to This new repo is a copy of the pinentry code of gopass, but without the commit history. Unfortunately the behavior of finding the pinentry binary changed here from just returning pinentry of the variable to actually using to . returns the (hard-coded) path to the relative pinentry binary in the gnupg folder. Since there is none (and the choice of pinentry flavor is left up to the gpg-agent so it didn't concern anyone), it now fails. This is a known problem of gpgconf, and something that is probably not easily fixed. For reference, here are the somewhat related issues: , . Steps to reproduce the behavior: yubikey-agent () yubikey-agent It returns Yubikey-agent should start. I submitted an upstream PR with a small fix that allows the upstream library to fall back to the PATH pinentry when the path returned by gpgconf doesn't exist. See . If agrees with the changes, and yubikey-agent uses the new version of the library, it should work again. and Please run and paste the result. Maintainer information:
Pinentry already approved the PR. A PR for an updated yubikey-agent is underway. For anyone interested in testing this, here is the snipped I use in my to override the yubikey-agent version with the commit of the PR: and yes, it works ;-) Edit 2021-11-13: Changed Rev and sha256 to reflect changes in Yubikey PR
Thanks for the clear bug report, I don't think there's much we can do until FiloSottile/yubikey-agent is merged, and its maintainer can take months to approve PRs.
thanks for looking at the code! I updated my comment and I agree, now we wait.
Great, the upstream PR has been merged, now we just need to await a new version tag
Change:
"tree-sitter-agda" # abandoned "tree-sitter-fluent" <ins> # to unblock my update "csharp-tree-sitter" </ins> ]; ignoredTreeSitterOrgReposJson = jsonFile "ignored-tree-sitter-org-repos" ignoredTreeSitterOrgRepos;

Discussion:
Project description <!-- Describe the project a little: --I've recently watched the videos on norg and found the plugin very code. At some point though I had an error because my system was missing this treesitter grammar: It doesn't seem packaged yet (I checked unstable). Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ... Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
noip = callPackage ../tools/networking/noip { }; <del> inherit (callPackages ../applications/networking/cluster/nomad { }) </del> <ins> inherit (callPackage ../applications/networking/cluster/nomad { }) </ins> nomad nomad_1_4 nomad_1_5

Discussion:
The NixOS tests for netbox are failing to evaluate: It seems like the module tries to override the package to pass in the plugins that are configured in the module, but for some reason it's overriding the function in instead of the one in . The former doesn't have a plugins argument, so that causes this error. You can also replicate this in : I don't really know what changed to cause this to happen, as it doesn't seem like it should. Steps to reproduce the behavior: The system configuration should evaluate. <!-- 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]:
Possibly related issue with an which used to work: Ping
The thing these packages have in common seems to be that they use to pull in a few different versions into . It seems like something changed about recently.
I think you're right, That commit changes to for a bunch of packages, including citrix_workspace and netbox.
Change:
<del> { lib, stdenv, swiProlog, makeWrapper, </del> <ins> { lib, stdenv, swi-prolog, makeWrapper, </ins> fetchFromGitHub, lexiconPath ? "prolog/lexicon/clex_lexicon.pl", pname ? "ape",

Discussion:
It seems that errors with when attempting to have in . There has been no updates in the lspserver. I came across this while trying to update my systems. Currently, says , so that was the last build I had with the lsp not causing a build failure. Steps to reproduce the behavior: this expression: It seems this started happening in . Works fine on the parent commit. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It seems adding to allows it to build, it is not clear to me how is being used here as I am not familiar with how packs work in swiProlog and why made this necessary. From looking at that commit in , it appears to be something that changed upstream. This builds:
I can confirm that with 9.1.21, swi-prolog + lsp-server builds just fine, even with the latest packaging. Something must indeed have changed upstream. 9.1.22 is the first version that stops building for me. The notes that the pack system got a refactor at that point, so that's probably what is going on here, but nothing indicates a sudden need for git. If git is now necessary for pack installation (even if we already pre-cloned everything) it should be a dependency. any idea why git became necessary here?
We can resolve this with a patch to SWI-Prolog to respect in the options, then adding that option to our invocation. I submitted a PR to SWI-Prolog (SWI-Prolog/swipl-devel). If upstream merges this, we can just apply the same patch to stable.
swi-prolog 9.2.7 backported the PR mentioned above. I've modified the package definition to supply the proper flag which suppresses git use during extraPacks install.
Change:
"test_settings_restored" ]; <ins> __darwinAllowLocalNetworking = true; </ins> meta = with lib; { description = "py.test plugin for testing of Django applications"; homepage = "https://pytest-django.readthedocs.org/en/latest/";

Discussion:
fails to build on aarch64-darwin due to failing tests due to a sandbox issue. See also: Tests should pass, allowing the package build to succeed. none listed for pytest-django specifically, for django in general Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
In a case like this, would disabling these tests be appropriate? They seem to only need access to -- is that permissible in a sandboxed build?
Future self: this was fixed by adding , which seems to currently have zero mentions in the nixpkgs manual (or the nixos manual) or Defined in nix: It adds to the sandbox-exec call.
Change:
nixpkgs.hostPlatform = "aarch64-linux"; nixpkgs.buildPlatform = "aarch64-darwin"; }; <ins> withSameHostAndBuild = eval { nixpkgs.hostPlatform = "aarch64-linux"; nixpkgs.buildPlatform = "aarch64-linux"; }; </ins> ambiguous = { _file = "ambiguous.nix"; nixpkgs.hostPlatform = "aarch64-linux";

Discussion:
A clear and concise description of what the bug is. When a nixos configuration has and both set to the same string, the module defined always determines that the system is cross-compiled, even when it should not be. Steps to reproduce the behavior: a nixos config with the example configuration: building and notice that the entire world gets rebuilt since it tries to build cross-compilation toolchains A clear and concise description of what you expected to happen. I would expect that the module would determine I am not cross-compiling the nixos system and build accordingly. 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]:
Change:
}: let <del> thunderbird-unwrapped = thunderbirdPackages.thunderbird-102; </del> <ins> thunderbird-unwrapped = thunderbirdPackages.thunderbird-115; </ins> <del> version = "102.15.1"; </del> <ins> version = "115.3.2"; </ins> majVer = lib.versions.major version; betterbird-patches = fetchFromGitHub { owner = "Betterbird"; repo = "thunderbird-patches"; <del> rev = "${version}-bb41"; </del> <ins> rev = "${version}-bb15"; </ins> postFetch = '' echo "Retrieving external patches"

Discussion:
Package name: betterbird Latest released version: 115.3.2-bb15 <!-- Search your package here: --- Current version on the unstable channel: 102.15.1 Current version on the stable/release channel: 102.15.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.
Change:
"dev": true }, "node_modules/@types/node": { <del> "version": "18.19.39", "resolved": "https://registry.npmjs.org/@types/node/-/node-18.19.39.tgz", "integrity": "sha512-nPwTRDKUctxw3di5b4TfT3I0sWDiWoPQCZjXhvdkINntwr8lcoVCKsTgnXeRubKIlfnV+eN/HYk6Jb40tbcEAQ==", </del> <ins> "version": "18.19.40", "resolved": "https://registry.npmjs.org/@types/node/-/node-18.19.40.tgz", "integrity": "sha512-MIxieZHrm4Ee8XArBIc+Or9HINt2StOmCbgRcXGSJl8q14svRvkZPe7LJq9HKtTI1SK3wU8b91TjntUm7T69Pg==", </ins> "dev": true, "dependencies": { "undici-types": "~5.26.4"

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:
{ stdenv, fetchurl, libX11, libXtst, libXext, libXdamage, libXfixes, wineUnstable, makeWrapper, libXau <del> , bash, patchelf }: </del> <ins> , bash, patchelf, config }: </ins> let topath = "${wineUnstable}/bin";

Discussion:
channel is wedged and cannot advance despite successful Hydra tested builds and completed , probably due to some bug in the channel scripts, but it's not clear. One possibility is that a Nix update caused some of the NAR list files (like ) to be corrupted, but it's not clear why this is blocking the channel from advancing.
Closed by
Change:
done mkdir src/build cd src/build <ins> gappsWrapperArgs+=("--prefix" "LD_LIBRARY_PATH" ":" $LD_LIBRARY_PATH) </ins> ''; shared = if stdenv.isDarwin then "dylib" else "shared";

Discussion:
Operations like File -Open crashes DrRacket with the error EDIT: I installed from unstable Install Start Presssystem: host os: multi-user?: sandbox: version: channels(root): channels(simendsjo): nixpkgs:
I strongly suspect it needs . I can take a quick look.
Change:
''; nativeBuildInputs = [ autoPatchelfHook makeWrapper wrapQtAppsHook ]; <del> buildInputs = [ qtbase qtwebengine qtx11extras qtquickcontrols2 qtgraphicaleffects icu63 ]; </del> <ins> buildInputs = [ minizip icu63 nss ]; </ins> installPhase = '' mkdir -p $out/share/teamviewer $out/bin $out/share/applications

Discussion:
Using teamviewer with I can not connect to remote hosts. The connection is established, but the window does not appear. If i try to connect to the same host again, I receive the message that I already have a connection open. TeamViewer is working as expected on EndeavourOS. Steps to reproduce the behavior: TeamViewer to any host for password appears for connected host does not appear to the same host again "you are already connected" appears the host computer it says that Im connected It seems like its the same bug as I also get the same errors in my log file <!-- 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]:
please try the linked PR and report back if this solved your issue. Thanks
I can confirm that it work!!! :partyingface: Thanks for the fast reply :)) However, I'm now getting a commercial use restriction ! I dont know if this has anything to do with nixpkgs or if its just because I tried to connect many times now. On the teamviewer website I have requested to remove my restriction lets see how it goes ;)
yay! I am pretty sure this is independent of NixOS. I had this in the past as well (independent of NixOS). I don't know how teamviewer tries to detect commercial use. But glad to here it works!
I would really like to learn more about packaging programs for nixpkgs so I can contribute more myself. Do you have any recommendations on how to learn the different options for mkDerivation, the different phases, wrapping programs and libraries, etc.? I feel like the documentation is basically non-existend. If anything comes to mind (including workshops, etc.) feel free to just send me an email (this issue is probably the wrong place to discuss this)
Hi awesome! I'm just gonna answer you here for anyone who is also interested: There is a handbook () which has a whole chapter about contributing to There is which helps a lot (just search for it or ask a question there) It helped me a lot to look at how other packages are packed.

Just clone and look at how similar services or programs are packaged There is a matrix Generally just start small. Find some nixpkgs which you'd like to see upgraded and update the version and hash and build it locally in your nixpkgs repo and submit a pull request ;-) If you still have trouble, just ask again on discourse (Im there, too) and we'll go from there :+1:
Change:
cudaArchitecturesString = strings.concatStringsSep ";" cudaArchitectures; minArch = let <del> minArch' = builtins.head (builtins.sort builtins.lessThan cudaArchitectures); </del> <ins> minArch' = builtins.head (builtins.sort strings.versionOlder cudaArchitectures); </ins> in <del> # If this fails some day, something must've changed and we should re-validate our assumptions assert builtins.stringLength minArch' == 2; </del> # "75" -> "750"  Cf. https://bitbucket.org/icl/magma/src/f4ec79e2c13a2347eff8a77a3be6f83bc2daec20/CMakeLists.txt#lines-273 "${minArch'}0"; <ins> cuda-common-redist = with cudaPackages; [ libcublas # cublas_v2.h libcusparse # cusparse.h ]; </ins> <del> cuda_joined = symlinkJoin { name = "cuda-redist-${cudaVersion}"; </del> <ins> # Build-time dependencies cuda-native-redist = symlinkJoin { name = "cuda-native-redist-${cudaVersion}"; </ins> paths = with cudaPackages; [ <del> cuda_nvcc </del> cuda_cudart # cuda_runtime.h <del> libcublas libcusparse </del> <ins> cuda_nvcc </ins> ] ++ lists.optionals (strings.versionOlder cudaVersion "11.8") [ cuda_nvprof # <cuda_profiler_api.h> ] ++ lists.optionals (strings.versionAtLeast cudaVersion "11.8") [ cuda_profiler_api # <cuda_profiler_api.h> <del> ]; </del> <ins> ] ++ cuda-common-redist; }; # Run-time dependencies cuda-redist = symlinkJoin { name = "cuda-redist-${cudaVersion}"; paths = cuda-common-redist; </ins> }; in

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:
import ./make-test-python.nix ({ lib, pkgs, ... }: let testId = "7CFNTQM-IMTJBHJ-3UWRDIU-ZGQJFR6-VCXZ3NB-XUH3KZO-N52ITXR-LAIYUAU"; <ins> testName = "testDevice foo'bar"; </ins> in { name = "syncthing-init";

Discussion:
Configuring with special characters (like ) causes the Syncthing service to fail: Device names may be any string that Syncthing supports via its UI. Syncthing does support . (guessing based on ) system: - nixpkgs @
Could you confirm fixes the issue? would also fix it
Yep, fixes it. Thanks!
Change:
"-DCOMPILER_RT_ENABLE_IOS=OFF" ]) ++ lib.optionals (lib.versionAtLeast version "19" && stdenv.isDarwin && lib.versionOlder stdenv.hostPlatform.darwinMinVersion "10.13") [ "-DSANITIZER_MIN_OSX_VERSION=10.10" <ins> ]  ++ lib.optionals (noSanitizers && lib.versionAtLeast release_version "19") [ "-DCOMPILER_RT_BUILD_CTX_PROFILE=OFF" </ins> ]; outputs = [ "out" "dev" ];

Discussion:
Steps to reproduce the behavior: (or try building pkgsLLVM.llvmPackages_git.compiler-rt) It seems like useLLVM causes the sanitizers to be disabled, not sure why this is the case as LLVM can rebuild itself with sanitizers enabled (outside of nixpkgs). See Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Ok, removing those useLLVM checks resulted in this:
cc may be helpful.
Unable to reproduce this.
Huh. I just ran into it with the new llvmPackages_git 19 -20 update in nixpkgs Hopefully the above nix file will be allow someone to reproduce it.
That seems to still produce the same result.
Turns out this is related to .
CC since this is related to sanitizers.
It's reproducible by building at version : Building version works fine:
Interesting, I wasn't using no-libc I think but I was doing it under pkgsLLVM and on aarch64-linux. That version doesn't look right.
Really? It seems to be the . Also, I have good news! Following the , I tried adding to , and it works:
Yeah, that's two weeks ago. Git is updated every week on Sunday. The PR for this week's update worked (although it only tests LLVM to clang). Interesting, I can get on this tonight.
Change:
hydraPlatforms = []; }; deriveCran = mkDerive { <del> mkHomepage = {name, snapshot, ...}: "http://mran.revolutionanalytics.com/snapshot/${snapshot}/web/packages/${name}/"; </del> <ins> mkHomepage = {name, snapshot, ...}: "https://cran.r-project.org/${snapshot}/web/packages/${name}/"; </ins> mkUrls = {name, version, snapshot}: [ <del> "http://mran.revolutionanalytics.com/snapshot/${snapshot}/src/contrib/${name}_${version}.tar.gz" </del> <ins> "https://packagemanager.rstudio.com/cran/${snapshot}/src/contrib/${name}_${version}.tar.gz" </ins> ]; };

Discussion:
relies on MRAN mirror, which at the end of this month. Could we switch to another mirror such as CRAN/posit package manager?
We do need to switch, not just the update script but currently CRAN packages are fetched from MRAN. Official CRAN mirrors would be preferable but the organisation is not ideal as the archive tarballs are at a different path to the latest release.
is a similar service. I'm not sure if it's equivalent to MRAN. or could work
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
''; activationScript = '' <ins> ${set_XDG_CONFIG_HOME} </ins> # The KDE icon cache is supposed to update itself automatically, but it uses # the timestamp on the icon theme directory as a trigger. This doesn't work # on NixOS because the timestamp never changes. As a workaround, delete the

Discussion:
Describe the bug After upgrade to 20.03 nixos-activation.service don't start . Error log: nixos-activation.service - Run user-specific NixOS activation Loaded: loaded (/nix/store/jcv2nvwkdc4hlhfx2dcchw3xgnmgyk8n-unit-nixos-activation.service/nixos-activation.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-02-21 11:57:14 CET; 8s ago Process: ExecStart=/nix/store/6hls8gx0c7prqf6gc2s1q9kp5w57jnb4-unit-script-nixos-activation-start (code=exited, status=1/FAILURE) Main PID: (code=exited, status=1/FAILURE) lut 21 11:57:14 nixos systemd[1389]: Starting Run user-specific NixOS activation... lut 21 11:57:14 nixos 6hls8gx0c7prqf6gc2s1q9kp5w57jnb4-unit-script-nixos-activation-start[]: /nix/store/6hls8gx0c7prqf6gc2s1q9kp5w57jnb4-unit-script-nixos-activation-start: line 22: XDGCONFIGHOME: parameter null or not set lut 21 11:57:14 nixos systemd[1389]: nixos-activation.service: Main process exited, code=exited, status=1/FAILURE lut 21 11:57:14 nixos systemd[1389]: nixos-activation.service: Failed with result 'exit-code'. lut 21 11:57:14 nixos systemd[1389]: Failed to start Run user-specific NixOS activation. I am using home manager but empty profile without home manager is also broken. After switch channel to 19.09 everything is OK. To Reproduce Steps to reproduce the behavior: to 20.03 Additional context I am using KDE. Adding XDGCONFIGHOME to this file does not solve the problem completely. Service start but for ex. flatpak app not.

Metadata Please run and paste the result. nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): channels(piotrek): nixpkgs: Maintainer information:
caused by
I had this issue too, and it can be fixed by enabling this : I am not really sure why, this fix come from another issue that is plasma related.
cc
Yes, it's solve error related to XDGCONFIGHOME but flatpak app still fail to launch. Starting KeePassXC result in error: The name org.freedesktop.Accounts was not provided by any .service files. Unrelated problem? EDIT: Yes, it's
As far as I understand this is actually a workaround and not a real solution. iirc the suggested workaround was for a now fixed problem where plasma wouldn't start due to a hardcoded limit on env vars
It is indeed a workaround, sorry for the bad phrasing. I know this is a workaround for another issue that has been merged, but it has fixed the issue for me.
Change:
sonar-scanner-cli = callPackage ../tools/security/sonar-scanner-cli { }; solr = callPackage ../servers/search/solr { }; <del> solr_7 = solr; solr_8 = solr; </del> solvespace = callPackage ../applications/graphics/solvespace { };

Discussion:
, CVSSv3=9.8 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc Cc