jiebi/CodeConvo huggingface dataset:
Change:
{ lib, stdenv, fetchurl, autoreconfHook <del> , mailutils, inetutils </del> <ins> , mailutils, enableMail ? true , inetutils </ins> , IOKit, ApplicationServices }: let

Discussion:
Describe the bug On a ZFS-enabled 20.03 system: IMHO zed does not need the ability to send email by default. Also mariadb-connector should have a separate -dev output so that its doesn't end up in the system closure.
cc
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 .
Seems still important: And: And:
Adjusted to milestone 21.03. BTW, If someone wants to backport the fix it shouldn't cause any issues.
Took a stab at this in
Change:
jwm-settings-manager = callPackage ../applications/window-managers/jwm/jwm-settings-manager.nix { }; <del> k3s_1_24 = callPackage ../applications/networking/cluster/k3s/1_24 { }; k3s_1_25 = callPackage ../applications/networking/cluster/k3s/1_25 { }; inherit (callPackage ../applications/networking/cluster/k3s { }) k3s_1_26 k3s_1_27 ; </del> <ins> k3s_1_24 = callPackage ../applications/networking/cluster/k3s/1_24 { buildGoModule = buildGo120Module; }; k3s_1_25 = callPackage ../applications/networking/cluster/k3s/1_25 { buildGoModule = buildGo120Module; }; inherit (callPackage ../applications/networking/cluster/k3s { buildGoModule = buildGo120Module; }) k3s_1_26 k3s_1_27; </ins> k3s = k3s_1_27; k3sup = callPackage ../applications/networking/cluster/k3sup { };

Discussion:
Tried updating to latest nixos-unstable, but k3s service won't start due to bug described here (): According to the issue golang 1.20 should be used for building. Steps to reproduce the behavior: to latest nixos-unstable k3s service enabled won't start k3s is starting without errors I downgraded to k3s125 for the time being, this version seems unaffected by the bug, 1.26 and 1.27 both seem to not work properly <!-- 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.
Thanks for the clear report, and digging up the upstream issue! Appreciated! I put up a PR to fix this: Since the tests pass there, that seems like a good sign the service starts up after that fix
Thank you for the quick fix, I tried to build your branch on my kind of weak Linux server, but I think it ran out of memory, so I can't test it right now unfortunately. Are there any tests in place for the module that check if it can start correctly? Maybe implementing something like that could save time in the future
There are such tests, yup. On current nixpkgs master: In , only package builds were tested, not individual packages. I think it just impacted so many packages total it wasn't practical to run all the package's tests.
Ah, that makes a lot of sense, my next question would have been why it didn't show up as failing earlier Thanks for the explanation! Did you have a chance to test it with the service? If not, I can boot up my slightly beefier NAS and see if it works there.
The k3s tests in the PR pass, which means the service starts and a pod runs! The tests cover enough that I'm fine trusting them for this fix. I appreciate the offer though!
Change:
}; passthru.tests = { <del> inherit (nixosTests) freshrss-sqlite freshrss-pgsql freshrss-http-auth; </del> <ins> inherit (nixosTests) freshrss-sqlite freshrss-pgsql freshrss-http-auth freshrss-none-auth; </ins> }; buildInputs = [ php ];

Discussion:
Unable to use freshrss. It returns the error . Try http://localhost, be redirected to http://localhost/i/?rid=, see the error It should run without errors. thank you all for maintaining this module Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I think this issue is happening because the default user isn't being created by the 'freshrss-config' service when authType none is specified. I'll work on a PR to fix this shortly. In the meanwhile, I think a workaround would be to start freshrss with authType form configured once, to initialize the default user, then switching to authType none afterwards.
Change:
, fetchFromGitHub , python , cmake <ins> , ninja </ins> }: let <del> pyEnv = python.withPackages (ps: [ ps.setuptools ]); </del> <ins> pyEnv = python.withPackages (ps: [ ps.setuptools ps.tomli ps.pip ps.setuptools ]); </ins> in stdenv.mkDerivation rec { pname = "lief"; <del> version = "0.12.3"; </del> <ins> version = "0.13.2"; </ins> src = fetchFromGitHub { owner = "lief-project"; repo = "LIEF"; rev = version; <del> sha256 = "sha256-wZgv4AFc7DrMCyxMLKQxO1mUTDAU4klK8aZAySqGJoY="; </del> <ins> sha256 = "sha256-lH4SqwPB2Jp/wUI2Cll67PQbHbwMqpNuLy/ei8roiHg="; </ins> }; outputs = [ "out" "py" ]; nativeBuildInputs = [ cmake <ins> ninja </ins> ]; # Not a propagatedBuildInput because only the $py output needs it; $out is

Discussion:
Steps to reproduce the behavior: Might be worth updating to 0.13.2 as well system: host os: multi-user?: sandbox: version: channels(root): channels(mia): nixpkgs:
Change:
configureFlags = [ "--enable-xmlwriter" ]; <del> patches = lib.optionals (lib.versions.majorMinor php.version == "8.2" && lib.versionOlder php.version "8.2.22") [ </del> <ins> patches = lib.optionals (lib.versions.majorMinor php.version == "8.1") [ # Fix tests with libxml2 2.12 (fetchpatch { url = "https://github.com/php/php-src/commit/061058a9b1bbd90d27d97d79aebcf2b5029767b0.patch"; hash = "sha256-0hOlAG+pOYp/gUU0MUMZvzWpgr0ncJi5GB8IeNxxyEU="; excludes = [ "NEWS" ]; }) # Backport of PHP_LIBXML_IGNORE_DEPRECATIONS_START and PHP_LIBXML_IGNORE_DEPRECATIONS_END # Required for libxml2 2.13 compatibility patch. ../development/interpreters/php/php81-fix-libxml2-2.13-compatibility.patch # Fix build with libxml2 2.13+. Has to be applied after libxml2 2.12 patch. (fetchpatch { url = "https://github.com/php/php-src/commit/9b4f6b09d58a4e54ee60443bf9a8b166852c03e0.patch"; hash = "sha256-YC3I0BQi3o3+VmRu/UqpqPpaSC+ekPqzbORTHftbPvY="; }) ] ++ lib.optionals (lib.versions.majorMinor php.version == "8.2" && lib.versionOlder php.version "8.2.22") [ </ins> # Fixes compatibility with libxml2 2.13. Part of 8.3.10RC1+, 8.2.22RC1+ (fetchpatch { url = "https://github.com/php/php-src/commit/4fe821311cafb18ca8bdf20b9d796c48a13ba552.diff?full_index=1";

Discussion:
Steps to reproduce the behavior: php-simplexml-8.1.2 This happen after latest flake update Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hydra build : and seem fine: Probably related: (fixes for 8.2 and 8.3 with same error) 1 is out of active support, so there was no backport for from upstream PS you did not ping any maintainers for that package, so they would need to notice this issue (which is unlikely)
Also causes an lsp-plugins build failure. Gonna ping maintainers.
this is fixed in master
forgive my ignorance, but what needs to happen for the fix on master to make its way to the unstable channel? I would love to be able to rebuild my system soon
fixed "lsp-plugins build failure" (it does not depend on php 8.1 version now) If your system update depends on in some other way it won't help. does not build on current master as of (2024-07-30T19:50:23Z)
Well if you only need to rebuild your system again and you don't necessarily care about the updates you're missing out on, you can try using a previous version of your file
Change:
<ins> From 94d8a9efe6ec86a6e5b4806dbfb82ac926286456 Mon Sep 17 00:00:00 2001 From: Yureka <yuka@yuka.dev> Date: Sun, 30 Jun 2024 09:45:58 +0200 Subject: [PATCH] Fix build with _PY_SHORT_FLOAT_REPR == 0 --- Include/internal/pycore_dtoa.h | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/Include/internal/pycore_dtoa.h b/Include/internal/pycore_dtoa.h index c5cfdf4ce8..e4222c5267 100644 --- a/Include/internal/pycore_dtoa.h +++ b/Include/internal/pycore_dtoa.h @@ -11,8 +11,6 @@ extern "C" { #include "pycore_pymath.h"        // _PY_SHORT_FLOAT_REPR -#if _PY_SHORT_FLOAT_REPR == 1 - typedef uint32_t ULong; struct @@ -22,15 +20,15 @@ Bigint { ULong x[1]; }; -#ifdef Py_USING_MEMORY_DEBUGGER +#if defined(Py_USING_MEMORY_DEBUGGER) || _PY_SHORT_FLOAT_REPR == 0 struct _dtoa_state { int _not_used; }; -#define _dtoa_interp_state_INIT(INTERP)  +#define _dtoa_state_INIT(INTERP)  {0} -#else  // !Py_USING_MEMORY_DEBUGGER +#else  // !Py_USING_MEMORY_DEBUGGER && _PY_SHORT_FLOAT_REPR != 0 /* The size of the Bigint freelist */ #define Bigint_Kmax 7 @@ -66,8 +64,6 @@ extern char* _Py_dg_dtoa(double d, int mode, int ndigits, int *decpt, int *sign, char **rve); extern void _Py_dg_freedtoa(char *s); -#endif // _PY_SHORT_FLOAT_REPR == 1 - extern PyStatus _PyDtoa_Init(PyInterpreterState *interp); extern void _PyDtoa_Fini(PyInterpreterState *interp); -- 2.45.1 </ins>

Discussion:
() regressed cross compilation for python3. Steps to reproduce the behavior: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
preparing a PR.
Change:
-      [main] -      no-auto-default=* -    ''' <del> +    extraConfig.main.no-auto-default = "*"; </del> <ins> +    settings.main.no-auto-default = "*"; </ins> }; ``` ''

Discussion:
In file : patch networking.networkmanager = { extraConfig = = "*"; ... The code suggests option has been removed. However, in given example, it's still using . This leads to a confusion. Change it to . <!-- make sure this issue is not redundant or obsolete --- [ ] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [ ] checked [open documentation issues] for possible duplicates [ ] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]:
Change:
shortuuid ]; <del> preCheck = '' export HOME=$(mktemp -d) ''; </del> checkInputs = [ azure-core bokeh

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags: -
fixed in
Change:
stdenv.mkDerivation (finalAttrs: { pname = "juce"; <del> version = "7.0.10"; </del> <ins> version = "7.0.11"; </ins> src = fetchFromGitHub { owner = "juce-framework"; repo = "juce"; rev = finalAttrs.version; <del> hash = "sha256-CAHhHPTUvIyDOh2CdvNmw26HfoWWtbqRRiR+3Ky4GYA="; </del> <ins> hash = "sha256-XFC+MYxUE3NatM2oYykiPJtiQLy33JD64VZFfZS2Tas="; </ins> }; patches = [

Discussion:
Package name: jusce Latest released version: 7.0.11 Current version on the unstable channel: 7.0.10 Current version on the stable/release channel: 7.0.7 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:
rst2ansi = callPackage ../development/python-modules/rst2ansi { }; <ins> rst2pdf = callPackage ../development/python-modules/rst2pdf { }; </ins> rstcheck = callPackage ../development/python-modules/rstcheck { }; rstcheck-core = callPackage ../development/python-modules/rstcheck-core { };

Discussion:
rst2pdf The usual way of creating PDF from reStructuredText is by going through LaTeX. This tool provides an alternative by producing PDF directly using the ReportLab library. Metadata homepage URL: source URL: license: MIT platforms: unix, linux, darwin, ...
I want to package this - will try to do it in a few hours.
Change:
etlegacy = callPackage ../games/etlegacy { lua = lua5_4; }; <ins> fastfetch = darwin.apple_sdk_11_0.callPackage ../tools/misc/fastfetch { inherit (darwin.apple_sdk_11_0.frameworks) AppKit Cocoa CoreDisplay CoreVideo CoreWLAN DisplayServices Foundation IOBluetooth MediaRemote OpenCL; inherit (darwin) moltenvk; }; </ins> fscan = callPackage ../tools/security/fscan { }; copier = callPackage ../tools/misc/copier { };

Discussion:
Project description fastfetch is a [neofetch] like tool for fetching system information and displaying them in a pretty way. It is written in c to achieve much better performance, Metadata source URL: license: mit, bsd, gpl2+ ,: mit platforms: unix, linux, darwin, : linux
Please review and check if it works.
Change:
in stdenv.mkDerivation rec { pname = "amdvlk"; <del> version = "2022.Q2.3"; </del> <ins> version = "2022.Q2.2"; </ins> src = fetchRepoProject { name = "${pname}-src"; manifest = "https://github.com/GPUOpen-Drivers/AMDVLK.git"; rev = "refs/tags/v-${version}"; <del> sha256 = "Yd2juNdSP8TdSX9j/iXsC2xrIRzDEuXJbms91AqwjEc="; </del> <ins> sha256 = "4LV6g2snT1usY+Ic9Hb/IwXAJQ97I9DigZCah6mwewA="; </ins> }; buildInputs = [

Discussion:
Every Vulkan application (even from nixpkgs) simply doesn't work. For example: wine (DXVK): dolphin-emu-beta: Running returns absolutely nothing: I have to manually CTRL+C to interrupt it. works for some reason... Steps to reproduce the behavior: an AMD GPU (I guess) and be on nixos-unstable; ; a Vulkan application (except ). You can try . doesn't work! It should work. Latest build (that I tried) where I don't reproduce the problem is from June 24. The first (that I tried) where I do reproduce the problem is from June 27. I tried wiping (because maybe there was some rogue configuration file doing something?) to no avail. My GPU is an integrated Vega 6 (from a Ryzen 4500U). Tested both RADV and AMDVLK (both don't work).
I bisected the cause: . I have no idea why it does it with RADV, though it may be because I have both installed and using . (I'll test with RADV only now)
And without , Vulkan works even after that commit. Seems to be caused by
Change:
# fails to configure on darwin due to gmp not found configureFlags = [ "LIBS=-L${gmp}/lib" "CXXFLAGS=-I${gmp.dev}/include" ]; <del> # disable stackprotector on aarch64-darwin for now # https://github.com/NixOS/nixpkgs/issues/127608 hardeningDisable = lib.optionals (stdenv.isAarch64 && stdenv.isDarwin) [ "stackprotector" ]; </del> postPatch = '' sed -e "s@ /bin/bash@bash@g" -i Makefile.std find . -exec sed -e "s@/usr/bin/perl@${perl}/bin/perl@g" -i '{}' ';'

Discussion:
Describe the bug I'm on a mission to get (and thence ) compiling on M1 Macs, and having fixed , the next stumbling block is 4.1.1. Sadly, the build fails with , presumably related to . To Reproduce Steps to reproduce the behavior: Expected behavior A clear and concise description of what you expected to happen. Screenshots Additional context This works fine when built for x8664 on the same machine. 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 system: host os: multi-user?: sandbox: version: channels(steve): nixpkgs: Maintainer information:
Submitted PR which disables Fortran support for OpenMPI on aarch64-darwin. Would that fix the issue for you or do you require Fortran?
This seems to be the build failure:
I actually have no idea if I require Fortran. I mean, presumably it's enabled for some reason, so I'm a little wary of disabling it on only one platform/arch combination: that feels like an atypical workaround.
To reproduce: I wonder if the gcc maintainers can offer any insight?
seems to hint at the stack-protector hardening, so perhaps something like could work around that? (no idea what's the real cause though, and I have no Darwin machine at hand)
You were right! Sent a PR in
Change:
<ins> { lib, appimageTools, fetchurl }: let version = "2.12.0"; pname = "wowup-cf"; name = "${pname}-${version}"; src = fetchurl { url = "https://github.com/WowUp/WowUp.CF/releases/download/v${version}/WowUp-CF-${version}.AppImage"; hash = "sha256-uWz/EQBX/d1UBfpc9EL4x+UH72kINd6pqFIvJkV16e8="; }; appimageContents = appimageTools.extractType1 { inherit name src; }; in appimageTools.wrapType1 { inherit name src; extraInstallCommands = '' mv $out/bin/${name} $out/bin/${pname} install -m 444 -D ${appimageContents}/${pname}.desktop -t $out/share/applications substituteInPlace $out/share/applications/${pname}.desktop  --replace 'Exec=AppRun' 'Exec=${pname}' cp -r ${appimageContents}/usr/share/icons $out/share ''; meta = with lib; { description = "World of Warcraft addon updater with CurseForge support"; longDescription = '' WowUp is the community centered World of Warcraft addon updater. We attempt to bring the addon community together in an easy to use updater application. We have an ever growing list of supported features. ''; homepage = "https://wowup.io/"; downloadPage = "https://github.com/WowUp/WowUp.CF/releases"; license = licenses.unfree; sourceProvenance = with sourceTypes; [ binaryNativeCode ]; maintainers = with maintainers; [ pbek ]; platforms = [ "x86_64-linux" ]; }; } </ins>

Discussion:
Project description Open source addon manager for world of warcraft Metadata homepage URL: source license: GPL V3 platforms: unix, linux, darwin, Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
in case you want to test: (only for Linux).
Change:
vulkan-headers wayland ] ++ lib.optionals cudaSupport ( <del> with cudaPackages; [ cuda_cccl cuda_cudart libcublas ]); </del> <ins> with cudaPackages; [ cuda_cccl cuda_cudart libcublas ] ); </ins> cmakeFlags = [ "-DKOMPUTE_OPT_USE_BUILT_IN_VULKAN_HEADER=OFF"

Discussion:
Greetings. I'm trying to run gpt4all in cuda acceleration, but there is no option for CUDA acceleration in app. Launching from terminal give me this error:failed to initialize CUDA: CUDA driver is a stub library Steps to reproduce the behavior: gpt4all-cuda -Applictiation-Device device section, there is only CPU and Auto Cuda device should be detectable. Exporting resolve this issue and gpt4all detect cuda device. <!-- 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]:
I'm sorry I won't be able to help since I don't particularly use it anymore and I don't have any NVidia devices.
Understandable. Maybe can take are look here then, because not only this app affected by this bug as far as i can see.
Small overlay wrapper in case anyone have this issue also: Probably something similar required for amd card.
Hi thanks for reporting the issue and finding the fix. Could you please submit a PR? Instead of using the wrapper you can add to the package's (best in the part of the list conditioned on ). That's the nice thing about ROCm: nothing of the sort is required; you can just link the driver directly, no need to play hide-n-seek with nvidia. However I don't see any references in the gpt4all expression or in the upstream repo, I'm not sure they support ROCm. One could still use the cuda version with amd devices, via in
same issue, but with AMD card. About sumbiting a PR. I don't feel confident enough in nixos to do such thing for now.
Do as you feel is best for you, but do know that we'd guide you and that the entry threshold is meant to be kept low
the PR that adds if is enabled in if you could take a look at it pls.
Change:
existing process, but will need to start that process from gdb (so it is a child). Or you can set `boot.kernel.sysctl."kernel.yama.ptrace_scope"` to 0. <ins> - Gitea 1.21 upgrade has several breaking changes, including: - Custom themes and other assets that were previously stored in `custom/public/*` now belong in `custom/public/assets/*` - New instances of Gitea using MySQL now ignore the `[database].CHARSET` config option and always use the `utf8mb4` charset, existing instances should migrate via the `gitea doctor convert` CLI command. </ins> - The `hardware.pulseaudio` module now sets permission of pulse user home directory to 755 when running in "systemWide" mode. It fixes [issue 114399](https://github.com/NixOS/nixpkgs/issues/114399).

Discussion:
Package name: gitea Latest released version: 1.21.1 () <!-- Search your package here: --- Current version on the unstable channel: 1.20.5 Current version on the stable/release channel: 1.19.4 <!-- 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.
thanks. I've created:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
{ lib, stdenv , fetchurl <ins> , fetchpatch </ins> , pkg-config , desktop-file-utils , SDL

Discussion:
sfxr and sfxr-qt segfault when the gui is run. Please run and paste the result.
Nevermind, it looks like they work in a nixos test... it must have to do with my system
FYI I ran into this recently after bumping as well. Must be some sort of Qt caching? I'm not too familiar with Qt.
Can confirm, deleting fixed it for me too
still segfaults for me. I tried to debug it with with , but when I ran it that way, it just hangs:
Bump On my machine (NixOS 23.11) runs, possibly with a broken theme but I'm not sure. Mine doesn't look like the picture in the at least: ! still simply Segfaults.
Looks like (thanks!). I'll apply that patch tomorrow. please open another issue for the sfxr-qt theming issue
Change:
stdenv.mkDerivation rec { pname = "harfbuzz${lib.optionalString withIcu "-icu"}"; <del> version = "5.3.1"; </del> <ins> version = "6.0.0"; </ins> src = fetchurl { url = "https://github.com/harfbuzz/harfbuzz/releases/download/${version}/harfbuzz-${version}.tar.xz"; <del> sha256 = "sha256-Smzgl7dagSH6zEuoO1sIO/7GV/RbADzVo0JPKua0Q00="; </del> <ins> sha256 = "HRAQoXUdB21SkeQzwThQKnlNZ5p0mNEmjuIeLUoUDrQ="; </ins> }; <del> patches = [ # Pick upstream patch for exported symbol test failing on darwin # https://github.com/harfbuzz/harfbuzz/issues/3850 (fetchpatch { name = "harfbuzz-fix-check-symbol-tests-lto-and-darwin.patch"; url = "https://github.com/harfbuzz/harfbuzz/commit/b0b7a65388da25ae3fa01e969ad6abc67eed4f49.patch"; sha256 = "0my064r88pikw6q70hbgf6hwfkw544b9f5ai73qhn2a3c83jqn06"; }) ]; </del> postPatch = '' patchShebangs src/*.py test '' + lib.optionalString stdenv.isDarwin ''

Discussion:
Trying to use harfbuzz in a CMake project, CMake fails with the following: That path comes from /nix/store/7ahz2g1i3m2pfk96fjl6j37ldcwlxpbg-harfbuzz-3.3.2-dev/lib/cmake/harfbuzz/harfbuzz-, probably on line 25 which says . Steps to reproduce the behavior: a CMake project that tries to link an executable to harfbuzz: to configure project () error above The project configures successfully. <!-- 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.
I think I found a potential clean solution, this patch applies to harfbuzz. Meson has a path join operator, which I made it use instead of the plain string concat operation: Going to see if I can upstream it. (the same change for libdir just for consistency, it isn't technically needed) EDIT: Nope, this doesn't work yet. There must be something similar going on somewhere else still.
While the last one didn't work, this one does but it's nowhere as clean. Oh well.
Fixed in harfbuzz 6.0.0.