jiebi/CodeConvo huggingface dataset:
Change:
smu = callPackage ../tools/text/smu { }; <ins> smpq = callPackage ../applications/misc/smpq { }; </ins> sn0int = callPackage ../tools/security/sn0int { }; snabb = callPackage ../tools/networking/snabb { };

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: devilutionx <!-- 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.2.1 desired version: 1.3.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. There are a number of changes in the new version, many of which make it difficult to package for nixpkgs.
Change:
}; nativeBuildInputs = [ <del> cython </del> <ins> cython_3 </ins> ]; propagatedBuildInputs = [

Discussion:
Steps to reproduce the behavior: Also fails on Hydra: I think the issue might be an old version of cython? Hydra lists python3.11-cython-0.29.36 which seems to be before Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Overriding the package to use instead of seems to do the trick, but it breaks the pytestCheckPhase. I put this in my overlay:
Change:
<ins> { unrar , fetchzip }: unrar.overrideAttrs (finalAttrs: _: { version = "6.2.12"; src = fetchzip { url = "https://www.rarlab.com/rar/unrarsrc-${finalAttrs.version}.tar.gz"; stripRoot = false; hash = "sha256-VAL3o9JGmkAcEssa/P/SL9nyxnigb7dX9YZBHrG9f0A="; }; sourceRoot = finalAttrs.src.name; }) </ins>

Discussion:
Package name: unrar Latest released version: 7.00 beta 3 Current version on the unstable channel: 6.2.12 Current version on the stable/release channel: 6.2.12 I receive more and more RAR files which are created with Unrar 7.00 beta versions / require a more recent version tan 6.2.12 I would appreciated if the existing unrar package can be updated or a new unrar-beta package be proposed .. Changelog : Notify maintainers
There was an automatic update in that I marked as draft, exactly because it's in beta. I'd much rather add a new package. what do you think?
I don't think we should update to the beta either. Sometimes I think about adding beta and release candidate versions to package , but that would be a nixpkgs policy discussion.
If people are still creating new RAR files then I don't want to be maintainer of this package. Stop using RAR.
Change:
<xi:include href="maven.section.xml" /> <xi:include href="node.section.xml" /> <xi:include href="ocaml.section.xml" /> <del> <xi:include href="perl.xml" /> </del> <ins> <xi:include href="perl.section.xml" /> </ins> <xi:include href="php.section.xml" /> <xi:include href="python.section.xml" /> <xi:include href="qt.section.xml" />

Discussion:
This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! in this issue that you intend to work on it. (Please also post if you stop working on it) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.
Done. Works on my machine. Will send PR. Roast me.
Change:
install -Dm 755 ./bun $out/bin/bun runHook postInstall ''; <ins> passthru = { sources = { "aarch64-darwin" = fetchurl { url = "https://github.com/oven-sh/bun/releases/download/bun-v${version}/bun-darwin-aarch64.zip"; sha256 = "RYTRcc8xccRmxuKOXwX3bBWJSXLI2/XfH4/7ZdcUBdE="; }; "aarch64-linux" = fetchurl { url = "https://github.com/oven-sh/bun/releases/download/bun-v${version}/bun-linux-aarch64.zip"; sha256 = "LixLrzSsgbXyfpFKiksM4zNS5iDU3tXOrr7fP8yJknM="; }; "x86_64-darwin" = fetchurl { url = "https://github.com/oven-sh/bun/releases/download/bun-v${version}/bun-darwin-x64.zip"; sha256 = "SGZcT2uVy6egr99FzyaykUWLuZBqDsvbCM/lsgy//g0="; }; "x86_64-linux" = fetchurl { url = "https://github.com/oven-sh/bun/releases/download/bun-v${version}/bun-linux-x64.zip"; sha256 = "ssZtJi+CEVn7MjPMqFkwv1lnwE7a7ttkmiuoT0Y6wao="; }; }; updateScript = writeShellScript "update-bun" '' set -o errexit export PATH="${lib.makeBinPath [ curl jq common-updater-scripts ]}" NEW_VERSION=$(curl --silent https://api.github.com/repos/oven-sh/bun/releases/latest | jq '.tag_name | ltrimstr("bun-v")' --raw-output) if [[ "${version}" = "$NEW_VERSION" ]]; then echo "The new version same as the old version." exit 0 fi for platform in ${lib.escapeShellArgs meta.platforms}; do update-source-version "bun" "0" "${lib.fakeSha256}" --source-key="sources.$platform" update-source-version "bun" "$NEW_VERSION" --source-key="sources.$platform" done ''; }; </ins> meta = with lib; { homepage = "https://bun.sh"; changelog = "https://github.com/Jarred-Sumner/bun/releases/tag/bun-v${version}";

Discussion:
Bun should have an auto-update field so that it can be automatically updated. N/A Please run and paste the result.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
docker-credential-gcr = callPackage ../tools/admin/docker-credential-gcr { }; <ins> docker-credential-helpers = callPackage ../tools/admin/docker-credential-helpers { }; </ins> doodle = callPackage ../applications/search/doodle { }; dr14_tmeter = callPackage ../applications/audio/dr14_tmeter { };

Discussion:
Project description docker-credential-helpers is a suite of programs to use native stores to keep Docker credentials safe. Metadata (same as source) source URL: license: mit platforms: unix, linux, darwin Please note that contains multiple programs: (Windows specific) These might want to be shipped as independent packages Some of them are platform specific while others like , should work on both darwin (), linux and BSDs as well.
Change:
whatever the {command}`setfont` program considers the default font. Can be either a font name or a path to a PSF font file. <ins> Use `null` to let the kernel choose a built-in font. The default is 8x16, and, as of Linux 5.3, Terminus 32 bold for display resolutions of 2560x1080 and higher. These fonts cover the [IBM437][] character set. [IBM437]: https://en.wikipedia.org/wiki/Code_page_437 </ins> ''; };

Discussion:
NixOS's default kernel configuration only enables the 8x8 and 8x16 fonts. This is not ideal, because they are too small for high-resolution displays. The current workaround used by is to set . There are problems with this however: during early boot, before the GPU drivers are loaded, the firmware or bootloader may initialize the display at a lower resolution, resulting in an oversized font in fact, the hidpi module sets , which in my opinion is a bad idea, because it will force switching to a low resolution when the firmware could have set us up with a high-res framebuffer; this also breaks seamless boot for those who care (sd-boot's default is to keep the mode unchanged) resolution switches reset the font to the kernel default, and under certain circumstances it seems a race condition can prevent userspace from setting the font correctly again The kernel is actually able to select an appropriate font for the current resolution using a simple heuristic since mid-2019 (). This bypasses the problems listed above and ensures a good font is always selected after resolution switches. The only requirement appears to be that the fonts must be built into the kernel. Font-related kconfig options as configured by NixOS: Arch Linux: So Arch enables the default 8x16 and Terminus 16x32 (the same font that the hidpi module sets). The observed behavior on Arch is that it seamlessly switches fonts after mode switches, and I've never seen this break since it has been enabled.
Same issue here with a NVIDIA card and a 3840x1600 monitor. tty0 console text covers the entire screen. I couldn't resolve this issue manually with and (DP-3 is my monitor). Setting the font manually to the default value () gives the right font size but this particular font doesn't have antialiasing which looks quite bad on a HIDPI monitor.
There's no antialiasing in console fonts, they're all bitmap fonts.
Gotcha, thanks. On side note, I looked for a different consolefont and came up with this. Looks a lot better now :smile:
Change:
dontWrapGApps = true; preFixup = '' <del> makeWrapperArgs+=("''${gappsWrapperArgs[@]}") </del> <ins> makeWrapperArgs+=( "''${gappsWrapperArgs[@]}" --prefix PATH : ${lib.makeBinPath [ xdotool wl-clipboard ]} ) </ins> ''; meta = {

Discussion:
The emoji picker terminates unexpectedly upon clicking an emoji. Steps to reproduce the behavior: any X desktop environment, and make sure is not installed an emoji error message: The emoji is inserted in the current window and the emoji picker exits gracefully. N/A N/A Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thank you!
Change:
cargo-all-features = callPackage ../development/tools/rust/cargo-all-features { }; cargo-apk = callPackage ../development/tools/rust/cargo-apk { }; cargo-audit = callPackage ../development/tools/rust/cargo-audit { <del> inherit (darwin.apple_sdk.frameworks) Security; </del> <ins> inherit (darwin.apple_sdk.frameworks) Security SystemConfiguration; </ins> }; cargo-benchcmp = callPackage ../development/tools/rust/cargo-benchcmp { }; cargo-binstall = callPackage ../development/tools/rust/cargo-binstall { };

Discussion:
Steps to reproduce the behavior: libgit2 Just tried to update to current nixos-unstable but this build failure prevented that. <!-- 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]:
The build failure is not happening for me. I need more information about what you are building and how you are building it exactly.
Hi I'm observing this with
Suspect caused by
that could certainly be the case, I only tested libgit2 but I am removing all older libgit2 versions in which should also fix this issue
Sorry for missing that. It comes up when building cargo-update-13.3.0.
Yep - I noticed this because the latest version of crane doesn't work in all cases: cargo-audit can't be built on nixpkgs latest.
This due to the usage of system level http-parser instead of the bundled http-parser which handles . An easy fix that works: However, I am not sure what the other implications are when using the bundled version versus the system-wide version which was introduced .
Change:
python3Packages.buildPythonApplication rec { pname = "pyradio"; <del> version = "0.8.7.2"; </del> <ins> version = "0.8.9.9"; </ins> src = fetchFromGitHub { owner = "coderholic"; repo = pname; rev = version; <del> sha256 = "0h2sxaqpmc1d1kpvpbcs9wymgzhx25x0x9p7dbyfw9r90i6123q1"; </del> <ins> sha256 = "04asw5alkkf2q5iixswarj6ddb0y4a6ixm7cckl6204jiyxpv6kc"; </ins> }; checkPhase = ''

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! --- [x] I am a noob and tried to fulfill the above requirements to the best of my abilities and understanding of github name: pyradio <!-- 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.8.7.2 desired version: 0.8.9.9 at least 0.8.8.5 (last of 0.8.8 chain) <!-- 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. The current version (0.8.7.2) is crashing for me when increasing/decreasing the volume. (Fixed in 0.8.8) The newest 0.8.9 versions feature a radio-browser-overlay, which would be very nice.
PR in
Change:
, stdenv , callPackage , fetchFromGitHub <ins> , fetchurl </ins> , rocmUpdateScript , makeWrapper , cmake

Discussion:
The build for a lot of ROCm components broke with , which updated CMake from 3.29.0 to 3.29.1, basically breaking all of ROCm. This commit was merged via and recently made its way from staging into unstable in the last few days. Steps to reproduce the behavior: The builds for a number of ROCm components now fail with error messages like the following: This is possible related to how ROCm uses of CMake incorrectly. See , , and I have posted about this issue on the CMake discourse to verify if this is considered a bug in CMake, as suggested by <!-- 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]:
The first recommendation we got from CMake was updating to 3.29.2, which has already been merged to staging:
I was able to confirm that with that commit that updates CMake to 3.29.2 builds again. I will leave this issue open until the relevant changes make it into unstable.
is there an easy way to temporarily use the cmake version from staging in my configuration for a specific package, without using staging for every dependency of that package?
A workaround could be to apply this as patch:
One possible fix would be overriding the CMake version that is used inside of ROCm to update to the newer version, and merging that with a PR to master. The advantage of this compared to would be that we do not need to worry about the fix actually breaking the build once the version update lands (I have not tested that this happens, but I could imagine it does). It might be a good idea to do this by making the overridden version of a part of , and removing extra dependency on elsewhere in ROCm. Also ROCm 5.7 and 6.0 are both broken, so if we want to merge a fix before the CMake version update lands in unstable, we should fix both. I am not working on a fix for this, and I couldn't merge one, but I'm happy to review PRs.
Change:
freeformType = let validSettingsPrimitiveTypes = oneOf [ int str bool float ]; validSettingsTypes = oneOf [ validSettingsPrimitiveTypes (listOf validSettingsPrimitiveTypes) ]; <del> settingsType = (attrsOf validSettingsTypes); in attrsOf (oneOf [ string settingsType (listOf settingsType) ]) </del> <ins> settingsType = oneOf [ str (attrsOf validSettingsTypes) ]; in attrsOf (oneOf [ settingsType (listOf settingsType) ]) </ins> // { description = '' unbound.conf configuration type. The format consist of an attribute set of settings. Each settings can be either one value, a list of

Discussion:
Describe the bug Unbound allows the "include" directive to appear more than once. : However the type definition of is too strict. This code raises an error: Notify maintainers Metadata Maintainer information:
Could you provide me with the value you set the option to?
An example has been provided above. Simply set to a list of string. The service will fail, but it should work. You can try
Ah yes indeed, sorry I didn't see that. I'll open a PR that fixes this.
Change:
''; }; <del> open = lib.mkEnableOption '' the open source NVIDIA kernel module </del> <ins> open = lib.mkOption { example = true; description = "Whether to enable the open source NVIDIA kernel module."; type = lib.types.bool; defaultText = lib.literalExpression '' lib.mkIf (lib.versionOlder config.hardware.nvidia.package.version "560") false ''; }; gsp.enable = lib.mkEnableOption '' the GPU System Processor (GSP) on the video card </ins> '' // { <del> defaultText = lib.literalExpression ''lib.versionAtLeast config.hardware.nvidia.package.version "560"''; </del> <ins> defaultText = lib.literalExpression '' config.hardware.nvidia.open || lib.versionAtLeast config.hardware.nvidia.package.version "555" ''; </ins> }; }; };

Discussion:
The RPATH of , as installed by the standard nvidia package () in nixos 23.11, has no entry for , causing it to fail if anyone actually used that particular interface. Steps to reproduce the behavior: The nvidia package should set proper RPATHs on the installed libraries. I ran into this because I was trying to clean up the steam package of issues, and steam's does a lot of sanity checking of its environment and reported the issue from inside the FHS environment. <!-- 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]:
That library is an internal compatibility layer for openssl1.1. Since we link openssl3 into the nvidia driver it never gets used and is meant to fail to load. Since NixOS makes sure that openssl3 is always available this library is functionally useless. We could probably just remove that file (like we do with ) to regain some disk space and satisfy the checks you mentioned.
Sounds good. Better to not ship it than ship it broken, especially if nobody needs it.
Change:
protocols.source  = pkgs.iana-etc + "/etc/protocols"; # /etc/hosts: Hostname-to-IP mappings. <del> hosts.source = pkgs.runCommand "hosts" {} '' cat ${escapeShellArgs cfg.hostFiles} > $out ''; </del> <ins> hosts.source = pkgs.concatText "hosts" cfg.hostFiles; </ins> # /etc/netgroup: Network-wide groups. netgroup.text = mkDefault "";

Discussion:
In my config I have and when building it gives me the following error: However if I replace it with it builds without errors. Even weirder, If I do it works without problems. The configuration builds normally system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
Tried surrounding the path in quotes?
wouldn't that make a string and not include the file in the store? As it stands, the files does get included in the store because succeds without problems.
Change:
Whether not to index bind mounts ''; }; }; config = mkIf cfg.enable {

Discussion:
It seems that has no effect, even when using . the following to and : to rebuild locatedb (assuming you have the nixpkgs repo somewher) Expected: Files in directories are pruned. Actual: Files in directories are present in the result. I was able to work around the issue by using instead of using ; that seems to work as expected. From brief experiments running directly, it seems that the env var doesn't do anything (contrary to the documentation), so this may be an upstream bug. System: 17.03.1820. (Gorilla) Nix version: nix-env (Nix) 1.11.14 Nixpkgs version: "17.03.1820." Sandboxing enabled: false
Change:
<ins> { lib, stdenv, buildGraalvmNativeImage, babashka, fetchurl, fetchFromGitHub, clojure, writeScript, testers, clojure-lsp, }: buildGraalvmNativeImage rec { pname = "clojure-lsp"; version = "2024.04.22-11.50.26"; src = fetchFromGitHub { owner = "clojure-lsp"; repo = "clojure-lsp"; rev = version; hash = "sha256-GyPIFYR+/BZ+vq6+yuer5HoVILXLWNw1sW8XpJ7q4SA="; }; jar = fetchurl { url = "https://github.com/clojure-lsp/clojure-lsp/releases/download/${version}/clojure-lsp-standalone.jar"; hash = "sha256-dB16225A7L3nWplvqlal+5gho+LmqqVGPN9dfasKaPk="; }; extraNativeImageBuildArgs = [ # These build args mirror the build.clj upstream # ref: https://github.com/clojure-lsp/clojure-lsp/blob/2024.04.22-11.50.26/cli/build.clj#L141-L144 "--no-fallback" "--native-image-info" "--features=clj_easy.graal_build_time.InitClojureClasses" ]; doCheck = true; checkPhase = '' runHook preCheck export HOME="$(mktemp -d)" ./clojure-lsp --version | fgrep -q '${version}' '' # TODO: fix classpath issue per https://github.com/NixOS/nixpkgs/pull/153770 #${babashka}/bin/bb integration-test ./clojure-lsp + '' runHook postCheck ''; passthru.tests.version = testers.testVersion { inherit version; package = clojure-lsp; command = "clojure-lsp --version"; }; passthru.updateScript = writeScript "update-clojure-lsp" '' #!/usr/bin/env nix-shell #!nix-shell -i bash -p curl common-updater-scripts gnused jq nix set -eu -o pipefail latest_version=$(curl -s https://api.github.com/repos/clojure-lsp/clojure-lsp/releases/latest | jq --raw-output .tag_name) old_jar_hash=$(nix-instantiate --eval --strict -A "clojure-lsp.jar.drvAttrs.outputHash" | tr -d '"' | sed -re 's|[+]|&|g') curl -o clojure-lsp-standalone.jar -sL https://github.com/clojure-lsp/clojure-lsp/releases/download/$latest_version/clojure-lsp-standalone.jar new_jar_hash=$(nix-hash --flat --type sha256 clojure-lsp-standalone.jar | sed -re 's|[+]|&|g') rm -f clojure-lsp-standalone.jar nixFile=$(nix-instantiate --eval --strict -A "clojure-lsp.meta.position" | sed -re 's/^"(.*):[0-9]+"$/1/') sed -i "$nixFile" -re "s|"$old_jar_hash"|"$new_jar_hash"|" update-source-version clojure-lsp "$latest_version" ''; meta = { description = "Language Server Protocol (LSP) for Clojure"; homepage = "https://github.com/clojure-lsp/clojure-lsp"; changelog = "https://github.com/clojure-lsp/clojure-lsp/releases/tag/${version}"; sourceProvenance = [ lib.sourceTypes.binaryBytecode ]; license = lib.licenses.mit; maintainers = [ lib.maintainers.ericdallo ]; }; } </ins>

Discussion:
Hi folks, I saw that clojure-lsp was out of date I tried to build the new version (2024.04.22-11.50.26) Unfortunately after bumping the version and fixing the hashes, we have a build error. Specifically the version check that was recently is failing. Steps to reproduce the behavior: clojure-lsp with version (see ) Full build log: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
codeblocks = callPackage ../applications/editors/codeblocks { }; codeblocksFull = codeblocks.override { contribPlugins = true; }; <ins> cudatext-qt = callPackage ../applications/editors/cudatext { widgetset = "qt5"; }; cudatext-gtk = callPackage ../applications/editors/cudatext { widgetset = "gtk2"; }; cudatext = cudatext-qt; </ins> convos = callPackage ../applications/networking/irc/convos { }; comical = callPackage ../applications/graphics/comical { };

Discussion:
Cross-platform text editor, written in Lazarus From: Repository: Mirror: Development seems very active (last commit 15 minutes ago). Might be a nice open source alternative to SublimeText.
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 .
Still important to me.