Question:
When changing an SVP option during playback or the played file in mpv, starting from mpv 0.37.0, due to , it spams: and SVP no longer reports any connected player at the bottom of its window after that. top left logo, "Open file via mpv", pick a video the video is playing, switch back and forth between one of the buttons under "Do frame rate conversion" like "To screen" and "Movie x2" In mpv 0.36 and earlier, it says: and SVP keeps working normally. SVP has no source code available and new versions haven't been released on Linux since 2021, while mpv 0.37 came out in November 2023, making it unlikely to be fixed upstream any time soon. I've made a dirty workaround by to re-add the option, and overriding the source of the mpv package in my flake + home-manager setup. Handling both the external mpv package and the one within SVP's (the mpv that gets used by SVP's in-GUI "Open file") gets complicated - here are the relevant parts: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for your investigation! Indeed it looks like modifying mpv to add the option back is the best way. Based on the diff on your fork, the change seems small enough for us to maintain. On the other hand, patching SVP is impossible due to its tamper protection.
A couple questions: the mpv package gets updated, it might break building SVP with the patch. Do github checks catch these cases, or will the SVP package just be broken until someone else notices? I give you push access to the forked repo, to rebase and regenerate the patch as needed? I rarely update my system, so the repo will likely be left randomly outdated until I have to take care of it. you make the SVP package take and overridable parameters, so that it isn't so hard to e.g. add scripts to the internal mpv? to make a standard external mpv connect to SVP will fail since it won't be patched, is there a good way to indicate to users that they should install in their environment? The parameters mentioned above should probably also be made known.
package in nixpkgs will be broken. However I also have this SVP package on my NUR, and have daily CI runs to rebuild packages, so once it breaks I will notice and make a fix. isn't necessary. I can rebase the patch on mainline mpv as needed. will add them. can't think of any good way for now.

<del> { stdenv , buildFHSEnv , writeShellScriptBin , fetchurl , callPackage , makeDesktopItem , copyDesktopItems , ffmpeg , glibc , jq , lib , libmediainfo , libsForQt5 , libusb1 , ocl-icd , p7zip , patchelf , socat , vapoursynth , xdg-utils , xorg , zenity </del> <ins> { stdenv, buildFHSEnv, writeShellScriptBin, fetchurl, callPackage, makeDesktopItem, copyDesktopItems, ffmpeg, glibc, jq, lib, libmediainfo, libsForQt5, libusb1, ocl-icd, p7zip, patchelf, socat, vapoursynth, xdg-utils, xorg, zenity, </ins> }: let mpvForSVP = callPackage ./mpv.nix { };


Question:
When changing an SVP option during playback or the played file in mpv, starting from mpv 0.37.0, due to , it spams: and SVP no longer reports any connected player at the bottom of its window after that. top left logo, "Open file via mpv", pick a video the video is playing, switch back and forth between one of the buttons under "Do frame rate conversion" like "To screen" and "Movie x2" In mpv 0.36 and earlier, it says: and SVP keeps working normally. SVP has no source code available and new versions haven't been released on Linux since 2021, while mpv 0.37 came out in November 2023, making it unlikely to be fixed upstream any time soon. I've made a dirty workaround by to re-add the option, and overriding the source of the mpv package in my flake + home-manager setup. Handling both the external mpv package and the one within SVP's (the mpv that gets used by SVP's in-GUI "Open file") gets complicated - here are the relevant parts: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for your investigation! Indeed it looks like modifying mpv to add the option back is the best way. Based on the diff on your fork, the change seems small enough for us to maintain. On the other hand, patching SVP is impossible due to its tamper protection.
A couple questions: the mpv package gets updated, it might break building SVP with the patch. Do github checks catch these cases, or will the SVP package just be broken until someone else notices? I give you push access to the forked repo, to rebase and regenerate the patch as needed? I rarely update my system, so the repo will likely be left randomly outdated until I have to take care of it. you make the SVP package take and overridable parameters, so that it isn't so hard to e.g. add scripts to the internal mpv? to make a standard external mpv connect to SVP will fail since it won't be patched, is there a good way to indicate to users that they should install in their environment? The parameters mentioned above should probably also be made known.
package in nixpkgs will be broken. However I also have this SVP package on my NUR, and have daily CI runs to rebuild packages, so once it breaks I will notice and make a fix. isn't necessary. I can rebase the patch on mainline mpv as needed. will add them. can't think of any good way for now.

svp-dist = stdenv.mkDerivation rec { pname = "svp-dist"; <del> version = "4.5.210-2"; </del> <ins> version = "4.6.263"; </ins> src = fetchurl { url = "https://www.svp-team.com/files/svp4-linux.${version}.tar.bz2"; <del> hash = "sha256-dY9uQ9jzTHiN2XSnOrXtHD11IIJW6t9BUzGGQFfZ+yg="; </del> <ins> sha256 = "sha256-HyRDVFHVmTan/Si3QjGQpC3za30way10d0Hk79oXG98="; </ins> }; <del> nativeBuildInputs = [ p7zip patchelf ]; </del> <ins> nativeBuildInputs = [ p7zip patchelf ]; </ins> dontFixup = true; unpackPhase = ''


Question:
When changing an SVP option during playback or the played file in mpv, starting from mpv 0.37.0, due to , it spams: and SVP no longer reports any connected player at the bottom of its window after that. top left logo, "Open file via mpv", pick a video the video is playing, switch back and forth between one of the buttons under "Do frame rate conversion" like "To screen" and "Movie x2" In mpv 0.36 and earlier, it says: and SVP keeps working normally. SVP has no source code available and new versions haven't been released on Linux since 2021, while mpv 0.37 came out in November 2023, making it unlikely to be fixed upstream any time soon. I've made a dirty workaround by to re-add the option, and overriding the source of the mpv package in my flake + home-manager setup. Handling both the external mpv package and the one within SVP's (the mpv that gets used by SVP's in-GUI "Open file") gets complicated - here are the relevant parts: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for your investigation! Indeed it looks like modifying mpv to add the option back is the best way. Based on the diff on your fork, the change seems small enough for us to maintain. On the other hand, patching SVP is impossible due to its tamper protection.
A couple questions: the mpv package gets updated, it might break building SVP with the patch. Do github checks catch these cases, or will the SVP package just be broken until someone else notices? I give you push access to the forked repo, to rebase and regenerate the patch as needed? I rarely update my system, so the repo will likely be left randomly outdated until I have to take care of it. you make the SVP package take and overridable parameters, so that it isn't so hard to e.g. add scripts to the internal mpv? to make a standard external mpv connect to SVP will fail since it won't be patched, is there a good way to indicate to users that they should install in their environment? The parameters mentioned above should probably also be made known.
package in nixpkgs will be broken. However I also have this SVP package on my NUR, and have daily CI runs to rebuild packages, so once it breaks I will notice and make a fix. isn't necessary. I can rebase the patch on mainline mpv as needed. will add them. can't think of any good way for now.

desktopName = "SVP 4 Linux"; genericName = "Real time frame interpolation"; icon = "svp-manager4"; <del> categories = [ "AudioVideo" "Player" "Video" ]; mimeTypes = [ "video/x-msvideo" "video/x-matroska" "video/webm" "video/mpeg" "video/mp4" ]; </del> <ins> categories = [ "AudioVideo" "Player" "Video" ]; mimeTypes = [ "video/x-msvideo" "video/x-matroska" "video/webm" "video/mpeg" "video/mp4" ]; </ins> terminal = false; startupNotify = true; }) ]; meta = with lib; { <ins> mainProgram = "SVPManager"; </ins> description = "SmoothVideo Project 4 (SVP4) converts any video to 60 fps (and even higher) and performs this in real time right in your favorite video player"; homepage = "https://www.svp-team.com/wiki/SVP:Linux"; platforms = [ "x86_64-linux" ];


Question:
Steps to reproduce the behavior: stig If I try to install it from my config, I get . If I try to run it by nix-shell: is the nixpkgs commit I'm currently using to get a working version of this program. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The different experience you get with vs is a problem in your Nix environment - probably an old version of nixpkgs you use for vs how you build "your config". However the test failing mark this package is now completely broken. See also discussion with upstream at: . I opened that marks stig as broken, and it will close this issue when merged.
stig works for me with this overlay: I think since addresses
It'd be great if you'd share this in a PR.
Opened at !

description = "TUI and CLI for the BitTorrent client Transmission"; homepage = "https://github.com/rndusr/stig"; license = licenses.gpl3Plus; <del> maintainers = with maintainers; [ doronbehar ]; </del> <ins> # Too many broken tests, and it fails to launch broken = true; maintainers = with maintainers; [  ]; </ins> }; }


Question:
Steps to reproduce the behavior: stig If I try to install it from my config, I get . If I try to run it by nix-shell: is the nixpkgs commit I'm currently using to get a working version of this program. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The different experience you get with vs is a problem in your Nix environment - probably an old version of nixpkgs you use for vs how you build "your config". However the test failing mark this package is now completely broken. See also discussion with upstream at: . I opened that marks stig as broken, and it will close this issue when merged.
stig works for me with this overlay: I think since addresses
It'd be great if you'd share this in a PR.
Opened at !

{ lib <del> , stdenv </del> , fetchFromGitHub , python310Packages , testers


Question:
Steps to reproduce the behavior: stig If I try to install it from my config, I get . If I try to run it by nix-shell: is the nixpkgs commit I'm currently using to get a working version of this program. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The different experience you get with vs is a problem in your Nix environment - probably an old version of nixpkgs you use for vs how you build "your config". However the test failing mark this package is now completely broken. See also discussion with upstream at: . I opened that marks stig as broken, and it will close this issue when merged.
stig works for me with this overlay: I think since addresses
It'd be great if you'd share this in a PR.
Opened at !

pname = "stig"; # This project has a different concept for pre release / alpha, # Read the project's README for details: https://github.com/rndusr/stig#stig <del> version = "0.12.8a0"; </del> <ins> version = "0.12.10a0"; </ins> src = fetchFromGitHub { owner = "rndusr"; repo = "stig"; rev = "v${version}"; <del> sha256 = "sha256-vfmuA6DqWvAygcS6N+qX1h+Ag+P4eOwm41DhAFZR3r8="; </del> <ins> sha256 = "sha256-lSFI4/DxWl17KFgLXZ7c5nW/e5IUGN7s8Gm6wTM5ZWg="; </ins> }; propagatedBuildInputs = with python310Packages; [


Question:
Steps to reproduce the behavior: stig If I try to install it from my config, I get . If I try to run it by nix-shell: is the nixpkgs commit I'm currently using to get a working version of this program. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The different experience you get with vs is a problem in your Nix environment - probably an old version of nixpkgs you use for vs how you build "your config". However the test failing mark this package is now completely broken. See also discussion with upstream at: . I opened that marks stig as broken, and it will close this issue when merged.
stig works for me with this overlay: I think since addresses
It'd be great if you'd share this in a PR.
Opened at !

version = "stig version ${version}"; }; <ins> # https://github.com/rndusr/stig/issues/214#issuecomment-1995651219 dontUsePytestCheck = true; </ins> meta = with lib; { description = "TUI and CLI for the BitTorrent client Transmission"; homepage = "https://github.com/rndusr/stig"; license = licenses.gpl3Plus; <del> # Too many broken tests, and it fails to launch broken = true; </del> maintainers = with maintainers; [  ]; }; }


Question: Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

, enableQt ? true , callPackage , qtwayland <ins> , fetchPypi </ins> }: let <del> version = "4.5.3"; </del> <ins> version = "4.5.4"; python = python3.override { self = python; packageOverrides = self: super: { # Pin ledger-bitcoin to 0.2.1 ledger-bitcoin = super.ledger-bitcoin.overridePythonAttrs (oldAttrs: rec { version = "0.2.1"; format = "pyproject"; src = fetchPypi { pname = "ledger_bitcoin"; inherit version; hash = "sha256-AWl/q2MzzspNIo6yf30S92PgM/Ygsb+1lJsg7Asztso="; }; }); }; }; </ins> libsecp256k1_name = if stdenv.isLinux then "libsecp256k1.so.{v}"


Question: Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

owner = "spesmilo"; repo = "electrum"; rev = version; <del> sha256 = "sha256-Lr6ynHAbyaiaxYAWU5j5Wh5acxO5HkP1/jpnFrL4j68="; </del> <ins> sha256 = "sha256-fDu2PlEQOF7ftlS6dYw15S2XiAx+D/bng4zC9ELj6uk="; </ins> postFetch = '' mv $out ./all


Question: Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

in <del> python3.pkgs.buildPythonApplication { </del> <ins> python.pkgs.buildPythonApplication { </ins> pname = "electrum"; inherit version; src = fetchurl { url = "https://download.electrum.org/${version}/Electrum-${version}.tar.gz"; <del> sha256 = "sha256-kej0msc7SB+51ad5xZrT8MMEY5rfYOGqum6RO1gBH5s="; </del> <ins> sha256 = "sha256-lDuwXhOjcbCx8x/oIoigrklDwCbhn1trf5lDf/X/1Qc="; </ins> }; postUnpack = ''


Question: Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

nativeBuildInputs = lib.optionals enableQt [ wrapQtAppsHook ]; buildInputs = lib.optional (stdenv.isLinux && enableQt) qtwayland; <del> propagatedBuildInputs = with python3.pkgs; [ </del> <ins> propagatedBuildInputs = with python.pkgs; [ </ins> aiohttp aiohttp-socks aiorpcx


Question: Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

ckcc-protocol keepkey trezor <ins> bitbox02 cbor pyserial </ins> ] ++ lib.optionals enableQt [ pyqt5 qdarkstyle ]; <del> checkInputs = with python3.pkgs; lib.optionals enableQt [ </del> <ins> checkInputs = with python.pkgs; lib.optionals enableQt [ </ins> pyqt6 ];


Question: Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

wrapQtApp $out/bin/electrum ''; <del> nativeCheckInputs = with python3.pkgs; [ pytestCheckHook pyaes pycryptodomex ]; </del> <ins> nativeCheckInputs = with python.pkgs; [ pytestCheckHook pyaes pycryptodomex ]; </ins> pytestFlagsArray = [ "tests" ];


Question: Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

changelog = "https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES"; license = licenses.mit; platforms = platforms.all; <del> maintainers = with maintainers; [ joachifm np prusnak ]; </del> <ins> maintainers = with maintainers; [ joachifm np prusnak chewblacka ]; </ins> mainProgram = "electrum"; }; }


Question:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags: - -
Thanks and !

pytestCheckHook ]; <del> disabledTests = lib.optionals stdenv.isDarwin [ </del> <ins> disabledTests = [ # Time based "test_decode_threads" ] ++ lib.optionals stdenv.isDarwin [ </ins> # https://github.com/bigcat88/pillow_heif/issues/89 # not reproducible in nixpkgs "test_opencv_crash"


Question:
Steps to reproduce the behavior: .config.contentAddressedByDefault = true; .firefox.package = pkgs.wrapFirefox pkgs.firefox-devedition-unwrapped {}; to build I also have march/mtune set and can't/won't use firefox-bin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I think this is $outPath of gcc
I think my fix worked

, sndio , libjack2 , speechd <ins> , removeReferencesTo </ins> }: ## configurability of the wrapper itself


Question:
Steps to reproduce the behavior: .config.contentAddressedByDefault = true; .firefox.package = pkgs.wrapFirefox pkgs.firefox-devedition-unwrapped {}; to build I also have march/mtune set and can't/won't use firefox-bin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I think this is $outPath of gcc
I think my fix worked

}; })); <del> nativeBuildInputs = [ makeWrapper lndir jq ]; </del> <ins> nativeBuildInputs = [ makeWrapper lndir jq removeReferencesTo ]; </ins> buildInputs = [ browser.gtk3 ];


Question:
Steps to reproduce the behavior: .config.contentAddressedByDefault = true; .firefox.package = pkgs.wrapFirefox pkgs.firefox-devedition-unwrapped {}; to build I also have march/mtune set and can't/won't use firefox-bin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I think this is $outPath of gcc
I think my fix worked

passthru = { unwrapped = browser; }; disallowedRequisites = [ stdenv.cc ]; <ins> postInstall = '' find "$out" -type f -exec remove-references-to -t ${stdenv.cc} '{}' + ''; </ins> meta = browser.meta // { inherit (browser.meta) description; mainProgram = launcherName;


Question:
Package name: koreader Latest released version: 2024.03.1 <!-- Search your package here: --- Current version on the unstable channel: 2023.04 Current version on the stable/release channel: 2023.04 <!-- 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 test

in stdenv.mkDerivation rec { pname = "koreader"; <del> version = "2023.04"; </del> <ins> version = "2024.03.1"; </ins> src = if stdenv.isAarch64 then fetchurl { url = "https://github.com/koreader/koreader/releases/download/v${version}/koreader-${version}-arm64.deb"; <del> sha256 = "sha256-uuspjno0750hQMIB5HEhbV63wCna2izKOHEGIg/X0bU="; </del> <ins> hash = "sha256-9Bu+mWfJuPaH5nV71JMrcGipiZWfcf19KfVauCW92+I="; </ins> } else fetchurl { url = "https://github.com/koreader/koreader/releases/download/v${version}/koreader-${version}-amd64.deb"; <del> sha256 = "sha256-tRUeRB1+UcWT49dchN0YDvd0L5n1YRdtMSFc8yy6m5o="; </del> <ins> hash = "sha256-EZ3iqp0A2BZwI343nvvp71RGQx6FPesUBy4Lha4Yz4U="; </ins> }; src_repo = fetchFromGitHub {


Question:
Package name: koreader Latest released version: 2024.03.1 <!-- Search your package here: --- Current version on the unstable channel: 2023.04 Current version on the stable/release channel: 2023.04 <!-- 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 test

owner = "koreader"; rev = "v${version}"; fetchSubmodules = true; <del> sha256 = "sha256-c3j6hs0W0H2jDg6JVfU6ov7r7kucbqrQqf9PAvYBcJ0="; </del> <ins> sha256 = "sha256-gHn1xqBc7M9wkek1Ja1gry8TKIuUxQP8T45x3z2S4uc="; </ins> }; sourceRoot = ".";


Question:
fails to find libcdparanoia and flac at runtime. This is a regression from , and appears to be more or less the same issue, except for Plasma 6. Steps to reproduce the behavior: to rip a CD with K3b It works, and lists Flac as a supported format. If applicable, add screenshots to help explain your problem. The fix from should still apply in some form? Manually adding flac to and libcdparanoia to works around the problem. also (maintainer for Plasma 5 K3b) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Please test

libsamplerate, cdrdao, cdrtools, <ins> cdparanoia, </ins> dvdplusrwtools, libburn, <ins> libdvdcss, </ins> normalize, sox, transcode,


Question:
fails to find libcdparanoia and flac at runtime. This is a regression from , and appears to be more or less the same issue, except for Plasma 6. Steps to reproduce the behavior: to rip a CD with K3b It works, and lists Flac as a supported format. If applicable, add screenshots to help explain your problem. The fix from should still apply in some form? Manually adding flac to and libcdparanoia to works around the problem. also (maintainer for Plasma 5 K3b) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Please test

]; qtWrapperArgs = [ <del> "--prefix PATH ':' ${lib.makeBinPath [ </del> <ins> "--prefix PATH : ${lib.makeBinPath [ </ins> cdrdao cdrtools dvdplusrwtools


Question:
fails to find libcdparanoia and flac at runtime. This is a regression from , and appears to be more or less the same issue, except for Plasma 6. Steps to reproduce the behavior: to rip a CD with K3b It works, and lists Flac as a supported format. If applicable, add screenshots to help explain your problem. The fix from should still apply in some form? Manually adding flac to and libcdparanoia to works around the problem. also (maintainer for Plasma 5 K3b) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Please test

vcdimager flac ]}" <ins> # FIXME: this should really be done with patchelf --add-rpath, but it breaks the binary somehow "--prefix LD_LIBRARY_PATH : ${lib.makeLibraryPath [ cdparanoia libdvdcss ]}" </ins> ]; meta.mainProgram = "k3b"; }


Question:
Project description A waveform viewer with a focus on a snappy usable interface, and extensibility. <!-- Describe the project a little: --Metadata homepage URL: https://surfer- source URL: license: eupl12 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I tried to package it myself however, the following derivation fails: Error: Similar issue: Looks like the real issue has been solved couple years ago. I should update the derivation accordingly.

githubId = 1162118; name = "Harald Gliebe"; }; <ins> hakan-demirli = { email = "ehdemirli@proton.me"; github = "hakan-demirli"; githubId = 78746991; name = "Emre Hakan Demirli"; }; </ins> hakuch = { email = "hakuch@gmail.com"; github = "hakuch";