jiebi/CodeConvo huggingface dataset:
Code change:
fastjar = callPackage ../development/tools/java/fastjar { }; <del> jextract = callPackage ../development/tools/java/jextract { }; </del> httpunit = callPackage ../development/libraries/java/httpunit { }; javaCup = callPackage ../development/libraries/java/cup {

Related discussion:
text: And now that Panama/FF&M is final, I'm hoping it will be possible to use jextract 22 to build headers for JDK 23+. Newer versions of jextract might offer improvements, but headers generated for JDK 22 should work wth JDK 23+ (I don't know what guarantees the JDK makes for that, but this seems a reasonable conclusion given a stable API.)
Nice to hear that, and thanks for your work! IMO, I think it's worth. The point is that JDK 21 is a LTS version, some downstreams prefer to use a LTS version of JDK to develop their projects. For them, if we don't keep JDK 21's , this will be unavailable to them unless they give up on choosing LTS and do some extra effort - porting their project to a newer version of JDK.
I agree. But I also strongly encourage new projects to start with JDK 22 and existing projects to migrate as quickly as possible. Having to make sure "preview mode" is set in the compiler and at runtime can cause various problems with tools and the output of the latest is significantly improved. In general, it's much better to be using a non-LTS JDK with a non-preview feature than and LTS JDK with a preview feature. I migrated my project recently and wish I had migrated to JDK 22 much earlier.
PR has been merged. I gave it a quick test on macOS/aarch64 and it seems to be working. (I used it to build which uses JDK 22 and Panama via Gradle's Java toolchains)
Code change:
buildPythonApplication rec { pname = "pmbootstrap"; <del> version = "1.45.0"; </del> <ins> version = "1.50.0"; </ins> src = fetchPypi { inherit pname version; <del> sha256 = "sha256-75ZFzhRsczkwhiUl1upKjSvmqN0RkXaM8cKr4zLgi4w="; </del> <ins> hash = "sha256-UtXUq+B3EMHS3CTqfzbyQK0gHgrFwcwQ6zTzw/EwIuA="; </ins> }; repo = fetchFromGitLab {

Related discussion:
text: <!-- 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: pmbootstrap <!-- 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.45.0 desired version: 1.49.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.
Code change:
buildGoModule rec { pname = "teleport"; <del> version = "6.1.2"; </del> <ins> version = "6.1.3"; </ins> # This repo has a private submodule "e" which fetchgit cannot handle without failing. src = fetchFromGitHub { owner = "gravitational"; repo = "teleport"; rev = "v${version}"; <del> sha256 = "sha256-4ZaebTTgGrGRQbMfDw1PL/qtDKmHbSY6kPmWyFeIcAU="; </del> <ins> sha256 = "sha256-kb7qRPZKXDY0Qy3/72epAGaN2FCOO/XAN8lOoUYkoM0="; </ins> }; vendorSha256 = null;

Related discussion:
text: Describe the bug In order to be able to invoke the command from teleport is using  call. There is a wrapper around to bring into PATH . That means is invoked from without wrapper and the browser page never opens (due to missing ). To Reproduce Steps to reproduce the behavior: Expected behavior The path to the wrapper must be persisted in the Screenshots If applicable, add screenshots to help explain your problem. Additional context 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 Please run and paste the result. Maintainer information:
Code change:
nativeBuildInputs = [ meson ninja python3 <del> pkgconfig gettext makeWrapper </del> <ins> pkgconfig gettext wrapGAppsHook </ins> libxml2 libxslt docbook_xsl docbook_xml_dtd_42 ];

Related discussion:
text: Inkscape has support for openclipart but it doesn't work in the package provided by nixpkgs. inkscape to File -Import Clip Art... a search term and click the Search button. the in the GUI and in the terminal. NixOS 18.09 and nixpkgs master.
I researched a bit and thought adding glib-networking would fix it. I wrote the following patch, but it doesn't seem to have any effect:
I wonder whether it really is because TLS support is unavailable, or because uses an invalid security certificate?
Good point. Hm, that's weird. I followed that URL () a day or two ago (when I first noticed this) and was redirected to https:// without problems. But now I see the certificate warning in firefox.
I think it may be a packaging bug after all. Look at this grep: The message only appears in the glib tree, in the gdummytlsbackend.c file. No matches from glib-networking, which AFAIK, provides TLS support.
I tried the patch and am getting Probably because the site is down.
is not down for me.
Thank you!
Code change:
buildInputs = [ eigen boost glew opencsg cgal mpfr gmp glib harfbuzz lib3mf libzip double-conversion freetype fontconfig <del> qtbase qtmultimedia qscintilla </del> <ins> qtbase qtmultimedia qscintilla cairo </ins> ] ++ lib.optionals stdenv.isLinux [ libGLU libGL wayland wayland-protocols qtwayland ] ++ lib.optional stdenv.isDarwin qtmacextras ++ lib.optional spacenavSupport libspnav

Related discussion:
text: OpenSCAD seems to be built without support for PDF exports. (This is a very useful feature to print projections on paper to check the dimensions of a design for example). Version: OpenSCAD version 2021.01 On nixpkgs: master (2022-09-18) Open OpenSCAD Go to File -Export -Export as PDF… Save to some file Observe the following error in the OpenSCAD console: CC package maintainers:
Any idea what dependency they need for PDF? (image file export has been enough for me so I never looked)
I think cairo. (I was looking into this earlier today.)
Yes, cairo was missing:
Code change:
, fetchFromGitHub , setuptools_scm , vdf <ins> , bash </ins> , steam-run , winetricks , zenity

Related discussion:
text: This issue is mainly a note to myself since the upgrade won't be trivial and will need a lot of testing. Protontricks is now using the Pressure Vessel runtime, so I have to refactor my patches with steam-run to account for this. <!-- 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: protontricks <!-- 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.4.4 desired version: 1.5.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: myself
Code change:
<del> { python_openzwave, fetchPypi }: </del> <ins> { python_openzwave, fetchPypi, openzwave, fetchFromGitHub }: </ins> <del> python_openzwave.overridePythonAttrs (oldAttrs: rec { </del> <ins> (python_openzwave.override { openzwave = openzwave.overrideAttrs (oldAttrs: { version = "unstable-2020-03-24"; src = fetchFromGitHub { owner = "home-assistant"; repo = "open-zwave"; rev = "94267fa298c1882f0dc73c0fd08f1f755ba83e83"; sha256 = "0p2869fwidz1wcqzfm52cwm9ab96pmwkna3d4yvvh21nh09cvmwk"; }; patches = [ ]; }); }).overridePythonAttrs (oldAttrs: rec { </ins> pname = "homeassistant_pyozw"; version = "0.1.10";

Related discussion:
text: Hi, i need to use open-zwave as a dependency for a build, but the version built in the Nix package is a specific fork for supporting home-assistant, which does not work for my package build due to linking errors. I will happily contribute a new package, but I'm not sure how to proceed, with regards to how it would fit in with this package, or if indeed the best way would be to modify this package to use the upstream repo. Pinging people who have maintained the package, apologies for the noise!
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
We should replace the package with an official version and make use the fork.
Code change:
, mkDerivation , variant ? "standalone" , fetchFromGitHub <del> , fetchpatch </del> , cmake , pkg-config , ninja

Related discussion:
text: Steps to reproduce the behavior: gmic in a nix shell using the unstable channel Add any other context about the problem here.
Will be fixed by
Thanks! Note that it makes darktable fail to build.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Code change:
, libxml2 , libzip , ncurses <ins> , xlsSupport ? false </ins> }: stdenv.mkDerivation rec {

Related discussion:
text: libxls, one of the optional dependencies for sc-im has 6 open CVEs for arbitrary code execution, which were reported on github 5 months ago and the issue hasn't even been responded to. I think this dependency should be made optional and probably should not be included by default. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
## Files in versions/ are generated automatically by update.sh ## dotnet_3_1 = import ./versions/3.1.nix (buildAttrs // { icu = icu70; }); <del> dotnet_5_0 = import ./versions/5.0.nix (buildAttrs // { inherit icu; }); </del> dotnet_6_0 = import ./versions/6.0.nix (buildAttrs // { inherit icu; }); dotnet_7_0 = import ./versions/7.0.nix (buildAttrs // { inherit icu; }); in

Related discussion:
text: Since May 10, .NET 5.0 is EOL (End Of Life), and should not be used. Should it be marked as EOF similar to dotnet 2.2 and 3.0? See All packages using dotnet 5.0 should be updated to use a newer, supported version. These packages still need updating: [x] - [x] - [x] - [x] pkgs/development/tools/build- - [x] -
There is at least one package, which currently uses dotnet 5 sdk - . So we will need to update it beforehand. Btw, I'm not sure if we have any policy regarding packages removal, for nixpkgs in general or specifically for it's dotnet part. , what do you think?
The package is also using .NET 5: . But this is because I made the PR upstream updating it from .NET 4 to 5. I suspect that the transition to 6 will be similarly easy.
I think we should just mark it as depricated, as many projects do still use it upstream. Dotnet version 3 is also still commonly used, so I dont expect it would be realistic to remove version 5 any time soon. also uses dotnet 5 by default, I'll go ahead and switch that over now. See . That doesnt mark dotnet 5 as deprecated or change anything from a SDK perspective, just some preperation work.
See as well, it adds a warning whenever dotnet version 5 is used. Not using a throw for now since a few packages depend on it and I dont have the time to clean that all up at the moment.
Can you provide a list of packages that need updating?
Based on a quick grep: pkgs/development/tools/build-
I believe that after all the above PRs are merged, we should be able to safely remove .NET 5 from nixpkgs :)
Code change:
<!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. --> <ins> - [ownCloud Infinite Scale Stack](https://owncloud.com/infinite-scale-4-0/), a modern and scalable rewrite of ownCloud. </ins> - [Handheld Daemon](https://github.com/hhd-dev/hhd), support for gaming handhelds like the Legion Go, ROG Ally, and GPD Win. Available as [services.handheld-daemon](#opt-services.handheld-daemon.enable). - [Guix](https://guix.gnu.org), a functional package manager inspired by Nix. Available as [services.guix](#opt-services.guix.enable).

Related discussion:
text: "ownCloud Infinite Scale Stack" or owncloud rewritten in Go. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: asl20 platforms: unix
There are some hassles to deal with on this one. PNPM usage: Image assets downloaded with curl (and no hashes or revisions) Code generation tools and code repositories downloaded by
Note that ownCloud provide prebuilt binaries for oCIS. It's fairly simple to get these working on NixOS: Perhaps this can be used as a temporary solution until we can build it ourselves?
I used your derivation and opened . I tested it a bit, and will work on a proper module over next few days/weeks, can you share if you are already using above derivation, and if yes, how stable are rc releases?
I've been using the rc for a while and haven't had any major issues. It's probably better to go with the stable release by default though. Perhaps we could package both?
Has the situation changed where the OCIS can be built from source now? I'd rather not use a proprietary binary.
Code change:
let cfg = config.power.ups; <del> in </del> <ins> defaultPort = 3493; nutFormat = { type = with lib.types; let singleAtom = nullOr (oneOf [ bool int float str ]) // { description = "atom (null, bool, int, float or string)"; }; in attrsOf (oneOf [ singleAtom (listOf (nonEmptyListOf singleAtom)) ]); generate = name: value: let normalizedValue = lib.mapAttrs (key: val: if lib.isList val then forEach val (elem: if lib.isList elem then elem else [elem]) else if val == null then [] else [[val]] ) value; mkValueString = concatMapStringsSep " " (v: let str = generators.mkValueStringDefault {} v; in # Quote the value if it has spaces and isn't already quoted. if (hasInfix " " str) && !(hasPrefix """ str && hasSuffix """ str) then ""${str}"" else str ); in pkgs.writeText name (lib.generators.toKeyValue { mkKeyValue = generators.mkKeyValueDefault { inherit mkValueString; } " "; listsAsDuplicateKeys = true; } normalizedValue); }; installSecrets = source: target: secrets: pkgs.writeShellScript "installSecrets.sh" '' install -m0600 -D ${source} "${target}" ${concatLines (forEach secrets (name: '' ${pkgs.replace-secret}/bin/replace-secret  '@${name}@'  "$CREDENTIALS_DIRECTORY/${name}"  "${target}" ''))} chmod u-w "${target}" ''; upsmonConf = nutFormat.generate "upsmon.conf" cfg.upsmon.settings; upsdUsers = pkgs.writeText "upsd.users" (let # This looks like INI, but it's not quite because the # 'upsmon' option lacks a '='. See: man upsd.users userConfig = name: user: concatStringsSep "n      " (concatLists [ [ "[${name}]" "password = "@upsdusers_password_${name}@"" ] (optional (user.upsmon != null) "upsmon ${user.upsmon}") (forEach user.actions (action: "actions = ${action}")) (forEach user.instcmds (instcmd: "instcmds = ${instcmd}")) ]); in concatStringsSep "nn" (mapAttrsToList userConfig cfg.users)); </ins> <del> let </del> upsOptions = {name, config, ...}: { options = {

Related discussion:
text: Describe the bug I'm trying to use NixOS in a UPS client (not server). When , the and services shouldn't be running. There is a note that says that is not used currently. To Reproduce Steps to reproduce the behavior: Error: and fail. Expected behavior only upsmon should be running 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 Maintainer information: See also
Looks like there's a pretty simple workaround:
I marked this as stale due to inactivity. &rarr;
Code change:
${stdenv.lib.optionalString (buildAndTestSubdir != null) "pushd ${buildAndTestSubdir}"} runHook preCheck echo "Running cargo test ${argstr} -- ''${checkFlags} ''${checkFlagsArray+''${checkFlagsArray[@]}}" <del> cargo test ${argstr} -- ''${checkFlags} ''${checkFlagsArray+"''${checkFlagsArray[@]}"} </del> <ins> cargo test -j $NIX_BUILD_CORES ${argstr} -- --test-threads=$NIX_BUILD_CORES ''${checkFlags} ''${checkFlagsArray+"''${checkFlagsArray[@]}"} </ins> runHook postCheck ${stdenv.lib.optionalString (buildAndTestSubdir != null) "popd"} '');

Related discussion:
text: Describe the bug Building packages that use always try to use all cores, independent of ( argument to nix-build) To Reproduce Run , and observe that it spawns many rustc processes (depending on the amount of available processors). Expected behavior The function should pass as argument to cargo. Additional notes Fixing this will probably cause a rebuild of all rust packages, so should we batch this with other changes to the cargo builder? Notify maintainers
has been merged
Code change:
### E ### <ins> EBTKS = ebtks; # Added 2024-01-21 </ins> ec2_ami_tools = ec2-ami-tools; # Added 2021-10-08 ec2_api_tools = ec2-api-tools; # Added 2021-10-08 ec2-utils = amazon-ec2-utils; # Added 2022-02-01

Related discussion:
text: For x8664-darwin, aarch64-darwin: build .#EBTKS x8664-darwin: aarch64-darwin:
Code change:
buildDotnetModule rec { pname = "ArchiSteamFarm"; # nixpkgs-update: no auto update <del> version = "5.5.0.11"; </del> <ins> version = "5.5.2.3"; </ins> src = fetchFromGitHub { owner = "JustArchiNET"; repo = "ArchiSteamFarm"; rev = version; <del> hash = "sha256-VlJiTCdoH6hlVtQgECIlbsQvg3S58B5IIy1zRxh1eOg="; </del> <ins> hash = "sha256-8MrVeJ4XVU7WdYv0mbwz64hIGglisb6+vUoicl4/WC0="; </ins> }; dotnet-runtime = dotnetCorePackages.aspnetcore_8_0;

Related discussion:
text: Package name: ArchiSteamFarm Latest released version: 5.5.2.3 <!-- Search your package here: --- Current version on the unstable channel: 5.5.0.11 Current version on the stable/release channel: 5.4.12.5 <!-- 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]:
It helps if I also open the PR when doing the update
Code change:
ragnarwm = handleTest ./ragnarwm.nix {}; rasdaemon = handleTest ./rasdaemon.nix {}; readarr = handleTest ./readarr.nix {}; <ins> realm = handleTest ./realm.nix {}; </ins> redis = handleTest ./redis.nix {}; redlib = handleTest ./redlib.nix {}; redmine = handleTest ./redmine.nix {};

Related discussion:
text: Project description A simple, high performance relay server written in rust. Metadata homepage URL: source URL: license: mit platforms: Linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
ln -s $out/opt/teams/teams $out/bin/ ''; <ins> dontAutoPatchelf = true; # Includes runtimeDependencies in the RPATH of the included Node modules # so that dynamic loading works. We cannot use directly runtimeDependencies # here, since the libraries from runtimeDependencies are not propagated # to the dynamically loadable node modules because of a condition in # autoPatchElfHook since *.node modules have Type: DYN (Shared object file) # instead of EXEC or INTERP it expects. # Fixes: https://github.com/NixOS/nixpkgs/issues/85449 postFixup = '' autoPatchelf "$out" runtime_rpath="${lib.makeLibraryPath runtimeDependencies}" for mod in $(find "$out/opt/teams" -name '*.node'); do mod_rpath="$(patchelf --print-rpath "$mod")" echo "Adding runtime dependencies to RPATH of Node module $mod" patchelf --set-rpath "$runtime_rpath:$mod_rpath" "$mod" done; ''; </ins> meta = with stdenv.lib; { description = "Microsoft Teams"; homepage = "https://teams.microsoft.com";

Related discussion:
text: Describe the bug When calling somebody using Microsoft Teams, it seems that the softwares fallback on ALSA plugin, which makes the audio output butchered (hearing noises when someone's talking, but unable to understand what this person is saying). To Reproduce Steps to reproduce the behavior: teams (require an Office 365 accounts) somebody Expected behavior It should use the PulseAudio backend during calls. Additional context I'm using Sway as my window manager (thus, running on wayland). Notify maintainers Microsoft Teams package maintainer: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(ely): nixpkgs:
How can one tell it that it falls back to the ALSA plugin? Apart from the butchered sound that is?
Inside Pavucontrol, you see it uses an "ALSA Plugin" as a backend. It shows ALSA only during a call, on the rest of the software it shows as a standard pulseaudio program output.
Code change:
stdenv.mkDerivation (finalAttrs: { pname = "astro-language-server"; <del> version = "2.10.0"; </del> <ins> version = "2.14.2"; </ins> src = fetchFromGitHub { owner = "withastro"; repo = "language-tools"; rev = "@astrojs/language-server@${finalAttrs.version}"; <del> hash = "sha256-WdeQQaC9AVHT+/pXLzaC6MZ6ddHsFSpxoDPHqWvqmiQ="; </del> <ins> hash = "sha256-4GaLyaRUN9qS2U7eSzASB6fSQY2+fWtgfb54uuHjuh4="; </ins> }; pnpmDeps = pnpm_8.fetchDeps {

Related discussion:
text: Package name: astro-language-server Latest released version: 2.14.2 <!-- Search your package here: --- Current version on the unstable channel: 2.10.0 Current version on the stable/release channel: None <!-- 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]:
I'm on it ^^. I've got a working version. Gonna soon open a PR :+1: