jiebi/CodeConvo huggingface dataset:
Change:
A link, from the manual, that was working in the past day is now broken. to: for "Examples of real-world NixOS configuration files can be found at" on the following link, which is:
I have no idea where that repository went, so I propose we just delete that reference.
might be a useful resource, if we want to link to something.
It certainly is a useful resource; it strikes me that we'd better link to something "official" or at least curated in the manual, though. Perhaps someone could take the time to find "good" repos to link to? For a newbie it'll be quite difficult to tell what's what.
That said, I don't think we need to hash out the details of a replacement to deal with this issue.
It appears to have existed up until at least a month ago:

Discussion:
# TODO add plugins having various licenses, see http://www.vamp-plugins.org/download.html <del> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo, libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate, libsndfile, makeWrapper, pulseaudio, qt4, redland, rubberband, vampSDK </del> <ins> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo , libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate , libsndfile, makeWrapper, pkgconfig, pulseaudio, qt4, redland , rubberband, vampSDK </ins> }: <del> stdenv.mkDerivation { name = "sonic-visualiser-1.8"; </del> <ins> stdenv.mkDerivation rec { name = "sonic-visualiser-${version}"; version = "1.9"; </ins> src = fetchurl { <del> url = http://downloads.sourceforge.net/sv1/sonic-visualiser-1.8.tar.gz; sha256 = "16ik6q9n92wljvnqcv7hyzb9v3yp3ixxp6df9kasf53fii973dh7"; </del> <ins> url = "http://code.soundsoftware.ac.uk/attachments/download/194/${name}.tar.gz"; sha256 = "00igf7j6s8xfyxnlkbqma0yby9pknxqzy8cmh0aw95ix80cw56fq"; </ins> }; buildInputs = [ libsndfile qt4 fftw /* should be fftw3f ??*/ bzip2 librdf rubberband libsamplerate vampSDK alsaLib librdf_raptor librdf_rasqal redland <ins> pkgconfig </ins> # optional jackaudio # portaudio

description = "View and analyse contents of music audio files"; homepage = http://www.sonicvisualiser.org/; license = "GPLv2"; <del> maintainers = [ stdenv.lib.maintainers.marcweber stdenv.lib.maintainers.goibhniu ]; </del> <ins> maintainers = [ stdenv.lib.maintainers.marcweber stdenv.lib.maintainers.goibhniu ]; </ins> platforms = stdenv.lib.platforms.linux; }; }
Change:
The output from building the target on macOS: Note that if I hack the patch file associated with the derivation to use a extension, it builds fine.
The should be changed to a placeholder and then the placeholder should be replaced with

Discussion:
-                "libcrypto.dylib"                ;; default system libcrypto, which may have insufficient crypto -                "/usr/lib/libcrypto.dylib")) -  (:cygwin (:or "cygcrypto-1.1.dll" "cygcrypto-1.0.0.dll"))) <del> +  (t "@openssl@/lib/libcrypto.so")) </del> <ins> +  (t "@libcrypto@")) </ins> (cffi:define-foreign-library libssl -  (:windows (:or #+(and windows x86-64) "libssl-1_1-x64.dll"

-                                  "libssl.so")) -  (:cygwin (:or "cygssl-1.1.dll" "cygssl-1.0.0.dll")) -  (t (:default "libssl3"))) <del> +  (t "@openssl@/lib/libssl.so")) </del> <ins> +  (t "@libssl@")) </ins> (unless (member :cl+ssl-foreign-libs-already-loaded *features*)

{ lib, stdenv, callPackage, fetchFromGitHub, runCommandLocal, makeWrapper, substituteAll <del> , sbcl, bash, which, perl, nettools </del> <ins> , sbcl, bash, which, perl, hostname </ins> , openssl, glucose, minisat, abc-verifier, z3, python , certifyBooks ? true } @ args:

patches = [(substituteAll { src = ./0001-Fix-some-paths-for-Nix-build.patch; libipasir = "${libipasir}/lib/${libipasir.libname}"; <del> openssl = openssl.out; </del> <ins> libssl = "${openssl.out}/lib/libssl${stdenv.hostPlatform.extensions.sharedLibrary}"; libcrypto = "${openssl.out}/lib/libcrypto${stdenv.hostPlatform.extensions.sharedLibrary}"; </ins> })]; buildInputs = [

sbcl ] ++ lib.optionals certifyBooks [ # To build community books, we need Perl and a couple of utilities: <del> which perl nettools makeWrapper </del> <ins> which perl hostname makeWrapper </ins> # Some of the books require one or more of these external tools: openssl.out glucose minisat abc-verifier libipasir z3 (python.withPackages (ps: [ ps.z3 ]))
Change:
I run the command I expect it to give me a fortune cookie However, I get this error ! Steps to reproduce the behavior: ?? Maintainer information:
Fix is to add in

Discussion:
'') ]; meta = with lib; { <ins> mainProgram = "fortune"; </ins> description = "A program that displays a pseudorandom message from a database of quotations"; license = licenses.bsdOriginal; platforms = platforms.unix;
Change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: puppet-lint <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2.3.6 desired version: 2.5.2 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
GEM remote: https://rubygems.org/ specs: <del> puppet-lint (2.3.6) </del> <ins> puppet-lint (2.5.2) </ins> PLATFORMS ruby

puppet-lint BUNDLED WITH <del> 2.1.4 </del> <ins> 2.2.24 </ins>

{ puppet-lint = { <ins> groups = ["default"]; platforms = []; </ins> source = { remotes = ["https://rubygems.org"]; <del> sha256 = "1wyk2l440d96ps3x127r52n51kqpqi2nzb3xlg92qn6aksqhnkis"; </del> <ins> sha256 = "1rcj3cb6lf90g6vvhh3c9p8yn7pgibglf9k5878bzd6pn5ag0h9v"; </ins> type = "gem"; }; <del> version = "2.3.6"; </del> <ins> version = "2.5.2"; </ins> }; }
Change:
The new change to yubikey-agent breaks yubikey-agent on NixOS. The upstream library used to be and switched to This new repo is a copy of the pinentry code of gopass, but without the commit history. Unfortunately the behavior of finding the pinentry binary changed here from just returning pinentry of the variable to actually using to . returns the (hard-coded) path to the relative pinentry binary in the gnupg folder. Since there is none (and the choice of pinentry flavor is left up to the gpg-agent so it didn't concern anyone), it now fails. This is a known problem of gpgconf, and something that is probably not easily fixed. For reference, here are the somewhat related issues: , . Steps to reproduce the behavior: yubikey-agent () yubikey-agent It returns Yubikey-agent should start. I submitted an upstream PR with a small fix that allows the upstream library to fall back to the PATH pinentry when the path returned by gpgconf doesn't exist. See . If agrees with the changes, and yubikey-agent uses the new version of the library, it should work again. and Please run and paste the result. Maintainer information:
Pinentry already approved the PR. A PR for an updated yubikey-agent is underway. For anyone interested in testing this, here is the snipped I use in my to override the yubikey-agent version with the commit of the PR: and yes, it works ;-) Edit 2021-11-13: Changed Rev and sha256 to reflect changes in Yubikey PR
Thanks for the clear bug report, I don't think there's much we can do until FiloSottile/yubikey-agent is merged, and its maintainer can take months to approve PRs.
thanks for looking at the code! I updated my comment and I agree, now we wait.
Great, the upstream PR has been merged, now we just need to await a new version tag

Discussion:
buildGoModule rec { pname = "yubikey-agent"; <del> version = "0.1.5"; </del> <ins> version = "unstable-2022-03-17"; </ins> src = fetchFromGitHub { owner = "FiloSottile"; <del> repo = pname; rev = "v${version}"; sha256 = "14s61jgcmpqh70jz0krrai8xg0xqhwmillxkij50vbsagpxjssk6"; </del> <ins> repo = "yubikey-agent"; rev = "205a7ef2554625c7494038600d963123d6311873"; sha256 = "sha256-wJpN63KY5scmez6yYFsIr3JLEUB+YSl/XvoatIIeRI0="; </ins> }; buildInputs =

substituteInPlace main.go --replace 'notify-send' ${libnotify}/bin/notify-send ''; <del> vendorSha256 = "1v4ccn7ysh8ax1nkf1v9fcgsdnz6zjyh6j6ivyljyfvma1lmcrmk"; </del> <ins> vendorSha256 = "sha256-SnjbkDPVjAnCbM2nLqBsuaPZwOmvDTKiUbi/93BlWVQ="; </ins> doCheck = false;
Change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: calibre <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 5.30.0 desired version: 5.31.1 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: The URL for returns 404 (). It seems like Debian removed the 5.30.0 URL and now only has those for 5.31.1. Please tag this issue in your PR.

Discussion:
mkDerivation rec { pname = "calibre"; <del> version = "5.30.0"; </del> <ins> version = "5.31.1"; </ins> src = fetchurl { url = "https://download.calibre-ebook.com/${version}/${pname}-${version}.tar.xz"; <del> sha256 = "058dqqxhc3pl4is1idlnc3pz80k4r681d5aj4a26v9acp8j7zy4f"; </del> <ins> sha256 = "sha256-3LGEWuHms54ji9GWSyLl8cFWIRBqHY1Jf/CNPJOywrU="; </ins> }; <del> # https://sources.debian.org/patches/calibre/5.30.0+dfsg-1 </del> <ins> # https://sources.debian.org/patches/calibre/5.31.1+dfsg-1 </ins> patches = [ #  allow for plugin update check, but no calibre version check (fetchpatch { <del> name = "0001_only_plugin_update.patch"; url = "https://sources.debian.org/data/main/c/calibre/${version}%2Bdfsg-1/debian/patches/0001-only-plugin-update.patch"; sha256 = "sha256-aGT8rJ/eQKAkmyHBWdY0ouZuWvDwtLVJU5xY6d3hY3k="; </del> <ins> name = "0001-only-plugin-update.patch"; url = "https://raw.githubusercontent.com/debian-calibre/calibre/debian/${version}%2Bdfsg-1/debian/patches/0001-only-plugin-update.patch"; sha256 = "sha256-dLzO1TWP7Q4nw2a3oN7qlhGCmcA0NKJrZidUnD6hUMA="; </ins> }) ] ++ lib.optional (!unrarSupport) ./dont_build_unrar_plugin.patch;
Change:
It looks like the upstream repo was retagged. Doesn't really affect anyone until the package is rebuilt by hydra. python3Packages.iso3166 source is retrieved. I needed to rebuild some packages from source, and this is one of many that failed to build Please run and paste the result. Maintainer information:

Discussion:
owner = "deactivated"; repo = "python-iso3166"; rev = version; <del> sha256 = "0zs9za9dr2nl5srxir08yibmp6nffcapmzala0fgh8ny7y6rafrx"; </del> <ins> sha256 = "sha256-/y7c2qSA6+WKUP9YTSaMBjBxtqAuF4nB3MKvL5P6vL0="; </ins> }; checkInputs = [
Change:
We currently use version and export it to The help page suggests there is version 201 and the file name should be : () The change will also likely need a hwdb file according to: This is apparently required to support cameras that use SCSI tunneling support: cc (maintainer) ( the udev file)
For reference Fedora

Discussion:
buildPackages.libgphoto2; in '' <del> mkdir -p $out/lib/udev/rules.d </del> <ins> mkdir -p $out/lib/udev/{rules.d,hwdb.d} </ins> ${executablePrefix}/lib/libgphoto2/print-camera-list  <del> udev-rules version 175 group camera  >$out/lib/udev/rules.d/40-gphoto2.rules </del> <ins> udev-rules version 201 group camera  >$out/lib/udev/rules.d/40-libgphoto2.rules ${executablePrefix}/lib/libgphoto2/print-camera-list  hwdb version 201 group camera  >$out/lib/udev/hwdb.d/20-gphoto.hwdb </ins> ''; meta = {
Change:
postcss-cli fails to start. Steps to reproduce the behavior: No error. points to . Please run and paste the result. Maintainer information:
I spent quite some time trying to figure this out but I just don't understand well enough to fix this, sorry.
does not support , see
ref Maybe since then moved from something else to esm? Not sure.
Could this actually be because (the bin) lists (the lib) as a peerDependency since version 8 Whenever node2nix runs, it doesn't check for peer dependencies so (the lib) is not included. According to the node- on master, the postcss-cli does not have postcss in its dependencies.
Nah, I have installed at the path that is to in the bin wrapper and it still does not work.
Ha, they did move to esm pretty recently:
I guess replace the wrapping with a symbolic link post install and it should work?
Thanks for the awesome insight. I'll try this tomorrow if I have some time.
I created to fix this.

Discussion:
wrapProgram "$out/bin/postcss"  --prefix NODE_PATH : ${self.postcss}/lib/node_modules  --prefix NODE_PATH : ${self.autoprefixer}/lib/node_modules <ins> ln -s '${self.postcss}/lib/node_modules/postcss' "$out/lib/node_modules/postcss" </ins> ''; passthru.tests = { simple-execution = pkgs.callPackage ./package-tests/postcss-cli.nix { inherit (self) postcss-cli; }; }; <del> meta.mainProgram = "postcss"; </del> <ins> meta = { mainProgram = "postcss"; maintainers = with lib.maintainers; [ Luflosi ]; }; </ins> }; prisma = super.prisma.override rec {
Change:
Roundcube with the plugin enabled fails to start due to an error caused by . This seems to be caused by . Enable the module with and . Roundcube with the plugin enabled should start. and are somewhat related to this issue. Maintainer information:
Sorry, but I don't have a roundcube instance anymore and I don't have time to dig, so I'm going to step out of the role of maintainer of this package.
Created a that will resolve this

Discussion:
roundcubePlugin rec { pname = "carddav"; <del> version = "3.0.3"; </del> <ins> version = "4.3.0"; </ins> src = fetchzip { <del> url = "https://github.com/blind-coder/rcmcarddav/releases/download/v${version}/carddav-${version}.tar.bz2"; sha256 = "0scqxqfwv9r4ggaammmjp51mj50qc5p4jmjliwjvcwyjr36wjq3z"; </del> <ins> url = "https://github.com/mstilkerich/rcmcarddav/releases/download/v${version}/carddav-v${version}.tar.gz"; sha256 = "1jk1whx155svfalf1kq8vavn7jsswmzx4ax5zbj01783rqyxkkd5"; </ins> }; }
Change:
Project description It's a colourscheme that has an implementation for gtk, it's pretty! We have gtk themes like on here, but wasn't sure if the process is any different when it comes to packaging this instead. Metadata homepage URL: source URL:

Discussion:
<ins> { stdenv , fetchFromGitHub , lib , gnome-themes-extra , gtk-engine-murrine , gtk_engines }: stdenv.mkDerivation rec { pname = "rose-pine-gtk-theme"; version = "unstable-2021-02-22"; src = fetchFromGitHub { owner = "rose-pine"; repo = "gtk"; rev = "9cd2dd449f911973ec549231a57a070d256da9fd"; sha256 = "0lqx8dmv754ix3xbg7h440x964n0bg4lb06vbzvsydnbx79h7lvy"; }; buildInputs = [ gnome-themes-extra # adwaita engine for Gtk2 gtk_engines # pixmap engine for Gtk2 ]; propagatedUserEnvPkgs = [ gtk-engine-murrine # murrine engine for Gtk2 ]; installPhase = '' runHook preInstall mkdir -p $out/share/themes cp -a Rose-Pine $out/share/themes rm $out/share/themes/*/LICENSE runHook postInstall ''; meta = with lib; { description = "Rosé Pine theme for GTK"; homepage = "https://github.com/rose-pine/gtk"; license = licenses.gpl3Only; platforms = platforms.linux; maintainers = [ maintainers.romildo ]; }; } </ins>

rime-data = callPackage ../data/misc/rime-data { }; <ins> rose-pine-gtk-theme = callPackage ../data/themes/rose-pine-gtk { }; </ins> route159 = callPackage ../data/fonts/route159 { }; sampradaya = callPackage ../data/fonts/sampradaya { };
Change:
On with , the tests fails with the following error: Steps to reproduce the behavior: -shell -p python3Packages.scikitimage The tests run without errors. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- system: host os: multi-user?: sandbox: version: channels(smaret): nixpkgs:

Discussion:
{ lib <ins> , stdenv </ins> , fetchFromGitHub , buildPythonPackage , python

# Requires network access (actually some data is loaded via `skimage._shared.testing.fetch` in the global scope, which calls `pytest.skip` when a network is unaccessible, leading to a pytest collection error). "${installedPackageRoot}/skimage/filters/rank/tests/test_rank.py" ]; <del> pytestFlagsArray = [ "${installedPackageRoot}" "--pyargs" "skimage" ] ++ builtins.map (testid: "--deselect=" + testid) [ </del> <ins> pytestFlagsArray = [ "${installedPackageRoot}" "--pyargs" "skimage" ] ++ builtins.map (testid: "--deselect=" + testid) ([ </ins> # These tests require network access "skimage/data/test_data.py::test_skin" "skimage/data/tests/test_data.py::test_skin" "skimage/io/tests/test_io.py::test_imread_http_url" "skimage/restoration/tests/test_rolling_ball.py::test_ndim" <del> ]; </del> <ins> ] ++ lib.optionals stdenv.isDarwin [ # Matplotlib tests are broken inside darwin sandbox "skimage/feature/tests/test_util.py::test_plot_matches" "skimage/filters/tests/test_thresholding.py::TestSimpleImage::test_try_all_threshold" "skimage/io/tests/test_mpl_imshow.py::" ]); </ins> # Check cythonized modules pythonImportsCheck = [
Change:
paper-icon-theme last saw an official upstream release in 2018, but there are some fixes since then which are important for rendering of symbolic icons in e.g. rhythmbox and nemo (see e.g. snwh/paper-icon-theme). it would be useful if nixpkgs could use the latest upstream commit rather than the last release. name: paper-icon-theme current version: 2018-06-24 desired version: unstable-2020-03-12 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
<del> { lib, stdenv, fetchFromGitHub, meson, ninja, gtk3, python3, gnome, gnome-icon-theme, hicolor-icon-theme }: </del> <ins> { lib, stdenv, fetchFromGitHub, meson, ninja, gtk3, gnome, gnome-icon-theme, hicolor-icon-theme, jdupes }: </ins> stdenv.mkDerivation rec { pname = "paper-icon-theme"; <del> version = "2018-06-24"; </del> <ins> version = "unstable-2020-03-12"; </ins> src = fetchFromGitHub { owner = "snwh"; repo = pname; <del> rev = "c7cd013fba06dd8fd5cdff9f885520e2923266b8"; sha256 = "0x45zkjnmbz904df63ph06npbm3phpgck4xwyymx8r8jgrfplk6v"; </del> <ins> rev = "aa3e8af7a1f0831a51fd7e638a4acb077a1e5188"; sha256 = "0x6qzch4rrc8firb1dcf926j93gpqxvd7h6dj5wwczxbvxi5bd77"; </ins> }; nativeBuildInputs = [ meson ninja gtk3 <del> python3 </del> <ins> jdupes </ins> ]; propagatedBuildInputs = [

dontDropIconThemeCache = true; <del> postPatch = '' patchShebangs meson/post_install.py ''; </del> <ins> # These fixup steps are slow and unnecessary for this package dontPatchELF = true; dontRewriteSymlinks = true; </ins> postInstall = '' # The cache for Paper-Mono-Dark is missing gtk-update-icon-cache "$out"/share/icons/Paper-Mono-Dark; <ins> # replace duplicate files with symlinks jdupes -l -r $out/share/icons </ins> ''; meta = with lib; {
Change:
Tried today to update my nixOS system, which was last updated on 27/10/2021. Now when trying to nixos-rebuild switch i get the following error: Using unstable. relevant part of setup: home.packages = with pkgs; [ (python3.withPackages (ps: with ps; [jupyter numpy pandas matplotlib])) ]; flake was updated as below: • Updated input 'nixpkgs': 'github:nixos/nixpkgs/' (2021-10-27) → 'github:nixos/nixpkgs/' (2021-11-13)
Hey, thanks for the report with the thorough explanations. This seems to be an issue with . For some reason they don't set in their call in . For the actual collision I'm afraid we can't do much about it. Users of both and might expect to find in the closure. So I'd suggest to ask home-manager to allow collisions, or move your colliding packages into . Feel free to ping me if you think there is another cause for the issue.
I've just hit this problem in a flake :
(doesn't happen on so I'm using that for now)
Reopening, as is inside Nixpkgs. I'm somewhat surprised that it doesn't .
using a file works though, so there's something different about flakes dev shells maybe ?
Are you sure that you are supplying nixos-unstable to ? I can also reproduce with nix-shell:
oh, I'm actually using a nixos-unstable channel from 2 weeks ago, you're right
That's on purpose, so we can find packaging mistakes. The version bump introduced the regression. Upstream
Proposed fix
This appears to have broken : Edit: sorry, I'll post on the PR not the issue...

Discussion:
checkInputs = [ pytest xmltodict nbconvert ipywidgets ]; propagatedBuildInputs = [ async_generator traitlets nbformat nest-asyncio jupyter-client ]; <ins> postFixup =  '' # Remove until fixed by upstream # https://github.com/jupyter/nbclient/pull/173#issuecomment-968760082 rm $out/bin/.jupyter-run-wrapped rm $out/bin/jupyter-run ''; </ins> meta = with lib; { homepage = "https://github.com/jupyter/nbclient"; description = "A client library for executing notebooks";
Change:
Not sure. Issue exists after updating unstable from to
I also got hit by this problem. This seems caused by this PR: My system builds fine with the commit just before that (), but not after () <details<summaryBuild logs</summary</details
It would be nice to reproduce it locally, to find a proper fix. are you doing anything special to install the vim plugins? Do you have your configuration somewhere online?
Sure. My config lives here: I'm configuring Neovim through the home-manager module.
thanks, I'm using home-manager too, but so far I cannot reproduce it, I'll take a look to your config
I can reproduce it, but looks like an error with you config, you are installing 2 times the same plugin, here: and here:
That was it I was able to update nixpkgs, thanks!
in your case, is the same reason? Maybe we could try to add a better error message
In my case it is And I do not see that there is anything duplicated...
I see that you are using some out of tree vim plugins (fzf-preview is not in nixpkgs). Is the nix expression with those plugins public? Maybe a copy/paste error with your plugins? Did you forget to change the name/pname attribute for one of your plugins?
fzf-preview: None of my expressions are public, because they're in a git repository with private data. But here it is: I checked that my plugins are named correctly and they are. The error: Indicates that there's something wrong with a fzf plugin, yes. But I do nothing fancy with fzf in my configuration:
I think that is caused by , fzf-vim also installs fzf in your vim plugins, you only need
you're right, that solved the issue for me! Thanks! But now it does not find - I guess this is unrelated though!
I don't think that the error you are getting is related to this
Hm,... maybe it is... it seems that fugitive cannot be found, although it is installed...

Discussion:
linkVimlPlugin = plugin: packageName: dir: '' mkdir -p $out/pack/${packageName}/${dir} <ins> if test -e "$out/pack/${packageName}/${dir}/${lib.getName plugin}"; then printf "nERROR - Duplicated vim plugin: ${lib.getName plugin}nn" exit 1 fi </ins> ln -sf ${plugin}/${rtpPath} $out/pack/${packageName}/${dir}/${lib.getName plugin} '';