Question: ])); RemoveIPC = true; RestrictAddressFamilies = [ <del> "AF_UNIX"  # for sd_notify() call </del> <ins> "AF_UNIX" </ins> "AF_INET" "AF_INET6" <ins> "AF_NETLINK" </ins> ]; RestrictNamespaces = true; RestrictRealtime = true;

lists a listener option called that can be used to listen for incoming network connections only on the specified interface. Unfortunately does not accept this option. Steps to reproduce the behavior: This should evaluate cleanly. Incidentally, that assertion message drops the component in the attribute path, it might be nice to fix that.


Question: { lib , buildGoModule , fetchFromGitHub <ins> , fetchYarnDeps , fixup_yarn_lock </ins> , grafana-agent , nixosTests <ins> , nodejs </ins> , stdenv , systemd , testers <ins> , yarn </ins> }: buildGoModule rec {

I started grafana-agent in flow mode, and tried to access the http API at http://localhost:. Unfortunately, instead of providing a web interface to debug the current list of components, I get a "404 page not found". Steps to reproduce the behavior: grafana-agent in flow mode. port via HTTP I'd expect grafana-agent to ship with the web interface. Please run and paste the result.
It looks like is what's building the frontend. Unfortunately, the web interface seems managed by yarn (and has a ), so we'd need to first provide a . I tried to have resolve the dependency, but it seems it's not able to:
I manually patched things in to bump to a more recent version, compatible with the react version that's mentioned in , but ugh, I'm not really sure why it's that way. I'll ask upstream.
yeah, sorry, I don't use flow mode (yet?) and the nixos module does not support it either, as far as I am aware. I can try looking into it as well, first, before you raise an issue upstream. While the nixos module might lack support for it (for now?), I believe we should try fix it nonetheless :)
Yeah, we should probably have a second NixOS module for flow mode, it's very different and the existing config structure doesn't make much sense - for now I just did ship my own custom systemd unit for it: But yeah, without the web ui it's quite annoying to debug, so we should probably get that sorted out first, before providing a module and getting more people to use it.
fyi
I tried to move it over, but still seems to be terribly slow when trying to resolve deps and not being able to, so I guess we should stay with yarn.
We should prefer yarn simply due to upstream having an instead of a :) ^


Question: buildInputs = [ nss nspr libqb ] ++ optional enableDbus dbus <del> ++ optional enableInfiniBandRdma [ librdmacm libibverbs ] </del> <ins> ++ optional enableInfiniBandRdma rdma-core </ins> ++ optional enableMonitoring libstatgrab ++ optional enableSnmp net_snmp;

The packages and are outdated () and have been replaced by the package (). To update a derivation just replace those two packages by as a build input. The following packages depend on and/or : [x] openmpi (fixed in ) [x] (does not find librdmacm in the configure phase when compiled against rdma-core) [x] (infiniband support seems to be defunct. configure does not check for IB libs and it is not linked against any of the required libs, libibverbs or librdmacm) [x] (RDMA support was removed from )


Question: { lib , buildPythonPackage , fetchFromGitHub <del> , setuptools </del> , apispec , boto3 , cachetools

Steps to reproduce the behavior: localstack (from unstable) (version 3.2.0) localstack 2.3.0 works and so does (tagged because you bumped the version) (the channel is slightly messed up. I am using 23.11 but with flakes) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The new version requires too many dependencies to package up in a reasonable time frame and even includes circular ones. contains a revert to 3.0.0 which builds for me and shows the usage. Can you take a look if that works for you?
Sorry for the delay! Yes, the revert works well for me! Thank you!


Question: <ins> { lib , mkYarnPackage , fetchFromGitHub , fetchYarnDeps }: let pname = "ember-cli"; version = "5.3.0"; src = fetchFromGitHub { owner = "ember-cli"; repo = "ember-cli"; rev = "v${version}"; hash = "sha256-xkMsPE+iweIV14m4kE4ytEp4uHMJW6gr+n9oJblr4VQ="; }; in mkYarnPackage { inherit pname version src; offlineCache = fetchYarnDeps { yarnLock = src + "/yarn.lock"; hash = "sha256-QgT2JFvMupJo+pJc13n2lmHMZkROJRJWoozCho3E6+c="; }; packageJSON = ./package.json; meta = with lib; { homepage = "https://github.com/ember-cli/ember-cli"; description = "The Ember.js command line utility"; license = licenses.mit; maintainers = with maintainers; [ jfvillablanca ]; platforms = platforms.all; mainProgram = "ember"; }; } </ins>

ember-cli nodePackage The command line utility. If someone could give us some pointers we might actually have a crack at it ourselves ... Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin


Question: mongoaudit = callPackage ../tools/security/mongoaudit { }; <del> mongodb-compass = callPackage ../tools/misc/mongodb-compass { }; </del> mongodb-tools = callPackage ../tools/misc/mongodb-tools { }; moosefs = callPackage ../tools/filesystems/moosefs { };

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


Question: buildInputs = [ gmp ]; enableParallelBuilding = true; <del> preConfigure = '' cd src ''; </del> <ins> cmakeDir = "../src"; # Running the tests is required to build the *.olean files for the core # library. doCheck = true; postPatch = "patchShebangs ."; </ins> postInstall = stdenv.lib.optionalString stdenv.isDarwin '' substituteInPlace $out/bin/leanpkg

Describe the bug For some reason neither of nix-env, nix-build or nix-shell compile Lean standard library, i.e. there are no .olean files. This results in abysmal performance even on trivial code, because every time it needs to recompile entire library in memory. Also, there is no leanstatic.a installed. To Reproduce Steps to reproduce the behavior: Expected behavior There should be compiled .olean files. Additional context Building Lean manually using compiles standard_library by default without issues. Also, there was no such issue on older NixOS. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Turned out that compiling standard_lib was included in tests. Adding should fix the issue.
Except that 39 tests have failed :disappointed:
This patch fixes all remaining issues, which proves that in NixOS 20.09 expression for Lean is broken:


Question: index 3616104..e9bbfda 100755 --- a/setup.py +++ b/setup.py <del> @@ -112,7 +112,7 @@ class InstallAndUpdateDataDirectory(DistUtilsExtra.auto.install_auto): DistUtilsExtra.auto.install_auto.run(self) target_data = '/' + os.path.relpath(self.install_data, self.root) + '/' </del> <ins> @@ -94,7 +94,7 @@ # Root is undefined if not installing into an alternate root root = self.root or "/" target_data = '/' + os.path.relpath(self.install_data, root) + '/' </ins> -        target_pkgdata = target_data + 'share/ulauncher/' +        target_pkgdata = '@out@/share/ulauncher/' target_scripts = '/' + os.path.relpath(self.install_scripts, <del> self.root) + '/' </del> <ins> root) + '/' </ins>

Describe the bug I'm unsure what the error is, but it seems to relate to ulauncher being unable to find the project path, whatever that may be. To Reproduce Steps to reproduce the behavior: Expected behavior For Ulauncher to start normally Additional context This is the error message I get: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(miyuki): nixpkgs: Maintainer information:
See the PR linked above. The issue is that the ulauncher package must be installed via , , , or something similar. Using does not work (for reasons explained in the patch). The PR both updates ulauncher and adds a note to explain what's going on to Nix users trying out the package. I think it would be a good idea to create a NixOS module for Ulauncher. I might be able to do this after I finish exams in a couple weeks.
Alright guys, the real solution here is to just use rofi. With a little work you can make it look pretty good and with a little extra work one could easily make it look similar to ulauncher. Here is my config I tried to fix this issue up but it seemed to work for maintainers thus it was the end of that story
Hello ulauncher package maintainer here. This definitely shouldn't be the end of the story. I do want to get these issues fixed. The problem is that ulauncher wants to store paths to its assets in a config file within . Typically we'd just let it use paths for everything, but that would cause ulauncher to break if we update the derivation then garbage-collect the old paths in . I also use Rofi right now, and it works. But I really want the plugin ecosystem of Ulauncher, so I'm motivated to fix this situation. Perhaps we could modify the current package to allow decoratively specifying the file contents (like ), which would allow the package to be used without messing with system state? Maybe we could even create something like and a NixOS module?
Perhaps this is a good fit for a home-manager module?


Question: index 3616104..e9bbfda 100755 --- a/setup.py +++ b/setup.py <del> @@ -112,7 +112,7 @@ class InstallAndUpdateDataDirectory(DistUtilsExtra.auto.install_auto): DistUtilsExtra.auto.install_auto.run(self) target_data = '/' + os.path.relpath(self.install_data, self.root) + '/' </del> <ins> @@ -94,7 +94,7 @@ # Root is undefined if not installing into an alternate root root = self.root or "/" target_data = '/' + os.path.relpath(self.install_data, root) + '/' </ins> -        target_pkgdata = target_data + 'share/ulauncher/' +        target_pkgdata = '@out@/share/ulauncher/' target_scripts = '/' + os.path.relpath(self.install_scripts, <del> self.root) + '/' </del> <ins> root) + '/' </ins>

In any case, this issue can probably be closed once is merged. Maybe a new issue should be opened to track the addition of an unlauncher module?
I marked this as stale due to inactivity. →
bad bot
I installed (rev ) through . Unfortunately, I get this error message on launch anyway.
same issue here


Question: rustPlatform.buildRustPackage rec { pname = "pastel"; <del> version = "0.8.0"; </del> <ins> version = "0.8.1"; </ins> src = fetchFromGitHub { owner = "sharkdp"; repo = pname; rev = "v${version}"; <del> sha256 = "00xxrssa3gbr5w2jsqlf632jlzc0lc2rpybnbv618ndy5lxidnw0"; </del> <ins> sha256 = "12n1a9j61r4spx0zi2kk85nslv11j1s510asxqvj92ggqhr2s3sq"; </ins> }; <del> cargoSha256 = "0kkhj58q1lgsyj7hpy3sxg1jva9q51m0i7j60zfzhnjnirwcd0h8"; </del> <ins> cargoSha256 = "12zachbg78ajx1n1mqp53rd00dzcss5cqhsq0119lalzc8b5zkrn"; </ins> buildInputs = lib.optional stdenv.isDarwin Security;

Describe the bug Doesn't build. To Reproduce Steps to reproduce the behavior: Expected behavior Screenshots Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:


Question: qtdeclarative = [ ./qtdeclarative.patch ]; qtscript = [ ./qtscript.patch ]; qtserialport = [ ./qtserialport.patch ]; <del> qtwebengine = [ ] </del> <ins> qtwebengine = [ # Fix build with bison-3.7: https://code.qt.io/cgit/qt/qtwebengine-chromium.git/commit/?id=1a53f599 (fetchpatch { name = "qtwebengine-bison-3.7-build.patch"; url = "https://code.qt.io/cgit/qt/qtwebengine-chromium.git/patch/?id=1a53f599"; sha256 = "1nqpyn5fq37q7i9nasag6i14lnz0d7sld5ikqhlm8qwq9d7gbmjy"; stripLen = 1; extraPrefix = "src/3rdparty/"; }) ] </ins> ++ optional stdenv.isDarwin ./qtwebengine-darwin-no-platform-check.patch; qtwebkit = [ ./qtwebkit.patch ] ++ optionals stdenv.isDarwin [

Describe the bug qtwebengine fails just after successfully configuring with error message To Reproduce ` Expected behavior should compile Notify maintainers Metadata
Pull request works on my machine. Thx.


Question: <ins> { lib , stdenv , fetchFromGitHub , patsh }: stdenv.mkDerivation rec { pname = "csvquote"; version = "0.1.5"; src = fetchFromGitHub { owner = "dbro"; repo = "csvquote"; rev = "v${version}"; hash = "sha256-847JAoDEfA9K4LB8z9cqSw+GTImqmITBylB/4odLDb0="; }; patches = [ # patch csvheader to use csvquote from the derivation ./csvquote-path.patch ]; nativeBuildInputs = [ patsh ]; makeFlags = [ "BINDIR=$(out)/bin" ]; preInstall = '' mkdir -p "$out/bin" ''; postInstall = '' substituteAllInPlace $out/bin/csvheader patsh $out/bin/csvheader -fs ${builtins.storeDir} ''; meta = with lib; { description = "Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines"; homepage = "https://github.com/dbro/csvquote"; license = licenses.mit; maintainers = with maintainers; [ figsoda ]; platforms = platforms.all; }; } </ins>

Project description Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin


Question: grep -l -r '/bin/bash' --null | xargs -0 sed -i -e "s!/bin/bash!${bash}/bin/bash!g" ''; <del> buildInputs = [ jdk ant python2 watchman python2Packages.pywatchman ]; nativeBuildInputs = [ makeWrapper ]; </del> <ins> nativeBuildInputs = [ makeWrapper python3 jdk11 ant watchman ]; </ins> buildPhase = '' <ins> # Set correct version, see https://github.com/facebook/buck/issues/2607 echo v${version} > .buckrelease </ins> ant PYTHONDONTWRITEBYTECODE=true ./bin/buck build -c buck.release_version=${version} buck ''; installPhase = '' <del> install -D -m755 buck-out/gen/programs/buck.pex $out/bin/buck </del> <ins> install -D -m755 buck-out/gen/*/programs/buck.pex $out/bin/buck </ins> wrapProgram $out/bin/buck  <del> --prefix PYTHONPATH : $PYTHONPATH  --prefix PATH : "${lib.makeBinPath [jdk watchman]}" </del> <ins> --prefix PATH : "${lib.makeBinPath [ jdk11 watchman python3 ]}" </ins> ''; meta = with lib; {

Buck as installed via nix reports with an older release version than the one listed in its nixpkgs My guess is that is probably the correct version. The issue here is that IIRC buck Expected behavior 's output should match the version rerefenced in the build file. Notify maintainers
I did try to investigate by bumping buck to its latest release that should be Python3 compatible but didn't get very far as I am unfamiliar with the build system. But maybe the patch helps With this I encountered a failure at the end of the build
buck now generates a hash for build outputs


Question: <del> [Nemo Action] Active=true Name=Open in Pulsar Comment=Open in Pulsar #%U is the current selected file, this will also work on current directory Exec=pulsar -n %U Icon-Name=pulsar Selection=any Extensions=any </del>

Package name: pulsar Latest released version: 1.117.0 Current version on the unstable channel: 1.114.0 Current version on the stable/release channel: 1.117.0 Notify maintainers


Question: "tests/" ]; <del> # See https://github.com/google/jax/issues/9705. disabledTests = lib.optionals usingMKL [ "test_custom_root_with_aux" ]; </del> <ins> # See #  * https://github.com/google/jax/issues/9705 #  * https://discourse.nixos.org/t/getting-different-results-for-the-same-build-on-two-equally-configured-machines/17921 #  * https://github.com/NixOS/nixpkgs/issues/161960 disabledTests = lib.optionals usingMKL [ "test_custom_linear_solve_cholesky" "test_custom_root_with_aux" "testEigvalsGrad_shape" ]; </ins> pythonImportsCheck = [ "jax"

Build of failed on x86_64-linux as of . Maintainer cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:


Question: <del> <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" version="5.0" xml:id="sec-customising-packages"> <title>Customising Packages</title> <para> Some packages in Nixpkgs have options to enable or disable optional functionality or change other aspects of the package. For instance, the Firefox wrapper package (which provides Firefox with a set of plugins such as the Adobe Flash player) has an option to enable the Google Talk plugin. It can be set in <filename>configuration.nix</filename> as follows: <filename> nixpkgs.config.firefox.enableGoogleTalkPlugin = true; </filename> </para> <warning> <para> Unfortunately, Nixpkgs currently lacks a way to query available configuration options. </para> </warning> <para> Apart from high-level options, it’s possible to tweak a package in almost arbitrary ways, such as changing or disabling dependencies of a package. For instance, the Emacs package in Nixpkgs by default has a dependency on GTK 2. If you want to build it against GTK 3, you can specify that as follows: <programlisting> <xref linkend="opt-environment.systemPackages"/> = [ (pkgs.emacs.override { gtk = pkgs.gtk3; }) ]; </programlisting> The function <varname>override</varname> performs the call to the Nix function that produces Emacs, with the original arguments amended by the set of arguments specified by you. So here the function argument <varname>gtk</varname> gets the value <literal>pkgs.gtk3</literal>, causing Emacs to depend on GTK 3. (The parentheses are necessary because in Nix, function application binds more weakly than list construction, so without them, <xref linkend="opt-environment.systemPackages"/> would be a list with two elements.) </para> <para> Even greater customisation is possible using the function <varname>overrideAttrs</varname>. While the <varname>override</varname> mechanism above overrides the arguments of a package function, <varname>overrideAttrs</varname> allows changing the <emphasis>attributes</emphasis> passed to <literal>mkDerivation</literal>. This permits changing any aspect of the package, such as the source code. For instance, if you want to override the source code of Emacs, you can say: <programlisting> <xref linkend="opt-environment.systemPackages"/> = [ (pkgs.emacs.overrideAttrs (oldAttrs: { name = "emacs-25.0-pre"; src = /path/to/my/emacs/tree; })) ]; </programlisting> Here, <varname>overrideAttrs</varname> takes the Nix derivation specified by <varname>pkgs.emacs</varname> and produces a new derivation in which the original’s <literal>name</literal> and <literal>src</literal> attribute have been replaced by the given values by re-calling <literal>stdenv.mkDerivation</literal>. The original attributes are accessible via the function argument, which is conventionally named <varname>oldAttrs</varname>. </para> <para> The overrides shown above are not global. They do not affect the original package; other packages in Nixpkgs continue to depend on the original rather than the customised package. This means that if another package in your system depends on the original package, you end up with two instances of the package. If you want to have everything depend on your customised instance, you can apply a <emphasis>global</emphasis> override as follows: <screen> nixpkgs.config.packageOverrides = pkgs: { emacs = pkgs.emacs.override { gtk = pkgs.gtk3; }; }; </screen> The effect of this definition is essentially equivalent to modifying the <literal>emacs</literal> attribute in the Nixpkgs source tree. Any package in Nixpkgs that depends on <literal>emacs</literal> will be passed your customised instance. (However, the value <literal>pkgs.emacs</literal> in <varname>nixpkgs.config.packageOverrides</varname> refers to the original rather than overridden instance, to prevent an infinite recursion.) </para> </section> </del>

This tracks the conversion of from DocBook to CommonMark per . here that you intend to work on this. (Please also post if you stop working on this.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections in the NixOS and Nixpkgs manual for inspiration. the CommonMark back to DocBook xml with: from nixpkgs root dir with: a preview server with: your work at on steps 5-9. it looks good, commit both the new file and the generated file, submit a PR and reference this issue.


Question: <del> <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" version="5.0" xml:id="sec-customising-packages"> <title>Customising Packages</title> <para> Some packages in Nixpkgs have options to enable or disable optional functionality or change other aspects of the package. For instance, the Firefox wrapper package (which provides Firefox with a set of plugins such as the Adobe Flash player) has an option to enable the Google Talk plugin. It can be set in <filename>configuration.nix</filename> as follows: <filename> nixpkgs.config.firefox.enableGoogleTalkPlugin = true; </filename> </para> <warning> <para> Unfortunately, Nixpkgs currently lacks a way to query available configuration options. </para> </warning> <para> Apart from high-level options, it’s possible to tweak a package in almost arbitrary ways, such as changing or disabling dependencies of a package. For instance, the Emacs package in Nixpkgs by default has a dependency on GTK 2. If you want to build it against GTK 3, you can specify that as follows: <programlisting> <xref linkend="opt-environment.systemPackages"/> = [ (pkgs.emacs.override { gtk = pkgs.gtk3; }) ]; </programlisting> The function <varname>override</varname> performs the call to the Nix function that produces Emacs, with the original arguments amended by the set of arguments specified by you. So here the function argument <varname>gtk</varname> gets the value <literal>pkgs.gtk3</literal>, causing Emacs to depend on GTK 3. (The parentheses are necessary because in Nix, function application binds more weakly than list construction, so without them, <xref linkend="opt-environment.systemPackages"/> would be a list with two elements.) </para> <para> Even greater customisation is possible using the function <varname>overrideAttrs</varname>. While the <varname>override</varname> mechanism above overrides the arguments of a package function, <varname>overrideAttrs</varname> allows changing the <emphasis>attributes</emphasis> passed to <literal>mkDerivation</literal>. This permits changing any aspect of the package, such as the source code. For instance, if you want to override the source code of Emacs, you can say: <programlisting> <xref linkend="opt-environment.systemPackages"/> = [ (pkgs.emacs.overrideAttrs (oldAttrs: { name = "emacs-25.0-pre"; src = /path/to/my/emacs/tree; })) ]; </programlisting> Here, <varname>overrideAttrs</varname> takes the Nix derivation specified by <varname>pkgs.emacs</varname> and produces a new derivation in which the original’s <literal>name</literal> and <literal>src</literal> attribute have been replaced by the given values by re-calling <literal>stdenv.mkDerivation</literal>. The original attributes are accessible via the function argument, which is conventionally named <varname>oldAttrs</varname>. </para> <para> The overrides shown above are not global. They do not affect the original package; other packages in Nixpkgs continue to depend on the original rather than the customised package. This means that if another package in your system depends on the original package, you end up with two instances of the package. If you want to have everything depend on your customised instance, you can apply a <emphasis>global</emphasis> override as follows: <screen> nixpkgs.config.packageOverrides = pkgs: { emacs = pkgs.emacs.override { gtk = pkgs.gtk3; }; }; </screen> The effect of this definition is essentially equivalent to modifying the <literal>emacs</literal> attribute in the Nixpkgs source tree. Any package in Nixpkgs that depends on <literal>emacs</literal> will be passed your customised instance. (However, the value <literal>pkgs.emacs</literal> in <varname>nixpkgs.config.packageOverrides</varname> refers to the original rather than overridden instance, to prevent an infinite recursion.) </para> </section> </del>

This tracks the conversion of from Docbook to CommonMark per . here that you intend to work on this. (Please also post if you stop working on this.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections in the NixOS and Nixpkgs manual for inspiration. the CommonMark back to DocBook xml with: from nixpkgs root dir with: a preview server with: your work at on steps 5-9. it looks good, commit both the new file and the generated file, submit a PR and reference this issue.
I opened a PR for and : PTAL, thanks in advance for reviewing :-)


Question: <ins> #!/usr/bin/env nix-shell #!nix-shell -i bash -p curl gojq nix-prefetch-github common-updater-scripts set -eou pipefail pkg_dir="$(dirname "$0")" gh-curl () { curl --silent ${GITHUB_TOKEN:+-u ":$GITHUB_TOKEN"} "$1" } version="$(gh-curl "https://api.github.com/repos/ente-io/ente/releases" | gojq 'map(select(.draft == false and .prerelease == false and (.tag_name | startswith("auth-v")))) | first | .tag_name' --raw-output)" short_version="${version:6}" if [[ "$short_version" == "$UPDATE_NIX_OLD_VERSION" ]]; then echo "ente-auth is already up-to-date: $short_version" exit 0 fi echo "Updating to $short_version" # Subtree needed for lockfile and icons auth_tree="$(gh-curl "https://api.github.com/repos/ente-io/ente/git/trees/$version" | gojq '.tree[] | select(.path == "auth") | .url' --raw-output)" # Get lockfile, filter out incompatible sqlite dependency and convert to JSON echo "Updating lockfile" pubspec_lock="$(gh-curl "$auth_tree" | gojq '.tree[] | select(.path == "pubspec.lock") | .url' --raw-output)" gh-curl "$pubspec_lock" | gojq '.content | @base64d' --raw-output | gojq --yaml-input 'del(.packages.sqlite3_flutter_libs)' > "$pkg_dir/pubspec.lock.json" # Get rev and hash of simple-icons submodule echo "Updating icons" assets_tree="$(gh-curl "$auth_tree" | gojq '.tree[] | select(.path == "assets") | .url' --raw-output)" simple_icons_rev="$(gh-curl "$assets_tree" | gojq '.tree[] | select(.path == "simple-icons") | .sha' --raw-output)" nix-prefetch-github --rev "$simple_icons_rev" simple-icons simple-icons > "$pkg_dir/simple-icons.json" # Update package version and hash echo "Updating package source" update-source-version ente-auth "$short_version" --file="$pkg_dir/package.nix" </ins>

Project description Ente's 2FA app. An end-to-end encrypted, cross platform and free app for storing your 2FA codes with cloud backups. Works offline. You can even use it without signing up for an account if you don't want the cloud backups or multi-device sync. Metadata homepage URL: source URL: license: AGPL-3.0 license platforms: linux, windows, android, ios, apple silicon macOS, web Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: sha256 = "0pnva72f2w4jcgnl1y7nw5rdly4ipx3hji4c9yc9s0hna1n2ijxn"; }; <del> buildInputs = [ libxml2 postgresql geos proj gdal json_c protobufc ]; </del> <ins> buildInputs = [ libxml2 postgresql geos proj gdal json_c protobufc ] ++ stdenv.lib.optional stdenv.isDarwin libiconv; </ins> nativeBuildInputs = [ perl pkgconfig ]; dontDisableStatic = true;

Describe the bug has , preventing it from being used on other platforms, particularly Darwin in my case. To Reproduce nix-shell to get this error: error: Package ‘postgis-2.5.2’ in is not supported on ‘x8664-darwin’, refusing to evaluate. Expected behavior Produce a postgresql-and-plugins package with postgis available. Additional context Simply allowing doesn't work immediately because PostGIS' build system is quirky. There was some relevant-looking discussion on . Metadata system: host os: multi-user?: sandbox: version: channels(lukeworth): nixpkgs:


Question: necessary, but outside the scope of the Mailman module. </para> </section> <ins> <section xml:id="module-services-mailman-other-mtas"> <title>Using with other MTAs</title> <para> Mailman also supports other MTA, though with a little bit more configuration. For example, to use Mailman with Exim, you can use the following settings: <programlisting>{ config, ... }: { services = { mailman = { enable = true; siteOwner = "mailman@example.org"; <link linkend="opt-services.mailman.enablePostfix">enablePostfix</link> = false; settings.mta = { incoming = "mailman.mta.exim4.LMTP"; outgoing = "mailman.mta.deliver.deliver"; lmtp_host = "localhost"; lmtp_port = "8024"; smtp_host = "localhost"; smtp_port = "25"; configuration = "python:mailman.config.exim4"; }; }; exim = { enable = true; # You can configure Exim in a separate file to reduce configuration.nix clutter config = builtins.readFile ./exim.conf; }; }; }</programlisting> </para> <para> The exim config needs some special additions to work with Mailman. Currently NixOS can't manage Exim config with such granularity. Please refer to <link xlink:href="https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html">Mailman documentation</link> for more info on configuring Mailman for working with Exim. </para> </section> </ins> </chapter>

Describe the bug Mailman module in NixOS requires postfix enabled and has no way to configure Mailman to work with other MTAs supported by both NixOS and mailman upstream. To Reproduce Steps to reproduce the behavior: postfix mailman the evaluation with an assertion Expected behavior The Mailman module allows to select an MTA of choice (or even adapts to the currently enabled MTA) Screenshots n/a Additional context Notify maintainers cc Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(vika): nixpkgs: Maintainer information:
It looks like exim's configuration should be RFC42-ised first if we want to inject Mailman-related settings into Exim config, which is a requirement (Mailman requires a custom Exim router and transport).
Yes, the module is currently quite opinionated. If you're willing to contribute exim support that's great.
I see how I could make it work, but the first version of it will require manual editing of Exim's config files (because RFC42-ising Exim will be a pain, even though I have some drafts on how to translate Nix into the syntax that's required), and I'm not sure if it will be merge-worthy enough :3
Exim config is complicated enough as is, I'm not sure adding an intermediate layer from nix will help that much. I also don't really see this integrating well with existing or other exim config. I'm honestly kind of surprised this works for postfix.


Question: usb-devices = callPackage ../development/python-modules/usb-devices { }; <ins> usb-monitor = callPackage ../development/python-modules/usb-monitor { }; </ins> usbrelay-py = callPackage ../os-specific/linux/usbrelay/python.nix { }; usbtmc = callPackage ../development/python-modules/usbtmc { };

Project description As discussed in is now EOL and the dev's have moved their effort to . As per the in order for it to work specific need to be set up. We can probably do something similar to what we do for the expression: Metadata homepage URL: source URL: license: GPL3 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
For people who subscribed to this issue: I opened to add streamcontroller


Question: sed -E "s#(libEGL_nvidia)#$i/lib/1#" 10_nvidia.json > 10_nvidia.json.fixed sed -E "s#(libnvidia-egl-wayland)#$i/lib/1#" 10_nvidia_wayland.json > 10_nvidia_wayland.json.fixed <del> install -Dm644 10_nvidia.json.fixed $i/share/glvnd/egl_vendor.d/nvidia.json install -Dm644 10_nvidia_wayland.json.fixed $i/share/glvnd/egl_vendor.d/nvidia_wayland.json </del> <ins> install -Dm644 10_nvidia.json.fixed $i/share/glvnd/egl_vendor.d/10_nvidia.json install -Dm644 10_nvidia_wayland.json.fixed $i/share/egl/egl_external_platform.d/10_nvidia_wayland.json if [[ -f "15_nvidia_gbm.json" ]]; then sed -E "s#(libnvidia-egl-gbm)#$i/lib/1#" 15_nvidia_gbm.json > 15_nvidia_gbm.json.fixed install -Dm644 15_nvidia_gbm.json.fixed $i/share/egl/egl_external_platform.d/15_nvidia_gbm.json mkdir -p $i/lib/gbm ln -s $i/lib/libnvidia-allocator.so $i/lib/gbm/nvidia-drm_gbm.so fi </ins> fi done

Yes. We have a package which is what I tried, but since it’s a thin wrapper around it’s possible that it’s still not built with the right options. Also I’ve noticed these messages from : does not show the extension, and GLX applications fail to start. Originally posted by in I probably merged , too early. I'm not totally sure this is working properly.
This is pretty much a help wanted because I lack the depth of knowledge and hardware to help anymore with Nvidia things. My goal with finishing was that it could be possible and improved upon. i.e packages are built with the capability etc.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
The last few evenings, I have tinkered around a bit. I was not successful so far. Here are my findings: I have set the following options: This page says that there is no acceleration support for xwayland and nvidia yet but glxgears fails to start, so I think this is another issue There are multiple versions of : One from the egl-wayland package, the other from nvidia-x11 package. As the one in is loaded, I tried to replace it with the one from egl-wayland. Though, the result is the same with both. When starting an application, which would use acceleration, I can observe this line in the kernel log: Using , I can see that is accessed, though one of the calls fails: one more thing: looking at , gnome-shell is listed. Maybe it has working acceleration? Edit: Got a bit further: Found a reference to an additional directory, which is used to look up libraries: Creating a file in there: with the file in /run/opengl-driver/lib/libnvidia-egl- being replaced by the one from egl-wayland package. Now the error in xwayland is just a warning: I can run a wayland native terminal, but still fails If you have any suggestions, what to try next, I would be glad to give it a try.
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant.


Question: sed -E "s#(libEGL_nvidia)#$i/lib/1#" 10_nvidia.json > 10_nvidia.json.fixed sed -E "s#(libnvidia-egl-wayland)#$i/lib/1#" 10_nvidia_wayland.json > 10_nvidia_wayland.json.fixed <del> install -Dm644 10_nvidia.json.fixed $i/share/glvnd/egl_vendor.d/nvidia.json install -Dm644 10_nvidia_wayland.json.fixed $i/share/glvnd/egl_vendor.d/nvidia_wayland.json </del> <ins> install -Dm644 10_nvidia.json.fixed $i/share/glvnd/egl_vendor.d/10_nvidia.json install -Dm644 10_nvidia_wayland.json.fixed $i/share/egl/egl_external_platform.d/10_nvidia_wayland.json if [[ -f "15_nvidia_gbm.json" ]]; then sed -E "s#(libnvidia-egl-gbm)#$i/lib/1#" 15_nvidia_gbm.json > 15_nvidia_gbm.json.fixed install -Dm644 15_nvidia_gbm.json.fixed $i/share/egl/egl_external_platform.d/15_nvidia_gbm.json mkdir -p $i/lib/gbm ln -s $i/lib/libnvidia-allocator.so $i/lib/gbm/nvidia-drm_gbm.so fi </ins> fi done

This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
I'm trying to get this working as well. However I can't even get the session chooser in GDM in 20.09. Is it only working in unstable? Any tips? Here's my config
With this overlay and the 470.42.01 driver, nvidia is usable with xwayland. :tada: , unigene-valley and so far every game I started on Steam. Only issues I have so far are that chrome does not start properly Workaround is to start it with some options: and in CSGO there is noticeable input delay.
I've updated to the latest nixos-unstable () which includes updated & , but I'm still facing issues. While it's generally working I have problems with some apps. : : : Additionally in my system logs I can see: & are both working. My relevant config: I also tried using an overlay to apply the new meson flags from overlay: Is there anything else I need to set up?
also fails with
I have a very similar setup as and am experiencing precisely the same errors. I'm not sure whether it's an issue with gnome, my particular config, or what. Things work fine when running in an X session.
:thinking: I don't see anything missing with your config . I have updated my config to and removed the overlay. and are producing the same errors, and chrome won't function properly unless started with and are working for me, as well as and and . Note: Seam is installed via but this should only be relevant for running games inside steam, not steam itself.


Question: sed -E "s#(libEGL_nvidia)#$i/lib/1#" 10_nvidia.json > 10_nvidia.json.fixed sed -E "s#(libnvidia-egl-wayland)#$i/lib/1#" 10_nvidia_wayland.json > 10_nvidia_wayland.json.fixed <del> install -Dm644 10_nvidia.json.fixed $i/share/glvnd/egl_vendor.d/nvidia.json install -Dm644 10_nvidia_wayland.json.fixed $i/share/glvnd/egl_vendor.d/nvidia_wayland.json </del> <ins> install -Dm644 10_nvidia.json.fixed $i/share/glvnd/egl_vendor.d/10_nvidia.json install -Dm644 10_nvidia_wayland.json.fixed $i/share/egl/egl_external_platform.d/10_nvidia_wayland.json if [[ -f "15_nvidia_gbm.json" ]]; then sed -E "s#(libnvidia-egl-gbm)#$i/lib/1#" 15_nvidia_gbm.json > 15_nvidia_gbm.json.fixed install -Dm644 15_nvidia_gbm.json.fixed $i/share/egl/egl_external_platform.d/15_nvidia_gbm.json mkdir -p $i/lib/gbm ln -s $i/lib/libnvidia-allocator.so $i/lib/gbm/nvidia-drm_gbm.so fi </ins> fi done

I came here because I'm experiencing the same as and Can't launch Steam or Kitty under Wayland: nvidia: 470.42.01 xwayland: 21.1.2 Config is virtually identical to
I found this issue because I had the same problem as After reading , I tried to create a different file (listed in the end). And that solved my problem. With this file, I can open steam. However, alacritty still has an error. Maybe that relates to another . The cause of this problem is that even though both and packages provide , cannot be found without a json file. The says: So, maybe we should add a json file /usr/share/egl/eglexternalplatform.d /xxx.jsonnvidia-x11egl-waylandlibnvidia-egl-wayland.solibnvidia-egl-, gnome setting says my video card is "Unknown". In the end, I will post my related config:
I filed this issue to see if we can patch to look in the right place: If we can't get it to look in then we should probably just add the etc symlink in the nixos module so that this works correctly for end users out of the box. I'll send an initial PR shortly and will update it in that egl-wayland issue gets a useful answer (or if there's another way to patch a closed source SO that I'm not thinking of).
BTW, I can confirm the different results. When I override nvidia's with our "upstream" one, I get more info in , but I'm not sure if there are other functional differences. Not sure what I would've expected, but it nags me that there's a difference.
PR:
Interesting, there IS a way to override the egl_externaplatform search path(s):
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
would this still be an issue after ?
I think it needs and
I am taking over as I've been using that setup as a daily driver and have a rough working understanding of the pieces fitting together. And to confirm, the general problem here, that is addressed in , is EGLStreams working in Wayland environment with the NVIDIA driver (aka, it doesn't now because we don't "wire up" NVIDIA's egl driver per egl-wayland's expectations).


Question: sed -E "s#(libEGL_nvidia)#$i/lib/1#" 10_nvidia.json > 10_nvidia.json.fixed sed -E "s#(libnvidia-egl-wayland)#$i/lib/1#" 10_nvidia_wayland.json > 10_nvidia_wayland.json.fixed <del> install -Dm644 10_nvidia.json.fixed $i/share/glvnd/egl_vendor.d/nvidia.json install -Dm644 10_nvidia_wayland.json.fixed $i/share/glvnd/egl_vendor.d/nvidia_wayland.json </del> <ins> install -Dm644 10_nvidia.json.fixed $i/share/glvnd/egl_vendor.d/10_nvidia.json install -Dm644 10_nvidia_wayland.json.fixed $i/share/egl/egl_external_platform.d/10_nvidia_wayland.json if [[ -f "15_nvidia_gbm.json" ]]; then sed -E "s#(libnvidia-egl-gbm)#$i/lib/1#" 15_nvidia_gbm.json > 15_nvidia_gbm.json.fixed install -Dm644 15_nvidia_gbm.json.fixed $i/share/egl/egl_external_platform.d/15_nvidia_gbm.json mkdir -p $i/lib/gbm ln -s $i/lib/libnvidia-allocator.so $i/lib/gbm/nvidia-drm_gbm.so fi </ins> fi done

That is pretty tangential to NVIDIA having a driver that supports GBM allocation and "wiring it up" (an extra piece included in ), and it being discoverable (whatever I send to replace ). Hope that helps.
Also, to reiterate, is good to merge independently on it's own and will resolve this issue. Separately, a replacement for will be necessary for the ideal Sway scenario without users having to set an extra env var.
I thought the point of the new Nvidia driver was to finally move away from EGLStreams? Is EGLStreams used by the new stable driver at all?
I don't know? It doesn't really matter, we should still fix it? Like, the fundamental issue is that we're simply not installing the Nvidia driver correctly for NixOS when it comes to these important configuration JSON files. Plus, it's not like everything is going to immediately switch to GBM, drop EGL, know about the env var, on and on. That, and the wiring for GBM is in that PR and I'm not splitting them apart at the current merge rate.


Question: nativeBuildInputs = [ pkgconfig ]; buildInputs = [ igraph ]; <ins> propagatedBuildInputs = [ texttable ]; </ins> src = fetchPypi { inherit pname version; sha256 = "4601638d7d22eae7608cdf793efac75e6c039770ec4bd2cecf76378c84ce7d72"; }; <ins> # NB: We want to use our igraph, not vendored igraph, but even with # pkg-config on the PATH, their custom setup.py still needs to be explicitly # told to do it. ~ C. setupPyGlobalFlags = [ "--use-pkg-config" ]; </ins> doCheck = !isPy3k; meta = {

, CVSSv3=6.5 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc
I couldn't get the vulnerability to compile and run, so I don't know for sure whether this version bump is actually a fix. Nonetheless, here's a PR.


Question: nativeBuildInputs = [ pkgconfig ]; buildInputs = [ igraph ]; <ins> propagatedBuildInputs = [ texttable ]; </ins> src = fetchPypi { inherit pname version; sha256 = "4601638d7d22eae7608cdf793efac75e6c039770ec4bd2cecf76378c84ce7d72"; }; <ins> # NB: We want to use our igraph, not vendored igraph, but even with # pkg-config on the PATH, their custom setup.py still needs to be explicitly # told to do it. ~ C. setupPyGlobalFlags = [ "--use-pkg-config" ]; </ins> doCheck = !isPy3k; meta = {

Describe the bug Build fails when trying to install . I get: To Reproduce Expected behavior The package should install without error. Metadata Maintainer information:
cc
Related to
Tried the following: It doesn't even bother about the C-core Version 6 that I asked: What am I doing wrong ?
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 .
Refreshed. My PR will fix this issue. Thanks for your patience.


Question: <del> From 28a27bdbb9500797e6767f80c8128b09112aeed5 Mon Sep 17 00:00:00 2001 From: "H.J. Lu" <hjl.tools@gmail.com> Date: Sat, 11 Aug 2018 06:41:33 -0700 Subject: [PATCH] x86: Properly add X86_ISA_1_NEEDED property Existing properties may be removed during property merging.  We avoid adding X86_ISA_1_NEEDED property only if existing properties won't be removed. bfd/ PR ld/23428 * elfxx-x86.c (_bfd_x86_elf_link_setup_gnu_properties): Don't add X86_ISA_1_NEEDED property only if existing properties won't be removed. ld/ PR ld/23428 * testsuite/ld-elf/dummy.s: New file. * testsuite/ld-elf/linux-x86.S: Add X86_FEATURE_1_AND property. * testsuite/ld-elf/linux-x86.exp: Add dummy.s to pr23428. (cherry picked from commit ab9e342807d132182892de1be1a92d6e91a5c1da) --- bfd/elfxx-x86.c                   | 28 ++++++++++++++++++++++------ ld/testsuite/ld-elf/dummy.s       |  1 + ld/testsuite/ld-elf/linux-x86.S   | 28 ++++++++++++++++++++++++++++ ld/testsuite/ld-elf/linux-x86.exp |  2 +- 6 files changed, 66 insertions(+), 7 deletions(-) create mode 100644 ld/testsuite/ld-elf/dummy.s diff --git a/bfd/elfxx-x86.c b/bfd/elfxx-x86.c index 7ccfd25815..2d8f7b640b 100644 --- a/bfd/elfxx-x86.c +++ b/bfd/elfxx-x86.c @@ -2588,7 +2588,6 @@ _bfd_x86_elf_link_setup_gnu_properties prop->pr_kind = property_number; } else if (has_text -	       && elf_properties (ebfd) == NULL && elf_tdata (info->output_bfd)->o->build_id.sec == NULL && !htab->elf.dynamic_sections_created && !info->traditional_format @@ -2598,11 +2597,28 @@ _bfd_x86_elf_link_setup_gnu_properties /* If the separate code program header is needed, make sure that the first read-only PT_LOAD segment has no code by adding a GNU_PROPERTY_X86_ISA_1_NEEDED note.  */ -	  prop = _bfd_elf_get_property (ebfd, -					GNU_PROPERTY_X86_ISA_1_NEEDED, -					4); -	  prop->u.number = GNU_PROPERTY_X86_ISA_1_486; -	  prop->pr_kind = property_number; +	  elf_property_list *list; +	  bfd_boolean need_property = TRUE; + +	  for (list = elf_properties (ebfd); list; list = list->next) +	    switch (list->property.pr_type) +	      { +	      case GNU_PROPERTY_STACK_SIZE: +	      case GNU_PROPERTY_NO_COPY_ON_PROTECTED: +	      case GNU_PROPERTY_X86_ISA_1_NEEDED: +		/* These properties won't be removed during merging.  */ +		need_property = FALSE; +		break; +	      } + +	  if (need_property) +	    { +	      prop = _bfd_elf_get_property (ebfd, +					    GNU_PROPERTY_X86_ISA_1_NEEDED, +					    4); +	      prop->u.number = GNU_PROPERTY_X86_ISA_1_486; +	      prop->pr_kind = property_number; +	    } } /* Create the GNU property note section if needed.  */ diff --git a/ld/testsuite/ld-elf/dummy.s b/ld/testsuite/ld-elf/dummy.s new file mode 100644 index 0000000000..403f98000d --- /dev/null +++ b/ld/testsuite/ld-elf/dummy.s @@ -0,0 +1 @@ +# Dummy diff --git a/ld/testsuite/ld-elf/linux-x86.S b/ld/testsuite/ld-elf/linux-x86.S index bdf40c6e01..d94abc1106 100644 --- a/ld/testsuite/ld-elf/linux-x86.S +++ b/ld/testsuite/ld-elf/linux-x86.S @@ -61,3 +61,31 @@ syscall: ret			/* Return to caller.  */ .size syscall, .-syscall .section .note.GNU-stack,"",@progbits + +	.section ".note.gnu.property", "a" +#ifdef __LP64__ +	.p2align 3 +#else +	.p2align 2 +#endif +	.long 1f - 0f		/* name length */ +	.long 5f - 2f		/* data length */ +	.long 5			/* note type */ +0:	.asciz "GNU"		/* vendor name */ +1: +#ifdef __LP64__ +	.p2align 3 +#else +	.p2align 2 +#endif +2:	.long 0xc0000002	/* pr_type.  */ +	.long 4f - 3f		/* pr_datasz.  */ +3: +	.long 0x2 +4: +#ifdef __LP64__ +	.p2align 3 +#else +	.p2align 2 +#endif +5: diff --git a/ld/testsuite/ld-elf/linux-x86.exp b/ld/testsuite/ld-elf/linux-x86.exp index 36217c6fb4..f6f5a80853 100644 --- a/ld/testsuite/ld-elf/linux-x86.exp +++ b/ld/testsuite/ld-elf/linux-x86.exp @@ -37,7 +37,7 @@ run_ld_link_exec_tests [list  "Run PR ld/23428 test"  "--no-dynamic-linker -z separate-code"  ""  -	{ linux-x86.S pr23428.c }  +	{ linux-x86.S pr23428.c dummy.s }  "pr23428"  "pass.out"  "$NOPIE_CFLAGS -fno-asynchronous-unwind-tables"  -- 2.20.1 </del>

Describe the bug is currently in nixpkgs master. It was released in July 2018. was released in October 2019. It contains a few improvements and may also contains fix for some vulnerabilities: Is there a reason to keep the old version in nixpkgs, other than a lack of manpower? I'd be happy to do this work, but I just want to be sure that I was not starting a long, difficult and redundant work. I already tried a "naive" bump of the and but it does not work, mostly because most of the patchs are not valid anymore.
This was solved by cc.
Thank you for continuing this work!


Question: githubId = 84152630; name = "Ashley Chiara"; }; <ins> ashleyghooper = { email = "ashleyghooper@gmail.com"; github = "ashleyghooper"; githubId = 11037075; name = "Ashley Hooper"; }; </ins> aske = { email = "aske@fmap.me"; github = "aske";

Project description ET: Legacy is an open source project based on the code of Wolfenstein: Enemy Territory which was released in 2010 under the terms of the GPLv3 license. Metadata homepage URL: source URL: license: gpl3 platforms: unix, linux, darwin
I got a derivation to work: This is for the 32-bit build, client only. Run and use the binary. Planning to properly package it and contribute to nixpkgs, but since it's my first package it'll require some more time. Also planning to get the server and omnibot working.
I marked this as stale due to inactivity. →
Still interested.
My version of derivation gist doesn't seem to work now that I've upgraded to NixOS 22.05. Haven't had time to investigate too much yet. Whether I try to join an online game server or host a game, I get the below error:
This adaptation of gist is working for me. It's currently for the 32-bit Linux version only, so produces a package . There is an option to use the mod libs built by the ET Legacy project (CI pipeline) or compile them locally.
Hi guys Based on gist I did compiled using NixOS VM Machine it runs fine but there a small quirks there Date is not set correctly it is set to beginning of the time :D Also does ignores manually set env variables ?
Added those 2 in etlegacy*.nix files ` Those 2 should fix issue with correct compile date and naming scheme to build non package But it does not Am I doing something wrong ? :D
Package created and pull request created. Just waiting on PR to be approved so the package can be to nixpkgs.
Is it normal I cannot find the package in the unstable channel?
I think there may be some delay as it migrates to the unstable channel, and then into 23.05.
it seems to be in unstable now.


Question: LC_ALL = "en_US.UTF-8"; <ins> pytestFlags = stdenv.lib.optionals (xineBackend || !withGstPlugins) [ "--ignore=tests/plugin/test_replaygain.py" ] ++ [ # upstream does actually not enforce source code linting "--ignore=tests/quality" # build failure on Arch Linux # https://github.com/NixOS/nixpkgs/pull/77796#issuecomment-575841355 "--ignore=tests/test_operon.py" ]; </ins> checkPhase = '' runHook preCheck <del> env XDG_DATA_DIRS="$out/share:${gtk3}/share/gsettings-schemas/${gtk3.name}:$XDG_DATA_DIRS"  </del> <ins> env XDG_DATA_DIRS="$out/share:${gtk3}/share/gsettings-schemas/${gtk3.name}:$XDG_ICON_DIRS:$XDG_DATA_DIRS"  </ins> HOME=$(mktemp -d)  xvfb-run -s '-screen 0 800x600x24' dbus-run-session  --config-file=${dbus.daemon}/share/dbus-1/session.conf  <del> py.test${stdenv.lib.optionalString (xineBackend || !withGstPlugins) " --ignore=tests/plugin/test_replaygain.py"} </del> <ins> py.test $pytestFlags </ins> runHook postCheck '';

fails to install on . It worked before the recent update. It fails early on in the check phase. I'm guessing the fact that I have to build it from source at all is because it also fails everywhere else, so there's no cached build to download. Try to install on system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Hmm, the tests worked just fine for me on
Do they work for you now? What's kinda weird is that I never get an error message or anything. You see in the output I posted above, there's just loads of dots. It kind of sits there printing dots for a while and then it looks like it just times out or something.
For what it's worth if I put in the derivation, the resulting player is perfectly functional at least for my purposes. Haven't tested every feature or anything though.
I think it crashes during the test. I will try bisecting.
Bisecting was inconclusive because I ran out of resources when building webkitgtk.
What commands did you run? I have a server with plenty of resources that's just sitting idle at the moment, I could try run it on that.
but I guess it might make more sense to skip the builds where dependencies failed by running something like:
Cool, I've been running this for a while, for what it's worth it's currently narrowed it down to between and .
I'll let you know in the morning when it's finished.
The original bisect command I ran didn't take into account the case where dependencies failed to build, so I had to run it again with a script like the one you suggested. Here's the output of :
FWIW I managed to build it by setting in an overlay. Works for me, but I wouldn't suggest that this is done in the Hydra build of course!
Yeah, we should probably add in the expression if this still occurs.
I get quite a bit further, attempting to build rather than . The entire test suite finishes, then reports three test failures related to icons and GTK / GDK.
Seems like the tests are failing again
I marked this as stale due to inactivity. →
EDIT: Kindly ignore this comment, didn't notice that I was using the deprecated repository. Hi, I'm encountering the same errors as reported previously. In case anyone else is experiencing the same, I was able to fix them using:


Question: <ins> { config, lib, pkgs, ... }: with lib; let cfg = config.programs.msmtp; in { meta.maintainers = with maintainers; [ pacien ]; options = { programs.msmtp = { enable = mkEnableOption "msmtp - an SMTP client"; setSendmail = mkOption { type = types.bool; default = true; description = '' Whether to set the system sendmail to msmtp's. ''; }; defaults = mkOption { type = types.attrs; default = {}; example = { aliases = "/etc/aliases"; port = 587; tls = true; }; description = '' Default values applied to all accounts. See msmtp(1) for the available options. ''; }; accounts = mkOption { type = with types; attrsOf attrs; default = {}; example = { "default" = { host = "smtp.example"; auth = true; user = "someone"; passwordeval = "cat /secrets/password.txt"; }; }; description = '' Named accounts and their respective configurations. The special name "default" allows a default account to be defined. See msmtp(1) for the available options. Use `programs.msmtp.extraConfig` instead of this attribute set-based option if ordered account inheritance is needed. It is advised to use the `passwordeval` setting to read the password from a secret file to avoid having it written in the world-readable nix store. The password file must end with a newline (`n`). ''; }; extraConfig = mkOption { type = types.lines; default = ""; description = '' Extra lines to add to the msmtp configuration verbatim. See msmtp(1) for the syntax and available options. ''; }; }; }; config = mkIf cfg.enable { environment.systemPackages = [ pkgs.msmtp ]; services.mail.sendmailSetuidWrapper = mkIf cfg.setSendmail { program = "sendmail"; source = "${pkgs.msmtp}/bin/sendmail"; setuid = false; setgid = false; }; environment.etc."msmtprc".text = let mkValueString = v: if v == true then "on" else if v == false then "off" else generators.mkValueStringDefault {} v; mkKeyValueString = k: v: "${k} ${mkValueString v}"; mkInnerSectionString = attrs: concatStringsSep "n" (mapAttrsToList mkKeyValueString attrs); mkAccountString = name: attrs: '' account ${name} ${mkInnerSectionString attrs} ''; in '' defaults ${mkInnerSectionString cfg.defaults} ${concatStringsSep "n" (mapAttrsToList mkAccountString cfg.accounts)} ${cfg.extraConfig} ''; }; } </ins>

The ssmtp program is dead/unmaintained. The commonly suggested substitute is msmtp. While [home-manager has a module for msmtp][1], NixOS lacks one. [1]: Let's: [x] Done in We should probably also: [x] Remove the ssmtp NixOS module and add migration instructions to the release notes () [x] Remove the ssmtp package ()
I marked this as stale due to inactivity. →
The module works really well. Thanks for the module


Question: patchelf  --add-needed libasound.so.2  --add-needed libdbus-1.so.3  <ins> --add-needed libGL.so.1  </ins> --add-needed libpthread.so.0  --add-needed libudev.so.1  --add-needed libvulkan.so.1

segfaults on launch Game runs Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I noticed this as well yesterday running nixos-unstable


Question: optionalString config.security.pam.enableEcryptfs '' mr ${pkgs.ecryptfs}/lib/security/pam_ecryptfs.so, '' + <ins> optionalString config.security.pam.enableFscrypt '' mr ${pkgs.fscrypt-experimental}/lib/security/pam_fscrypt.so, '' + </ins> optionalString (isEnabled (cfg: cfg.pamMount)) '' mr ${pkgs.pam_mount}/lib/security/pam_mount.so, '' +

I would like to use to encrypt my home directory. is already packaged (as , for some reason) What's missing is the PAM setup (). Given that exists for EcryptFS, I would like to request support for via the option, or something similar. I am aware that EcryptFS is available, to achieve the same goals, however it seems to be considered deprecated by other distributions (, ) and has some which I am not comfortable with.
This is just to say hi and to share that I too am interested in this feature
I marked this as stale due to inactivity. →


Question: installPhase = '' install -D -m755 buck-out/gen/*/programs/buck.pex $out/bin/buck wrapProgram $out/bin/buck  <del> --prefix PATH : "${lib.makeBinPath [ jdk11 watchman python3 ]}" </del> <ins> --prefix PATH : "${lib.makeBinPath [ jdk8 watchman python3 ]}" </ins> ''; meta = with lib; {

Buck build system is packaged with the wrong JDK it seems PR introduced a bump in JDK version, see (). Metadata Please run and paste the result. Maintainer information:
I guess the most recent version should support java 11:
Until they make a stable release with those changes included, we will just use jdk8


Question: libXfixes libGL nspr <del> nss </del> <ins> nss_latest </ins> systemd # For GTKLookAndFeel

A clear and concise description of what the bug is. Steps to reproduce the behavior: to or -build switch to install android-studio android-studio and open one project the right-top button to sign to Google will open a dialog show nothing happened android-studio can open the default browser and success to sign in google. ! 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.
This is the same problem as , which I'm experiencing. Clicking documentation links from within Android Studio does nothing other than showing a jumping icon of Firefox besides the cursor for a few seconds (on KDE Plasma, X11), while it's expected to open the page in Firefox.


Question: <ins> { lib, buildNpmPackage, fetchFromGitHub, python3, nixosTests, }: let pname = "open-webui"; version = "0.2.4"; src = fetchFromGitHub { owner = "open-webui"; repo = "open-webui"; rev = "v${version}"; hash = "sha256-jWO0mo26C+QTIX5j3ucDk/no+vQnAh7Q6JwB3lLM83k="; }; frontend = buildNpmPackage { inherit pname version src; npmDepsHash = "sha256-QIgYHZusuq2QD8p8MGsNVhCbz6fR+qP9UuU/kbBkadc="; # Disabling `pyodide:fetch` as it downloads packages during `buildPhase` # Until this is solved, running python packages from the browser will not work. postPatch = '' substituteInPlace package.json  --replace-fail "npm run pyodide:fetch && vite build" "vite build"  ''; env.CYPRESS_INSTALL_BINARY = "0"; # disallow cypress from downloading binaries in sandbox installPhase = '' runHook preInstall mkdir -p $out/share cp -a build $out/share/open-webui runHook postInstall ''; }; in python3.pkgs.buildPythonApplication rec { inherit pname version src; pyproject = true; # The custom hook tries to run `npm install` in `buildPhase`. # We don't have to worry, as nodejs depedencies are managed by `frontend` drv. postPatch = '' substituteInPlace pyproject.toml  --replace-fail '[tool.hatch.build.hooks.custom]' ""  --replace-fail ', build = "open_webui/frontend"' "" ''; pythonRelaxDeps = true; pythonRemoveDeps = [ # using `psycopg2` instead "psycopg2-binary" # using `opencv4` "opencv-python-headless" # package request: https://github.com/NixOS/nixpkgs/issues/317065 "rapidocr-onnxruntime" # package request: https://github.com/NixOS/nixpkgs/issues/317066 "langfuse" # package request: https://github.com/NixOS/nixpkgs/issues/317068 "langchain-chroma" ]; dependencies = with python3.pkgs; [ beautifulsoup4 fastapi uvicorn python-multipart flask flask-cors python-socketio python-jose passlib requests aiohttp peewee peewee-migrate psycopg2 pymysql bcrypt litellm boto3 argon2-cffi apscheduler google-generativeai langchain langchain-community fake-useragent chromadb sentence-transformers pypdf docx2txt python-pptx unstructured markdown pypandoc pandas openpyxl pyxlsb xlrd validators opencv4 fpdf2 rank-bm25 faster-whisper pyjwt black youtube-transcript-api pytube ]; build-system = with python3.pkgs; [ hatchling pythonRelaxDepsHook ]; pythonImportsCheck = [ "open_webui" ]; postInstall = '' wrapProgram $out/bin/open-webui  --set FRONTEND_BUILD_DIR "${frontend}/share/open-webui" ''; passthru.tests = { inherit (nixosTests) open-webui; }; meta = { description = "Full-stack of open-webui. open-webui is a user-friendly WebUI for LLMs (Formerly Ollama WebUI)"; homepage = "https://github.com/open-webui/open-webui"; changelog = "https://github.com/open-webui/open-webui/blob/${src.rev}/CHANGELOG.md"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ shivaraj-bh ]; mainProgram = "open-webui"; }; } </ins>

Project description WebUI service for Large Language Models Video demonstration by : .. basically self-hostable ChatGPT-like service Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Additional info Follow-up on for open-webui nixos module. There seems to be an ongoing work on the subject by and on Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Relevant Merge Request:
Just for reference / workaround here's another nix package:
Thanks for that reference. That pdm tool workaround looks a lot more maintainable for the Python backend. Maybe i'll have time to try another PR in the next weeks. In the meantime and as a much simpler UI i packaged as part of PR It would be great if someone could review it.
I would like to mention that in the latest release switched to , I am not sure of any straightforward way to do this while packaging it for .
I just tested your flake, it's impressive, especially the nice UI at the end showing all the processes ! Regarding open-webui, it would be so nice to have that in !!!
Thank you, planning to have more UIs and devShell integration (for CLI tools that interact with ollama). I would love that too! Although there are a few challenges (like the one I pointed above regarding ), I am willing to contribute here. Also, maintainers are quick to respond, in case we need any upstream contributions to make it happen.


Question: See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html>. ''; }; <del> in [ </del> <ins> in (lib.optionals cfg.enablePostfix [ </ins> { assertion = postfix.enable; <del> message = "Mailman requires Postfix"; </del> <ins> message = '' Mailman's default NixOS configuration requires Postfix to be enabled. If you want to use another MTA, set services.mailman.enablePostfix to false and configure settings in services.mailman.settings.mta. Refer to <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html> for more info. ''; </ins> } (requirePostfixHash [ "relayDomains" ] "postfix_domains") (requirePostfixHash [ "config" "transport_maps" ] "postfix_lmtp") (requirePostfixHash [ "config" "local_recipient_maps" ] "postfix_lmtp") <del> ]; </del> <ins> ]); </ins> users.users.mailman = { description = "GNU Mailman";

Describe the bug Mailman module in NixOS requires postfix enabled and has no way to configure Mailman to work with other MTAs supported by both NixOS and mailman upstream. To Reproduce Steps to reproduce the behavior: postfix mailman the evaluation with an assertion Expected behavior The Mailman module allows to select an MTA of choice (or even adapts to the currently enabled MTA) Screenshots n/a Additional context Notify maintainers cc Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(vika): nixpkgs: Maintainer information:
It looks like exim's configuration should be RFC42-ised first if we want to inject Mailman-related settings into Exim config, which is a requirement (Mailman requires a custom Exim router and transport).
Yes, the module is currently quite opinionated. If you're willing to contribute exim support that's great.
I see how I could make it work, but the first version of it will require manual editing of Exim's config files (because RFC42-ising Exim will be a pain, even though I have some drafts on how to translate Nix into the syntax that's required), and I'm not sure if it will be merge-worthy enough :3
Exim config is complicated enough as is, I'm not sure adding an intermediate layer from nix will help that much. I also don't really see this integrating well with existing or other exim config. I'm honestly kind of surprised this works for postfix.


Question: , texinfo , hevea , buildDocs ? false <ins> , optimize ? false # optimize sage to the current system (obviously impure) </ins> }: stdenv.mkDerivation rec {

The recent changes seem to make sage crash when it tries to run some code using openblas (I think). I installed the sage derivation from the latest github repository. In the sage interpreter, run the following sage crashes with the following message: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(okideal): channels(root): nixpkgs:
Procedural: as it is , please specify the CPU model. Looks like the Sage build system had the idea to use somewhere… I.e. the local build could work. I wonder how feasible it is to find where Sage does it — the Sage derivation is allowed to rebuild a lot of dependencies because it is just too much pain to make it use the system versions.
Here is the output of lscpu
From the traceback it presumably crashes here: which is which indeed is an AMD-only instruction (MMX? thought that would be long obsolete by now...)
You were right. A local build works fine. Thanks for the help.
Thanks for your report. do we set to and give up?
This should be fixed by exporting (see ). I'm not quite ready to give up (even though it would probably be the healthier choice :grin:). I'm actually currently experimenting with doing it the "right way" and replacing the sage buildsytem with nix (with a mix of sage and system dependencies).
can you confirm that the latest binary works?
Sorry for the late answer. The binaries from the master branch seem to work. The initial crashes are gone and running gives only unrelated failures. Installing from still gives me the old, faulty binaries though.
Are you sure you updated the channel? What do you mean by "binaries from master"?
I meant that installing from the master branch of the git repository works. I was not aware that there is a difference between nixos-unstable and nixpkgs-unstable. The latter does not seem to include the fix yet. Installing from nixos-unstable works well. Thanks for your help.
Okay, I guess hydra is a bit overwhelmed by all the fixes for the upcoming release. Thanks for reporting.


Question: <ins> { lib , stdenv , fetchFromGitHub , cmake , gcc12Stdenv , SDL2 , libGL }: gcc12Stdenv.mkDerivation (finalAttrs: { pname = "bstone"; version = "1.2.12"; src = fetchFromGitHub { owner = "bibendovsky"; repo = "bstone"; rev = "v${finalAttrs.version}"; hash = "sha256-wtW595cSoVTZaVykxOkJViNs3OmuIch9nA5s1SqwbJo="; }; nativeBuildInputs = [ cmake ]; buildInputs = [ libGL SDL2 ]; postInstall = '' mkdir -p $out/bin mv $out/bstone* $out/bin ''; meta = { description = "Unofficial source port for the Blake Stone series"; homepage = "https://github.com/bibendovsky/bstone"; changelog = "https://github.com/bibendovsky/bstone/blob/${finalAttrs.src.rev}/CHANGELOG.md"; license = with lib.licenses; [ gpl2Plus # Original game source code mit # BStone ]; maintainers = with lib.maintainers; [ keenanweaver ]; mainProgram = "bstone"; platforms = lib.platforms.linux; #TODO: macOS / Darwin support }; }) </ins>

Project description Unofficial source port for Blake Stone series (Aliens Of Gold and Planet Strike). Metadata homepage URL: source URL: license: mit platforms: linux


Question: nativeBuildInputs = [ meson ninja pkg-config python3 wayland-scanner ]; buildInputs = [ cairo colord dbus freerdp lcms2 libGL libXcursor libdrm libevdev libinput <del> libjpeg libseat libunwind libva libwebp libxcb libxkbcommon mesa mtdev pam </del> <ins> libjpeg seatd libunwind libva libwebp libxcb libxkbcommon mesa mtdev pam </ins> pango pipewire udev vaapi wayland wayland-protocols xlibsWrapper ];

error while building using unstable channel trying to build a system using weston pkg building successfully I assume its an easy name swap changing "libseat" on 4th line to "seatd"


Question: dontStrip = true; src = fetchzip { <del> url = "https://usa.kyoceradocumentsolutions.com/content/dam/kdc/kdag/downloads/technical/executables/drivers/kyoceradocumentsolutions/us/en/Kyocera_Linux_PPD_Ver_${version}.tar.gz"; </del> <ins> url = "https://la.kyoceradocumentsolutions.com/content/dam/kdc/kdag/downloads/technical/executables/drivers/kyoceradocumentsolutions/lad/en/Kyocera_Linux_PPD_Ver_${version}.tar.gz"; </ins> sha256 = "11znnlkfssakml7w80gxlz1k59f3nvhph91fkzzadnm9i7a8yjal"; };

Describe the bug The uses the following source definition to build (in ): This source is no longer available, returning an HTP 302 redirect to a new homepage: Navigating the new home, this seems to be an alternative download location: However it seems to be a different file (warning, very slow download, file is ~ 140M in size): To Reproduce Steps to reproduce the behavior: -shell -p cups-kyodialog3 Expected behavior Packabe builds properly. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(marc): nixpkgs: Maintainer information:
I was slightly wrong because I don't understand how is supposed to work; it is the same file. The following works for me: I had to add the URL fragment to get to extract the file though.
does kyodialog3 works this way? Could you create a merge request?


Question: , bison ? null , flex , texinfo <ins> , perl </ins> }: let reuseLibs = enableShared && withAllTargets; <del> # Remove gold-symbol-visibility patch when updating, the proper fix # is now upstream. # https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=330b90b5ffbbc20c5de6ae6c7f60c40fab2e7a4f;hp=99181ccac0fc7d82e7dabb05dc7466e91f1645d3 version = "2.31.1"; </del> <ins> version = "2.34"; </ins> basename = "binutils"; # The targetPrefix prepended to binary names to allow multiple binuntils on the # PATH to both be usable.


Question: <del> { lib, fetchurl, appimageTools, imagemagick }: </del> <ins> { lib, fetchurl, appimageTools, imagemagick, systemd }: </ins> let pname = "ledger-live-desktop";

Describe the bug From IRC: ; Looks like we currently just use their appimage: and our appimage tooling uses buildUserFHSEnv: It seems like we can either: using (build from source, maybe?) similar to how iohk patches Daedalus.
I tried packaging it with yarn2nix, but stumbled upon , unfortunately.
I don't know much about the appimage architecture. Why exactly can we not run appimages natively without FhsUserEnv? Is it just because binaries linking against fhs paths? In this case we probably could run autoPatchelfHook on the contents of the appimage and produce a new image that links against nix libs. EDIT: I just tried this. Extracted the appimage contents, patched all binaries, but then when executing ledger-live-desktop, I'm getting: Currently I'm running ledger live via qemu + usb device passthru via . That works fine.
how difficult would it be to lift Daedalus's patch and use it for the libudev inside the fhs? I've never worked with FHS before, but also don't want to build ledger live from source...
I tried to build ledger live from source and it didn't work because of the issue that mentioned. Patching libudev worked though.
can you link to the patch? It would be great to be able to use my more-trusted nixos machines for these types of activities.
I already created a PR for it and it's referenced above. This one:
Feel free to comment in the PR whether it actually works for you :)
The patch had to be re-done in Should this problem probably be communicated to upstream, so we can think about how to fix this long-term in a more sustainable fashion?


Question: sha256 = "0wmw823ildwm9rcfyk22pvzg100yhps3y9hfjlrpspfd1hhkbp0d"; <del> extraPatches = [ ]; </del> <ins> extraPatches = [ reapplyPathSanitizerPatch ]; </ins> }; zfsUnstable = common {

Describe the bug When booting with ZFS legacy mountpoints like this: the boot fails as described in this post: To Reproduce I guess this is difficult if not anyone is having this issue with legacy mountpoints, but it seems that in the linked discourse post, I'm not the only one with this issue. But I've tested it just on this commit: where it fails, and on this (just one commit before): And there everything works. Expected behavior Mounting of legacy ZFS mountpoints succeeds while booting. Notify maintainers <!-- Metadata Please run and paste the result. Maintainer information: --
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Can you check if this is fixed by ?
I tried with this overlay: Not sure if that's the way to do it, but it didn't work.
it should probably be
Thanks I tried that, and it didn't work. Not sure how to confirm the patch got applied properly though.
if you have the log output, you will have something like:
Guys, just to report, I'm in the latest zen with ZFS 2.0.1-1 with encryption, unstable channel and I'm not having any problems.
I've just found time to test this, thanks for the research. The patch did indeed fix the issue for me! (I've checked the log output for the application of the patch). For the sake of completeness the overlay I've applied (needed a slightly different sha256 sum for me):
Could you make a PR adding the patch to zfs?


Question: "OCT_INSTALL_DIR=$(out)/${octave.sitePath}/oct" ]; <ins> postFixup = '' substituteInPlace $out/lib/cmake/nlopt/NLoptLibraryDepends.cmake --replace  'INTERFACE_INCLUDE_DIRECTORIES "''${_IMPORT_PREFIX}/' 'INTERFACE_INCLUDE_DIRECTORIES "' ''; </ins> meta = { homepage = "https://nlopt.readthedocs.io/en/latest/"; description = "Free open-source library for nonlinear optimization";

A clear and concise description of what the bug is. The package doesn't include a folder. I am looking for a version of which includes the executable. Are we building the package incorrectly such that it doesn't include a binary? Any and all help/advice is much appreciated :bow: Steps to reproduce the behavior: output - notice there is no folder A clear and concise description of what you expected to happen. I want the executable. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- might know something about this? :man_shrugging:
was the binary there before On a quick note: I have never used , so I am not familiar with the package. It seems that the package also needs an update:
It appears that the binary requires AMPL, a commercial package, which is not packaged in nixpkgs. See: https://coin-
ah, I understand. Thank you.


Question: mv $out/usr/* $out/ rm -r $out/share/lintian rm -r $out/usr/ <ins> sed -i "s/${pname})/.${pname}-wrapped)/" $out/bin/${pname} </ins> # sed -i "s/'${pname}'/'.${pname}-wrapped'/" $out/bin/${pname} wrapProgram $out/bin/${pname}  --prefix "PATH" : "${gvfs}/bin"

We've had issues with building atom-beautify since This happens now in both Atom and Atom Beta channels. Error for Atom: Error for Atom Beta: Travis CI for your fork Travis CI or a Docker image for nix and checkout master from atom and atom-beta Last successful beta/stable build: https://travis- Last successful stable build: https://travis- Both failed: https://travis-
here is a new issue.
Seems to be related to
For stable maybe, beta is slightly different error.


Question: captive-browser = callPackage ../applications/networking/browsers/captive-browser { }; <del> ndn-cxx = callPackage ../development/libraries/ndn-cxx { boost = boost175; }; </del> <ins> ndn-cxx = callPackage ../development/libraries/ndn-cxx { }; </ins> ndn-tools = callPackage ../tools/networking/ndn-tools { };

The default boost version has been bumped from 1.69 (or 1.75) to 1.77. This is a notice for maintainers that the following packages are now failing to build: - - - - - - - - - - [x] cryfs A typical fix would involve pinning the package to a specific version (e.g. see )
My fix in is not the same as . Is there a very good reason to prefer one over the other ?
Well, I like trying to keep it away from the huge top-level file. (which is e.g. harder to use in git)
Re. pivx, I think we should mark it broken. Our current version is very old (and therefore useless), and the new version includes a rust build. I don't have the capacity to fix this ATM.
In my case, what broke it was the update from boost175 to boost177. Fix is in .
It's in the branch now, so please target any further fixes there as well (unless they're a mass rebuild, etc.)
colobot fixed with
FYI, ledger has some broken behavior with the new boost version, although it curiously doesn't cause a test failure: ledger/ledger.
Our expression does not attempt to run tests.
Ah, that would be why, thanks. Nevertheless, the binary exhibits the same problem described in that issue in interactive use.


Question: modernx-zydezu = callPackage ./modernx-zydezu.nix { }; mpris = callPackage ./mpris.nix { }; mpv-cheatsheet = callPackage ./mpv-cheatsheet.nix { }; <ins> mpv-discord = callPackage ./mpv-discord.nix { }; </ins> mpv-notify-send = callPackage ./mpv-notify-send.nix { }; mpv-osc-modern = callPackage ./mpv-osc-modern.nix { }; mpv-playlistmanager = callPackage ./mpv-playlistmanager.nix { };

Project description A cross-platform Discord Rich Presence integration for mpv with no external dependencies. (MPV Userscript) Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, windows
I've already but haven't PR'ed this to nixpkgs yet. Will probably do this when I get home from vacation next week.


Question: stdenv.mkDerivation rec { pname = "shotwell"; <del> version = "0.31.5"; </del> <ins> version = "0.31.7"; </ins> src = fetchurl { url = "mirror://gnome/sources/${pname}/${lib.versions.majorMinor version}/${pname}-${version}.tar.xz"; <del> sha256 = "sha256-OwSPxs6ZsjLR4OqbjbB0CDyGyI07bWMTaiz4IXqkXBk="; </del> <ins> sha256 = "sha256-gPCj2HVS+L3vpeNig77XZ9AFdtqMyWpEo9NKQjXEmeA="; </ins> }; <ins> patches = [ # Fix build with vala 0.56.4, can be removed on next update # https://gitlab.gnome.org/GNOME/shotwell/-/merge_requests/69 (fetchpatch2 { url = "https://gitlab.gnome.org/GNOME/shotwell/-/commit/cd82759231e5ece2fa0dea40397c9051d15fd5c2.patch"; hash = "sha256-Vy2kvUlmPdEEuPB1RTcI5pGYNveeiQ+lId0YVlWo4wU="; }) ]; </ins> nativeBuildInputs = [ meson ninja

Steps to reproduce the behavior: shotwell from latest nixos-unstable I simply install shotwell with . Noticed that often updates this derivation, last time it was changed by but I don't think his change would cause this. Otherwise - meta.maintainers is empty. Please run and paste the result.


Question: stdenv.mkDerivation rec { pname = "xow"; <del> version = "0.5"; </del> <ins> version = "unstable-2022-04-24"; </ins> src = fetchFromGitHub { owner = "medusalix"; repo = "xow"; <del> rev = "v${version}"; sha256 = "071r2kx44k1sc49cad3i607xg618mf34ki1ykr5lnfx9y6qyz075"; </del> <ins> rev = "d335d6024f8380f52767a7de67727d9b2f867871"; sha256 = "0q5nr21p4dlx2a99hiivwz6qj9anrqqsdhiz6xi375yqkxis4251"; </ins> }; firmware = fetchurl {

Enabling services.hardware. (as a systemd service) breaks. Steps to reproduce the behavior: error about and several other errors like "has not been declared", "does not name a type", etc. To rebuild xow and everything else without any issues. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
The git not found problem is not fatal and the derivation overrides the version info anyway. Looks like another victim of our stdenv compiler upgrade. Looks like upstream master has a fix for that. Upstream is also orphaned so upgrading the derivation to an unstable revision is going to be needed in the short term and in the long term a replacement should probably be found. I don't have a working controller to test xow with any more so if someone wants to adopt the package, feel free to.


Question: perlPackages.buildPerlPackage rec { pname = "SpamAssassin"; <del> version = "4.0.0"; rulesRev = "r1905950"; </del> <ins> version = "4.0.1"; rulesRev = "r1916528"; </ins> src = fetchurl { url = "mirror://apache/spamassassin/source/Mail-${pname}-${version}.tar.bz2"; <del> hash = "sha256-5aoXBQowvHK6qGr9xgSMrepNHsLsxh14dxegWbgxnog="; </del> <ins> hash = "sha256-l3XtdVnoPsPmwD7bK+j/x/FcxAX7E+hcFI6wvxkXIag="; </ins> }; defaultRulesSrc = fetchurl { url = "mirror://apache/spamassassin/source/Mail-${pname}-rules-${version}.${rulesRev}.tgz"; <del> hash = "sha256-rk/7uRfrx/76ckD8W7UVHdpmP45AWRYa18m0Lu0brG0="; </del> <ins> hash = "sha256-OB6t/H5RPl9zU4m3gXPeWvRx89Bv5quPEpY0pmRLS/Q="; </ins> }; patches = [

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]:


Question: pixman cairo pango <ins> ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk_11_0.frameworks.CoreText </ins> ]; desktopItems = [

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]:


Question: in stdenv.mkDerivation rec { pname = "openshadinglanguage"; <del> version = "1.12.13.0"; </del> <ins> version = "1.12.14.0"; </ins> src = fetchFromGitHub { owner = "AcademySoftwareFoundation"; repo = "OpenShadingLanguage"; rev = "v${version}"; <del> hash = "sha256-EVV7YHovWwbRju+uv8IK2wpcpoK1ndZ8yNRHzU8LUuE="; </del> <ins> hash = "sha256-x8t7uC4q29MkTCIS1rK0ICw78u5zZG+/zyhwttLOBr4="; </ins> }; cmakeFlags = [

rendered in : ! bumping osl to did not work. Applying did not work <!-- 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: nixpkgs:
I have verified that the problem exists with the current derivation even with version , which was updated away from in . I guess somehow the ZLIB_VERSION is replaced improperly , but I've got no idea what could be causing it, and I'm really confused why it's only become a problem recently, as it doesn't look like osl has been touched in either.
I've tracked it down to , and reverting it seems to fix it. I also believe it's a cmake issue. Consider this file Output: Maybe because the header changed to (? But if I'm reading the correctly, I think it should just set the version to an empty string? Either way, this patch seems to fix it I don't think it's worth raising with zlib because with the next patch version they're going to fix it anyway. It might be worth warning them in advance of 1.4. It's probably worth raising with cmake, because they will want to support all version, and then zlib won't have to care anymore either. I can open a PR for this tomorrow or when I have time, but don't wait for me if anybody wants to do it before.
Nice catch! One minor note: you are looking at 's master branch. It seems to be already fixed there as: We'll need that backport to . UPDATE: or wait for to reach master. With now is in .


Question: githubId = 303489; name = "Manuel Bärenz"; }; <ins> tu-maurice = { email = "valentin.gehrke+nixpkgs@zom.bi"; github = "tu-maurice"; githubId = 16151097; name = "Valentin Gehrke"; }; </ins> tv = { email = "tv@krebsco.de"; github = "4z3";

Project description Converts Linux images and kernels into UEFI images. Metadata homepage URL: source URL: license: GPL3 platforms: Linux


Question: ''; }; <ins> virtualisation.libvirtd.qemuOvmf = mkOption { type = types.bool; default = true; description = '' Allows libvirtd to take advantage of OVMF when creating new QEMU VMs with UEFI boot. ''; }; </ins> virtualisation.libvirtd.extraOptions = mkOption { type = types.listOf types.str; default = [ ];

In , I introduced support in libvirtd for UEFI VM creation. rightfully remarked that this brings closure-size up too much. Looking into OVMF shows that only 1MB out of the 114MB install size is needed to enable said UEFI VM creation. I think that we should look into splitting out OVMF_(CODE|VARS) from the rest package.


Question: python3Packages.buildPythonApplication rec { pname = "electron-cash"; <del> version = "4.2.0"; </del> <ins> version = "4.2.4"; </ins> src = fetchFromGitHub { owner = "Electron-Cash"; repo = "Electron-Cash"; rev = version; <del> sha256 = "0ixsx4224jilc5zis6wbsbxqxv10mm5sksrzq15xp30zz0bzb6md"; </del> <ins> sha256 = "sha256-hiOS0cTaPqllb31p+6nU4GYvw/E1Hdn8yd3sppzGkqg="; </ins> }; propagatedBuildInputs = with python3Packages; [ <del> dnspython </del> <ins> # requirements pyaes </ins> ecdsa <ins> requests qrcode protobuf </ins> jsonrpclib-pelix <del> matplotlib pbkdf2 pyaes pycrypto pyqt5 </del> pysocks <del> qrcode requests tlslite-ng </del> qdarkstyle <ins> python-dateutil </ins> stem <ins> certifi pathvalidate dnspython </ins> <del> # plugins keepkey </del> <ins> # requirements-binaries pyqt5 psutil pycryptodomex cryptography # requirements-hw cython </ins> trezor <ins> keepkey </ins> btchip <ins> hidapi pyscard pysatochip </ins> ]; nativeBuildInputs = [ wrapQtAppsHook ];

Describe the bug failed to build on master. To Reproduce Steps to reproduce the behavior: nixpkgs master Expected behavior It builds. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(oxa): nixpkgs: Maintainer information:


Question: }; buildInputs = [ makeWrapper pkgconfig e19.efl python27 dbus ]; <del> propagatedBuildInputs = [ python27Packages.pythonefl_1_11 python27Packages.dbus e19.elementary ]; </del> <ins> propagatedBuildInputs = [ python27Packages.pythonefl_1_12 python27Packages.dbus e19.elementary ]; </ins> postInstall = '' <del> wrapProgram $out/bin/econnman-bin --prefix PYTHONPATH : ${python27Packages.dbus}/lib/python2.7/site-packages:${python27Packages.pythonefl_1_11}/lib/python2.7/site-packages </del> <ins> wrapProgram $out/bin/econnman-bin --prefix PYTHONPATH : ${python27Packages.dbus}/lib/python2.7/site-packages:${python27Packages.pythonefl_1_12}/lib/python2.7/site-packages </ins> ''; meta = {

Possible, because X11/xkb/rules/*.lst [0] are somewhere 'hidden' in the /nix/store. [0]
Fixed, just let me do some updating on E19 libraries and I will make a pull request.


Question: src = fetchurl { url = <del> "https://storage.googleapis.com/flutter_infra/releases/${channel}/linux/flutter_linux_v${version}-${channel}.tar.xz"; </del> <ins> "https://storage.googleapis.com/flutter_infra/releases/${channel}/linux/${filename}"; </ins> sha256 = sha256Hash; };

When trying to install , the build fails with: To reproduce, use the following and run it with : I think this happens because of the symlink of the , which seems to be resolved while running the build and in that case the symlink target does not exist. /cc btw: could you please also add support for the latest beta / dev / stable releases?
Hey it's fixed in the latest commit. Can you try it ?
Works fine, thank you very much for the fast fix!


Question: outputs = [ "out" "dev" "doc" ]; nativeBuildInputs = [ autoreconfHook pkg-config ]; <del> buildInputs = [ fftw ]; </del> <ins> buildInputs = lib.optionals withFftw3 [ fftw ]; </ins> <del> configureFlags = [ "--with-fft=gpl-fftw3" ] ++ lib.optional stdenv.isAarch64 "--disable-neon"; </del> <ins> configureFlags = lib.optionals withFftw3 [ "--with-fft=gpl-fftw3" ] ++ lib.optional stdenv.isAarch64 "--disable-neon"; </ins> meta = with lib; { homepage = "https://www.speex.org/";

Easyeffects crashes when Echo Canceller is used (at least when applied on input). I've been told that it works fine on arch linux. Though it might be my hardware that somehow makes it crash. Steps to reproduce the behavior: Echo Canceller module to the Input Easy Effects to one of recording apps It doesn't crash It doesn't write anything useful in the logs, just exits with code 137. Please run and paste the result.
I can reproduce it but it is not a regular crash – there is not core dump. It appears to be killed. Weirdly when I run it with: The termination is not caught.
For me it reproduced with gdb: Maybe it's terminated when child process is crashed?
hmm, it seems to be something wrong with speex when configured to use the fftw library... not sure what, but this doesn't crash:
The same also happens in Speech Processor effect now:
Unfortunately this didn't seem to do the trick for me, it still crashes with the Echo Canceller.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I have the same problem. The thing is, used to work OK on my system. Then I tried the module, after which this issue appeared. However, now it's persisting. I undid the change, even tried booting into old generation, but is still getting killed with the echo canceller on. For reference, this is what I used to try to enable the echo cancel module (not sure if it ever worked):


Question: check_systemd = callPackage ../servers/monitoring/nagios/plugins/check_systemd.nix { }; <del> neo4j = callPackage ../servers/nosql/neo4j { }; </del> <ins> neo4j = callPackage ../servers/nosql/neo4j { jre = jre8_headless; }; </ins> neo4j-desktop = callPackage ../applications/misc/neo4j-desktop { };

Describe the bug Neo4j does not start because it cannot locate a Java Runtime. To Reproduce On my system, I installed with: Then, running shows: "The operation couldn’t be completed. Unable to locate a Java Runtime." Expected behavior Neo4j should start. Additional context Note that shows Note the line that sets to . Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run and paste the result. Maintainer information: