jiebi/CodeConvo huggingface dataset:
Change:
In this was to the list of . As is linux-only this breaks the build for and all of it's dependencies on other platforms such as The package also seems to build without this dependency (at least on ) -- I hope I didn't overlook something here (also sadly can't check right now). Thank you! Steps to reproduce the behavior: or Add any other context about the problem here. <!-- 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]:

Discussion:
buildPythonPackage rec { pname = "langchain-community"; <del> version = "0.0.32"; </del> <ins> version = "0.0.33"; </ins> pyproject = true; disabled = pythonOlder "3.8";

src = fetchPypi { pname = "langchain_community"; inherit version; <del> hash = "sha256-FRAhfWRsg4D1TphQNR9tKgsN1zxQG2Zsb0tAuqgWCyk="; </del> <ins> hash = "sha256-u1bbwe8RygnyWEaOETaHga3akhnhRAc+MM2mlJbTQrI="; </ins> }; build-system = [ poetry-core ];

buildPythonPackage rec { pname = "langchain-core"; <del> version = "0.1.43"; </del> <ins> version = "0.1.44"; </ins> pyproject = true; disabled = pythonOlder "3.8";

src = fetchPypi { pname = "langchain_core"; inherit version; <del> hash = "sha256-SZEz+two7899JDBiNlIVGAgLsQ/Yv290Jt5KK78q67U="; </del> <ins> hash = "sha256-4xOXXZrikmNC5vKtdgM40x8YsSI+m4tNxAja7q3kaoM="; </ins> }; pythonRelaxDeps = [

{ lib, <ins> stdenv, </ins> attr, buildPythonPackage, <ins> fastapi, </ins> fetchFromGitHub, freezegun, <ins> httpx, </ins> orjson, poetry-core, pydantic,

pythonOlder, pythonRelaxDepsHook, requests, <ins> uvicorn, </ins> }: buildPythonPackage rec { pname = "langsmith"; <del> version = "0.1.45"; </del> <ins> version = "0.1.48"; </ins> pyproject = true; disabled = pythonOlder "3.8";

owner = "langchain-ai"; repo = "langsmith-sdk"; rev = "refs/tags/v${version}"; <del> hash = "sha256-8A9wqhM8U5Q8o0uMyu+LQKhV+1Nsyg4opJjwylc6kkI="; </del> <ins> hash = "sha256-n24rlulncJHNyHFqszEbALGfnT7+tTGjLjwR7Fw1smI="; </ins> }; sourceRoot = "${src.name}/python";

]; nativeCheckInputs = [ <del> attr </del> <ins> fastapi </ins> freezegun <ins> httpx </ins> pytest-asyncio pytestCheckHook <ins> uvicorn ] ++ lib.optionals stdenv.isLinux [ attr </ins> ]; disabledTests = [

# due to circular import "tests/integration_tests/test_client.py" "tests/unit_tests/test_client.py" <ins> # Tests require a Langsmith API key "tests/evaluation/test_evaluation.py" </ins> ]; pythonImportsCheck = [ "langsmith" ];
Change:
Incus allow CPU hotplugging, but the cores remain offline in the NixOS VM image. Steps to reproduce the behavior: launch images:nixos/unstable nixos-cpu-hotplug config set nixos-cpu-hotplug 2 shell nixos-cpu-hotplog online state of CPU cores, e.g., using htop or the sysfs Hot plugged CPU cores need to be brought online to become usable. If applicable, add screenshots to help explain your problem. Installing the following rule sets hotplugged CPU online. The question that remains is whether to have the rules downstream or try to bring them upstream. I tested Ubuntu 24.04 for example, and they didn't have udev rules for that as well, so the ecosystem would likely benefit. <!-- 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]:

Discussion:
boot.kernelParams = ["console=tty1" "console=${serialDevice}"]; <ins> services.udev.extraRules = '' SUBSYSTEM=="cpu", CONST{arch}=="x86-64", TEST=="online", ATTR{online}=="0", ATTR{online}="1" ''; </ins> virtualisation.lxd.agent.enable = lib.mkDefault true; }; }

with subtest("lxd-agent has a valid path"): machine.succeed("incus exec ${instance-name} -- bash -c 'true'") <ins> with subtest("guest supports cpu hotplug"): machine.succeed("incus config set ${instance-name} limits.cpu=1") count = int(machine.succeed("incus exec ${instance-name} -- nproc").strip()) assert count == 1, f"Wrong number of CPUs reported, want: 1, got: {count}" machine.succeed("incus config set ${instance-name} limits.cpu=2") count = int(machine.succeed("incus exec ${instance-name} -- nproc").strip()) assert count == 2, f"Wrong number of CPUs reported, want: 2, got: {count}" </ins> ''; })
Change:
Project description A practical and pragmatic code editor (a fork of Lite XL). Metadata homepage URL: source URL: license: mit platforms: unix Additional information Here's the package stub: Build script can't find Lua even though it is provided. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I have managed to build it, now I just need to clean it up and open a PR.

Discussion:
<ins> { lib, stdenv, fetchFromGitHub, cacert, meson, ninja, pkg-config, freetype, libgit2, libuchardet, libzip, lua5_4, luajit, mbedtls_2, pcre2, SDL2, zlib, }: stdenv.mkDerivation (finalAttrs: { pname = "pragtical"; version = "3.3.1"; pluginManagerVersion = "1.2.9"; src = fetchFromGitHub { owner = "pragtical"; repo = "pragtical"; rev = "v${finalAttrs.version}"; fetchSubmodules = true; # also fetch required git submodules postFetch = '' cd "$out" export NIX_SSL_CERT_FILE=${cacert}/etc/ssl/certs/ca-bundle.crt substituteInPlace subprojects/ppm.wrap  --replace-fail 'revision = head' 'revision = v${finalAttrs.pluginManagerVersion}' ${lib.getExe meson} subprojects download  colors plugins ppm find subprojects -type d -name .git -prune -execdir rm -r {} + ''; hash = "sha256-T0IHpfMfx4P84RyBLtaYNead6a7cID2cUYwkyNnYMgc="; }; nativeBuildInputs = [ meson ninja pkg-config ]; buildInputs = [ freetype libgit2 libuchardet libzip lua5_4 luajit mbedtls_2 pcre2 SDL2 zlib ]; # workaround for `libmbedx509.so.1, libmbedcrypto.so.7: error adding symbols: DSO missing from command line` env.NIX_LDFLAGS = "-lmbedx509 -lmbedcrypto"; mesonFlags = [ "-Duse_system_lua=true" ]; meta = { changelog = "https://github.com/pragtical/pragtical/blob/${finalAttrs.src.rev}/changelog.md"; description = "A practical and pragmatic code editor"; homepage = "https://pragtical.dev"; license = lib.licenses.mit; mainProgram = "pragtical"; maintainers = with lib.maintainers; [ suhr tomasajt ]; platforms = lib.platforms.linux; }; }) </ins>
Change:
The NixOS manual's section on Emacs has a . It states which is at the very least misleading and potentially confusing since the docbook migration. Either remove these references to the manual being in docbook, or remove the section in its entirety, since (with the completion of the docbook migration) it seems unclear what relevance xml editing in emacs has to NixOS at all, and people interested in the topic will presumably look to other resources elsewhere (e.g. ). (I'd open a PR for either, but am unsure which one to prefer, hence this issue) <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] 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]:

Discussion:
You can use `woman` to get completion of all available man pages. For example, type `M-x woman <RET> nixos-rebuild <RET>.` <del> ### Editing DocBook 5 XML Documents {#sec-emacs-docbook-xml} Emacs includes [nXML](https://www.gnu.org/software/emacs/manual/html_node/nxml-mode/Introduction.html), a major-mode for validating and editing XML documents. When editing DocBook 5.0 documents, such as [this one](#book-nixos-manual), nXML needs to be configured with the relevant schema, which is not included. To install the DocBook 5.0 schemas, either add {var}`pkgs.docbook5` to [](#opt-environment.systemPackages) ([NixOS](#sec-declarative-package-mgmt)), or run `nix-env -f '<nixpkgs>' -iA docbook5` ([Nix](#sec-ad-hoc-packages)). Then customize the variable {var}`rng-schema-locating-files` to include {file}`~/.emacs.d/schemas.xml` and put the following text into that file: ::: {.example #ex-emacs-docbook-xml} ### nXML Schema Configuration (`~/.emacs.d/schemas.xml`) ```xml <?xml version="1.0"?> <!-- To let emacs find this file, evaluate: (add-to-list 'rng-schema-locating-files "~/.emacs.d/schemas.xml") --> <locatingRules xmlns="http://thaiopensource.com/ns/locating-rules/1.0"> <!-- Use this variation if pkgs.docbook5 is added to environment.systemPackages --> <namespace ns="http://docbook.org/ns/docbook" uri="/run/current-system/sw/share/xml/docbook-5.0/rng/docbookxi.rnc"/> <!-- Use this variation if installing schema with "nix-env -iA pkgs.docbook5". <namespace ns="http://docbook.org/ns/docbook" uri="../.nix-profile/share/xml/docbook-5.0/rng/docbookxi.rnc"/> --> </locatingRules> ``` ::: </del>
Change:
Package name: kitty Latest released version: 0.34.1 <!-- Search your package here: --- Current version on the unstable channel: 0.34.0 Current version on the stable/release channel: 0.31.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]:

Discussion:
with python3Packages; buildPythonApplication rec { pname = "kitty"; <del> version = "0.34.0"; </del> <ins> version = "0.34.1"; </ins> format = "other"; src = fetchFromGitHub { owner = "kovidgoyal"; repo = "kitty"; rev = "refs/tags/v${version}"; <del> hash = "sha256-IP1CWMHiWnBSbt+78EQ6hfX2A9FDhlwt0KLthXtO4dA="; </del> <ins> hash = "sha256-r7KZcSqREILMp0F9ajeHS5sglq/o88h2t+4BgbABjOY="; </ins> }; goModules = (buildGo122Module {
Change:
Cannot run nvidia compatable containers with docker 25 and = true; Steps to reproduce the behavior: Enable the following Run the following command: Result: nvidia-smi prints gpu If the same command above is run with podman, it correctly prints the GPU. My use case revolves around using this feature in docker compose: I am running this GPU via PCIE passthrough on a libvirt qemu vm if that's relevant. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hello I didn't have the time to try to reproduce yet -- I do use podman myself. -- Looking at the source code, it seems that it needs to be enabled: Also documented in: Have you enabled it explicitly in the or by some NixOS means ( maybe?)
Good news! I was able to reproduce your issue (thank you for the detailed description and I can also confirm that adding the following to my NixOS configuration fixed it: Now I'm going to open a PR to fix this problem, so that CDI works out of the box for Docker users as well.

Discussion:
config = { <ins> virtualisation.docker.daemon.settings = lib.mkIf (config.hardware.nvidia-container-toolkit.enable && (lib.versionAtLeast config.virtualisation.docker.package.version "25")) { features.cdi = true; }; </ins> hardware.nvidia-container-toolkit.mounts = let nvidia-driver = config.hardware.nvidia.package; in (lib.mkMerge [
Change:
Package name: Jellyseerr Latest released version: 1.8.1 <!-- Search your package here: --- Current version on the unstable channel: 1.7.0 Current version on the stable/release channel: 1.7.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: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
{ "name": "jellyseerr", <del> "version": "1.7.0", </del> <ins> "version": "1.8.1", </ins> "private": true, "scripts": { "dev": "nodemon -e ts --watch server --watch overseerr-api.yml -e .json,.ts,.yml -x ts-node -r tsconfig-paths/register --files --project server/tsconfig.json server/index.ts",

{ <del> "version": "1.7.0", "srcHash": "sha256-9ILP2HH7p8ELwrQOBnqPbvHdUnNrqEkA4OmxOuhNbEc=", "yarnSha256": "1ygb8pmwra570wmdkn7mxv9j90cgjh063b9cl0wl9hsmg687sk9h" </del> <ins> "version": "1.8.1", "srcHash": "sha256-B8Hnpi4XwK0WrHRgj7OSVUh49oRH9SVEHdzGbnDa8p8=", "yarnSha256": "ME19kHlVw0Q5oCytYQCUj4Ek0+712NkqB6eozOtF6/k=" </ins> }
Change:
I am on the unstable channel, running KDE. When I install ktorrent 24.02.2 (kdePackages.ktorrent) some toolbar buttons like start, pause and stop a torrent is missing. When I try version 23.08.5 (libsForQt5.ktorrent) they are there as expected. Steps to reproduce the behavior: ktorrent 24.02.2 (kdePackages.ktorrent) at the toolbar. There is only new, open and paste icons. click and select configure toolbar, there should be a drop down menu for selecting torrent icons but it's missing. V.23: ! V.24: ! Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Apparently it's the new intended default layout? There's a 'Configure Toolbars...' button in Settings menu
Perhaps you are right, now I looked at the screenshot of ktorrent on KDE website and I don't see those buttons either. That's odd, so now people have to use hotkeys to manage torrents? That's very silly if they removed important toolbar buttons, it's something the Gnome team does but I don't expect KDE team to do it. Settings Configure Toolbars does not contain the missing buttons. On v23 there is a drop down menu there where the torrent management icons are. I am on Plasma 6.
Looks like it can't find the kxmlgui layout files
Is that something you could fix? I see that on Arch Linux those files for package ktorrent 24.02.2 are in the folder /usr/share/kxmlgui5/ktorrent/. On nix the files are in /nix/store/phi9j2i10065cqhs89wkr8c0ap1hrypx-ktorrent-24.02.1/share/kxmlgui6/ktorrent/. Perhaps the Arch maintainers copied the files from the older version and that's why there is a kxmlgui5 folder instead of kxmlgui6. Maybe the buttons are present on Arch, I can not test now. If this can not be fixed then this report can be closed and I will have to either use hotkeys or switch to qbitorrent.
Yeah, it looks for kxmlgui5 directory while nixpkgs seem to force kxmlgui6
Oh great, kxmlgui has kxmlgui5 hardcoded in a bunch of places to this day.
Please test

Discussion:
cmakeFlags+=" -DKDE_INSTALL_KCONFUPDATEDIR=${!outputBin}/share/kconf_update" cmakeFlags+=" -DKDE_INSTALL_KAPPTEMPLATESDIR=${!outputDev}/share/kdevappwizard/templates" cmakeFlags+=" -DKDE_INSTALL_KFILETEMPLATESDIR=${!outputDev}/share/kdevfiletemplates/templates" <del> cmakeFlags+=" -DKDE_INSTALL_KXMLGUIDIR=${!outputBin}/share/kxmlgui6" </del> <ins> cmakeFlags+=" -DKDE_INSTALL_KXMLGUIDIR=${!outputBin}/share/kxmlgui5"  # Yes, this needs to be 5 and not 6. Don't ask. </ins> cmakeFlags+=" -DKDE_INSTALL_KNOTIFYRCDIR=${!outputBin}/share/knotifications6" cmakeFlags+=" -DKDE_INSTALL_ICONDIR=${!outputBin}/share/icons" cmakeFlags+=" -DKDE_INSTALL_LOCALEDIR=${!outputLib}/share/locale"
Change:
retains references to packages, bloating the closure massively. I'd expect to see no such results. If comparing to qt5: n/a Seems related to some wrapping issue. For example: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --All examples above were built against Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Do we need the qt6 plugins for designer?
I achieved the following nix diff-closures with the diff: The patch is not perfect but maybe a starting point?
Maybe a separate output that's not $dev for those plugins?
That change brings the closure from (nominally) 1.05 GiB to 925 MiB. I think the other notably sized dependency would be which appears to add 100+ MiB of its own (as it brings along ), but it's indirectly coming from

Discussion:
{ lib <ins> , stdenv </ins> , fetchFromGitLab <del> , mkKdeDerivation </del> , breeze-icons , breeze , cmake

, kirigami , kxmlgui , kdoctools <del> , mpv </del> <ins> , mpvqt </ins> , pkg-config , wrapQtAppsHook , qqc2-desktop-style

, yt-dlp }: <del> mkKdeDerivation rec { </del> <ins> stdenv.mkDerivation rec { </ins> pname = "haruna"; version = "1.0.2";

kirigami kxmlgui kdoctools <del> mpv </del> <ins> mpvqt </ins> qtbase ];

defaultArgs = { inherit version src; <del> outputs = ["out" "dev"]; </del> <ins> outputs = ["out" "dev" "devtools"]; </ins> nativeBuildInputs = [cmake qt6.wrapQtAppsHook moveDevHook] ++ extraNativeBuildInputs; buildInputs = [qt6.qtbase] ++ extraBuildInputs;

# shellcheck disable=SC2154 moveKF6DevTools() { <del> moveToOutput "${qtPluginPrefix}/designer" "${!outputDev}" </del> <ins> if [ -n "$devtools" ]; then mkdir -p "$devtools" moveToOutput "${qtPluginPrefix}/designer" "$devtools" fi </ins> } postInstallHooks+=('moveKF6DevTools')

hash = "sha256-XHiCxH7dJxJamloM2SJbiFHDt8j4rVfv/M9PaBzvgM4="; }; <del> extraBuildInputs = [mpv qtdeclarative]; </del> <ins> extraBuildInputs = [qtdeclarative]; extraPropagatedBuildInputs = [mpv]; </ins> meta.license = with lib.licenses; [bsd2 bsd3 cc-by-sa-40 cc0 lgpl21Only lgpl3Only lgpl3Plus mit]; }

nativeBuildInputs = []; buildInputs = []; <ins> outputs = ["out"]; </ins> installPhase = '' runHook preInstall
Change:
Steps to reproduce the behavior: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
perlPackages.buildPerlPackage rec { pname = "SpamAssassin"; <del> version = "4.0.0"; rulesRev = "r1905950"; </del> <ins> version = "4.0.1"; rulesRev = "r1916528"; </ins> src = fetchurl { url = "mirror://apache/spamassassin/source/Mail-${pname}-${version}.tar.bz2"; <del> hash = "sha256-5aoXBQowvHK6qGr9xgSMrepNHsLsxh14dxegWbgxnog="; </del> <ins> hash = "sha256-l3XtdVnoPsPmwD7bK+j/x/FcxAX7E+hcFI6wvxkXIag="; </ins> }; defaultRulesSrc = fetchurl { url = "mirror://apache/spamassassin/source/Mail-${pname}-rules-${version}.${rulesRev}.tgz"; <del> hash = "sha256-rk/7uRfrx/76ckD8W7UVHdpmP45AWRYa18m0Lu0brG0="; </del> <ins> hash = "sha256-OB6t/H5RPl9zU4m3gXPeWvRx89Bv5quPEpY0pmRLS/Q="; </ins> }; patches = [
Change:
I noticed in the derivation, but do not see it defined anywhere.
Pinging What is the status of this attribute? Should it be used? What purpose does it serve? It seems to me like it would be simpler if we just explicitly to .
It is defined in the cross adapter in . Yeah, I want to get rid of , like (). It's pointless.
Will be closed automatically when staging is merged.

Discussion:
in stdenv // { mkDerivation = { nativeBuildInputs ? [] <del> , selfNativeBuildInput ? args.crossAttrs.selfNativeBuildInput or false </del> , ... } @ args: <del> let # *BuildInputs exists temporarily as another name for # *HostInputs. # The base stdenv already knows that nativeBuildInputs and # buildInputs should be built with the usual gcc-wrapper # And the same for propagatedBuildInputs. nativeDrv = stdenv.mkDerivation args; in </del> stdenv.mkDerivation (args // { nativeBuildInputs = nativeBuildInputs <del> ++ stdenv.lib.optional selfNativeBuildInput nativeDrv </del> # without proper `file` command, libtool sometimes fails # to recognize 64-bit DLLs ++ stdenv.lib.optional (hostPlatform.config == "x86_64-w64-mingw32") pkgs.file
Change:
Steps to reproduce the behavior: Add any other context about the problem here. <!-- 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 started with but unfortunately there is more to do.

Discussion:
pname = "omegaconf"; version = "2.3.0"; pyproject = true; disabled = pythonOlder "3.6"; src = fetchFromGitHub { owner = "omry"; <del> repo = pname; </del> <ins> repo = "omegaconf"; </ins> rev = "refs/tags/v${version}"; hash = "sha256-Qxa4uIiX5TAyQ5rFkizdev60S4iVAJ08ES6FpNqf8zI="; };

sed -i 's/antlr4-python3-runtime==.*/antlr4-python3-runtime/' requirements/base.txt ''; <del> nativeBuildInputs = [ </del> <ins> build-system = [ </ins> setuptools <ins> ]; nativeBuildInputs = [ </ins> jre_minimal ]; <del> propagatedBuildInputs = [ </del> <ins> dependencies = [ </ins> antlr4-python3-runtime pyyaml ];

"ignore::DeprecationWarning" ]; <ins> disabledTests = [ "test_eq" ]; </ins> meta = with lib; { description = "Framework for configuring complex applications"; homepage = "https://github.com/omry/omegaconf";

buildPythonPackage rec { pname = "pydevd"; <del> version = "2.10.0"; </del> <ins> version = "3.0.3"; </ins> pyproject = true; disabled = pythonOlder "3.8";

owner = "fabioz"; repo = "PyDev.Debugger"; rev = "pydev_debugger_${lib.replaceStrings ["."] ["_"] version}"; <del> hash = "sha256-1tWiPj30x/ZXIBu2qzUCpyF1bLsJ0wW1QaxklD3h3A8="; </del> <ins> hash = "sha256-aylmLN7lVUza2lt2K48rJsx3XatXPgPjcmPZ05raLX0="; </ins> }; <del> nativeBuildInputs = [ </del> <ins> __darwinAllowLocalNetworking = true; build-system = [ </ins> setuptools ]; <del> __darwinAllowLocalNetworking = true; </del> nativeCheckInputs = [ numpy psutil

# https://github.com/fabioz/PyDev.Debugger/issues/227 "test_to_server_and_to_client" # AssertionError pydevd_tracing.set_trace_to_threads(tracing_func) == 0 <del> "test_tracing_other_threads" </del> <ins> "test_step_next_step_in_multi_threads" </ins> "test_tracing_basic" <ins> "test_tracing_other_threads" # subprocess.CalledProcessError "test_find_main_thread_id" </ins> ] ++ lib.optionals (pythonAtLeast "3.12") [ "test_case_handled_and_unhandled_exception_generator" "test_case_stop_async_iteration_exception"

meta = with lib; { description = "PyDev.Debugger (used in PyDev, PyCharm and VSCode Python)"; <del> mainProgram = "pydevd"; </del> homepage = "https://github.com/fabioz/PyDev.Debugger"; license = licenses.epl10; maintainers = with maintainers; [ onny ]; <ins> mainProgram = "pydevd"; </ins> }; }
Change:
Steps to reproduce the behavior: (e.g. use sth like ) (tried on both unstable n unstable-small) Seems somewhat similara Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Perhaps we can just remove this package? It's only required by ntfy-sh currently, which . Also, according to those release notes, hooks are a native part of mkdocs since 1.4, so I want to propose to just remove this.

Discussion:
<del> { lib , buildPythonPackage , isPy3k , fetchFromGitHub , mkdocs , pytestCheckHook }: buildPythonPackage rec { pname = "mkdocs-simple-hooks"; version = "0.1.5"; format = "setuptools"; disabled = !isPy3k; src = fetchFromGitHub { owner = "aklajnert"; repo = "mkdocs-simple-hooks"; rev = "v${version}"; hash = "sha256-N6xZjCREjJlhR6f8m65WJswUQv/TTdTbk670+C46UWQ="; }; propagatedBuildInputs = [ mkdocs ]; nativeCheckInputs = [ pytestCheckHook ]; pytestFlagsArray = [ "tests.py" ]; # disable failing tests disabledTests = [ "test_no_hooks_defined" "test_no_attribute" ]; meta = with lib; { description = "Define your own hooks for mkdocs, without having to create a new package."; homepage = "https://github.com/aklajnert/mkdocs-simple-hooks"; license = licenses.mit; maintainers = with maintainers; [ arjan-s ]; }; } </del>

mkdocs-rss-plugin = callPackage ../development/python-modules/mkdocs-rss-plugin { }; <del> mkdocs-simple-hooks = callPackage ../development/python-modules/mkdocs-simple-hooks { }; </del> mkdocs-swagger-ui-tag = callPackage ../development/python-modules/mkdocs-swagger-ui-tag { }; mkdocstrings = callPackage ../development/python-modules/mkdocstrings { };