jiebi/CodeConvo huggingface dataset:
Change:
Project description Metadata homepage URL: source URL: license: gpl3 platforms: linux

Discussion:
<ins> { lib , stdenv , fetchFromGitHub , python3 }: stdenv.mkDerivation rec { pname = "dool"; version = "1.2.0"; src = fetchFromGitHub { owner = "scottchiefbaker"; repo = "dool"; rev = "v${version}"; hash = "sha256-e6gLPmxOZBw6htiJ5Ljob2tQ9xB4kjK8vPs/9WMGER4="; }; buildInputs = [ python3 ]; makeFlags = [ "prefix=$(out)" ]; # fix the plugins directory postPatch = '' substituteInPlace dool  --replace  "os.path.abspath(os.path.dirname(sys.argv[0])) + '/plugins/'"  "'$out/share/dool/'" ''; meta = with lib; { description = "Python3 compatible clone of dstat"; homepage = "https://github.com/scottchiefbaker/dool"; changelog = "https://github.com/scottchiefbaker/dool/blob/${src.rev}/ChangeLog"; license = licenses.gpl3Plus; maintainers = with maintainers; [ figsoda ]; platforms = platforms.unix; }; } </ins>

buildGoModule = buildGo119Module; # build fails with 1.20 }; <ins> dool = callPackage ../tools/system/dool { }; </ins> dosfstools = callPackage ../tools/filesystems/dosfstools { }; dotnetfx35 = callPackage ../development/libraries/dotnetfx35 { };
Change:
Configuring with special characters (like ) causes the Syncthing service to fail: Device names may be any string that Syncthing supports via its UI. Syncthing does support . (guessing based on ) system: - nixpkgs @
Could you confirm fixes the issue? would also fix it
Yep, fixes it. Thanks!

Discussion:
# generate the new config by merging with the NixOS config options new_cfg=$(printf '%sn' "$old_cfg" | ${pkgs.jq}/bin/jq -c '. * { <del> "devices": (${builtins.toJSON devices}${optionalString (cfg.devices == {} || ! cfg.overrideDevices) " + .devices"}), "folders": (${builtins.toJSON folders}${optionalString (cfg.folders == {} || ! cfg.overrideFolders) " + .folders"}) } * ${builtins.toJSON cfg.extraOptions}') </del> <ins> "devices": ('${escapeShellArg (builtins.toJSON devices)}'${optionalString (cfg.devices == {} || ! cfg.overrideDevices) " + .devices"}), "folders": ('${escapeShellArg (builtins.toJSON folders)}'${optionalString (cfg.folders == {} || ! cfg.overrideFolders) " + .folders"}) } * '${escapeShellArg (builtins.toJSON cfg.extraOptions)}) </ins> # send the new config curl -X PUT -d "$new_cfg" ${cfg.guiAddress}/rest/config

import ./make-test-python.nix ({ lib, pkgs, ... }: let testId = "7CFNTQM-IMTJBHJ-3UWRDIU-ZGQJFR6-VCXZ3NB-XUH3KZO-N52ITXR-LAIYUAU"; <ins> testName = "testDevice foo'bar"; </ins> in { name = "syncthing-init";

nodes.machine = { services.syncthing = { enable = true; <del> devices.testDevice = { </del> <ins> devices.${testName} = { </ins> id = testId; }; folders.testFolder = { path = "/tmp/test"; <del> devices = [ "testDevice" ]; </del> <ins> devices = [ testName ]; </ins> }; extraOptions.gui.user = "guiUser"; };
Change:
Installing causes large dependencies such as and to be pulled in at run-time Steps to reproduce the behavior: that some of the large dependencies such as are pulled in. I'd expect and to be build-time dependencies, and as such shouldn't be needed at run-time The additional dependencies are being pulled in due to , which itself should be a build dependency. FWIW, declares as a make* dependency Please run and paste the result.
not the maintainer for -qt ( is), but I took a quick look at it nevertheless and it seems that gets to in the invocation for even if it is moved to . Unfortunately I don't know enough about the Qt ecosystem to tell why this is the case.
I think that the issue lies in qttools itself, for some reason after , qttools depends on clang and llvm at runtime This doesn't seem to be the case on and
qttools provides a qt plugin so wrapQtAppsHook will add to ‘QTPLUGINPATH’ automaticallyUnfortunately, the packaging of qttools is not subdivided, all output is almost in one packagethis leads to the addition of unnecessary runtime dependencies. ( Actually even may not be needed is required by and , lupdate seems to be just a optional feature dependency on clangbut is not feasiblewe have to recompile to disable this feature Splitting into multiple packages should be a better solutionqdoc/lupdate are often used to generate documentation/translations, almost no packages runtime depends on them This pr should solve the problem of qalculate-qt but this may cause some packages fail to find lupdate. it‘s not an elegant solution
I think it's easier to add a flag to qttools, and only use that variant for building the docs.
should be , set can prevent qttools from being recognized as a runtime dependency the pull request to disable clang-based c++ parser by default
If that helps, maybe is no longer necessary?
For this issue, yes But not sure if there is a package need qttools (qt plugin ) as runtime dependency
I checked all packages that depends on qttools, and found that most if not all of them have a runtime reference on qttools due to it being in . So this problem is actually widespread, we can have the workaround in for now.

Discussion:
--replace '$QT_INSTALL_DOCS' "${qtbase}/share/doc" done ''; <del> nativeBuildInputs = [ qttools ]; </del> <ins> nativeBuildInputs = [ (qttools.override { withClang = true; }) ]; </ins> qtInputs = [ qtdeclarative ]; cmakeFlags = [ "-DCMAKE_MESSAGE_LOG_LEVEL=STATUS"

, lib , qtbase , qtdeclarative <del> , llvmPackages </del> , cups <ins> , llvmPackages # clang-based c++ parser for qdoc and lupdate , withClang ? false </ins> }: qtModule { pname = "qttools"; <del> buildInputs = [ </del> <ins> buildInputs = lib.optionals withClang [ </ins> llvmPackages.libclang llvmPackages.llvm ];

nativeBuildInputs = [ cmake pkg-config <del> qttools </del> <ins> (qttools.override { withClang = true; }) </ins> wrapQtAppsHook python3 ninja
Change:
Failure happens locally as well when trying to build spotdl on the nixos-23.05 branch. this the tail of the log: The last line is apparently unrelated: (maintainer) (recent bumps)
This test doesn't fail if spotdl is built using version from this nixpkgs commit , I'm not sure if this is an upstream issue with spotdl while using newer yt-dlp versions (newer than ).

Discussion:
}; in python.pkgs.buildPythonApplication rec { pname = "spotdl"; <del> version = "4.1.10"; </del> <ins> version = "4.1.11"; </ins> format = "pyproject";

owner = "spotDL"; repo = "spotify-downloader"; rev = "refs/tags/v${version}"; <del> hash = "sha256-SmyUoMOlBJZTJH19NwTKbz/vo7Oh4tGHCQrW5DVZQWQ="; </del> <ins> hash = "sha256-I/53JapzTo6VXss82/F0qO/Etwd4i6ZP9FPjaFRHwV0="; </ins> }; nativeBuildInputs = with python.pkgs; [

"test_album_from_string" "test_album_from_url" "test_album_length" <del> "test_artist_from_url" </del> "test_artist_from_string" <ins> "test_artist_from_url" </ins> "test_convert" "test_download_ffmpeg" "test_download_song"

"test_preload_song" "test_song_from_search_term" "test_song_from_url" <ins> "test_yt_search" </ins> ]; makeWrapperArgs = [
Change:
Failure happens locally as well when trying to build spotdl on the nixos-23.05 branch. this the tail of the log: The last line is apparently unrelated: (maintainer) (recent bumps)
This test doesn't fail if spotdl is built using version from this nixpkgs commit , I'm not sure if this is an upstream issue with spotdl while using newer yt-dlp versions (newer than ).

Discussion:
{ lib , buildPythonPackage , fetchFromGitHub <ins> , flit-core </ins> , freezegun <del> , hatchling </del> , pytest , pytestCheckHook , pythonOlder

buildPythonPackage rec { pname = "pytest-freezer"; <del> version = "0.4.6"; </del> <ins> version = "0.4.8"; </ins> format = "pyproject"; disabled = pythonOlder "3.6";

owner = "pytest-dev"; repo = pname; rev = "refs/tags/${version}"; <del> hash = "sha256-0JZv6MavRceAV+ZOetCVxJEyttd5W3PCts6Fz2KQsh0="; </del> <ins> hash = "sha256-Eak6LNoyu2wvZbPaBBUO0UkyB9vni8YbsADGK0as7Cg="; </ins> }; nativeBuildInputs = [ <del> hatchling </del> <ins> flit-core </ins> ]; buildInputs = [
Change:
I cannot install on my Apple M1 PowerBook any more (potentially due to ?) I'm tracking (commit ) Steps to reproduce the behavior: Here's the output of
I'm afraid I don't have a Mac around to test with, but from glancing at the build log it appears the problem may go away if you remove from in the jsonnet derivation, or make it conditional on stdenv.hostPlatform.isStatic as suggested in .
I can confirm this issue. We worked around this in our own overlay by reverting to the last known (to us) NixPkgs version for the Jsonnet package only (i.e. we overlayed the derivation with one that is basically . No idea what exactly causes the problem, though.
didn't fix this, I still can't build jsonnet on Darwin.
This is fixed in , PTAL.

Discussion:
stdenv.mkDerivation rec { pname = "jsonnet"; version = "0.20.0"; <del> outputs = ["out" "doc"]; </del> <ins> outputs = [ "out" "doc" ]; </ins> src = fetchFromGitHub { rev = "v${version}";

nativeBuildInputs = [ jekyll cmake ]; buildInputs = [ gtest ]; <del> cmakeFlags = ["-DBUILD_STATIC_LIBS=ON" "-DUSE_SYSTEM_GTEST=ON" ]; </del> <ins> cmakeFlags = [ "-DUSE_SYSTEM_GTEST=ON" "-DBUILD_STATIC_LIBS=${if stdenv.hostPlatform.isStatic then "ON" else "OFF"}" "-DBUILD_SHARED_BINARIES=${if stdenv.hostPlatform.isStatic then "OFF" else "ON"}" ]; # https://github.com/google/jsonnet/issues/778 patches = [ ./fix-cpp-unresolved-symbols.patch ]; </ins> enableParallelBuilding = true;

<ins> diff --git a/cpp/CMakeLists.txt b/cpp/CMakeLists.txt index 3a52458..872e6c6 100644 --- a/cpp/CMakeLists.txt +++ b/cpp/CMakeLists.txt @@ -10,6 +10,7 @@ set(LIBJSONNETPP_SOURCE add_library(libjsonnet++ SHARED ${LIBJSONNETPP_HEADERS} ${LIBJSONNETPP_SOURCE}) add_dependencies(libjsonnet++ jsonnet) +target_link_libraries(libjsonnet++ libjsonnet) # target_link_libraries(libjsonnet libjsonnet) # CMake prepends CMAKE_SHARED_LIBRARY_PREFIX to shared libraries, so without </ins>
Change:
I cannot install on my Apple M1 PowerBook any more (potentially due to ?) I'm tracking (commit ) Steps to reproduce the behavior: Here's the output of
I'm afraid I don't have a Mac around to test with, but from glancing at the build log it appears the problem may go away if you remove from in the jsonnet derivation, or make it conditional on stdenv.hostPlatform.isStatic as suggested in .
I can confirm this issue. We worked around this in our own overlay by reverting to the last known (to us) NixPkgs version for the Jsonnet package only (i.e. we overlayed the derivation with one that is basically . No idea what exactly causes the problem, though.
didn't fix this, I still can't build jsonnet on Darwin.
This is fixed in , PTAL.

Discussion:
cmakeFlags = [ "-DUSE_SYSTEM_GTEST=ON" "-DBUILD_STATIC_LIBS=${if stdenv.hostPlatform.isStatic then "ON" else "OFF"}" <ins> ] ++ lib.optionals (!stdenv.isDarwin) [ </ins> "-DBUILD_SHARED_BINARIES=${if stdenv.hostPlatform.isStatic then "OFF" else "ON"}" ];
Change:
provides incorrect values to Qt bins / libs etc, when gives correct values. Steps to reproduce the behavior: , notice that paths are inside , notice that paths are inside A step 3 for to also use . qmake qmake6 This causes issues as it is expected for Qt tooling to be available in the folder, however the path that points to is missing tooling compared to . eg is available under with but it is not available under the folder provided by . qmake qmake6 (sorry don't know who the maintainers are)
This should probably also be done for qmake6:

Discussion:
extraOutputsToInstall = [ "out" "dev" ]; postBuild = '' <del> rm "$out/bin/qmake" cp "${qtbase}/bin/qmake" "$out/bin" </del> <ins> for f in qmake qmake6; do rm "$out/bin/$f" cp "${qtbase}/bin/$f" "$out/bin" done </ins> cat >"$out/bin/qt.conf" <<EOF [Paths] Prefix = $out
Change:
Project description Output management utility for sway and Hyprland. Metadata homepage URL: https://nwg- source URL: license: mit platforms: linux

Discussion:
<ins> { lib , fetchFromGitHub , atk , gdk-pixbuf , gobject-introspection , gtk-layer-shell , gtk3 , pango , python310Packages , wrapGAppsHook }: python310Packages.buildPythonApplication rec { pname = "nwg-displays"; version = "0.3.7"; src = fetchFromGitHub { owner = "nwg-piotr"; repo = "nwg-displays"; rev = "v${version}"; hash = "sha256-Y405ZeOSpc1aPKEzFdvlgJgpGAi9HUR+Hvx63uYdp88="; }; nativeBuildInputs = [ gobject-introspection wrapGAppsHook ]; buildInputs = [ gtk3 ]; propagatedBuildInputs = [ atk gdk-pixbuf gtk-layer-shell pango python310Packages.gst-python python310Packages.i3ipc python310Packages.pygobject3 ]; dontWrapGApps = true; preFixup = '' makeWrapperArgs+=("''${gappsWrapperArgs[@]}"); ''; # Upstream has no tests doCheck = false; meta = { homepage = "https://github.com/nwg-piotr/nwg-displays"; description = "Output management utility for Sway and Hyprland"; license = lib.licenses.mit; platforms = lib.platforms.linux; maintainers = [ ]; }; } </ins>

nwg-bar = callPackage ../applications/misc/nwg-bar { }; <ins> nwg-displays = callPackage ../applications/misc/nwg-displays { }; </ins> nwg-dock = callPackage ../applications/misc/nwg-dock { }; nwg-dock-hyprland = callPackage ../applications/misc/nwg-dock-hyprland { };
Change:
Many cmp-* plugins have dependencies like curl, fish, tmux etc. But those are not plugins. In result those programs are to nvim runtimepath. Looks like it was introduced by Steps to reproduce the behavior: package e.g. -pack-dir now contains curl and git directories. Binaries should not be linked to runtimepath. Paths to binaries should be replaced in plugin source code or to nvim's PATH (does it work with propagatedBuildInputs?). If applicable, add screenshots to help explain your problem. 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.

Discussion:
}; cmp-fish = super.cmp-fish.overrideAttrs { <del> dependencies = with self; [ nvim-cmp fish ]; </del> <ins> dependencies = with self; [ nvim-cmp ]; </ins> }; cmp-fuzzy-buffer = super.cmp-fuzzy-buffer.overrideAttrs {

}; cmp-git = super.cmp-git.overrideAttrs { <del> dependencies = with self; [ nvim-cmp curl git ]; </del> <ins> dependencies = with self; [ nvim-cmp ]; </ins> }; cmp-greek = super.cmp-greek.overrideAttrs {

}; cmp-npm = super.cmp-npm.overrideAttrs { <del> dependencies = with self; [ nvim-cmp nodejs plenary-nvim ]; </del> <ins> dependencies = with self; [ nvim-cmp plenary-nvim ]; </ins> }; cmp-nvim-lsp-signature-help = super.cmp-nvim-lsp-signature-help.overrideAttrs {

}; cmp-pandoc-nvim = super.cmp-pandoc-nvim.overrideAttrs { <del> dependencies = with self; [ nvim-cmp pandoc plenary-nvim ]; </del> <ins> dependencies = with self; [ nvim-cmp plenary-nvim ]; </ins> }; cmp-rg = super.cmp-rg.overrideAttrs { <del> dependencies = with self; [ nvim-cmp ripgrep ]; </del> <ins> dependencies = with self; [ nvim-cmp ]; </ins> }; cmp-snippy = super.cmp-snippy.overrideAttrs {
Change:
The systemd initrd (or stage1) does not work with a volatile root when there are 9p mounts present. A result of this is that VMs built with nixos/qemu-vm do not work when disabling the (and thus running on a tmpfs) and using the systemd initrd. Create a test that sets these options: The test should work just like the test works in who has identified the root cause (an ordering issue where the tmpfs is mounted before the 9p infrastructure is up) and found a hack around this behaviour.
I this to the board because it will require a test when it is fixed.
As a side note, we should consider using to implement volatile root with systemd stage 1.
As far as I can tell we could only do this if we mounted under .
So this works probabilistically. Sometimes it succeeds, and sometimes it fails with for one of the 9p file systems.
Ok this patch seems to fix it Which begs the question... why does it ever work, with or without volatile root? EDIT: Oh I bet it's a race condition caused by not depending on . In order for to appear, virtio modules need to have already been loaded. So, because gets mounted first, and needs to wait for to appear, that means virtio modules are definitely already loaded before any children of are mounted. And indeed, switching from to just does the trick as well.

Discussion:
"kmod-static-nodes.service" "local-fs-pre.target" "local-fs.target" <ins> "modprobe@.service" </ins> "multi-user.target" "paths.target" "poweroff.target"

value.fsType = "9p"; value.neededForBoot = true; value.options = <del> [ "trans=virtio" "version=9p2000.L"  "msize=${toString cfg.msize}" ] </del> <ins> [ "trans=virtio" "version=9p2000.L"  "msize=${toString cfg.msize}" "x-systemd.requires=modprobe@9pnet_virtio.service" ] </ins> ++ lib.optional (tag == "nix-store") "cache=loose"; }; in lib.mkMerge [
Change:
Package name: zoom-us Latest released version: 5.15.2.4260 <!-- Search your package here: --- Current version on the unstable channel: 5.15.0.4063 Current version on the stable/release channel: 5.14.7.2928 <!-- 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.

Discussion:
# and often with different versions.  We write them on three lines # like this (rather than using {}) so that the updater script can # find where to edit them. <del> versions.aarch64-darwin = "5.14.10.19202"; versions.x86_64-darwin = "5.14.10.19202"; versions.x86_64-linux = "5.15.0.4063"; </del> <ins> versions.aarch64-darwin = "5.15.2.19786"; versions.x86_64-darwin = "5.15.2.19786"; versions.x86_64-linux = "5.15.2.4260"; </ins> srcs = { aarch64-darwin = fetchurl { url = "https://zoom.us/client/${versions.aarch64-darwin}/zoomusInstallerFull.pkg?archType=arm64"; name = "zoomusInstallerFull.pkg"; <del> hash = "sha256-MK6xUkS+nX7SjIieduMhhFNqEUVdc89aPiCvHI2pjDQ="; </del> <ins> hash = "sha256-vERhyaNVxam6ypi9nU2t6RfBZgtzD6YECkSrxkxl/4E="; </ins> }; x86_64-darwin = fetchurl { url = "https://zoom.us/client/${versions.x86_64-darwin}/zoomusInstallerFull.pkg"; <del> hash = "sha256-JJ6nZ8WnTF8X8R0gIlFtsTbpdHhv65J5kWts+H3QDoM="; </del> <ins> hash = "sha256-Yx5seUks6s+NEBIxgltUQiNU3tjWpmNKMJwgAj9izh4="; </ins> }; x86_64-linux = fetchurl { url = "https://zoom.us/client/${versions.x86_64-linux}/zoom_x86_64.pkg.tar.xz"; <del> hash = "sha256-DhP6LZt/G3K9YDs7iXABsJMuhpzITP4aJ0PWXrFAL3I="; </del> <ins> hash = "sha256-R6M180Gcqu4yZC+CtWnixSkjPe8CvgoTPWSz7B6ZAlE="; </ins> }; };
Change:
Project description homebrew provides an evince installation method on macos: . Is this possible for nix? homepage URL: source URL: license: gpl2+ platforms: darwin
Are you interested in this?
Not sure if I'm the right person to tag. Don't think I've ever been involved in anything related
Seems to build fine at least, just needs to have expanded to . !
thanks very much :)

Discussion:
''; license = licenses.gpl2Plus; <del> platforms = platforms.linux; </del> <ins> platforms = platforms.unix; </ins> maintainers = teams.gnome.members ++ teams.pantheon.members; }; }
Change:
Package name: opentabletdriver Latest released version: 0.6.2 Current version on the unstable channel: 0.6.1 Current version on the stable/release channel: 0.6.0.4 Notify maintainers Note for maintainers: Please tag this issue in your PR.

Discussion:
buildDotnetModule rec { pname = "OpenTabletDriver"; <del> version = "0.6.1"; </del> <ins> version = "0.6.2.0"; </ins> src = fetchFromGitHub { owner = "OpenTabletDriver"; repo = "OpenTabletDriver"; rev = "v${version}"; <del> sha256 = "sha256-9C6rtq+1WTinlAs0SJs1/J1QRnKm5pGNDSbLQ0kRUXY="; </del> <ins> sha256 = "sha256-D1/DGvSBgG8wZMmyJ7QAHDcsMjC1YgSpxmSYzs6ntJg="; </ins> }; debPkg = fetchurl {
Change:
branch to nixos-unstable to your with
Bisect has identified (specifically ) as the source of this failure in nixpkgs, cc See also upstream issue
If you're using a flake, this is how I was able to mitigate this until it's fixed. I rolled back the changes from in a branch on my fork, and used it as an overlay for the affected packages like this: This is how you would add them to your overlay: Ofc, depending on how you do stuff, you'll have to fiddle with it a bit to get it to work. I found this helpful:
The fix is now on the nixos-unstable branch, but I still cannot build my system after updating, with the same build failure for opencolorio. Is this expected?
Probably not, since and both build on Hydra.
Oh thank you, this is very bizarre. I will ask on the forum what's going on
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Discussion:
"-DMZ_OPENSSL=ON" "-DMZ_BUILD_TESTS=${if finalAttrs.doCheck then "ON" else "OFF"}" "-DMZ_BUILD_UNIT_TESTS=${if finalAttrs.doCheck then "ON" else "OFF"}" <ins> "-DMZ_LIB_SUFFIX='-ng'" </ins> ] ++ lib.optionals stdenv.isDarwin [ # missing header file "-DMZ_LIBCOMP=OFF"

url = "https://github.com/AcademySoftwareFoundation/OpenColorIO/commit/332462e7f5051b7e26ee3d8c22890cd5e71e7c30.patch"; sha256 = "sha256-7xHALhnOkKszgFBgPIbiZQaORnEJ+1M6RyoZdFgjElM="; }) <ins> (fetchpatch { name = "minizip-ng-4.patch"; url = "https://gitlab.archlinux.org/archlinux/packaging/packages/opencolorio/-/raw/5fc40f42f5c05d905793610c37b46ca3649245f3/minizip-ng-4.patch"; hash = "sha256-B+dbBVRn0EuGtJaWxz5ah9el0RN7cLb81hgqnKkvhew="; }) </ins> ]; postPatch = lib.optionalString stdenv.isDarwin ''

"-DOCIO_INSTALL_EXT_PACKAGES=NONE" # GPU test fails with: freeglut (GPU tests): failed to open display '' "-DOCIO_BUILD_GPU_TESTS=OFF" <ins> "-Dminizip-ng_INCLUDE_DIR=${minizip-ng}/include" </ins> ] ++ lib.optional (!pythonBindings) "-DOCIO_BUILD_PYTHON=OFF" ++ lib.optional (!buildApps) "-DOCIO_BUILD_APPS=OFF";
Change:
Package name: staruml Latest released version: 4.1.6 <!-- Search your package here: --- Current version on the unstable channel: 4.1.6 Current version on the stable/release channel: 4.1.6 <!-- 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. --No maintainers. Last update in version was automated by and last major package change by Note for maintainers: Please tag this issue in your PR.

Discussion:
, atk, at-spi2-atk, dbus , gdk-pixbuf, pango, cairo , expat, libdrm, mesa <del> , alsa-lib, at-spi2-core, cups }: </del> <ins> , alsa-lib, at-spi2-core, cups , libxkbcommon }: </ins> let LD_LIBRARY_PATH = lib.makeLibraryPath [

xorg.libX11 xorg.libxcb xorg.libXcomposite xorg.libXcursor xorg.libXext xorg.libXfixes xorg.libXi xorg.libXrender xorg.libXtst <del> nss nspr atk at-spi2-atk dbus gdk-pixbuf pango cairo </del> <ins> xorg.libxshmfence libxkbcommon nss nspr atk at-spi2-atk dbus gdk-pixbuf pango cairo </ins> xorg.libXrandr expat libdrm mesa alsa-lib at-spi2-core cups ]; in stdenv.mkDerivation rec { <del> version = "4.1.6"; </del> <ins> version = "5.1.0"; </ins> pname = "staruml"; src = fetchurl { <del> url = "https://staruml.io/download/releases-v4/StarUML_${version}_amd64.deb"; sha256 = "sha256-CUOdpR8RExMLeOX8469egENotMNuPU4z8S1IGqA21z0="; </del> <ins> url = "https://staruml-7a0.kxcdn.com/releases-v5/StarUML_${version}_amd64.deb"; sha256 = "sha256-da1mY3OW24g6Ix0L57CBPbaMeSLzhOOjoBsyZszmNOc="; </ins> }; nativeBuildInputs = [ wrapGAppsHook dpkg ];