jiebi/CodeConvo huggingface dataset:
Change:
, openssl , wxGTK32 , gitUpdater <ins> , wrapGAppsHook </ins> }: gcc12Stdenv.mkDerivation rec {

Discussion:
(FreeFileSync:): GLib-GIO-ERROR **: 04:17:37.147: No GSettings schemas are installed on the system zsh: trace trap (core dumped) FreeFileSync Steps to reproduce the behavior: on browse Opens file picker. Should be possible to fix this with wrapGAppsHook. cf. <!-- 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.
Does adding to work for you?
Yes
How does one add this in their file? Do we just add pkgs.wrapGAppsHook into our environment.systempackages?
No, it's not supposed to be used like that. You can try adding gtk3 but no guarantees because issues like this should be fixed properly.
Change:
postPatch = '' substituteInPlace src/filesys.cpp --replace "/bin/rm" "${coreutils}/bin/rm" <ins> '' + lib.optionalString stdenv.isDarwin '' sed -i '/pagezero_size/d;/fixup_bundle/d' src/CMakeLists.txt </ins> ''; <del> postInstall = '' </del> <ins> postInstall = lib.optionalString stdenv.isLinux '' </ins> mkdir -pv $out/share/minetest/games/minetest_game/ cp -rv ${sources.data}/* $out/share/minetest/games/minetest_game/ patchShebangs $out

Discussion:
minetest fails to run and reports Killed: 9 build minetest and run on macos aarch64 (I can't confirm if x86 is also broken). A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.
Change:
++ lib.optionals (stdenv.hostPlatform.system != "aarch64-darwin") [ gnumeric ] )); <del> nativeCheckInputs = with python3.pkgs; [ </del> <ins> nativeCheckInputs = with python.pkgs; [ </ins> pytestCheckHook ] ++ pythonPath;

Discussion:
Steps to reproduce the behavior: diffoscope These tests are failing Full build log at I haven't done a git bisect yet, but it built fine on and is now failing on at commit <!-- 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]:
fails on as well fwiw bisected to
Change:
<del> { jdk , runCommand , patchelf </del> <ins> { stdenv , jdk </ins> , lib , modules ? [ "java.base" ] }: let <del> jre = runCommand "${jdk.name}-jre" { nativeBuildInputs = [ patchelf ]; </del> <ins> jre = stdenv.mkDerivation { name = "${jdk.name}-minimal-jre"; version = jdk.version; </ins> buildInputs = [ jdk ]; <ins> dontUnpack = true; # Strip more heavily than the default '-S', since if you're # using this derivation you probably care about this. stripDebugFlags = [ "--strip-unneeded" ]; buildPhase = '' runHook preBuild jlink --module-path ${jdk}/lib/openjdk/jmods --add-modules ${lib.concatStringsSep "," modules} --output $out runHook postBuild ''; dontInstall = true; </ins> passthru = { home = "${jre}"; }; <del> }   '' jlink --module-path ${jdk}/lib/openjdk/jmods --add-modules ${lib.concatStringsSep "," modules} --output $out patchelf --shrink-rpath $out/bin/* $out/lib/jexec $out/lib/jspawnhelper $out/lib/*.so $out/lib/*/*.so ''; </del> <ins> }; </ins> in jre

Discussion:
Describe the bug jreminimal package does not strip jlink result file. It should strip by default to save disk space. If I run , the size goes down to 17.5MB from 232.6MB. To Reproduce Steps to reproduce the behavior: Create some derivation that uses jreminimal. jreminimal will create using jlink, though it doesn't strip the binary at all. Expected behavior jreminimal strip the binary by default to make smaller. Additional context Related GitHub issue: Related NixOS discourse discussion: I don't know how strip works. What's the difference between and ? Which one is better in this case? 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 and paste the result.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
{ lib , stdenv , fetchurl <del> , python </del> <ins> , python311Packages </ins> , makeWrapper , gawk , bash

Discussion:
The CLI tool provided by the package throws a Python related error when executed. Steps to reproduce the behavior: I expect the CLI tool to run without throwing a Python error I'm testing with nixpkgs unstable. <!-- 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]:
any chance you could have a look at the problem?
CC
Suggest you use for instead of plain , and supply the in its pythonpath - grep nixpkgs to see usage examples. Though I suggest taking note of the dependency footprint the package will add to this.
Thanks. I have created a PR with a fix that work locally for me. I won't be available for the next weeks so feel free to improve and merge it without me if you have time.
Change:
outputHashAlgo = "sha256"; outputHashMode = "recursive"; <del> outputHash = "0qx1axqr0h5zbn2z9bnb1d0rbs0vajw4p8szw34nicngnn213g7k"; </del> <ins> outputHash = "sha256-IlHuvFfkqM3O+3PPVBqUJzQXJELKGKHrmI1tdxsBpSk="; </ins> }; # Point to our local deps repo

Discussion:
Gradle 7.4 is out, see (I am one of the maintainers, this is a TODO.)
Change:
<ins> diff --git a/scripts/meson-install.sh b/scripts/meson-install.sh index 859ae81..05a1c58 100644 --- a/scripts/meson-install.sh +++ b/scripts/meson-install.sh @@ -7,5 +7,5 @@ fi BOLT_DBDIR=$1 -echo "Creating database dir: ${BOLT_DBDIR}" -mkdir -p "${DESTDIR}/${BOLT_DBDIR}" +# echo "Creating database dir: ${BOLT_DBDIR}" +# mkdir -p "${DESTDIR}/${BOLT_DBDIR}" </ins>

Discussion:
As described in , GNOME 3 needs the to handle authenticating Thunderbolt 3 devices. This is not yet packaged for NixOS. I've bolt myself but have thus far been unsuccessful. Start a Gnome 3 session Navigate to Settings → Devices → Thunderbolt Expected Results: A nice GUI as . Actual Results: An error message: ! (Note: The error message is slightly misleading. Thunderbolt 3 is supported and working on my laptop, albeit with authorization disabled, but without GNOME doesn't know that.) system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Can you share the errors you have encountered when packaging? Perhaps we can point you to solution.
Right now I'm hitting two roadblocks with bolt itself: the man pages fails somewhere inside asciidoc: I'm not sure how to get more information / further work on that. I disable manpage generation (), everything compiles and links just fine but then fails with:
Yeah, meson sometimes gives incredibly useless error messages. The problem is the build trying to install files in and , which it looks up through pkgconfig. Adding these fixes these: We'll also need to knock out as it tries to create a directory in . This fixed the build for me:
You can try to add flag to the asciidoc command in the meson file (I recommend setting to the local checkout of the project in question). As for the second error, Meson only calls when it fails to write to install destination, which means that some is probably wrong.
There ought to be a message Perhaps you can find it in build directory under if you run with .
Woohoo! ! Now I just have to: things up out how to get the systemd unit file linked out how to properly test a patch against this repo request!
We'll have to make module, something like this: Will probably need too.
Change:
<del> { lib, appimageTools, fetchurl }: </del> <ins> { lib, appimageTools, makeWrapper, fetchurl }: </ins> let pname = "altair";

Discussion:
The Altair GraphQL Client doesn't respect the common environment variable to start its Electron app in Wayland mode. Steps to reproduce the behavior: the environment variable to package () Wayland, it's only displayed through XWayland I would expect the package to respect the flag (like does and set the flags accordingly for the Altair GraphQL Client. I'm using Hyprland on .
Hey I'm not too familiar with Wayland things and am mostly on macOS these days. Can you try building from and see if it solves the issue?
Thanks, Your patch works as expected for me :tada:
Change:
sha256 = "1scbggzghkzzfqg4ky3qh7h9w87c3zya4ls5disz7dbx56is7sgw"; }; <del> outputs = [ "out" ] ++ stdenv.lib.optional perlSupport "gitweb"; </del> <ins> outputs = [ "out" ]; </ins> hardeningDisable = [ "format" ];

Discussion:
start a webserver that is mean to serve for the current repo. In order to do this, it generates an httpd config with But the expression for moves to a separate output. Run in any repo.
Hm, ok, I have fixed the path issue, but it still doesn’t work because perl has no CGI module.
Change:
owner = "GSConnect"; repo = "gnome-shell-extension-gsconnect"; rev = "v${version}"; <del> hash = "sha256-n6NbNgl+2FOhly/BeR7I6BvPOYe7leAdeAegaqhcGJU="; </del> <ins> hash = "sha256-V2L65Fz1WcJE2ENE8uNgIuVSXLDHokcgM4Caz1sOdZM="; </ins> }; patches = [

Discussion:
Package name: gnomeExtensions.gsconnect Latest released version: 56 <!-- Search your package here: --- Current version on the unstable channel: 55 Current version on the stable/release channel: 55 <!-- 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. Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This is important, as gsconnect doesn't work on 23.11 with Gnome 45.
Change:
patches = [ # The webroot is hardcoded as ./wwwroot ./change-webroot.diff <ins> # Upstream removes database migrations between versions # Restore them to avoid breaking on updates # Info: Restores migrations for versions between v0.7.1.4 and v0.7.9 # On update: check if more migrations need to be restored! # Migrations should at least allow updates from previous NixOS versions ./restore-migrations.diff </ins> ]; postPatch = '' substituteInPlace API/Services/DirectoryService.cs --subst-var out

Discussion:
After updating from kavita v0.7.1.4 to v0.7.13 via , I got a message that my user was disabled. updating at most two versions at a time because database migrations . Steps to reproduce the behavior: up older kavita version, e.g., v0.7.1.4 to v0.7.13 All migrations are handled on update. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Oof, did not realize migrations didn't work. A bit confused as to how we would go around solving this in nixpkgs. No matter what we do, it seems like it would require manual intervention by the user when choosing the correct upgrade path.
Change:
psd-tools = callPackage ../development/python-modules/psd-tools { }; psutil = callPackage ../development/python-modules/psutil { <del> inherit (pkgs.darwin.apple_sdk.frameworks) IOKit; </del> <ins> inherit (pkgs.darwin.apple_sdk.frameworks) CoreFoundation IOKit; </ins> }; psutil-home-assistant = callPackage ../development/python-modules/psutil-home-assistant { };

Discussion:
For a while now, some routines have been segfaulting on darwin. This has become more problematic recently because newer versions of make a call to , which pretty robustly segfaults on darwin. Packages that use in their tests are failing as a result. e.g. 's own tests are of course disabled because they have proven to be so problematic. We've opened some upstream issues for these problems (, ), but I'm increasingly starting to feel these are Our Bugs. The next step is probably to do some proper debugging on these segfaults, but I personally lack the motivation to learn darwin's weird debugging ecosystem (give me gdb and ELF anyday), so instead I'm documenting my findings here. Steps to reproduce the behavior: on darwin (tested x86_64, macos 10.15) When I use a pip-installed version on the same machine it succeeds: Maintainer information:
I can’t reproduce on aarch64-darwin running macOS 12.0.1. I tried both the aarch64 and x86_64 builds of Python. (Not saying this isn’t a problem, but it may be that it’s dependent on the macOS version being run.)
~That is an interesting data point, because I'm quite certain that our uses a much newer SDK version.~ Hold on, I think we've miscommunicated, the pip method works for me too - I suppose listing it as the expected behaviour is unclear. Let me reword.
Does the first of my two snippets fail on your system?
Sorry, yeah. I also tested that first but only posted the second results. Here’s what I get with the first snippet.
I just tested the x86_64-darwin binaries on my aarch64-darwin system and got the crash.
Ok so it is still potentially SDK-version-related.
This sounds very similar to the problem in . I wonder if it's related.
I had a look at this when it was mentioned on matrix. From what I can tell the crash occurs as soon as psutil tries to interact with CoreFoundation types returned from querying the system. I did some printf style debugging by adding calls to , and all I could get was a crash. I suspect it's related to mixing and matching system CoreFoundation with swift-corefoundation built from source.

I haven't gotten to the bottom of the issue yet, but if psutil is explicitly linked with system CoreFoundation[1], then it seems to work. that forces the the linker to use system corefoundation. <details<summarycomparison</summaryWithout: With </details
how to resolve the issue?
Not sure if related I am getting this error
I also got same error on our CI (linux armd64) with . Is there a workaround for this?
Closing because of which is supposed to address this. And I can't reproduce on x86_64-darwin.
Change:
<ins> { lib, czkawka, makeWrapper, symlinkJoin, # configurable options extraPackages ? [ ], }: symlinkJoin { name = "czkawka-wrapped-${czkawka.version}"; inherit (czkawka) pname version outputs; nativeBuildInputs = [ makeWrapper ]; paths = [ czkawka ]; postBuild = '' ${lib.concatMapStringsSep "n" ( output: "ln --symbolic --no-target-directory ${czkawka.${output}} $${output}" ) (lib.remove "out" czkawka.outputs)} pushd $out/bin for f in *; do rm -v $f makeWrapper ${lib.getBin czkawka}/bin/$f $out/bin/$f  --prefix PATH ":" "${lib.makeBinPath extraPackages}" done popd ''; meta = czkawka.meta; } </ins>

Discussion:
The czkawka package is missing ffmpeg as a dependency. If ffmpeg is not found you get this error when trying to compare video files: Ignore the snap part, it throws this error when it can't find ffmpeg, regardless if snap or not. 't have ffmpeg installed on you system. comparing videos in czkawka throws error ffmpeg error. Just works. No error. Just works. First issue I've reported here, hopefully I'm doing this right. <!-- 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]:
Before I propose any changes, let me know a thing or two. When you install both ffmpeg and czkawka, then czkawka finds ffmpeg, correct?
Correct. It finds it no problem.
Change:
platforms = [ "x86_64-linux" ]; maintainers = with maintainers; [ nand0p atemu ]; license = licenses.gpl3Only; <del> broken = cudaSupport; </del> }; }

Discussion:
Describe the bug I'm not sure what's exactly going on here, but it looks like the build is attempting to use gcc10 includes from somewhere, while the default nvcc from cudatoolkit only supports gcc9 at best. Maybe someone better versed with how cmake works on NixOS could take a look? To Reproduce Steps to reproduce the behavior: to build from nixpkgs (). Expected behavior The package builds successfully with CUDA support. Additional context Persists after version bump Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Maintainer information:
Change:
buildPythonPackage rec { pname = "certbot"; <del> version = "2.4.0"; </del> <ins> version = "2.6.0"; </ins> src = fetchFromGitHub { owner = pname; repo = pname; rev = "refs/tags/v${version}"; <del> hash = "sha256-BQsdhlYABZtz5+SORiCVnWMZdMmiWGM9W1YLqObyFo8="; </del> <ins> hash = "sha256-CbYamk1+NvcyS6w7pOjpD5lqWHCk+VJqF9R3xYxzpQk="; </ins> }; sourceRoot = "${src.name}/${pname}";

Discussion:
When I try to request new certificates I get a : New certificates Please run and paste the result. on nixos-unstable
duplicate of (by 2 minutes :grin:)
Change:
buildInputs = [ breeze-icons <del> breeze-qt5 </del> <ins> breeze </ins> qqc2-desktop-style yt-dlp

Discussion:
Package name: haruna Latest released version: 1.0.1 <!-- Search your package here: --- Current version on the unstable channel: 0.12.3 Current version on the stable/release channel: 0.12.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]:
Change:
stdenv.mkDerivation (finalAttrs: { pname = "calibre"; <del> version = "7.7.0"; </del> <ins> version = "7.8.0"; </ins> src = fetchurl { url = "https://download.calibre-ebook.com/${finalAttrs.version}/calibre-${finalAttrs.version}.tar.xz"; <del> hash = "sha256-+kz3Fz1RDQ+ROgv7y0WNAWvIESKvHKID8UnSeCh8yA4="; </del> <ins> hash = "sha256-FxYuQzzuaWZihSsmeJc6ssG3VBr2YNEi3TkXyyymLUQ="; </ins> }; patches = [

Discussion:
Package name: calibre Latest released version: 7.8.0 <!-- Search your package here: --- Current version on the unstable channel: 7.7.0 Current version on the stable/release channel: 7.0.0 Notify maintainers Changelog: https://calibre- 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:
<ins> { config, lib, pkgs, ... }: with lib; let cfg = config.services.ananicy; configFile = pkgs.writeText "ananicy.conf" (generators.toKeyValue { } cfg.settings); extraRules = pkgs.writeText "extraRules" cfg.extraRules; servicename = if ((lib.getName cfg.package) == (lib.getName pkgs.ananicy-cpp)) then "ananicy-cpp" else "ananicy"; in { options = { services.ananicy = { enable = mkEnableOption "Ananicy, an auto nice daemon"; package = mkOption { type = types.package; default = pkgs.ananicy; defaultText = literalExpression "pkgs.ananicy"; example = literalExpression "pkgs.ananicy-cpp"; description = '' Which ananicy package to use. ''; }; settings = mkOption { type = with types; attrsOf (oneOf [ int bool str ]); default = { }; example = { apply_nice = false; }; description = '' See <link xlink:href="https://github.com/Nefelim4ag/Ananicy/blob/master/ananicy.d/ananicy.conf"/> ''; }; extraRules = mkOption { type = types.str; default = ""; description = '' Extra rules in json format on separate lines. See: <link xlink:href="https://github.com/Nefelim4ag/Ananicy#configuration"/> <link xlink:href="https://gitlab.com/ananicy-cpp/ananicy-cpp/#global-configuration"/> ''; example = literalExpression '' ''' { "name": "eog", "type": "Image-View" } { "name": "fdupes", "type": "BG_CPUIO" } ''' ''; }; }; }; config = mkIf cfg.enable { environment = { systemPackages = [ cfg.package ]; etc."ananicy.d".source = pkgs.runCommandLocal "ananicyfiles" { } '' mkdir -p $out # ananicy-cpp does not include rules or settings on purpose cp -r ${pkgs.ananicy}/etc/ananicy.d/* $out rm $out/ananicy.conf cp ${configFile} $out/ananicy.conf ${optionalString (cfg.extraRules != "") "cp ${extraRules} $out/nixRules.rules"} ''; }; # ananicy and ananicy-cpp have different default settings services.ananicy.settings = let mkOD = mkOptionDefault; in { cgroup_load = mkOD true; type_load = mkOD true; rule_load = mkOD true; apply_nice = mkOD true; apply_ioclass = mkOD true; apply_ionice = mkOD true; apply_sched = mkOD true; apply_oom_score_adj = mkOD true; apply_cgroup = mkOD true; } // (if ((lib.getName cfg.package) == (lib.getName pkgs.ananicy-cpp)) then { # https://gitlab.com/ananicy-cpp/ananicy-cpp/-/blob/master/src/config.cpp#L12 loglevel = mkOD "warn"; # default is info but its spammy cgroup_realtime_workaround = mkOD true; } else { # https://github.com/Nefelim4ag/Ananicy/blob/master/ananicy.d/ananicy.conf check_disks_schedulers = mkOD true; check_freq = mkOD 5; }); systemd = { # https://gitlab.com/ananicy-cpp/ananicy-cpp/#cgroups applies to both ananicy and -cpp enableUnifiedCgroupHierarchy = mkDefault false; packages = [ cfg.package ]; services."${servicename}" = { wantedBy = [ "default.target" ]; }; }; }; meta = { maintainers = with maintainers; [ artturin ]; }; } </ins>

Discussion:
Project description Ananicy (ANother Auto NICe daemon) — is a shell daemon created to manage processes' IO and CPU priorities, with community-driven set of rules for popular applications (anyone may add their own rule via github's pull request mechanism). It's mainly for desktop usage. Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
<ins> { lib , stdenv , symlinkJoin , prismlauncher-unwrapped , wrapQtAppsHook , qtbase  # needed for wrapQtAppsHook , qtsvg , qtwayland , xorg , libpulseaudio , libGL , glfw , openal , jdk8 , jdk17 , gamemode , msaClientID ? null , gamemodeSupport ? true , jdks ? [ jdk17 jdk8 ] , additionalLibs ? [ ] }: let prismlauncherFinal = prismlauncher-unwrapped.override { inherit msaClientID gamemodeSupport; }; in symlinkJoin { name = "prismlauncher-${prismlauncherFinal.version}"; paths = [ prismlauncherFinal ]; nativeBuildInputs = [ wrapQtAppsHook ]; buildInputs = [ qtbase qtsvg ] ++ lib.optional (lib.versionAtLeast qtbase.version "6") qtwayland; postBuild = '' wrapQtAppsHook ''; qtWrapperArgs = let libs = (with xorg; [ libX11 libXext libXcursor libXrandr libXxf86vm ]) ++ [ libpulseaudio libGL glfw openal stdenv.cc.cc.lib ] ++ lib.optional gamemodeSupport gamemode.lib ++ additionalLibs; in [ "--set LD_LIBRARY_PATH /run/opengl-driver/lib:${lib.makeLibraryPath libs}" "--prefix PRISMLAUNCHER_JAVA_PATHS : ${lib.makeSearchPath "bin/java" jdks}" # xorg.xrandr needed for LWJGL [2.9.2, 3) https://github.com/LWJGL/lwjgl/issues/128 "--prefix PATH : ${lib.makeBinPath [xorg.xrandr]}" ]; inherit (prismlauncherFinal) meta; } </ins>

Discussion:
It's common to use custom builds of GLFW with Minecraft, for things like improved Wayland support. At the moment, Prism Launcher is built and wrapped in a . This means that overriding libraries such as GLFW, that aren't actually used in the build process but rather used by prebuilt copies of Minecraft at runtime, result in a binary cache miss - triggering local a rebuild of the entire launcher. I propose that the wrapping pattern is implemented here, building the launch wrapper in a new derivation. This way, runtime dependencies can be changed without changing the hash of the launcher binary derivation.
This sounds like a good idea to me, let's do this