jiebi/CodeConvo huggingface dataset:
Change:
<del> { lib, stdenv </del> <ins> { lib , stdenv </ins> , fetchurl , substituteAll , cmake

Discussion:
Steps to reproduce the behavior: Stumbled upon this when upgrading my NixOS flake from to No maintainers so I'll just ping the last person to touch this <!-- 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]:
It broke in this PR merge Okay, the problem's with libxml2, which changed its interface a bit
Okay, I managed to fix the build, will open a PR shortly.
Thank you for writing the fix and creating the PR. Is something holding up the pull request? It's been open for over a week now.
I guess noone really reviewed the PR. I can maybe ask for a review.
I tried building mysql-workbench again today but it is still failing. Is it building properly for you? Or is it something on my end? output of
the pr that fixed this hasn't hit nixos-unstable yet, wait until it does. You can check here
Change:
''} echo '1 + 1' | $out/bin/node -i <del> ${lib.optionalString (javaVersion == "11") '' </del> <ins> ${lib.optionalString (javaVersion == "11" && stdenv.isLinux) '' # Doesn't work on MacOS, we have this error: "Launching JShell execution engine threw: Operation not permitted (Bind failed)" </ins> echo '1 + 1' | $out/bin/jshell ''}'';

Discussion:
Describe the bug When running I get the following error message: Looking at the executable the first line is: In fish does not return the name of the current executed file. It appear to work when running this using . Also as comparison look at the file generated via package manager: To Reproduce Steps to reproduce the behavior: Expected behavior should start the server Additional context So with . Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(yogsototh): nixpkgs: Maintainer information:
Hey this version is pretty outdated, could you try latest which is using graalvm binary?
Also the brew forumla you saw is outdated as well, the updated is
You are probably using the stable channel 20.09 channel, that should explain why you're still using the with JVM instead of GraalVM compiled binary. Switch to the unstable channel instead. I am not sure if it will work though since this package was never tested with macOS (and the fact that this package is broken in Hydra: ).
I just tested with latest master commit And if failed to build: I think the main bug is probably fixed. This is just another one :). This is late for me. I'll probably give it a look another day. Thanks for checking!
I think all GraalVM's packages build with Clojure are broken in macOS simply by the lack of people that has macOS systems to test/fix them. If you can fix this, a PR would be welcome :slightlysmilingface: .
Agreed If you have mac, using the homebrew official clojure-lsp formula should work as well: https://clojure-
Change:
libre-franklin = callPackage ../data/fonts/libre-franklin { }; <del> lmmath = callPackage ../data/fonts/lmodern/lmmath.nix {}; </del> <ins> lmmath = callPackage ../data/fonts/lmmath {}; </ins> lmodern = callPackage ../data/fonts/lmodern { };

Discussion:
A grep of : The latest version is 1.959 per I'd say that the texlive and fonts/lm-math versions can stay as they have different paths ( vs ), although ideally just the texlive version would stay, but the others are not helping anything at all.
cc for comments
– has meta, unpacks only the needed files – resides in the same directory with , tries to provide texmf So, perhaps, we should keep the implementation of under the name and make an alias. The satysfi needs to be fixed to use existing packages (also implements a duplicate of ).
Well, for texmf one would presumably use the TexLive package, as it has separated and outputs unlike the other packages. And it auto-updates along with the rest of TexLive. The only issue with using it as the sole package is that it's not a multiple output derivation so using it in the fonts list looks like rather than just . It shouldn't be that hard to set up TexLive to have attributes usable directly, by setting and so forth. Nix doesn't support multiple outputs for fixed-output derivations, so it'd be a bit of a hack.
The "packages" in are set up to be used with . They were not intended to be used in any other way.
Change:
, texinfo , ncurses , pcre <ins> , pkg-config </ins> , buildPackages }: let

Discussion:
Steps to reproduce the behavior: nixpkgs/#pkgsCross.armv7l-hf- () Not sure what's going on here, looking at zsh looks like it should build for ARM without any special handling. <!-- 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.
Most likely something related to glibc, since building with musl (at least through pkgsStatic) works. Also since it can't find any of these during configure:

This is from nixos-unstable current. For some reason, I get build failures with ZSH. This is with a nixpkgs (system=x86_64-linux) and nixpkgs.crossSystem set to . This seems to be the same failure (I checked, its the same derivation): Steps to reproduce the behavior: ... ... ... 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.
couldn't fix it. I'll leave this assigned to myself so i remember to take a another shot at it in ~6 months
Fixed by
Change:
# Idris wrapper with specified compiler and library paths, used to build packages <del> idris = (pkgs.callPackage ./idris-wrapper.nix {}) idris-no-deps { path = [ pkgs.gcc ]; lib = [pkgs.gmp]; }; </del> <ins> idris = pkgs.callPackage ./idris-wrapper.nix { inherit idris-no-deps; }; </ins> # Utilities for building packages

Discussion:
Idris requires a C compiler to function. To find a C compiler, it first checks IDRISCC, as implemented here: and then searches PATH. The current wrapper for the "idris" compiler binary appends /nix/store/...-gcc-wrapper/bin to the PATH. This unfortunately makes idris quite fragile: When my PATH has some bad program named "cc" on it, such as some ancient compiler that I've installed for whatever reason, idris will break. It's also a fairly unnecessary impurity. We should set IDRISCC in the wrapper instead, when it is not already set. This allows the user to still override the C compiler that is used if they want to, while significantly lowering the chance that things will be unexpectedly broken.
Change:
, python37Packages , stdenv , systemd <ins> , xdg-utils </ins> , zlib }: with lib;

Discussion:
Describe the bug Signing using external provider is not able to open browser for SAML authentication. To Reproduce Steps to reproduce the behavior: ./result/bin/appgate configured provider click on "sign in with provider" the error Expected behavior Browser opens to sign in. Screenshots  Additional context The strace output snippet: Notify maintainers Metadata Please run and paste the result. Maintainer information:
Change:
(mkJetBrainsProduct { inherit pname version src wmClass jdk; product = "Rider"; <ins> # icu is required by Rider.Backend extraLdPath = [ icu ]; </ins> meta = with lib; { homepage = "https://www.jetbrains.com/rider/"; inherit description license platforms;

Discussion:
For the last few weeks, Rider hasn't started. I get an dialog with the following text: In the console, there is a link to recovering from IDE errors. I've followed those including blowing away my config, log, and cache directories (which lets me go through the initial setup but still fails). Rider and build system. the CLI, navigate to a C# project and enter It starts up after a while and it is usable. I pasted above the text of the only dialog box. Looking through the error log, I saw this entry: This file exists but running on it show this: The problem seems to be the missing . Rider doesn't appear to have maintainers, but is on a number of packages in that file.
Will be resolved by
Change:
-    'libharfbuzz-0.dll') -fontconfig = _dlopen( -    ffi, 'fontconfig-1', 'fontconfig', 'libfontconfig', 'libfontconfig.so.1', <del> -    'libfontconfig-1.dylib', 'libfontconfig-1.dll') </del> <ins> -    'libfontconfig.1.dylib', 'libfontconfig-1.dll') </ins> -pangoft2 = _dlopen( -    ffi, 'pangoft2-1.0-0', 'pangoft2-1.0', 'libpangoft2-1.0-0', -    'libpangoft2-1.0.so.0', 'libpangoft2-1.0.dylib', 'libpangoft2-1.0-0.dll')

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:
https://github.com/asheq/close-buffers.vim/,HEAD, https://github.com/Civitasv/cmake-tools.nvim/,, https://github.com/winston0410/cmd-parser.nvim/,, <del> <<<<<<< HEAD </del> https://github.com/tzachar/cmp-ai/,HEAD, https://codeberg.org/FelipeLema/cmp-async-path/,, <del> ======= >>>>>>> 8c49439301ad (vimPlugins.nvim-genghis: init at 2024-05-21) </del> https://github.com/crispgm/cmp-beancount/,HEAD, https://github.com/hrsh7th/cmp-buffer/,, https://github.com/hrsh7th/cmp-calc/,,

Discussion:
An uncaught exception is raised when running the vimPluginUpdater script Steps to reproduce the behavior: the vim plugin update script with The script should not raise an exception Eception: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This is because the file has been corrupted by . I’ll send a PR to fix this in a bit.
Change:
let is_extension = gawkextlib != null; in stdenv.mkDerivation rec { pname = "gawkextlib-${name}"; <del> version = "unstable-2019-11-21"; </del> <ins> version = "unstable-2022-10-20"; </ins> src = fetchgit { url = "git://git.code.sf.net/p/gawkextlib/code"; <del> rev = "f70f10da2804e4fd0a0bac57736e9c1cf21e345d"; sha256 = "0r8fz89n3l4dfszs1980yqj0ah95430lj0y1lb7blfkwxa6c2xik"; </del> <ins> rev = "f6c75b4ac1e0cd8d70c2f6c7a8d58b4d94cfde97"; sha256 = "sha256-0p3CrQ3TBl7UcveZytK/9rkAzn69RRM2GwY2eCeqlkg="; </ins> }; postPatch = ''

Discussion:
Steps to reproduce the behavior: -build '<nixpkgs' -A gawk-with-extensions Still fails when I used My current workaround is removing haru from gawkextlib with:
Related: and not yet updated in gawkextlib:
Change:
{ <del> "version": "1.10.4", "desktopSrcHash": "cuMo0wRMC6+un3BQK0+Ecnjvs6HugNk71yElNJarlyc=", "desktopYarnHash": "0llnqwgiqggfcgjyaar2h2r1pyw8m14icfb1pcdphqxrah9gpsar", "webHash": "0vf8npddbx4dmq9c1ghak97jn28b18ssblbrq5smdhlzsnxlpm3l" </del> <ins> "version": "1.10.6", "desktopSrcHash": "TJGYavawLDLbP9Sg7HxIcOkr7hcTfAwk4fyOOEv4KhI=", "desktopYarnHash": "038rqg26dn8chzscck5mlhnw2viy6gr8pjb7zrcmi7ipx9h038a0", "webHash": "1wax4h5gfcq4giyq1igsix748cngky487kwvf69zb1gz95hjds9r" </ins> }

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: element-web <!-- 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: 1.10.4 desired version: 1.10.6 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Myself i am waiting for an , ... please keep an eye on the release.
Change:
dataDir = mkOption { type = types.str; <del> default = defaultDataDir; </del> <ins> default = if versionAtLeast config.system.stateVersion "17.09" then "/var/lib/ipfs" else "/var/lib/ipfs/.ipfs"; </ins> description = "The data dir for IPFS"; };

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:
patchShebangs meson-postinstall.py ''; <ins> dontWrapGApps = true; preFixup = '' makeWrapperArgs+=("''${gappsWrapperArgs[@]}") ''; postFixup = '' wrapPythonProgramsIn "$out/libexec" "$out $pythonPath" ''; </ins> passthru = { updateScript = gnome.updateScript { packageName = pname;

Discussion:
When the option is toggled, Tweaks log the following error on startup: GNOME Tweaks General tab, toggle Suspend when lid is closed It should prevent laptop suspension. The binary needs a python wrapper. Additionally, the setting creates which contains a store path, which might break on garbage collection. cc
For me the error is because I have a file which causes the module to exist but not have anything in it. Doesn't it have one? My take was that needs a dependency on the python package.
Even if you have python modules linked to your system profile, Python still should not pick them up. Unless something is contaminating the environment variable. By default, only executables in package’s directory are wrapped:
Oh yeah, I forgot. It's me. I'm the one contaminating the . I did it on purpose a while ago and it didn't occur to me that that's why my exception was different than yours, or I wouldn't have left my previous comment in the first place. Oh, I see. Thanks.
Please test
in the built package this is in
I opened for this:
Change:
, libopenmpt , libopus , libplacebo <ins> , libplacebo_5 </ins> , libpulseaudio , libraw1394 , librsvg

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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.
Done here:
Change:
<ins> diff --git a/ci/build/build-vscode.sh b/ci/build/build-vscode.sh index a72549fb..3aed1ad5 100755 --- a/ci/build/build-vscode.sh +++ b/ci/build/build-vscode.sh @@ -58,7 +58,6 @@ main() { # telemetry available; telemetry can still be disabled by flag or setting). # This needs to be done before building as Code will read this file and embed # it into the client-side code. -  git checkout product.json             # Reset in case the script exited early. cp product.json product.original.json # Since jq has no inline edit. jq --slurp '.[0] * .[1]' product.original.json <( cat << EOF @@ -105,7 +104,6 @@ EOF # Reset so if you develop after building you will not be stuck with the wrong # commit (the dev client will use `oss-dev` but the dev server will still use # product.json which will have `stable-$commit`). -  git checkout product.json popd </ins>

Discussion:
Currently, code-server (and openvscode-server) depends on 16 in nixpkgs, for the upcoming release of NixOS 23.11, this dependency must be dropped, and all upgrades must be performed to 18. From what I see on — 18 is supported as an engine. Otherwise, those programs are to be dropped. Please pick up the pieces cc
Drop will be performed in
Change:
<del> { lib, stdenv, rustPlatform, fetchFromGitHub, fetchzip, androidenv, makeWrapper }: </del> <ins> { lib , stdenv , rustPlatform , fetchFromGitHub , fetchpatch , fetchzip , androidenv , makeWrapper }: </ins> let version = "2.5"; apk = stdenv.mkDerivation {

Discussion:
see this issue Steps to reproduce the behavior: gnirehtet from 22.11 or unstable (22.05 still has a working version) a smartphone and enable adb it should suffice to build gnirehtet with rust 1.63 or older to fix the issue
Change:
, stdenv , callPackage , fetchFromGitHub <ins> , fetchpatch </ins> , makeWrapper , nixosTests , python3Packages

Discussion:
Mealie was updated from 1.7.0 to 1.9.0, and it's now failing to launch, even though I'm using the exact same configuration. It actually seems that just enabling Mealie, with no configuration isn't working. What's weird is that the error is referring to , which is a sops-nix directory. I even rebooted, but it's still getting that particular error Use the following configuration: Mealie successfully starts. Here's my original Nix configuration: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Tested on VM, works fine with the base configuration. The problem comes from the part of your configuration, it seams that you need the setup the user to get access to the directory. I'm not familiar with , is there a group you could add the user to so that it can access the directory ?
You can allow a specific user/group access to the decrypted sops secret file using the options. See this example in my config:
It still doesn't work after doing that. I wonder if it's some state getting left over that screws something up, because it's weird it would still not work after removing everything but . I deleted though, and it's still happening, and it also still works if I role back to 1.7.0. Although, I am using PostgreSQL so maybe it's something in there? Note that it's happening in . Here's my updated Nix file:
The issue seems to have something to do with this mealie commit: Mealie 1.9.0 works when the commit is reverted:
Somebody opened a PR to get this fixed upstream:
I've also opened , which prevents mealie from exploding when it encounters a secrets directory that it doesn't have permission to read. I've verified that it fixes this issue in my own NixOS deployment.
has been merged and should be out in the next release. In the meantime, we can pull in to the currently available v1.11.0 to fix the bug. I'll create a PR for this.
I'm still experiencing this issue when Mealie first starts after boot, but it goes away after restarting the service.

I'm guessing it's because sops-nix hasn't setup the directory yet? Should I open a new issue?
That warning message seems to be intentional. The patch always prints a warning before the directory is ignored.
Change:
pushd ${cargoRoot} export HOME=$(mktemp -d) <del> export -f cargoCheckHook runHook _eval _callImplicitHook </del> <ins> export -f cargoCheckHook runHook _eval _callImplicitHook _logHook </ins> export cargoCheckType=release dbus-run-session  --config-file=${dbus}/share/dbus-1/session.conf 

Discussion:
Steps to reproduce the behavior: bitwarden-desktop-2024-6.4 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]:
yep, same error on my machine, as well as in I guess should be exported:
I tried this, but failed with a different error
Are you sure you are trying to build it with the latest nixpkgs? I managed to build & run bitwarden 2024.6.4 log hooks stuff appeared recently , function
Ah yes, sorry, I forgot to pull latest nixpkgs, now it works. Happy to throw together a quick PR. Do you know why this works? I'm guessing it's got something to do with the checkPhase invoking and passing into another bash invocation (and cargoCheckHook depends on logHook). I got curious, and there aren't any other packages that export logHook like this:
Change:
godot = callPackage ../development/tools/godot {}; <ins> godot-export-templates = callPackage ../development/tools/godot/export-templates.nix { }; </ins> godot-headless = callPackage ../development/tools/godot/headless.nix { }; godot-server = callPackage ../development/tools/godot/server.nix { };

Discussion:
Project description made with godot engine it does not run with steam-run (), so a proper package would be great Metadata homepage URL: source URL: license: Blue Oak Model License platforms: linux, darwin, windows
Change:
stdenv.mkDerivation rec { name = "opensaml-cpp-${version}"; <del> version = "2.6.0"; </del> <ins> version = "2.6.1"; </ins> src = fetchgit { url = "https://git.shibboleth.net/git/cpp-opensaml.git"; <del> rev = "61193de29e4c9f1ccff7ed7e1f42c2748c62be77"; sha256 = "1jlxa1f2qn0kd15fzjqp80apxn42v47wg3mx1vk424m31rhi00xr"; </del> <ins> rev = version; sha256 = "0wjb6jyvh4hwpy1pvhh63i821746nqijysrd4vasbirkf4h6z7nx"; </ins> }; buildInputs = [ boost openssl log4shib xercesc xml-security-c xml-tooling-c zlib ];

Discussion:
There are at least two open security issues (CVE-2017-,CVE-2017-) which affect shibboleth-se and opensaml. The details can be obtained from the upstream annoucement: There are new releases & patches available that fix those open issues. Either updating or marking those packages as broken/insecure seems sensible to me. CC current maintainers:
Sorry for the late response. Thanks for bringing this to my attention. I will fix the packages in the next few days. I actually think the bigger issue is this one, which affects the xml parser: So xml-tooling-c also needs to be fixed, and should be marked broken if not fixed.
Change:
postInstall = '' mkdir -p $out/bin <del> # Copy the extracted assets, required to be in the same directory as the executable ${lib.optionalString oot.enable "cp ../OTRExporter/oot.otr $out/lib"} ${lib.optionalString ootMq.enable "cp ../OTRExporter/oot-mq.otr $out/lib"} </del> ln -s $out/lib/soh.elf $out/bin/soh <ins> install -Dm644 ../soh/macosx/sohIcon.png $out/share/pixmaps/soh.png ''; fixupPhase = '' wrapProgram $out/lib/soh.elf --prefix PATH ":" ${lib.makeBinPath [ gnome.zenity ]} </ins> ''; desktopItems = [

Discussion:
Package name: shipwright Latest released version: 8.0.4 <!-- Search your package here: --- Current version on the unstable channel: 7.1.1 Current version on the stable/release channel: 7.0.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 I tried updating myself and found 8.0.4 fails building with error I bisected to upstream commit and the file but I'm not sure how to resolve right now. <!-- 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]: