jiebi/CodeConvo huggingface dataset:
Change:
mkdir -p "$out/etc/bash_completion.d" cp -v $out/share/autojump/autojump.bash "$out/etc/bash_completion.d" <del> # FIXME: What's the right place for `autojump.zsh'? # This can be used as a workaround in .zshrc: # . $HOME/.nix-profile/share/autojump/autojump.zsh </del> <ins> cat <<SCRIPT > $out/bin/autojump-share #!/bin/sh # Run this script to find the autojump shared folder where all the shell # integration scripts are living. echo $out/share/autojump SCRIPT chmod +x $out/bin/autojump-share </ins> ''; meta = {

Discussion:
notes that this is a fixme.
cc
I use Nix as a package manager in Ubuntu, so I can't really test this. In Ubuntu, drops the file in , and the user is expected to change on their own.
I think the best approach would be to generate an script that returns the path to . Then it would work in the cases where it's installed in a random profile too. As long as it's on the PATH you can use
PR ^
Change:
<ins> { lib , buildPythonPackage , fetchFromGitHub , pytestCheckHook }: buildPythonPackage rec { pname = "pyuseragents"; version = "1.0.5"; src = fetchFromGitHub { owner = "Animenosekai"; repo = "useragents"; rev = "v${version}"; sha256 = "D7Qs3vsfkRH2FDkbfakrR+FfWzQFiOCQM7q9AdJavyU="; }; checkInputs = [ pytestCheckHook ]; pytestFlagsArray = [ "test.py" ]; pythonImportsCheck = [ "pyuseragents" ]; meta = with lib; { description = "Giving you a random User-Agent Header"; homepage = "https://github.com/Animenosekai/useragents"; license = with licenses; [ mit ]; maintainers = with maintainers; [ angustrau ]; }; } </ins>

Discussion:
Project description Translate, transliterate, get the language of texts in no time with the help of multiple APIs! Metadata homepage URL: source URL: license: agpl3 platforms: linux  It (most likely) runs on many platforms, but I am specifically interested in linux support.
Sweet! Thanks.
Change:
}; strategy = mkOption { <del> type = types.enum [ "history" "match_prev_cmd" ]; default = "history"; </del> <ins> type = types.listOf (types.enum [ "history" "completion" "match_prev_cmd" ]); default = [ "history" ]; </ins> description = '' <del> Set ZSH_AUTOSUGGEST_STRATEGY to choose the strategy for generating suggestions. There are currently two to choose from: </del> <ins> `ZSH_AUTOSUGGEST_STRATEGY` is an array that specifies how suggestions should be generated. The strategies in the array are tried successively until a suggestion is found. There are currently three built-in strategies to choose from: </ins> <del> * history: Chooses the most recent match. * match_prev_cmd: Chooses the most recent match whose preceding history item matches the most recently executed command (more info). Note that this strategy won't work as expected with ZSH options that don't preserve the history order such as HIST_IGNORE_ALL_DUPS or HIST_EXPIRE_DUPS_FIRST. </del> <ins> - `history`: Chooses the most recent match from history. - `completion`: Chooses a suggestion based on what tab-completion would suggest. (requires `zpty` module) - `match_prev_cmd`: Like `history`, but chooses the most recent match whose preceding history item matches the most recently executed command. Note that this strategy won't work as expected with ZSH options that don't preserve the history order such as `HIST_IGNORE_ALL_DUPS` or `HIST_EXPIRE_DUPS_FIRST`. </ins> ''; };

Discussion:
From Currently nixpkgs has as an . We should either have as a nix list of enums, or just a string to allow the user to specify a zsh array.
Change:
libow = callPackage ../development/libraries/libow { }; <del> libp11 = callPackage ../development/libraries/libp11 { }; </del> <ins> libp11 = callPackage ../development/libraries/libp11 { openssl = openssl_1_1; }; </ins> libpam-wrapper = callPackage ../development/libraries/libpam-wrapper { };

Discussion:
pam_p11 causes login segfault in NixOS 22.11. GDM and Gnome lock screen are also affected. Steps to reproduce the behavior: to log in on the console or run `: Bug was not present in 22.05.
Reverting does not help.
Fixed by: Can someone with commit access apply this patch?
Can you open a pull request with that patch?
I hope that NixOS can be unbureaucratic enough that PRs are not required for this kind of patch.
It's generally preferred to do basically everything through PRs, so some basic CI checks can run & maintainers can be pinged automatically. We can just self-merge though. I created containing your diff and adding a comment for explanation.
This seems to be whats causing my 22.11-beta19 install on an Alder Lake 12700H (no gpu) to not boot into GDM. This is a pretty heinous issue that should be tested for. The graphical installer doesn't install Vim, WPA_Supplicant or anything useful for figuring out what went wrong, despite having Vim and WPA Supplicant available on the installation media/calamares.
Well I just did - you're welcome. That's what beta releases are for, aren't they?
Change:
, tpmSupport ? false , tlsSupport ? false , debug ? false <del> , sourceDebug ? debug </del> <ins> # Usually, this option is broken, do not use it except if you know what you are # doing. , sourceDebug ? false </ins> }: assert csmSupport -> seabios != null;

Discussion:
Steps to reproduce the behavior: pkgsCross.aarch64-multiplatform.edk2 Full log here: Few last lines: EDK2 package was updated in nixpkgs, and after that cross-compilation from x86_64 to aarch64 stopped working. The issue appeared in latest update commit: The package has no maintainers set in meta. The breaking change was introduced by: I see cross-compilation fixes have been made previously by: Other contributors who have contributed over the past year, I got from and : "Sandro Jäckel" and Please run and paste the result.
Actually I had binfmt for aarch64-linux emulated, I disabled it and now build fails even earlier when it tries to run antlr built for aarch64-linux:
Unable to reproduce: I just cross compiled EDK2 with .
Wait, I had a dinosaur nixpkgs there on a feature branch, testing again.
I concur, antlr is trying to be executed but it's not a binary for the right platform. This seems to be a breakage upstream as they seem to ship their own ANTLR binaries.
I won't have time to tackle it as I have too much on my plate right now.
Any change on looking at this now as we are going towards NixOS 23.11?
Thank you!
Change:
runHook preInstall install -Dt $out/bin bin/* ln -sf $out/nim/bin/nim $out/bin/nim <ins> ln -sf $out/nim/lib $out/lib </ins> ./install.sh $out runHook postInstall '';

Discussion:
Running on any file results in the following error: . Looking at the store path of , the library files are located under instead of . Steps to reproduce the behavior: or runs on the specified file
I have a quick and dirty fix here - ; probably better to fix the root cause as to why nimsuggest expects the stdlibrary to be at that particular path though
can I cherry-pick to a PR?
- sure, please do
Change:
githubId = 772914; name = "Mikael Voss"; }; <ins> mwolfe = { email = "corp@m0rg.dev"; github = "m0rg-dev"; githubId = 38578268; name = "Morgan Wolfe"; }; </ins> maxwilson = { email = "nixpkgs@maxwilson.dev"; github = "mwilsoncoding";

Discussion:
The package PySolFC is broken: It does not even start but throws an exception. Looks like noone has ever tested this. :( -shell -p pysolfc .py Traceback (most recent call last): File "/nix/store/y3xs17qmzs898jyjcbp9vbcj2kkjqhgz-PySolFC-", line 37, in <modulefrom import main # noqa: E402,I202 File "/nix/store/y3xs17qmzs898jyjcbp9vbcj2kkjqhgz-PySolFC-2.6.4/lib/python3.9/site-", line 30, in <modulefrom import Application File "/nix/store/y3xs17qmzs898jyjcbp9vbcj2kkjqhgz-PySolFC-2.6.4/lib/python3.9/site-", line 31, in <modulefrom import GAMEDB, GI, loadGame File "/nix/store/y3xs17qmzs898jyjcbp9vbcj2kkjqhgz-PySolFC-2.6.4/lib/python3.9/site-", line 28, in <modulefrom pysollib.mfxutil import Struct, printerr File "/nix/store/y3xs17qmzs898jyjcbp9vbcj2kkjqhgz-PySolFC-2.6.4/lib/python3.9/site-", line 146, in <moduleuclock = AttributeError: module 'time' has no attribute 'clock'
Just ran into this as well. Looks like was removed in Python 3.8, but also the version of PySolFC in is three and a half years (and ten minor versions) old so decent chance bumping the package version takes care of it
Change:
<del> --- ./test_prctl.py	2018-01-26 16:02:52.000000000 -0500 +++ ./test_prctl.py	2018-06-21 18:26:43.370065009 -0400 @@ -154,6 +154,7 @@ prctl.set_keepcaps(False) self.assertEqual(prctl.get_keepcaps(), False) +    @unittest.skip("No access to /proc in the Nix build sandbox") @require('set_mce_kill') def test_mce_kill(self): """Test the MCE_KILL setting""" @@ -173,6 +174,7 @@ prctl.set_name(name) self.assertEqual(prctl.get_name(), name[:15]) +    @unittest.skip("The Nix build sandbox has no_new_privs already enabled") @require('get_no_new_privs') def test_no_new_privs(self): """Test the no_new_privs function""" @@ -189,6 +191,7 @@ self.assertNotEqual(sp.returncode, 0) os._exit(0) +    @unittest.skip("No access to /proc in the Nix build sandbox") def test_proctitle(self): """Test setting the process title, including too long titles""" title = "This is a test!" @@ -225,6 +228,7 @@ os._exit(0) self.assertRaises(OSError, prctl.set_ptracer, new_pid) +    @unittest.skip("The Nix build sandbox has seccomp already enabled") @require('get_seccomp') def test_seccomp(self): """Test manipulation of the seccomp setting""" </del>

Discussion:
Describe the bug Recently, started failing to build due to a test failure in . To Reproduce Steps to reproduce the behavior: Expected behavior Should build succesfully Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(kira): nixpkgs: Maintainer information:
The failure seems to be caused by the recent upgrade:
Change:
mkdir build pushd build cmake -G "Unix Makefiles" . ../third_party/ycmd/cpp -DPYTHON_LIBRARIES:PATH=${python}/lib/libpython2.7.so -DPYTHON_INCLUDE_DIR:PATH=${python}/include/python2.7 -DUSE_CLANG_COMPLETER=ON -DUSE_SYSTEM_LIBCLANG=ON <del> make ycm_support_libs -j''${NIX_BUILD_CORES} -l''${NIX_BUILD_CORES}} </del> <ins> make ycm_core -j''${NIX_BUILD_CORES} -l''${NIX_BUILD_CORES}} </ins> ${python}/bin/python ../third_party/ycmd/build.py --gocode-completer --clang-completer --system-libclang popd '';

Discussion:
To make sure that we are on the same page: Kernel: (run ): System: (NixOS: , Ubuntu/Fedora: , ...): Nix version: (run ): Nixpkgs version: (run ): fails with Build succeeds Build fails
I have the same issue.
Change:
users.extraUsers = [{ name = "nm-openvpn"; uid = config.ids.uids.nm-openvpn; <ins> } { # to enable link-local connections name = "avahi-autoipd"; uid = config.ids.uids.avahi-autoipd; </ins> }]; systemd.packages = cfg.packages;

Discussion:
To reproduce: create new (ethernet) connection, with ip4 set to link-local. When ing the connection, the following errors are thrown: An reveals the problem: I thought the following would fix it (): but this creates a new problem:
add that new user when NM is enabled in the nixos module.
Did suggestion work? I was just bitten by this issue.
Did not try it futher yet. If you want you can try it.
Change:
sha256 = "1p13b4abslq31pbgqf0bzs2ixns85yfdsm94326h2vcg0q7hqc24"; }; <del> # patchelf is needed for binaries in $out/share/samples nativeBuildInputs = [ autoPatchelfHook cmake pkgconfig ]; </del> <ins> nativeBuildInputs = [ cmake pkgconfig ]; </ins> buildInputs = [ libdrm libva libpciaccess libX11 libXau libXdmcp libpthreadstubs ]; <ins> checkInputs = [ gtest ]; cmakeFlags = [ "-DBUILD_SAMPLES=OFF" "-DBUILD_TESTS=${if doCheck then "ON" else "OFF"}" "-DUSE_SYSTEM_GTEST=ON" ]; doCheck = true; </ins> enableParallelBuild = true; meta = with stdenv.lib; {

Discussion:
Describe the bug references because is in the inputs and it patches the samples at : To Reproduce Expected behavior No reference. Additional context I'm up to patchelf binaries that we ship, but: 1) depends on intel-media-sdk and users of it shouldn't get gcc in their closure for this. 2) We don't have even to ship the samples to everyone. Maybe split the outputs? Notify maintainers . Metadata Maintainer information:
I did a quick attempt at splitting the output, but it didn't work out very well. I'll have a further look this weekend.
Interesting... it also happens when is not in the inputs. As an alternative approach to split the outputs. This seems to work: But I wonder: Why do we ship samples? Perhaps:
BTW Why did you use ? It seems the samples are build from source... I think you've meant to them? That would have had to be done with: But this also fails with the same error: Which is super . Anyway I think we should leave off the samples:
I vaguely remember that there were linking problems with the sample binaries, mostly likely due to not being put in rpath.
I've had a further look into this problem, and it looks like changing the datadir from to would solve the problem with rpath, making patchelf unnecessary. Come to think of it, I think the samples belong to in the first place, but it's only a minor annoyance we can easily change. As of why I didn't exclude the samples, I'm rather hesitant at removing features unless there's a good reason for doing so. I'm all for removing it if it does turn out to cause problems, but I'd prefer taking a different approach if I can.
Actually, it looks like there no longer is a problem with rpath, so we can safely remove without changing the build flags at all.
Correction, there still were rpath problems present and changing datadir to didn't solve the problem. There are ways to deal with this besides using , but maybe you're right and it's easier to just remove the samples at this point. For reference, I did some quick search to see what other distros are doing: Debian: packages the samples in a separate package [1] Fedora: disables the samples all together [2] It's divided, but at least we're not alone if we do remove it. [1]: [2]:
Change:
<ins> { config, pkgs, lib, ... }: with lib; let cfg = config.programs.tuxclocker; in { options.programs.tuxclocker = { enable = mkEnableOption (lib.mdDoc '' TuxClocker, a hardware control and monitoring program ''); enableAMD = mkEnableOption (lib.mdDoc '' AMD GPU controls. Sets the `amdgpu.ppfeaturemask` kernel parameter to 0xfffd7fff to enable all TuxClocker controls ''); enabledNVIDIADevices = mkOption { type = types.listOf types.int; default = [ ]; example = [ 0 1 ]; description = lib.mdDoc '' Enable NVIDIA GPU controls for a device by index. Sets the `Coolbits` Xorg option to enable all TuxClocker controls. ''; }; useUnfree = mkOption { type = types.bool; default = false; example = true; description = lib.mdDoc '' Whether to use components requiring unfree dependencies. Disabling this allows you to get everything from the binary cache. ''; }; }; config = let package = if cfg.useUnfree then pkgs.tuxclocker else pkgs.tuxclocker-without-unfree; in mkIf cfg.enable { environment.systemPackages = [ package ]; services.dbus.packages = [ package ]; # MSR is used for some features boot.kernelModules = [ "msr" ]; # https://download.nvidia.com/XFree86/Linux-x86_64/430.14/README/xconfigoptions.html#Coolbits services.xserver.config = let configSection = (i: '' Section "Device" Driver "nvidia" Option "Coolbits" "31" Identifier "Device-nvidia[${toString i}]" EndSection ''); in concatStrings (map configSection cfg.enabledNVIDIADevices); # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/include/amd_shared.h#n207 # Enable everything modifiable in TuxClocker boot.kernelParams = mkIf cfg.enableAMD [ "amdgpu.ppfeaturemask=0xfffd7fff" ]; }; } </ins>

Discussion:
Project description TuxClocker is a hardware controlling and monitoring program. TuxClocker consists of a DBus daemon and a Qt GUI that uses the daemon. It allows you to e.g. set a custom fan curve and overclock your CPU and GPU. Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
meta = with lib; { description = "Music notation and composition software"; homepage = "https://musescore.org/"; <del> license = licenses.gpl2; </del> <ins> license = licenses.gpl3Only; </ins> maintainers = with maintainers; [ vandenoever turion doronbehar ]; <ins> # Darwin requires CoreMIDI from SDK 11.3, we use the upstream built .dmg # file in ./darwin.nix in the meantime. </ins> platforms = platforms.linux; }; }

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 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: musescore <!-- The current version can be found easily with the same process as 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: 3.6.2 desired version: 4.0 <!-- 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.
Change:
meta = with lib; { description = "Simple framework for embedding Chromium-based browsers in other applications"; <del> homepage = "http://opensource.spotify.com/cefbuilds/index.html"; </del> <ins> homepage = "https://cef-builds.spotifycdn.com/index.html"; </ins> maintainers = with maintainers; [ puffnfresh ]; license = licenses.bsd3; platforms = with platforms; linux;

Discussion:
(Upstream bug, autoclosed due to NixOS not being supported: ) I get the following segv on start: This behavior was not present pre-v27.
Not sure what the issue is but removing a scene that had a browser embed in it stopped the crash. (I tried it because libcef is chrome).
Okay, I can confirm that adding a Browser scene (then quitting OBS, then opening it again) will cause a segfault. Actually adding the scene does not cause any problems, although I was unable to get it to render anything.
This is probably due to our CEF version being out of date. Currently building with a newer copy…
It was indeed our CEF version being out of date. It's practically ancient, from 2019-07-27. Building against latest gives me an OBS that doesn't crash on startup & shows stuff in the Browser source. See for the fix.
Change:
}; programs.gnupg.agent.pinentryPackage = mkDefault pkgs.pinentry-qt; <ins> programs.kde-pim.enable = mkDefault true; </ins> programs.ssh.askPassword = mkDefault "${kdePackages.ksshaskpass.out}/bin/ksshaskpass"; # Enable helpful DBus services.

Discussion:
There is currently no documentation, on how to combine the different PIM libraries, and what is needed to get a full Kontact experience. I installed all the seemingly relevant libraries, and it is still resulting in an error. I question the sense of shipping Kontact without Akonadi. Document on how to combine the different PIM libraries, and clearly stating, which one is needed in which case, and what combinations lead to what outcome. <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
We just need to figure out what's wrong and add that to the plasma6 module and maybe add a new option for it. We probably don't need and want to add explicit documentation for this.
Note to myself: We want to add an option named ` that right now only set the following but maybe more or less. To be tested. For proper testing a full log out might be necessary.
Change:
src = fetchurl ({ i686-linux = { # Don't use the Fedora27 build (as below) because there isn't one! <del> url = "http://haskell.org/ghc/dist/${version}/ghc-${version}-i386-deb9-linux.tar.xz"; </del> <ins> url = "${downloadsUrl}/${version}/ghc-${version}-i386-deb9-linux.tar.xz"; </ins> sha256 = "1p2h29qghql19ajk755xa0yxkn85slbds8m9n5196ris743vkp8w"; }; x86_64-linux = { # This is the Fedora build because it links against ncurses6 where the # deb9 one links against ncurses5, see here # https://github.com/NixOS/nixpkgs/issues/85924 for a discussion <del> url = "http://haskell.org/ghc/dist/${version}/ghc-${version}-x86_64-fedora27-linux.tar.xz"; </del> <ins> url = "${downloadsUrl}/${version}/ghc-${version}-x86_64-fedora27-linux.tar.xz"; </ins> sha256 = "18dlqm5d028fqh6ghzn7pgjspr5smw030jjzl3kq6q1kmwzbay6g"; }; aarch64-linux = { <del> url = "http://haskell.org/ghc/dist/${version}/ghc-${version}-aarch64-ubuntu18.04-linux.tar.xz"; </del> <ins> url = "${downloadsUrl}/${version}/ghc-${version}-aarch64-ubuntu18.04-linux.tar.xz"; </ins> sha256 = "11n7l2a36i5vxzzp85la2555q4m34l747g0pnmd81cp46y85hlhq"; }; x86_64-darwin = { <del> url = "http://haskell.org/ghc/dist/${version}/ghc-${version}-x86_64-apple-darwin.tar.xz"; </del> <ins> url = "${downloadsUrl}/${version}/ghc-${version}-x86_64-apple-darwin.tar.xz"; </ins> sha256 = "0s9188vhhgf23q3rjarwhbr524z6h2qga5xaaa2pma03sfqvvhfz"; }; }.${stdenv.hostPlatform.system}

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: ghc <!-- 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: desired version: <!-- 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.
Today I tried to install , but it failed at downloading : complained about hash mismatch. It seems like URL has changed.
I used the following overlay as a workaround:
Should work with .
Change:
python-gitlab = callPackage ../development/python-modules/python-gitlab { }; <del> google-cloud-sdk = callPackage ../tools/admin/google-cloud-sdk { }; google-cloud-sdk-gce = callPackage ../tools/admin/google-cloud-sdk { with-gce=true; }; </del> google-compute-engine = callPackage ../tools/virtualization/google-compute-engine { }; google-music = callPackage ../development/python-modules/google-music { };

Discussion:
Describe the bug Getting the error when trying to generate a signed URL: It is more than possible that I am doing something wrong because I can see as a dependency in , and in the output when installing the package: To Reproduce Try generating a signed URL. Expected behavior It should generate a signed URL (as described at ) Metadata Thank you for looking into this!
The same issue still exists in google-cloud-sdk-255.0.0
I'm still getting this error message when running on NixOS unstable.
I guess it's probably caused by , which replaced with in . There's a comment about this change in the PR:
can confirm the error with recent pkgs: Couldn't find it in commit history nor github discussion thread. What was the comment? Knowing the reason for this change will be helpful to open a new issue.
fixes it for but gsutil is still broken due to GoogleCloudPlatform/gsutil