jiebi/CodeConvo huggingface dataset:
Change:
url = "https://github.com/virt-manager/virt-manager/commit/83fcc5b2e8f2cede84564387756fe8971de72188.patch"; hash = "sha256-yEk+md5EkwYpP27u3E+oTJ8thgtH2Uy1x3JIWPBhqeE="; }) <ins> # fix crash with some cursor themes (fetchpatch { url = "https://github.com/virt-manager/virt-manager/commit/cc4a39ea94f42bc92765eb3bb56e2b7f9198be67.patch"; hash = "sha256-dw6yrMaAOnTh8Z6xJQQKmYelOkOl6EBAOfJQU9vQ8Ws="; }) </ins> ]; nativeBuildInputs = [

Discussion:
Virt-Manager throws an error when trying to create a vm, and does not create the vm Steps to reproduce the behavior: sway Virt-Manager A VM should be created ! The issue started after updating on the unstable branch and from what i can make out of the stack trace it seems like some gtk/dependency issue. I opend an issue for QEMU before because i thought that this was the problem but after trying it with i3 it worked just fine on the updated versions so i closed the issue again. Stacktraces: Error launching details.. Error starting installation.. <!-- Virt-Manager: Sway: --Nixos unstable with flakes
Okay I'm sorry i bothered you it was just me being dumb. For some reason virt-manager throws the before mentioned errors when not having a gtk-cursor theme installed. For anyone finding this issue in the future when using home-manager set:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
homepage = "https://github.com/searxng/fasttext-predict/"; license = licenses.mit; maintainers = with maintainers; [ SuperSandro2000 ]; <del> # ImportError: dynamic module does not define module export function (PyInit_fasttext_pybind) broken = stdenv.isDarwin; </del> }; }

Discussion:
The package is broken, , because it fails during on Darwin. I am uncertain if this is something that has to be fixed in , or can it be worked around in nixpkgs? Steps to reproduce the behavior: Build on macOS <!-- 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]:
can you help out here?
Change:
borgbackup = callPackage ../tools/backup/borg { }; <ins> borgmatic = callPackage ../tools/backup/borgmatic { }; </ins> boringtun = callPackage ../tools/networking/boringtun { }; # Upstream recommends qt5.12 and it doesn't build with qt5.15

Discussion:
borgmatic is simple, configuration-driven backup software for servers and workstations. Protect your files with client-side encryption. Backup your databases too. Monitor it all with integrated third-party services. Homepage: Source: License: GPL v3 () Platforms: UNIX, Linux, Darwin (I guess anywhere Python is supported)
I marked this as stale due to inactivity. &rarr;
Up!
Change:
"owner": "hashicorp", "provider-source-address": "registry.terraform.io/hashicorp/google", "repo": "terraform-provider-google", <del> "rev": "v3.47.0", "sha256": "05xb0q56y9088qbyaf3vzjm9im1s2azxffhjffjpzi0i79k0g2p0", "vendorSha256": "1h83p7ncv7b4ci7qdig7hb81zk9458fq9aqqbkryawf1w7wbaq2a", "version": "3.47.0" </del> <ins> "rev": "v3.62.0", "sha256": "0x0qp8nk88667hvlpgxrdjsgirw8iwv85gn3k9xb37a3lw7xs4qz", "vendorSha256": "0w6aavj1c4blpvsy00vz4dcj8rnxx6a586b16lqp6s1flqmlqrbi", "version": "3.62.0" </ins> }, "google-beta": { "owner": "hashicorp",

Discussion:
I'm trying to build the latest google terraform provider by overriding the existing versions, here is a reproducing the error I'm hitting: Is this possibly because the vendor/ directory was removed? I noticed this override: I'm looking for any way to build a more recent google terraform provider. Ideas?
Hi, to rephrase this as not a question - please may we have some more recent terraform providers? The current ones are quite old. I'm happy to do the work to update them but would appreciate some guidance around how these modules are meant to work - perhaps knows if this is an expected explosion due to the upstream vendor/ change? I'm not particularly familiar with go modules.
I found a solution to this, the problem occurs because "{go-modules}" is used within a string in "configurePhase". I something like this to my overlay (I'm using minio): Its far from ideal - unfortunately I can't find a way to hook and pull out the modules to push into the configure phase without copying all of the code to build the modules. It works... but its not great.
I marked this as stale due to inactivity. &rarr;
Change:
, mkDerivation , SDL2 , frei0r <ins> , ladspaPlugins </ins> , gettext , mlt , jack1

Discussion:
Shotcut in theory supports LADSPA plugins. However, LADSPA plugins are not found by Shotcut on NixOS version Install a bunch of LADSPA plugins (by listing them in ) Open Shotcut Add effects to a track Look for audio effects: no LADSPA plugins are shown Please run and paste the results.
cc maintainers
I tried to build shotcut and mlt with ladspa-sdk and set LADSPA_PATH, but did not manage to get the ladspa plugins working yet. ,-(
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 .
found out why: configure is using , which is not available, and therefore does disable ladspa. Preparing a PR.
Change:
mkdir -p $out/share mv * $out/share <del> ln -s $out/share/fluffychat $out/bin/fluffychat </del> <ins> makeWrapper "$out/share/fluffychat" "$out/bin/fluffychat"  --prefix "LD_LIBRARY_PATH" ":" "${lib.makeLibraryPath [ openssl olm ]}" </ins> FAV=$out/share/data/flutter_assets/assets/favicon.png ICO=$out/share/icons

Discussion:
Fluffychat cannot use e2e encryption in the new version. Sorry everyone, I, and the new fluffychat version, broke this. Working on the fix
Change:
{ object = pkgs.writeText "mdadm.conf" config.boot.initrd.mdadmConf; symlink = "/etc/mdadm.conf"; } <ins> { object = config.environment.etc."modprobe.d/nixos.conf".source; symlink = "/etc/modprobe.d/nixos.conf"; } { object = pkgs.stdenv.mkDerivation { name = "initrd-kmod-blacklist-ubuntu"; builder = pkgs.writeText "builder.sh" '' source $stdenv/setup target=$out ${pkgs.perl}/bin/perl -0pe 's/## file: iwlwifi.conf(.+?)##/##/s;' $src > $out ''; src = "${pkgs.kmod-blacklist-ubuntu}/modprobe.conf"; }; symlink = "/etc/modprobe.d/ubuntu.conf"; } </ins> ]; };

Discussion:
Currently, the initrd does not use/include the file generated by boot.blacklistedKernelModules & boot.extraModprobeConfig, making it impossible for NixOS to configure module parameters for any module loaded during stage 1. Notably this includes any modules needed to mount your root filesystem (e.g. lvm, zfs, etc.). Additionally it does not use/include the default blacklist in , which may have caused the issue mentioned in (based on Mathnerd314's last comment there). I have written a to fix the first part of this issue, but wanted to get some suggestions/feedback on a couple of things before submitting a pull request: my patch just duplicates from to recreate the file, but this seems like unnecessary duplication - is possible to sanely add the existing instead? was going to fix the second part of the issue as well, but found that the file by includes references to grep & xargs as part of a 'remove' option for iwlwifi. Obviously grep & xargs could be to the initrd, but as the option only applies when removing the module (which should not happen in the initrd) it would seem better to just filter that section out of the file before adding it to the initrd. You can trivially replicate this issue by adding some module to , adding a non-default parameter for it to boot.extraModprobeConfig, doing a rebuild and then rebooting - the parameter will still be the default. Thoughts?
Issue 1: you should be able to write something like to propagate the normal . Issue 2: agree it's easier to just filter them (though the initrd already has grep and xargs from busybox).
All right then, I'll change my commit in the next couple of days and submit a PR :).
Change:
''; passthru = { <del> # Instead of the vendored libraries, we propagate youtube-dl and yt-dlp via # the Python path. pythonPath = with kodi.pythonPackages; makePythonPath [ youtube-dl yt-dlp ]; </del> <ins> # Instead of the vendored libraries, we propagate yt-dlp via the Python # path. pythonPath = with kodi.pythonPackages; makePythonPath [ yt-dlp ]; </ins> }; meta = with lib; { homepage = "https://github.com/firsttris/plugin.video.sendtokodi"; <del> description = "Plays various stream sites on Kodi using youtube-dl"; </del> <ins> description = "Plays various stream sites on Kodi using yt-dlp"; </ins> license = licenses.mit; maintainers = teams.kodi.members ++ [ maintainers.pks ]; };

Discussion:
When trying to update nixos-24.05 from revision to , the check and build fail because is newly marked insecure (unstable PR: , backport PR: ). This breaks users of the package. I don't need the youtube-dl functionality and I don't wanna allow this insecure package on my system. Therefore, I'd appreciate an easier method to not depend on youtube-dl. This requires being able to build sendtokodi without youtube-dl altogether (and ensure sendtokodi does not use it). Either by default or as build option. Upstream seems to be mostly inactive, they won't help us here. Steps to reproduce the behavior: insecure packages (default behavior) to include sendtokodi on recent NixOS 24.05 ( or later) or unstable . Stable NixOS doesn't break on channel updates. Sendtokodi can be used without allowing any insecure packages. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --(the relevant nixpkgs commits/PRs are already referenced, I cannot build the config on the broken revision) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
sure code was never even used or executed in the entire life of this package in anyways, so all one has to do is remove from line and everything will be fine please go ahead and create a PR and it will be much appreciated :bow:
This isn't entirely true, as users can toggle between the two of them via a configuration. But regardless of that I agree that patching out the dependency is the right thing to do, even if it means that we will dishonor that configuration now. I've created to do so.
right, i sorta glossed over that part we should see if upstream wants to drop backend or not i suppose
Change:
src = fetchurl { # https://download.cdn.mozilla.net/pub/thunderbird/releases/ url = "mirror://mozilla/thunderbird/releases/${version}/source/thunderbird-${version}.source.tar.xz"; <del> hash = "sha256-og1Tu7PAHOqGs02jkHU291BCGuKDy1J+72v4Gsu4oDg="; </del> <ins> hash = "sha256-kn35avKqUdMix8VJrKJjSWViMLe/WnnxNasPpM7/cdM="; </ins> }; extraPostPatch = thunderbird-unwrapped.extraPostPatch or "" + /* bash */ ''

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:
{ lib , buildPythonPackage <del> , fetchpatch </del> , fetchPypi <del> , isPy3k , pytestCheckHook , coverage </del> <ins> , flit-core </ins> , ghostscript , pillow <ins> , pytestCheckHook , pythonOlder </ins> }: buildPythonPackage rec { pname = "pydyf"; <del> version = "0.1.2"; disabled = !isPy3k; </del> <ins> version = "0.5.0"; format = "pyproject"; disabled = pythonOlder "3.7"; </ins> src = fetchPypi { <del> inherit version; pname = "pydyf"; sha256 = "sha256-Hi9d5IF09QXeAlp9HnzwG73ZQiyoq5RReCvwDuF4YCw="; </del> <ins> inherit pname version; hash = "sha256-UedRrhUEA3wfwfSBURkTewEYAs1fbDU52wZsRVsUp+E="; </ins> }; <del> patches = [ # Fix tests for Ghostscript 9.56 # Remove after v0.1.3 has been released (fetchpatch { url = "https://github.com/CourtBouillon/pydyf/commit/d4c34823f1d15368753c9c26f7acc7a24fc2d979.patch"; sha256 = "sha256-2hHZW/q5CbStbpSJYbm3b23qKXANEb5jbPGQ83uHC+Q="; }) ]; </del> postPatch = '' substituteInPlace pyproject.toml  --replace "--isort --flake8 --cov --no-cov-on-fail" "" ''; <ins> nativeBuildInputs = [ flit-core ]; </ins> checkInputs = [ <del> pytestCheckHook coverage </del> ghostscript pillow <ins> pytestCheckHook ]; pythonImportsCheck = [ "pydyf" </ins> ]; meta = with lib; { <del> homepage = "https://doc.courtbouillon.org/pydyf/stable/"; </del> description = "Low-level PDF generator written in Python and based on PDF specification 1.7"; <ins> homepage = "https://doc.courtbouillon.org/pydyf/stable/"; </ins> license = licenses.bsd3; maintainers = with maintainers; [ rprecenth ]; };

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: <!-- 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: 54.3 desired version: 57.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:
sha256 = "11dzrp9q05dmvnwp4vk4ihcibqcf4xyr0ijscpi716cyy730flma"; excludes = [ "CMakeLists.txt" ]; }) <del> # Fixes for building calligra with modern poppler[-qt5] (fetchpatch { name = "poppler-22.03.0.patch"; url = "https://github.com/archlinux/svntogit-packages/raw/8f328bef497a9e3bc628e4e294c1a70b0c8b0eab/trunk/poppler-22.03.0.patch"; sha256 = "sha256-bOTnQcavXF49LIshNgzhXhyoEjzLmQJC/U7hO5P0bfY="; }) </del> # Fixes for building calligra with gcc11/c++17 (fetchpatch { name = "build_c++17_poppler.patch"; url = "https://github.com/archlinux/svntogit-packages/raw/bbbe35f97eb1033798f1cf95d427890168598199/trunk/068cd9ae.patch"; sha256 = "sha256-d9/ILwSeW+ov11DF191hzIaUafO/rjQrAeONwqDSKbA="; }) <ins> # Fixes for building calligra with modern poppler[-qt5] (fetchpatch { name = "calligra-poppler-22.03.patch"; url = "https://invent.kde.org/office/calligra/-/commit/236bacbe13739414e919de868283b0caf2df5d8a.patch"; sha256 = "sha256-9DmKPCvEFy2Cs3g7350iOCF5Vrx1HL+/8jr+Tb44CyE="; }) (fetchpatch { name = "calligra-poppler-22.04.patch"; url = "https://invent.kde.org/office/calligra/-/commit/6b75bec784c9835c78993349845d8c2ef22ec3de.patch"; sha256 = "sha256-z9/4he4x0WN2K/ZGrDAAtHF/W5X1PAtpeO6s7fgL/fA="; }) </ins> ]; postPatch = '' substituteInPlace CMakeLists.txt 

Discussion:
! Steps to reproduce the behavior: ... ... ... no fail system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
From what I looked earlier, probably due to poppler update. Here's similar stuff for inkscape:
Should be fixed by
Change:
- The module for the application firewall `opensnitch` got the ability to configure rules. Available as [services.opensnitch.rules](#opt-services.opensnitch.rules) <ins> - `services.mastodon` gained a tootctl wrapped named `mastodon-tootctl` similar to `nextcloud-occ` which can be executed from any user and switches to the configured mastodon user with sudo and sources the environment variables. </ins> - A new `virtualisation.rosetta` module was added to allow running `x86_64` binaries through [Rosetta](https://developer.apple.com/documentation/apple-silicon/about-the-rosetta-translation-environment) inside virtualised NixOS guests on Apple silicon. This feature works by default with the [UTM](https://docs.getutm.app/) virtualisation [package](https://search.nixos.org/packages?channel=unstable&show=utm&from=0&size=1&sort=relevance&type=packages&query=utm).

Discussion:
When one installs mastodon via the following minimal config: Then there is no obvious way to run tootctl. or any other login user doesn't have the executable by default, nor can this be enabled in an obvious way. is not a login user, so can't (and shouldn't?) log in as and execute . Steps to reproduce the behavior: mastodon as per minimal config above ... nope. ... nope. ... nope. ... nope. Any of: a setting such that is installed for that user an explanation in the docs what to do as a login user (probably bad idea?) Workaround: CC
I think upstream intends only to be run by the mastodon user. My way for doing that is just running and continuing in that shell. The reason why doesn't work is probably because sudo inherits PATH from the user you are coming from? I'm not sure I understand the concept of a login user enough. How would mastodon become a login user and why would that be a bad idea?
In the mastodon docs, it is described the following way: But is not possible, it gives the error They do recommend (which is what I meant by it shouldn't be a login user), but still they seem to do something different than nixos does. Maybe that's fine, and it would be helpful to document this somewhere, so people don't spend a long time trying to find it out.
This is default for almost all service users because they have no login shell. Use ` This is wrong. Sudo resets all path like variables like PATH and PYTHON PATH. Also inheriting needs to be turned on explicitly and PATH mist always ve inherited explicitly. Other services like nextcloud include a wrapper that sudos to the right user. This should be for mastodon, too.
Sounds like a good solution. Then we could make the command globally available.
That isn't? I would have expected that it is very similar to nextcloud-occ.
No currently it is only available to the mastodon user, so tootctl never gets called as the wrong user.
There is a hack in the nixos nextcloud-occ script that automatically sudoes if called by a different user. This could be adapted to tootctl I think.
Yes, this should be adapted. Changing the mastodon to a login user would not be the correct fix.
Change:
oblogout = throw "oblogout has been removed from nixpkgs, as it's archived upstream."; # added 2019-12-10 opencl-icd = ocl-icd; # added 2017-01-20 openexr_ctl = ctl; # added 2018-04-25 <del> openjpeg_2_1 = openjpeg_2; # added 2018-10-25 </del> <ins> openjpeg_1 = throw "openjpeg_1 has been removed, use openjpeg_2 instead"; # added 2021-01-24 openjpeg_2 = openjpeg; # added 2021-01-25 </ins> opensans-ttf = open-sans; # added 2018-12-04 openssh_with_kerberos = openssh; # added 2018-01-28 onnxruntime = throw "onnxruntime has been removed due to poor maintainability"; # added 2020-12-04

Discussion:
, CVSSv3=7.8 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
See also: ,
Change:
patches=$(mktemp -d) for dir in branding bugs external features misc; do cp -r ${betterbird-patches}/${majVer}/$dir/*.patch $patches/ <del> # files is not in series file and duplicated with external patch [[ $dir == bugs ]] && rm $patches/1820504-optimise-grapheme-m-c.patch </del> done cp ${betterbird-patches}/${majVer}/series* $patches/ chmod -R +w $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:
libcxx = callPackage ./libc++ {}; libcxxabi = callPackage ./libc++abi.nix {}; <ins> openmp = callPackage ./openmp.nix {}; </ins> }; in self

Discussion:
In Nixpkgs 17.09, 3.9 cannot find libstdc++ headers: This does work correctly with Clang 4.0 in 17.09, or Clang 3.9 in 17.03. Setting shows that the cc-wrapper is not adding the appropriate flags pointing to libstdc++ in gcc. See above. System: NixOS 17.03 Nix version: 1.12pre Nixpkgs version: 17.09beta285. Sandboxing enabled: no
According to git-bisect, one of the following commits is causing the issue (all by
Hmm, was supposed to have fixed this, but I guess only fixed 4.0. any idea?
Really thought I already applied those changes to the other versions, must have forgotten to push or something.
Ah I see now---I should have noticed when reviewing that. While we're at it, maybe we should inject it in cc-wrapper instead of stdenv? This mirrors and keeps slimmer.
Change:
<del> { lib , stdenv , fetchFromGitHub , chafa , cmake , darwin , dbus , dconf , ddcutil , glib , hwdata , imagemagick_light , libXrandr , libdrm , libglvnd , libpulseaudio , libselinux , libsepol , libxcb , makeBinaryWrapper , networkmanager , nix-update-script , ocl-icd , opencl-headers , overrideSDK , pcre , pcre2 , pkg-config , python3 , rpm , sqlite , testers , util-linux , vulkan-loader , wayland , xfce , xorg , yyjson , zlib , rpmSupport ? false , vulkanSupport ? true , waylandSupport ? true , x11Support ? true </del> <ins> { lib, stdenv, fetchFromGitHub, chafa, cmake, darwin, dbus, dconf, ddcutil, glib, hwdata, imagemagick_light, libXrandr, libdrm, libglvnd, libpulseaudio, libselinux, libsepol, libxcb, makeBinaryWrapper, nix-update-script, ocl-icd, opencl-headers, overrideSDK, pcre, pcre2, pkg-config, python3, rpm, sqlite, testers, util-linux, vulkan-loader, wayland, xfce, xorg, yyjson, zlib, rpmSupport ? false, vulkanSupport ? true, waylandSupport ? true, x11Support ? true, </ins> }: let stdenv' = if stdenv.isDarwin then overrideSDK stdenv "11.0" else stdenv; in stdenv'.mkDerivation (finalAttrs: { pname = "fastfetch"; <del> version = "2.20.0"; </del> <ins> version = "2.21.0"; </ins> src = fetchFromGitHub { owner = "fastfetch-cli"; repo = "fastfetch"; rev = finalAttrs.version; <del> hash = "sha256-8N2BG9eTZpAvnc1wiG6p7GJSCPfZ+NTbz8kLGPRg5HU="; </del> <ins> hash = "sha256-1bWWwMzbzECWARhl3ULMVF5QhbvrV5ShVT382BnRGg8="; </ins> }; <del> outputs = [ "out" "man" ]; </del> <ins> outputs = [ "out" "man" ]; </ins> nativeBuildInputs = [ cmake

Discussion:
Package name: fastfetch Latest released version: 2.21.0 <!-- Search your package here: --- Current version on the unstable channel: 2.20.0 Current version on the stable/release channel: 2.13.2 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: