jiebi/CodeConvo huggingface dataset:
Change:
rapidgzip = callPackage ../development/python-modules/rapidgzip { inherit (pkgs) nasm; }; <ins> rapidocr-onnxruntime = callPackage ../development/python-modules/rapidocr-onnxruntime { }; </ins> rapt-ble = callPackage ../development/python-modules/rapt-ble { }; rarfile = callPackage ../development/python-modules/rarfile {

Discussion:
Project description Awesome OCR multiple programing languages toolkits based on ONNXRuntime, OpenVION and PaddlePaddle. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: asl20 platforms: linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Can you help for packaging this thing, I tried, without luck so far :S
I tried packaging this and while it does build, but for some reason it fails to run, complaining that it couldn't find the module.
Could you also share the or eventually create a draft PR so we can collaborate?
I think I'll just make a draft PR instead :D
Yeah that's what I suggest in the second half of the sentence :D
Thank you !
Change:
, makeWrapper , moreutils , napi-rs-cli <del> , nodejs_18 </del> <ins> , nodejs_20 </ins> , patchutils_0_4_2 , pkg-config , python3

Discussion:
When signing in to the Bitwarden, I am met with the following . I have KDE wallet turned off, and my NixOS and nixpkgs channel are both set to stable. I also have another nix machine that runs NixOS and nixpkgs on unstable and this bug does not occur despite having KDE wallet turned off there as well. Bug is potentially tied to Steps to reproduce the behavior: off KDE wallet in to Bitwarden-desktop stable. Should sign in without issue despite KDE wallet being disabled. ! A package update would be great, as my understanding is this was fixed in an update by Bitwarden devs.
Change:
, desktop-file-utils, libSM, imagemagick }: stdenv.mkDerivation rec { <del> version = "20.08"; </del> <ins> version = "20.09"; </ins> pname = "mediainfo-gui"; src = fetchurl { url = "https://mediaarea.net/download/source/mediainfo/${version}/mediainfo_${version}.tar.xz"; <del> sha256 = "1baf2dj5s3g1x4ssqli1b2r1203syk42m09zhp36qcinmfixv11l"; </del> <ins> sha256 = "0rqg9z7s5bk7vlvjrs4gackzg7ib05a0dffi2ihsjf5a7kw7wcir"; </ins> }; nativeBuildInputs = [ autoreconfHook pkgconfig ];

Discussion:
, CVSSv3=7.8 (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives. Cc
Remediated - thus closing.
Change:
<del> { lib , fetchFromGitHub , dooit , python3 , testers , nix-update-script </del> <ins> { lib, fetchFromGitHub, dooit, python311, testers, nix-update-script, </ins> }: <ins> let python3 = python311; in </ins> python3.pkgs.buildPythonApplication rec { pname = "dooit"; version = "2.2.0";

Discussion:
Steps to reproduce the behavior: dooit I use nixos-unstable. NixVim and Helix with tree-sitter are not the cause of an issue, I can do a rebuild with them, error occurs then I add dooit. <!-- --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
If you do not ping listed maintainers for package (ie in ) they are not going to see this issue. Ping: Log with full chain: I assume from this fix for ( was with it in ): the intended way to fix it is to use for and not fix build for python 3.12.
Oh, sorry, I made a mistake with the formatting when I mentioned the package maintainer, I left it in the comment
Sorry, I forgot to come back to this... I was trying to see if I could fix textual/tree-sitter-languages/tree-sitter0_21 chain with python312. We can pin to 311 in the meantime.
That one seems to be relatively simple too ( had upstream pr - replacing with ). So something like this makes it build with python 3.12: <details<summarytree-sitter021 patch</summary</detailsIt was not accepted upstream, but they fully changed these parts around v0.23 so there is no used anymore. I am not sure if needs to be in this pinned state building with only python 3.11 for some reason.
Change:
license = licenses.gpl2Plus; platforms = platforms.linux; maintainers = [ maintainers.goibhniu ]; <ins> # Broken for Musl at 2023-12-28: # https://github.com/NixOS/nixpkgs/issues/277198 broken = stdenv.hostPlatform.isMusl; </ins> }; }

Discussion:
Steps to reproduce the behavior: ! <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --ping Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: https://dbus-
I have an interest in this package [as it comes often in musl builds] but I don't know fixing it. Would you have any clue?
Something like should work, it would just be better to go to staging.
This builds fine now.
Change:
<del> { fetchFromGitHub, python2Packages, stdenv, git, graphviz }: </del> <ins> { python3Packages, lib, git, graphviz }: </ins> <del> python2Packages.buildPythonApplication rec { </del> <ins> python3Packages.buildPythonApplication rec { </ins> pname = "git-big-picture"; <del> version = "0.10.1"; </del> <ins> version = "1.1.1"; format = "wheel"; </ins> <del> src = fetchFromGitHub { owner = "esc"; repo = pname; rev = "v${version}"; sha256 = "0b0zdq7d7k7f6p3wwc799347fraphbr20rxd1ysnc4xi1cj4wpmi"; </del> <ins> src = python3Packages.fetchPypi { inherit format version; pname = "git_big_picture";  # underscores needed for working download URL python = "py3";  # i.e. no Python 2.7 sha256 = "a20a480057ced1585c4c38497d27a5012f12dd29697313f0bb8fa6ddbb5c17d8"; </ins> }; <del> buildInputs = [ git graphviz ]; checkInputs = [ git ]; </del> postFixup = '' wrapProgram $out/bin/git-big-picture  <del> --prefix PATH ":" ${ stdenv.lib.makeBinPath buildInputs  } </del> <ins> --prefix PATH ":" ${ lib.makeBinPath [ git graphviz ]  } </ins> ''; meta = { description = "Tool for visualization of Git repositories"; <del> homepage = "https://github.com/esc/git-big-picture"; license = stdenv.lib.licenses.gpl3; platforms = stdenv.lib.platforms.linux; maintainers = [ stdenv.lib.maintainers.nthorne ]; </del> <ins> homepage = "https://github.com/git-big-picture/git-big-picture"; license = lib.licenses.gpl3Plus; platforms = lib.platforms.linux; maintainers = [ lib.maintainers.nthorne ]; </ins> }; }

Discussion:
, CVSSv3=9.8 (nixos-20.09) Scanned versions: nixos-20.09: . Cc
Change:
settingsSha256 = "0n4pj8dzkr7ccwrn5p46mn59cnijdhg8zmn3idjzrk56pq0hbgjr"; persistencedSha256 = "0bnjr0smhlwlqpyg9m6lca3b7brl2mw8aypc6p7525dn9d9kv6kb"; <del> patches = lib.optional (kernel.meta.branch == "4.19") ./drm_mode_connector.patch; </del> <ins> patches = [ (fetchurl { url = "https://git.archlinux.org/svntogit/packages.git/plain/trunk/kernel-4.16.patch?h=2ad07241ea525a6b6b555b6cb96a97634a4b2cb0"; sha256 = "11b3dp0na496rn13v5q4k66bf61174800g36rcwj42r0xj9cfak2"; }) (fetchurl { url = "https://git.archlinux.org/svntogit/packages.git/plain/trunk/kernel-5.1.patch?h=42d50ef8d6048608d18bdf2c296dd335260c5a1a"; sha256 = "03v46ym2bcckg9q2xrilkg21hfiwypr6gl4jmly2q3m4yza9ja6r"; })]; </ins> }; legacy_340 = generic {

Discussion:
doesn't build with or . Please run and paste the results.
In the case of nvidia, we need to add patches for more recent kernels. That's what other Distros do too: In the case of debian, they seem to reside in , but behind a loginwall. Can you have a look at
Fixed by .
Change:
hash = "sha256-v0jWEZo06vltEq//suGrvJ/AeeDxUG5CCFhbf03q34w="; }; <ins> patches = [ (fetchpatch2 { # https://github.com/tchellomello/python-amcrest/pull/235 name = "replace-distutils.patch"; url = "https://github.com/tchellomello/python-amcrest/commit/ec56049c0f5b49bc4c5bcf0acb7fea89ec1c1df4.patch"; hash = "sha256-ym+Bn795y+JqhNMk4NPnOVr3DwO9DkUV0d9LEaz3CMo="; }) ]; </ins> build-system = [ setuptools ]; dependencies = [

Discussion:
Steps to reproduce the behavior: -rebuild switch Here is my config for home-assistant: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
asdf = callPackage ../development/python-modules/asdf { }; <ins> asdf-astropy = callPackage ../development/python-modules/asdf-astropy { }; asdf-coordinates-schemas = callPackage ../development/python-modules/asdf-coordinates-schemas { }; </ins> asdf-standard = callPackage ../development/python-modules/asdf-standard { }; asdf-transform-schemas = callPackage ../development/python-modules/asdf-transform-schemas { }; <ins> asdf-wcs-schemas = callPackage ../development/python-modules/asdf-wcs-schemas { }; </ins> ase = callPackage ../development/python-modules/ase { }; asf-search = callPackage ../development/python-modules/asf-search { };

Discussion:
Project description Photutils is an Astropy package for detection and photometry of astronomical sources. Metadata homepage URL: source URL: license: 3-clause BSD platforms: unix, linux, darwin, Linux, Darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I could to built here withou errors from source, just the 1.11.0 version, it is not the latest one. My nix block:
Change:
stdenv.mkDerivation (finalAttrs: { pname = "lunacy"; <del> version = "9.6.2"; </del> <ins> version = "10.0.1"; </ins> src = fetchurl { url = "https://lcdn.icons8.com/setup/Lunacy_${finalAttrs.version}.deb"; <del> hash = "sha256-iTne+vUnv+O/+QUKgSUr+ACdZpXrvRQkZmqghJH1fDw="; </del> <ins> hash = "sha256-roD/bKv1N2sru/tZ6Zl1J2AyY1mgj2ssB2a42kwBNHM="; </ins> }; unpackCmd = ''

Discussion:
Package name: Latest released version: 10.0.1 <!-- Search your package here: --- Current version on the unstable channel: 9.6.2 Current version on the stable/release channel: 9.6.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]:
Change:
libsoup spice-protocol spice-gtk libepoxy at-spi2-core openssl gnome.adwaita-icon-theme json-glib libsodium webkitgtk harfbuzz <del> ] ++ optionals withLibsecret [ libsecret ]; </del> <ins> ] ++ optionals withLibsecret [ libsecret ] ++ optionals withVte [ vte ]; </ins> cmakeFlags = [ <del> "-DWITH_VTE=OFF" </del> <ins> "-DWITH_VTE=${if withVte then "ON" else "OFF"}" </ins> "-DWITH_TELEPATHY=OFF" "-DWITH_AVAHI=OFF" "-DWITH_LIBSECRET=${if withLibsecret then "ON" else "OFF"}"

Discussion:
I am trying to use 'remmina' as a SSH client. But when I click "Create a new connection profile", there is no SSH plugin in the list of plugins. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
Hi, i am new on nix and currently trying to setup a copy my current desktop in a vm with nix. so i came around this issue, as it got recently a label , i hope that its not a nerco bump. Remmina is missing the ssh plugin as the compiler flags are disabling VTE. See So its needed to add vte as input for the build and change the build flag. i did basically do the following override in my setup (flake), which results in a remmina binary which is capable to be used as ssh client Changing the default package should just need the import for vte, adding the buildInput and swich to . Sadly i am not yet to familiar with the contributing rules here for a PR i am just dropping that comment. Other distributions use remmina with SSH/VTE enabled (checked ubuntu on work machine and archlinux on private) and upstream advertise support as SSH client directly on the it sounds reasonable to activate it on default. Current packaging includes for SFTP support, which still gets enabled even when VTE is OFF.
Change:
, runCommandLocal , bison , flex <del> , llvmPackages_8 </del> <ins> , llvmPackages_11 , lld_11 </ins> , opencl-clang , python3 , spirv-llvm-translator

Discussion:
, current version: 20.34. desired version: 21.42. maintainers: The packages version is quite old and doesn't work properly on 11th gen cpus. There are also other PR which are interwoven with this such as: And also an issue that might be related To update this properly I think we need to update at least the following packages: , , and .
Change:
<ins> { buildFHSEnv, envision-unwrapped }: buildFHSEnv { name = "envision"; extraOutputsToInstall = [ "dev" ]; strictDeps = true; targetPkgs = pkgs: [ pkgs.envision-unwrapped ] ++ (with pkgs; [ glibc gcc ]) ++ ( # OpenHMD dependencies pkgs.openhmd.buildInputs ++ pkgs.openhmd.nativeBuildInputs ) ++ ( # OpenComposite dependencies pkgs.opencomposite.buildInputs ++ pkgs.opencomposite.nativeBuildInputs ++ [ pkgs.boost ] ) ++ ( # Monado dependencies ( pkgs.monado.buildInputs ++ pkgs.monado.nativeBuildInputs ++ (with pkgs; [ # Additional dependencies required by Monado when built using Envision mesa shaderc xorg.libX11 xorg.libxcb xorg.libXrandr xorg.libXrender xorg.xorgproto ]) ) ) ++ ( # SteamVR driver dependencies [ pkgs.zlib ]) ++ ( # WiVRn dependencies # TODO: Replace with https://github.com/NixOS/nixpkgs/pull/316975 once merged (with pkgs; [ avahi cmake cli11 ffmpeg git gst_all_1.gstreamer gst_all_1.gst-plugins-base libmd libdrm libpulseaudio libva ninja nlohmann_json openxr-loader pipewire systemdLibs # udev vulkan-loader vulkan-headers x264 ]) ++ (with pkgs; [ android-tools # For adb installing WiVRn APKs ]) ); profile = '' export CMAKE_LIBRARY_PATH=/usr/lib export CMAKE_INCLUDE_PATH=/usr/include export PKG_CONFIG_PATH=/usr/lib/pkgconfig:/usr/share/pkgconfig ''; extraInstallCommands = '' mkdir -p $out/share/applications $out/share/metainfo ln -s ${envision-unwrapped}/share/envision $out/share ln -s ${envision-unwrapped}/share/icons $out/share ln -s ${envision-unwrapped}/share/applications/org.gabmus.envision.desktop $out/share/applications ln -s ${envision-unwrapped}/share/metainfo/org.gabmus.envision.appdata.xml $out/share/metainfo ''; runScript = "envision"; meta = envision-unwrapped.meta // { description = "${envision-unwrapped.meta.description} (with build environment)"; }; } </ins>

Discussion:
Project description UI for building, configuring and running Monado, the open source OpenXR runtime. Metadata homepage URL: source URL: license: agpl3 platforms: unix, linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
To my information, software without a stable release isnt accepted yet.
Not even in unstable? Fair enough, I guess.
unstable automatically becomes stable, so yes :) I think once a release is done (even 0.x), it can be packaged, but don't take my word as the ultimate truth, please :sweat_smile:
This appears to be incorrect. was merged targeting a specific commit (despite actually having stable releases).
This is indeed incorrect; there are even specific rules for the attribute of unreleased versions.
Change:
<del> commit 96c271f8ab2be7ea4199078ea65ac50c6ada4685 Author: Pawel Hajdan, Jr <phajdan.jr@chromium.org> Date:   Wed Jul 26 21:51:54 2017 +0000 wip diff --git a/tools/gn/bootstrap/bootstrap.py b/tools/gn/bootstrap/bootstrap.py index 1390560f8e37..ff2ae57c46b0 100755 --- a/tools/gn/bootstrap/bootstrap.py +++ b/tools/gn/bootstrap/bootstrap.py @@ -449,6 +449,7 @@ def write_gn_ninja(path, root_gen_dir, options): 'base/metrics/histogram_base.cc', 'base/metrics/histogram_functions.cc', 'base/metrics/histogram_samples.cc', +      'base/metrics/histogram_snapshot_manager.cc', 'base/metrics/metrics_hashes.cc', 'base/metrics/persistent_histogram_allocator.cc', 'base/metrics/persistent_memory_allocator.cc', @@ -534,7 +535,7 @@ def write_gn_ninja(path, root_gen_dir, options): 'base/trace_event/heap_profiler_allocation_context_tracker.cc', 'base/trace_event/heap_profiler_allocation_register.cc', 'base/trace_event/heap_profiler_event_filter.cc', -      'base/trace_event/heap_profiler_event_writer.cc', +      'base/trace_event/heap_profiler_heap_dump_writer.cc', 'base/trace_event/heap_profiler_serialization_state.cc', 'base/trace_event/heap_profiler_stack_frame_deduplicator.cc', 'base/trace_event/heap_profiler_type_name_deduplicator.cc', </del>  No newline at end of file

Discussion:
I try to install vivaldi-ffmpeg-codecs, it tries to build it — Just try to install vivaldi-ffmpeg-codecs. there was the same thing in previous 18.03.
I found that was removed in . Here it is in the : And the helpful thread:
I tried bluntly update the chromium source where codecs stored. But it failed:
That patch is marked .
Let's call submitter:
I tried bluntly update the chromium source where codecs stored. This is the right approach, but you'll also have to remove the old patches and check whether you need any newer . The patches used by the are usually a good starting point.
So unless I'm mistaken, shouldn't we just build chromium & provide a vivaldi output? The chromium build is huge & we don't want Hydra to have to do it multiple times. What's the intended use of ffmpeg-vivaldi-codecs? I think we can disable libcxx building with in args, though.
As i can see, there are some license issues (?) with something like h264. So we build in on "client" side from sources (probably it's x264)... I don't know exactly...
Providing a Vivaldi output from chromium (as suggests) is difficult because chromium moves at a different speed than Vivaldi, so the resulting library may not fit properly. I don't know how often this happens, but it looks like upstream ffmpeg changes their ABI fairly often. The build actually isn't that much of an issue. The only difficulty is having to download and extract the full chromium tarball, the compile times are short as we only need . What's the intended use of ffmpeg-vivaldi-codecs? Vivaldi (the company) cannot distribute certain codecs in ffmpeg in their packages, so we have to compile that separately.
Change:
<del> commit 96c271f8ab2be7ea4199078ea65ac50c6ada4685 Author: Pawel Hajdan, Jr <phajdan.jr@chromium.org> Date:   Wed Jul 26 21:51:54 2017 +0000 wip diff --git a/tools/gn/bootstrap/bootstrap.py b/tools/gn/bootstrap/bootstrap.py index 1390560f8e37..ff2ae57c46b0 100755 --- a/tools/gn/bootstrap/bootstrap.py +++ b/tools/gn/bootstrap/bootstrap.py @@ -449,6 +449,7 @@ def write_gn_ninja(path, root_gen_dir, options): 'base/metrics/histogram_base.cc', 'base/metrics/histogram_functions.cc', 'base/metrics/histogram_samples.cc', +      'base/metrics/histogram_snapshot_manager.cc', 'base/metrics/metrics_hashes.cc', 'base/metrics/persistent_histogram_allocator.cc', 'base/metrics/persistent_memory_allocator.cc', @@ -534,7 +535,7 @@ def write_gn_ninja(path, root_gen_dir, options): 'base/trace_event/heap_profiler_allocation_context_tracker.cc', 'base/trace_event/heap_profiler_allocation_register.cc', 'base/trace_event/heap_profiler_event_filter.cc', -      'base/trace_event/heap_profiler_event_writer.cc', +      'base/trace_event/heap_profiler_heap_dump_writer.cc', 'base/trace_event/heap_profiler_serialization_state.cc', 'base/trace_event/heap_profiler_stack_frame_deduplicator.cc', 'base/trace_event/heap_profiler_type_name_deduplicator.cc', </del>  No newline at end of file

Discussion:
This probably isn't a strictly NixOS issue, but nevertheless should be mentioned. The hash for vivaldi-stable2.1.1337.51-1 has changed. The old one in nixpkgs is 08x6abyz65vx4ycj8ys8sib9z1adb8ybmnrqjck69b30kbz78rj2, while nix-env reports 00rxp6rardxjg17g2b28y2rj8szqlainp4ga6c58z981zkxvdlls. to unstable channels. -env -i vivaldi system: host os: multi-user?: sandbox: version: channels(void): channels(root): nixpkgs:
unfortunately, sometimes software projects update different package sources with different sha256sums on their website, which will then error during build, until it gets fixed again Can you add a Pull Request, updating the hash in
Change:
play-with-mpv = callPackage ../tools/video/play-with-mpv { }; <del> plausible = callPackage ../servers/web-apps/plausible { }; </del> <ins> plausible = callPackage ../servers/web-apps/plausible { nodejs = nodejs-16_x; }; </ins> pam-reattach = callPackage ../os-specific/darwin/pam-reattach { };

Discussion:
Steps to reproduce the behavior: a system configuration with plausible as a service (I'm on NixOS 22.11) I'm new to Nix, so I can't make the changes myself, but I've analyzed the issue and have found the problem. The issue is that when the package was made, nodejs included an older npm version (<9) which still had the command. This has been removed in newer nodejs versions however. This causes an error, because is used in the repository of plausible (atleast for the version that is pinned here). It can either be fixed by using an older nodejs package, using a newer version of the plausible repository or not using the deploy script from the repository and instead calling webpack manually using npm exec. Unfortunately, there are currently no maintainers. was originally a maintainer, but has removed himself. Please run and paste the result.
I'd be willing to help here in some capacity, but as I've said I'm new to Nix, so I would atleast need some guidance. I feel there are two ways of going forward here: either updating the package to not use while still pinning the same underlying version of plausible OR updating the package to use a newer version of plausible, which would mitigate the issue. With the first solution, I'm not sure what would happen with the version number. Would it stay the same, basically applying a fix for the already released version so it works again? Or would the version be incremented to something else (1.4.4.2?) to reflect the change, with the already published version remaining in a broken state? It would be helpful if someone with more experience could comment on this topic, or atleast point me in the right direction. I saw some stuff in the docs about backporting, but I'm not sure if this applies here.
can you test
Hey, thank you for working on this. Unfortunately, it does not seem to be working for me. Behaviour is as before. I ran on your branch.
can you provide exact commands you used to get right version of nixpkgs, including full command for nixos-rebuild
Sure. My config for plausible looks like this:
there is a typo should be
Ahh, sorry. With the correct command the build works now. Thank you.

I'm still getting another error when the unit is actually started, but it seems unrelated and probably has something to do with my config.
were you successful at starting plausible ? if so could you share your configuration ?