jiebi/CodeConvo huggingface dataset:
Change:
Steps to reproduce the behavior: the chromadb python package for python310. [1/7/9 built] building python3.10-chromadb-0.5.0 (pytestCheckPhase): chromadb/test/auth/testbasicauth[1/7/9 built] building python3.10-chromadb-0.5.0 (pytestCheckPhase): chromadb/test/aut[1/7/9 built] building python3.10-chromadb-0.5.0 (pytestCheckPhase): ... [ 4%] [1/7/9 built] building python3.10-chromadb-0.5.0 (pytestCheckPhase): ... [ 4%] [1/7/9 built] building python3.10-chromadb-0.5.0 (pytestCheckPhase): ... [ 4%] This is not the complete log but it is all that is visible in my terminal since only keeps the latest however many lines. The build reaches this test at 4% every time and then stalls there. I was able to fix the issue by adding an overlay to disable pytestCheckPhase, but this is obviously a workaround. <!-- 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 are flaky. I will ship an update later.

Discussion:
buildPythonPackage rec { pname = "chromadb"; <del> version = "0.5.4"; </del> <ins> version = "0.5.5"; </ins> pyproject = true; disabled = pythonOlder "3.9";

owner = "chroma-core"; repo = "chroma"; rev = "refs/tags/${version}"; <del> hash = "sha256-wzfzuWuNqLAjfAZC38p1iTtJHez/pJ9Ncgeo23o1dMo="; </del> <ins> hash = "sha256-e6ZctUFeq9hHXWaxGdVTiqFpwaU7A+EKn2EdQPI7DHE="; </ins> }; cargoDeps = rustPlatform.fetchCargoTarball { inherit src; name = "${pname}-${version}"; <del> hash = "sha256-0OE2i29oE6RpJRswQWI8+5dbA6lOWd3nhqe1RGlnjhk="; </del> <ins> hash = "sha256-3FmnQEpknYNzI3WlQ3kc8qa4LFcn1zpxKDbkATU7/48="; </ins> }; pythonRelaxDeps = [

"orjson" ]; <ins> build-system = [ setuptools setuptools-scm ]; </ins> nativeBuildInputs = [ cargo pkg-config protobuf rustc rustPlatform.cargoSetupHook <del> setuptools setuptools-scm </del> ]; buildInputs = [

zstd ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.Security ]; <del> propagatedBuildInputs = [ </del> <ins> dependencies = [ </ins> bcrypt build chroma-hnswlib

''; disabledTests = [ <del> # flaky / timing sensitive </del> <ins> # Tests are laky / timing sensitive </ins> "test_fastapi_server_token_authn_allows_when_it_should_allow" <ins> "test_fastapi_server_token_authn_rejects_when_it_should_reject" </ins> ]; disabledTestPaths = [
Change:
Currently, the derivation for libsigc++ includes a patch that appends to . As a result a C++ project that uses libsigc++-2.0 may be interpreted according to a different standard than expected. For instance, and using libsigc++ via pkg-config effectively downgrades this to C++11. The patch responsible seems to originate from the Debian project . As a side note, I feel pkg-config files are not the place to force a certain c++ standard. a c++ file that conforms to C++14 and higher (but not lower) a nix expression, e.g. that lists gcc, pkgconfig and libsigcxx as buildInputs the following command

Discussion:
url = "mirror://gnome/sources/libsigc++/${ver_maj}/${name}.tar.xz"; sha256 = "f843d6346260bfcb4426259e314512b99e296e8ca241d771d21ac64f28298d81"; }; <del> patches = [(fetchpatch { url = "https://anonscm.debian.org/cgit/collab-maint/libsigc++-2.0.git/plain" + "/debian/patches/0002-Enforce-c-11-via-pkg-config.patch?id=d451a4d195b1"; sha256 = "19g19473syp2z3kg8vdrli89lm9kcvaqajkqfmdig1vfpkbq0nci"; })]; </del> nativeBuildInputs = [ pkgconfig gnum4 ];
Change:
Suppose you have a project with some native dependency like and try to inside of a like this: Before , this worked fine, but since , building fails: Minimal reproducible example is in I only tested this on . Running for the example above shows that is missing from and . Indeed, adding to the resolves the problem:
cc
Interesting. Especially since we decided against using runCommandNoCC but somehow arrived at similar behavior. Sorry we broke this. I wonder what the best fix is. Should shellFor just always add the GCC dep? Or should gcc maybe become a runtime dependency of cabal-install since apparently that's actually what's going on here?
.
That’s an explanation, thank you! Now the question: What is the correct way to get gcc into scope? I guess the most pragmatic way is to just add it as a dependency of runCommand, but it feels like that is a bit wrong.
should work…
Still not convinced, that’s a clean solution. But yeah, I’ll do that.
Why wouldn't that be a clean solution? The C compiler is part of , so we need to make sure the environment also uses the default that actually has one.
I just wasn’t sure whether every shell should contain stdenv. But I guess that’s kinda stupid.

Discussion:
{ lib, stdenv, buildPackages, buildHaskellPackages, ghc <del> , jailbreak-cabal, hscolour, cpphs, runCommand </del> <ins> , jailbreak-cabal, hscolour, cpphs, runCommandCC </ins> , ghcWithHoogle, ghcWithPackages , nodejs }:

lib.optionals (!isCross) setupHaskellDepends); ghcCommandCaps = lib.toUpper ghcCommand'; <del> in runCommand name { </del> <ins> in runCommandCC name { </ins> inherit shellHook; depsBuildBuild = lib.optional isCross ghcEnvForBuild;
Change:
part of No errors in native compliation of emacsPackages.consult-gh <!-- 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]:

Discussion:
{ lib, consult, <del> embark, </del> <ins> embark-consult, </ins> fetchFromGitHub, forge, gh,

melpaBuild { pname = "consult-gh"; <del> version = "1.0-unstable-2024-08-11"; </del> <ins> version = "1.0-unstable-2024-08-24"; </ins> src = fetchFromGitHub { owner = "armindarvish"; repo = "consult-gh"; <del> rev = "640d4b9c71aa6dfff4f29c0207cc02316f1d61c8"; hash = "sha256-hFHex4cUAP1U5aK1bfa+va1jiWS8tRqtnMGxr17NWio="; </del> <ins> rev = "b1d85d179438e4b6469e1b78906a7dde8f07c822"; hash = "sha256-VmxuXvO0nl0h9IKU+XWfjW90KG/1B+qHoOVhvYJ8XTs="; </ins> }; packageRequires = [ consult <del> embark </del> <ins> embark-consult </ins> forge markdown-mode ]; propagatedUserEnvPkgs = [ gh ]; <ins> ignoreCompilationError = false; </ins> passthru.updateScript = unstableGitUpdater { }; meta = {
Change:
Steps to reproduce the behavior: Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
--out-dir lib/html-language-server/node/ npx babel ${extensions}/json-language-features/server/dist/node  --out-dir lib/json-language-server/node/ <del> npx babel ${extensions}/markdown-language-features/server/dist/node  --out-dir lib/markdown-language-server/node/ </del> cp -r ${vscode-extensions.dbaeumer.vscode-eslint}/share/vscode/extensions/dbaeumer.vscode-eslint/server/out  lib/eslint-language-server <del> mv lib/markdown-language-server/node/workerMain.js lib/markdown-language-server/node/main.js </del> ''; meta = with lib; {
Change:
Steps to reproduce the behavior: xdg-desktop-portal Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Can't repro on ()
I'm rebuilding /nix/store/1md85bcdrifm51lwmvj4qbcfcakbkz9r-xdg-desktop-portal- yet. My config was at As you can see, any override was not here.
I still can't repro, even with rebuilding. Could be a flaky test. Try building the package (not the config) on directly to rule out config issues.
It is caused by reading /proc/cmdline. It's confusing. Maybe it was an unreduciable build.
is the command line passed to your kernel, so... check kernel config? The "file" is world-readable for me though.
I mean we shouldn't read this actually, according to . That was a bug caused by nix. I think the best way is disabling this test. Anyway, I just use linux-zen-6.10.1 without any rebuild just from cache. I do not think It has anything to do with my kernel config.
This is a hilarious test actually: I'm tempted to just disable it entirely.
can you check and reply there if it works for you?
My remote desktop lost connection. Will be tested tonight.
Test are done.

Discussion:
# While upstream has `XDG_DESKTOP_PORTAL_DIR`, it is meant for tests and actually blocks # any configs from being loaded from anywhere else. ./nix-pkgdatadir-env.patch <ins> # test tries to read /proc/cmdline, which is not intended to be accessible in the sandbox ./trash-test.patch </ins> ]; nativeBuildInputs = [

<ins> diff --git a/tests/test_trash.py b/tests/test_trash.py index d745cd2..173e3e5 100644 --- a/tests/test_trash.py +++ b/tests/test_trash.py @@ -24,13 +24,6 @@ class TestTrash: def test_version(self, portal_mock): portal_mock.check_version(1) -    def test_trash_file_fails(self, portal_mock): -        trash_intf = portal_mock.get_dbus_interface() -        with open("/proc/cmdline") as fd: -            result = trash_intf.TrashFile(fd.fileno()) - -        assert result == 0 - def test_trash_file(self, portal_mock): trash_intf = portal_mock.get_dbus_interface() </ins>
Change:
Currently we provide packages for the syncthing versions 0.14, 0.12 and 0.13. The versions 0.12 and 0.13 are known to be an security issue (CVE-2017-) but not marked as such. Is there still a need for them or can we a) mark them as insecure, or b) remove them? In any way I would at least vote for having them marked as insecure. CC current syncthing maintainers:
The reason for keeping multiple versions around is due to the fairly rapid pace of development where new versions are not backwards compatible. We should definitely at least mark them as insecure. Feel like a PR?
I can provide that PR. What is a sensible timeline to remove the old versions then? Most if not all relevant distributions ship 0.14 already:
the PR has been created.
Merged. I'll post a notice on the ML. Let's target 1st Feb for removal.
Thanks!

Discussion:
preBuild = '' export buildFlagsArray+=("-tags" "noupgrade release") ''; <ins> meta = { knownVulnerabilities = [ "CVE-2017-1000420" ]; homepage = https://www.syncthing.net/; description = "Open Source Continuous File Synchronization"; license = stdenv.lib.licenses.mpl20; platforms = with stdenv.lib.platforms; linux ++ freebsd ++ openbsd ++ netbsd; }; </ins> }

''; meta = { <ins> knownVulnerabilities = [ "CVE-2017-1000420" ]; </ins> homepage = https://www.syncthing.net/; description = "Open Source Continuous File Synchronization"; license = stdenv.lib.licenses.mpl20;
Change:
Package name: proton-pass Latest released version: 1.22.0 <!-- Search your package here: --- Current version on the unstable channel: 1.20.2 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]:

Discussion:
}: stdenvNoCC.mkDerivation (finalAttrs: { pname = "proton-pass"; <del> version = "1.20.2"; </del> <ins> version = "1.22.0"; </ins> src = fetchurl { url = "https://proton.me/download/PassDesktop/linux/x64/ProtonPass_${finalAttrs.version}.deb"; <del> hash = "sha256-4QSBKVnEH7yDXwqY+29/a+yWv89i/TVCYO26V95KA4s="; </del> <ins> hash = "sha256-ARIUHmU/YN8IoAFMkcxzGAoH31vbJLT7HfYD6a57QaY="; </ins> }; dontConfigure = true;

description = "Desktop application for Proton Pass"; homepage = "https://proton.me/pass"; license = lib.licenses.gpl3Plus; <del> maintainers = with lib.maintainers; [ massimogengarelli sebtm ]; </del> <ins> maintainers = with lib.maintainers; [ luftmensch-luftmensch massimogengarelli sebtm ]; </ins> platforms = [ "x86_64-linux" ]; sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ]; mainProgram = "proton-pass";
Change:
Trying to run an action with azure-cli that requries authentication, az will fail to read the cached authentication token from the token cache: This is due to a version mismatch of . will update the package, I checked that the authentication works afterwards. That's me! Please run and paste the result. ` Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I also experience this issue with , as well as with . Thanks for adding the fix!

Discussion:
buildPythonPackage rec { pname = "msal-extensions"; <del> version = "1.1.0"; </del> <ins> version = "1.2.0"; </ins> pyproject = true; disabled = pythonOlder "3.7";

owner = "AzureAD"; repo = "microsoft-authentication-extensions-for-python"; rev = "refs/tags/${version}"; <del> hash = "sha256-ScInTvOgFxP5mgep5FRu6YZHPTtXhrcZGFE7Wdvcm4c="; </del> <ins> hash = "sha256-javYE1XDW1yrMZ/BLqIu/pUXChlBZlACctbD2RfWuis="; </ins> }; <del> nativeBuildInputs = [ setuptools ]; </del> <ins> build-system = [ setuptools ]; </ins> <del> propagatedBuildInputs = [ </del> <ins> dependencies = [ </ins> msal portalocker ];

buildPythonPackage rec { pname = "msal"; <del> version = "1.29.0"; </del> <ins> version = "1.30.0"; </ins> pyproject = true; disabled = pythonOlder "3.7"; src = fetchPypi { inherit pname version; <del> hash = "sha256-j2cl8Jl1JVP5sv6EEl4qXr5HtJ+S6syjPr7dOp66riU="; </del> <ins> hash = "sha256-tL8AhQCS5GUVfYFO+iShj3iChMmkeUkQJNYpAwheovs="; </ins> }; <del> nativeBuildInputs = [ setuptools ]; </del> <ins> build-system = [ setuptools ]; </ins> <del> propagatedBuildInputs = [ </del> <ins> dependencies = [ </ins> cryptography pyjwt requests
Change:
nixpkgs @
Introduced in
apologies for the breakage, please see
Thanks! Unfortunately, I have no rights to merge.
Please review and test, then I will merge.
Yep, it works.
Merged. In future, could you use the "Files changed" tab on the PR to do acceptance?

Discussion:
cudaPackages.cuda_cudart cudaPackages.cuda_cccl # <thrust/*> cudaPackages.libnpp # npp.h <del> cudaPackages.nvidia-optical-flow-sdk </del> <ins> nvidia-optical-flow-sdk </ins> ] ++ lib.optionals enableCublas [ # May start using the default $out instead once # https://github.com/NixOS/nixpkgs/issues/271792
Change:
When signing in to the Bitwarden, I am met with the following . I have KDE wallet turned off, and my NixOS and nixpkgs channel are both set to stable. I also have another nix machine that runs NixOS and nixpkgs on unstable and this bug does not occur despite having KDE wallet turned off there as well. Bug is potentially tied to Steps to reproduce the behavior: off KDE wallet in to Bitwarden-desktop stable. Should sign in without issue despite KDE wallet being disabled. ! A package update would be great, as my understanding is this was fixed in an update by Bitwarden devs.

Discussion:
, cargo , copyDesktopItems , dbus <del> , electron_28 </del> <ins> , electron_29 </ins> , fetchFromGitHub , glib , gnome

, makeWrapper , moreutils , napi-rs-cli <del> , nodejs_18 </del> <ins> , nodejs_20 </ins> , patchutils_0_4_2 , pkg-config , python3

}: let <del> description = "A secure and free password manager for all of your devices"; </del> <ins> description = "Secure and free password manager for all of your devices"; </ins> icon = "bitwarden"; <del> electron = electron_28; </del> <ins> electron = electron_29; </ins> in buildNpmPackage rec { pname = "bitwarden-desktop"; <del> version = "2024.4.1"; </del> <ins> version = "2024.6.4"; </ins> src = fetchFromGitHub { owner = "bitwarden"; repo = "clients"; rev = "desktop-v${version}"; <del> hash = "sha256-UzVzo8tq719W2EwUE4NfvUrqhb61fvd60EGkavQmv3Q="; </del> <ins> hash = "sha256-oQ2VZoxePdYUC+xMKlRMpvPubSPULvt31XSh/OBw3Ec="; </ins> }; patches = [

| ${moreutils}/bin/sponge apps/desktop/src/package-lock.json ''; <del> nodejs = nodejs_18; </del> <ins> nodejs = nodejs_20; </ins> makeCacheWritable = true; <del> npmFlags = [ "--legacy-peer-deps" ]; </del> <ins> npmFlags = [ "--engine-strict" "--legacy-peer-deps" ]; </ins> npmWorkspace = "apps/desktop"; <del> npmDepsHash = "sha256-qkg1psct/ekIXB6QmJX1n/UOKUhYSD9Su7t/b4/4miM="; </del> <ins> npmDepsHash = "sha256-9d9pWrFYelAx/PPDHY3m92Frp8RSQuBqpiOjmWtm/1g="; </ins> cargoDeps = rustPlatform.fetchCargoTarball { name = "${pname}-${version}";

patches; patchFlags = [ "-p4" ]; sourceRoot = "${src.name}/${cargoRoot}"; <del> hash = "sha256-lvEJmjzhpMhm+9INYHWpdltinUOI3DMtFN/ddDQrUvo="; </del> <ins> hash = "sha256-ZmblY1APVa8moAR1waVBZPhrf5Wt1Gi6dvAxkhizckQ="; </ins> }; cargoRoot = "apps/desktop/desktop_native";

cp -r locales resources{,.pak} $out/opt/Bitwarden popd <del> makeWrapper '${electron}/bin/electron' "$out/bin/bitwarden"  </del> <ins> makeWrapper '${lib.getExe electron}' "$out/bin/bitwarden"  </ins> --add-flags $out/opt/Bitwarden/resources/app.asar  --add-flags "''${NIXOS_OZONE_WL:+''${WAYLAND_DISPLAY:+--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations}}"  --set-default ELECTRON_IS_DEV 0
Change:
The package contains a prebuilt file which links to which obviously won't work on NixOS. Steps to reproduce the behavior: to system packages to open it from application launcher won't find the executable The field in the file should point to the actual executable in the nix store Running a simple script to replace the offending line with during the build might already be able to fix the issue. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
<del> { lib , stdenv , fetchFromGitHub , unstableGitUpdater , curl , gtkmm3 , glibmm , gnutls , yajl , pkg-config </del> <ins> { lib, stdenv, fetchFromGitHub, unstableGitUpdater, curl, gtkmm3, glibmm, gnutls, yajl, pkg-config, </ins> }: stdenv.mkDerivation (finalAttrs: { pname = "samrewritten";

makeFlags = [ "PREFIX=$(out)" ]; <del> nativeBuildInputs = [ pkg-config ]; </del> <ins> nativeBuildInputs = [ pkg-config ]; </ins> buildInputs = [ curl

yajl ]; <ins> postInstall = '' substituteInPlace $out/share/applications/samrewritten.desktop  --replace-fail "Exec=/usr/bin/samrewritten" "Exec=samrewritten" ''; </ins> passthru.updateScript = unstableGitUpdater { }; meta = {
Change:
Package name: blastem Latest released version: 0.6.2-unstable-2024-08-14 <!-- Search your package here: --- Current version on the unstable channel: 0.6.2-unstable-2024-03-31 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]:

Discussion:
stdenv.mkDerivation (finalAttrs: { pname = "blastem"; <del> version = "0.6.2-unstable-2024-03-31"; </del> <ins> version = "0.6.2-unstable-2024-08-14"; </ins> src = fetchhg { url = "https://www.retrodev.com/repos/blastem"; <del> rev = "48ab1e3e5df5"; hash = "sha256-UZl5fIE7LJqxwS8kFJ3xr8BJyHF60dnRNeA5k7lAuxg="; </del> <ins> rev = "aa888682faa0"; hash = "sha256-0xw9O0o1pkJiXHyZer4nMJeLlRXS3Z4YYoLgfkrz3Yo="; </ins> }; # will probably be fixed in https://github.com/NixOS/nixpkgs/pull/302481
Change:
Package name: pcsx2 Latest released version: 2.1.98 <!-- Search your package here: --- Current version on the unstable channel: 2.1.17 Current version on the stable/release channel: 1.7.5587 <!-- 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]:
As you wish:

Discussion:
lib, fetchFromGitHub, fetchpatch, <del> pcsx2, </del> shaderc, }: <del> { </del> <ins> let </ins> pcsx2 = let self = { pname = "pcsx2"; <del> version = "2.1.17"; </del> <ins> version = "2.1.102"; </ins> src = fetchFromGitHub { <ins> pname = "pcsx2-source"; inherit (self) version; </ins> owner = "PCSX2"; repo = "pcsx2"; rev = "v${self.version}"; <del> hash = "sha256-yVao/8ZAssM0llKMR66fMbzsRL3WCkFyUk6ZD/MEaSc="; </del> <ins> hash = "sha256-OBxrdZVx6HbSFO6sc2D2HP6iYH3ZKDj+uEqM7cxZNm0="; </ins> }; }; in

# The pre-zipped files in releases don't have a versioned link, we need to zip # them ourselves <del> pcsx2_patches = { pname = "pcsx2_patches"; version = "0-unstable-2024-07-14"; src = fetchFromGitHub { owner = "PCSX2"; repo = "pcsx2_patches"; rev = "afb17c4d851c54f93d4249e1e1dc8c57e2d0e6c6"; hash = "sha256-OaZ5TMbxM4v4HhLa2ctM8xx//FQkHH3+dkxZX9/svjc="; </del> <ins> pcsx2_patches = let self = { pname = "pcsx2_patches"; version = "0-unstable-2024-08-12"; src = fetchFromGitHub { pname = "pcsx2_patches-source"; inherit (self) version; owner = "PCSX2"; repo = "pcsx2_patches"; rev = "9ea7fca481e1e4c2263ca69f9a5c9a70c92626dc"; hash = "sha256-T0yTTW6P/NrZsANoduj+gCXyd5qqDRETxLblmnVnP/o="; }; </ins> }; <del> }; </del> <ins> in self; </ins> shaderc-patched = let pname = "shaderc-patched-for-pcsx2";

(lib.cmakeBool "SHADERC_SKIP_TESTS" true) ]; }); <ins> in { inherit pcsx2 pcsx2_patches shaderc-patched; </ins> }
Change:
Package name: Latest released version: 0.28.0 <!-- Search your package here: --- Current version on the unstable channel: 0.27.0 Current version on the stable/release channel: N/A <!-- 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! --- There is an old one for updating to 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 tried doing this myself but can't get it to build as the new version request Golang 1.23 and I couldn't work out how to get nix to build with that.

Discussion:
{ lib, <ins> go_1_23, </ins> buildGoModule, fetchFromGitHub, installShellFiles,

resticprofile, }: <del> buildGoModule rec { </del> <ins> let # can be removed when the default go version is at least 1.23 buildGoModule' = buildGoModule.override { go = go_1_23; }; in buildGoModule' rec { </ins> pname = "resticprofile"; <del> version = "0.27.1"; </del> <ins> version = "0.28.0"; </ins> src = fetchFromGitHub { owner = "creativeprojects"; repo = "resticprofile"; rev = "refs/tags/v${version}"; <del> hash = "sha256-HHFeWsEO1KUzL5Y6Iwy7MylA//JYzY3h1EwKrUHfXpY="; </del> <ins> hash = "sha256-Ab+XesAw/GkNEGwAp1ERUlfDlI9Kxmd0UnS52v+nWIs="; </ins> }; postPatch = ''

''; <del> vendorHash = "sha256-t2R5uNsliSn+rIvRM0vT6lQJY62DhhozXnONiCJ9CMc="; </del> <ins> vendorHash = "sha256-LLFdVB4n07Sq/QH1C7rutdpzfhkJvM9lvRg5exyYixM="; </ins> ldflags = [ "-X main.commit=${src.rev}"