jiebi/CodeConvo huggingface dataset:
Change:
</para> <programlisting> $ nix-build . -A nixosTests.login.driverInteractive <del> $ ./result/bin/nixos-test-driver --interactive </del> <ins> $ ./result/bin/nixos-test-driver </ins> [...] &gt;&gt;&gt; </programlisting>

Discussion:
When building an interactive test driver with and running the generated binary, the test just runs without an interactivity. Steps to reproduce the behavior: that the test just starts instead of displaying the interactive prompt. I'd expect to be dropped into the interactive prompt. cc as someone who's touched a lot.
Mostly reviews and minor additions though. Maybe broke it, but that's just a guess. Probably best to bisect with if going back to before that doesn't fix the problem.
Ah, it was broken by
Change:
strictDeps = true; buildInputs = [ ncurses ]; <ins> # https://github.com/Aloxaf/fzf-tab/issues/337 env = lib.optionalAttrs stdenv.cc.isClang { NIX_CFLAGS_COMPILE = toString [ "-Wno-error=implicit-function-declaration" "-Wno-error=implicit-int" ]; }; </ins> postConfigure = '' pushd modules ./configure --disable-gdbm --without-tcsetpgrp

Discussion:
Steps to reproduce the behavior: zsh-fzf-tab Full log here: 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]:
Sorry, the darwin one isn't mantained by me. cc: who commited fixes of fzf-tab on darwin.
There have been various succesfully builds of this recently, as even though I usually delete garbage over 14 days I have this: I guess on darwin we either need to not run , or else we need to build and install a .dylib, if fzf-tab supports that.
Change:
vttest = callPackage ../tools/misc/vttest { }; <del> wacomtablet = libsForQt514.callPackage ../tools/misc/wacomtablet { }; </del> <ins> wacomtablet = libsForQt5.callPackage ../tools/misc/wacomtablet { }; </ins> wasmer = callPackage ../development/interpreters/wasmer { };

Discussion:
Describe the bug The KDE Wacom configuration module is not working, showing "The shared library was not found": To Reproduce Steps to reproduce the behavior: KDE KDE system settings Expected behavior The configuration module should work Screenshots ! Additional context Add any other context about the problem here. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
can confirm ! system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: (was not mentioned before)
not sure if this is related to
This is still be a problem on 20.09
According to strace, the missing library file is either or . The latter is provided by , so it somehow needs to be made discoverable in the environment of kcmshell5.
Running into same problem now on 20.09.
Just to clarify, does just need backporting to 20.09, or are people still experiencing issues on master after was merged?
I think it just needs backporting, but I'm not yet familiar enough with NixOS to say for sure. I just upgraded my system to unstable and is working as expected (which I'm assuming is because of ). !
I marked this as stale due to inactivity. &rarr;
There was a PR to backport it to 20.09, but nobody reviewed it and it was closed when 20.09 went end-of-life, so I'm assuming everybody using kcm-wacomtablet is now happily running 21.05 or unstable and we can close this.
Yes, I can confirm it is working again in 21.05.
Change:
<del> { stdenv, fetchurl, cmake, boost, mysql }: </del> <ins> { stdenv , fetchurl , cmake , boost , openssl , mysql80 }: </ins> stdenv.mkDerivation rec { pname = "libmysqlconnectorcpp"; <del> version = "1.1.9"; </del> <ins> version = "8.0.19"; </ins> src = fetchurl { <del> url = "https://cdn.mysql.com/Downloads/Connector-C++/mysql-connector-c++-${version}.tar.gz"; sha256 = "1r6j17sy5816a2ld759iis2k6igc2w9p70y4nw9w3rd4d5x88c9y"; </del> <ins> url = "https://cdn.mysql.com/Downloads/Connector-C++/mysql-connector-c++-${version}-src.tar.gz"; sha256 = "fDvXTOZKkwDn1IG3aziK2VAXpSSAxpi3VVea7GLUoh4="; </ins> }; <del> buildInputs = [ cmake boost mysql ]; </del> <ins> nativeBuildInputs = [ cmake ]; </ins> <del> cmakeFlags = [ "-DMYSQL_LIB_DIR=${mysql}/lib" ]; </del> <ins> buildInputs = [ boost openssl mysql80 ]; cmakeFlags = [ # libmysqlclient is shared library "-DMYSQLCLIENT_STATIC_LINKING=false" # still needed for mysql-workbench "-DWITH_JDBC=true" ]; </ins> meta = { <del> homepage = https://dev.mysql.com/downloads/connector/cpp/; </del> <ins> homepage = "https://dev.mysql.com/downloads/connector/cpp/"; </ins> description = "C++ library for connecting to mysql servers."; license = stdenv.lib.licenses.gpl2; platforms = stdenv.lib.platforms.unix;

Discussion:
Describe the bug On , fails to build because there are lots of compiler warnings and those are treated as errors. To Reproduce Steps to reproduce the behavior: out the branch of the repo's root directory, run Expected behavior Build succeeds and a symlink is created pointing to the build result. Observed behavior <details<summaryBuild fails with the following output (click to expand)</summary</detailsand with exit code . Screenshots n/a Additional context n/a Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(das-g): nixpkgs: Maintainer information:
Change:
<del> { config, lib, pkgs, ... }: </del> <ins> { config, lib, pkgs, options, ... }: </ins> with lib; let <del> inherit (pkgs) ipfs runCommand makeWrapper; </del> cfg = config.services.ipfs; <ins> opt = options.services.ipfs; </ins> ipfsFlags = toString ([ (optionalString  cfg.autoMount                   "--mount") <del> #(optionalString  cfg.autoMigrate                 "--migrate") </del> (optionalString  cfg.enableGC                    "--enable-gc") (optionalString (cfg.serviceFdlimit != null)     "--manage-fdlimit=false") (optionalString (cfg.defaultMode == "offline")   "--offline") (optionalString (cfg.defaultMode == "norouting") "--routing=none") ] ++ cfg.extraFlags); <del> defaultDataDir = if versionAtLeast config.system.stateVersion "17.09" then "/var/lib/ipfs" else "/var/lib/ipfs/.ipfs"; # Wrapping the ipfs binary with the environment variable IPFS_PATH set to dataDir because we can't set it in the user environment wrapped = runCommand "ipfs" { buildInputs = [ makeWrapper ]; preferLocalBuild = true; } '' mkdir -p "$out/bin" makeWrapper "${ipfs}/bin/ipfs" "$out/bin/ipfs"  --set IPFS_PATH ${cfg.dataDir}  --prefix PATH : /run/wrappers/bin ''; commonEnv = { environment.IPFS_PATH = cfg.dataDir; path = [ wrapped ]; serviceConfig.User = cfg.user; serviceConfig.Group = cfg.group; }; baseService = recursiveUpdate commonEnv { wants = [ "ipfs-init.service" ]; # NB: migration must be performed prior to pre-start, else we get the failure message! preStart = optionalString cfg.autoMount '' ipfs --local config Mounts.FuseAllowOther --json true ipfs --local config Mounts.IPFS ${cfg.ipfsMountDir} ipfs --local config Mounts.IPNS ${cfg.ipnsMountDir} '' + concatStringsSep "n" (collect isString (mapAttrsRecursive (path: value: # Using heredoc below so that the value is never improperly quoted '' read value <<EOF ${builtins.toJSON value} EOF ipfs --local config --json "${concatStringsSep "." path}" "$value" '') ({ Addresses.API = cfg.apiAddress; Addresses.Gateway = cfg.gatewayAddress; Addresses.Swarm = cfg.swarmAddress; } // cfg.extraConfig)) ); serviceConfig = { ExecStart = "${wrapped}/bin/ipfs daemon ${ipfsFlags}"; Restart = "on-failure"; RestartSec = 1; } // optionalAttrs (cfg.serviceFdlimit != null) { LimitNOFILE = cfg.serviceFdlimit; }; }; </del> in { ###### interface

Discussion:
Describe the bug IPFS module should use upstream systemd files for socket-based activation. Right now we have a custom service file that is different from the one in ipfs-go 0.5.0. This is something quickly I can do. /cc
Change:
# gst_plugins needed for setup-hooks buildInputs = buildInputs ++ [ makeWrapper ] ++ gst_plugins; <del> cmakeFlags = [ "-DUSE_SYSTEM_PROJECTM=ON" ]; </del> <ins> preConfigure = '' rm -rf ext/{,lib}clementine-spotifyblob ''; cmakeFlags = [ "-DUSE_SYSTEM_PROJECTM=ON" "-DSPOTIFY_BLOB=OFF" ]; </ins> enableParallelBuilding = true;

Discussion:
Describe the bug Since some day, clementine refuse to work. I bisected the error to the commit . The error message in the terminal is: realloc(): invalid pointer fish : Tâche , './result/bin/clementine' terminée par le signal SIGABRT (Abandon) To Reproduce go to a nixpkgs git tree Expected behavior clementine start as expected 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 system: host os: multi-user?: sandbox: version: channels(root): channels(marius): nixpkgs: Maintainer information:
Looks like we are hitting here. cc
I could have sworn I tested this… let me see if I can reproduce this issue.
Yup, and reverting the projectm fix makes it run again. Hm… I was really sure I tested clementine. I don't think I'll have time to look into this properly until the weekend, so as a quick fix, you can revert the projectm update, if you want to.
Change:
<ins> From 2d6dd1c286eb57fbf968510318cafc94888b98de Mon Sep 17 00:00:00 2001 From: OPNA2608 <christoph.neidahl@gmail.com> Date: Sun, 13 Jun 2021 21:56:03 +0200 Subject: [PATCH] Darwin build fix --- gspell/Makefile.am | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/gspell/Makefile.am b/gspell/Makefile.am index 69ee421..7c58973 100644 --- a/gspell/Makefile.am +++ b/gspell/Makefile.am @@ -95,6 +95,7 @@ nodist_libgspell_core_la_SOURCES =  $(BUILT_SOURCES) libgspell_core_la_LIBADD =	 +	$(GTK_MAC_LIBS)            $(CODE_COVERAGE_LIBS) libgspell_core_la_CFLAGS =			 @@ -161,6 +162,12 @@ gspell_private_headers +=  gspell_private_c_files +=  gspell-osx.c +libgspell_core_la_CFLAGS +=  +	-xobjective-c + +libgspell_core_la_LDFLAGS +=  +	-framework Cocoa + endif # OS_OSX if HAVE_INTROSPECTION -- 2.29.3 </ins>

Discussion:
Project description CherryTree by Giuspen, currently, we are using version 0.39.4, meanwhile the latest application is on 0.99.37. There's a weird jump of version from 0.39.4 to 0.99.13. I don't know why this happens. Metadata homepage URL: source URL: license: GPL3 + platforms: Linux
Package request is the wrong issue type for this, Out-of-date package report would've been better. ! The package is sadly orphaned so there's no maintainer to ping for this.
Change:
]; }); <ins> # As a nix user, use this derivation instead of "luarocks_bootstrap" luarocks = prev.luarocks.overrideAttrs (oa: { nativeBuildInputs = oa.nativeBuildInputs ++ [ installShellFiles lua unzip ]; # cmake is just to compile packages with "cmake" buildType, not luarocks itself dontUseCmakeConfigure = true; propagatedBuildInputs = [ zip unzip cmake ]; postInstall = lib.optionalString (stdenv.buildPlatform.canExecute stdenv.hostPlatform) '' installShellCompletion --cmd luarocks  --bash <($out/bin/luarocks completion bash)  --fish <($out/bin/luarocks completion fish)  --zsh <($out/bin/luarocks completion zsh) installShellCompletion --cmd luarocks-admin  --bash <($out/bin/luarocks-admin completion bash)  --fish <($out/bin/luarocks-admin completion fish)  --zsh <($out/bin/luarocks-admin completion zsh) ''; meta = oa.meta // { mainProgram = "luarocks"; }; }); </ins> luasec = prev.luasec.overrideAttrs (oa: { externalDeps = [ { name = "OPENSSL"; dep = openssl; }

Discussion:
luarocks exists that other luarocks packages can depend on. When trying to build a rockspec that depends on luarocks with , it fails. The entry in the generated luarocks config contains an entry for luarocks, but luarocks doesn't recognise it and tries to download the package instead. I have created a repository to reproduce it with: Run A workaround is to use to generate a expression for luarocks (), and to add that package to the 's instead of the package from nixpkgs. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
thanks for creating the test repo, it's helpful. I've looked at the generated LUAROCKSCONFIG and all looks good and I think luarocks just doesn't recognize the installed luarocks because of My first thought would have been to rename the current luarocks into a luarocksbootstrap and add a generated derivation, for which we could run the tests without the cyclic dependency luarocks -busted -luarocks. While this might be the best outcome longterm, I am looking into the quickfix which would be to generate the manifest for the current luarocks
Change:
<del> { lib, stdenv, fetchurl, makeWrapper, jre , version ? "1.6" }: let versionMap = { "1.5" = { flinkVersion = "1.5.5"; sha256 = "18wqcqi3gyqd40nspih99gq7ylfs20b35f4dcrspffagwkfp2l4z"; }; "1.6" = { flinkVersion = "1.11.1"; sha256 = "0338bg2sb427c1rrf2cmsz63sz0yk6gclpli2lskq0mpx72wxpl0"; }; }; in with versionMap.${version}; </del> <ins> { lib, stdenv, fetchurl, makeWrapper, jre }: </ins> stdenv.mkDerivation rec { <del> name = "flink-${flinkVersion}"; </del> <ins> pname = "flink"; version = "1.12.1"; </ins> src = fetchurl { <del> url = "mirror://apache/flink/${name}/${name}-bin-scala_2.11.tgz"; inherit sha256; </del> <ins> url = "mirror://apache/flink/${pname}-${version}/${pname}-${version}-bin-scala_2.11.tgz"; sha256 = "146azc5wg1xby3nqz8mha959qy99z2h8032rfgs2mcl3d5rrsm2l"; </ins> }; nativeBuildInputs = [ makeWrapper ];

Discussion:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
Change:
<ins> { lib , python3Packages , fetchFromGitLab , vkbasalt }: python3Packages.buildPythonApplication rec { pname = "vkbasalt-cli"; version = "3.1.1"; src = fetchFromGitLab { owner = "TheEvilSkeleton"; repo = pname; rev = "v${version}"; sha256 = "sha256-4MFqndnvwAsqyer9kMNuCZFP/Xdl7W//AyCe7n83328="; }; postPatch = '' substituteInPlace vkbasalt/lib.py  --replace /usr ${vkbasalt} ''; pythonImportsCheck = [ "vkbasalt.lib" ]; meta = with lib; { description = "Command-line utility for vkBasalt"; homepage = "https://gitlab.com/TheEvilSkeleton/vkbasalt-cli"; license = with licenses; [ lgpl3Only gpl3Only ]; maintainers = with maintainers; [ martfont ]; }; } </ins>

Discussion:
error when creating a bottle Steps to reproduce the behavior: bottles to create a new bottle during dxvk installation process with the following error message No error when trying to create a bottle ! I'm pretty new to nixos so it might be a configuration error on my part I apologize in advanced if I tagged the wrong maintainers
It should be fixed in (I don't reproduce it there). (I think it's caused by the fact I )
gotcha. feel free to close if you think it's gonna be fixed in next release. thanks :)
Change:
installFlags = [ "INSTALL_ROOT=$(out)" ] ++ optional withDocumentation "install_docs"; <ins> qtWrapperArgs = [ "--set-default PERFPROFILER_PARSER_FILEPATH ${lib.getBin perf}/bin" ]; </ins> preConfigure = '' substituteInPlace src/plugins/plugins.pro  --replace '$$[QT_INSTALL_QML]/QtQuick/Controls' '${qtquickcontrols}/${qtbase.qtQmlPrefix}/QtQuick/Controls'

Discussion:
Describe the bug Qt Creator profiling tools are not working because of a missing prerequisite: . To Reproduce Steps to reproduce the behavior: Qt Creator with a simple C/C++ project the Analyze menu choose the Performance Analyzer command get the following error: is indeed missing. Expected behavior The program gets profiled. Notify maintainers Metadata Please run and paste the result.
For what it's worth, on a different distro I had this same problem which was resolved by installing elfutils-devel and then recompiling qt-creator. The build silently skips building this tool if this dependency is absent.
I marked this as stale due to inactivity. &rarr;
still an issue
would you be able to point me in the general direction of making this happen on NixOS?
Test
I still get "Could not start the perfparser utility program. Make sure a working Perf parser is available at the location given by the PERFPROFILERPARSERFILEPATH environment variable."
try now
updated, cancel the build and try again
... I still get "Could not start the perfparser utility program. Make sure a working Perf parser is available at the location given by the PERFPROFILERPARSERFILEPATH environment variable." What am I doing wrong?
Which channel are you following, if unstable then have you updated
I'm using from (which is the first commit that includes the patch)
try this
It still doesn't work for me :(
looks like perfparser is actually a program built by qtcreator i've switched the pr to be a update pr so that we get perfparser
Change:
platforms = []; source = { remotes = ["https://rubygems.org"]; <del> sha256 = "18zbsr03drpx7mknm927i2kz5b49s0lwmrbmsdknfa674z0xy6sm"; </del> <ins> sha256 = "0hf9y5lbi1xcadc2fw87wlif75s1359c2wwlvvd0gag7cq5dm0pm"; </ins> type = "gem"; }; <del> version = "0.19.0"; </del> <ins> version = "0.23.1"; </ins> }; }

Discussion:
The fusuma program in the package of the same name crashes when trying to run it. The breaking change causing this issue was made somewhere in the last 56 days: That's when I last updated this particular host, after which everything was still working fine. Steps to reproduce the behavior: "fusuma" package to run fusuma I expected fusuma to start running and be available for use. N/A Instead of displaying the expected behavior, the program crashes: In addition, if I clone the repo, then open a and run the cloned project in that nix-shell, that runs successfully unmodified on the same host. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks especially for the celerity of the fix!
Is there supposed to be a delay between this merge and availability updating? I can clearly see this PR is merged, but when I update my system the new version isn't in there.
Yes, see
One month later, I don't see the updated package. How long can this take ?
The update is already on master, but I don't think it's been backported yet. Are you on NixOS 23.11 instead of unstable?
Yes.
Backported in , should take a few days to land.
Many thanks for the commit !
Change:
<del> { stdenv, lib, fetchurl, callPackage, substituteAll, python3, pkgconfig </del> <ins> { stdenv, lib, fetchurl, callPackage, substituteAll, python3, pkgconfig, writeText </ins> , xorg, gtk3, glib, pango, cairo, gdk-pixbuf, atk , wrapGAppsHook, xorgserver, getopt, xauth, utillinux, which , ffmpeg_4, x264, libvpx, libwebp, x265

Discussion:
Describe the bug Attempting to start xpra fails with the following X server log: To Reproduce Steps to reproduce the behavior: run start :200
Change:
google-chrome = callPackage ../applications/networking/browsers/google-chrome { }; <del> google-chrome-beta = google-chrome.override { chromium = chromiumBeta; channel = "beta"; }; google-chrome-dev = google-chrome.override { chromium = chromiumDev; channel = "dev"; }; </del> go-graft = callPackage ../applications/networking/go-graft { }; gostatic = callPackage ../applications/misc/gostatic { };

Discussion:
Package name: google-chrome Latest released version: 116.0.5845.187 Current version on the unstable channel: 116.0.5845.179 Current version on the stable/release channel: 116.0.5845.179 Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Please note a new version of Chrome is now available to address an exploited-in-the-wild zero-day vulnerability in the WebP image parsing code in the Chrome browser. This vulnerability could allow arbitrary code execution when a specially crafted image is viewed. Please update as soon as possible. For more information on the vulnerability, tracked as CVE-2023-4863, refer to this disclosure from Google: Note for maintainers: Please tag this issue in your PR.
I'm seeing on both 23.05 and unstable. Per chromium/google-chrome was one of the first things that was patched.
Those versions are released on both channels but on stable updates for google-chrome-dev and google-chrome-beta are missing
Change:
python3.pkgs.buildPythonApplication rec { pname = "gajim"; <del> version = "1.3.2"; </del> <ins> version = "1.3.3"; </ins> src = fetchurl { url = "https://gajim.org/downloads/${lib.versions.majorMinor version}/gajim-${version}.tar.gz"; <del> sha256 = "1vjzv8zg9s393xw81klcgbkn4h6j2blzla9iil5kqfrw7wmldskh"; </del> <ins> sha256 = "1337qkpcv7j0fgws9scnk82mn2l7s17060vmrbh3ihinmxmbxg6x"; </ins> }; buildInputs = [

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: gajim <!-- 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: 1.3.2 desired version: 1.3.3 <!-- 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:
inherit (old) version src; sourceRoot = "${old.src.name}/spectre_oxi"; <del> cargoHash = "sha256-ZBlxJjkHb2buvXK6VGP6FMnSFk8RUX7IgHjNofnGDAs="; </del> <ins> cargoHash = "sha256-SqbU9YwZ5pvdFUr7XBAkkfoqiLHI0JwJRwH7Wj1JDNg="; </ins> preCheck = '' mkdir tests/tmp/

Discussion:
Steps to reproduce the behavior: 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]: