Question:
Steps to reproduce the behavior: Attempt to build vmware-workstation from the unstable branch using the following command: sudo nixos-rebuild switch --flake ~/nixos#framework --show-trace Observe the build failure with the following error related to the --docdir option in the configure flags. Build log Running phase: updateAutotoolsGnuConfigScriptsPhase Updating Autotools / GNU config script to a newer upstream version: Updating Autotools / GNU config script to a newer upstream version: Running phase: configurePhase fixing libtool script patching script interpreter paths in ./configure ./configure: interpreter directive changed from "#! /bin/sh" to "/nix/store/4bj2kxdm1462fzcc2i2s4dn33g2angcc-bash-5.2p32/bin/sh" configure flags: --disable-static --prefix=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3 --bindir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/bin --sbindir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/sbin --includedir=/nix/store/f8yb3rhalwdpaig8lwxd4plgbqn8vagk-gdbm-1.8.3-dev/include --oldincludedir=/nix/store/f8yb3rhalwdpaig8lwxd4plgbqn8vagk-gdbm-1.8.3-dev/include --mandir=/nix/store/64jmdcjmdl94l4hbadwqsz7j8qg16dwb-gdbm-1.8.3-man/share/man --infodir=/nix/store/vs7bglvjl3pxp2ffc98v5w7xlinn0q5j-gdbm-1.8.3-info/share/info --docdir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/share/doc/gdbm --libdir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/lib --libexecdir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/libexec --localedir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/share/locale --enable-libgdbm-compat configure: error: unrecognized option: --docdir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/share/doc/gdbm Try `./configure --help' for more information. Additional context I tried building the package on NixOS 24.05 with the following command, and the build succeeded without any issues: Notify maintainers cc Metadata [user nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Please update the issue's title with the actual package name ()
do we really need specific gdbm version during the build? or as a buildInputs?
I removed the override from and I can build and run vmware just fine. Could you just update the dependency version to 1.24 and remove the install override?
How can I do it myself? Download and edit the nixpkg and edit it?
Sorry, I didn't mean "you" as in you specifically, but more generally as a third person pronoun. I don't know how either, never contributed to nixpkgs before . I meant for the question to be at nixpkgs contributors to know if what I proposed makes sense. EDIT: Oh, might have misunderstood you. If you want to do the same thing I did then yes, get a local clone of nixpkgs, edit the file and point your system nixpkgs to the local clone. Here's the patch that worked for me: <details<summaryClick to show patch </summary</detailsNote that it doesn't pin the version of gdbm, it will always use the latest version from nixpkgs which may cause with future versions. I'm assuming there was a reason the original was pinned to 1.8.3.
Thanks it's very informative!

sha256 = "sha256-JSEW1gqQuLGRkathlwZU/TnG6dL/xWKW4//SfE+kO0A="; }; <del> gdbm3 = gdbm.overrideAttrs (old: rec { version = "1.8.3"; src = fetchurl { url = "mirror://gnu/gdbm/gdbm-${version}.tar.gz"; sha256 = "sha256-zDQDOKLii0AFirnrU1SiHVP4ihWC6iG6C7GFw3ooHck="; }; installPhase = '' mkdir -p $out/lib cp .libs/libgdbm*.so* $out/lib/ ''; }); </del> vmware-unpack-env = buildFHSEnv rec { name = "vmware-unpack-env"; targetPkgs = pkgs: [ zlib ];


Question:
Steps to reproduce the behavior: Attempt to build vmware-workstation from the unstable branch using the following command: sudo nixos-rebuild switch --flake ~/nixos#framework --show-trace Observe the build failure with the following error related to the --docdir option in the configure flags. Build log Running phase: updateAutotoolsGnuConfigScriptsPhase Updating Autotools / GNU config script to a newer upstream version: Updating Autotools / GNU config script to a newer upstream version: Running phase: configurePhase fixing libtool script patching script interpreter paths in ./configure ./configure: interpreter directive changed from "#! /bin/sh" to "/nix/store/4bj2kxdm1462fzcc2i2s4dn33g2angcc-bash-5.2p32/bin/sh" configure flags: --disable-static --prefix=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3 --bindir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/bin --sbindir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/sbin --includedir=/nix/store/f8yb3rhalwdpaig8lwxd4plgbqn8vagk-gdbm-1.8.3-dev/include --oldincludedir=/nix/store/f8yb3rhalwdpaig8lwxd4plgbqn8vagk-gdbm-1.8.3-dev/include --mandir=/nix/store/64jmdcjmdl94l4hbadwqsz7j8qg16dwb-gdbm-1.8.3-man/share/man --infodir=/nix/store/vs7bglvjl3pxp2ffc98v5w7xlinn0q5j-gdbm-1.8.3-info/share/info --docdir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/share/doc/gdbm --libdir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/lib --libexecdir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/libexec --localedir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/share/locale --enable-libgdbm-compat configure: error: unrecognized option: --docdir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/share/doc/gdbm Try `./configure --help' for more information. Additional context I tried building the package on NixOS 24.05 with the following command, and the build succeeded without any issues: Notify maintainers cc Metadata [user nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Please update the issue's title with the actual package name ()
do we really need specific gdbm version during the build? or as a buildInputs?
I removed the override from and I can build and run vmware just fine. Could you just update the dependency version to 1.24 and remove the install override?
How can I do it myself? Download and edit the nixpkg and edit it?
Sorry, I didn't mean "you" as in you specifically, but more generally as a third person pronoun. I don't know how either, never contributed to nixpkgs before . I meant for the question to be at nixpkgs contributors to know if what I proposed makes sense. EDIT: Oh, might have misunderstood you. If you want to do the same thing I did then yes, get a local clone of nixpkgs, edit the file and point your system nixpkgs to the local clone. Here's the patch that worked for me: <details<summaryClick to show patch </summary</detailsNote that it doesn't pin the version of gdbm, it will always use the latest version from nixpkgs which may cause with future versions. I'm assuming there was a reason the original was pinned to 1.8.3.
Thanks it's very informative!

libxslt libxml2 libuuid <del> gdbm3 </del> <ins> gdbm </ins> readline xz cups


Question: system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

pytest-xdist, pytestCheckHook, tables, <ins> pythonAtLeast, </ins> }: buildPythonPackage rec {


Question: system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

}; patches = [ <del> (fetchpatch { name = "gsd_3-compatibility.patch"; url = "https://github.com/mdtraj/mdtraj/commit/81209d00817ab07cfc4668bf5ec88088d16904c0.patch"; hash = "sha256-ttNmij7csxF0Z5wPPwhGumRX055W2IgFjRAe6nI6GNY="; }) # remove pkg_resources usage # https://github.com/mdtraj/mdtraj/pull/1837 (fetchpatch { name = "fix-runtime-error.patch"; url = "https://github.com/mdtraj/mdtraj/commit/02d44d4db7039fceb199c85b4f993244804f470d.patch"; hash = "sha256-nhbi3iOrDSM87DyIp1KVt383Vvb6aYOgkjuYzviqiq8="; }) # remove distutils usage # https://github.com/mdtraj/mdtraj/pull/1834 (fetchpatch { name = "python312-compatibility.patch"; url = "https://github.com/mdtraj/mdtraj/commit/95d79747deef42c976ca362a57806b61933409f3.patch"; hash = "sha256-Cq7/d745q6ZgAyWGM4ULnSsWezsbnu1CjSz5eqYSb+g="; }) </del> # disable intrinsics when SIMD is not available # TODO: enable SIMD with python3.12 # https://github.com/mdtraj/mdtraj/pull/1884


Question: system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

"test_precentered_2" ]; <ins> # these files import distutils # remove once https://github.com/mdtraj/mdtraj/pull/1916 is merged disabledTestPaths = lib.optionals (pythonAtLeast "3.12") [ "test_mol2.py" "test_netcdf.py" ]; </ins> pythonImportsCheck = [ "mdtraj" ]; meta = with lib; {


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

[[package]] name = "zed" <del> version = "0.149.3" </del> <ins> version = "0.149.5" </ins> dependencies = [ "activity_indicator", "anyhow",


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

rustPlatform.buildRustPackage rec { pname = "zed"; <del> version = "0.149.3"; </del> <ins> version = "0.149.5"; </ins> src = fetchFromGitHub { owner = "zed-industries"; repo = "zed"; rev = "refs/tags/v${version}"; <del> hash = "sha256-fz0StzZIqDLmip0M2959h7ZgoB+cdTC5QNKKNRVZItA="; </del> <ins> hash = "sha256-RQGYcJJf65arew9iwtPh/jFYMbXiY9Wg7xEjAsUSvEA="; </ins> fetchSubmodules = true; };


Question:
Steps to reproduce the behavior: X 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Awesome. Now I have malware with 200M+ size and a libcef within.
Interesting you actually have a fsverity-enabled build directory, so this is probably an upstream issue that nobody has run into while running the tests. Specifically it looks like this line is detecting something is not behaving as it should: I recommended that you open this issue upstream. You can temporarily fix the build locally by overriding the package and setting to .
Also, could you post the rest of the line starting with . It is getting cut off by your pager and seems to contain the actual error from the mount attempt.

}: stdenv.mkDerivation (finalAttrs: { pname = "composefs"; <del> version = "1.0.5"; </del> <ins> version = "1.0.6"; </ins> src = fetchFromGitHub { owner = "containers"; repo = "composefs"; rev = "v${finalAttrs.version}"; <del> hash = "sha256-2h0wwtuhvFz5IExR/Fu0l+/nTAlDpMREVRjgrhbEghw="; </del> <ins> hash = "sha256-9YEY7oTjWwVT2KbzTOOc6sJIGEAkdLSKDf1noF1cYuA="; </ins> }; strictDeps = true; outputs = [ "out" "lib" "dev" ]; postPatch = lib.optionalString installExperimentalTools '' <del> sed -i "s/install : false/install : true/g" tools/meson.build </del> <ins> substituteInPlace tools/meson.build  --replace-fail "install : false" "install : true" </ins> ''; nativeBuildInputs = [ meson ninja go-md2man pkg-config ];


Question: Keeweb opens an empty window, hangs for a few seconds and then the program simply crashes. Looks like a missing libGL dependency. <details<summaryLog without libGL</summary</detailsSteps to reproduce the behavior: Keeweb from Terminal or .desktop file. Keeweb not crashing. Just an empty window with only an icon and title. Can be started with following Command: <details<summaryUsing this overlay to launch it without having to use the terminal.</summary</details<!-- 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]:

<del> { lib , stdenv , fetchurl , undmg , dpkg , autoPatchelfHook , wrapGAppsHook3 , makeWrapper , alsa-lib , at-spi2-atk , gdk-pixbuf , glibc , nss , udev , xorg , gnome-keyring , mesa , gtk3 , libusb1 , libsecret , libappindicator , xdotool }: let pname = "keeweb"; version = "1.18.7"; srcs = { x86_64-linux = fetchurl { url = "https://github.com/keeweb/keeweb/releases/download/v${version}/KeeWeb-${version}.linux.x64.deb"; hash = "sha256-/U+vn5TLIU9/J6cRFjuAdyGzlwC04mp4L2X2ETp+ZSE="; }; x86_64-darwin = fetchurl { url = "https://github.com/keeweb/keeweb/releases/download/v${version}/KeeWeb-${version}.mac.x64.dmg"; hash = "sha256-+ZFGrrw0tZ7F6lb/3iBIyGD+tp1puVhkPv10hfp6ATU="; }; aarch64-darwin = fetchurl { url = "https://github.com/keeweb/keeweb/releases/download/v${version}/KeeWeb-${version}.mac.arm64.dmg"; hash = "sha256-bkhwsWYLkec16vMOfXUce7jfrmI9W2xHiZvU1asebK4="; }; }; src = srcs.${stdenv.hostPlatform.system} or (throw "Unsupported system: ${stdenv.hostPlatform.system}"); libraries = [ alsa-lib at-spi2-atk gdk-pixbuf nss udev xorg.libX11 xorg.libXcomposite xorg.libXext xorg.libXrandr xorg.libXScrnSaver xorg.libXtst xorg.libxshmfence gnome-keyring mesa gtk3 libusb1 libsecret libappindicator xdotool ]; meta = with lib; { description = "Free cross-platform password manager compatible with KeePass"; mainProgram = "keeweb"; homepage = "https://keeweb.info/"; changelog = "https://github.com/keeweb/keeweb/blob/v${version}/release-notes.md"; sourceProvenance = with sourceTypes; [ binaryNativeCode ]; license = licenses.mit; maintainers = with maintainers; [ sikmir ]; platforms = builtins.attrNames srcs; }; in if stdenv.isDarwin then stdenv.mkDerivation { inherit pname version src meta; nativeBuildInputs = [ undmg ]; sourceRoot = "."; installPhase = '' mkdir -p $out/Applications cp -r *.app $out/Applications ''; } else stdenv.mkDerivation { inherit pname version src meta; nativeBuildInputs = [ autoPatchelfHook wrapGAppsHook3 makeWrapper ]; buildInputs = libraries; unpackPhase = '' ${dpkg}/bin/dpkg-deb --fsys-tarfile $src | tar --extract ''; installPhase = '' runHook preInstall mkdir -p $out/bin cp -r usr/share $out/share makeWrapper $out/share/keeweb-desktop/keeweb $out/bin/keeweb  --argv0 "keeweb"  --add-flags "$out/share/keeweb-desktop/resources/app.asar"  --prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath libraries}" runHook postInstall ''; } </del>


Question: Keeweb opens an empty window, hangs for a few seconds and then the program simply crashes. Looks like a missing libGL dependency. <details<summaryLog without libGL</summary</detailsSteps to reproduce the behavior: Keeweb from Terminal or .desktop file. Keeweb not crashing. Just an empty window with only an icon and title. Can be started with following Command: <details<summaryUsing this overlay to launch it without having to use the terminal.</summary</details<!-- 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]:

<ins> { lib, libGL, stdenv, fetchurl, undmg, dpkg, autoPatchelfHook, wrapGAppsHook3, alsa-lib, at-spi2-atk, gdk-pixbuf, nss, udev, gnome-keyring, mesa, gtk3, libusb1, libsecret, libappindicator, xdotool, libX11, libXcomposite, libXext, libXrandr, libXScrnSaver, libXtst, libxshmfence, }: let pname = "keeweb"; version = "1.18.7"; srcs = { x86_64-linux = fetchurl { url = "https://github.com/keeweb/keeweb/releases/download/v${version}/KeeWeb-${version}.linux.x64.deb"; hash = "sha256-/U+vn5TLIU9/J6cRFjuAdyGzlwC04mp4L2X2ETp+ZSE="; }; x86_64-darwin = fetchurl { url = "https://github.com/keeweb/keeweb/releases/download/v${version}/KeeWeb-${version}.mac.x64.dmg"; hash = "sha256-+ZFGrrw0tZ7F6lb/3iBIyGD+tp1puVhkPv10hfp6ATU="; }; aarch64-darwin = fetchurl { url = "https://github.com/keeweb/keeweb/releases/download/v${version}/KeeWeb-${version}.mac.arm64.dmg"; hash = "sha256-bkhwsWYLkec16vMOfXUce7jfrmI9W2xHiZvU1asebK4="; }; }; src = srcs.${stdenv.hostPlatform.system} or (throw "Unsupported system: ${stdenv.hostPlatform.system}"); libraries = [ alsa-lib at-spi2-atk gdk-pixbuf libGL nss udev libX11 libXcomposite libXext libXrandr libXScrnSaver libXtst libxshmfence gnome-keyring mesa gtk3 libusb1 libsecret libappindicator xdotool ]; meta = { description = "Free cross-platform password manager compatible with KeePass"; mainProgram = "keeweb"; homepage = "https://keeweb.info/"; changelog = "https://github.com/keeweb/keeweb/blob/v${version}/release-notes.md"; sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ]; license = lib.licenses.mit; maintainers = with lib.maintainers; [ sikmir ]; platforms = builtins.attrNames srcs; }; in if stdenv.isDarwin then stdenv.mkDerivation { inherit pname version src meta ; nativeBuildInputs = [ undmg ]; sourceRoot = "."; installPhase = '' mkdir -p $out/Applications cp -r *.app $out/Applications ''; } else stdenv.mkDerivation { inherit pname version src meta ; nativeBuildInputs = [ autoPatchelfHook wrapGAppsHook3 ]; buildInputs = libraries; unpackPhase = '' ${dpkg}/bin/dpkg-deb --fsys-tarfile $src | tar --extract ''; installPhase = '' runHook preInstall mkdir -p $out/bin cp -r usr/share $out/share runHook postInstall ''; postFixup = '' makeWrapper $out/share/keeweb-desktop/keeweb $out/bin/keeweb  --argv0 "keeweb"  --add-flags "$out/share/keeweb-desktop/resources/app.asar"  --prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath libraries}"  ''${gappsWrapperArgs[@]} ''; } </ins>


Question: Keeweb opens an empty window, hangs for a few seconds and then the program simply crashes. Looks like a missing libGL dependency. <details<summaryLog without libGL</summary</detailsSteps to reproduce the behavior: Keeweb from Terminal or .desktop file. Keeweb not crashing. Just an empty window with only an icon and title. Can be started with following Command: <details<summaryUsing this overlay to launch it without having to use the terminal.</summary</details<!-- 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]:

keepass-diff = callPackage ../applications/misc/keepass-diff { }; <del> keeweb = callPackage ../applications/misc/keeweb { }; </del> evolution-data-server-gtk4 = evolution-data-server.override { withGtk3 = false; withGtk4 = true; }; evolution-ews = callPackage ../applications/networking/mailreaders/evolution/evolution-ews { }; evolution = callPackage ../applications/networking/mailreaders/evolution/evolution { };


Question:
has an assertion on enableSSL that requires certFile, keyFile, and caFile, but caFile is optional with SSL and only used for client certificate validation. ttyd is able to serve over SSL with valid certificates Steps to reproduce the behavior: builds with the provided options Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've committed a fixed file to my own flake that fixes the assertion (as well as adding the "--ssl" flag, which was missing)
please view

inherit (lib) optionals types <del> concatLists mapAttrsToList </del> mkOption ;


Question:
has an assertion on enableSSL that requires certFile, keyFile, and caFile, but caFile is optional with SSL and only used for client certificate validation. ttyd is able to serve over SSL with valid certificates Steps to reproduce the behavior: builds with the provided options Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've committed a fixed file to my own flake that fixes the assertion (as well as adding the "--ssl" flag, which was missing)
please view

++ optionals (cfg.socket != null) [ "--interface" cfg.socket ] ++ optionals (cfg.interface != null) [ "--interface" cfg.interface ] ++ [ "--signal" (toString cfg.signal) ] <del> ++ (concatLists (mapAttrsToList (_k: _v: [ "--client-option" "${_k}=${_v}" ]) cfg.clientOptions)) </del> <ins> ++ (lib.concatLists (lib.mapAttrsToList (_k: _v: [ "--client-option" "${_k}=${_v}" ]) cfg.clientOptions)) </ins> ++ [ "--terminal-type" cfg.terminalType ] ++ optionals cfg.checkOrigin [ "--check-origin" ] ++ optionals cfg.writeable [ "--writable" ] # the typo is correct ++ [ "--max-clients" (toString cfg.maxClients) ] ++ optionals (cfg.indexFile != null) [ "--index" cfg.indexFile ] ++ optionals cfg.enableIPv6 [ "--ipv6" ] <del> ++ optionals cfg.enableSSL [ "--ssl-cert" cfg.certFile "--ssl-key" cfg.keyFile "--ssl-ca" cfg.caFile ] </del> <ins> ++ optionals cfg.enableSSL [ "--ssl" "--ssl-cert" cfg.certFile "--ssl-key" cfg.keyFile ] ++ optionals ( cfg.enableSSL && cfg.caFile != null ) [ "--ssl-ca" cfg.caFile ] </ins> ++ [ "--debug" (toString cfg.logLevel) ]; in


Question:
has an assertion on enableSSL that requires certFile, keyFile, and caFile, but caFile is optional with SSL and only used for client certificate validation. ttyd is able to serve over SSL with valid certificates Steps to reproduce the behavior: builds with the provided options Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've committed a fixed file to my own flake that fixes the assertion (as well as adding the "--ssl" flag, which was missing)
please view

assertions = [ { assertion = cfg.enableSSL <del> -> cfg.certFile != null && cfg.keyFile != null && cfg.caFile != null; message = "SSL is enabled for ttyd, but no certFile, keyFile or caFile has been specified."; } </del> <ins> -> cfg.certFile != null && cfg.keyFile != null; message = "SSL is enabled for ttyd, but no certFile or keyFile has been specified."; } </ins> { assertion = cfg.writeable != null; message = "services.ttyd.writeable must be set"; } { assertion = ! (cfg.interface != null && cfg.socket != null);


Question: Since Zettlr is an Electron app, it needs to be run with certain command-line arguments on Wayland (specifically ). In NixOS, setting the environment variable to should automatically tell packages to use this command-line argument, but this requires integrating it into the package file (see ) for an example. The Zettlr package does not currently do this, which results in pixelated and glitchy graphics on Wayland unless it is manually run with the correct command-line arguments. This should be a pretty simple fix, as it has been implemented before for many other Electron apps by creating a binary wrapper.

builtins.mapAttrs (pname: attrs: callPackage ./generic.nix (attrs // { inherit pname; })) { zettlr = { <del> version = "3.0.2"; hash = "sha256-xwBq+kLmTth15uLiYWJOhi/YSPZVJNO6JTrKFojSDXA="; </del> <ins> version = "3.2.0"; hash = "sha256-gttDGWFJ/VmOyqgOSKnCqqPtNTKJd1fmDpa0ZAX3xc8="; </ins> }; }


Question: Since Zettlr is an Electron app, it needs to be run with certain command-line arguments on Wayland (specifically ). In NixOS, setting the environment variable to should automatically tell packages to use this command-line argument, but this requires integrating it into the package file (see ) for an example. The Zettlr package does not currently do this, which results in pixelated and glitchy graphics on Wayland unless it is manually run with the correct command-line arguments. This should be a pretty simple fix, as it has been implemented before for many other Electron apps by creating a binary wrapper.

<del> { pname , version , hash , appimageTools , lib , fetchurl </del> <ins> { pname, version, hash, appimageTools, lib, fetchurl, makeWrapper, </ins> }: # Based on https://gist.github.com/msteen/96cb7df66a359b827497c5269ccbbf94 and joplin-desktop nixpkgs.


Question: Since Zettlr is an Electron app, it needs to be run with certain command-line arguments on Wayland (specifically ). In NixOS, setting the environment variable to should automatically tell packages to use this command-line argument, but this requires integrating it into the package file (see ) for an example. The Zettlr package does not currently do this, which results in pixelated and glitchy graphics on Wayland unless it is manually run with the correct command-line arguments. This should be a pretty simple fix, as it has been implemented before for many other Electron apps by creating a binary wrapper.

appimageTools.wrapType2 rec { inherit pname version src; <del> extraPkgs = pkgs: [ pkgs.texliveMedium pkgs.pandoc ]; </del> <ins> extraPkgs = pkgs: [ pkgs.texliveMedium pkgs.pandoc ]; </ins> extraInstallCommands = '' <ins> source "${makeWrapper}/nix-support/setup-hook" wrapProgram $out/bin/zettlr  --add-flags "''${NIXOS_OZONE_WL:+''${WAYLAND_DISPLAY:+--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations}}" </ins> install -m 444 -D ${appimageContents}/Zettlr.desktop $out/share/applications/Zettlr.desktop install -m 444 -D ${appimageContents}/Zettlr.png $out/share/icons/hicolor/512x512/apps/Zettlr.png substituteInPlace $out/share/applications/Zettlr.desktop  <del> --replace 'Exec=AppRun' 'Exec=${pname}' </del> <ins> --replace-fail 'Exec=AppRun' 'Exec=${pname}' </ins> ''; <del> meta = with lib; { </del> <ins> meta = { </ins> description = "Markdown editor for writing academic texts and taking notes"; homepage = "https://www.zettlr.com"; platforms = [ "x86_64-linux" ]; <del> license = licenses.gpl3; maintainers = with maintainers; [ tfmoraes ]; </del> <ins> license = lib.licenses.gpl3; maintainers = with lib.maintainers; [ tfmoraes ]; </ins> mainProgram = "zettlr"; }; }


Question: I'm trying to use GZDoom, but the Vulkan backend isn't working. No errors, but it will silently fall back to OpenGL. Apparently this is the case if GZDoom can't find the correct Vulkan drivers. I have a Radeon RX 5700 XT, so my GPU definitely supports Vulkan. Steps to reproduce the behavior: basic without any mods <kbdesc</kbdthen <kbd~</kbdAt the end of its loading it should say what renderer it is using This is a screenshot of it running with Vulkan from someone else's system: ! This is a screenshot of what it looks like when it's using OpenGL: ! Note the lines. GZDoom uses Vulkan Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

<ins> { lib, stdenv, fetchFromGitHub, makeWrapper, makeDesktopItem, copyDesktopItems, SDL2, bzip2, cmake, fluidsynth, game-music-emu, gtk3, imagemagick, libGL, libjpeg, libsndfile, libvpx, libwebp, mpg123, ninja, openal, pkg-config, vulkan-loader, zlib, zmusic, }: stdenv.mkDerivation rec { pname = "gzdoom"; version = "4.12.2"; src = fetchFromGitHub { owner = "ZDoom"; repo = "gzdoom"; rev = "g${version}"; fetchSubmodules = true; hash = "sha256-taie1Iod3pXvuxxBC7AArmtndkIV0Di9mtJoPvPkioo="; }; outputs = [ "out" "doc" ]; nativeBuildInputs = [ cmake copyDesktopItems imagemagick makeWrapper ninja pkg-config ]; buildInputs = [ SDL2 bzip2 fluidsynth game-music-emu gtk3 libGL libjpeg libsndfile libvpx libwebp mpg123 openal vulkan-loader zlib zmusic ]; postPatch = '' substituteInPlace tools/updaterevision/UpdateRevision.cmake  --replace-fail "ret_var(Tag)" "ret_var("${src.rev}")"  --replace-fail "ret_var(Timestamp)" "ret_var("1970-00-00 00:00:00 +0000")"  --replace-fail "ret_var(Hash)" "ret_var("${src.rev}")"  --replace-fail "<unknown version>" "${src.rev}" ''; cmakeFlags = [ "-DDYN_GTK=OFF" "-DDYN_OPENAL=OFF" ]; desktopItems = [ (makeDesktopItem { name = "gzdoom"; exec = "gzdoom"; desktopName = "GZDoom"; comment = meta.description; icon = "gzdoom"; categories = [ "Game" ]; }) ]; postInstall = '' mv $out/bin/gzdoom $out/share/games/doom/gzdoom makeWrapper $out/share/games/doom/gzdoom $out/bin/gzdoom  --set LD_LIBRARY_PATH ${lib.makeLibraryPath [ vulkan-loader ]} for size in 16 24 32 48 64 128; do mkdir -p $out/share/icons/hicolor/"$size"x"$size"/apps magick $src/src/win32/icon1.ico -background none -resize "$size"x"$size" -flatten  $out/share/icons/hicolor/"$size"x"$size"/apps/gzdoom.png done; ''; meta = { homepage = "https://github.com/ZDoom/gzdoom"; description = "Modder-friendly OpenGL and Vulkan source port based on the DOOM engine"; mainProgram = "gzdoom"; longDescription = '' GZDoom is a feature centric port for all DOOM engine games, based on ZDoom, adding an OpenGL renderer and powerful scripting capabilities. ''; license = lib.licenses.gpl3Plus; platforms = lib.platforms.linux; maintainers = with lib.maintainers; [ azahi lassulus Gliczy ]; }; } </ins>


Question: I'm trying to use GZDoom, but the Vulkan backend isn't working. No errors, but it will silently fall back to OpenGL. Apparently this is the case if GZDoom can't find the correct Vulkan drivers. I have a Radeon RX 5700 XT, so my GPU definitely supports Vulkan. Steps to reproduce the behavior: basic without any mods <kbdesc</kbdthen <kbd~</kbdAt the end of its loading it should say what renderer it is using This is a screenshot of it running with Vulkan from someone else's system: ! This is a screenshot of what it looks like when it's using OpenGL: ! Note the lines. GZDoom uses Vulkan Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

<del> { lib , stdenv , fetchFromGitHub , makeWrapper , makeDesktopItem , copyDesktopItems , SDL2 , bzip2 , cmake , fluidsynth , game-music-emu , gtk3 , imagemagick , libGL , libjpeg , libsndfile , libvpx , libwebp , mpg123 , ninja , openal , pkg-config , vulkan-loader , zlib , zmusic }: stdenv.mkDerivation rec { pname = "gzdoom"; version = "4.12.2"; src = fetchFromGitHub { owner = "ZDoom"; repo = "gzdoom"; rev = "g${version}"; fetchSubmodules = true; hash = "sha256-taie1Iod3pXvuxxBC7AArmtndkIV0Di9mtJoPvPkioo="; }; outputs = [ "out" "doc" ]; nativeBuildInputs = [ cmake copyDesktopItems imagemagick makeWrapper ninja pkg-config ]; buildInputs = [ SDL2 bzip2 fluidsynth game-music-emu gtk3 libGL libjpeg libsndfile libvpx libwebp mpg123 openal vulkan-loader zlib zmusic ]; postPatch = '' substituteInPlace tools/updaterevision/UpdateRevision.cmake  --replace "ret_var(Tag)" "ret_var("${src.rev}")"  --replace "ret_var(Timestamp)" "ret_var("1970-00-00 00:00:00 +0000")"  --replace "ret_var(Hash)" "ret_var("${src.rev}")" ''; cmakeFlags = [ "-DDYN_GTK=OFF" "-DDYN_OPENAL=OFF" ]; desktopItems = [ (makeDesktopItem { name = "gzdoom"; exec = "gzdoom"; desktopName = "GZDoom"; comment = meta.description; icon = "gzdoom"; categories = [ "Game" ]; }) ]; postInstall = '' mv $out/bin/gzdoom $out/share/games/doom/gzdoom makeWrapper $out/share/games/doom/gzdoom $out/bin/gzdoom for size in 16 24 32 48 64 128; do mkdir -p $out/share/icons/hicolor/"$size"x"$size"/apps convert -background none -resize "$size"x"$size" $src/src/win32/icon1.ico -flatten  $out/share/icons/hicolor/"$size"x"$size"/apps/gzdoom.png done; ''; meta = with lib; { homepage = "https://github.com/ZDoom/gzdoom"; description = "Modder-friendly OpenGL and Vulkan source port based on the DOOM engine"; mainProgram = "gzdoom"; longDescription = '' GZDoom is a feature centric port for all DOOM engine games, based on ZDoom, adding an OpenGL renderer and powerful scripting capabilities. ''; license = licenses.gpl3Plus; platforms = platforms.linux; maintainers = with maintainers; [ azahi lassulus ]; }; } </del>


Question: I'm trying to use GZDoom, but the Vulkan backend isn't working. No errors, but it will silently fall back to OpenGL. Apparently this is the case if GZDoom can't find the correct Vulkan drivers. I have a Radeon RX 5700 XT, so my GPU definitely supports Vulkan. Steps to reproduce the behavior: basic without any mods <kbdesc</kbdthen <kbd~</kbdAt the end of its loading it should say what renderer it is using This is a screenshot of it running with Vulkan from someone else's system: ! This is a screenshot of what it looks like when it's using OpenGL: ! Note the lines. GZDoom uses Vulkan Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

eternity = callPackage ../games/doom-ports/eternity-engine { }; <del> gzdoom = callPackage ../games/doom-ports/gzdoom { }; </del> odamex = callPackage ../games/doom-ports/odamex { }; prboom-plus = callPackage ../games/doom-ports/prboom-plus { };


Question:
I noticed that nvim wasn't loading any of my treesitter plugins. I decided to check the plugin directory. hm. something is very wrong here. it isn't pulling in any grammars. let's investigate: ok, so it's looking for a file at . what does the grammar derivation look like? So the parser is ending up at instead of . What does the grammar derivation's source look like? Checking , this code has been in place for years. Checking for , I find It was merged three weeks ago. I see that is open. I couldn't find any information on this problem with GitHub search... Could that PR be merged quicker please? My editor setup is broken now :( system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I think this is not actually the direct cause of the issue you're seeing since the grammars go through (see the below, which precisely corrects the observed discrepancy) You're not seeing the grammars when you because the grammars are in . I explain how to properly build it in The PR is broken, don't get me wrong, but I think not this directly :p. For why your is broken, see I think it's because of your dependency on and which pulls in a without any grammars but I'm not sure. You can try giving an approval, I'm in the same boat as you (I don't have merge permissions). Apologies for breaking your setup!

let inherit (neovimUtils) grammarToPlugin; <del> generatedGrammars = callPackage ./generated.nix { </del> <ins> initialGeneratedGrammars = callPackage ./generated.nix { </ins> inherit (tree-sitter) buildGrammar; }; <ins> grammarOverrides = final: prev: { nix = prev.nix.overrideAttrs { # workaround for https://github.com/NixOS/nixpkgs/issues/332580 prePatch = "rm queries/highlights.scm"; }; }; generatedGrammars = lib.fix (lib.extends grammarOverrides (_: initialGeneratedGrammars)); </ins> generatedDerivations = lib.filterAttrs (_: lib.isDerivation) generatedGrammars;


Question:
I noticed that nvim wasn't loading any of my treesitter plugins. I decided to check the plugin directory. hm. something is very wrong here. it isn't pulling in any grammars. let's investigate: ok, so it's looking for a file at . what does the grammar derivation look like? So the parser is ending up at instead of . What does the grammar derivation's source look like? Checking , this code has been in place for years. Checking for , I find It was merged three weeks ago. I see that is open. I couldn't find any information on this problem with GitHub search... Could that PR be merged quicker please? My editor setup is broken now :( system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I think this is not actually the direct cause of the issue you're seeing since the grammars go through (see the below, which precisely corrects the observed discrepancy) You're not seeing the grammars when you because the grammars are in . I explain how to properly build it in The PR is broken, don't get me wrong, but I think not this directly :p. For why your is broken, see I think it's because of your dependency on and which pulls in a without any grammars but I'm not sure. You can try giving an approval, I'm in the same boat as you (I don't have merge permissions). Apologies for breaking your setup!

# pkgs.vimPlugins.nvim-treesitter.withAllGrammars withPlugins = f: self.nvim-treesitter.overrideAttrs { <del> passthru.dependencies = let grammars = map grammarToPlugin (f (tree-sitter.builtGrammars // builtGrammars)); copyGrammar = grammar: let name = lib.last (lib.splitString "-" grammar.name); in "ln -sf ${grammar}/parser/${name}.so $out/parser/${name}.so"; in [ (runCommand "vimplugin-treesitter-grammars" { meta.platforms = lib.platforms.all; } '' mkdir -p $out/parser ${lib.concatMapStringsSep "n" copyGrammar grammars} '') ]; </del> <ins> passthru.dependencies = map grammarToPlugin (f (tree-sitter.builtGrammars // builtGrammars)); </ins> }; withAllGrammars = withPlugins (_: allGrammars);


Question:
package lists and as dependencies but upstream uses instead. Steps to reproduce the behavior: dependencies of package it to the dependencies listed by upstream and should not be in the dependencies list, but should n/a <!-- 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]:
That's a bot.
Thank you for the quick turnaround!

certifi, cffi, charset-normalizer, <ins> cryptography, </ins> cython, <del> fetchPypi, </del> <ins> fetchFromGitHub, </ins> filelock, idna, keyring, <del> oscrypto, </del> packaging, pandas, platformdirs, pyarrow, <del> pycryptodomex, </del> pyjwt, pyopenssl, <ins> pytest-xdist, pytestCheckHook, </ins> pythonOlder, pytz, requests,


Question:
package lists and as dependencies but upstream uses instead. Steps to reproduce the behavior: dependencies of package it to the dependencies listed by upstream and should not be in the dependencies list, but should n/a <!-- 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]:
That's a bot.
Thank you for the quick turnaround!

sortedcontainers, tomlkit, typing-extensions, <del> wheel, </del> }: buildPythonPackage rec {


Question:
package lists and as dependencies but upstream uses instead. Steps to reproduce the behavior: dependencies of package it to the dependencies listed by upstream and should not be in the dependencies list, but should n/a <!-- 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]:
That's a bot.
Thank you for the quick turnaround!

disabled = pythonOlder "3.8"; <del> src = fetchPypi { pname = "snowflake_connector_python"; inherit version; hash = "sha256-/ZvCqxv1OE0si2W8ALsEdVV9UvBHenESkzSqtT+Wef0="; </del> <ins> src = fetchFromGitHub { owner = "snowflakedb"; repo = "snowflake-connector-python"; rev = "refs/tags/v${version}"; hash = "sha256-A6QnKCROd1vJpFCTrLEoHVo43xojdjpgYS3qQm64gcY="; </ins> }; build-system = [ cython setuptools <del> wheel </del> ]; dependencies = [ asn1crypto certifi cffi charset-normalizer <ins> cryptography </ins> filelock idna <del> oscrypto </del> packaging platformdirs <del> pycryptodomex </del> pyjwt pyopenssl pytz


Question:
package lists and as dependencies but upstream uses instead. Steps to reproduce the behavior: dependencies of package it to the dependencies listed by upstream and should not be in the dependencies list, but should n/a <!-- 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]:
That's a bot.
Thank you for the quick turnaround!

typing-extensions ]; <del> passthru.optional-dependencies = { </del> <ins> optional-dependencies = { </ins> pandas = [ pandas pyarrow


Question:
package lists and as dependencies but upstream uses instead. Steps to reproduce the behavior: dependencies of package it to the dependencies listed by upstream and should not be in the dependencies list, but should n/a <!-- 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]:
That's a bot.
Thank you for the quick turnaround!

secure-local-storage = [ keyring ]; }; <del> # Tests require encrypted secrets, see # https://github.com/snowflakedb/snowflake-connector-python/tree/master/.github/workflows/parameters doCheck = false; </del> <ins> preCheck = '' export HOME=$(mktemp -d) ''; nativeCheckInputs = [ pytest-xdist pytestCheckHook ]; disabledTestPaths = [ # Tests require encrypted secrets, see # https://github.com/snowflakedb/snowflake-connector-python/tree/master/.github/workflows/parameters "test/extras/simple_select1.py" "test/integ" # error getting schema from stream, error code: 0, error info: Expected to # be able to read 19504 bytes for message body but got 19503 "test/unit/test_connection.py" "test/unit/test_cursor.py" "test/unit/test_error_arrow_stream.py" "test/unit/test_ocsp.py" "test/unit/test_retry_network.py" "test/unit/test_s3_util.py" ]; disabledTests = [ # Tests connect to the internet "test_status_when_num_of_chunks_is_zero" "test_test_socket_get_cert" ]; </ins> pythonImportsCheck = [ "snowflake"


Question:
A small difference in the dependencies used by aider and nixpkgs causes aider to crash. aider 0.56.0 something should get a stack overflow See <!-- 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]:
was closed by mistake so opened this
Thanks for opening this issue. Discussion started here It is clear that v1.44.22 of is what causes the issue but I'm not sure what could be done. maybe you have an idea?
There is an open issue in the repo, we have to wait for the dependencies to be updated upstream unfortunately. On the next update of this dependency ill be sure to try to run aider. Sorry for the inconvenience !
Why don't you use ?
the issue on aider's repo was closed the fix is to not use the wrong version of litellm :sweat:
it's not so simple for python packages. each one is a forest of carefully balanced dependencies.
Latest aider update matches with the latest litellm update, so we should be good in a couple of days

self = python3; packageOverrides = _: super: { tree-sitter = super.tree-sitter_0_21; }; }; <del> version = "0.56.0"; </del> <ins> version = "0.57.0"; </ins> in python3.pkgs.buildPythonApplication { pname = "aider-chat";


Question:
A small difference in the dependencies used by aider and nixpkgs causes aider to crash. aider 0.56.0 something should get a stack overflow See <!-- 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]:
was closed by mistake so opened this
Thanks for opening this issue. Discussion started here It is clear that v1.44.22 of is what causes the issue but I'm not sure what could be done. maybe you have an idea?
There is an open issue in the repo, we have to wait for the dependencies to be updated upstream unfortunately. On the next update of this dependency ill be sure to try to run aider. Sorry for the inconvenience !
Why don't you use ?
the issue on aider's repo was closed the fix is to not use the wrong version of litellm :sweat:
it's not so simple for python packages. each one is a forest of carefully balanced dependencies.
Latest aider update matches with the latest litellm update, so we should be good in a couple of days

owner = "paul-gauthier"; repo = "aider"; rev = "refs/tags/v${version}"; <del> hash = "sha256-e0Fqj67vYt41Zbr1FN2fuLp6cHRius8RtacBHLgB9dM="; </del> <ins> hash = "sha256-ErDepSju8B4GochHKxL03aUfOLAiNfTaXBAllAZ144M="; </ins> }; pythonRelaxDeps = true;


Question:
A small difference in the dependencies used by aider and nixpkgs causes aider to crash. aider 0.56.0 something should get a stack overflow See <!-- 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]:
was closed by mistake so opened this
Thanks for opening this issue. Discussion started here It is clear that v1.44.22 of is what causes the issue but I'm not sure what could be done. maybe you have an idea?
There is an open issue in the repo, we have to wait for the dependencies to be updated upstream unfortunately. On the next update of this dependency ill be sure to try to run aider. Sorry for the inconvenience !
Why don't you use ?
the issue on aider's repo was closed the fix is to not use the wrong version of litellm :sweat:
it's not so simple for python packages. each one is a forest of carefully balanced dependencies.
Latest aider update matches with the latest litellm update, so we should be good in a couple of days

pypandoc pyperclip pyyaml <ins> psutil </ins> rich scipy sounddevice


Question: Package name:crow-translate Latest released version:3.0.0 <!-- Search your package here: --- Current version on the unstable channel:2.11.1 Current version on the stable/release channel:2.11.1 <!-- 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]:

{ lib , stdenv <del> , fetchzip </del> <ins> , fetchFromGitLab </ins> , cmake , extra-cmake-modules , qttools


Question: Package name:crow-translate Latest released version:3.0.0 <!-- Search your package here: --- Current version on the unstable channel:2.11.1 Current version on the stable/release channel:2.11.1 <!-- 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]:

, wrapQtAppsHook , gst_all_1 , testers <del> , crow-translate </del> }: <del> stdenv.mkDerivation rec { </del> <ins> stdenv.mkDerivation (finalAttrs: { </ins> pname = "crow-translate"; <del> version = "2.11.1"; </del> <ins> version = "3.0.0"; </ins> <del> src = fetchzip { url = "https://github.com/${pname}/${pname}/releases/download/${version}/${pname}-${version}-source.tar.gz"; hash = "sha256-1rq1pF4tOaZNEaHflxlBuHta80EzD9m3O99geR1EPxE="; </del> <ins> src = fetchFromGitLab { domain = "invent.kde.org"; owner = "office"; repo = "crow-translate"; rev = "v${finalAttrs.version}"; hash = "sha256-hdrhxbv44DlxoF1JU1d2auP/vR8a3IJI+hN7PhdPMaY="; fetchSubmodules = true; </ins> }; postPatch = '' <del> substituteInPlace data/io.crow_translate.CrowTranslate.desktop  --replace "Exec=qdbus" "Exec=${lib.getBin qttools}/bin/qdbus" </del> <ins> substituteInPlace data/org.kde.CrowTranslate.desktop.in  --subst-var-by QT_BIN_DIR ${lib.getBin qttools}/bin </ins> ''; nativeBuildInputs = [


Question: Package name:crow-translate Latest released version:3.0.0 <!-- Search your package here: --- Current version on the unstable channel:2.11.1 Current version on the stable/release channel:2.11.1 <!-- 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]:

''; passthru.tests.version = testers.testVersion { <del> package = crow-translate; </del> <ins> package = finalAttrs.finalPackage; </ins> }; <del> meta = with lib; { </del> <ins> meta = { </ins> description = "Simple and lightweight translator that allows to translate and speak text using Google, Yandex and Bing"; <del> homepage = "https://crow-translate.github.io/"; license = licenses.gpl3Plus; maintainers = with maintainers; [ sikmir ]; platforms = platforms.linux; </del> <ins> homepage = "https://invent.kde.org/office/crow-translate"; license = lib.licenses.gpl3Plus; maintainers = with lib.maintainers; [ sikmir ]; platforms = lib.platforms.linux; </ins> mainProgram = "crow"; }; <del> } </del> <ins> }) </ins>


Question: Package name: rio Latest released version: 0.1.13 <!-- Search your package here: --- Current version on the unstable channel: 0.1.13 Current version on the stable/release channel: 0.0.39 <!-- 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]:

in rustPlatform.buildRustPackage rec { pname = "rio"; <del> version = "0.1.13"; </del> <ins> version = "0.1.15"; </ins> src = fetchFromGitHub { owner = "raphamorim"; repo = "rio"; <del> rev = "refs/tags/v${version}"; hash = "sha256-JrmjQjKpL9di66z4IYTcWhNBL0CgalqOhQgVDpkh6b0="; </del> <ins> rev = "v${version}"; hash = "sha256-aLqWhRaNqi7gMDxBITLU/Tj//h7RURycLSZXOOq83As="; </ins> }; <del> cargoHash = "sha256-KWdkpQY1F0RU3JViFrXEp+JW6xdaofEmp2SlAkzPMPU="; </del> <ins> cargoHash = "sha256-4nqJbz2vauO4jRuUSDjBV1pVrAJMhIP4+eUwS1+GecU="; </ins> nativeBuildInputs = [ ncurses


Question:
The final merged version of isn't building. Just build with the initial configuration that would give on a UEFI machine, along with: Build successfully and boot into Dom0 on next reboot. <img width="1201" alt="image" src=""During the progress of , the issue isn't happening as of . Might be a regression happened in the last few commits before it's merged. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Whoops. That's my bad. Will make a PR in a few.

runtimeEnv = { efiMountPoint = config.boot.loader.efi.efiSysMountPoint; }; <ins> # We disable SC2016 because we don't want to expand the regexes in the sed commands. excludeShellChecks = [ "SC2016" ]; </ins> text = builtins.readFile ./xen-boot-builder.sh; }; in


Question: Package name: paperless-ngx Latest released version: 2.12.1 <!-- Search your package here: --- Current version on the unstable channel: 2.11.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. --

}: let <del> version = "2.11.6"; </del> <ins> version = "2.12.1"; </ins> src = fetchFromGitHub { owner = "paperless-ngx"; repo = "paperless-ngx"; rev = "refs/tags/v${version}"; <del> hash = "sha256-RNX+KS2h9zrOK8QzeQWH55pkNPTDW4gic2HLG+XXLRg="; </del> <ins> hash = "sha256-txqwVGLUel74ObCqwMWSqa4Nd2eDRf0SqAIes5tlMDg="; </ins> }; # subpath installation is broken with uvicorn >= 0.26


Question: Package name: paperless-ngx Latest released version: 2.12.1 <!-- Search your package here: --- Current version on the unstable channel: 2.11.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. --

cd src-ui ''; <del> npmDepsHash = "sha256-ML1Yp3JIMbRF6kVu190ReoY7oDUtUfNkHE7dHF6YUAE="; </del> <ins> npmDepsHash = "sha256-hb2z2cPMTN5bHtUldTR5Mvgo4nZL8/S+Uhfis37gF44="; </ins> nativeBuildInputs = [ pkg-config


Question: Package name: paperless-ngx Latest released version: 2.12.1 <!-- Search your package here: --- Current version on the unstable channel: 2.11.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. --

in python.pkgs.buildPythonApplication rec { pname = "paperless-ngx"; <del> format = "other"; </del> <ins> pyproject = false; </ins> inherit version src; <ins> postPatch = '' # pytest-xdist makes the tests flaky substituteInPlace src/setup.cfg  --replace-fail "--numprocesses auto --maxprocesses=16" "" ''; </ins> nativeBuildInputs = [ gettext xorg.lndir ]; <del> propagatedBuildInputs = with python.pkgs; [ </del> <ins> dependencies = with python.pkgs; [ </ins> bleach channels channels-redis


Question: Package name: paperless-ngx Latest released version: 2.12.1 <!-- Search your package here: --- Current version on the unstable channel: 2.11.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. --

''; installPhase = let <del> pythonPath = python.pkgs.makePythonPath propagatedBuildInputs; </del> <ins> pythonPath = python.pkgs.makePythonPath dependencies; </ins> in '' runHook preInstall


Question: Package name: paperless-ngx Latest released version: 2.12.1 <!-- Search your package here: --- Current version on the unstable channel: 2.11.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. --

makeWrapper $out/lib/paperless-ngx/src/manage.py $out/bin/paperless-ngx  --prefix PYTHONPATH : "${pythonPath}"  --prefix PATH : "${path}" <del> makeWrapper ${python.pkgs.celery}/bin/celery $out/bin/celery  </del> <ins> makeWrapper ${lib.getExe python.pkgs.celery} $out/bin/celery  </ins> --prefix PYTHONPATH : "${pythonPath}:$out/lib/paperless-ngx/src"  --prefix PATH : "${path}"


Question: Package name: paperless-ngx Latest released version: 2.12.1 <!-- Search your package here: --- Current version on the unstable channel: 2.11.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. --

pytest-httpx pytest-mock pytest-rerunfailures <del> pytest-xdist </del> pytestCheckHook ];


Question: No desktop file is installed when installing httpie-desktop. Steps to reproduce the behavior: httpie-desktop. find it in the application list of GNOME. Find it in the application list of GNOME. <!-- 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(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

lib, fetchurl, }: appimageTools.wrapType2 rec { pname = "httpie-desktop"; version = "2024.1.2";


Question: No desktop file is installed when installing httpie-desktop. Steps to reproduce the behavior: httpie-desktop. find it in the application list of GNOME. Find it in the application list of GNOME. <!-- 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(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

hash = "sha256-OOP1l7J2BgO3nOPSipxfwfN/lOUsl80UzYMBosyBHrM="; }; <ins> extraInstallCommands = let contents = appimageTools.extractType2 { inherit pname version src; }; in '' mkdir -p $out/share cp -r ${contents}/usr/share/* $out/share chmod +w $out/share install -Dm644 ${contents}/httpie.desktop $out/share/applications/httpie.desktop substituteInPlace $out/share/applications/httpie.desktop  --replace-fail 'Exec=AppRun' 'Exec=httpie-desktop' ''; </ins> meta = with lib; { description = "Cross-platform API testing client for humans. Painlessly test REST, GraphQL, and HTTP APIs"; homepage = "https://github.com/httpie/desktop";


Question:
python27Packages.faulthandler fails to build on the unstable channel Cc () The output shows test failures due to regular expressions not matching. E.g. It seems that the tests are expecting to see in the message, while the actual error says . If it's just that, I hope that it would be easy to fix the build. I am happy to help if given some guidance. Full output: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs:
This is an upstream issue. See similar issue Best write them that they should also accept , , etc. Then you can open a PR here that adds a patch to the derivation.
Thanks, will look into that. It probably makes sense to keep this issue open to track the upstream one though.
Note that a patch is available ( ), it may make sense to apply it (e.g. done for Fedora ) while waiting for a new release. I am still happy to try and do that.
I don't think that patch will work. It accepts but not .
Sorry, I missed that :(
I opened an upstream PR: And I applied the patch in Nixpkgs:
fyi has now been merged and a release is pending (see )... hopefully we won't need the patch after that. Thanks everyone for your work!
I removed the patches in .

<del> { stdenv, fetchPypi, buildPythonPackage }: </del> <ins> { stdenv, fetchPypi, buildPythonPackage, fetchpatch }: </ins> buildPythonPackage rec { <del> name = "${pname}-${version}"; </del> pname = "faulthandler"; version = "3.0";


Question:
python27Packages.faulthandler fails to build on the unstable channel Cc () The output shows test failures due to regular expressions not matching. E.g. It seems that the tests are expecting to see in the message, while the actual error says . If it's just that, I hope that it would be easy to fix the build. I am happy to help if given some guidance. Full output: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs:
This is an upstream issue. See similar issue Best write them that they should also accept , , etc. Then you can open a PR here that adds a patch to the derivation.
Thanks, will look into that. It probably makes sense to keep this issue open to track the upstream one though.
Note that a patch is available ( ), it may make sense to apply it (e.g. done for Fedora ) while waiting for a new release. I am still happy to try and do that.
I don't think that patch will work. It accepts but not .
Sorry, I missed that :(
I opened an upstream PR: And I applied the patch in Nixpkgs:
fyi has now been merged and a release is pending (see )... hopefully we won't need the patch after that. Thanks everyone for your work!
I removed the patches in .

sha256 = "acc10e10909f0f956ba1b42b6c450ea0bdaaa27b3942899f65931396cfcdd36a"; }; <ins> patches = [ (fetchpatch { url = https://github.com/vstinner/faulthandler/commit/67b661e.patch; sha256 = "1nn8c9nq5qypja949hzz0n4yprsyr63wihf5g3gwrinm2nkjnnv7"; }) (fetchpatch { url = https://github.com/vstinner/faulthandler/commit/07cbb7b.patch; sha256 = "0fh6rjyjw7z1hsiy3sgdc8j9mncg1vlv3y0h4bplqyw18vq3srb3"; }) ]; </ins> meta = { description = "Dump the Python traceback"; license = stdenv.lib.licenses.bsd2;


Question:
Steps to reproduce the behavior: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hydra can reproduce:
I tracked down the potential source of this failure, and am working on a fix. These builds take 30 minutes for me though, so it's slow going.
Please see for a fix. Testing appreciated.
Thanks for the quick patch. EDIT: My way of installing to profile didn't pull the fix, I'll see if I can figure out a way to do it properly using the pr review package
Builds and runs... seg faults as soon as I load a model, but that's an AMD driver thing (whole WM crashes)... Ship it :laughing:
I did see some segfaults, but was able to restart and get it to load on my 6700xt. “Glad” to know it’s known and common.
Nice! Thanks for this - excited to see it roll into unstable soon. Ollama seems to always have some issue - is there a "working group" that has some focus on this program and nix? Anyway, thanks again!
The problems with crashing aren't nix problems, they're crappy amd driver issues. It doesn't crash if you don't load models close to the max vram available... obviously it shouldn't crash if you do, but amd... so yeah

# this also disables necessary patches contained in `ollama/llm/patches/` # those patches are applied in `postPatch` ./disable-git.patch <ins> # we provide our own deps at runtime ./skip-rocm-cp.patch </ins> ]; postPatch = ''


Question:
Steps to reproduce the behavior: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hydra can reproduce:
I tracked down the potential source of this failure, and am working on a fix. These builds take 30 minutes for me though, so it's slow going.
Please see for a fix. Testing appreciated.
Thanks for the quick patch. EDIT: My way of installing to profile didn't pull the fix, I'll see if I can figure out a way to do it properly using the pr review package
Builds and runs... seg faults as soon as I load a model, but that's an AMD driver thing (whole WM crashes)... Ship it :laughing:
I did see some segfaults, but was able to restart and get it to load on my 6700xt. “Glad” to know it’s known and common.
Nice! Thanks for this - excited to see it roll into unstable soon. Ollama seems to always have some issue - is there a "working group" that has some focus on this program and nix? Anyway, thanks again!
The problems with crashing aren't nix problems, they're crappy amd driver issues. It doesn't crash if you don't load models close to the max vram available... obviously it shouldn't crash if you do, but amd... so yeah

<ins> diff --git a/llm/generate/gen_linux.sh b/llm/generate/gen_linux.sh index 48d08fd0..e50f7b36 100755 --- a/llm/generate/gen_linux.sh +++ b/llm/generate/gen_linux.sh @@ -284,9 +284,6 @@ if [ -z "${OLLAMA_SKIP_ROCM_GENERATE}" -a -d "${ROCM_PATH}" ]; then mkdir -p "${ROCM_DIST_DIR}" for dep in $(ldd "${BUILD_DIR}/bin/ollama_llama_server" | grep "=>" | cut -f2 -d= | cut -f2 -d' ' | grep -v "${GOARCH}/rocm${ROCM_VARIANT}" | grep -e rocm -e amdgpu -e libtinfo -e libnuma -e libelf ); do cp -a "${dep}"* "${ROCM_DIST_DIR}" -        if [ $(readlink -f "${dep}") != "${dep}" ] ; then -            cp $(readlink -f "${dep}") "${ROCM_DIST_DIR}" -        fi done install dist </ins>


Question:
It would be nice to see packaged such that at least an executable is exposed.
How about doing it yourself? Have a look at the and at the many examples in If you have questions, just ask them in this thread.

<ins> { python, stdenv }: with python.pkgs; buildPythonApplication rec { pname = "chkcrontab"; version = "1.7"; src = fetchPypi { inherit pname version; sha256 = "0gmxavjkjkvjysgf9cf5fcpk589gb75n1mn20iki82wifi1pk1jn"; }; meta = with stdenv.lib; { description = "A tool to detect crontab errors"; license = licenses.asl20; maintainers = with maintainers; [ ma27 ]; homepage = https://github.com/lyda/chkcrontab; }; } </ins>


Question:
It would be nice to see packaged such that at least an executable is exposed.
How about doing it yourself? Have a look at the and at the many examples in If you have questions, just ask them in this thread.

container-linux-config-transpiler = callPackage ../development/tools/container-linux-config-transpiler { }; <ins> chkcrontab = callPackage ../tools/admin/chkcrontab { }; </ins> djmount = callPackage ../tools/filesystems/djmount { }; dgsh = callPackage ../shells/dgsh { };


Question: fails with the following error since #diff-: on master The systemd build system changed to meson but the systemd-cryptsetup-generator was not updated.

outputs = [ "out" ]; buildPhase = '' <del> make $makeFlags built-sources make $makeFlags systemd-cryptsetup make $makeFlags systemd-cryptsetup-generator </del> <ins> ninja systemd-cryptsetup systemd-cryptsetup-generator </ins> ''; <del> # For some reason systemd-cryptsetup-generator is a wrapper-script # with the current release of systemd. We want the real one. # TODO: Remove `.libs` prefix when the wrapper-script is gone </del> installPhase = '' mkdir -p $out/lib/systemd/ <del> cp .libs/systemd-cryptsetup $out/lib/systemd/systemd-cryptsetup cp .libs/*.so $out/lib/ </del> <ins> cp systemd-cryptsetup $out/lib/systemd/systemd-cryptsetup cp src/shared/*.so $out/lib/systemd/ </ins> mkdir -p $out/lib/systemd/system-generators/ <del> cp .libs/systemd-cryptsetup-generator $out/lib/systemd/system-generators/systemd-cryptsetup-generator </del> <ins> cp systemd-cryptsetup-generator $out/lib/systemd/system-generators/systemd-cryptsetup-generator </ins> ''; })


Question: Neomutt's bundled tool is unable to find . We should probably replace that string in the perl script. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:

enableParallelBuilding = true; postPatch = '' <ins> substituteInPlace contrib/smime_keys  --replace /usr/bin/openssl ${openssl}/bin/openssl </ins> for f in doc/*.{xml,xsl}*  ; do substituteInPlace $f  --replace http://docbook.sourceforge.net/release/xsl/current     ${docbook_xsl}/share/xml/docbook-xsl


Question:
I have a Samsung M2022W (usb) that works on a raspberrypi using raspbian (2017-11-29-raspbian-stretch-). I had to pick the ML-2160 driver in CUPS 2.2.1 as recommended by On NixOS (cups-2.2.2): [nawal nix-info system: "x8664-linux", multi-user?: yes, version: nix-env (Nix) 1.11.16, channels(nawal): "nixos-17.03-17.03.1082.", channels(root): "nixos-17.09.3149.", nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs If I use services.printing = { enable = true; drivers = [ pkgs.samsungUnifiedLinuxDriver ]; extraConf = '' LogLevel debug ''; extraFilesConf = '' FileDevice yes ''; }; and pick the same driver, I get garbage printed out. I tried to track down the ppd on raspbian, but only found: pi $ grep 2160 /usr/share/cups/drv/splix- ModelName "ML-2160" PCFileName "" and (i.e. it generated the ppd when I installed the printer apparently). On nixos: [nawal | grep 2160 /nix/store/6f2zx8dl4w0kzgw3wj8f466mvkcgc3dc-samsung-UnifiedLinuxDriver-4.00.39/opt/share/ppd/ML- /nix/store/nmp023llc8fix567f413a5rqbx4sw45g-cups-progs/share/cups/model/ML- Having diffed them, I notice amongst a huge number of differences: [nawal diff /nix/store/nmp023llc8fix567f413a5rqbx4sw45g-cups-progs/share/cups/model/ML- | grep Version < FileVersion: "2.0.0" < PSVersion: "(3010.000) 0" < QPDL QPDLVersion: "3" < *cupsVersion: 2.2 so raspbian is using a version "2.0.0" and "2.2" of something or other, whereas nixos is using a version "1.2" and "1.1" of similar things. I managed to get my printer to work by copying the ppd across, but I don't understand enough of cups (nor now have the inclination to learn) to figure out what's going on or how to make nixos do the right thing (i.e. in a word, print). I thought this might be useful for someone else who wants to pick it up? Happy to hack around the raspbian if you need more info, or try out things if you need me to while the sd card contains raspbian.
Can you find out what package on Raspbian provides the driver? Have you installed proprietary Samsung driver there? If not, can you try removing ? It seems we have latest version of but not the latest of the proprietary driver but you don't seem to use it.
I'll have a look tomorrow evening - how do i use the new splix without upgrading everything to the same commit?
Find out your current commit with (look at the suffix), then clone nixpkgs repository (), checkout current commit (), fetch my changes () and cherry-pick my patch atop your current commit (). Then you can rebuild nixpkgs with .
I can confirm this works. Thanks for the detailed instructions and for fixing it so quickly! NB: I had to do: (i.e. ) thanks

<del> { stdenv, fetchsvn, fetchurl, cups, zlib }: </del> <ins> { stdenv, fetchsvn, cups, zlib, jbigkit }: </ins> let rev = "315"; in stdenv.mkDerivation rec { name = "splix-svn-${rev}"; src = fetchsvn { # We build this from svn, because splix hasn't been in released in several years # although the community has been adding some new printer models.


Question:
I have a Samsung M2022W (usb) that works on a raspberrypi using raspbian (2017-11-29-raspbian-stretch-). I had to pick the ML-2160 driver in CUPS 2.2.1 as recommended by On NixOS (cups-2.2.2): [nawal nix-info system: "x8664-linux", multi-user?: yes, version: nix-env (Nix) 1.11.16, channels(nawal): "nixos-17.03-17.03.1082.", channels(root): "nixos-17.09.3149.", nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs If I use services.printing = { enable = true; drivers = [ pkgs.samsungUnifiedLinuxDriver ]; extraConf = '' LogLevel debug ''; extraFilesConf = '' FileDevice yes ''; }; and pick the same driver, I get garbage printed out. I tried to track down the ppd on raspbian, but only found: pi $ grep 2160 /usr/share/cups/drv/splix- ModelName "ML-2160" PCFileName "" and (i.e. it generated the ppd when I installed the printer apparently). On nixos: [nawal | grep 2160 /nix/store/6f2zx8dl4w0kzgw3wj8f466mvkcgc3dc-samsung-UnifiedLinuxDriver-4.00.39/opt/share/ppd/ML- /nix/store/nmp023llc8fix567f413a5rqbx4sw45g-cups-progs/share/cups/model/ML- Having diffed them, I notice amongst a huge number of differences: [nawal diff /nix/store/nmp023llc8fix567f413a5rqbx4sw45g-cups-progs/share/cups/model/ML- | grep Version < FileVersion: "2.0.0" < PSVersion: "(3010.000) 0" < QPDL QPDLVersion: "3" < *cupsVersion: 2.2 so raspbian is using a version "2.0.0" and "2.2" of something or other, whereas nixos is using a version "1.2" and "1.1" of similar things. I managed to get my printer to work by copying the ppd across, but I don't understand enough of cups (nor now have the inclination to learn) to figure out what's going on or how to make nixos do the right thing (i.e. in a word, print). I thought this might be useful for someone else who wants to pick it up? Happy to hack around the raspbian if you need more info, or try out things if you need me to while the sd card contains raspbian.
Can you find out what package on Raspbian provides the driver? Have you installed proprietary Samsung driver there? If not, can you try removing ? It seems we have latest version of but not the latest of the proprietary driver but you don't seem to use it.
I'll have a look tomorrow evening - how do i use the new splix without upgrading everything to the same commit?
Find out your current commit with (look at the suffix), then clone nixpkgs repository (), checkout current commit (), fetch my changes () and cherry-pick my patch atop your current commit (). Then you can rebuild nixpkgs with .
I can confirm this works. Thanks for the detailed instructions and for fixing it so quickly! NB: I had to do: (i.e. ) thanks

}; preBuild = '' <del> makeFlags="V=1 DISABLE_JBIG=1 CUPSFILTER=$out/lib/cups/filter CUPSPPD=$out/share/cups/model" </del> <ins> makeFlags="$makeFlags CUPSFILTER=$out/lib/cups/filter CUPSDRV=$out/share/cups/drv" </ins> ''; <del> buildInputs = [cups zlib]; </del> <ins> buildFlags = [ "drv" "all" ]; makeFlags = [ "DRV_ONLY=1" ]; buildInputs = [ cups zlib jbigkit ]; </ins> meta = { <ins> description = "CUPS drivers for SPL (Samsung Printer Language) printers"; </ins> homepage = http://splix.sourceforge.net; platforms = stdenv.lib.platforms.linux; maintainers = [ stdenv.lib.maintainers.peti ];


Question:
When the user of the SSH connection used by the SSH substituter does not have a shell configured it defaults to , which causes the following error: Which actually is the decimal representation of the first few letters of the following error reported by (thanks for figuring that out). Since with the release of Nix 2.0 it has become easy to setup a SSH substituter, so I expect that more people might run into this problem. I know of at least another that reported it on the IRC. Instead of the serialized integer error it should just have reported the actual error, or at least it should have given a more specific error about the response being bogus. Forget to set for the user of the SSH substituter connection. system: host os: multi-user?: sandbox: version: (from nixos-unstable around 5 Mar) channels(root): channels(matthijs): nixpkgs: (nixos-17.09 around 22 Feb)
I some debug echo messages to my profile scripts and I got this error as well (with a different number). To fix it, I had to remove any output from the profiles ...
Just stumbled into this too. I figured should be enough on the server part, but alas.
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
I'm 90% sure this issue is still valid.
It is.
It is.
I marked this as stale due to inactivity. →
Probably still
Made to show a better error message. But I feel that should print its message to stderr instead of stdout...
I just run into this error running
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

{ stdenv, fetchurl, unzip, jdk, makeWrapper }: stdenv.mkDerivation rec { <del> name = "gradle-2.1"; </del> <ins> name = "gradle-2.2.1"; </ins> src = fetchurl { url = "http://services.gradle.org/distributions/${name}-bin.zip"; <del> sha256 = "0y7qifc61nng24zn73bdwh5d0m25dnllfiwfkyw220mblag4zviy"; </del> <ins> sha256 = "420aa50738299327b611c10b8304b749e8d3a579407ee9e755b15921d95ff418"; </ins> }; installPhase = ''


Question:
When the user of the SSH connection used by the SSH substituter does not have a shell configured it defaults to , which causes the following error: Which actually is the decimal representation of the first few letters of the following error reported by (thanks for figuring that out). Since with the release of Nix 2.0 it has become easy to setup a SSH substituter, so I expect that more people might run into this problem. I know of at least another that reported it on the IRC. Instead of the serialized integer error it should just have reported the actual error, or at least it should have given a more specific error about the response being bogus. Forget to set for the user of the SSH substituter connection. system: host os: multi-user?: sandbox: version: (from nixos-unstable around 5 Mar) channels(root): channels(matthijs): nixpkgs: (nixos-17.09 around 22 Feb)
I some debug echo messages to my profile scripts and I got this error as well (with a different number). To fix it, I had to remove any output from the profiles ...
Just stumbled into this too. I figured should be enough on the server part, but alas.
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
I'm 90% sure this issue is still valid.
It is.
It is.
I marked this as stale due to inactivity. →
Probably still
Made to show a better error message. But I feel that should print its message to stderr instead of stdout...
I just run into this error running
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

makeWrapper ${jdk}/bin/java $out/bin/gradle  --set JAVA_HOME ${jdk}  <del> --add-flags "-classpath $out/lib/gradle-launcher-2.1.jar org.gradle.launcher.GradleMain" </del> <ins> --add-flags "-classpath $out/lib/gradle-launcher-2.2.1.jar org.gradle.launcher.GradleMain" </ins> ''; phases = "unpackPhase installPhase";


Question:
It is an intermittent failure, see , not much we can do about it other than restarting the build. I opened an upstream issue
I've now tried doing a third build locally for this: all have failed. That doesn't seem intermittent to me.
It is succeeding for me most of the time, hydra also managed to build it in the past.
Maybe try setting ? Not sure if it will help but it has helped with some derivations in the past.
managed to reproduce it even with parallel building disabled:
Interestingly lowering parallelism is what seems to trigger the issue for me. If I build with all cores (8) it seems to get past that part of the build all the time, I'm yet to see it succeed when building with a single core.
Can confirm that low parallelism is the problem. is building successfully, which is the first time it has worked for me. That's consistent with what I've seen, not having it build successfully a single time (and it has always only used a single core).
I also got the issue when doing a nixos-rebuild on my 2-core laptop, but it succeeded on the same laptop when using nix-build, which means that all cores are available for just webkitgtk. This is the error message I got:
Would it make sense to add the stopgap fix suggested in So something like this: diff diff --git index .. --- +++ -60,6 +60,12 stdenv.mkDerivation rec { "-DENABLEGTKDOC=OFF" ]; postConfigure = '' # A stopgap for a non-deterministic build failure when using only one core # Upstream bug: ninja JavaScriptCoreForwardingHeaders WTFForwardingHeaders ''; NIXCFLAGS_COMPILE = optionalString stdenv.isDarwin " -lintl";
Open the file Add the following in line 258: add_dependencies(LLIntOffsetsExtractor JavaScriptCoreForwardingHeaders)
This will be no longer neccesary with

patchShebangs . ''; <ins> postConfigure = '' # A stopgap for a non-deterministic build failure when using only one core # Upstream bug: https://bugs.webkit.org/show_bug.cgi?id=183788#c4 ninja JavaScriptCoreForwardingHeaders WTFForwardingHeaders ''; </ins> cmakeFlags = [ "-DPORT=GTK" "-DUSE_LIBHYPHEN=0"


Question:
Installing Nixos from the 18.03 minimal installation DVD iso, for a fresh 64-bit Hyper-V vm target system, is failing for me at : Running under strace, there is a possible match at but this was from a quick grep from a lot of content, so might well be a red herring. That path is present in the host (CD-booted) system. Full trace . I tried to follow the vanilla NixOS installation instructions as closely as possible. [This is the installation CD system] system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: In case relevant, the hardware- contents are:
Having the same issue right now.
Getting the same using for a fresh installation attempt. Identical installation steps with succeeds.
Confirmed that also succeeds in my case. :heavycheckmark: :x: :x:
I'm having the same issue on an Acer ES1-132
Yep, here too on an XPS 13 9370
I had the same issue. My workaround was to temporarily set after which the install would succeed but not write the boot-listing efivar. Then I manually created that efivar with efibootmgr. I imagine the command would have worked from the installation media, but I'm not sure since I ran it in Debian. (on my system the EFI boot partition is /dev/sdb9) There were also *.efi files generated in efinixos, but I didn't try any since it booted with this.
I saw this as well, on an AsRock Z77 Extreme4. LSLeary's workaround was fine for me since I prefer to boot via rEFInd anyway. I was able to manually touch or cp another boot entry to the destination (per strace) without any error, so it doesn't seem that the firmware is preventing the creation of the variable.
is anyone actively working on this? what does severity blocker signify?
I know this ticket is for a fresh install, but I installed 17.09 and upgrade 18.03 and it worked fine in case anyone needs a workaround.
Also seeing this when installing on vmware, but with custom install media built from the nixos-18.03channel as of today (). No problems with 17.09. EFI is certainly enabled on the host.
I run into the exact same problem while trying to install NixOS 18.03 into VMware.
I got the same behaviour when I tried to install NixOS 18.03 on Dell XPS 13 (9360).
Same issue when tying a fresh install of nixos-minimal-18.03..-x86_64- on VirtualBox. "EFI" option in virtual machine system settings is enabled. I followed the install instructions as closely as possible.
Cannot perform a clean install on Lenovo X1 Yoga 2018.
I got the same issue when installing NixOS-18.03 () on a recent Intel NUC.
A fix has been pushed to the master and 18.03 branches. It will take some time to reach the channel, and for a new ISO to be generated using the fix, but this specific issue should be fixed soon for new installs. In the meantime, should work. Once installed, the option can be put back to the defaults (removed from your configuration) as the issue only affects the installation environment.
For the record, I was unable to boot using the aforelinked efibootmgr workaround on a 2018 Lenovo X1 Yoga. I had a pre-existing Linux boot entry, which I removed, but the new entry that I did not appear as a startup option.
Alternatively,  can be used with grub, This will put the bootloader in the default fallback location. While it is documented as "hardcoded to try first", I'm not sure this is right. It will, though, try to boot that specific location when no other option is possible. As a final alternative, adding at in the ESP (the fallback location) can help; rEFInd will scan for existing EFI programs on the ESP partitions, which would allow selecting systemd-boot. Though, all of this assumes that the installation process finished. EDIT: For anyone reading this in the (hopefully) few hours left until the channel bumps and the iso updates on the website This build is the iso built in the same evaluation that *
Sorry to drag this from the dead but the website has not updated to the new Isos. the build mentioned by samueldr is complete and the iso there solved this issue on hyper-v for me.
Confirmed (what Wolfereign said) - thanks!
I think this issue was automatically closed by the github merge bot, but shouldn't have been.
4 days ago, it shouldn't have been closed; github doesn't know about nixos channels. The current iso image on is made from commit , which is after , and . Simply put, the 18.03 iso do contain the needed fix for this specific issue. The iso image on the website was updated somewhere between ~24h ago (when the channel advanced) and a couple hours ago when I checked whether the iso image changed. I have also, just in case, verified that it does not reproduce the fixed issue. I'm using this post to add this note:
If I look correctly, the ISO on web has been for over thirty hours now, and that commit does contain . I wonder... can you be more specific? What do you mean by "website has not updated"? EDIT: oh, github didn't show me the last posts when I was writing this :-)
The website is updated now. When I checked at the time of my post the isos on the website (official download links) had not been updated.
Edit: Ignore me. We did something silly with efibootmgr to wipe EFI entries during install, which weirdly enough triggers exactly this error.

exit 126 fi <del> mkdir -m 0755 -p "$mountPoint/dev" </del> <ins> mkdir -m 0755 -p "$mountPoint/dev" "$mountPoint/sys" </ins> mount --rbind /dev "$mountPoint/dev" <ins> mount --rbind /sys "$mountPoint/sys" </ins> # Run the activation script. Set $LOCALE_ARCHIVE to supress some Perl locale warnings. LOCALE_ARCHIVE=$system/sw/lib/locale/locale-archive chroot "$mountPoint" "$system/activate" >&2 || true


Question:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. →
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to

<del> { lib, stdenv, fetchurl, fetchpatch, pkg-config, intltool, xorg, pcre, gst_all_1, glib , xosd, libnotify, enchant, wrapGAppsHook, gdk-pixbuf }: </del> <ins> { stdenv , lib , fetchurl , fetchpatch , autoreconfHook , intltool , pkg-config , wrapGAppsHook , enchant , gdk-pixbuf , glib , gst_all_1 , libnotify , pcre , xorg , xosd }: </ins> stdenv.mkDerivation { <del> pname = "xneur"; version = "0.20.0"; </del> <ins> pname = "xneur"; version = "0.20.0"; </ins> src = fetchurl { url = "https://github.com/AndrewCrewKuznetsov/xneur-devel/raw/f66723feb272c68f7c22a8bf0dbcafa5e3a8a5ee/dists/0.20.0/xneur_0.20.0.orig.tar.gz";


Question:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. →
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to

}; nativeBuildInputs = [ <del> pkg-config intltool wrapGAppsHook </del> <ins> autoreconfHook intltool pkg-config wrapGAppsHook </ins> ]; buildInputs = [ <del> xorg.libX11 xorg.libXtst pcre gst_all_1.gstreamer glib xosd xorg.libXext xorg.libXi libnotify enchant gdk-pixbuf gst_all_1.gst-plugins-base gst_all_1.gst-plugins-good </del> <ins> enchant gdk-pixbuf glib gst_all_1.gst-plugins-base gst_all_1.gst-plugins-good gst_all_1.gstreamer libnotify pcre xorg.libX11 xorg.libXext xorg.libXi xorg.libXtst xosd </ins> ]; patches = [


Question:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. →
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to

url = "https://salsa.debian.org/debian/xneur/-/raw/da38ad9c8e1bf4e349f5ed4ad909f810fdea44c9/debian/patches/gcc-10.patch"; sha256 = "0pc17a4sdrnrc4z7gz28889b9ywqsm5mzm6m41h67j2f5zh9k3fy"; }) <ins> (fetchpatch { name = "enchant2.patch"; url = "https://salsa.debian.org/debian/xneur/-/raw/695b0fea56cde4ff6cf0f3988218c5cb9d7ff5ae/debian/patches/enchant2.patch"; sha256 = "02a3kkfzdvs5f8dfm6j5x3jcn5j8qah9ykfymp6ffqsf4fijp65n"; }) </ins> ]; postPatch = '' <del> sed -e 's@for xosd_dir in@for xosd_dir in ${xosd} @' -i configure </del> <ins> sed -e 's@for xosd_dir in@for xosd_dir in ${xosd} @' -i configure.ac </ins> ''; meta = with lib; {


Question:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. →
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to

<del> { lib, stdenv, fetchurl, aspell, pkg-config, glib, hunspell, hspell }: stdenv.mkDerivation rec { version = "1.6.1"; pname = "enchant"; src = fetchurl { url = "https://github.com/AbiWord/${pname}/releases/download/${pname}-1-6-1/${pname}-${version}.tar.gz"; sha256 = "1xg3m7mniyqyff8qv46jbfwgchb6di6qxdjnd5sfir7jzv0dkw5y"; }; nativeBuildInputs = [ pkg-config ]; buildInputs = [ aspell glib hunspell hspell ]; meta = with lib; { description = "Generic spell checking library"; homepage = "https://abiword.github.io/enchant"; platforms = platforms.unix; badPlatforms = [ "x86_64-darwin" ]; license = licenses.lgpl21; # never built on aarch64-darwin since first introduction in nixpkgs broken = stdenv.isDarwin && stdenv.isAarch64; }; } </del>


Question:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. →
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to

emacsWithPackages = emacs.pkgs.withPackages; # Added 2020-12-18 enblendenfuse = throw "'enblendenfuse' has been renamed to/replaced by 'enblend-enfuse'"; # Converted to throw 2022-02-22 <ins> enchant1 = throw "enchant1 has been removed from nixpkgs, as it was unmaintained"; # Added 2023-01-18 </ins> encryptr = throw "encryptr was removed because it reached end of life"; # Added 2022-02-06 envdir = throw "envdir has been dropped due to the lack of maintenance from upstream since 2018"; # Added 2022-06-03 envelope = throw "envelope has been removed from nixpkgs, as it was unmaintained"; # Added 2021-08-05


Question:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. →
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to

emanote = haskell.lib.compose.justStaticExecutables haskellPackages.emanote; <del> enchant1 = callPackage ../development/libraries/enchant/1.x.nix { }; </del> enchant2 = callPackage ../development/libraries/enchant/2.x.nix { }; enchant = enchant2;


Question:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. →
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to

xmind = callPackage ../applications/misc/xmind { }; <del> xneur = callPackage ../applications/misc/xneur { enchant = enchant1; }; </del> <ins> xneur = callPackage ../applications/misc/xneur { }; </ins> gxneur = callPackage ../applications/misc/gxneur  { inherit (gnome2) libglade GConf;