Question: Project description Add Korean Nanum fonts: Nanum Gothic Nanum Barun Gothic Nanum Barunpen Nanum Brush Nanum Myengjo Nanum Pen Nanum Square Nanum Square Round Metadata homepage URL: source URL: license: ofl platforms: all

<ins> { fetchzip, lib }: let version = "20170925"; in fetchzip { name = "nanum-${version}"; url = "mirror://ubuntu/pool/universe/f/fonts-nanum/fonts-nanum_${version}.orig.tar.xz"; sha256 = "sha256-lSTeQEuMmlQxiQqrx9tNScifE8nMOUDJF3lCfoAFIJk="; postFetch = '' unpackDir="$TMPDIR/unpack" mkdir "$unpackDir" cd "$unpackDir" tar xf "$downloadedFile" --strip-components=1 mkdir -p $out/share/fonts cp *.ttf $out/share/fonts ''; meta = with lib; { description = "Nanum Korean font set"; homepage = "https://hangeul.naver.com/font"; license = licenses.ofl; maintainers = with lib.maintainers; [ serge ]; platforms = platforms.all; }; } </ins>


Question: Project description Add Korean Nanum fonts: Nanum Gothic Nanum Barun Gothic Nanum Barunpen Nanum Brush Nanum Myengjo Nanum Pen Nanum Square Nanum Square Round Metadata homepage URL: source URL: license: ofl platforms: all

nafees = callPackage ../data/fonts/nafees { }; <ins> nanum = callPackage ../data/fonts/nanum {  }; </ins> nanum-gothic-coding = callPackage ../data/fonts/nanum-gothic-coding {  }; national-park-typeface = callPackage ../data/fonts/national-park { };


Question:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

<del> {stdenv, lib, fetchurl, perl, libedit, ncurses, gmp}: </del> <ins> {stdenv, lib, fetchurl, perl, libedit, ncurses5, gmp}: </ins> stdenv.mkDerivation rec { version = "6.10.2";


Question:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

(if stdenv.isLinux then '' find . -type f -perm -0100  -exec patchelf --interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"  <del> --set-rpath "${libedit}/lib:${ncurses.out}/lib:${gmp.out}/lib" {} ; </del> <ins> --set-rpath "${libedit}/lib:${ncurses5.out}/lib:${gmp.out}/lib" {} ; </ins> for prog in ld ar gcc strip ranlib; do find . -name "setup-config" -exec sed -i "s@/usr/bin/$prog@$(type -p $prog)@g" {} ; done


Question:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

<del> {stdenv, fetchurl, perl, ncurses, gmp, libiconv}: </del> <ins> {stdenv, fetchurl, perl, ncurses5, gmp, libiconv}: </ins> stdenv.mkDerivation rec { version = "7.0.4";


Question:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

stdenv.lib.optionalString stdenv.isLinux '' find . -type f -perm -0100  -exec patchelf --interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"  <del> --set-rpath "${ncurses.out}/lib:${gmp.out}/lib" {} ; </del> <ins> --set-rpath "${ncurses5.out}/lib:${gmp.out}/lib" {} ; </ins> sed -i "s|/usr/bin/perl|perlx00        |" ghc-${version}/ghc/stage2/build/tmp/ghc-stage2 sed -i "s|/usr/bin/gcc|gccx00        |" ghc-${version}/ghc/stage2/build/tmp/ghc-stage2 for prog in ld ar gcc strip ranlib; do


Question:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

<del> {stdenv, fetchurl, perl, ncurses, gmp, libiconv, makeWrapper}: </del> <ins> {stdenv, fetchurl, perl, ncurses5, gmp, libiconv, makeWrapper}: </ins> stdenv.mkDerivation rec { version = "7.4.2";


Question:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

# find editline/gmp. stdenv.lib.optionalString stdenv.isLinux '' mkdir -p "$out/lib" <del> ln -sv "${ncurses.out}/lib/libncurses.so" "$out/lib/libncurses${stdenv.lib.optionalString stdenv.is64bit "w"}.so.5" </del> <ins> ln -sv "${ncurses5.out}/lib/libncurses.so" "$out/lib/libncurses${stdenv.lib.optionalString stdenv.is64bit "w"}.so.5" </ins> find . -type f -perm -0100  -exec patchelf --interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"  --set-rpath "$out/lib:${gmp.out}/lib" {} ;


Question:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

{ lib, stdenv, fetchurl, pkgconfig <ins> , abiVersion </ins> , mouseSupport ? false , unicode ? true , gpm }: let <del> inherit (stdenv) isDarwin; abiVersion = if isDarwin then "5" else "6"; version = if isDarwin then "5.9" else "6.0"; sha256 = if isDarwin </del> <ins> version = if abiVersion == "5" then "5.9" else "6.0"; sha256 = if abiVersion == "5" </ins> then "0fsn7xis81za62afan0vvm38bvgzg5wfmv1m86flqcj0nj7jjilh" else "0q3jck7lna77z5r42f13c4xglc7azd19pxfrjrpgp2yf615w4lgm"; in


Question:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

inherit sha256; }; <del> patches = [ ./clang.patch ]; </del> <ins> patches = [ ./clang.patch ] ++ lib.optional (abiVersion == "5" && stdenv.cc.isGNU) ./gcc-5.patch; </ins> outputs = [ "dev" "out" "man" ]; setOutputFlags = false; # some aren't supported


Question:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

<ins> https://bugs.gentoo.org/545114 extracted from the upstream change (which had many unrelated commits in one) From 97bb4678dc03e753290b39bbff30ba2825df9517 Mon Sep 17 00:00:00 2001 From: "Thomas E. Dickey" <dickey@invisible-island.net> Date: Sun, 7 Dec 2014 03:10:09 +0000 Subject: [PATCH] ncurses 5.9 - patch 20141206 + modify MKlib_gen.sh to work around change in development version of gcc introduced here: https://gcc.gnu.org/ml/gcc-patches/2014-06/msg02185.html https://gcc.gnu.org/ml/gcc-patches/2014-07/msg00236.html (reports by Marcus Shawcroft, Maohui Lei). diff --git a/ncurses/base/MKlib_gen.sh b/ncurses/base/MKlib_gen.sh index d8cc3c9..b91398c 100755 --- a/ncurses/base/MKlib_gen.sh +++ b/ncurses/base/MKlib_gen.sh @@ -474,11 +474,22 @@ sed -n -f $ED1  -e 's/gen_$//'  -e 's/  / /g' >>$TMP +cat >$ED1 <<EOF +s/  / /g +s/^ // +s/ $// +s/P_NCURSES_BOOL/NCURSES_BOOL/g +EOF + +# A patch discussed here: +#	https://gcc.gnu.org/ml/gcc-patches/2014-06/msg02185.html +# introduces spurious #line markers.  Work around that by ignoring the system's +# attempt to define "bool" and using our own symbol here. +sed -e 's/bool/P_NCURSES_BOOL/g' $TMP > $ED2 +cat $ED2 >$TMP + $preprocessor $TMP 2>/dev/null  -| sed  -	-e 's/  / /g'  -	-e 's/^ //'  -	-e 's/_Bool/NCURSES_BOOL/g'  +| sed -f $ED1  | $AWK -f $AW2  | sed -f $ED3  | sed  </ins>


Question:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.

notify-sharp = callPackage ../development/libraries/notify-sharp { }; <del> ncurses = callPackage ../development/libraries/ncurses { }; </del> <ins> ncurses5 = callPackage ../development/libraries/ncurses { abiVersion = "5"; }; ncurses6 = callPackage ../development/libraries/ncurses { abiVersion = "6"; }; ncurses = if stdenv.isDarwin then ncurses5 else ncurses6; </ins> neardal = callPackage ../development/libraries/neardal { };


Question:
Krita fails to build with the following error Steps to reproduce the behavior: Build Krita should build. nixpkgs @
In libraw was updated. Switch to the old stable libraw020 to fix this build.
Installing kirta is showing like it's not in the cache, any idea why?
You're attempting to build the older derivation. And building it would fail. Newer binaries are available:
If you rely on channels, you might want to watch
I'm using the "" and just updated it, and I get this: So, that means the PR is not in that channel yet? If it's that, good to know, didn't know that tool.
Yes, channels that are not -small usually lag by roughly one day.

<del> { libraw, fetchFromGitHub }: libraw.overrideAttrs (_: rec { version = "0.20.2"; src = fetchFromGitHub { owner = "LibRaw"; repo = "LibRaw"; rev = version; sha256 = "16nm4r2l5501c9zvz25pzajq5id592jhn068scjxhr8np2cblybc"; }; }) </del>


Question:
Krita fails to build with the following error Steps to reproduce the behavior: Build Krita should build. nixpkgs @
In libraw was updated. Switch to the old stable libraw020 to fix this build.
Installing kirta is showing like it's not in the cache, any idea why?
You're attempting to build the older derivation. And building it would fail. Newer binaries are available:
If you rely on channels, you might want to watch
I'm using the "" and just updated it, and I get this: So, that means the PR is not in that channel yet? If it's that, good to know, didn't know that tool.
Yes, channels that are not -small usually lag by roughly one day.

stdenv.mkDerivation { pname = "libraw"; <del> version = "unstable-2021-12-03"; </del> <ins> version = "0.20.2.p2"; </ins> src = fetchFromGitHub { owner = "LibRaw"; repo = "LibRaw"; <del> rev = "52b2fc52e93a566e7e05eaa44cada58e3360b6ad"; sha256 = "kW0R4iPuqnFuWYDrl46ok3kaPcGgY2MqZT7mqVX+BDQ="; </del> <ins> rev = "fedad11e87daad7b7d389a3ef84ccf10b5e84710"; # current 0.20-stable branch sha256 = "1mklf8lzybzyg75ja34822xlv6h9nw93griyrjjna7darl1dyvja"; </ins> }; outputs = [ "out" "lib" "dev" "doc" ];


Question:
Krita fails to build with the following error Steps to reproduce the behavior: Build Krita should build. nixpkgs @
In libraw was updated. Switch to the old stable libraw020 to fix this build.
Installing kirta is showing like it's not in the cache, any idea why?
You're attempting to build the older derivation. And building it would fail. Newer binaries are available:
If you rely on channels, you might want to watch
I'm using the "" and just updated it, and I get this: So, that means the PR is not in that channel yet? If it's that, good to know, didn't know that tool.
Yes, channels that are not -small usually lag by roughly one day.

<ins> { libraw, fetchFromGitHub }: libraw.overrideAttrs (_: rec { version = "unstable-2021-12-03"; src = fetchFromGitHub { owner = "LibRaw"; repo = "LibRaw"; rev = "52b2fc52e93a566e7e05eaa44cada58e3360b6ad"; sha256 = "kW0R4iPuqnFuWYDrl46ok3kaPcGgY2MqZT7mqVX+BDQ="; }; }) </ins>


Question:
Krita fails to build with the following error Steps to reproduce the behavior: Build Krita should build. nixpkgs @
In libraw was updated. Switch to the old stable libraw020 to fix this build.
Installing kirta is showing like it's not in the cache, any idea why?
You're attempting to build the older derivation. And building it would fail. Newer binaries are available:
If you rely on channels, you might want to watch
I'm using the "" and just updated it, and I get this: So, that means the PR is not in that channel yet? If it's that, good to know, didn't know that tool.
Yes, channels that are not -small usually lag by roughly one day.

fplll = callPackage ../development/libraries/fplll {}; fplll_20160331 = callPackage ../development/libraries/fplll/20160331.nix {}; <del> freeimage = callPackage ../development/libraries/freeimage { }; </del> <ins> freeimage = callPackage ../development/libraries/freeimage { libraw = libraw_unstable; }; </ins> freetts = callPackage ../development/libraries/freetts { jdk = jdk8; # TODO: remove override https://github.com/NixOS/nixpkgs/pull/89731


Question:
Krita fails to build with the following error Steps to reproduce the behavior: Build Krita should build. nixpkgs @
In libraw was updated. Switch to the old stable libraw020 to fix this build.
Installing kirta is showing like it's not in the cache, any idea why?
You're attempting to build the older derivation. And building it would fail. Newer binaries are available:
If you rely on channels, you might want to watch
I'm using the "" and just updated it, and I get this: So, that means the PR is not in that channel yet? If it's that, good to know, didn't know that tool.
Yes, channels that are not -small usually lag by roughly one day.

gegl = callPackage ../development/libraries/gegl { inherit (darwin.apple_sdk.frameworks) OpenCL; <del> libraw = libraw_0_20; </del> }; gensio = callPackage ../development/libraries/gensio {};


Question:
Krita fails to build with the following error Steps to reproduce the behavior: Build Krita should build. nixpkgs @
In libraw was updated. Switch to the old stable libraw020 to fix this build.
Installing kirta is showing like it's not in the cache, any idea why?
You're attempting to build the older derivation. And building it would fail. Newer binaries are available:
If you rely on channels, you might want to watch
I'm using the "" and just updated it, and I get this: So, that means the PR is not in that channel yet? If it's that, good to know, didn't know that tool.
Yes, channels that are not -small usually lag by roughly one day.

}; libraw = callPackage ../development/libraries/libraw { }; <del> libraw_0_20 = callPackage ../development/libraries/libraw/0_20.nix { }; </del> <ins> libraw_unstable = callPackage ../development/libraries/libraw/unstable.nix { }; </ins> libraw1394 = callPackage ../development/libraries/libraw1394 { };


Question:
The package is failing to build Steps to reproduce the behavior: The package to build successfully without errors
I'm sorry, I haven't used in years - but also nothing with that package has changed in some while. I'd assume an upstream problem?
I don't use but took a look out of curiosity. It was an upstream problem that is fixed by a few commits after the latest 2.4.0 release. There hasn't been a new release since then. Is the best thing to do here pull down that commit as an isolated patch or to bump the revision that's pulled down to that (untagged) revision?
Can we use in the meantime?

{ lib, fetchFromGitHub, cmake, curl, xorg, avahi, qtbase, mkDerivation, openssl, wrapGAppsHook, <del> avahiWithLibdnssdCompat ? avahi.override { withLibdnssdCompat = true; } </del> <ins> avahiWithLibdnssdCompat ? avahi.override { withLibdnssdCompat = true; }, fetchpatch </ins> }: mkDerivation rec {


Question:
The package is failing to build Steps to reproduce the behavior: The package to build successfully without errors
I'm sorry, I haven't used in years - but also nothing with that package has changed in some while. I'd assume an upstream problem?
I don't use but took a look out of curiosity. It was an upstream problem that is fixed by a few commits after the latest 2.4.0 release. There hasn't been a new release since then. Is the best thing to do here pull down that commit as an isolated patch or to bump the revision that's pulled down to that (untagged) revision?
Can we use in the meantime?

fetchSubmodules = true; }; <ins> patches = [ # This patch can be removed when a new version of barrier (greater than 2.4.0) # is released, which will contain this commit. (fetchpatch { name = "add-missing-cstddef-header.patch"; url = "https://github.com/debauchee/barrier/commit/4b12265ae5d324b942698a3177e1d8b1749414d7.patch"; sha256 = "sha256-ajMxP7szBFi4h8cMT3qswfa3k/QiJ1FGI3q9fkCFQQk="; }) ]; </ins> buildInputs = [ curl xorg.libX11 xorg.libXext xorg.libXtst avahiWithLibdnssdCompat qtbase ]; nativeBuildInputs = [ cmake wrapGAppsHook ];


Question:
scipy doesn't build on Darwin right now (trunk). Hydra: The error in Hydra seems to be some builder failure and not actually related to the issue. It however fails as well when I try to build on my Mac. We should get rid of both issues. Steps to reproduce the behavior: to build It builds I don't need this Python module myself but a lot of other packages depend on it. This is currently the package with the most dependants (322) that fails so it'd be nice to have this cleaned up before ZHF starts. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
The too many open files sounds like it could be related to the very low default limit on open files on macOS. For me it defaults to 256, I think more recent versions have increased the limit but it's still lower than for Linux and the tests were probably written with that in mind.
scipy builds for me on both x86_64-darwin and aarch64-darwin. $ nix-info -m system: host os: multi-user?: sandbox: version: channels(reckenrode): channels(root): nixpkgs:
what does report for you?
Ok, then my hypothesis is debunked.
Could this be due to the file descriptor leak bug in nix ? This would explain why it fails to build for some users but not for others. I believe the bug was fixed in nix 2.8.
scipy seems to be build for me on , can anyone else confirm? Looks like it's still failing on .
can we just disable the tests on for now? as a note (or whatever) can bump the open file limit but you might then run into memory limits like I've experienced in
I'm going to disable tests on so we can work on other issues for ZHF. If anyone wants to debug specific failures in scipy please reply to this issue. It currently causes hundreds of other packages to transitively fail.
Wonder if reducing parallelism would help.

rm scipy/linalg/tests/test_lapack.py ''; <del> doCheck = true; </del> <ins> doCheck = !(stdenv.isx86_64 && stdenv.isDarwin); </ins> preConfigure = '' sed -i '0,/from numpy.distutils.core/s//import setuptools;from numpy.distutils.core/' setup.py


Question:
The issue is what the title says. By half, I mean and for my previously used from emacs-overlay to your system the eln cache in your home, e.g. to open emacs for the manual for by and inputing the eln cache in your home: , you will find together other eln cache. I think this is a bug since is builtin for emacs and it's eln cache should be distributed together with . Uses of will not need to native-compile builtin libraries themselves. does distributed together with from emacs-overlay I used before. It's . might be related to the bump of 28 , so
The difference between the two versions is that one is built from the tarball, while the other is built from Git. The tarball includes byte-compiled () files but not native-compiled () files. The build notices the files and does not rebuild them, but native-compilation is a side-effect of byte-compilation and so the files aren't built either. (Almost all of the files you see for the new version are trampolines, there are only 3 non-trampoline files.)
ideally we'd run , which is the expected way of deleting such things (or perhaps even ). But the tarball only has a , so we'd need to run , then , then again, which is super ugly. Hopefully deleting the files the naïve way is enough?
I think maybe we should just skip the tarball entirely and fetch it from git instead.
There are other side-effects caused by skipping the tarball. This claims, for example, that bootstrapping is only expected to happen to emacs developers. Part of bootstrapping is converting the Japanese input method dictionaries, and this takes some amount of time. They're in the tarball at , but are absent in the git checkout.
That's a good point, I would still rather inflate build times a bit and exercise bootstrapping as a part of our regular build though to completely avoid these types of issues.
I'm hesitant about building things in a way that upstream doesn't expect, unless necessary to adapt for nixpkgs. For a related example, using the repo instead of the tar distribution for Ruby caused a subtle problem where the commit hash was not propagated, which broke the bootsnap gem's cache invalidation (fixed in , by using the tarball). The real question here, I think, is how upstream expects native compilation to be used if their tarball doesn't support it.

import ./generic.nix (rec { version = "28.1"; <del> sha256 = "sha256-KLGz0JkDegiPCkyiUdfnJi6rXqFneqv/psRCaWGtdeE="; </del> <ins> sha256 = "sha256-D33wnlxhx0LyG9WZaQDj2II3tG0HcJdZTC4dSA3lrgY="; </ins> patches = _: [ ]; })


Question:
The issue is what the title says. By half, I mean and for my previously used from emacs-overlay to your system the eln cache in your home, e.g. to open emacs for the manual for by and inputing the eln cache in your home: , you will find together other eln cache. I think this is a bug since is builtin for emacs and it's eln cache should be distributed together with . Uses of will not need to native-compile builtin libraries themselves. does distributed together with from emacs-overlay I used before. It's . might be related to the bump of 28 , so
The difference between the two versions is that one is built from the tarball, while the other is built from Git. The tarball includes byte-compiled () files but not native-compiled () files. The build notices the files and does not rebuild them, but native-compilation is a side-effect of byte-compilation and so the files aren't built either. (Almost all of the files you see for the new version are trampolines, there are only 3 non-trampoline files.)
ideally we'd run , which is the expected way of deleting such things (or perhaps even ). But the tarball only has a , so we'd need to run , then , then again, which is super ugly. Hopefully deleting the files the naïve way is enough?
I think maybe we should just skip the tarball entirely and fetch it from git instead.
There are other side-effects caused by skipping the tarball. This claims, for example, that bootstrapping is only expected to happen to emacs developers. Part of bootstrapping is converting the Japanese input method dictionaries, and this takes some amount of time. They're in the tarball at , but are absent in the git checkout.
That's a good point, I would still rather inflate build times a bit and exercise bootstrapping as a part of our regular build though to completely avoid these types of issues.
I'm hesitant about building things in a way that upstream doesn't expect, unless necessary to adapt for nixpkgs. For a related example, using the repo instead of the tar distribution for Ruby caused a subtle problem where the commit hash was not propagated, which broke the bootsnap gem's cache invalidation (fixed in , by using the tarball). The real question here, I think, is how upstream expects native compilation to be used if their tarball doesn't support it.

, sigtool, jansson, harfbuzz, sqlite, nixosTests , dontRecurseIntoAttrs, emacsPackagesFor , libgccjit, targetPlatform, makeWrapper # native-comp params <ins> , fetchFromSavannah </ins> , systemd ? null , withX ? !stdenv.isDarwin , withNS ? stdenv.isDarwin


Question:
The issue is what the title says. By half, I mean and for my previously used from emacs-overlay to your system the eln cache in your home, e.g. to open emacs for the manual for by and inputing the eln cache in your home: , you will find together other eln cache. I think this is a bug since is builtin for emacs and it's eln cache should be distributed together with . Uses of will not need to native-compile builtin libraries themselves. does distributed together with from emacs-overlay I used before. It's . might be related to the bump of 28 , so
The difference between the two versions is that one is built from the tarball, while the other is built from Git. The tarball includes byte-compiled () files but not native-compiled () files. The build notices the files and does not rebuild them, but native-compilation is a side-effect of byte-compilation and so the files aren't built either. (Almost all of the files you see for the new version are trampolines, there are only 3 non-trampoline files.)
ideally we'd run , which is the expected way of deleting such things (or perhaps even ). But the tarball only has a , so we'd need to run , then , then again, which is super ugly. Hopefully deleting the files the naïve way is enough?
I think maybe we should just skip the tarball entirely and fetch it from git instead.
There are other side-effects caused by skipping the tarball. This claims, for example, that bootstrapping is only expected to happen to emacs developers. Part of bootstrapping is converting the Japanese input method dictionaries, and this takes some amount of time. They're in the tarball at , but are absent in the git checkout.
That's a good point, I would still rather inflate build times a bit and exercise bootstrapping as a part of our regular build though to completely avoid these types of issues.
I'm hesitant about building things in a way that upstream doesn't expect, unless necessary to adapt for nixpkgs. For a related example, using the repo instead of the tar distribution for Ruby caused a subtle problem where the commit hash was not propagated, which broke the bootsnap gem's cache invalidation (fixed in , by using the tarball). The real question here, I think, is how upstream expects native compilation to be used if their tarball doesn't support it.

, withSQLite3 ? false , withCsrc ? true , withWebP ? false <del> , srcRepo ? false, autoreconfHook ? null, texinfo ? null </del> <ins> , srcRepo ? true, autoreconfHook ? null, texinfo ? null </ins> , siteStart ? ./site-start.el , nativeComp ? false , withAthena ? false


Question:
The issue is what the title says. By half, I mean and for my previously used from emacs-overlay to your system the eln cache in your home, e.g. to open emacs for the manual for by and inputing the eln cache in your home: , you will find together other eln cache. I think this is a bug since is builtin for emacs and it's eln cache should be distributed together with . Uses of will not need to native-compile builtin libraries themselves. does distributed together with from emacs-overlay I used before. It's . might be related to the bump of 28 , so
The difference between the two versions is that one is built from the tarball, while the other is built from Git. The tarball includes byte-compiled () files but not native-compiled () files. The build notices the files and does not rebuild them, but native-compilation is a side-effect of byte-compilation and so the files aren't built either. (Almost all of the files you see for the new version are trampolines, there are only 3 non-trampoline files.)
ideally we'd run , which is the expected way of deleting such things (or perhaps even ). But the tarball only has a , so we'd need to run , then , then again, which is super ugly. Hopefully deleting the files the naïve way is enough?
I think maybe we should just skip the tarball entirely and fetch it from git instead.
There are other side-effects caused by skipping the tarball. This claims, for example, that bootstrapping is only expected to happen to emacs developers. Part of bootstrapping is converting the Japanese input method dictionaries, and this takes some amount of time. They're in the tarball at , but are absent in the git checkout.
That's a good point, I would still rather inflate build times a bit and exercise bootstrapping as a part of our regular build though to completely avoid these types of issues.
I'm hesitant about building things in a way that upstream doesn't expect, unless necessary to adapt for nixpkgs. For a related example, using the repo instead of the tar distribution for Ruby caused a subtle problem where the commit hash was not propagated, which broke the bootsnap gem's cache invalidation (fixed in , by using the tarball). The real question here, I think, is how upstream expects native compilation to be used if their tarball doesn't support it.

patches = patches fetchpatch; <del> src = fetchurl { url = "mirror://gnu/emacs/${name}.tar.xz"; </del> <ins> src = fetchFromSavannah { repo = "emacs"; rev = version; </ins> inherit sha256; };


Question:
On startup, Tor Browser doesn't start if some variables about Wayland aren't set. Steps to reproduce the behavior: and (if set) Tor Browser in a terminal and see the error message. Tor Browser should start. This issue was caused by . currently does not fix the problem. In the meantime, an easy fix would be : <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Notifying peoples from the aforementioned PRs instead. Please run and paste the result.
I can confirm this issue
thanks !

TMPDIR="''${TMPDIR:-/tmp}"  HOME="$HOME"  XAUTHORITY="''${XAUTHORITY:-$HOME/.Xauthority}"  <del> DISPLAY="$DISPLAY"  </del> <ins> DISPLAY="''${DISPLAY:-}"  </ins> DBUS_SESSION_BUS_ADDRESS="''${DBUS_SESSION_BUS_ADDRESS:-unix:path=$XDG_RUNTIME_DIR/bus}"   XDG_DATA_HOME="$HOME/.local/share"


Question:
On startup, Tor Browser doesn't start if some variables about Wayland aren't set. Steps to reproduce the behavior: and (if set) Tor Browser in a terminal and see the error message. Tor Browser should start. This issue was caused by . currently does not fix the problem. In the meantime, an easy fix would be : <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Notifying peoples from the aforementioned PRs instead. Please run and paste the result.
I can confirm this issue
thanks !

PULSE_SERVER="''${PULSE_SERVER:-}"  PULSE_COOKIE="''${PULSE_COOKIE:-}"   <del> MOZ_ENABLE_WAYLAND=$MOZ_ENABLE_WAYLAND  WAYLAND_DISPLAY="$WAYLAND_DISPLAY"  XDG_RUNTIME_DIR="$XDG_RUNTIME_DIR"  XCURSOR_PATH="$XCURSOR_PATH"  </del> <ins> MOZ_ENABLE_WAYLAND="''${MOZ_ENABLE_WAYLAND:-}"  WAYLAND_DISPLAY="''${WAYLAND_DISPLAY:-}"  XDG_RUNTIME_DIR="''${XDG_RUNTIME_DIR:-}"  XCURSOR_PATH="''${XCURSOR_PATH:-}"  </ins>  APULSE_PLAYBACK_DEVICE="''${APULSE_PLAYBACK_DEVICE:-plug:dmix}"


Question:
On startup, Tor Browser doesn't start if some variables about Wayland aren't set. Steps to reproduce the behavior: and (if set) Tor Browser in a terminal and see the error message. Tor Browser should start. This issue was caused by . currently does not fix the problem. In the meantime, an easy fix would be : <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Notifying peoples from the aforementioned PRs instead. Please run and paste the result.
I can confirm this issue
thanks !

LD_LIBRARY_PATH=$libPath $TBB_IN_STORE/TorBrowser/Tor/tor --version >/dev/null echo "Checking tor-browser wrapper ..." <del> DISPLAY="" MOZ_ENABLE_WAYLAND="" WAYLAND_DISPLAY="" XAUTHORITY=""  XCURSOR_PATH="" XDG_RUNTIME_DIR="" XDG_SESSION_TYPE=""  DBUS_SESSION_BUS_ADDRESS="" TBB_HOME=$(mktemp -d)  </del> <ins> TBB_HOME=$(mktemp -d)  </ins> $out/bin/tor-browser --version >/dev/null '';


Question:
The option, which enables by default on high-resolution displays like my 4K laptop screen, is supposed to set the console font within the initrd before displaying the LUKS password prompt. However, with , this does not happen until stage 2, so the prompt is tiny. Enable , , and . The console font should be switched before the LUKS password prompt, not after.
Relevant code is probably that it sets . should then properly set everything up if it can find its files in :
Does it work when you do ?
No, it can’t, because points to a font file that’s not present in the initrd.
This works though. It’s a little jarring in that the font is changed about a second before the framebuffer resolution is changed, so it’s temporarily huge. Ideally those would happen simultaneously. But at least they both happen in time for the LUKS prompt.

"${config.boot.initrd.systemd.package}/lib/systemd/systemd-vconsole-setup" "${config.boot.initrd.systemd.package.kbd}/bin/setfont" "${config.boot.initrd.systemd.package.kbd}/bin/loadkeys" <del> "${config.boot.initrd.systemd.package.kbd.gzip}/bin/gzip" # keyboard layouts are compressed </del> <ins> "${config.boot.initrd.systemd.package.kbd.gzip}/bin/gzip" # Fonts and keyboard layouts are compressed ] ++ optionals (hasPrefix builtins.storeDir cfg.font) [ "${cfg.font}" ] ++ optionals (hasPrefix builtins.storeDir cfg.keyMap) [ "${cfg.keyMap}" </ins> ]; systemd.services.reload-systemd-vconsole-setup =


Question: , an application that simulates user input to keep the screen awake when pressing gamepad buttons, relies on on Plasma Wayland to do this. However, isn't installed (or at least, it's not in ) with a default Plasma installation, making not work: (Among other errors) Steps to reproduce the behavior: Plasma (), without "installing" ; a Plasma Wayland session; ; 'll see the error message, and the program won't work. There is no error message and the program works (which is what happens by installing ). I don't know if the best solution is to add to Plasma or to . I'd vote for the former, since (if I'm not wrong), is already installed with Plasma, it's just not in PATH, and I don't see the harm in being there. Still, that's why I opened an issue. By the way, can't be installed "alone". NixOS says: <!-- 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.

plasma-browser-integration konsole oxygen <ins> (lib.getBin qttools) # Expose qdbus in PATH </ins> ]; in requiredPackages


Question: , an application that simulates user input to keep the screen awake when pressing gamepad buttons, relies on on Plasma Wayland to do this. However, isn't installed (or at least, it's not in ) with a default Plasma installation, making not work: (Among other errors) Steps to reproduce the behavior: Plasma (), without "installing" ; a Plasma Wayland session; ; 'll see the error message, and the program won't work. There is no error message and the program works (which is what happens by installing ). I don't know if the best solution is to add to Plasma or to . I'd vote for the former, since (if I'm not wrong), is already installed with Plasma, it's just not in PATH, and I don't see the harm in being there. Still, that's why I opened an issue. By the way, can't be installed "alone". NixOS says: <!-- 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.

services.accounts-daemon.enable = true; # when changing an account picture the accounts-daemon reads a temporary file containing the image which systemsettings5 may place under /tmp systemd.services.accounts-daemon.serviceConfig.PrivateTmp = false; <ins> services.power-profiles-daemon.enable = mkDefault true; services.system-config-printer.enable = mkIf config.services.printing.enable (mkDefault true); </ins> services.udisks2.enable = true; services.upower.enable = config.powerManagement.enable; <del> services.system-config-printer.enable = mkIf config.services.printing.enable (mkDefault true); </del> services.xserver.libinput.enable = mkDefault true; # Extra UDEV rules used by Solid


Question:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: qtcreator <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 5.0.3 desired version: 7.0.1 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Version 8.0.0 is now available.

<ins> { stdenv , lib , fetchurl , cmake , pkg-config , ninja , python3 , qtbase , qt5compat , qtdeclarative , qtdoc , qtquick3d , qtquicktimeline , qtserialport , qtsvg , qttools , qtwebengine , qtshadertools , wrapQtAppsHook , yaml-cpp , litehtml , gumbo , llvmPackages , rustc-demangle , elfutils , perf }: stdenv.mkDerivation rec { pname = "qtcreator"; version = "9.0.2"; src = fetchurl { url = "https://download.qt.io/official_releases/${pname}/${lib.versions.majorMinor version}/${version}/qt-creator-opensource-src-${version}.tar.xz"; sha256 = "sha256-7KWMxcoNOXiWlAVCYZzyA/WWLuPIggCBIics23Ifoyg="; }; nativeBuildInputs = [ cmake pkg-config qttools wrapQtAppsHook python3 ninja ]; buildInputs = [ qtbase qtdoc qtsvg qtquick3d qtwebengine qtserialport qtshadertools qt5compat qtdeclarative qtquicktimeline yaml-cpp litehtml gumbo llvmPackages.libclang llvmPackages.llvm rustc-demangle elfutils ]; cmakeFlags = [ # workaround for missing CMAKE_INSTALL_DATAROOTDIR # in pkgs/development/tools/build-managers/cmake/setup-hook.sh "-DCMAKE_INSTALL_DATAROOTDIR=${placeholder "out"}/share" # qtdeclarative in nixpkgs does not provide qmlsc # fix can't find Qt6QmlCompilerPlusPrivate "-DQT_NO_FIND_QMLSC=TRUE" "-DWITH_DOCS=ON" "-DBUILD_DEVELOPER_DOCS=ON" "-DBUILD_QBS=OFF" "-DQTC_CLANG_BUILDMODE_MATCH=ON" "-DCLANGTOOLING_LINK_CLANG_DYLIB=ON" ]; qtWrapperArgs = [ "--set-default PERFPROFILER_PARSER_FILEPATH ${lib.getBin perf}/bin" ]; postInstall = '' substituteInPlace $out/share/applications/org.qt-project.qtcreator.desktop  --replace "Exec=qtcreator" "Exec=$out/bin/qtcreator" ''; meta = with lib; { description = "Cross-platform IDE tailored to the needs of Qt developers"; longDescription = '' Qt Creator is a cross-platform IDE (integrated development environment) tailored to the needs of Qt developers. It includes features such as an advanced code editor, a visual debugger and a GUI designer. ''; homepage = "https://wiki.qt.io/Qt_Creator"; license = licenses.lgpl3Plus; maintainers = [ maintainers.rewine ]; platforms = platforms.linux; }; } </ins>


Question:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: qtcreator <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 5.0.3 desired version: 7.0.1 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Version 8.0.0 is now available.

inherit (linuxPackages) perf; }; <ins> qtcreator-qt6 = qt6Packages.callPackage ../development/tools/qtcreator/qt6.nix { inherit (linuxPackages) perf; stdenv = llvmPackages_14.stdenv; llvmPackages = llvmPackages_14; }; </ins> qxmledit = libsForQt5.callPackage ../applications/editors/qxmledit {} ; r10k = callPackage ../tools/system/r10k { };


Question:
I notice zoom-us from nixpkgs-unstable gets killed by SIGILL shortly after the application window is shown. This does not occur when running zoom-us from NixOS 21.11. A strace ends with the following output: Observe that the zoom process is killed by SIGILL shortly after the application window is shown. The Zoom application proceeds to run without crashing. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
I stepped through commits that touched zoom-us. The behavior appears to start with (no launch), resp. with (SIGILL observed).
I can‘t reproduce this issue, at least I get into a video call and to making faces at myself for a minute without issues. I am running zoom 5.10.4, on x86_64-linux with kernel 5.17.9.
I didn't see this on my system using the version from nixpkgs . It's expected that would not launch (it's fixed by the commits after). These should really have been one commit, or in another order to allow bisection, but oh well.
From what I can muster, SIGILL is caught while in It looks like is part of the binary distribution of Zoom and not built as part of nixpkgs? But I figure if can run it with no crash it’s more likely an application bug rather than some ABI issue?
I now notice that one Zoom invocation results in two coredumps. The other one is a SIGSYS arising from libc. I’m not really versed in such dark magics, but FWIW:
I really don't expect to be able to debug this, but could you post the output of and (and maybe if the output is short, particularly around the marker) from gdb on the SIGILL core? To me this really feels like a zoom problem. You don't happen to be using an ancient or unusual processor do you?
It looks like version 5.10.6 (3192) is out for linux now, so it might be worth trying that too.
Cheers, that seems to resolve the problem. Not really, it’s an i9-10885H. In case you’re still curious for whatever reason, I’ve attached the information copied from gdb. Otherwise I’d say this issue is obsoleted by the new Zoom release. (NB just said “No function contains program counter for selected frame.”)
my zoom is dying too, I got it working for now with
Thanks, that's pretty interesting; something jumps into the middle of an instruction. Good that updating it works anyway.

version = { aarch64-darwin = "5.10.4.6592"; x86_64-darwin = "5.10.4.6592"; <del> x86_64-linux = "5.10.4.2845"; </del> <ins> x86_64-linux = "5.10.6.3192"; </ins> }.${system} or throwSystem; srcs = {


Question:
I notice zoom-us from nixpkgs-unstable gets killed by SIGILL shortly after the application window is shown. This does not occur when running zoom-us from NixOS 21.11. A strace ends with the following output: Observe that the zoom process is killed by SIGILL shortly after the application window is shown. The Zoom application proceeds to run without crashing. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
I stepped through commits that touched zoom-us. The behavior appears to start with (no launch), resp. with (SIGILL observed).
I can‘t reproduce this issue, at least I get into a video call and to making faces at myself for a minute without issues. I am running zoom 5.10.4, on x86_64-linux with kernel 5.17.9.
I didn't see this on my system using the version from nixpkgs . It's expected that would not launch (it's fixed by the commits after). These should really have been one commit, or in another order to allow bisection, but oh well.
From what I can muster, SIGILL is caught while in It looks like is part of the binary distribution of Zoom and not built as part of nixpkgs? But I figure if can run it with no crash it’s more likely an application bug rather than some ABI issue?
I now notice that one Zoom invocation results in two coredumps. The other one is a SIGSYS arising from libc. I’m not really versed in such dark magics, but FWIW:
I really don't expect to be able to debug this, but could you post the output of and (and maybe if the output is short, particularly around the marker) from gdb on the SIGILL core? To me this really feels like a zoom problem. You don't happen to be using an ancient or unusual processor do you?
It looks like version 5.10.6 (3192) is out for linux now, so it might be worth trying that too.
Cheers, that seems to resolve the problem. Not really, it’s an i9-10885H. In case you’re still curious for whatever reason, I’ve attached the information copied from gdb. Otherwise I’d say this issue is obsoleted by the new Zoom release. (NB just said “No function contains program counter for selected frame.”)
my zoom is dying too, I got it working for now with
Thanks, that's pretty interesting; something jumps into the middle of an instruction. Good that updating it works anyway.

}; x86_64-linux = fetchurl { url = "https://zoom.us/client/${version}/zoom_x86_64.pkg.tar.xz"; <del> sha256 = "9gspydrGaEjzAM0nK1u0XNm07HTupJ2wnPxCFWy+Nts="; </del> <ins> sha256 = "8QIkF5+875VFoGK6T0CROsqML6bJDG934c1gkuz8Klk="; </ins> }; };


Question:
ACME certificates cannot be provisioned automatically, even though run in manual mode succeeds. This seems to occur whenever allocating a new certificate, and possibly when renewing one. System: (Flounder) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: "16.03.1168."
Hi guys; if any of you know what's going on here, it'd be greatly appreciated. From what I can tell, the Terms of Service are out of date for nixpkgs's version of letsencrypt - and this makes the service pretty much unusable. If you have any ideas about how we can fix this, I'll be happy to investigate further and make a fix.
Luckily only happens when creating a new account, so renews are not affected. Thanks for reporting. Fixed. :beers:
Awesome; thanks for the very fast fix! I'm wondering if there's a more permanent way to solve this - being unable to deploy new servers whenever letsencrypt releases a new TOS seems a bit fragile. Maybe we could add a configuration option to set the TOS hash on the command line when invoking simp_le?
That's a good idea. Also as we're right before releasing 16.09 we should add that option before the release so NixOS users can easily update the hash themselves if needed.
Hi! Even if the new configuration option to set the TOSH hash would only appear in (makes sense, it's a new feature), is the hash fix () going to reach ? It doesn't seem to be there for now:
Thanks for the reminder. I'll look at it. The only potential problem is that is at another version in 16.03. The patch should apply cleanly, though.
any news? If someone need a fix, just add the following snippet to your configuration to override the package with a patched one: Then you can use the options as usual! But I hope the patch will soon be available in :)
Ah, thanks for testing that! In that case I'll simply backport that patch.
Ok, backported. Will be in the 16.03 channel soon. I'll keep this issue open because I want an to add an option for 16.09 to specify the TOS hash in the module.
Confirmed to work on ! Thanks a lot!
are you still planning on doing this in time for 16.09?
what are actionables here for 16.09?
We won't implement this for now because we need to replace simp_le anyway.
This is happening again?
That fix worked for me. I've no idea if it breaks anything else for others.

python2Packages.buildPythonApplication rec { name = "certbot-${version}"; <del> version = "0.11.1"; </del> <ins> version = "0.19.0"; </ins> src = fetchFromGitHub { owner = "certbot"; repo = "certbot"; rev = "v${version}"; <del> sha256 = "0f8s6wzj69gnqld6iaskmmwyg5zy5v3zwhp1n1izxixm0vhkzgrq"; </del> <ins> sha256 = "14i3q59v7j0q2pa1dri420fhil4h0vgl4vb471hp81f4y14gq6h7"; </ins> }; propagatedBuildInputs = with python2Packages; [


Question:
ACME certificates cannot be provisioned automatically, even though run in manual mode succeeds. This seems to occur whenever allocating a new certificate, and possibly when renewing one. System: (Flounder) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: "16.03.1168."
Hi guys; if any of you know what's going on here, it'd be greatly appreciated. From what I can tell, the Terms of Service are out of date for nixpkgs's version of letsencrypt - and this makes the service pretty much unusable. If you have any ideas about how we can fix this, I'll be happy to investigate further and make a fix.
Luckily only happens when creating a new account, so renews are not affected. Thanks for reporting. Fixed. :beers:
Awesome; thanks for the very fast fix! I'm wondering if there's a more permanent way to solve this - being unable to deploy new servers whenever letsencrypt releases a new TOS seems a bit fragile. Maybe we could add a configuration option to set the TOS hash on the command line when invoking simp_le?
That's a good idea. Also as we're right before releasing 16.09 we should add that option before the release so NixOS users can easily update the hash themselves if needed.
Hi! Even if the new configuration option to set the TOSH hash would only appear in (makes sense, it's a new feature), is the hash fix () going to reach ? It doesn't seem to be there for now:
Thanks for the reminder. I'll look at it. The only potential problem is that is at another version in 16.03. The patch should apply cleanly, though.
any news? If someone need a fix, just add the following snippet to your configuration to override the package with a patched one: Then you can use the options as usual! But I hope the patch will soon be available in :)
Ah, thanks for testing that! In that case I'll simply backport that patch.
Ok, backported. Will be in the 16.03 channel soon. I'll keep this issue open because I want an to add an option for 16.09 to specify the TOS hash in the module.
Confirmed to work on ! Thanks a lot!
are you still planning on doing this in time for 16.09?
what are actionables here for 16.09?
We won't implement this for now because we need to replace simp_le anyway.
This is happening again?
That fix worked for me. I've no idea if it breaks anything else for others.

pythonPackages.buildPythonApplication rec { pname = "simp_le-client"; <del> version = "0.2.0"; </del> <ins> version = "0.6.1"; </ins> name = "${pname}-${version}"; src = pythonPackages.fetchPypi { inherit pname version; <del> sha256 = "1zg18jfry9mvkri3yd2f5mwfsl27ac9zmnll3bm93jb91jhd6ssh"; </del> <ins> sha256 = "0x4fky9jizs3xi55cdy217cvm3ikpghiabysan71b07ackkdfj6k"; </ins> }; checkPhase = ''


Question:
This is from nixos-unstable current. For some reason, I get build failures with ZSH. This is with a nixpkgs (system=x86_64-linux) and nixpkgs.crossSystem set to . This seems to be the same failure (I checked, its the same derivation): Steps to reproduce the behavior: ... ... ... A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. 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.
couldn't fix it. I'll leave this assigned to myself so i remember to take a another shot at it in ~6 months
Fixed by

, texinfo , ncurses , pcre <ins> , pkg-config </ins> , buildPackages }: let


Question:
This is from nixos-unstable current. For some reason, I get build failures with ZSH. This is with a nixpkgs (system=x86_64-linux) and nixpkgs.crossSystem set to . This seems to be the same failure (I checked, its the same derivation): Steps to reproduce the behavior: ... ... ... A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. 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.
couldn't fix it. I'll leave this assigned to myself so i remember to take a another shot at it in ~6 months
Fixed by

]; strictDeps = true; <del> nativeBuildInputs = [ autoreconfHook perl groff texinfo pcre] </del> <ins> nativeBuildInputs = [ autoreconfHook perl groff texinfo pkg-config ] </ins> ++ lib.optionals stdenv.isLinux [ util-linux yodl ]; buildInputs = [ ncurses pcre ];


Question:
This is from nixos-unstable current. For some reason, I get build failures with ZSH. This is with a nixpkgs (system=x86_64-linux) and nixpkgs.crossSystem set to . This seems to be the same failure (I checked, its the same derivation): Steps to reproduce the behavior: ... ... ... A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. 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.
couldn't fix it. I'll leave this assigned to myself so i remember to take a another shot at it in ~6 months
Fixed by

"zsh_cv_sys_dynamic_strip_lib=yes" ]; <ins> preConfigure = '' # use pkg-config instead of pcre-config configureFlagsArray+=("PCRECONF=''${PKG_CONFIG} libpcre") ''; </ins> # the zsh/zpty module is not available on hydra # so skip groups Y Z checkFlags = map (T: "TESTNUM=${T}") (lib.stringToCharacters "ABCDEVW");


Question:
Project description Metadata homepage URL: source URL: license: Business Source License 1.1, change to Apache License 2.0 on June 1st 2027 platforms: linux
Can you check out my PR if everything works?

</listitem> <listitem> <para> <ins> <link xlink:href="https://dragonflydb.io/">dragonflydb</link>, a modern replacement for Redis and Memcached. Available as <link linkend="opt-services.dragonflydb.enable">services.dragonflydb</link>. </para> </listitem> <listitem> <para> </ins> <link xlink:href="https://github.com/leetronics/infnoise">infnoise</link>, a hardware True Random Number Generator dongle. Available as <link xlink:href="options.html#opt-services.infnoise.enable">services.infnoise</link>.


Question:
Project description Metadata homepage URL: source URL: license: Business Source License 1.1, change to Apache License 2.0 on June 1st 2027 platforms: linux
Can you check out my PR if everything works?

- [appvm](https://github.com/jollheef/appvm), Nix based app VMs. Available as [virtualisation.appvm](options.html#opt-virtualisation.appvm.enable). <ins> - [dragonflydb](https://dragonflydb.io/), a modern replacement for Redis and Memcached. Available as [services.dragonflydb](#opt-services.dragonflydb.enable). </ins> - [infnoise](https://github.com/leetronics/infnoise), a hardware True Random Number Generator dongle. Available as [services.infnoise](options.html#opt-services.infnoise.enable).


Question:
Project description Metadata homepage URL: source URL: license: Business Source License 1.1, change to Apache License 2.0 on June 1st 2027 platforms: linux
Can you check out my PR if everything works?

./services/databases/clickhouse.nix ./services/databases/cockroachdb.nix ./services/databases/couchdb.nix <ins> ./services/databases/dragonflydb.nix </ins> ./services/databases/firebird.nix ./services/databases/foundationdb.nix ./services/databases/hbase.nix


Question:
Project description Metadata homepage URL: source URL: license: Business Source License 1.1, change to Apache License 2.0 on June 1st 2027 platforms: linux
Can you check out my PR if everything works?

<ins> { config, lib, pkgs, ... }: with lib; let cfg = config.services.dragonflydb; dragonflydb = pkgs.dragonflydb; settings = { port = cfg.port; dir = "/var/lib/dragonflydb"; keys_output_limit = cfg.keysOutputLimit; } // (lib.optionalAttrs (cfg.bind != null) { bind = cfg.bind; }) // (lib.optionalAttrs (cfg.requirePass != null) { requirepass = cfg.requirePass; }) // (lib.optionalAttrs (cfg.maxMemory != null) { maxmemory = cfg.maxMemory; }) // (lib.optionalAttrs (cfg.memcachePort != null) { memcache_port = cfg.memcachePort; }) // (lib.optionalAttrs (cfg.dbNum != null) { dbnum = cfg.dbNum; }) // (lib.optionalAttrs (cfg.cacheMode != null) { cache_mode = cfg.cacheMode; }); in { ###### interface options = { services.dragonflydb = { enable = mkEnableOption "DragonflyDB"; user = mkOption { type = types.str; default = "dragonfly"; description = "The user to run DragonflyDB as"; }; port = mkOption { type = types.port; default = 6379; description = "The TCP port to accept connections."; }; bind = mkOption { type = with types; nullOr str; default = "127.0.0.1"; description = '' The IP interface to bind to. <literal>null</literal> means "all interfaces". ''; }; requirePass = mkOption { type = with types; nullOr str; default = null; description = "Password for database"; example = "letmein!"; }; maxMemory = mkOption { type = with types; nullOr ints.unsigned; default = null; description = '' The maximum amount of memory to use for storage (in bytes). <literal>null</literal> means this will be automatically set. ''; }; memcachePort = mkOption { type = with types; nullOr port; default = null; description = '' To enable memcached compatible API on this port. <literal>null</literal> means disabled. ''; }; keysOutputLimit = mkOption { type = types.ints.unsigned; default = 8192; description = '' Maximum number of returned keys in keys command. <literal>keys</literal> is a dangerous command. We truncate its result to avoid blowup in memory when fetching too many keys. ''; }; dbNum = mkOption { type = with types; nullOr ints.unsigned; default = null; description = "Maximum number of supported databases for <literal>select</literal>"; }; cacheMode = mkOption { type = with types; nullOr bool; default = null; description = '' Once this mode is on, Dragonfly will evict items least likely to be stumbled upon in the future but only when it is near maxmemory limit. ''; }; }; }; ###### implementation config = mkIf config.services.dragonflydb.enable { users.users = optionalAttrs (cfg.user == "dragonfly") { dragonfly.description = "DragonflyDB server user"; dragonfly.isSystemUser = true; dragonfly.group = "dragonfly"; }; users.groups = optionalAttrs (cfg.user == "dragonfly") { dragonfly = { }; }; environment.systemPackages = [ dragonflydb ]; systemd.services.dragonflydb = { description = "DragonflyDB server"; wantedBy = [ "multi-user.target" ]; after = [ "network.target" ]; serviceConfig = { ExecStart = "${dragonflydb}/bin/dragonfly --alsologtostderr ${builtins.concatStringsSep " " (attrsets.mapAttrsToList (n: v: "--${n} ${strings.escapeShellArg v}") settings)}"; User = cfg.user; # Filesystem access ReadWritePaths = [ settings.dir ]; StateDirectory = "dragonflydb"; StateDirectoryMode = "0700"; # Process Properties LimitMEMLOCK = "infinity"; # Caps CapabilityBoundingSet = ""; NoNewPrivileges = true; # Sandboxing ProtectSystem = "strict"; ProtectHome = true; PrivateTmp = true; PrivateDevices = true; ProtectKernelTunables = true; ProtectKernelModules = true; ProtectControlGroups = true; LockPersonality = true; RestrictAddressFamilies = [ "AF_INET" "AF_INET6" ]; RestrictRealtime = true; PrivateMounts = true; MemoryDenyWriteExecute = true; }; }; }; } </ins>


Question:
Project description Metadata homepage URL: source URL: license: Business Source License 1.1, change to Apache License 2.0 on June 1st 2027 platforms: linux
Can you check out my PR if everything works?

<ins> { fetchFromGitHub , fetchurl , lib , stdenv , double-conversion , gperftools , mimalloc , rapidjson , liburing , xxHash , abseil-cpp_202111 , gbenchmark , glog , gtest , jemalloc , gcc-unwrapped , autoconf , autoconf-archive , automake , cmake , ninja , boost , libunwind , libtool , openssl }: let pname = "dragonflydb"; version = "0.1.0"; src = fetchFromGitHub { owner = pname; repo = "dragonfly"; rev = "v${version}"; hash = "sha256-P6WMW/n+VezWDXGagT4B+ZYyCp8oufDV6MTrpKpLZcs="; fetchSubmodules = true; }; # Needed exactly 5.4.4 for patch to work lua = fetchurl { url = "https://github.com/lua/lua/archive/refs/tags/v5.4.4.tar.gz"; hash = "sha256-L/ibvqIqfIuRDWsAb1ukVZ7c9GiiVTfO35mI7ZD2tFA="; }; in stdenv.mkDerivation { inherit pname version src; postPatch = '' mkdir -p ./build/{third_party,_deps} ln -s ${double-conversion.src} ./build/third_party/dconv ln -s ${mimalloc.src} ./build/third_party/mimalloc ln -s ${rapidjson.src} ./build/third_party/rapidjson ln -s ${gbenchmark.src} ./build/_deps/benchmark-src ln -s ${gtest.src} ./build/_deps/gtest-src cp -R --no-preserve=mode,ownership ${gperftools.src} ./build/third_party/gperf cp -R --no-preserve=mode,ownership ${liburing.src} ./build/third_party/uring cp -R --no-preserve=mode,ownership ${xxHash.src} ./build/third_party/xxhash cp -R --no-preserve=mode,ownership ${abseil-cpp_202111.src} ./build/_deps/abseil_cpp-src cp -R --no-preserve=mode,ownership ${glog.src} ./build/_deps/glog-src chmod u+x ./build/third_party/uring/configure cp ./build/third_party/xxhash/cli/xxhsum.{1,c} ./build/third_party/xxhash patch -p1 -d ./build/_deps/glog-src < ${./glog.patch} sed ' s@REPLACEJEMALLOCURL@file://${jemalloc.src}@ s@REPLACELUAURL@file://${lua}@ ' ${./fixes.patch} | patch -p1 ''; nativeBuildInputs = [ autoconf autoconf-archive automake cmake ninja ]; buildInputs = [ boost libunwind libtool openssl ]; cmakeFlags = [ "-DCMAKE_AR=${gcc-unwrapped}/bin/gcc-ar" "-DCMAKE_RANLIB=${gcc-unwrapped}/bin/gcc-ranlib" ]; ninjaFlags = "dragonfly"; doCheck = false; dontUseNinjaInstall = true; installPhase = '' runHook preInstall mkdir -p $out/bin cp ./dragonfly $out/bin runHook postInstall ''; meta = with lib; { description = "A modern replacement for Redis and Memcached"; homepage = "https://dragonflydb.io/"; license = licenses.bsl11; platforms = platforms.linux; maintainers = with maintainers; [ yureien ]; }; } </ins>


Question:
Project description Metadata homepage URL: source URL: license: Business Source License 1.1, change to Apache License 2.0 on June 1st 2027 platforms: linux
Can you check out my PR if everything works?

<ins> diff --git a/helio/cmake/third_party.cmake b/helio/cmake/third_party.cmake index aeb78d9..e9d4e6b 100644 --- a/helio/cmake/third_party.cmake +++ b/helio/cmake/third_party.cmake @@ -143,7 +143,7 @@ endfunction() FetchContent_Declare( gtest -  URL https://github.com/google/googletest/archive/release-1.11.0.zip +  DOWNLOAD_COMMAND true ) FetchContent_GetProperties(gtest) @@ -154,7 +154,7 @@ endif () FetchContent_Declare( benchmark -  URL https://github.com/google/benchmark/archive/v1.6.1.tar.gz +  DOWNLOAD_COMMAND true ) FetchContent_GetProperties(benchmark) @@ -169,7 +169,7 @@ endif () FetchContent_Declare( abseil_cpp -  URL https://github.com/abseil/abseil-cpp/archive/20211102.0.tar.gz +  DOWNLOAD_COMMAND true PATCH_COMMAND patch -p1 < "${CMAKE_CURRENT_LIST_DIR}/../patches/abseil-20211102.patch" ) @@ -183,11 +183,7 @@ endif() FetchContent_Declare( glog -  GIT_REPOSITORY https://github.com/romange/glog -  GIT_TAG Absl - -  GIT_PROGRESS    TRUE -  GIT_SHALLOW     TRUE +  DOWNLOAD_COMMAND true ) FetchContent_GetProperties(glog) @@ -233,10 +229,7 @@ endif() add_third_party( gperf -  URL https://github.com/gperftools/gperftools/archive/gperftools-2.9.1.tar.gz -  #GIT_REPOSITORY https://github.com/gperftools/gperftools -  #GIT_TAG gperftools-2.9.1 -  GIT_SHALLOW TRUE +  DOWNLOAD_COMMAND true PATCH_COMMAND autoreconf -i   # update runs every time for some reason # CMAKE_PASS_FLAGS "-DGPERFTOOLS_BUILD_HEAP_PROFILER=OFF -DGPERFTOOLS_BUILD_HEAP_CHECKER=OFF  #                   -DGPERFTOOLS_BUILD_DEBUGALLOC=OFF -DBUILD_TESTING=OFF   @@ -260,11 +253,12 @@ else() endif() add_third_party(mimalloc -  URL https://github.com/microsoft/mimalloc/archive/refs/tags/v2.0.5.tar.gz +  DOWNLOAD_COMMAND true # Add -DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_FLAGS=-O0 to debug CMAKE_PASS_FLAGS "-DCMAKE_BUILD_TYPE=Release -DMI_BUILD_SHARED=OFF -DMI_BUILD_TESTS=OFF  -                    -DMI_INSTALL_TOPLEVEL=ON -DMI_OVERRIDE=${MI_OVERRIDE} -DCMAKE_C_FLAGS=-g" +                    -DMI_INSTALL_TOPLEVEL=ON -DMI_OVERRIDE=${MI_OVERRIDE} -DCMAKE_C_FLAGS=-g  +                    -DCMAKE_INSTALL_LIBDIR=${THIRD_PARTY_LIB_DIR}/mimalloc/lib" BUILD_COMMAND make -j4 mimalloc-static INSTALL_COMMAND make install @@ -274,7 +268,7 @@ add_third_party(mimalloc ) add_third_party(jemalloc -  URL https://github.com/jemalloc/jemalloc/releases/download/5.2.1/jemalloc-5.2.1.tar.bz2 +  URL REPLACEJEMALLOCURL PATCH_COMMAND ./autogen.sh CONFIGURE_COMMAND <SOURCE_DIR>/configure --prefix=${THIRD_PARTY_LIB_DIR}/jemalloc --with-jemalloc-prefix=je_ --disable-libdl ) @@ -282,24 +276,23 @@ add_third_party(jemalloc add_third_party( xxhash -  URL https://github.com/Cyan4973/xxHash/archive/v0.8.0.tar.gz +  DOWNLOAD_COMMAND true SOURCE_SUBDIR cmake_unofficial -  CMAKE_PASS_FLAGS "-DCMAKE_POSITION_INDEPENDENT_CODE=ON -DBUILD_SHARED_LIBS=OFF" +  CMAKE_PASS_FLAGS "-DCMAKE_POSITION_INDEPENDENT_CODE=ON -DBUILD_SHARED_LIBS=OFF  +                    -DCMAKE_INSTALL_LIBDIR=${THIRD_PARTY_LIB_DIR}/xxhash/lib" ) add_third_party( uring -  GIT_REPOSITORY https://github.com/axboe/liburing.git -  GIT_TAG liburing-2.1 +  DOWNLOAD_COMMAND true CONFIGURE_COMMAND <SOURCE_DIR>/configure --prefix=${THIRD_PARTY_LIB_DIR}/uring BUILD_IN_SOURCE 1 ) add_third_party( rapidjson -  GIT_REPOSITORY https://github.com/Tencent/rapidjson.git -  GIT_TAG 1a803826f1197b5e30703afe4b9c0e7dd48074f5 +  DOWNLOAD_COMMAND true CMAKE_PASS_FLAGS "-DRAPIDJSON_BUILD_TESTS=OFF -DRAPIDJSON_BUILD_EXAMPLES=OFF  -DRAPIDJSON_BUILD_DOC=OFF" LIB "none" diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt index 0dc0824..d5b38b3 100644 --- a/src/CMakeLists.txt +++ b/src/CMakeLists.txt @@ -1,6 +1,6 @@ add_third_party( lua -  URL https://github.com/lua/lua/archive/refs/tags/v5.4.4.tar.gz +  URL REPLACELUAURL PATCH_COMMAND patch -p1 -i "${CMAKE_SOURCE_DIR}/patches/lua-v5.4.4.patch" CONFIGURE_COMMAND echo BUILD_IN_SOURCE 1 @@ -11,7 +11,8 @@ add_third_party( add_third_party( dconv -  URL https://github.com/google/double-conversion/archive/refs/tags/v3.2.0.tar.gz +  DOWNLOAD_COMMAND true +  CMAKE_PASS_FLAGS "-DCMAKE_INSTALL_LIBDIR=${THIRD_PARTY_LIB_DIR}/dconv/lib" LIB libdouble-conversion.a ) </ins>


Question:
Project description Metadata homepage URL: source URL: license: Business Source License 1.1, change to Apache License 2.0 on June 1st 2027 platforms: linux
Can you check out my PR if everything works?

<ins> diff --git a/CMakeLists.txt b/CMakeLists.txt index 846b4448..b4900ead 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -39,6 +39,7 @@ option (PRINT_UNSYMBOLIZED_STACK_TRACES "Print file offsets in traces instead of symbolizing" OFF) option (WITH_CUSTOM_PREFIX "Enable support for user-generated message prefixes" ON) option (WITH_GFLAGS "Use gflags" ON) +option (WITH_ABSL "Use absl flags" OFF) option (WITH_GTEST "Use Google Test" ON) option (WITH_PKGCONFIG "Enable pkg-config support" ON) option (WITH_SYMBOLIZE "Enable symbolize module" ON) @@ -87,6 +88,13 @@ if (WITH_GFLAGS) endif (gflags_FOUND) endif (WITH_GFLAGS) +if (WITH_ABSL) +  set (HAVE_ABSL_FLAGS 1) +  set (ac_cv_have_abslflags 1) +else (WITH_ABSL) +set (ac_cv_have_abslflags 0) +endif (WITH_ABSL) + find_package (Threads) find_package (Unwind) @@ -1025,7 +1033,7 @@ write_basic_package_version_file ( ${CMAKE_CURRENT_BINARY_DIR}/glog-config-version.cmake COMPATIBILITY SameMajorVersion) -export (TARGETS glog NAMESPACE glog:: FILE glog-targets.cmake) +# export (TARGETS glog NAMESPACE glog:: FILE glog-targets.cmake) export (PACKAGE glog) get_filename_component (_PREFIX "${CMAKE_INSTALL_PREFIX}" ABSOLUTE) diff --git a/src/base/commandlineflags.h b/src/base/commandlineflags.h index bcb12dea..1c9d9294 100644 --- a/src/base/commandlineflags.h +++ b/src/base/commandlineflags.h @@ -57,6 +57,25 @@ #include <gflags/gflags.h> +#else +#ifdef HAVE_ABSL_FLAGS +#include <absl/flags/flag.h> + +#define FLAG(name) absl::GetFlag(FLAGS_##name) + +#define DEFINE_bool(name, value, meaning)  +  ABSL_FLAG(bool, name, value, meaning) + +#define DEFINE_int32(name, value, meaning)  +  ABSL_FLAG(GOOGLE_NAMESPACE::int32, name, value, meaning) + +#define DEFINE_uint32(name, value, meaning)  +  ABSL_FLAG(GOOGLE_NAMESPACE::uint32, name, value, meaning) + +#define DEFINE_string(name, value, meaning)  +  ABSL_FLAG(std::string, name, value, meaning) + + #else #include <glog/logging.h> @@ -108,6 +127,7 @@ }                                                            using fLS::FLAGS_##name +#endif #endif  // HAVE_LIB_GFLAGS // Define GLOG_DEFINE_* using DEFINE_* . By using these macros, we diff --git a/src/base/mutex.h b/src/base/mutex.h index e82c597f..a58c1412 100644 --- a/src/base/mutex.h +++ b/src/base/mutex.h @@ -319,11 +319,6 @@ class WriterMutexLock { void operator=(const WriterMutexLock&); }; -// Catch bug where variable name is omitted, e.g. MutexLock (&mu); -#define MutexLock(x) COMPILE_ASSERT(0, mutex_lock_decl_missing_var_name) -#define ReaderMutexLock(x) COMPILE_ASSERT(0, rmutex_lock_decl_missing_var_name) -#define WriterMutexLock(x) COMPILE_ASSERT(0, wmutex_lock_decl_missing_var_name) - }  // namespace MUTEX_NAMESPACE using namespace MUTEX_NAMESPACE; diff --git a/src/config.h.cmake.in b/src/config.h.cmake.in index b225b7ec..a4c58c96 100644 --- a/src/config.h.cmake.in +++ b/src/config.h.cmake.in @@ -34,6 +34,8 @@ /* define if you have google gflags library */ #cmakedefine HAVE_LIB_GFLAGS +#cmakedefine HAVE_ABSL_FLAGS + /* define if you have google gmock library */ #cmakedefine HAVE_LIB_GMOCK diff --git a/src/glog/logging.h.in b/src/glog/logging.h.in index 95a573b1..54cd838f 100644 --- a/src/glog/logging.h.in +++ b/src/glog/logging.h.in @@ -89,6 +89,10 @@ #include <gflags/gflags.h> #endif +#if @ac_cv_have_abslflags@ +#include <absl/flags/declare.h> +#endif + #if @ac_cv_cxx11_atomic@ && __cplusplus >= 201103L #include <atomic> #elif defined(GLOG_OS_WINDOWS) @@ -395,6 +399,14 @@ typedef void(*CustomPrefixCallback)(std::ostream& s, const LogMessageInfo& l, vo #undef DECLARE_uint32 #endif +#if @ac_cv_have_abslflags@ +#define DECLARE_VARIABLE 1 +#define DECLARE_bool(name) ABSL_DECLARE_FLAG(bool, name) +#define DECLARE_int32(name) ABSL_DECLARE_FLAG(@ac_google_namespace@::int32, name) +#define DECLARE_uint32(name) ABSL_DECLARE_FLAG(@ac_google_namespace@::uint32, name) +#define DECLARE_string(name) ABSL_DECLARE_FLAG(std::string, name) +#endif + #ifndef DECLARE_VARIABLE #define DECLARE_VARIABLE(type, shorttype, name, tn)                      namespace fL##shorttype {                                              diff --git a/src/glog/vlog_is_on.h.in b/src/glog/vlog_is_on.h.in index 7526fc34..16e60f46 100644 --- a/src/glog/vlog_is_on.h.in +++ b/src/glog/vlog_is_on.h.in @@ -64,6 +64,14 @@ #include <glog/log_severity.h> #if defined(__GNUC__) + +#if @ac_cv_have_abslflags@ +  extern int32_t absl_proxy_v; +  #define VLEVEL (@ac_google_namespace@::absl_proxy_v) +#else +  #define VLEVEL (FLAGS_v) +#endif + // We emit an anonymous static int* variable at every VLOG_IS_ON(n) site. // (Normally) the first time every VLOG_IS_ON(n) site is hit, // we determine what variable will dynamically control logging at this site: @@ -74,7 +82,7 @@ __extension__   ({ static @ac_google_namespace@::SiteFlag vlocal__ = {NULL, NULL, 0, NULL};        @ac_google_namespace@::int32 verbose_level__ = (verboselevel);                     -     (vlocal__.level == NULL ? @ac_google_namespace@::InitVLOG3__(&vlocal__, &FLAGS_v,  +     (vlocal__.level == NULL ? @ac_google_namespace@::InitVLOG3__(&vlocal__, &VLEVEL,  __FILE__, verbose_level__) : *vlocal__.level >= verbose_level__);  }) #else diff --git a/src/logging.cc b/src/logging.cc index 4028ccc0..fc618d3a 100644 --- a/src/logging.cc +++ b/src/logging.cc @@ -103,7 +103,9 @@ using std::fdopen; #endif // There is no thread annotation support. +#ifndef EXCLUSIVE_LOCKS_REQUIRED #define EXCLUSIVE_LOCKS_REQUIRED(mu) +#endif static bool BoolFromEnv(const char *varname, bool defval) { const char* const valstr = getenv(varname); @@ -351,8 +353,9 @@ static const char* GetAnsiColorCode(GLogColor color) { // Safely get max_log_size, overriding to 1 if it somehow gets defined as 0 static uint32 MaxLogSize() { -  return (FLAGS_max_log_size > 0 && FLAGS_max_log_size < 4096 -              ? FLAGS_max_log_size +  uint32 maxlogsize = FLAG(max_log_size); +  return (maxlogsize > 0 && maxlogsize < 4096 +              ? maxlogsize : 1); } @@ -721,7 +724,7 @@ inline void LogDestination::SetStderrLogging(LogSeverity min_severity) { // Prevent any subtle race conditions by wrapping a mutex lock around // all this stuff. MutexLock l(&log_mutex); -  FLAGS_stderrthreshold = min_severity; +  absl::SetFlag(&FLAGS_stderrthreshold, min_severity); } inline void LogDestination::LogToStderr() { @@ -747,8 +750,8 @@ static void ColoredWriteToStderrOrStdout(FILE* output, LogSeverity severity, const char* message, size_t len) { bool is_stdout = (output == stdout); const GLogColor color = (LogDestination::terminal_supports_color() && -                           ((!is_stdout && FLAGS_colorlogtostderr) || -                            (is_stdout && FLAGS_colorlogtostdout))) +                           ((!is_stdout && FLAG(colorlogtostderr)) || +                            (is_stdout && FLAG(colorlogtostdout)))) ? SeverityToColor(severity) : COLOR_DEFAULT; @@ -789,7 +792,7 @@ static void ColoredWriteToStdout(LogSeverity severity, const char* message, FILE* output = stdout; // We also need to send logs to the stderr when the severity is // higher or equal to the stderr threshold. -  if (severity >= FLAGS_stderrthreshold) { +  if (severity >= FLAG(stderrthreshold)) { output = stderr; } ColoredWriteToStderrOrStdout(output, severity, message, len); @@ -808,7 +811,7 @@ static void WriteToStderr(const char* message, size_t len) { inline void LogDestination::MaybeLogToStderr(LogSeverity severity, const char* message, size_t message_len, size_t prefix_len) { -  if ((severity >= FLAGS_stderrthreshold) || FLAGS_alsologtostderr) { +  if ((severity >= FLAG(stderrthreshold)) || FLAG(alsologtostderr)) { ColoredWriteToStderr(severity, message, message_len); #ifdef GLOG_OS_WINDOWS (void) prefix_len; @@ -835,8 +838,8 @@ inline void LogDestination::MaybeLogToStderr(LogSeverity severity, inline void LogDestination::MaybeLogToEmail(LogSeverity severity, const char* message, size_t len) { if (severity >= email_logging_severity_ || -      severity >= FLAGS_logemaillevel) { -    string to(FLAGS_alsologtoemail); +      severity >= FLAG(logemaillevel)) { +    string to(FLAG(alsologtoemail)); if (!addresses_.empty()) { if (!to.empty()) { to += ","; @@ -862,7 +865,7 @@ inline void LogDestination::MaybeLogToLogfile(LogSeverity severity, time_t timestamp, const char* message, size_t len) { -  const bool should_flush = severity > FLAGS_logbuflevel; +  const bool should_flush = severity > FLAG(logbuflevel); LogDestination* destination = log_destination(severity); destination->logger_->Write(should_flush, timestamp, message, len); } @@ -871,9 +874,9 @@ inline void LogDestination::LogToAllLogfiles(LogSeverity severity, time_t timestamp, const char* message, size_t len) { -  if (FLAGS_logtostdout) {  // global flag: never log to file +  if (FLAG(logtostdout)) {  // global flag: never log to file ColoredWriteToStdout(severity, message, len); -  } else if (FLAGS_logtostderr) {  // global flag: never log to file +  } else if (FLAG(logtostderr)) {  // global flag: never log to file ColoredWriteToStderr(severity, message, len); } else { for (int i = severity; i >= 0; --i) { @@ -1032,25 +1035,25 @@ void LogFileObject::FlushUnlocked(){ bytes_since_flush_ = 0; } // Figure out when we are due for another flush. -  const int64 next = (FLAGS_logbufsecs +  const int64 next = (FLAG(logbufsecs) * static_cast<int64>(1000000));  // in usec next_flush_time_ = CycleClock_Now() + UsecToCycles(next); } bool LogFileObject::CreateLogfile(const string& time_pid_string) { string string_filename = base_filename_; -  if (FLAGS_timestamp_in_logfile_name) { +  if (FLAG(timestamp_in_logfile_name)) { string_filename += time_pid_string; } string_filename += filename_extension_; const char* filename = string_filename.c_str(); //only write to files, create if non-existant. int flags = O_WRONLY | O_CREAT; -  if (FLAGS_timestamp_in_logfile_name) { +  if (FLAG(timestamp_in_logfile_name)) { //demand that the file is unique for our timestamp (fail if it exists). flags = flags | O_EXCL; } -  int fd = open(filename, flags, FLAGS_logfile_mode); +  int fd = open(filename, flags, FLAG(logfile_mode)); if (fd == -1) return false; #ifdef HAVE_FCNTL // Mark the file close-on-exec. We don't really care if this fails @@ -1083,7 +1086,7 @@ bool LogFileObject::CreateLogfile(const string& time_pid_string) { file_ = fdopen(fd, "a");  // Make a FILE*. if (file_ == NULL) {  // Man, we're screwed! close(fd); -    if (FLAGS_timestamp_in_logfile_name) { +    if (FLAG(timestamp_in_logfile_name)) { unlink(filename);  // Erase the half-baked evidence: an unusable log file, only if we just created it. } return false; @@ -1125,8 +1128,8 @@ bool LogFileObject::CreateLogfile(const string& time_pid_string) { // Make an additional link to the log file in a place specified by // FLAGS_log_link, if indicated -    if (!FLAGS_log_link.empty()) { -      linkpath = FLAGS_log_link + "/" + linkname; +    if (!FLAG(log_link).empty()) { +      linkpath = FLAG(log_link) + "/" + linkname; unlink(linkpath.c_str());                  // delete old one if it exists if (symlink(filename, linkpath.c_str()) != 0) { // silently ignore failures @@ -1165,7 +1168,7 @@ void LogFileObject::Write(bool force_flush, rollover_attempt_ = 0; struct ::tm tm_time; -    if (FLAGS_log_utc_time) { +    if (FLAG(log_utc_time)) { gmtime_r(&timestamp, &tm_time); } else { localtime_r(&timestamp, &tm_time); @@ -1253,14 +1256,14 @@ void LogFileObject::Write(bool force_flush, << ' ' << setw(2) << tm_time.tm_hour << ':' << setw(2) << tm_time.tm_min << ':' -                       << setw(2) << tm_time.tm_sec << (FLAGS_log_utc_time ? " UTCn" : "n") +                       << setw(2) << tm_time.tm_sec << (FLAG(log_utc_time) ? " UTCn" : "n") << "Running on machine: " << LogDestination::hostname() << 'n'; if(!g_application_fingerprint.empty()) { file_header_stream << "Application fingerprint: " << g_application_fingerprint << 'n'; } -    const char* const date_time_format = FLAGS_log_year_in_prefix +    const char* const date_time_format = FLAG(log_year_in_prefix) ? "yyyymmdd hh:mm:ss.uuuuuu" : "mmdd hh:mm:ss.uuuuuu"; file_header_stream << "Running duration (h:mm:ss): " @@ -1284,7 +1287,7 @@ void LogFileObject::Write(bool force_flush, // greater than 4096, thereby indicating an error. errno = 0; fwrite(message, 1, message_len, file_); -    if ( FLAGS_stop_logging_if_full_disk && +    if ( FLAG(stop_logging_if_full_disk) && errno == ENOSPC ) {  // disk full, stop writing to disk stop_writing = true;  // until the disk is return; @@ -1307,7 +1310,7 @@ void LogFileObject::Write(bool force_flush, FlushUnlocked(); #ifdef GLOG_OS_LINUX // Only consider files >= 3MiB -    if (FLAGS_drop_log_memory && file_length_ >= (3U << 20U)) { +    if (FLAG(drop_log_memory) && file_length_ >= (3U << 20U)) { // Don't evict the most recent 1-2MiB so as not to impact a tailer // of the log file and to avoid page rounding issue on linux < 4.7 uint32 total_drop_length = @@ -1348,7 +1351,7 @@ void LogCleaner::Disable() { } void LogCleaner::UpdateCleanUpTime() { -  const int64 next = (FLAGS_logcleansecs +  const int64 next = (FLAG(logcleansecs) * 1000000);  // in usec next_cleanup_time_ = CycleClock_Now() + UsecToCycles(next); } @@ -1664,7 +1667,7 @@ void LogMessage::Init(const char* file, //    I20201018 160715 f5d4fbb0 logging.cc:1153] //    (log level, GMT year, month, date, time, thread_id, file basename, line) // We exclude the thread_id for the default thread. -  if (FLAGS_log_prefix && (line != kNoLogPrefix)) { +  if (FLAG(log_prefix) && (line != kNoLogPrefix)) { std::ios saved_fmt(NULL); saved_fmt.copyfmt(stream()); stream().fill('0'); @@ -1672,7 +1675,7 @@ void LogMessage::Init(const char* file, if (custom_prefix_callback == NULL) { #endif stream() << LogSeverityNames[severity][0]; -          if (FLAGS_log_year_in_prefix) { +          if (FLAG(log_year_in_prefix)) { stream() << setw(4) << 1900 + logmsgtime_.year(); } stream() << setw(2) << 1 + logmsgtime_.month() @@ -1703,11 +1706,11 @@ void LogMessage::Init(const char* file, } data_->num_prefix_chars_ = data_->stream_.pcount(); -  if (!FLAGS_log_backtrace_at.empty()) { +  if (!FLAG(log_backtrace_at).empty()) { char fileline[128]; snprintf(fileline, sizeof(fileline), "%s:%d", data_->basename_, line); #ifdef HAVE_STACKTRACE -    if (FLAGS_log_backtrace_at == fileline) { +    if (FLAG(log_backtrace_at) == fileline) { string stacktrace; DumpStackTraceToString(&stacktrace); stream() << " (stacktrace:n" << stacktrace << ") "; @@ -1746,7 +1749,7 @@ ostream& LogMessage::stream() { // Flush buffered message, called by the destructor, or any other function // that needs to synchronize the log. void LogMessage::Flush() { -  if (data_->has_been_flushed_ || data_->severity_ < FLAGS_minloglevel) { +  if (data_->has_been_flushed_ || data_->severity_ < FLAG(minloglevel)) { return; } @@ -1808,7 +1811,7 @@ static char fatal_message[256]; void ReprintFatalMessage() { if (fatal_message[0]) { const size_t n = strlen(fatal_message); -    if (!FLAGS_logtostderr) { +    if (!FLAG(logtostderr)) { // Also write to stderr (don't color to avoid terminal checks) WriteToStderr(fatal_message, n); } @@ -1837,8 +1840,8 @@ void LogMessage::SendToLog() EXCLUSIVE_LOCKS_REQUIRED(log_mutex) { // global flag: never log to file if set.  Also -- don't log to a // file if we haven't parsed the command line flags to get the // program name. -  if (FLAGS_logtostderr || FLAGS_logtostdout || !IsGoogleLoggingInitialized()) { -    if (FLAGS_logtostdout) { +  if (FLAG(logtostderr) || FLAG(logtostdout) || !IsGoogleLoggingInitialized()) { +    if (FLAG(logtostdout)) { ColoredWriteToStdout(data_->severity_, data_->message_text_, data_->num_chars_to_log_); } else { @@ -1891,7 +1894,7 @@ void LogMessage::SendToLog() EXCLUSIVE_LOCKS_REQUIRED(log_mutex) { fatal_time = logmsgtime_.timestamp(); } -    if (!FLAGS_logtostderr && !FLAGS_logtostdout) { +    if (!FLAG(logtostderr) && !FLAG(logtostdout)) { for (int i = 0; i < NUM_SEVERITIES; ++i) { if (LogDestination::log_destinations_[i]) { LogDestination::log_destinations_[i]->logger_->Write(true, 0, "", 0); @@ -2238,7 +2241,7 @@ static bool SendEmailInternal(const char*dest, const char *subject, subject, body, dest); } -    string logmailer = FLAGS_logmailer; +    string logmailer = FLAG(logmailer); if (logmailer.empty()) { logmailer = "/bin/mail"; } @@ -2338,9 +2341,9 @@ const vector<string>& GetLoggingDirectories() { if (logging_directories_list == NULL) { logging_directories_list = new vector<string>; -    if ( !FLAGS_log_dir.empty() ) { +    if ( !FLAG(log_dir).empty() ) { // A dir was specified, we should use it -      logging_directories_list->push_back(FLAGS_log_dir); +      logging_directories_list->push_back(FLAG(log_dir)); } else { GetTempDirectories(logging_directories_list); #ifdef GLOG_OS_WINDOWS @@ -2654,7 +2657,7 @@ LogMessageTime::LogMessageTime(std::tm t) { LogMessageTime::LogMessageTime(std::time_t timestamp, WallTime now) { std::tm t; -  if (FLAGS_log_utc_time) +  if (FLAG(log_utc_time)) gmtime_r(&timestamp, &t); else localtime_r(&timestamp, &t); @@ -2673,7 +2676,7 @@ void LogMessageTime::init(const std::tm& t, std::time_t timestamp, void LogMessageTime::CalcGmtOffset() { std::tm gmt_struct; int isDst = 0; -  if ( FLAGS_log_utc_time ) { +  if ( FLAG(log_utc_time )) { localtime_r(&timestamp_, &gmt_struct); isDst = gmt_struct.tm_isdst; gmt_struct = time_struct_; diff --git a/src/raw_logging.cc b/src/raw_logging.cc index 43159832..8532362b 100644 --- a/src/raw_logging.cc +++ b/src/raw_logging.cc @@ -123,8 +123,8 @@ static char crash_buf[kLogBufSize + 1] = { 0 };  // Will end in '0' GLOG_ATTRIBUTE_FORMAT(printf, 4, 5) void RawLog__(LogSeverity severity, const char* file, int line, const char* format, ...) { -  if (!(FLAGS_logtostdout || FLAGS_logtostderr || -        severity >= FLAGS_stderrthreshold || FLAGS_alsologtostderr || +  if (!(FLAG(logtostdout) || FLAG(logtostderr) || +        severity >= FLAG(stderrthreshold) || FLAG(alsologtostderr) || !IsGoogleLoggingInitialized())) { return;  // this stderr log message is suppressed } diff --git a/src/utilities.cc b/src/utilities.cc index a332f1a1..a9d5102a 100644 --- a/src/utilities.cc +++ b/src/utilities.cc @@ -141,7 +141,7 @@ static void DumpStackTrace(int skip_count, DebugWriter *writerfn, void *arg) { int depth = GetStackTrace(stack, ARRAYSIZE(stack), skip_count+1); for (int i = 0; i < depth; i++) { #if defined(HAVE_SYMBOLIZE) -    if (FLAGS_symbolize_stacktrace) { +    if (FLAG(symbolize_stacktrace)) { DumpPCAndSymbol(writerfn, arg, stack[i], "    "); } else { DumpPC(writerfn, arg, stack[i], "    "); diff --git a/src/vlog_is_on.cc b/src/vlog_is_on.cc index e478a366..4b7a5cae 100644 --- a/src/vlog_is_on.cc +++ b/src/vlog_is_on.cc @@ -43,14 +43,24 @@ #include <glog/logging.h> #include <glog/raw_logging.h> #include "base/googleinit.h" +#include "config.h" // glog doesn't have annotation #define ANNOTATE_BENIGN_RACE(address, description) using std::string; +#ifdef HAVE_ABSL_FLAGS + +ABSL_FLAG(int32_t, v, 0, "Show all VLOG(m) messages for m <= this." +" Overridable by --vmodule.").OnUpdate([] { +      GOOGLE_NAMESPACE::absl_proxy_v = absl::GetFlag(FLAGS_v); +    }); + +#else GLOG_DEFINE_int32(v, 0, "Show all VLOG(m) messages for m <= this." " Overridable by --vmodule."); +#endif GLOG_DEFINE_string(vmodule, "", "per-module verbose level." " Argument is a comma-separated list of <module name>=<log level>." @@ -60,6 +70,8 @@ GLOG_DEFINE_string(vmodule, "", "per-module verbose level." _START_GOOGLE_NAMESPACE_ +int32_t absl_proxy_v = 0; + namespace glog_internal_namespace_ { // Used by logging_unittests.cc so can't make it static here. @@ -132,7 +144,8 @@ static void VLOG2Initializer() { // Can now parse --vmodule flag and initialize mapping of module-specific // logging levels. inited_vmodule = false; -  const char* vmodule = FLAGS_vmodule.c_str(); +  string vmodule_str = FLAG(vmodule); +  const char* vmodule = vmodule_str.c_str(); const char* sep; VModuleInfo* head = NULL; VModuleInfo* tail = NULL; @@ -164,7 +177,7 @@ static void VLOG2Initializer() { // This can be called very early, so we use SpinLock and RAW_VLOG here. int SetVLOGLevel(const char* module_pattern, int log_level) { -  int result = FLAGS_v; +  int result = FLAG(v); size_t const pattern_len = strlen(module_pattern); bool found = false; { </ins>


Question:
Project description Metadata homepage URL: source URL: license: Business Source License 1.1, change to Apache License 2.0 on June 1st 2027 platforms: linux
Can you check out my PR if everything works?

dr14_tmeter = callPackage ../applications/audio/dr14_tmeter { }; <ins> dragonflydb = callPackage ../servers/nosql/dragonflydb { }; </ins> dragonfly-reverb = callPackage ../applications/audio/dragonfly-reverb { }; drawing = callPackage ../applications/graphics/drawing { };


Question:
As of nixos/nixpkgs (i.e., today) seems to be failing due to an unsupported command line switch being passed (see ) Actually, starting doesn't fail, but some (all?) of the other command line arguments are ignored. For example, I tried setting , but see how insists on starting on port . Removing the switch makes start as expected, respecting the other given command line switches, but is this what we want to do? cc
this was broken due to Catalyst bump. See duplicated - I don't know how to best fix this as switch might have an impact. If someone has time to fix it, I'd be very happy :)

<ins> diff --git a/lib/CatalystX/Script/Server/Starman.pm b/lib/CatalystX/Script/Server/Starman.pm index 670bd74..7b3bd2e 100644 --- a/lib/CatalystX/Script/Server/Starman.pm +++ b/lib/CatalystX/Script/Server/Starman.pm @@ -9,7 +9,7 @@ our $VERSION = '0.02'; extends 'Catalyst::Script::Server'; -has '+fork' => ( default => 1, init_arg => undef ); +has '+fork' => ( default => 1 ); has [qw/ keepalive restart restart_delay restart_regex restart_directory/] => ( init_arg => undef, is => 'ro' ); @@ -70,7 +70,7 @@ CatalystX::Script::Server::Starman - Replace the development server with Starman -d --debug           force debug mode -f --fork            handle each request in a new process -                            (defaults to false) +                            (defaults to true) -? --help            display this help and exits -h --host            host (defaults to all) -p --port            port (defaults to 3000) </ins>


Question:
As of nixos/nixpkgs (i.e., today) seems to be failing due to an unsupported command line switch being passed (see ) Actually, starting doesn't fail, but some (all?) of the other command line arguments are ignored. For example, I tried setting , but see how insists on starting on port . Removing the switch makes start as expected, respecting the other given command line switches, but is this what we want to do? cc
this was broken due to Catalyst bump. See duplicated - I don't know how to best fix this as switch might have an impact. If someone has time to fix it, I'd be very happy :)

url = mirror://cpan/authors/id/A/AB/ABRAXXA/CatalystX-Script-Server-Starman-0.02.tar.gz; sha256 = "0h02mpkc4cmi3jpvcd7iw7xyzx55bqvvl1qkf967gqkvpklm0qx5"; }; <ins> patches = [ # See Nixpkgs issues #16074 and #17624 ../development/perl-modules/CatalystXScriptServerStarman-fork-arg.patch ]; </ins> buildInputs = [ TestWWWMechanizeCatalyst ]; propagatedBuildInputs = [ CatalystRuntime Moose namespaceautoclean Starman ]; meta = {


Question:
The systemd-boot image built in nixpkgs has gaps in the section table. This leads to signature verification failure with some UEFI Secure Boot implementations (e.g. Dell XPS 13 9310) Using NixOS 22.05 @ Using some old version from NixOS 21.11 that I still have in the store: N/A Allegedly something like this was fixed in systemd upstream and the commit is present in v250.4 but for some reason it still appears and Secure Boot fails. <!-- 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. system: host os: multi-user?: sandbox: version: nixpkgs:
Relevant:
This commit might be the culprit: I will try confirm this, but since it requires rebuilding systemd, it'll take a while.
It's more likely a problem of sbsigntools:
Does your hardware still correctly validate the signature with this patch applied?
Yes, signature verification works with this patch (and only with this patch). Hardware is Dell XPS 13 9310. See also

<del> --- sbsigntools/configure.ac	2018-09-25 10:30:00.878766256 -0500 +++ configure.ac.new	2018-09-25 10:34:56.231277375 -0500 @@ -71,15 +71,16 @@ </del> <ins> diff --git a/configure.ac b/configure.ac index 4ffb68f..d8a8265 100644 --- a/configure.ac +++ b/configure.ac @@ -71,15 +71,16 @@ AM_CONDITIONAL(TEST_BINARY_FORMAT, [ test "$EFI_ARCH" = "arm" -o "$EFI_ARCH" = " </ins> # no consistent view of where gnu-efi should dump the efi stuff, so find it ## <del> for path in /lib /lib64 /usr/lib /usr/lib64 /usr/lib32 /lib/efi /lib64/efi /usr/lib/efi /usr/lib64/efi; do </del> <ins> for path in /lib /lib64 /usr/lib /usr/lib64 /usr/lib32 /lib/efi /lib64/efi /usr/lib/efi /usr/lib64/efi /usr/lib/gnuefi /usr/lib64/gnuefi ; do </ins> -    if test -e $path/crt0-efi-$EFI_ARCH.o; then -       CRTPATH=$path +    if test -e @@NIX_GNUEFI@@/$path/crt0-efi-$EFI_ARCH.o; then


Question:
The systemd-boot image built in nixpkgs has gaps in the section table. This leads to signature verification failure with some UEFI Secure Boot implementations (e.g. Dell XPS 13 9310) Using NixOS 22.05 @ Using some old version from NixOS 21.11 that I still have in the store: N/A Allegedly something like this was fixed in systemd upstream and the commit is present in v250.4 but for some reason it still appears and Secure Boot fails. <!-- 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. system: host os: multi-user?: sandbox: version: nixpkgs:
Relevant:
This commit might be the culprit: I will try confirm this, but since it requires rebuilding systemd, it'll take a while.
It's more likely a problem of sbsigntools:
Does your hardware still correctly validate the signature with this patch applied?
Yes, signature verification works with this patch (and only with this patch). Hardware is Dell XPS 13 9310. See also

-DEFI_FUNCTION_WRAPPER" CPPFLAGS_save="$CPPFLAGS" CPPFLAGS="$CPPFLAGS $EFI_CPPFLAGS" <del> @@ -90,5 +91,5 @@ </del> <ins> @@ -90,5 +91,5 @@ AC_SUBST(EFI_ARCH, $EFI_ARCH) </ins> AC_SUBST(CRTPATH, $CRTPATH) AC_CONFIG_FILES([Makefile src/Makefile lib/ccan/Makefile]


Question:
The systemd-boot image built in nixpkgs has gaps in the section table. This leads to signature verification failure with some UEFI Secure Boot implementations (e.g. Dell XPS 13 9310) Using NixOS 22.05 @ Using some old version from NixOS 21.11 that I still have in the store: N/A Allegedly something like this was fixed in systemd upstream and the commit is present in v250.4 but for some reason it still appears and Secure Boot fails. <!-- 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. system: host os: multi-user?: sandbox: version: nixpkgs:
Relevant:
This commit might be the culprit: I will try confirm this, but since it requires rebuilding systemd, it'll take a while.
It's more likely a problem of sbsigntools:
Does your hardware still correctly validate the signature with this patch applied?
Yes, signature verification works with this patch (and only with this patch). Hardware is Dell XPS 13 9310. See also

, openssl, libuuid, gnu-efi, libbfd }: <del> stdenv.mkDerivation { </del> <ins> stdenv.mkDerivation rec { </ins> pname = "sbsigntool"; <del> version = "0.9.1"; </del> <ins> version = "0.9.4"; </ins> src = fetchgit { url = "https://git.kernel.org/pub/scm/linux/kernel/git/jejb/sbsigntools.git"; <del> rev = "v0.9.1"; sha256 = "098gxmhjn8acxjw5bq59wq4xhgkpx1xn8kjvxwdzpqkwq9ivrsbp"; </del> <ins> rev = "v${version}"; sha256 = "sha256-dbjdA+hjII/k7wABTTJV5RBdy4KlNkFlBWEaX4zn5vg="; </ins> }; patches = [ ./autoconf.patch ];


Question:
The systemd-boot image built in nixpkgs has gaps in the section table. This leads to signature verification failure with some UEFI Secure Boot implementations (e.g. Dell XPS 13 9310) Using NixOS 22.05 @ Using some old version from NixOS 21.11 that I still have in the store: N/A Allegedly something like this was fixed in systemd upstream and the commit is present in v250.4 but for some reason it still appears and Secure Boot fails. <!-- 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. system: host os: multi-user?: sandbox: version: nixpkgs:
Relevant:
This commit might be the culprit: I will try confirm this, but since it requires rebuilding systemd, it'll take a while.
It's more likely a problem of sbsigntools:
Does your hardware still correctly validate the signature with this patch applied?
Yes, signature verification works with this patch (and only with this patch). Hardware is Dell XPS 13 9310. See also

meta = with lib; { description = "Tools for maintaining UEFI signature databases"; homepage    = "http://jk.ozlabs.org/docs/sbkeysync-maintaing-uefi-key-databases"; <del> maintainers = [ maintainers.tstrobel ]; </del> <ins> maintainers = with maintainers; [ hmenke tstrobel ]; </ins> platforms   = [ "x86_64-linux" ]; # Broken on i686 license     = licenses.gpl3; };


Question: Project description describe the project a little is a highly configurable dashboard for Neovim. It's an alternative to Metadata homepage URL: source URL: license: MIT platforms: Anything that can run Neovim, I would assume

meta.homepage = "https://github.com/vim-scripts/align/"; }; <ins> alpha-nvim = buildVimPluginFrom2Nix { pname = "alpha-nvim"; version = "2022-04-22"; src = fetchFromGitHub { owner = "goolord"; repo = "alpha-nvim"; rev = "4781fcfea5ddc1a92d41b32dc325132ed6fce7a8"; sha256 = "03i75403lskpgaqv7xp5hk4v6kqb0sv15ciil9jyj735ylhry3qq"; }; meta.homepage = "https://github.com/goolord/alpha-nvim/"; }; </ins> aniseed = buildVimPluginFrom2Nix { pname = "aniseed"; version = "2022-05-14";


Question: Project description describe the project a little is a highly configurable dashboard for Neovim. It's an alternative to Metadata homepage URL: source URL: license: MIT platforms: Anything that can run Neovim, I would assume

https://github.com/slashmili/alchemist.vim/,, https://github.com/dense-analysis/ale/,, https://github.com/vim-scripts/align/,, <ins> https://github.com/goolord/alpha-nvim/,HEAD, </ins> https://github.com/Olical/aniseed/,, https://github.com/pearofducks/ansible-vim/,, https://github.com/ckarnell/antonys-macro-repeater/,,