jiebi/CodeConvo huggingface dataset:
Change:
nordzy-cursor-theme = callPackage ../data/icons/nordzy-cursor-theme { }; inherit (callPackages ../data/fonts/noto-fonts {}) <del> noto-fonts noto-fonts-cjk noto-fonts-emoji noto-fonts-emoji-blob-bin noto-fonts-extra; </del> <ins> noto-fonts noto-fonts-cjk-sans noto-fonts-cjk-serif noto-fonts-emoji noto-fonts-emoji-blob-bin noto-fonts-extra; </ins> nuclear = callPackage ../applications/audio/nuclear { };

Discussion:
Describe the bug According to and , noto-fonts-cjk should have 14 ttc files, but noto-fonts-cjk in nixpkgs downloads from , this zip files doesn't include serif fonts. To Reproduce Steps to reproduce the behavior: -env -iA -list : family | grep 'Noto Serif CJK' Expected behavior It should output: Notify maintainers Metadata Please run and paste the result.
The nix file should download 14 .ttc files and install to target directory in a loop, it's a simple logic, but sorry I'm not familiar with Nix language yet. Mention more people involved in this file since 2020: hope this gets fixed soon, thanks!
As I recall, the issue with packaging it initially is there was no Super OTC version of the noto serif cjk font available. There still isn't a Super OTC in the repository. There is https://noto-website- from , but that URL doesn't look stable. I guess for now you could use , it is 99% the same font.
, thanks for your quick response! Although is almost same, fontconfig can’t assure it will alway be selected for document using , there are a few other popular cjk font such as Arphic PR UMing & UKai, WenQuanYi, GNU freefont, GNU unifont. Like Debian, Gentoo also packages separate ttc files. FreeBSD even packages separate otf font, I guess this can save some memory and time for applications to load a font subset. It’s a pity google doesn’t upload a single super otc file for noto serif cjk, but I guess the huge noto sans zip is uploaded to git by mistake, it’s kept there just to not break download url. So I suggest just packaging 14 separate ttc file, it’s convenient enough compared to those separate otf files. Another reminder, it’s better to also include a fontconfig configuration snippet like Debian and Gentoo.
Arch also packages separate ttc and include a fontconfig configuration file.
I marked this as stale due to inactivity. &rarr;
Still important to me.
Change:
<ins> { stdenv, fetchFromGitHub , ffmpeg , imagemagick , makeWrapper , mplayer }: stdenv.mkDerivation rec { pname = "gopro"; version = "1.0"; src = fetchFromGitHub { owner = "KonradIT"; repo = "gopro-linux"; rev = version; sha256 = "0sb9vpiadrq8g4ag828h8mvq01fg0306j0wjwkxdmwfqync1128l"; }; nativeBuildInputs = [ makeWrapper ]; installPhase = '' runHook preInstall install -Dm755 gopro -t $out/bin wrapProgram $out/bin/gopro  --prefix PATH ":" "${stdenv.lib.makeBinPath [ ffmpeg imagemagick mplayer ]}" runHook postInstall ''; meta = with stdenv.lib; { description = "Command line interface for processing media filmed on GoPro HERO 3, 4, 5, 6, and 7 cameras"; homepage = "https://github.com/KonradIT/gopro-linux"; platforms = platforms.linux; license = licenses.gpl3; maintainers = with maintainers; [ jonringer ]; }; } </ins>

Discussion:
Project description The gopro-linux is a shell script that interacts with the gopro on Linux
Change:
buildInputs = [ nettle ]; <del> # Otherwise, the shell completion files are not built cargoBuildFlags = [ "--package" "sequoia-sqv" ]; # Use a predictable target directory, to access it when installing shell # completion files. preBuild = '' export CARGO_TARGET_DIR="$(pwd)/target" ''; </del> <ins> # Install shell completion files and manual pages. Unfortunatly it is hard to # predict the paths to all of these files generated during the build, and it # is impossible to control these using `$OUT_DIR` or alike, as implied by # upstream's `build.rs`. This is a general Rust issue also discussed in # https://github.com/rust-lang/cargo/issues/9661, also discussed upstream at: # https://gitlab.com/sequoia-pgp/sequoia-wot/-/issues/56 </ins> postInstall = '' <ins> installManPage target/*/release/build/*/out/man-pages/sqv.1 </ins> installShellCompletion --cmd sqv  <del> --zsh target/_sqv  --bash target/sqv.bash  --fish target/sqv.fish </del> <ins> --zsh target/*/release/build/*/out/shell-completions/_sqv  --bash target/*/release/build/*/out/shell-completions/sqv.bash  --fish target/*/release/build/*/out/shell-completions/sqv.fish </ins> ''; doCheck = true; passthru.updateScript = nix-update-script { }; <del> meta = with lib; { </del> <ins> meta = { </ins> description = "Command-line OpenPGP signature verification tool"; homepage = "https://docs.sequoia-pgp.org/sqv/"; <del> license = licenses.gpl2Plus; maintainers = with maintainers; [ doronbehar ]; </del> <ins> license = lib.licenses.gpl2Plus; maintainers = with lib.maintainers; [ doronbehar ]; </ins> mainProgram = "sqv"; }; }

Discussion:
Steps to reproduce the behavior: Observed: Full checkPhase log (copied from Garnix): 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. --- system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The checkPhase still fails with this PR applied, but it is a different error: Error: While creating /homeless- Caused by: Permission denied (os error 13)
Thanks for the report (I thought I rebuilt it successfully before I opened the PR). Now should be ready now (the failing test is skipped, and an upstream issue was created).
Change:
stdenv.mkDerivation (edk2.setup "OvmfPkg/OvmfPkg${targetArch}.dsc" { name = "OVMF-2014-12-10"; <ins> outputs = [ "out" "fd" ]; </ins> # TODO: properly include openssl for secureBoot buildInputs = [nasm iasl] ++ stdenv.lib.optionals (secureBoot == true) [ openssl ];

Discussion:
In , I introduced support in libvirtd for UEFI VM creation. rightfully remarked that this brings closure-size up too much. Looking into OVMF shows that only 1MB out of the 114MB install size is needed to enable said UEFI VM creation. I think that we should look into splitting out OVMF_(CODE|VARS) from the rest package.
Change:
"PasswordManagerEnabled" = false; "SpellcheckEnabled" = true; "SpellcheckLanguage" = [ <del> "de" "en-US" ]; </del> <ins> "de" "en-US" ]; </ins> } ''; };

Discussion:
Describe the bug addon in chromium does not work. After install addon show errors: "Failed to connect to the main process." "Verify the installation of the plasma-browser-integration package. The running environment of the Plasma desktop environment must be at least version 5.13." "Specified native messaging host not found." Manually run from console not help. To Reproduce Steps to reproduce the behavior: Add to : Expected behavior No errors. Additional context I found issue Everything looks like the same problem but in chromium Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run nix-shell -p nix-info --run "nix-info -m" and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Try adding the following line to your configuration:
now And also does not work. Maybe I need to reboot?
That issue is actually unrelated, it has to do with a patch only in our source build of firefox.
I make test with: in . The same error.
I can't reproduce this issue. I just tested in a vm using with this configuration: Are you using plasma5?
Yes plasma5. Looks like it worked for me too. Now all errors are gone. Thanks !
Why are we adding to systemPackages when using the chromium program module? It does this for you.
Just an oversight on my part. You're right, adding chromium to systemPackages is not necessary.
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".

If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
Thanks - the fix worked for me! Can you please comment on what's the role of package that you install?
I marked this as stale due to inactivity. &rarr;
Proposed fix in
Change:
hash = "sha256-7vkw6H0ZQoHEwNusY6QWh/vPbSCdP1ZaaqABHsZH6hQ="; }; <ins> patches = [./cstdint.patch ]; </ins> nativeBuildInputs = [ pybind11 setuptools

Discussion:
This turned up in a check for a upgrade. The floret build error is unrelated to the other upgrade. The build runs normally until isn't found. is also refusing to build due to this dependency. Patching the dependency fixes the build. PR with patch forthcoming Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
, plotsSupport ? true }: <del> let # Development version of anki has bumped to beautifulsoup4 beautifulsoup = callPackage ./beautifulsoup.nix { }; qt4 = pyqt4.qt; in buildPythonApplication rec { version = "2.0.52"; </del> <ins> buildPythonApplication rec { version = "2.1.6-beta1"; </ins> name = "anki-${version}"; src = fetchurl { urls = [ <del> "https://apps.ankiweb.net/downloads/current/${name}-source.tgz" </del> <ins> "https://apps.ankiweb.net/downloads/beta/${name}-source.tgz" # "https://apps.ankiweb.net/downloads/current/${name}-source.tgz" </ins> # "http://ankisrs.net/download/mirror/${name}.tgz" # "http://ankisrs.net/download/mirror/archive/${name}.tgz" ]; <del> sha256 = "0yjyxgpk79rplz9z2r93kmlk09ari6xxfrz1cfm2yl9v8zfw1n6l"; </del> <ins> sha256 = "0yqn8qjx9dyf754jljhyyrk8mahii188nz0yifl1lr3py9sxzbsf"; </ins> }; <del> propagatedBuildInputs = [ pyqt4 sqlalchemy pyaudio beautifulsoup httplib2 send2trash ] </del> <ins> propagatedBuildInputs = [ pyqt5 sqlalchemy beautifulsoup4 send2trash pyaudio requests decorator markdown ] </ins> ++ lib.optional plotsSupport matplotlib; checkInputs = [ pytest glibcLocales nose ]; buildInputs = [ lame mplayer libpulseaudio  ]; <ins> makeWrapperArgs = [ ''--prefix PATH ':' "${lame}/bin:${mplayer}/bin"'' ]; </ins> patches = [ # Disable updated version check. ./no-version-check.patch <del> (substituteAll { src = ./fix-paths.patch; inherit lame mplayer qt4; qt4name = qt4.name; }) </del> ]; buildPhase = ''

Discussion:
With the current packaged version of Anki, downloading addons fails with an SSLCERTIFICATEVERIFYFAILED. Download any addon from the Ankiweb library. I used , but any addon causes the issue. Go to to enter the ID. Then this error shows up in a dialog box: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
The update to anki 2.1 () will close this issue, according to my testing. (Add-on downloads work perfectly.)
(oops, I'll keep it open until that PR is merged)
Given that some useful addons don't support Anki 2.1, I'd like this to be fixed for 2.0. OTOH I'm not sure how this can be done.
You can still manually install addons by dropping the files in . An example is described .
Change:
kanata-with-cmd = callPackage ../tools/system/kanata { withCmd = true; }; <ins> ksmbd-tools = callPackage ../os-specific/linux/ksmbd-tools { }; </ins> ksnip = libsForQt5.callPackage ../tools/misc/ksnip { }; kubevirt = callPackage ../tools/virtualization/kubevirt { };

Discussion:
Project description ... because if that title doesn't excite, I don't know what will... This would be the userspace side of Linux 5.15's kernel samba support (). Metadata homepage URL: source URL: license: gpl2 platforms: linux
I marked this as stale due to inactivity. &rarr;
Change:
<del> { stdenvNoCC, callPackage, fetchurl, autoPatchelfHook, unzip, openssl, lib }: let dists = { aarch64-darwin = { arch = "aarch64"; shortName = "darwin"; sha256 = "sha256-R17Ga4C6PSxfL1bz6IBjx0dYFmX93i0y8uqxG1eZKd4="; }; aarch64-linux = { arch = "aarch64"; shortName = "linux"; sha256 = "sha256-KSC4gdsJZJoPjMEs+VigVuqlUDhg4sL054WRlAbB+eA="; }; </del> <ins> { lib , stdenvNoCC , callPackage , fetchurl , autoPatchelfHook , unzip , openssl , writeShellScript , curl , jq , common-updater-scripts }: </ins> <del> x86_64-darwin = { arch = "x64"; shortName = "darwin"; sha256 = "sha256-CVqFPvZScNTudE2wgUctwGDgTyaMeN8dUNmLatcKo5M="; }; x86_64-linux = { arch = "x64"; shortName = "linux"; sha256 = "sha256-N3hGPyp9wvb7jjpaFLJcdNIRyLvegjAe+MiV2aMS1nE="; }; }; dist = dists.${stdenvNoCC.hostPlatform.system} or (throw "Unsupported system: ${stdenvNoCC.hostPlatform.system}"); in </del> stdenvNoCC.mkDerivation rec { <del> version = "0.1.11"; </del> <ins> version = "0.1.13"; </ins> pname = "bun"; <del> src = fetchurl { url = "https://github.com/Jarred-Sumner/bun-releases-for-updater/releases/download/bun-v${version}/bun-${dist.shortName}-${dist.arch}.zip"; sha256 = dist.sha256; }; </del> <ins> src = passthru.sources.${stdenvNoCC.hostPlatform.system} or (throw "Unsupported system: ${stdenvNoCC.hostPlatform.system}"); </ins> strictDeps = true; nativeBuildInputs = [ unzip ] ++ lib.optionals stdenvNoCC.isLinux [ autoPatchelfHook ];

Discussion:
Bun should have an auto-update field so that it can be automatically updated. N/A Please run and paste the result.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
# Also add symlinks for Fedora dir layout: https://src.fedoraproject.org/cgit/rpms/edk2.git/tree/edk2.spec ln -s $fd/FV/AAVMF_CODE.fd $fd/AAVMF/QEMU_EFI-pflash.raw ln -s $fd/FV/AAVMF_VARS.fd $fd/AAVMF/vars-template-pflash.raw <del> '' else '' </del> <ins> '' else if stdenv.hostPlatform.isRiscV then '' mkdir -vp $fd/FV mv -v $out/FV/RISCV_VIRT_{CODE,VARS}.fd $fd/FV/ truncate -s 32M $fd/FV/RISCV_VIRT_CODE.fd truncate -s 32M $fd/FV/RISCV_VIRT_VARS.fd '' else '' </ins> mkdir -vp $fd/FV mv -v $out/FV/OVMF{,_CODE,_VARS}.fd $fd/FV <del> ''; </del> <ins> ''); </ins> dontPatchELF = true;

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:
inherit ruby; name = "${gemName}-${version}"; gemName = "tmuxinator"; <del> version = "3.0.5"; source.sha256 = "1ycsx9mvl0jsds4igi6avxclsyl5lndh1mpj2ykvzfz26wdddg6p"; </del> <ins> version = "3.1.2"; source.sha256 = "t96v3RwBfezB644RVbTmO8i/xh1F23WQC8PBxc/msjg="; </ins> erubis = buildRubyGem rec { inherit ruby;

Discussion:
Package name: tmuxinator Latest released version: 3.1.2Current version on the unstable channel: 3.0.5 Current version on the stable/release channel: 3.0.5 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
cp -r locales resources{,.pak} $out/opt/Bitwarden popd <del> makeWrapper '${electron}/bin/electron' "$out/bin/bitwarden"  </del> <ins> makeWrapper '${lib.getExe electron}' "$out/bin/bitwarden"  </ins> --add-flags $out/opt/Bitwarden/resources/app.asar  --add-flags "''${NIXOS_OZONE_WL:+''${WAYLAND_DISPLAY:+--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations}}"  --set-default ELECTRON_IS_DEV 0 

Discussion:
When signing in to the Bitwarden, I am met with the following . I have KDE wallet turned off, and my NixOS and nixpkgs channel are both set to stable. I also have another nix machine that runs NixOS and nixpkgs on unstable and this bug does not occur despite having KDE wallet turned off there as well. Bug is potentially tied to Steps to reproduce the behavior: off KDE wallet in to Bitwarden-desktop stable. Should sign in without issue despite KDE wallet being disabled. ! A package update would be great, as my understanding is this was fixed in an update by Bitwarden devs.
Change:
rm -r "${sitePackages}/etc" installManPage man/*.[1-9] <ins> # This is a symlink to the build python version created by `updatePyExec`, seemingly to assure the same python version is used? rm $out/bin/fail2ban-python ln -s ${python3.interpreter} $out/bin/fail2ban-python </ins> '' + lib.optionalString stdenv.isLinux '' # see https://github.com/NixOS/nixpkgs/issues/4968 rm -r "${sitePackages}/usr"

Discussion:
Steps to reproduce the behavior: (qemu binfmt emulation must be enabled for armv7l-linux, otherwise a different error occurs when cross-compiling) I originally came upon this error when trying to build a NixOS SD card image with the fail2ban service enabled. The issue is related to cross-compilation. I'm not an expert, but it looks like the cross-compiled package tries to interact in some way with the host's x86_64 python package, which understandably isn't allowed, as that wouldn't work on the target system.
Shouldn't be necessary. At least one issue is that the cross target is invoked for 2to3 conversion instead of native python. I don't know how this should be fixed though. Maybe related:
Fix in
Even after applying it fails with applying Fails with the same error, So my PR does not cause it. Building with allows us to debug
Change:
<ins> { lib , stdenv , buildGoModule , darwin , fetchFromGitHub , restish , testers , xorg }: buildGoModule rec { pname = "restish"; version = "0.17.0"; src = fetchFromGitHub { owner = "danielgtaylor"; repo = "restish"; rev = "refs/tags/v${version}"; hash = "sha256-sXktiYCymoqZgEWQJHYn9KAUxtZYNCSyDyPC8D/X+Mw="; }; vendorHash = "sha256-quDHEoHVAEAnw+M0xiAd07s/EOhVUgH0T1z8TaBcbj0="; buildInputs = lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.Cocoa darwin.apple_sdk.frameworks.Kernel ] ++ lib.optionals stdenv.isLinux [ xorg.libX11 xorg.libXcursor xorg.libXi xorg.libXinerama xorg.libXrandr ]; ldflags = [ "-s" "-w" "-X=main.version=${version}" ]; preCheck = '' export HOME=$(mktemp -d) ''; passthru.tests.version = testers.testVersion { package = restish; }; meta = with lib; { description = "CLI tool for interacting with REST-ish HTTP APIs"; homepage = "https://rest.sh/"; changelog = "https://github.com/danielgtaylor/restish/releases/tag/v${version}"; license = licenses.mit; maintainers = with maintainers; [ fab ]; }; } </ins>

Discussion:
is a CLI for interacting with -ish HTTP APIs with some nice features built-in — like always having the latest API resources, fields, and operations available when they go live on the API without needing to install or update anything. Metadata homepage URL: source URL: license: mit platforms: linux, darwin, windows
Ah I didn't realise that there was an existing PR to add it
Change:
, libnotify , libdmapsharing , gnome <ins> , gobject-introspection </ins> , totem-pl-parser , tdb , json-glib

Discussion:
Rhythmbox ships a bunch of plugins that are written in Python, but they don't seem to work in Rhythmbox as it's currently packaged. Steps to reproduce the behavior: in the settings, in the plugins tab that a large number of plugins (e.g. for replaygain support) are missing Rhythmbox's Python plugins should be usable. I got some way towards fixing this with the following overlay: which at least makes the Python plugins show up in the settings menu, but enabling them fails, printing the following to xsession-errors: I tried setting as suggested in other issues related to gobject-introspection, and also adding gobject-introspection to nativeBuildInputs, but couldn't get any closer to getting the plugins working. Please run and paste the result. Maintainer information:
Have you tried adding python modules to ? Another option to try is adding to dependencies—if I understand correctly, it should have a setup hook to set env variables for python to find its libraries later.
I tried moving to propagatedBuildInputs, but it still doesn't seem to work. And buildInputs already includes in the nixpkgs derivation, right?
The error come from . I think must be patched to initialize using given PATH and PYTHONPATH or .
I'm able to take this further by wrapping rhythmbox with prefix.
Change:
marlin-calc = callPackage ../tools/misc/marlin-calc {}; <del> mathics = with python2Packages; toPythonApplication mathics; </del> masscan = callPackage ../tools/security/masscan { stdenv = gccStdenv; };

Discussion:
The mathics test does not work because: /cc (commit history)
I see the same error with on the 20.03 beta channel. I think it also happens on Master. It used to work (maybe a few weeks ago? if I have time I'll bisect).
I removing mathics.