jiebi/CodeConvo huggingface dataset:
Change:
stdenv.mkDerivation rec { pname = "sqlite-analyzer"; <del> version = "3.32.2"; </del> <ins> version = "3.32.3"; </ins> src = assert version == sqlite.version; fetchurl { url = "https://sqlite.org/2020/sqlite-src-${archiveVersion version}.zip"; <del> sha256 = "1jqhs896cvp9l399mjpbv1x2qbfvq875l1vrgnl3zc4ffdjxs9z0"; </del> <ins> sha256 = "1fgmslzf013ry3a7g2vms7zyg24gs53gfj308r6ki4inbn3g04lk"; </ins> }; nativeBuildInputs = [ unzip ];

Discussion:
, CVSSv3=9.8 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives. Cc Cc
See also: , ,

, CVSSv3=9.8 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc Cc
See also:

, CVSSv3=7.5 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc Cc

, CVSSv3=9.8 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.0 (nixos-20.03) CVSSv3=5.5 (nixos-20.03) CVSSv3=5.5 (nixos-20.03) CVSSv3=5.5 (nixos-20.03) CVSSv3=5.5 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives. Cc Cc
See also: ,

, CVSSv3=9.8 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.
See also:

, CVSSv3=9.8 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.

, CVSSv3=9.8 (nixos-20.03) CVSSv3=9.8 (nixos-20.03) CVSSv3=9.8 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=5.9 (nixos-20.03) CVSSv3=5.5 (nixos-20.03) CVSSv3=5.3 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives.
See also:

, CVSSv3=9.8 (nixos-19.09) CVSSv3=9.8 (nixos-19.09) CVSSv3=9.8 (nixos-19.09) CVSSv3=7.5 (nixos-19.09) CVSSv3=7.5 (nixos-19.09) CVSSv3=7.5 (nixos-19.09) CVSSv3=7.5 (nixos-19.09) CVSSv3=7.5 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09) CVSSv3=5.9 (nixos-19.09) CVSSv3=5.5 (nixos-19.09) CVSSv3=5.3 (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.
See also:
30.1 is also the default version in 20.03 ATM.
Change:
<del> { stdenv, fetchzip, python, pythonPackages, unzip, systemd, gamin }: </del> <ins> { stdenv, fetchzip, python, pythonPackages, unzip, gamin }: </ins> <del> let version = "0.9.1"; in </del> <ins> let version = "0.9.3"; in </ins> pythonPackages.buildPythonPackage { name = "fail2ban-${version}";

Discussion:
with current current unstable channel, the fail2ban package misses its etc path. The package hasn't been updated for some time and the out path is apparently generated by rewriting pathes in its : This suggests that the breakage might be related to the recent python packaging rework, so /cc as well as pkg maintainers
Change:
githubId = 11212268; name = "gruve-p"; }; <ins> grxnola = { github = "grxnola"; githubId = 49906709; name = "grxnola"; }; </ins> gschwartz = { email = "gsch@pennmedicine.upenn.edu"; github = "GregorySchwartz";

Discussion:
Project description is a distributed object programming environment for Guile (a Racket version is also currently maintained). It is mantained by and is built to be the core layer for building broader decentralized networking technologies. Metadata homepage URL: https://spritely.institute/goblins/ source URL: https://spritely.institute/files/releases/guile-goblins/guile-goblins- license: Apache v2 platforms: Linux, maybe Darwin, maybe Unix
Change:
<ins> --- a/dropbox.in +++ b/dropbox.in @@ -71,7 +71,7 @@ PARENT_DIR = os.path.expanduser("~") DROPBOX_DIST_PATH = "%s/.dropbox-dist" % PARENT_DIR -DROPBOXD_PATH = os.path.join(DROPBOX_DIST_PATH, "dropboxd") +DROPBOXD_PATH = "@dropboxd@" DESKTOP_FILE = "@DESKTOP_FILE_DIR@/dropbox.desktop" enc = locale.getpreferredencoding() </ins>

Discussion:
Running fails with message . system: host os: multi-user?: sandbox: version: channels(root): channels(mnacamura): nixpkgs:
I tried this patch: Then, it says It seems that the module is now visible from python but another problem has popped up.
looks like an intentional bug in the program. Try running without variable in the environment to trigger the alternative branch.
Oh, it comes from our packaging.
Change:
''; }; <ins> hardware.wirelessRegulatoryDatabase = mkOption { default = false; type = types.bool; description = '' Load the wireless regulatory database at boot. ''; }; </ins> };

Discussion:
Newer kernels (4.15+) can look for wireless regulatory info from (for us this is I think?), replacing the need for user-space helper like . (at least in the common case, I believe) <-- latest CRDA git adds note about this Not the same as the regdb, although I'm not sure the difference is as important for NiXOS'ers compared to other distributions. Info on internal:
I don't want to hijack the thread but my problem may be related. Recently, not sure why, I can't connect to an AP I previously could connect to so I suspect it's my machne (my phone can still access it), thus I've been looking at wifi information. I used to have a plain error then I while now it at least attempt to connect: so I wonder if it's expected on nixos ? NB: it's annoying all these errors when building kernels. do others have it too (I should probably look at hydras rather...
To get the file loaded, you need to add to . ` to see the files. Then you should see the following in : I haven't quite figured out what the best way to set the correct regulatory domain is however... short of just using .
oh great thanks ! that was not obvious. I was looking for a setting to set on boot as a kernel parameter but haven't found it yet. Some interesting read suggests one can embed the kernel in the db as well ?!
Something like this should work: Admittedly not ideal since it only works at module load time though.
Thanks Setting the following gives me the correct wifi config (check with ): Looking through the documents on: It seems to be a bit of a mess.... is an 'old' option, but NetworkManager has no support for setting the reg domain. I think having a module (?) might be a very good idea, and such an option should be to. ArchLinux deals with it by using a custom rule to run when is loaded ([source][al]). [al]: Another idea would be to a option, though that doesn't fix NetworkManager.
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 .
This should not be stale I think. Should NixOS just add to as default?
cc
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
pkgconfig wrapGAppsHook pythonPackages.wrapPython <ins> lndir </ins> ]; pythonPath = [ pythonPackages.wxPython ]; propagatedBuildInputs = [ pythonPackages.wxPython ]; buildInputs = [ <del> libGLU_combined zlib libX11 wxGTK pcre libXdmcp gettext glew glm libpthreadstubs </del> <ins> libGLU_combined zlib libX11 wxGTK pcre libXdmcp glew glm libpthreadstubs </ins> cairo curl openssl boost swig python ] ++ optional (oceSupport) opencascade

Discussion:
KISYSMOD and KISYS3DMOD point to missing directories. On my system they are and , respectively. Neither of these paths exist though. I do see a few other kicad-5.0.0 directories in the Nix store, but I'm not sure if I should use those (and if so, which one). the environment variables (Preferences Configure Paths...)
The library is also supposed to be at which does not exist while points to it.
Mostly fixed by . Symbols and footprints are now included, and the variables point to the correct location. We don't have the 3D models by default as they're five gigabytes, for that you need to use the derivation (which unfortunately means recompiling kicad for now).
Change:
<del> { stdenv , lib </del> <ins> { lib , stdenv </ins> , fetchurl , fetchpatch <ins> , cairo </ins> , cmake <del> , ninja , pkg-config , libiconv , libintl , zlib </del> <ins> , pcre , boost , cups-filters </ins> , curl <del> , cairo , freetype </del> , fontconfig <ins> , freetype , inkscape </ins> , lcms <ins> , libiconv , libintl </ins> , libjpeg <ins> , ninja </ins> , openjpeg <ins> , pkg-config , scribusUnstable , texlive , zlib </ins> , withData ? true, poppler_data , qt5Support ? false, qtbase ? null , introspectionSupport ? false, gobject-introspection ? null , utils ? false, nss ? null , minimal ? false , suffix ? "glib" <del> , inkscape , cups-filters , texlive , scribusUnstable </del> }: let mkFlag = optset: flag: "-DENABLE_${flag}=${if optset then "on" else "off"}"; in stdenv.mkDerivation rec { <del> name = "poppler-${suffix}-${version}"; version = "21.05.0"; # beware: updates often break cups-filters build, check texlive and scribusUnstable too! </del> <ins> pname = "poppler-${suffix}"; version = "21.06.1"; # beware: updates often break cups-filters build, check texlive and scribusUnstable too! </ins> outputs = [ "out" "dev" ]; src = fetchurl { <del> url = "${meta.homepage}/poppler-${version}.tar.xz"; sha256 = "sha256-2v1Te2gPrRIVvED8U9HzjoRJ18GFvGDVqJ4dJskNvYw="; </del> <ins> url = "https://poppler.freedesktop.org/poppler-${version}.tar.xz"; sha256 = "sha256-hrCeWgLeQAgaORbvhxHFEo6vSx/FnV+H0Oxm8E9ZXbQ="; </ins> }; nativeBuildInputs = [

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- 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! --- name: nixos.poppler <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 21.05.0 desired version: 21.06.01 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR. The current version of is causing evince to crash frequently:
Change:
<del> { lib, python3, fetchPypi }: python3.pkgs.buildPythonApplication rec { </del> <ins> { lib, fetchFromGitHub, python3, }: python3.pkgs.buildPythonApplication { </ins> pname = "pywalfox-native"; version = "2.7.4"; <del> src = fetchPypi { inherit version; pname = "pywalfox"; hash = "sha256-Wec9fic4lXT7gBY04D2EcfCb/gYoZcrYA/aMRWaA7WY="; </del> <ins> src = fetchFromGitHub { owner = "Frewacom"; repo = "pywalfox-native"; rev = "7ecbbb193e6a7dab424bf3128adfa7e2d0fa6ff9"; hash = "sha256-i1DgdYmNVvG+mZiFiBmVHsQnFvfDFOFTGf0GEy81lpE="; </ins> }; pythonImportsCheck = [ "pywalfox" ];

Discussion:
The package requires an "install" step which is not currently in the package. Attempting to perform this imperatively fails: Steps to reproduce the behavior: . . Theoretically, this should be run for the user, without the user needing to run it. I'm not sure what needs, exactly, but in any case needs to be able to be run at some point. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi! The pywalfox install isn't exactly nix/NixOS friendly + imperative in nature ... and since the only important part that it does is copying a manifest file I usually just do it myself. For example here is my personal home-manager module for inspiration I'm not exactly sure how to cover every case since for some people the path to the manifest should be (root install) and for others that either only use home-manager or just want it installed in the userspace only, which is inaccessible to simple nix setups. I could try putting it in the former path and see if it works for the latter mentioned cases I guess? I'll later try debugging the latter cases with the global path, but I remember running into issues while trying to implement this and ultimately just giving up and writing the hm module instead.
Hey and by the error message, it says the nix store is read only, perhaps you need to check the nix store permission / use root?
There's a branch on the pywalfox repo that works flawlessly on nixOS read more: I have the following snippet that builds the python package
Should be resolved, let me know if any issues persist.
Could you backport this to stable?
Change:
'' mkdir -p $TMPDIR/"${buildPackages.stdenv.cc.libc.out}/lib/locale" <ins> echo 'C.UTF-8/UTF-8 ' >> ../glibc-2*/localedata/SUPPORTED </ins> # Hack to allow building of the locales (needed since glibc-2.12) sed -i -e 's,^$(rtld-prefix) $(common-objpfx)locale/localedef,localedef --prefix='$TMPDIR',' ../glibc-2*/localedata/Makefile ''

Discussion:
Support for C.UTF-8 was to , however, not to . Including as a or during run-time may break as mentioned in and Please run and paste the results. cc
Yeah. Make sense to add it to glibcLocales too. I had the intention it would actually look in both places. But maybe this is not the case if is exported as environment variable.
Also checkout
This is fixed in staging and staging-19.03.
Great, thanks!
Change:
install -Dm755 ${./dub-to-nix.py} "$out/bin/dub-to-nix" patchShebangs "$out/bin/dub-to-nix" wrapProgram "$out/bin/dub-to-nix"  <del> --prefix PATH : ${lib.makeBinPath [ nix ]} </del> <ins> --prefix PATH : ${binPath} </ins> ''

Discussion:
fails to build a lockfile with dependencies in the format (). Here's the error: any repository whose contains a dependency that fetches from Git, e.g. , e.g. . a few moments, then see error. A generated lockfile containing the Git dependency. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for reporting this bug, I'll try to extend the lockfile logic later today, (the current one is pretty primitive, as you might have seen)
Change:
build-system = [ setuptools <del> wheel </del> cython ]; <del> dependencies = [ # https://github.com/grantjenks/py-tree-sitter-languages/issues/67 tree-sitter0_21 ]; </del> <ins> dependencies = [ tree-sitter ]; </ins> # Generate languages.so file (build won't fail without this, but tests will). preBuild = '' ${python.pythonOnBuildForHost.interpreter} build.py ''; <del> nativeCheckInputs = [ pytestCheckHook ]; </del> <ins> nativeCheckInputs = [ pytestCheckHook ]; </ins> # Without cd $out, tests fail to import the compiled cython extensions. # Without copying the ./tests/ directory to $out, pytest won't detect the # tests and run them. See also:

Discussion:
Steps to reproduce the behavior: Originally found building Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
That's not a build failure, but an evaluation failure. If you want to make not depend on , you need to figure out where does this dependency comes from, and try to remove it. The reason we disabled is documented in the code: Note that although the issue is fixed, we intentionally provide an expression for , so that we can build with it. See also: You can work around this issue by using instead, or try to be creative and make depend on the latest (and not ), by fixing the upstream issue . Good luck!
I'm closing this, as this is an upstream issue. Ideally it would have been possible to declaratively write with Nix why packages are disabled for certain Python implementation, and that would have improved the evaluation failure message you observed. I think I saw discussion about such a feature, but I can't find any links now unfortunately.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
<ins> { lib, buildNpmPackage, fetchFromGitHub, nix-update-script }: buildNpmPackage rec { pname = "terminal-stocks"; version = "1.0.14"; src = fetchFromGitHub { owner = "shweshi"; repo = pname; rev = "v${version}"; hash = "sha256-AzLMqp5t9u1ne+xCKp0dq/3V3DKJ1Ou9riAN+KqkStg="; }; npmDepsHash = "sha256-GOg6B8BWkWegxeYmlHSJjFNrb/frb6jdzjjNSGF38Zo="; dontNpmBuild = true; passthru.updateScript = nix-update-script {}; meta = with lib; { description = "Terminal based application that provides stock price information"; homepage = "https://github.com/shweshi/terminal-stocks"; maintainers = with maintainers; [ mislavzanic ]; license = licenses.mit; }; } </ins>

Discussion:
Project description Fetch stock information, market summary right in your terminal. Metadata homepage URL: source URL: license: mit linux
PR made: .
Change:
services.xserver.drivers = singleton { name = "nvidia"; modules = [ nvidia_x11.bin ]; <del> libPath = [ nvidia_x11 ]; </del> deviceSection = optionalString optimusCfg.enable '' BusID "${optimusCfg.nvidiaBusId}"

Discussion:
Proposal: Make a mesa setup-hook: find opengl programs in $out, fix rpath to point to (or ). Drop .
I'm not certain about all the consequences. It isn't just &ndash; there can also be other required things on that path, e.g. and . But I guess the packages that stop finding libs should be fixable easily by adding the reference explicitly somehow. What might also be a problem: during chrooted builds we have no , so if mesa is removed_ from rpath, I think many executables wouldn't even start due to that dependency, e.g. through libcairo. That would be worked around if we only at the beginning of rpath without removing the mesa reference.
Will this affect people using Nixpkgs outside NixOS?
it should be the same, need for creating manually, or setting another proper . The behavior should be the same as of now, except we don't need which would apply to every binary.
Closely related: there might be a change how libGL implementations are switched. So far only nvidia is known to use that interface, but it's well possible the other major players will jump in soon.
(triage) any action items?
No, just brainstorming here.
(triage) I assume this hasn’t been implemented yet?
There's , which will set RUNPATH in various dispatch libraries to look in , and I suggested dropping the global there, too.
Once I remove from , when I log in via LightDM (as supposed to SDDM or a console login), I still get this in : . Note how there's no 32-bit link and there is also the absolute path to the driver directory (which in my case does nothing because libraries are under ). I'm pretty sure it's coming from . SDDM must be unsetting it while LightDM is letting it through to the user session. We should remove this so it doesn't affect the session, and fix things as necessary by adding RUNPATH to programs that need it (X server, individual display managers, wayland stuff?). I will try with NVidia but cannot try other drivers.
I see two drivers that still rely on to override default system libraries, and .

Not only do they directly provide libraries like , , and instead of using dispatch libraries (, ), they override other system libraries: has symlinks to NixOS builds of a whole bunch of Xorg libraries (e.g. , , ). There is a comment in the package saying it makes some programs work, without explaining why. has replacements of , , and some LLVM libraries (, ). Because NixOS has patched glibc to give priority over , any program that links to one of these libraries will load the one from the AMD drivers. This can result in horrible breakage (what happens to programs that link to LLVM when they get the AMD thing?). This is so ugly and prone to break things that I think we should consider dropping both drivers. If not then we should at least go forward with dropping only for drivers that don't need it (mesa, nvidia).
Change:
<del> { lib, newScope }: </del> <ins> { lib, newScope, config }: </ins> lib.makeScope newScope (self: with self; { autopair = callPackage ./autopair.nix { }; <del> autopair-fish = callPackage ./autopair-fish.nix { }; </del> buildFishPlugin = callPackage ./build-fish-plugin.nix { }; colored-man-pages = callPackage ./colored-man-pages.nix { };

Discussion:
Currently, there are two almost identical packages for in nixpkgs. They were merged in CC
Change:
programs.geary.enable = mkDefault true; programs.gnome-disks.enable = mkDefault true; programs.gnome-terminal.enable = mkDefault true; <del> programs.evince.enable = mkDefault true; </del> programs.file-roller.enable = mkDefault true; environment.systemPackages = with pkgs // pkgs.gnome // pkgs.cinnamon; utils.removePackagesByName [

Discussion:
I have 2 clear bugs for cinnamon that I can't find a way to solve 1- not working due to missing of 2- doesn't show events due to missing of both of the issues related to Steps to reproduce the behavior: in any of the bugged apps
Change:
inherit (stdenv) buildPlatform hostPlatform; inherit (stdenv.lib) fix' extends makeOverridable; <del> inherit (haskellLib) overrideCabal getHaskellBuildInputs; </del> <ins> inherit (haskellLib) overrideCabal getBuildInputs; </ins> mkDerivationImpl = pkgs.callPackage ./generic-builder.nix { inherit stdenv;

Discussion:
now aborts with on switch between commits (last working) and (introduces the error for me) use this and Please run and paste the results.
Change:
installPhase = '' runHook preInstall <ins> install -Dm755 darkman -t $out/bin </ins> make PREFIX=$out install runHook postInstall '';

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:
, gnum4 , openssl , libxml2 <ins> , zlib </ins> }: stdenv.mkDerivation rec {

Discussion:
Steps to reproduce the behavior: to update the system with nixos-rebuild failed with message error: builder for '/nix/store/dq3k8nz8ass49r942swi73z09a20m53r-julia-' failed with exit code 2; last 10 log lines: For full logs, run 'nix log /nix/store/dq3k8nz8ass49r942swi73z09a20m53r-julia-'. Please run and paste the result.