jiebi/CodeConvo huggingface dataset:
Change:
]; in stdenv.mkDerivation ({ <del> inherit dontUnpack LC_ALL jar; </del> <ins> inherit dontUnpack jar; </ins> nativeBuildInputs = (args.nativeBuildInputs or [ ]) ++ [ graalvmDrv glibcLocales ];

Discussion:
After babashka can't display Unicode characters I have a babashka script that outputs the following JSON: The text is a Nerd Font Symbol code point. After the output is: Steps to reproduce the behavior: This has been fixed in the past by I did not test other packages that could be affected by the PR.
Pretty sure this is related to this bug in GraalVM upstream: I am curious if this is affecting projects using GraalVM 21.0.0 vanilla or if not, how is it working and why it is broken in .
It does seem that even setting up inside the C compiler environment is not sufficient to make it work. CC to see if they have more context on what the possibly issue is.
I also hit this today. I tested the same version(v1.3.186) from upstream binary release, which does not have this issue. Shall we always sync the same version of graavm as upstream build ci?
I don't think this is the issue and even if it was, it is not like babashka is the only GraalVM package we have.
I know that folks can't reproduce this issue with upstream, but I also can't reproduce it with GraalVM using Java, e.g.: A patch if anyone wants to test to be applied to : So, can anyone reproduce this issue with GraalVM Native Image itself? If not, the only thing I can think is that the issue here is the GCC (i.e.: non-static) version (upstream compiles with by default). Or something else.
So I got this warning: But this was after already started to build, so I assume this is the same issue as and need to be fixed upstream.
To explain in more details why I think this is an upstream issue: I don't get the same in the initial part of the build, only when the build starts that I get this warning. So what I assume is doing: Running the CC (C Compiler) inside a shell with clean environment We see the , because this shell couldn't set the proper locale thanks to missing environment variables (e.g.: ) Since this shell environment has no environment variables (at least, not the environment variables that we need), this ends up breaking macOS compilation and locale (Unicode) support in Linux Not sure why it works in GraalVM itself though yet. This is all really strange.

While I'm not familiar with graalvm, I do find a hack for this issue, maybe can weigh in to test whether this hack is valid: Some inspiration from a random reddit post and those issues: And I do find it's using , so I thought if I those two into build args, maybe it'd work. And indeed it seems to work.. After I built bb with above args,
BTW, I cannot reproduce with GraalVM Native Image on helloworld java as well. Helloworld produced by GraalVM Native Image has correct unicode output.
Thanks for investigating this issue. Opened so we can have this fixed.
Change:
''; postInstall = '' <del> install -Dm555 target/release/bundle/deb/surrealist_${finalAttrs.version}_*/data/usr/bin/surrealist -t $out/bin cp -r target/release/bundle/deb/surrealist_${finalAttrs.version}_*/data/usr/share $out </del> <ins> install -Dm555 target/release/bundle/deb/Surrealist_${finalAttrs.version}_*/data/usr/bin/surrealist -t $out/bin cp -r target/release/bundle/deb/Surrealist_${finalAttrs.version}_*/data/usr/share $out </ins> ''; postFixup = '' <del> wrapProgram "$out/bin/surrealist" --set WEBKIT_DISABLE_COMPOSITING_MODE 1 </del> <ins> wrapProgram "$out/bin/surrealist"  --set GIO_EXTRA_MODULES ${glib-networking}/lib/gio/modules  --set WEBKIT_DISABLE_COMPOSITING_MODE 1 </ins> ''; meta = with lib; {

Discussion:
Steps to reproduce the behavior: Attempt to build surrealist version 2.0.6 on NixOS 24.11. The build fails during the build phase. I reported a similar issue here: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
another failure
Change:
in (concatStringsSep "n" (flatten [ <ins> "runHook preInstall" </ins> (optionalString (withScripting) "buildPythonPath "${base} $pythonPath" n") # wrap each of the directly usable tools

Discussion:
Describe the bug is missing a menu entry to launch the application. To Reproduce Steps to reproduce the behavior: Expected behavior There should be a menu entry to launch the application. 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
see (probably shouldn't have been closed)
Change:
<del> { lib, stdenv, fetchFromGitHub, makeDesktopItem, makeWrapper, ant, jdk, jre, gtk2, glib, xorg, Cocoa }: </del> <ins> { lib, stdenv, fetchFromGitHub, makeDesktopItem, makeWrapper, wrapGAppsHook, ant, jdk, jre, gtk2, glib, xorg, Cocoa }: </ins> let _version = "2.10.2";

Discussion:
When a user starts and opens a file dialog the application crashes with (Jameica 2.10.2:): GLib-GIO-ERROR **: 22:23:21.974: No GSettings schemas are installed on the system Steps to reproduce the behavior: jameica a "workspace" -manage backups -restore different backup Opens a gtk file dialog jameica crashes on every file dialog for me. the backup path is just the easiest accessible and something a user may come along quickly. i was already playing around a bit with the wrapGAppsHook, but i just dont get it running atm. so maybe someone else want to take a look on that. i am running a kde session on wayland, but i doubt that it make any difference on gnome or other DE. <!-- 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.
created a pr for it. my first tries in adding wrapGappsHook did fail as i did not get, that the order for nativeBuildinputs do matter.
Change:
fetchSubmodules = true; }; <ins> patches = [ # Lets obs-browser build against CEF 90.1.0+ ./Enable-file-access-and-universal-access-for-file-URL.patch # Lets obs-browser build against CEF 91.1.0+ ./Change-product_version-to-user_agent_product.patch ]; </ins> nativeBuildInputs = [ addOpenGLRunpath cmake pkg-config ]; buildInputs = [

Discussion:
(Upstream bug, autoclosed due to NixOS not being supported: ) I get the following segv on start: This behavior was not present pre-v27.
Not sure what the issue is but removing a scene that had a browser embed in it stopped the crash. (I tried it because libcef is chrome).
Okay, I can confirm that adding a Browser scene (then quitting OBS, then opening it again) will cause a segfault. Actually adding the scene does not cause any problems, although I was unable to get it to render anything.
This is probably due to our CEF version being out of date. Currently building with a newer copy…
It was indeed our CEF version being out of date. It's practically ancient, from 2019-07-27. Building against latest gives me an OBS that doesn't crash on startup & shows stuff in the Browser source. See for the fix.
Change:
, glib , fuse , installShellFiles <ins> , wrapGAppsHook </ins> }: let pname = "onedriver";

Discussion:
After installing onedriver, the program crashes when trying to add a new account. Steps to reproduce the behavior: onedriver onedriver-launcher adding a new account It should open the new account window. If applicable, add screenshots to help explain your problem. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<del> { gtk3 , gdk-pixbuf , librsvg , webp-pixbuf-loader , gobject-introspection , glib-networking , glib , shared-mime-info , gsettings-desktop-schemas , wrapGAppsHook3 , gtk-layer-shell , gnome , libxkbcommon , openssl , pkg-config , hicolor-icon-theme , rustPlatform , lib , fetchFromGitHub </del> <ins> { gtk3, gdk-pixbuf, librsvg, webp-pixbuf-loader, gobject-introspection, glib-networking, glib, shared-mime-info, gsettings-desktop-schemas, wrapGAppsHook3, gtk-layer-shell, gnome, libxkbcommon, openssl, pkg-config, hicolor-icon-theme, rustPlatform, lib, fetchFromGitHub, luajit, luajitPackages, libpulseaudio, features ? [ ], </ins> }: <ins> let hasFeature = f: features == [ ] || builtins.elem f features; in </ins> rustPlatform.buildRustPackage rec { pname = "ironbar"; <del> version = "0.14.1"; </del> <ins> version = "0.15.0"; </ins> src = fetchFromGitHub { owner = "JakeStanger"; repo = "ironbar"; rev = "v${version}"; <del> hash = "sha256-y4w4i/IVe1+wjB2tsCPQH6c7XTl93u45Q0pXFi3TY1E="; </del> <ins> hash = "sha256-SowZ3qo06x32+A02Wmq4N/rU/yxyKqkn407qHzJLU0M="; </ins> }; <del> cargoHash = "sha256-h5yNJM+NvX/Hi86iSegHWevPcPZeDmJ4y/qNr3G20Qg="; </del> <ins> cargoHash = "sha256-DaF669mOnICTnUzH4mc640xIecin/UEZSk7PWDjQbr0="; </ins> <del> buildInputs = [ gtk3 gdk-pixbuf glib gtk-layer-shell glib-networking shared-mime-info gnome.adwaita-icon-theme hicolor-icon-theme gsettings-desktop-schemas libxkbcommon openssl ]; </del> <ins> buildInputs = [ gtk3 gdk-pixbuf glib gtk-layer-shell glib-networking shared-mime-info gnome.adwaita-icon-theme hicolor-icon-theme gsettings-desktop-schemas libxkbcommon ] ++ lib.optionals (hasFeature "http") [ openssl ] ++ lib.optionals (hasFeature "volume") [ libpulseaudio ] ++ lib.optionals (hasFeature "cairo") [ luajit ]; </ins> nativeBuildInputs = [ pkg-config wrapGAppsHook3 gobject-introspection ]; <ins> propagatedBuildInputs = [ gtk3 ]; </ins> <del> propagatedBuildInputs = [ gtk3 ]; </del> <ins> runtimeDeps = [ luajitPackages.lgi ]; </ins> <del> preFixup = '' gappsWrapperArgs+=( </del> <ins> buildNoDefaultFeatures = features != [ ]; buildFeatures = features; gappsWrapperArgs = '' </ins> # Thumbnailers --prefix XDG_DATA_DIRS : "${gdk-pixbuf}/share" --prefix XDG_DATA_DIRS : "${librsvg}/share"

Discussion:
Package name: Ironbar Latest released version: 0.15.0Current version on the unstable channel: 0.14.1 Current version on the stable/release channel: 0.13.0 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
} // a // { <del> name = "gimp-plugin-${a.name}"; </del> <ins> name = "gimp-plugin-${a.name or "${a.pname}-${a.version}"}"; </ins> buildInputs = [ gimp gimp.gtk glib ] ++ (a.buildInputs or []); nativeBuildInputs = [ pkgconfig intltool ] ++ (a.nativeBuildInputs or []); }

Discussion:
Installing the gimpPlugins.resynthesizer2 package does not result in a working plugin; the python scripts are installed, but not the two native executables it depends on (called "resynthesizer" and "resynthesizer" Try to install the package "gimpPlugins.resynthesizer2". Expected result: There should be a few new menu options in the Gimp, amongst them "Filter -Enhance -Heal Selection..." Actual result: No new menu options; python scripts cannot find the executables. Possible solution: I made it work by creating a derivation that adds a the following postInstall: postInstall = "installPlugins src/resynthesizer/resynthesizer src/resynthesizer-gui/resynthesizergui"; system: host os: multi-user?: sandbox: version: channels(cable): nixpkgs:
You need to make the plugins available to GIMP, not install it locally. The following should work:
Just tried it (on a nix shell) - but same result; the resulting installation of gimp-with-plugins links to a resynthesizer2 package that lacks the native executables, only has the python scripts (which don't work without the executables)
Hmm, there was an issue with , saves us.
Change:
# See: https://github.com/NixOS/nixpkgs/issues/213408 pkgs.substitute { src = "${systemd}/example/sysctl.d/50-coredump.conf"; <del> replacements = [ </del> <ins> substitutions = [ </ins> "--replace" "${systemd}" "${pkgs.symlinkJoin { name = "systemd"; paths = [ systemd ]; }}"

Discussion:
Using with , currently does not allow me to replace a string that contains spaces. Steps to reproduce the behavior: the code below: It gives the following error: I tried quoting it, escaping the spaces... but none of them seemed to work. The I did succeeds. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. I posted this in the NixOS matrix room a while ago (but I forgot to submit an issue): !$ People showed me some bash magic I couldn't understand, I think they might be helpful and worth checking out. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (git blame) cc (people in the original conversation) Please run and paste the result. (I'm sorry if I described anything incorrectly, I'm a not a native English speaker and I am still trying to improve my language skills) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Should be fixed with , please give it a try :)
Wonderful! It worked for me
Change:
<ins> { lib , buildGoModule , fetchFromGitHub , makeWrapper , installShellFiles , docker , distrobox }: buildGoModule rec { pname = "apx"; version = "1.4.2"; src = fetchFromGitHub { owner = "Vanilla-OS"; repo = pname; rev = version; sha256 = "sha256-BswX4Jo/RReM/tXo29V9rIvKjN8ylECPe0oo0FCQcGY="; }; vendorSha256 = null; ldflags = [ "-s" "-w" ]; nativeBuildInputs = [ makeWrapper installShellFiles ]; postInstall = '' mkdir -p $out/etc/apx cat > "$out/etc/apx/config.json" <<EOF { "containername": "apx_managed", "image": "docker.io/library/ubuntu", "pkgmanager": "apt", "distroboxpath": "${distrobox}/bin/distrobox" } EOF wrapProgram $out/bin/apx --prefix PATH : ${lib.makeBinPath [ docker distrobox ]} installManPage man/apx.1 man/es/apx.1 ''; meta = with lib; { description = "The Vanilla OS package manager"; homepage = "https://github.com/Vanilla-OS/apx"; license = licenses.gpl3; maintainers = with maintainers; [ dit7ya ]; }; } </ins>

Discussion:
Project description apx is the Vanilla OS package manager. It’s meant to be simple to use, but also powerful with support to installing packages from multiple sources without altering the root filesystem. Metadata homepage URL: source URL: license: gpl3 platforms: linux
Thank you!
Change:
, jackaudioSupport ? false, libjack2 , cudaSupport ? config.cudaSupport or false, cudatoolkit , colladaSupport ? true, opencollada <del> , enableNumpy ? false, makeWrapper </del> <ins> , makeWrapper </ins> , pugixml, SDL, Cocoa, CoreGraphics, ForceFeedback, OpenAL, OpenGL }:

Discussion:
Describe the bug blender 2.82 built with enableNumpy set to true builds and installs without errors, but at run-time it fails to find numpy. There may be other issues with other libraries not being found as I'm having trouble activating a number of plugins and I don't think all use numpy, though at the moment I can only say for certainty numpy doesn't work. To Reproduce Steps to reproduce the behavior: blender with blender and go to the Scripting tab. in the console. The following comes up: This worked with 2.81. Expected behavior numpy should be imported with no errors. Metadata Result of : Maintainer information:
Change:
version = ext.version; <ins> relativeLocation = ext.vscodeExtUniqueId; </ins> location = { "$mid" = 1; fsPath = ext.outPath + "/share/vscode/extensions/${ext.vscodeExtUniqueId}";

Discussion:
In VSCode (and Codium), the extension is unable to load icons, and uses generic rectangles instead. Opening VSCode/Codium with shows: Steps to reproduce the behavior: . can see that what are supposed to be GitLens icons are rectangles instead. GitLens should load the icons correctly. EDIT: Instead of rectangles, the icons are invisible now. ! ! Bug also happens with the extension fetched from (both from vscode-marketplace and open-vsx). The bug doesn't reproduce with . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
VScode only allows files to be loaded from certain root folders (). On NixOS, the extensionsDir is in the Nix store with links to the different extensions (also in the Nix store). This issue is that the extensions tries to load the file from the extension's folder directly () and not from the extensions folder (something like ). If the path of the font is , it should work ( must be in the authorised folders whereas isn't).
Facing this until today. Anyone has workaround for this issue?
pinging as maintainer
thanks for the research! Do you think this is something we can substitute in our packaging? Or does it require an upstream fix?
I researched into this as well. I am not really sure how came to his conclusion, that the problem stems from vscode/vscodium not having permissions to load icons from specific places, if I understood him correctly. Neither do I know how we could test this hypothesis. EDIT: I was stupid. It's because of the error What I noticed, however, is that the extension has the same problem: Furthermore, if I go into my folder and issues the command , I get the following output: Not sure about the spring-boot-dashboard extension, but it seems like extensions which define this attribute in their cannot load their icons.
Change:
<del> { stdenv, lib, fetchurl, autoPatchelfHook }: stdenv.mkDerivation rec { pname = "deepspeech"; version = "0.9.3"; src = fetchurl { url = "https://github.com/mozilla/DeepSpeech/releases/download/v${version}/native_client.amd64.cpu.linux.tar.xz"; sha256 = "1qy2gspprcxi76jk06ljp028xl0wkk1m3mqaxyf5qbhhfbvvpfap"; }; setSourceRoot = "sourceRoot=`pwd`"; nativeBuildInputs = [ autoPatchelfHook ]; buildInputs = [ stdenv.cc.cc.lib ]; installPhase = '' install -D deepspeech $out/bin/deepspeech install -D deepspeech.h $out/include/deepspeech.h install -D libdeepspeech.so $out/lib/libdeepspeech.so ''; meta = with lib; { homepage = https://github.com/mozilla/DeepSpeech; description = "Open source embedded (offline, on-device) speech-to-text engine, which can run in real time on broad range of devices"; license = licenses.mpl20; platforms = [ "x86_64-linux" ]; maintainers = with maintainers; [ rvolosatovs ]; }; } </del>

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: tts <!-- 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: 0.0.9 desired version: 0.0.11 maintainers: mozilla fired the team and they founded a new company to continue their work new releases can be found here
We are aware of the forks, we'll probably get to it before the branch-off. STT (DeepSpeech) was recently packaged, but does not build from source, so my interest in that package is limited.
Same also not a STT user.
can you update deepspeech to the new repo, call it stt and deprecate deepspeech? how to deprecate a package is documented here: please add a review. when anything is unclear, i would like to improve it
How about we call it instead?
i don't think that is very helpful for the end-user. the package name should match the upstream project name
do you want to update tts again?
Hello, just wanted to say that there has been a new release , in case someone wants to give it a shot.
Change:
upgrade_all= repair= profile=/nix/var/nix/profiles/system <del> buildHost= </del> <ins> buildHost=localhost </ins> targetHost= maybeSudo=()

Discussion:
Even if the target host gets the toplevel closure, later steps in the nixos-rebuild will always the build closure over to the targetHost (which can thousands of packages larger) and is potentially unnecessary. PR which introduced of the .drv: Additional Context: For our scenario, we would to the machine, as the machines are usually underpowered compared our dev boxes, and our dev boxes would likely have the configurations in the store as we were iterating on the configurations. Thus it was odd that we copied the closure over and still have to copy an additional 2200 - 4000 paths, when the runtime closure already existed.
I'm not entirely sure how introduced this behaviour. The only thing I there was a function allowing flakes to be built remotely. Copying results to the target host was not touched in that PR.
Previous behavior created a realised outpath: new behavior creates a derivation, then 's it: for a to be valid, it needs every single .drv dependency. For me, this is 2000-5000 and FOD paths which need to be instantiated and copied; as opposed to ~120 new outpaths
I guess I'm missing something. With the previous behaviour, it was not possible to build remotely, so you had to do . If you give the same params now, it will only copy the out paths, not the derivations. (And to clarify: it's not that important to me, but I always like to know what I could have done better.)
I guess the previous built the toplevel locally, then pushed it. Now this behavior pushes the .drv closure over, then realises it. Probably not that bad if the target host has a small configuration, but hosts which have 2-3 dozen services, and several dozen packages start to get .drv closures in the thousands, and it does become quite painful. I guess I would have prefered to be the default (which also would have retained previous behavior). And realisation on the target host should be done with
Change:
<del> { stdenv, lib, fetchFromGitHub, fetchpatch, cmake, pkg-config </del> <ins> { stdenv, lib, fetchFromGitHub, cmake, pkg-config </ins> , alsa-lib, asio, avahi, boost179, flac, libogg, libvorbis, libopus, soxr , IOKit, AudioToolbox , aixlog, popl , pulseaudioSupport ? false, libpulseaudio , nixosTests }: <del> assert pulseaudioSupport -> libpulseaudio != null; </del> stdenv.mkDerivation rec { pname = "snapcast"; <del> version = "0.27.0"; </del> <ins> version = "0.28.0"; </ins> src = fetchFromGitHub { owner  = "badaix"; repo   = "snapcast"; rev    = "v${version}"; <del> sha256 = "sha256-dlK1xQQqst4VQjioC7MZzqXwMC+JfqtvnD5lrOqGhYI="; </del> <ins> sha256 = "sha256-XxpiLojs1TI3qM7yXS+OPcHKo6pLcfJ+Eop7GjQ4HQw="; </ins> }; <del> patches = [ # Can be removed with next release after 0.27.0 (fetchpatch { name = "include-cstdint.patch"; url = "https://github.com/badaix/snapcast/commit/481f08199ca31c60c9a3475f1064e6b06a503d12.patch"; hash = "sha256-klpvmBpBAlBMtcgnNfW6X6vDbJFnOuOsPUDXcNf5tGc="; }) ]; </del> nativeBuildInputs = [ cmake pkg-config ]; # snapcast also supports building against tremor but as we have libogg, that's # not needed

Discussion:
Package name: snapcast Latest released version: 0.28.0 <!-- Search your package here: --- Current version on the unstable channel: 0.27.0 Current version on the stable/release channel: 0.27.0 <!-- 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]: