jiebi/CodeConvo huggingface dataset:
Change:
The in the nixpkgs manual has this example: But it isn't clear how this is supposed to be used. suggests that the hook is self-contained in its dependency, but this example fails to build: With Give a minimal example usage of it. <!-- 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]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

Discussion:
name = "something-hook"; propagatedBuildInputs = [ pkgs.commandsomething ]; depsTargetTargetPropagated = [ pkgs.libsomething ]; <del> } ./script.sh </del> <ins> } ./script.sh; </ins> ``` ### setup hook that depends on the hello package and runs hello and @shell@ is substituted with path to bash {#sec-pkgs.makeSetupHook-usage-example} ```nix <del> pkgs.makeSetupHook { </del> <ins> pkgs.makeSetupHook { </ins> name = "run-hello-hook"; <del> propagatedBuildInputs = [ pkgs.hello ]; substitutions = { shell = "${pkgs.bash}/bin/bash"; }; passthru.tests.greeting = callPackage ./test { }; meta.platforms = lib.platforms.linux; } (writeScript "run-hello-hook.sh" '' #!@shell@ hello '') </del> <ins> # Put dependencies here if they have hooks or necessary dependencies propagated # otherwise prefer direct paths to executables. propagatedBuildInputs = [ pkgs.hello pkgs.cowsay ]; substitutions = { shell = "${pkgs.bash}/bin/bash"; cowsay = "${pkgs.cowsay}/bin/cowsay"; }; } ( writeScript "run-hello-hook.sh" '' #!@shell@ # the direct path to the executable has to be here because # this will be run when the file is sourced # at which point '$PATH' has not yet been populated with inputs @cowsay@ cow _printHelloHook() { hello } preConfigureHooks+=(_printHelloHook) '' ); </ins> ``` ## Attributes {#sec-pkgs.makeSetupHook-attributes}
Change:
Steps to reproduce the behavior: pkgs.transmission to your environment.systemPackages (or use = true;) build will fail when trying to download a file that does not exist That does not seem to exist (I think, sorry for the @ otherwise) <!-- 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:
patches = [ # fix build with openssl 3.0 <del> (fetchurl { url = "https://gitweb.gentoo.org/repo/gentoo.git/plain/net-p2p/transmission/files/transmission-3.00-openssl-3.patch"; hash = "sha256-peVrkGck8AfbC9uYNfv1CIu1alIewpca7A6kRXjVlVs="; }) </del> <ins> ./transmission-3.00-openssl-3.patch </ins> ]; outputs = [ "out" "apparmor" ];

<ins> From 6ee128b95bacaff20746538dc97c2b8e2b9fcc29 Mon Sep 17 00:00:00 2001 From: Mike Gilbert <floppym@gentoo.org> Date: Sun, 15 May 2022 10:54:38 -0400 Subject: [PATCH] openssl: load "legacy" provider for RC4 --- libtransmission/crypto-utils-openssl.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/libtransmission/crypto-utils-openssl.c b/libtransmission/crypto-utils-openssl.c index 45fd71913..14d680654 100644 --- a/libtransmission/crypto-utils-openssl.c +++ b/libtransmission/crypto-utils-openssl.c @@ -20,6 +20,9 @@ #include <openssl/rand.h> #include <openssl/ssl.h> #include <openssl/x509.h> +#if OPENSSL_VERSION_MAJOR >= 3 +#include <openssl/provider.h> +#endif #include "transmission.h" #include "crypto-utils.h" @@ -184,6 +187,10 @@ static void openssl_evp_cipher_context_free(EVP_CIPHER_CTX* handle) tr_rc4_ctx_t tr_rc4_new(void) { +#if OPENSSL_VERSION_MAJOR >= 3 +    OSSL_PROVIDER_load(NULL, "default"); +    OSSL_PROVIDER_load(NULL, "legacy"); +#endif EVP_CIPHER_CTX* handle = EVP_CIPHER_CTX_new(); if (check_result(EVP_CipherInit_ex(handle, EVP_rc4(), NULL, NULL, NULL, -1))) -- 2.35.1 </ins>
Change:
Not sure if it's a local-ai (or rather one of its dependency llama-cpp/gpt4all) but I can't leverage GPU inference of my nvidia RTX3060 because of error I think. nvidia-smi output looks ok: +
----------+ |-----------------------------------------+------------------------+----------------------+ [90m10:21PM[0m DBG GRPC(mistral-7b-): stderr : search path=/nix/store/bn7pnigb0f8874m6riiw6dngsmdyic1g-gcc-13.3.0-lib/lib/glibc-hwcaps/x86-64-v3:/nix/store/bn7pnigb0f8874m6riiw6dngsmdyic1g-gcc-13.3.0-lib/lib/glibc-hwcaps/x86-64-v2:/nix/store/bn7pnigb0f8874m6riiw6dngsmdyic1g-gcc-13.3.0-lib/lib:/nix/store/zx9yfgv4ag607b8m3dgcp5p94b6vd13c-cudacudart-12.2.140-lib/lib/stubs/glibc-hwcaps/x86-64-v3:/nix/store/zx9yfgv4ag607b8m3dgcp5p94b6vd13c-cudacudart-12.2.140-lib/lib/stubs/glibc-hwcaps/x86-64-v2:/nix/store/zx9yfgv4ag607b8m3dgcp5p94b6vd13c-cudacudart-12.2.140-lib/lib/stubs (RUNPATH from file /tmp/localai/backend_data/backend-assets/grpc/llama-cpp-avx2) ls -l /run/opengl-driver/lib | head lrwxrwxrwx - root 1 janv. 1970 d3d -/nix/store/fh3p3s1gg0ick2f295zfwi2jlr78166r-mesa-24.1.1-drivers/lib/d3d dr-xr-xr-x - root 1 janv. 1970 dri lrwxrwxrwx - root 1 janv. 1970 gbm -/nix/store/w7fcnyxkxara9fixrmigzrir3k8fbdb3-nvidia-x11-550.90.07-6.8.12/lib/gbm lrwxrwxrwx - root 1 janv. 1970 nvidia -/nix/store/w7fcnyxkxara9fixrmigzrir3k8fbdb3-nvidia-x11-550.90.07-6.8.12/lib/nvidia lrwxrwxrwx - root 1 janv. 1970 systemd -/nix/store/w7fcnyxkxara9fixrmigzrir3k8fbdb3-nvidia-x11-550.90.07-6.8.12/lib/systemd dr-xr-xr-x - root 1 janv. 1970 vdpau lrwxrwxrwx - root 1 janv. 1970 -/nix/store/w7fcnyxkxara9fixrmigzrir3k8fbdb3-nvidia-x11-550.90.07- lrwxrwxrwx - root 1 janv. 1970 -/nix/store/w7fcnyxkxara9fixrmigzrir3k8fbdb3-nvidia-x11-550.90.07- console [user nix-shell -p nix-info --run "nix-info -m" output here Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
using llama-cpp directly works fine so I suspect a problem in local-ai building. I will stick to llama-cpp for now
This is being loaded instead of

Discussion:
postFixup = let LD_LIBRARY_PATH = [ ] <del> ++ lib.optionals with_cublas [ (lib.getLib libcublas) cuda_cudart addDriverRunpath.driverLink ] </del> <ins> ++ lib.optionals with_cublas [ # driverLink has to be first to avoid loading the stub version of libcuda.so # https://github.com/NixOS/nixpkgs/issues/320145#issuecomment-2190319327 addDriverRunpath.driverLink (lib.getLib libcublas) cuda_cudart ] </ins> ++ lib.optionals with_clblas [ clblast ocl-icd ] ++ lib.optionals with_openblas [ openblas ] ++ lib.optionals with_tts [ piper-phonemize ];
Change:
An uncaught exception is raised when running the vimPluginUpdater script Steps to reproduce the behavior: the vim plugin update script with The script should not raise an exception Eception: <!-- 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]:
This is because the file has been corrupted by . I’ll send a PR to fix this in a bit.

Discussion:
repo,branch,alias <del> https://codeberg.org/FelipeLema/cmp-async-path/,, </del> https://github.com/euclidianAce/BetterLua.vim/,, https://github.com/vim-scripts/BufOnly.vim/,, https://github.com/jackMort/ChatGPT.nvim/,HEAD,

https://github.com/asheq/close-buffers.vim/,HEAD, https://github.com/Civitasv/cmake-tools.nvim/,, https://github.com/winston0410/cmd-parser.nvim/,, <del> <<<<<<< HEAD </del> https://github.com/tzachar/cmp-ai/,HEAD, https://codeberg.org/FelipeLema/cmp-async-path/,, <del> ======= >>>>>>> 8c49439301ad (vimPlugins.nvim-genghis: init at 2024-05-21) </del> https://github.com/crispgm/cmp-beancount/,HEAD, https://github.com/hrsh7th/cmp-buffer/,, https://github.com/hrsh7th/cmp-calc/,,
Change:
Project description Self-hosted & Fully-automated ActivityPub Bridge for Static Sites. Metadata homepage URL: source URL: license: agpl3Only platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I'll try to make a PR.

Discussion:
githubId = 11614750; name = "Alexander Sharov"; }; <ins> kwaa = { name = "藍+85CD"; email = "kwa@kwaa.dev"; matrix = "@kwaa:matrix.org"; github = "kwaa"; githubId = 50108258; keys = [{ fingerprint = "ABCB A12F 1A8E 3CCC F10B  5109 4444 7777 3333 4444"; }]; }; </ins> kwohlfahrt = { email = "kai.wohlfahrt@gmail.com"; github = "kwohlfahrt";

<ins> { cmake , fetchFromGitHub , gitUpdater , lib , openssl , pkg-config , rustPlatform }: rustPlatform.buildRustPackage rec { pname = "hatsu"; version = "0.2.0"; src = fetchFromGitHub { owner = "importantimport"; repo = "hatsu"; rev = "v${version}"; hash = "sha256-gBzhuV0SDmNwl5PkpdGxkMBn5m4vEXfv23WK7+ZzQs8="; }; cargoHash = "sha256-A2tl0jjKODA/qodxkIe/3V4ZDGV4X0myiduJsLtd7r0="; nativeBuildInputs = [ cmake pkg-config ]; buildInputs = [ openssl ]; env = { OPENSSL_NO_VENDOR = true; }; passthru.updateScript = gitUpdater { rev-prefix = "v"; ignoredVersions = "beta"; }; meta = { description = "Self-hosted and fully-automated ActivityPub bridge for static sites"; homepage = "https://github.com/importantimport/hatsu"; license = lib.licenses.agpl3Only; mainProgram = "hatsu"; maintainers = with lib.maintainers; [ kwaa ]; platforms = lib.platforms.linux; }; } </ins>
Change:
Project description A VS Code theme for the night owls out there. Now introducing Light Owl theme for daytime usage. Decisions were based on meaningful contrast for reading comprehension and for optimal razzle dazzle. Metadata homepage URL: https://open- source URL: license: mit platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I'm creating this issue hoping to get some recommendations on where to look for information on how to package a vscode extension. I'm under the impression (correct me if I'm wrong) that a vscode extension should be a simpler project to package for my first shot at it. I've followed the contribution instructions for nixpkgs so I have the repo forked and ready to go. I'm just unfamiliar with what changes I actually need to make. Any assistance with this would be greatly appreciated.
Have a look in: Read the Edit: Build as:
Great, thanks. I'll look into those.
In case you can't solve your problem, we need to update docs. But then, I need to know what problem you are having.
I'm getting stuck on the value for that I'm suppose to use. Based on the other extensions I'm confident I'm not just using the commit hash but I'm not sure where the sha256 values are coming from. Do you have any additional information on this?
When you try to build it will generate the hash for you, so you copy and paste it. (What you have to do is just to erase the hash so it gets recomputed.)
Did it work for you? In case yes, consider upstreaming. (And closing this issue.)
I've kept the PR as a draft while I work out any issues with it and finish reading through the contribution docs. Is there any directions on how to correct the formatting? I thought I was following it while first making the
thanks for all your help with this process.

Discussion:
githubId = 4303706; keys = [ { fingerprint = "B00F E582 FD3F 0732 EA48  3937 F558 14E4 D687 4375"; } ]; }; <ins> pladypus = { name = "Peter Loftus"; email = "loftusp5976+nixpkgs@gmail.com"; github = "pladypus"; githubId = 56337621; }; </ins> plchldr = { email = "mail@oddco.de"; github = "plchldr";

}; }; <ins> sdras.night-owl = buildVscodeMarketplaceExtension rec { mktplcRef = { name = "night-owl"; publisher = "sdras"; version = "2.0.1"; hash = "sha256-AqfcVV9GYZ+GLgusXfij9z4WzrU9cCHp3sdZb0i6HzE="; }; meta = { changelog = "https://github.com/sdras/night-owl-vscode-theme/blob/main/CHANGELOG.md#${ builtins.replaceStrings [ "." ] [ "" ] mktplcRef.version }"; description = "A Visual Studio Code theme named Light Owl for daytime usage"; longDescription = '' A VS Code theme for the night owls out there. Now introducing Light Owl theme for daytime usage. Decisions were based on meaningful contrast for reading comprehension and for optimal razzle dazzle. ''; downloadPage = "https://marketplace.visualstudio.com/items?itemName=sdras.night-owl"; homepage = "https://github.com/sdras/night-owl-vscode-theme"; license = lib.licenses.mit; maintainers = [ lib.maintainers.pladypus ]; }; }; </ins> seatonjiang.gitmoji-vscode = buildVscodeMarketplaceExtension { mktplcRef = { publisher = "seatonjiang";
Change:
Currently the fira, fira-sans e fira-mono packages use the source available in the . According to , this repository is not up to date: The latest versions of the fonts are available at <!-- 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:
symlinkJoin rec { pname = "fira"; <del> inherit (fira-mono) version; </del> <ins> inherit (fira-sans) version; </ins> name = "${pname}-${version}"; paths = [

meta = { description = "Fira font family including Fira Sans and Fira Mono"; <del> homepage = "https://mozilla.github.io/Fira/"; </del> <ins> homepage = "https://bboxtype.com/fira/"; </ins> license = lib.licenses.ofl; platforms = lib.platforms.all; };
Change:
Steps to reproduce the behavior: mattermost-desktop Electron 28 and has it as an explicit dependency: I patched it in my own fork of nixpkgs to just use instead of hardcoding the version and that seems to work fine. Is there a reason why it is pinned to a specific electron version? <!-- 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:
{ lib , stdenv , fetchurl <del> , electron_28 </del> <ins> , electron </ins> , makeWrapper }:

substituteInPlace $out/share/applications/Mattermost.desktop  --replace /share/mattermost-desktop/mattermost-desktop /bin/mattermost-desktop <del> makeWrapper '${lib.getExe electron_28}' $out/bin/${pname}  </del> <ins> makeWrapper '${lib.getExe electron}' $out/bin/${pname}  </ins> --set-default ELECTRON_IS_DEV 0  --add-flags $out/share/${pname}/app.asar  --add-flags "''${NIXOS_OZONE_WL:+''${WAYLAND_DISPLAY:+--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations}}"
Change:
Steps to reproduce the behavior: Checking waybar's , it appears that fixing this would just be a case of passing in . <!-- 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]:
It appears that a similar issue also arises with .

Discussion:
mesonFlags = (lib.mapAttrsToList lib.mesonEnable { <del> "cava" = cavaSupport; </del> <ins> "cava" = cavaSupport && lib.asserts.assertMsg sndioSupport "Sndio support is required for Cava"; </ins> "dbusmenu-gtk" = traySupport; "jack" = jackSupport; <ins> "libevdev" = evdevSupport; </ins> "libinput" = inputSupport; "libnl" = nlSupport; "libudev" = udevSupport;
Change:
maintainer seams to be not active Package name: sayonara Latest released version: 1.10.0-stable1 <!-- Search your package here: --- Current version on the unstable channel: 1.7.0-stable3 Current version on the stable/release channel:1.7.0-stable3 <!-- 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]:
please edit the title to provide more info
seems to work fine

Discussion:
in mkDerivation rec { pname = "sayonara"; <del> version = "1.7.0-stable3"; </del> <ins> version = "1.10.0-stable1"; </ins> src = fetchFromGitLab { owner = "luciocarreras"; repo = "sayonara-player"; rev = version; <del> hash = "sha256-tJ/8tGNkmTwWRCpPy/h85SP/6QDAgcaKWJdM5MSAXJw="; </del> <ins> hash = "sha256-ZcuWe1dsLJS4/nLXSSKB7wzPU9COFyE4vPSwZIo0bgI="; </ins> }; <ins> # error: no matching function for call to 'max' postPatch = '' substituteInPlace src/Components/Playlist/PlaylistModifiers.cpp  --replace-fail "std::max" "std::max<MilliSeconds>" ''; </ins> nativeBuildInputs = [ cmake ninja pkg-config qttools ]; buildInputs = [
Change:
default: cc Until then, just edit manually.
Remember you can do this too: = [ "/ip4/0.0.0.0/tcp/4001" "/ip6/::/tcp/4001" ]; It seems reasonable to have this default, however, since the nixos module has no way of getting the daemon to reset options when the user removes an explicit option from Incidentally, some config needs special handling, since it can't be set without re-initializing the leveldb, etc. I don't like the idea of having to duplicate every default setting into a , but I guess there's no other way until the ipfs devs make the daemon's config less stateful. I would prefer they move this type of runtime config into command-line args whose absence indicates that defaults should be used. Perhaps we should file that upstream.

Discussion:
# NB: migration must be performed prior to pre-start, else we get the failure message! preStart = '' ipfs repo fsck # workaround for BUG #4212 (https://github.com/ipfs/go-ipfs/issues/4214) <del> ipfs --local config Addresses.API ${cfg.apiAddress} ipfs --local config Addresses.Gateway ${cfg.gatewayAddress} </del> '' + optionalString cfg.autoMount '' ipfs --local config Mounts.FuseAllowOther --json true ipfs --local config Mounts.IPFS ${cfg.ipfsMountDir}

EOF ipfs --local config --json "${concatStringsSep "." path}" "$value" '') <del> cfg.extraConfig) </del> <ins> ({ Addresses.API = cfg.apiAddress; Addresses.Gateway = cfg.gatewayAddress; Addresses.Swarm = cfg.swarmAddress; } // cfg.extraConfig)) </ins> ); serviceConfig = { ExecStart = "${wrapped}/bin/ipfs daemon ${ipfsFlags}";

description = "Where IPFS exposes its API to"; }; <ins> swarmAddress = mkOption { type = types.listOf types.str; default = [ "/ip4/0.0.0.0/tcp/4001" "/ip6/::/tcp/4001" ]; description = "Where IPFS listens for incoming p2p connections"; }; </ins> enableGC = mkOption { type = types.bool; default = false;
Change:
Steps to reproduce the behavior: flyctl-0.2.69 Looks like recent bump with failing ofborg was merged and attempted to be backported right away... <!-- 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]:
Copied my response from the backport of the linked PR
This is caused by a weird map merge implementation in the sentry-go SDK used by upstream, that is only hit when the tests are run with . Upstream runs tests without the tag, and we have the tag in our derivation which propagates through to the tests I will include a temporary fix as part of the bump, and file upstream issues for both flyctl and sentry-go
This has been addressed in

Discussion:
buildGoModule rec { pname = "flyctl"; <del> version = "0.2.69"; </del> <ins> version = "0.2.71"; </ins> src = fetchFromGitHub { owner = "superfly"; repo = "flyctl"; rev = "v${version}"; <del> hash = "sha256-6SPJt+az+C0amCnRScp85JqUfnWswHdS1OtOMa40Haw="; </del> <ins> hash = "sha256-d2qoTRWuUh7Kn0uqT3fIlB8BbFJmyVEIlfInS3m+etc="; </ins> }; <del> vendorHash = "sha256-O5lUw0XzQUoy3mAmSpeW6WfBgg0FLxXkk7hCUAS2+o8="; </del> <ins> vendorHash = "sha256-iRZrjkWQxuUW/YM5TygFt+g8suM5iLGsWsCt4QQOX3M="; </ins> subPackages = [ "." ];

''; # We override checkPhase to be able to test ./... while using subPackages <ins> # Temporary fix for https://github.com/superfly/flyctl/issues/3642. We # should go back to buildGoDir instead of go test once that is resolved. </ins> checkPhase = '' runHook preCheck # We do not set trimpath for tests, in case they reference test assets export GOFLAGS=''${GOFLAGS//-trimpath/} <del> buildGoDir test ./... </del> <ins> go test ./... </ins> runHook postCheck '';
Change:
Project description The elevator pitch: But it's mostly used to install and run AI applications pretty easily, the creator made this video: Which is the same as on the homepage. Metadata homepage URL: https://pinokio.computer/ source URL: license: MIT platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I created a PR based on this packaging request.

Discussion:
<ins> { lib , stdenv , fetchurl , pkgs , appimageTools }: let pname = "pinokio"; version = "1.3.4"; src = fetchurl { x86_64-darwin = { url = "https://github.com/pinokiocomputer/pinokio/releases/download/${version}/Pinokio-${version}.dmg"; hash = "sha256-Il5zaVWu4icSsKmMjU9u1/Mih34fd+xNpF1nkFAFFGo="; }; x86_64-linux = { url = "https://github.com/pinokiocomputer/pinokio/releases/download/${version}/Pinokio-${version}.AppImage"; hash = "sha256-/E/IAOUgxH9RWpE2/vLlQy92LOgwpHF79K/1XEtSpXI="; }; }.${stdenv.system} or (throw "Unsupported system: ${stdenv.system}"); appimageContents = appimageTools.extractType2 { inherit pname version src; }; meta = { homepage = "https://pinokio.computer"; description = "Browser to install, run, and programmatically control ANY application automatically"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ ByteSudoer ]; platforms = [ "x86_64-darwin" "x86_64-linux" ]; mainProgram = "pinokio"; sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ]; }; in if stdenv.isDarwin then stdenv.mkDerivation { inherit pname version src meta; sourceRoot = "."; nativeBuildInputs = with pkgs; [ undmg ]; installPhase = '' runHook preInstall mkdir -p "$out/Applications" mv Pinokio.app $out/Applications/ runHook postInstall ''; } else appimageTools.wrapType2 { inherit pname version src meta; extraInstallCommands = '' mkdir -p $out/share/pinokio cp -a ${appimageContents}/{locales,resources} $out/share/pinokio cp -a ${appimageContents}/usr/share/icons $out/share/ install -Dm 444 ${appimageContents}/pinokio.desktop -t $out/share/applications ''; } </ins>
Change:
Whenever is used with vivaldi to set it's binary path into a session variable for example, it produces a big warning stating that the attribute is missing and it will default to package name. a library function that needs the attribute like lib.getExe the vivaldi package as below: rebuild the config: the build process a big warning will appear stating the following: , Do the hint stated in the warning and use it like:

Discussion:
homepage    = "https://vivaldi.com"; license     = licenses.unfree; sourceProvenance = with sourceTypes; [ binaryNativeCode ]; <ins> mainProgram = "vivaldi"; </ins> maintainers = with maintainers; [ otwieracz badmutex ]; platforms   = [ "x86_64-linux" "aarch64-linux" ]; };
Change:
Project description : A single-executable, statically linked CLI program runnable on most hardware (written in go). This provides most of the functionality of the , but on the command line for your scripting needs! Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin I have created a nix flake that packages ardugotools , so most of the work is already done, it would just need to be to the main repo.

Discussion:
<ins> { lib, buildGoModule, fetchFromGitHub, ... }: let version = "0.5.1"; in buildGoModule { pname = "ardugotools"; inherit version; src = fetchFromGitHub { owner = "randomouscrap98"; repo = "ardugotools"; rev = "refs/tags/v${version}"; hash = "sha256-c+sJoE5NML06bl6ch+OiN1vO0rdyE2gf/z4pzY7i5Qk="; }; vendorHash = "sha256-Z9ObsS+GwVsz6ZlXCgN0WlShHzbmx4WLa/1/XLSSAAs="; meta = { description = "CLI toolset for Arduboy"; changelog = "https://github.com/randomouscrap98/ardugotools/releases/tag/v${version}"; homepage = "https://github.com/randomouscrap98/ardugotools"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ luftmensch-luftmensch ]; mainProgram = "ardugotools"; }; } </ins>