Question: <ins> { lib, alsa-lib, callPackage, cmake, ffmpeg, fribidi, game-music-emu, libXdmcp, libXv, libass, libcddb, libcdio, libpulseaudio, libsidplayfp, libva, libxcb, ninja, pkg-config, qt5, qt6, stdenv, taglib, vulkan-headers, vulkan-tools, # Configurable options qtVersion ? "6", # Can be 5 or 6 }: let sources = callPackage ./sources.nix { }; in assert lib.elem qtVersion [ "5" "6" ]; stdenv.mkDerivation (finalAttrs: { pname = sources.qmplay2.pname + "-qt" + qtVersion; inherit (sources.qmplay2) version src; postPatch = '' pushd src cp -va ${sources.qmvk.src}/* qmvk/ chmod --recursive 744 qmvk popd ''; nativeBuildInputs = [ cmake ninja pkg-config ] ++ lib.optionals (qtVersion == "6") [ qt6.wrapQtAppsHook ] ++ lib.optionals (qtVersion == "5") [ qt5.wrapQtAppsHook ]; buildInputs = [ alsa-lib ffmpeg fribidi game-music-emu libXdmcp libXv libass libcddb libcdio libpulseaudio libsidplayfp libva libxcb taglib vulkan-headers vulkan-tools ] ++ lib.optionals (qtVersion == "6") [ qt6.qt5compat qt6.qtbase qt6.qtsvg qt6.qttools ] ++ lib.optionals (qtVersion == "5") [ qt5.qtbase qt5.qttools ]; strictDeps = true; # Because we think it is better to use only lowercase letters! # But sometimes we come across case-insensitive filesystems... postInstall = '' [ -e $out/bin/qmplay2 ] || ln -s $out/bin/QMPlay2 $out/bin/qmplay2 ''; passthru = { inherit sources; }; meta = { homepage = "https://github.com/zaps166/QMPlay2/"; description = "Qt-based Multimedia player"; longDescription = '' QMPlay2 is a video and audio player. It can play all formats supported by FFmpeg and libmodplug (including J2B and SFX). It also supports Audio CD, raw files, Rayman 2 music, and chiptunes. It also contains YouTube and MyFreeMP3 browser. ''; license = lib.licenses.lgpl3Plus; mainProgram = "qmplay2"; maintainers = with lib.maintainers; [ AndersonTorres kashw2 ]; platforms = lib.platforms.linux; }; }) </ins>

Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.


Question: installPhase = '' runHook preInstall <del> # TODO: Remove when the next stable Itch is stabilized substituteInPlace ./resources/app/package.json  --replace "kitch" "itch" </del> mkdir -p $out/bin $out/share/itch/resources/app cp -r resources/app "$out/share/itch/resources/" install -Dm644 LICENSE -t "$out/share/licenses/$pkgname/" install -Dm644 LICENSES.chromium.html -t "$out/share/licenses/$pkgname/" <del> for icon in $icons/icon*.png </del> <ins> for icon in ${icons}/icon*.png </ins> do <del> iconsize="''${icon#$icons/icon}" </del> <ins> iconsize="''${icon#${icons}/icon}" </ins> iconsize="''${iconsize%.png}" icondir="$out/share/icons/hicolor/''${iconsize}x''${iconsize}/apps/" install -Dm644 "$icon" "$icondir/itch.png"

Package name: itch Latest released version: 26.1.3 Current version on the unstable channel: 26.1.3 Current version on the stable/release channel: 26.1.3 <!-- 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! --- The current version is broken since butler is marked broken Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The latest version on seems to be 26.1.3 which is used in the package.
There is 26.1.5 as a source code , but current package uses binaryBytecode


Question: qpageview = callPackage ../development/python-modules/qpageview { }; <ins> qpsolvers = callPackage ../development/python-modules/qpsolvers { }; </ins> qrcode = callPackage ../development/python-modules/qrcode { }; qreactor = callPackage ../development/python-modules/qreactor { };

Project description qpsolvers is python library for solving quadratic programming problems. It contains wrappers for multiple solvers like osqp, cvxopt, quadprog and much more. Metadata homepage URL: source URL: license: LGPLv3 platforms: platform independent (python3.10)
This package wants new version of and new package - . I will try add PR today, but now you can use my NUR repo if you want:


Question: }; nativeBuildInputs = [ <ins> # uname output embedded in https://gitlab.gnome.org/GNOME/libgtop/-/blob/master/src/daemon/Makefile.am deterministic-uname </ins> pkg-config gtk-doc perl

libgtop is not reproducible, since it embed the output of into one of its binaries. See or build on 2 machines with different kernel versions. Report attached since r13y will not keep it, I think: libgtop build should be reproducible. This patch works from a nixpkgs perspective: However, it should ideally be reported and fixed upstream. N/A Maintainer information:
I marked this as stale due to inactivity. →


Question: <ins> { lib, flutter324, fetchFromGitHub, webkitgtk, sqlite, libayatana-appindicator, makeDesktopItem, copyDesktopItems, imagemagick, makeWrapper, xdg-user-dirs, }: let # fetch simple-icons directly to avoid cloning with submodules, # which would also clone a whole copy of flutter simple-icons = fetchFromGitHub (lib.importJSON ./simple-icons.json); in flutter324.buildFlutterApplication rec { pname = "ente-auth"; version = "4.0.2"; src = fetchFromGitHub { owner = "ente-io"; repo = "ente"; sparseCheckout = [ "auth" ]; rev = "auth-v${version}"; hash = "sha256-me+fT79vwqBBNsRWWo58GdzBf58LNB4Mk+pmCLvn/ik="; }; sourceRoot = "${src.name}/auth"; pubspecLock = lib.importJSON ./pubspec.lock.json; patchPhase = '' rmdir assets/simple-icons ln -s ${simple-icons} assets/simple-icons ''; gitHashes = { desktop_webview_window = "sha256-jdNMpzFBgw53asWlGzWUS+hoPdzcL6kcJt2KzjxXf2E="; ente_crypto_dart = "sha256-XBzQ268E0cYljJH6gDS5O0Pmie/GwuhMDlQPfopSqJM="; flutter_local_authentication = "sha256-r50jr+81ho+7q2PWHLf4VnvNJmhiARZ3s4HUpThCgc0="; flutter_secure_storage_linux = "sha256-x45jrJ7pvVyhZlpqRSy3CbwT4Lna6yi/b2IyAilWckg="; sqflite = "sha256-TdvCtEO7KL1R2oOSwGWllmS5kGCIU5CkvvUqUJf3tUc="; }; nativeBuildInputs = [ copyDesktopItems imagemagick makeWrapper ]; buildInputs = [ webkitgtk sqlite libayatana-appindicator ]; # Based on https://github.com/ente-io/ente/blob/main/auth/linux/packaging/rpm/make_config.yaml # and https://github.com/ente-io/ente/blob/main/auth/linux/packaging/ente_auth.appdata.xml desktopItems = makeDesktopItem { name = "ente_auth"; exec = "ente_auth"; icon = "ente-auth"; desktopName = "Ente Auth"; genericName = "Ente Authentication"; comment = "Open source 2FA authenticator, with end-to-end encrypted backups"; categories = [ "Utility" ]; keywords = [ "Authentication" "2FA" ]; mimeTypes = [ "x-scheme-handler/enteauth" ]; startupNotify = false; }; postInstall = '' FAV=$out/app/data/flutter_assets/assets/icons/auth-icon.png ICO=$out/share/icons install -D $FAV $ICO/ente-auth.png for size in 24 32 42 64 128 256 512; do D=$ICO/hicolor/''${size}x''${size}/apps mkdir -p $D magick $FAV -resize ''${size}x''${size} $D/ente-auth.png done install -Dm444 linux/packaging/ente_auth.appdata.xml -t $out/share/metainfo wrapProgram $out/bin/ente_auth  --prefix PATH : ${lib.makeBinPath [ xdg-user-dirs ]} ''; passthru.updateScript = ./update.sh; meta = { description = "End-to-end encrypted, cross platform and free app for storing your 2FA codes with cloud backups"; longDescription = '' Ente's 2FA app. An end-to-end encrypted, cross platform and free app for storing your 2FA codes with cloud backups. Works offline. You can even use it without signing up for an account if you don't want the cloud backups or multi-device sync. ''; homepage = "https://ente.io/auth/"; changelog = "https://github.com/ente-io/ente/releases/tag/auth-v${version}"; license = lib.licenses.agpl3Only; maintainers = with lib.maintainers; [ niklaskorz schnow265 zi3m5f gepbird ]; mainProgram = "ente_auth"; platforms = [ "x86_64-linux" "aarch64-linux" ]; }; } </ins>

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


Question: meta.homepage = "https://github.com/iamcco/coc-spell-checker/"; }; <ins> coc-svelte = buildVimPluginFrom2Nix { pname = "coc-svelte"; version = "2022-03-14"; src = fetchFromGitHub { owner = "coc-extensions"; repo = "coc-svelte"; rev = "7dda98527c0831e287ae8cd1c85cfc958c949d4a"; sha256 = "0ci35dph7zz53hiw65xp79g6i8h5yk1zlcbinljfcdn5635wsjbn"; }; meta.homepage = "https://github.com/coc-extensions/coc-svelte/"; }; coc-tailwindcss = buildVimPluginFrom2Nix { pname = "coc-tailwindcss"; version = "2020-08-19"; src = fetchFromGitHub { owner = "iamcco"; repo = "coc-tailwindcss"; rev = "5f41aa1feb36e39b95ccd83be6a37ee8c475f9fb"; sha256 = "189abl36aj862m5nz8jjdgdfc4s6xbag030hi9m13yd6fbg99f85"; }; meta.homepage = "https://github.com/iamcco/coc-tailwindcss/"; }; </ins> coc-nvim = buildVimPluginFrom2Nix { pname = "coc.nvim"; version = "2022-03-26";

Project description Various vim plugins iamcco/coc-tailwindcss coc-extensions/coc-svelte evanleck/vim-svelte


Question: statix = buildVimPluginFrom2Nix rec { inherit (statix) pname src meta; version = "0.1.0"; <del> dependencies = with self; [ statix ]; </del> postPatch = '' # check that version is up to date grep 'pname = "statix-vim"' -A 1 flake.nix

When adding as a plugin I get: . completes without issue. I have plenty of other vim plugins in the exact same manner without issue.


Question: mkdir -p $out/share/{java,applications} cp ${module}-${version}.jar $out/share/java/. cp "${editorItem}/share/applications/"* $out/share/applications <del> makeWrapper ${jre8}/bin/java $out/bin/$exec  </del> <ins> makeWrapper ${jdk}/bin/java $out/bin/$exec  </ins> --prefix XDG_DATA_DIRS : "$XDG_ICON_DIRS:${gtk3.out}/share:${gsettings-desktop-schemas}/share:$out/share:$GSETTINGS_SCHEMAS_PATH"  --add-flags "-jar $out/share/java/${module}-${version}.jar -d${toString stdenv.hostPlatform.parsed.cpu.bits}" '';

Wanted to install and start sweethomed.application. the build worked without problems but when i started it, it didnt started. Steps to reproduce the behavior: sweethome3d.application via configuration file to start it Starting the Application stucks at the start screen ! Add any other context about the problem here. At the moment its installed in my user context. When i try to start it as my user over the terminal i get no errors. When i start it with "sudo sweethome3d" I get the following error, and it also dont start, also start at starting screen and vanishing from the task bar: I think these happens because its not installed as user, but propably it helps to find the issue.
Starting random applications as root seems like an unwise idea.
Apologies, I misread the error, this appears to be a separate issue
Just to confirm, which GPU do you use?
I've got the same issue, and none of the solutions given in appear to work. On my side says my GPU is . EDIT: I should mention SH3D 7.02 works fine on my setup Mmh, I just tried with , and things work just fine (even though I'm on NixOS + tells me OpenGL is happy)...
Same problem here, on NIXOS unstable. Stuck on the starting blue window. Had to install it with flatpak in the mean time... Any idea?
sorry for delay i dont get informations from messages in last time from github... really annoying... I have an Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics]
Same here, also on Intel hardware.
Based on the NixGL idea, applying the following patch works to update to the latest version and fix the driver issue on Intel. But this does not seem like the best way to go about it; I can't find a single other package messing with , and it seems more like a debugging tool than something that should be in a package.
I forgot to mention, to avoid getting terrible performance (< 1 fps), I also had to set Not sure if it's needed for others. Maybe related to my using Wayland/Sway. I also have to use to get the window displayed properly, but that's a common issue for most Java apps and tiling windowing managers.
I also ran into this issue with a Nvidia card.


Question: mkdir -p $out/share/{java,applications} cp ${module}-${version}.jar $out/share/java/. cp "${editorItem}/share/applications/"* $out/share/applications <del> makeWrapper ${jre8}/bin/java $out/bin/$exec  </del> <ins> makeWrapper ${jdk}/bin/java $out/bin/$exec  </ins> --prefix XDG_DATA_DIRS : "$XDG_ICON_DIRS:${gtk3.out}/share:${gsettings-desktop-schemas}/share:$out/share:$GSETTINGS_SCHEMAS_PATH"  --add-flags "-jar $out/share/java/${module}-${version}.jar -d${toString stdenv.hostPlatform.parsed.cpu.bits}" '';

For me, was needed (with patch). I also needed . and didn't seem needed (or give noticable changes).


Question: let <del> _enableDitaaFilter = enableExtraPlugins || enableDitaaFilter; </del> <ins> _enableDitaaFilter = (enableExtraPlugins && enableJava) || enableDitaaFilter; </ins> _enableMscgenFilter = enableExtraPlugins || enableMscgenFilter; _enableDiagFilter = enableExtraPlugins || enableDiagFilter; _enableQrcodeFilter = enableExtraPlugins || enableQrcodeFilter;

Since is provided by the non-free on aarch64, I'm not able to install asciidoc-full or any software that requires it to create e.g. the man pages. Can we make an option different from ? /cc
Making new granular options is fine, but I think enableStandardFeatures should still include java. (Or else the option is dishonest.) Alternatively, can we switch to openjdk (assuming that works on aarch64)?
It was just recently changed to in I'm fine with granular options, even though it will be quite some work to make packages not use anymore.
Oh, so this problem is due to licensing, not wanting to use non-free software? I didn't pick up on that earlier. How about adding a disableJava option, that has priority over enableStandardFeatures? Hm, this feels like a local solution to a global problem.
is a good idea! What do you think should be the default?
If enableStandardFeatures is true, you should get java. Setting disableJava then enables standard features except those requiring java. I'm not sure if doing this (per package) is a good idea though. Isn't this the start of a new whack-a-mole game?
Yes, it's certainly not a perfect solution, but I can then use an overlay which sets for . Alternatively, we could enable Java for x86 only by default.
Perhaps it would be less confusing to have so the additive condition is positive.


Question: <ins> diff --git a/src/amd/vulkan/winsys/amdgpu/radv_amdgpu_winsys.h b/src/amd/vulkan/winsys/amdgpu/radv_amdgpu_winsys.h index 06ca90564f0..bb244f8f358 100644 --- a/src/amd/vulkan/winsys/amdgpu/radv_amdgpu_winsys.h +++ b/src/amd/vulkan/winsys/amdgpu/radv_amdgpu_winsys.h @@ -30,6 +30,7 @@ #include <amdgpu.h> #include <pthread.h> +#include <sys/types.h> #include "util/list.h" #include "util/rwlock.h" #include "ac_gpu_info.h" diff --git a/src/gallium/drivers/freedreno/freedreno_util.h b/src/gallium/drivers/freedreno/freedreno_util.h index 22f99c41909..2f3195926be 100644 --- a/src/gallium/drivers/freedreno/freedreno_util.h +++ b/src/gallium/drivers/freedreno/freedreno_util.h @@ -108,6 +108,8 @@ extern bool fd_binning_enabled; #include <sys/types.h> #include <sys/syscall.h> +#define gettid() ((pid_t)syscall(SYS_gettid)) + #define DBG(fmt, ...)                                                           do {                                                                         if (FD_DBG(MSGS))                                                         diff --git a/src/gallium/frontends/nine/nine_debug.c b/src/gallium/frontends/nine/nine_debug.c index f3a6a945025..f4a6c41a612 100644 --- a/src/gallium/frontends/nine/nine_debug.c +++ b/src/gallium/frontends/nine/nine_debug.c @@ -65,7 +65,7 @@ _nine_debug_printf( unsigned long flag, { static boolean first = TRUE; static unsigned long dbg_flags = DBG_ERROR | DBG_WARN; -    unsigned long tid = 0; +    pthread_t tid = 0; if (first) { first = FALSE; @@ -74,7 +74,7 @@ _nine_debug_printf( unsigned long flag, #if defined(HAVE_PTHREAD) if (dbg_flags & DBG_TID) -        tid = (unsigned long)pthread_self(); +        tid = pthread_self(); #endif if (dbg_flags & flag) { diff --git a/src/util/rand_xor.c b/src/util/rand_xor.c index 81b64f1ea71..56ebd2eccdf 100644 --- a/src/util/rand_xor.c +++ b/src/util/rand_xor.c @@ -28,6 +28,7 @@ #if defined(HAVE_GETRANDOM) #include <sys/random.h> #endif +#include <sys/types.h>         /* size_t, ssize_t */ #include <unistd.h> #include <fcntl.h> #endif </ins>

Mesa 21.3.2 present in is causing , and they point to , not yet fixed as of now. Reverting to nixos-unstable to Mesa 21.2.6 updates fixes the issue. Steps to reproduce the behavior: sure you're using Intel GPU nixos channel to No flickering should happen on the application screen. Mesa bug report has a video demonstrating the issue. If applicable, add screenshots to help explain your problem. cc: Please run and paste the result.
According to the bug report this seems to affect at least Blender as well. Anyway, we can leave this issue open for a while (in case it helps users to figure this out) but I don't think there's anything actionable for Nixpkgs (it's an upstream bug and we simply have to wait until a fix is released via a new version). It looks like the patch from should be submitted formally via a PR so that it might get included in Mesa 21.3.4.
This is also happening on qutebrowser for me, but only on the wayland backend. I have a temporary fix to just launch with , but this obviously disables the hardware. Works fine though so far for just browsing and work stuff, at least until a proper fix is merged.
It's unlikely that the patch will be applied for 21.3.4 (as no one filed a MR for it so far), should we apply it downstream?
I'm seeing this in qutebrowser as well (non-wayland)
I'd prefer to avoid applying a patch that hasn't been reviewed upstream.
+1 for what said. Luckily a developer from Intel started looking into this so let's see how things will develop: Ideally a patch will be ready for 21.3.4 but the release might happen in two days (unless it gets delayed) so it'll indeed be close (but we'll of course re-evaluate our options once the release is out).
Unfortunately it was indeed too close for the patch to land in Mesa 21.3.4. However, now there's at least an alternative patch from Paulo Zanoni (the Intel developer) and Giuseppe Ghibò (author of the other patch) and others confirmed that it's working: I've included that patch in Does someone have time to test it () and report if it indeed fixes the issues?


Question: <ins> diff --git a/src/amd/vulkan/winsys/amdgpu/radv_amdgpu_winsys.h b/src/amd/vulkan/winsys/amdgpu/radv_amdgpu_winsys.h index 06ca90564f0..bb244f8f358 100644 --- a/src/amd/vulkan/winsys/amdgpu/radv_amdgpu_winsys.h +++ b/src/amd/vulkan/winsys/amdgpu/radv_amdgpu_winsys.h @@ -30,6 +30,7 @@ #include <amdgpu.h> #include <pthread.h> +#include <sys/types.h> #include "util/list.h" #include "util/rwlock.h" #include "ac_gpu_info.h" diff --git a/src/gallium/drivers/freedreno/freedreno_util.h b/src/gallium/drivers/freedreno/freedreno_util.h index 22f99c41909..2f3195926be 100644 --- a/src/gallium/drivers/freedreno/freedreno_util.h +++ b/src/gallium/drivers/freedreno/freedreno_util.h @@ -108,6 +108,8 @@ extern bool fd_binning_enabled; #include <sys/types.h> #include <sys/syscall.h> +#define gettid() ((pid_t)syscall(SYS_gettid)) + #define DBG(fmt, ...)                                                           do {                                                                         if (FD_DBG(MSGS))                                                         diff --git a/src/gallium/frontends/nine/nine_debug.c b/src/gallium/frontends/nine/nine_debug.c index f3a6a945025..f4a6c41a612 100644 --- a/src/gallium/frontends/nine/nine_debug.c +++ b/src/gallium/frontends/nine/nine_debug.c @@ -65,7 +65,7 @@ _nine_debug_printf( unsigned long flag, { static boolean first = TRUE; static unsigned long dbg_flags = DBG_ERROR | DBG_WARN; -    unsigned long tid = 0; +    pthread_t tid = 0; if (first) { first = FALSE; @@ -74,7 +74,7 @@ _nine_debug_printf( unsigned long flag, #if defined(HAVE_PTHREAD) if (dbg_flags & DBG_TID) -        tid = (unsigned long)pthread_self(); +        tid = pthread_self(); #endif if (dbg_flags & flag) { diff --git a/src/util/rand_xor.c b/src/util/rand_xor.c index 81b64f1ea71..56ebd2eccdf 100644 --- a/src/util/rand_xor.c +++ b/src/util/rand_xor.c @@ -28,6 +28,7 @@ #if defined(HAVE_GETRANDOM) #include <sys/random.h> #endif +#include <sys/types.h>         /* size_t, ssize_t */ #include <unistd.h> #include <fcntl.h> #endif </ins>

Thanks a lot for putting together a fix! I'm happy to test. Could you confirm I understood the instructions correctly? 1) integrate the code from the above PR into my nixpkgs tree. 2) put the following into my nixos config: 3) replace with the path to my nixpkgs tree. 4) run Did I get that right?
It's the easiest if you use a separate/dedicated Nixpkgs tree for Mesa ( in the example). That way you don't have to rebuild a lot of other packages (which would most likely still take way too long). You can also cherry-pick the commit to (I'd recommend doing that) which saves additional rebuilds (I only tested it that way so no idea how many many builds are currently cached for staging-next). The rest looks fine. And thanks in advance :)
It works like a charm. Thanks
Seems like this wasn't closed automatically once landed in master. Should be fixed now. And upstream merged the required patches in the meantime (s. note in ). And thanks for testing the fix and :)


Question: wl-screenrec = callPackage ../tools/wayland/wl-screenrec { }; <ins> wleave = callPackage ../tools/wayland/wleave { }; </ins> wlogout = callPackage ../tools/wayland/wlogout { }; wlopm = callPackage ../tools/wayland/wlopm { };

Project description A Wayland-native logout script written in Gtk3 Metadata homepage URL: source URL: license: mit platforms: unix, linux
It's already packaged in nixpkgs-wayland IIRC


Question: owner = "tailscale"; repo = "tailscale"; rev = "v${version}"; <del> hash = "sha256-rB/zaJavA3OH1HK7Rfpta/QmQzi0xsEYTvW5JzzTAlI="; </del> <ins> hash = "sha256-PFXXd5ToBbvuGl+u4nEAHy1F696lxHD3PrPJ3Tpb+eg="; </ins> }; patches = [

Package name: tailscale Latest released version: 1.72.0 <!-- Search your package here: --- Current version on the unstable channel: 1.70.0 Current version on the stable/release channel: 1.66.4 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: homepage = https://github.com/thestinger/termite/; maintainers = with maintainers; [ koral garbas ]; platforms = platforms.all; <del> broken = true; </del> }; }; in if configFile == null then termite else symlinkJoin {

The package has been . Trying to install results in the following error: Why was the package marked as broken? Is there a way to help fix it? System: Nix version: Nixpkgs version:
According to the project homepage it requires a different version of the vte library: If you package this one and add it as a dependency the package should work again.
Thanks for the response . Could you help understand the reasoning behind the commit that marked it as broken? Was the problem that was being packaged with the wrong dependency?
The dependency it needs is not in NixPkgs, so it has to be packaged and nobody cared enough to do it.
We had the patched vte under gnome-3.20, but 3.20 was now removed whole without porting that to the vte in 3.22. EDIT: refs and .
I've wasted hours trying to fix building the special vte library, you may try to continue: This fails with: I don't see marking one package broken preferable to keeping the whole gnome-3.20 in tree, sadly. Please open a pull request if you manage to succeed, but I don't see myself wasting more time on this otherwise soon.
I fixed the errors you found during compilation and submitted a PR to upstream VTE. As the changes may take a while to propagate down into vte-ng, I them as patches to the vte-ng package, which is now used to compile termite.


Question: timerConfig.OnCalendar = cfg.dump.interval; }; }; <ins> meta.maintainers = with lib.maintainers; [ srhb ]; </ins> }

Describe the bug gitea fails to start due to a too restrictive systemd setup To Reproduce Looks like is a bit too restrictive. :smile:
ping
Removing the blacklist of and gets us past the test, I think, but there's still problems with the socket.
Judging from this error output: it looks like it fails in prescript during in Interestingly enough, there is a right underneath that, in which does not seem to be the issue. This does not look like an issue with Gitea itself, since it fails during the service pre script. Since the and will only be run if the configuration is managed by nix, the tests pass if I set in the test config. (unfortunatly I don't know much about systemd services and especially systemd sanboxing, so I'm not sure if the information from above is useful or not)
Any chance the service is broken too? I recently updated and service failed to start. I haven't dug into it yet... I may have seen something about a database permission issue.
Temporary fix for someone who using bleeding-edge Gitea:
This doesn't solve the issue for me. I get the following output:
Pretty strange. It works for me (). You can try to disable it at all () and if it'll still not work then just change in the same way all other parameters to default values that were introduced in . p.s. probably there's must be something like a mkForceRemove, but I haven't found anything in manual.
Ok the fix is actually working, I just had an own AmbientCapabilities definition in my configuration which didn't play nicely with the new options.


Question: buildGoModule rec { pname = "apx"; <del> version = "1.7.0-1"; </del> <ins> version = "1.8.2"; </ins> src = fetchFromGitHub { owner = "Vanilla-OS"; repo = pname; <del> rev = "v${version}"; hash = "sha256-tonI3S0a08MbR369qaKS2BoWc3QzXWzTuGx/zSgUz7s="; </del> <ins> rev = "refs/tags/${version}"; hash = "sha256-nBhSl4r7LlgCA5/HCLpOleihE5n/JCJgf43KdCklQbg="; </ins> }; vendorSha256 = null;

Package name: Apx Latest released version: 1.8.2 <!-- Search your package here: --- Current version on the unstable channel: 0-1 Current version on the stable/release channel: N/A <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR.


Question: <ins> --- a/llm/generate/gen_common.sh +++ b/llm/generate/gen_common.sh @@ -60,6 +60,9 @@ } apply_patches() { +    patch -i '@cmakeIncludePatch@' "${LLAMACPP_DIR}/examples/server/CMakeLists.txt" +    return + # Wire up our CMakefile if ! grep ollama ${LLAMACPP_DIR}/examples/server/CMakeLists.txt; then echo 'include (../../../ext_server/CMakeLists.txt) # ollama' >>${LLAMACPP_DIR}/examples/server/CMakeLists.txt @@ -113,6 +116,8 @@ # Keep the local tree clean after we're done with the build cleanup() { +    return + (cd ${LLAMACPP_DIR}/examples/server/ && git checkout CMakeLists.txt server.cpp) if [ -n "$(ls -A ../patches/*.diff)" ]; then </ins>

Package name: ollama Latest released version: 0.1.20 <!-- Search your package here: --- Current version on the unstable channel: 0.1.17 Current version on the stable/release channel: 0.1.7 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
20 was released.[^1] :tada: Had a quick look into the source changes. Seems that patching is required because of the integration of ROCm. [^1]:
I modified the title :-)
21 is going to be released very soon.
I opened
update: 0.1.22 is the latest version.
Seems update can be problematic. I've tried manually download and executing new ollama and encountered a lot of issues connected with ROCM libraries. After adding I've got it to state where it crushes: But before adding it seems also miss new version of because it was asking for but current unstable version have CPU works fine without mentioned ROCM packages.
This appears to have been resolved by . Reopen if it's not.


Question: "-Ddocs-build=true" ]; <ins> preConfigure = '' export KBUILD_BUILD_TIMESTAMP="$(date -u -d @$SOURCE_DATE_EPOCH)" ''; </ins> doCheck = true; meta = with lib; {

Building the manpages for this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: (please share the relevant fragment of the diffoscope output here, and any additional analysis you may have done)


Question: cp "${sweethome3dItem}/share/applications/"* $out/share/applications <del> # MESA_GL_VERSION_OVERRIDE is needed since the update from MESA 19.3.3 to 20.0.2: # without it a "Profiles [GL4bc, GL3bc, GL2, GLES1] not available on device null" # exception is thrown on startup. # https://discourse.nixos.org/t/glx-not-recognised-after-mesa-update/6753 makeWrapper ${jre8}/bin/java $out/bin/$exec  --set MESA_GL_VERSION_OVERRIDE 2.1  </del> <ins> makeWrapper ${jdk}/bin/java $out/bin/$exec  </ins> --prefix XDG_DATA_DIRS : "$XDG_ICON_DIRS:${gtk3.out}/share:${gsettings-desktop-schemas}/share:$out/share:$GSETTINGS_SCHEMAS_PATH"  <ins> --prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath [ libGL ]}"  </ins> --add-flags "-Dsun.java2d.opengl=true -jar $out/share/java/${module}-${version}.jar -cp $out/share/java/Furniture.jar:$out/share/java/Textures.jar:$out/share/java/Help.jar -d${toString stdenv.hostPlatform.parsed.cpu.bits}"


Question: cp "${sweethome3dItem}/share/applications/"* $out/share/applications <del> # MESA_GL_VERSION_OVERRIDE is needed since the update from MESA 19.3.3 to 20.0.2: # without it a "Profiles [GL4bc, GL3bc, GL2, GLES1] not available on device null" # exception is thrown on startup. # https://discourse.nixos.org/t/glx-not-recognised-after-mesa-update/6753 makeWrapper ${jre8}/bin/java $out/bin/$exec  --set MESA_GL_VERSION_OVERRIDE 2.1  </del> <ins> makeWrapper ${jdk}/bin/java $out/bin/$exec  </ins> --prefix XDG_DATA_DIRS : "$XDG_ICON_DIRS:${gtk3.out}/share:${gsettings-desktop-schemas}/share:$out/share:$GSETTINGS_SCHEMAS_PATH"  <ins> --prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath [ libGL ]}"  </ins> --add-flags "-Dsun.java2d.opengl=true -jar $out/share/java/${module}-${version}.jar -cp $out/share/java/Furniture.jar:$out/share/java/Textures.jar:$out/share/java/Help.jar -d${toString stdenv.hostPlatform.parsed.cpu.bits}"


Question: extraArgs = [ "--version-regex" "r(.*)" ]; }; <del> nativeBuildInputs = [ cmake pkg-config ]; </del> <ins> nativeBuildInputs = [ cmake pkg-config ] ++ lib.optional buildAudaciousPlugin gtk3; </ins> <del> buildInputs = [ mpg123 ffmpeg libvorbis libao jansson speex ]; </del> <ins> buildInputs = [ mpg123 ffmpeg libvorbis libao jansson speex ] ++ lib.optional buildAudaciousPlugin (audacious.override { audacious-plugins = null; }); preConfigure = '' substituteInPlace cmake/dependencies/audacious.cmake  --replace "pkg_get_variable(AUDACIOUS_PLUGIN_DIR audacious plugin_dir)" "set(AUDACIOUS_PLUGIN_DIR "$out/lib/audacious")" ''; </ins> cmakeFlags = [ <del> # There's no nice way to build the audacious plugin without a circular dependency "-DBUILD_AUDACIOUS=OFF" </del> # It always tries to download it, no option to use the system one "-DUSE_CELT=OFF" <del> ]; </del> <ins> ] ++ lib.optional (! buildAudaciousPlugin) "-DBUILD_AUDACIOUS=OFF"; </ins> meta = with lib; { description = "A library for playback of various streamed audio formats used in video games";

The audacious package imports audacious-plugins to build most of the common plugins and then link them into the audacious lib path. However, this makes it hard to add more audacious plugins, like vgmstream. The vgmstream package currently has its , because importing the audacious package causes an infinite recursion error. Steps to reproduce the behavior: vgmstream to audacious-plugins buildInputs audacious to vgmstream's buildInputs and comment out the disable configure flag -shell -p audacious-plugins I expected that adding vgmstream to audacious-plugins would enable the plugin. Instead, the build crashes with an infinite recursion. How is it currently working for audacious to import audacious-plugins and audacious-plugins to import audacious? Can this same magic be extended to other plugins? This about how fcitx is packaged shows that fcitx-addons imports fcitx with no reverse import, should the audacious package be refactored to be similar? Should the audacious package gain an extra parameter to take extra plugin derivations, which can be created outside of the audacious-plugins derivation? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Instead of adding , did you try to add instead? is without as input, and it is used to break the loop.
Thank you for the quick response! That would be elegant, but I don't see any result in my grep of nixpkgs or in the .
Sorry, it is here: Basically you need to do and this should do the trick. Considering that we are going to use this in more than one place it probably makes sense to introduce it as a , but the result is the same regardless.
Oh that's a neat trick! I'll try that approach out next. Thank you so much! I tried out the extra-plugins approach here, seems to work but is not ergonomic:
I , and it's a lot easier to use as a user! If it looks good as an approach, please provide some review feedback and I'll squash it down for a PR :)
Shall I send a PR for a final review?


Question: <ins> { lib , stdenv , rustPlatform , fetchFromGitHub }: rustPlatform.buildRustPackage rec { pname = "evebox"; version = "0.17.2"; src = fetchFromGitHub { owner = "jasonish"; repo = "evebox"; rev = version; hash = "sha256-djL5cdudJNPAWLMQPS2Dkcc9H/gouOuu8evcBDdY9wA="; }; cargoLock = { lockFile = ./Cargo.lock; outputHashes = { "libsqlite3-sys-0.25.2" = "sha256-+c7ong6ca4WkEHl7ynCNn3WW68jF3pSYbllRsaNFGLc="; "suricatax-rule-parser-0.1.0" = "sha256-upWgOKSAuj0pYGTeYKANzwutoF/m4AQ7MkzGYXmPbEo="; }; }; meta = { description = "Web Based Event Viewer (GUI) for Suricata EVE Events in Elastic Search"; homepage = "https://evebox.org/"; changelog = "https://github.com/jasonish/evebox/releases/tag/${src.rev}"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ felbinger ]; broken = stdenv.isDarwin; }; } </ins>

Project description EveBox is a Suricata alert and event management tool for the Suricata IDS/NSM Engine. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: <del> diff --git a/bin/nexus b/bin/nexus index e7ed3fb..8db766b 100755 --- a/bin/nexus +++ b/bin/nexus @@ -440,7 +440,8 @@ add_class_path "$app_home/lib/boot/org.apache.karaf.diagnostic.boot-4.0.9.jar" add_class_path "$app_home/lib/boot/org.apache.karaf.jaas.boot-4.0.9.jar" vmoptions_val="" -read_vmoptions "$prg_dir/$progname.vmoptions" +VM_OPTS=${VM_OPTS_FILE:-"$prg_dir/$progname.vmoptions"} +read_vmoptions "$VM_OPTS" INSTALL4J_ADD_VM_PARAMS="$INSTALL4J_ADD_VM_PARAMS $vmoptions_val" </del>

Package name: nexus Latest released version: 3.69.0 <!-- Search your package here: --- Current version on the unstable channel: 3.68.1-02 Current version on the stable/release channel: 3.68.1-02 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: (mkChangedOptionModule [ "security" "initialRootPassword" ] [ "users" "users" "root" "initialHashedPassword" ] <del> (cfg: if cfg.security.initialHashedPassword == "!" </del> <ins> (cfg: if cfg.security.initialRootPassword == "!" </ins> then null <del> else cfg.security.initialHashedPassword)) </del> <ins> else cfg.security.initialRootPassword)) </ins> ]; ###### interface

Describe the bug A clear and concise description of what the bug is. I am using nixops to manage a number of machines, some of which use nixpkgs-unstable. When deploying a machine with nixpkgs-unstable, I started getting errors stating . These are likely linked to a change in the last week or so, as I've been able to deploy the same machine perfectly fine last week. When run with , I get: After getting this error the first time, I initialHashedPassword to all 2 of my users, as well as root, as follows: This fails with the same error. Deploying with nixpkgs 20.03 works fine. The error seems to originate from , specifically: I also tried adding , which naturally fails as that attribute doesn't exist. It also fails with the same trace when using instead of To Reproduce Steps to reproduce the behavior: to deploy a machine (maybe nixops is required?) with the latest nixpkgs-unstable Expected behavior The machine should deploy normally, even without , as it used to last week Screenshots N/A Additional context I suspect it might be linked to Notify maintainers - Tagging you as your PR was the last one to touch this area Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(raghav): nixpkgs: I'm using nixops release-1.7 Maintainer information:
Yeah, this really smells like .
Argh, I made a stupid typo. I'll fix this ASAP.


Question: in stdenv.mkDerivation rec { pname = "mpv"; <del> version = "0.33.1"; </del> <ins> version = "0.34.0"; </ins> <del> outputs = [ "out" "dev" ]; </del> <ins> outputs = [ "out" "dev" "man" ]; </ins> src = fetchFromGitHub { <del> owner  = "mpv-player"; repo   = "mpv"; rev    = "v${version}"; sha256 = "06rw1f55zcsj78ql8w70j9ljp2qb1pv594xj7q9cmq7i92a7hq45"; </del> <ins> owner = "mpv-player"; repo = "mpv"; rev = "v${version}"; sha256 = "sha256-qa6xZV4aLcHBMa2bIqoKjte4+KWEGGZre4L0u1+eDE8="; </ins> }; <del> patches = [ # To make mpv build with libplacebo 3.104.0: (fetchpatch { # vo_gpu: placebo: update for upstream API changes url = "https://github.com/mpv-player/mpv/commit/7c4465cefb27d4e0d07535d368febdf77b579566.patch"; sha256 = "1yfc6220ak5kc5kf7zklmsa944nr9q0qaa27l507pgrmvcyiyzrx"; }) # TOREMOVE when > 0.33.1 # youtube-dl has been abandonned and is now unusable w/ # youtube.com. Mpv migrated to yt-dlp since the 0.33.1 but did not # cut a new release yet. See # https://github.com/mpv-player/mpv/pull/9209 (fetchpatch { url = "https://github.com/mpv-player/mpv/commit/d1c92bfd79ef81ac804fcc20aee2ed24e8d587aa.patch"; sha256 = "1dwxzng3gsrx0gjljm5jmfcjz3pzdss9z2l0n25rmmb4nbcrcx1f"; }) ]; </del> postPatch = '' patchShebangs ./TOOLS/ ''; <del> passthru = { inherit # The wrapper consults luaEnv and lua.version luaEnv lua # In the wrapper, we want to reference vapoursynth which has the # `python3` passthru attribute (which has the `sitePrefix` # attribute). This way we'll be sure that in the wrapper we'll # use the same python3.sitePrefix used to build vapoursynth. vapoursynthSupport vapoursynth ; }; NIX_LDFLAGS = optionalString x11Support "-lX11 -lXext " + optionalString stdenv.isDarwin "-framework CoreFoundation"; </del> <ins> NIX_LDFLAGS = lib.optionalString x11Support "-lX11 -lXext " + lib.optionalString stdenv.isDarwin "-framework CoreFoundation"; </ins> wafConfigureFlags = [ "--enable-libmpv-shared"

<!-- 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 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: mpv <!-- The current version can be found easily with the same process than 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: 0.33.1 desired version: 0.34.0 <!-- 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.


Question: return _fileSystem.directory(_fileSystem.path.join(_rootOverride.path, 'bin', 'cache')); } else { -      return _fileSystem.directory(_fileSystem.path.join(flutterRoot, 'bin', 'cache')); <del> +      return _fileSystem.directory(_fileSystem.path.join(homeDirPath, '.cache', 'flutter')); </del> <ins> +      return _fileSystem.directory(_fileSystem.path.join(globals.fsUtils.homeDirPath, '.cache', 'flutter')); </ins> } }

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


Question: bitwise = callPackage ../tools/misc/bitwise { }; <ins> blanket = callPackage ../applications/audio/blanket { }; </ins> brakeman = callPackage ../development/tools/analysis/brakeman { }; brewtarget = libsForQt514.callPackage ../applications/misc/brewtarget { } ;

Project description ! Metadata homepage URL: source URL: license: gpl3 platforms: linux
FTR: This requires an update of .
I marked this as stale due to inactivity. →


Question: inherit (pkgs) xmlsec; }; <ins> pysatochip = callPackage ../development/python-modules/pysatochip { }; </ins> pysc2 = callPackage ../development/python-modules/pysc2 { }; pyscard = callPackage ../development/python-modules/pyscard {

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


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

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


Question: }; url_preview_ip_range_blacklist = mkOption { type = types.listOf types.str; <del> default = []; </del> <ins> default = [ "127.0.0.0/8" "10.0.0.0/8" "172.16.0.0/12" "192.168.0.0/16" "100.64.0.0/10" "169.254.0.0/16" ]; </ins> description = '' List of IP address CIDR ranges that the URL preview spider is denied from accessing.

default value causes previews to fail. the usual homeserver config Do not configure (so that the default value is used) Post URL into a preview enabled room Find similar error in synapse log: The option defaults to . Were those values intended as default for the option? Excerpt from a working configuration: /cc (as you discussed the security implications in )
Seems like a good bet.
thanks for fixing this, I was just wondering about this earlier today:


Question: # If multiple remote sources are enabled, nuget will try them all # concurrently and use the one that responds first. We always use the # first source that has the package. <del> echo "$package $version is available on $url, but was downloaded from ${base_addresses[$used_source]}$package/$version/$package.$version.nupkg" 1>&2 </del> <ins> echo "$package $version is available at $url, but was restored from $used_source" 1>&2 </ins> found=true break else

I'm getting an error /nix/store/jx2hdq8n3fdj0bm58qxgy0psyyl0vd05-nuget-to-nix/bin/nuget-to-nix: line 56: baseaddresses[$usedsource]: unbound variable when trying to generate a lockfile for . Steps to reproduce the behavior: this simple file: to generate the script the error Be able to generate the lockfile. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. I guess was the one to introduce the variable there.
could you give a try?
The problem seems to be that there's a repo in the sdk at , containing only . This is somehow referenced implicitly. I'm not sure if we should do anything more to handle this situation, but the message fix should do for now.


Question: , fetchpatch , python3Packages , asciidoc <del> , makeWrapper </del> <ins> , wrapGAppsNoGuiHook </ins> , iw }:

Steps to reproduce the behavior: to NixOS config Successfully start. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: <del> { lib, stdenv, fetchFromGitHub } : </del> <ins> { lib , stdenv , fetchFromGitHub , netpbm }: </ins> stdenv.mkDerivation rec { pname = "fbcat";

Steps to reproduce the behavior: working program Add any other context about the problem here. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:


Question: <ins> --- a/llm/llama.cpp/examples/server/CMakeLists.txt +++ b/llm/llama.cpp/examples/server/CMakeLists.txt @@ -11,3 +11,4 @@ TARGET_LINK_LIBRARIES(${TARGET} PRIVATE ws2_32) endif() target_compile_features(${TARGET} PRIVATE cxx_std_11) +include (../../../ext_server/CMakeLists.txt) # ollama </ins>


Question: print("skipping systemd-boot update to %s because of known regression" % available_version) else: print("updating systemd-boot from %s to %s" % (installed_version, available_version)) <del> subprocess.check_call(["@systemd@/bin/bootctl", "--esp-path=@efiSysMountPoint@", "update"]) </del> <ins> subprocess.check_call(["@systemd@/bin/bootctl", "--esp-path=@efiSysMountPoint@"] + bootctl_flags + ["update"]) </ins> mkdir_p("@efiSysMountPoint@/efi/nixos") mkdir_p("@efiSysMountPoint@/loader/entries")

During systemd-boot update step attempts to touch EFI variables, even when is set to . Steps to reproduce the behavior: NixOS 21.05 with systemd-boot and to NixOS 21.11 () switch fails with: An error is just an indication of update trying to touch EFI variables. (I have EFI vars touching disabled on that system because of some unrelated firmware breakage) Manually running properly finishes, further switches work fine. systemd-boot update should not touch EFI variables during upgrade. <!-- 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. Maintainer information:
I had a similar issue which I fixed by running "sudo nixos-rebuild --install-bootloader switch"
The fix for this got reverted in


Question: moveToOutput bin/isc-config.sh $dev moveToOutput bin/host $host <del> ln -sf $host/bin/host $bin/bin </del> moveToOutput bin/dig $dnsutils moveToOutput bin/nslookup $dnsutils moveToOutput bin/nsupdate $dnsutils <del> ln -sf $dnsutils/bin/{dig,nslookup,nsupdate} $bin/bin ln -sf $host/bin/host $dnsutils/bin </del> for f in "$lib/lib/"*.la "$dev/bin/"{isc-config.sh,bind*-config}; do sed -i "$f" -e 's|-L${openssl.dev}|-L${openssl.out}|g'

The symlinking between the multiple outputs of seems to prevent it from installing. I was looking to install it to have the dig command available. - System: 17.03pre94050. (Gorilla) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: "17.03pre94050."
11.4 still doesn't contain :-( How could we have that as default in 16.09? I consider it quite an important feature for + multiple outputs. would you be against porting that PR to 1.11.5 and making that default in 16.09 and master?
+1 for a 1.11.5 Nix release in general :)
Since this seems to be an issue for multiple packages, I am raising the severity on here.
Looks like the same kind of issue as So +1 for Nix 1.11.5 on NixOS 16.09, if that's what it takes to fix this.
ping again about nix-1.11.5 (my comment above).


Question: librarian-puppet-go = callPackage ../development/tools/librarian-puppet-go { }; <ins> libgcc = stdenv.cc.cc.libgcc or null; </ins> # This is for e.g. LLVM libraries on linux. gccForLibs = if stdenv.targetPlatform == stdenv.hostPlatform && targetPackages.stdenv.cc.isGNU

On or cross-compiled from , breaks: From : You can either run this on another architecture using . or should not crash: This was responsible for failing to replicate datasets to my ARM NAS. The issue does not_ occur for natively compiled builds. It appears to be a cross-compilation issue only.
It is a bug in / derivations. In non-cross cases it gets copied from used to bid into output: But in cross-case used to build does not yet provide as it needs bits of for it (and the library path is slightly incorrect). One of possible workarounds is to try to add to to get it pulled via from expected location.
We don't do the copying to glibc anymore, but this error still occurs as described on current nixpkgs master.
Yup. cross-compilation never propagated to in any form (and does not today).
Could you please try this PR? It should fix the problem.
With that PR, I'm seeing this on both (a Raspberry Pi CM4) and with QEMU on : Log from aarch64 machine: Log from machine with QEMU:
Well it's finding now, so there's clearly some other problem with addition to that. When I run it with I even get line numbers from inside : That line () is the last line in the following snippet of code: ... so is deliberately ing here due to . Grepping through the docs turns up: This is happening because uses . Once you do that, glibc needs to unwind the stack frame of any thread that calls . And unwinders are a giant headache. I'm afraid that's all I've got here. I've removed the closed-by from since it was only part of the problem here.
Ah, I think I know what it is. We can compile a without , but it won't have an unwinder. We need to pass the glibc headers to the build in order to get one of those.
would you please try ? I believe it fixes one of the two problems which caused this issue, and it includes which fixes the other one. It works for me: BTW, this issue (cross-compile , then run it under qemu) is a really valuable test case. We really ought to add it to so Hydra will catch any regressions automatically.


Question: librarian-puppet-go = callPackage ../development/tools/librarian-puppet-go { }; <ins> libgcc = stdenv.cc.cc.libgcc or null; </ins> # This is for e.g. LLVM libraries on linux. gccForLibs = if stdenv.targetPlatform == stdenv.hostPlatform && targetPackages.stdenv.cc.isGNU

Especially since the failure mode gives the user no error message to help them troubleshoot the problem! is a great candidate for this since it's one of those very rare non-C++ programs that uses advanced stack-unwinding features from pthreads.
Confirming fixes the issue. Tested with both and on real hardware and with QEMU on x86_64.
~I think this is fixed, and more cleanly,~ by Edit: it is not. :frowning_face: I will keep trying. Test is in Currently building.
Added this to , but commented out since it is not fixed yet.


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

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


Question: <ins> { config, lib, pkgs, ... }: let cfg = config.programs.darling; in { options = { programs.darling = { enable = lib.mkEnableOption (lib.mdDoc "Darling, a Darwin/macOS compatibility layer for Linux"); package = lib.mkPackageOptionMD pkgs "darling" {}; }; }; config = lib.mkIf cfg.enable { security.wrappers.darling = { source = lib.getExe cfg.package; owner = "root"; group = "root"; setuid = true; }; }; } </ins>

Darling is a compatibility layer for running macOS apps on Linux (think Wine for macOS). I think it would be interesting to work on with macOS support. They have reverse engineered some headers that Apple doesn't release publicly so having them in "libdarling" could be useful.
We already have this part:
Just heard of Darling. I would be delighted if it could be used for running builds on NixOS!
It seem to be packaged by but only for macOS. If i understand the project correctly, that makes no sense. We want it on linux, to run macOS apps. Also, the package has no version. That's probably because they havn't tagged a version yet. So this is pre-alpha state software. could you update the package to the commit the "stable" AUR package uses and add a version as described here: ? Then we can close this issue.
It looks like the project has started using tagged versions:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
I'd still be very interested in seeing this , especially with the hope of future cross-compilation support
This would even make it possible to package Mac binaries for Linux!
I'm interested in this so that I can test cross compiled binaries when running tests.
I marked this as stale due to inactivity. →
Not stale!!
darling-dmg is just part of . To be exact, it is included as a submodule in the source tree of darling. The darling build will come with kernel modules. It would need someone with kernel-packaging experience to pack it into Nixpkgs. Build instructions in the Darling Docs:
I marked this as stale due to inactivity.


Question: <ins> { config, lib, pkgs, ... }: let cfg = config.programs.darling; in { options = { programs.darling = { enable = lib.mkEnableOption (lib.mdDoc "Darling, a Darwin/macOS compatibility layer for Linux"); package = lib.mkPackageOptionMD pkgs "darling" {}; }; }; config = lib.mkIf cfg.enable { security.wrappers.darling = { source = lib.getExe cfg.package; owner = "root"; group = "root"; setuid = true; }; }; } </ins>

→
I'd still like to see this, though largely for much the same reason Andrew mentions at this point -- I've started working with zig and being able to test cross-compiled macos binaries would be brilliant.
I have got most of a Darling build file running, but I have found an interesting issue. Wever I build I get the following error: From this cmake file: As far as I can tell, the command is a special MacOS thing, and I unfortunately do not understand CMake well enough to fix it...
Well, turns out the issue is that Darling relies on git-submodules, and it looks like this must be built against the Git repo directly, not against the released tarball...
What would therefore be a derivation?
What do you mean It's just a with .
I tried to re-package the prebuilt deb from darling GitHub releases. Here is the nix code darling- Save these 2 snippets as and darling-, then run . With 2 problems: needs setuid/setgid perms, while nix-build would fail if dpkg-deb -x executed directly. I use fakeroot to ignore this problem. always fails. I am not a darling expert, have no idea.
Ah, fantastic, thanks! Looking forward to having this in nixpkgs anyway, but let's see how we go there.
It could be named when entering Nixpkgs.
Good suggestion. I've edited those two scripts.
I got as far as finding out that darlingserver doesn't start with that script because it expects /usr/bin, so updating my to a version, the next issue was that darlingserver was trying to mount overlayfs on "lowerdir=/usr/libexec/darling,up" (may be incomplete, this is strace output) which did not exist.
After a bit of tinkering I got Darling to build from source. I opened with more info. Please give it a try!
It seems that they now use instead of the kernel module. This would make packaging easier.
What's the purpose of ? If it is only the sandbox part of Darling, a new name like would bring less confusion. Update: Opened PR to do the renaming.


Question: { stdenv, fetchurl, makeWrapper, pkgconfig, nss, nspr, libqb <del> , dbus, librdmacm, libibverbs, libstatgrab, net_snmp </del> <ins> , dbus, rdma-core, libstatgrab, net_snmp </ins> , enableDbus ? false , enableInfiniBandRdma ? false , enableMonitoring ? false

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


Question: <ins> { "name": "ember-cli", "version": "5.3.0", "description": "Command line tool for developing ambitious ember.js apps", "keywords": [ "app", "app-kit", "blockchain", "cli", "ember", "ember-app-kit", "ember.js", "kit" ], "homepage": "https://cli.emberjs.com/release/", "bugs": { "url": "https://github.com/ember-cli/ember-cli/issues" }, "repository": { "type": "git", "url": "https://github.com/ember-cli/ember-cli.git" }, "license": "MIT", "author": "Stefan Penner, Robert Jackson and ember-cli contributors", "main": "lib/cli/index.js", "bin": { "ember": "./bin/ember" }, "scripts": { "docs": "yuidoc", "lint": "eslint . --cache", "prepack": "yarn docs", "test": "node --unhandled-rejections=strict tests/runner", "test:all": "node --unhandled-rejections=strict tests/runner all", "test:cover": "nyc --all --reporter=text --reporter=lcov node tests/runner all", "test:debug": "node --unhandled-rejections=strict debug tests/runner", "test:slow": "node --unhandled-rejections=strict tests/runner slow" }, "dependencies": { "@babel/core": "^7.22.10", "@pnpm/find-workspace-dir": "^6.0.2", "broccoli": "^3.5.2", "broccoli-builder": "^0.18.14", "broccoli-concat": "^4.2.5", "broccoli-config-loader": "^1.0.1", "broccoli-config-replace": "^1.1.2", "broccoli-debug": "^0.6.5", "broccoli-funnel": "^3.0.8", "broccoli-funnel-reducer": "^1.0.0", "broccoli-merge-trees": "^4.2.0", "broccoli-middleware": "^2.1.1", "broccoli-slow-trees": "^3.1.0", "broccoli-source": "^3.0.1", "broccoli-stew": "^3.0.0", "calculate-cache-key-for-tree": "^2.0.0", "capture-exit": "^2.0.0", "chalk": "^4.1.2", "ci-info": "^3.8.0", "clean-base-url": "^1.0.0", "compression": "^1.7.4", "configstore": "^5.0.1", "console-ui": "^3.1.2", "core-object": "^3.1.5", "dag-map": "^2.0.2", "diff": "^5.1.0", "ember-cli-is-package-missing": "^1.0.0", "ember-cli-lodash-subset": "^2.0.1", "ember-cli-normalize-entity-name": "^1.0.0", "ember-cli-preprocess-registry": "^5.0.1", "ember-cli-string-utils": "^1.1.0", "ensure-posix-path": "^1.1.1", "execa": "^5.1.1", "exit": "^0.1.2", "express": "^4.18.1", "filesize": "^10.0.8", "find-up": "^5.0.0", "find-yarn-workspace-root": "^2.0.0", "fixturify-project": "^2.1.1", "fs-extra": "^11.1.1", "fs-tree-diff": "^2.0.1", "get-caller-file": "^2.0.5", "git-repo-info": "^2.1.1", "glob": "^8.1.0", "heimdalljs": "^0.2.6", "heimdalljs-fs-monitor": "^1.1.1", "heimdalljs-graph": "^1.0.0", "heimdalljs-logger": "^0.1.10", "http-proxy": "^1.18.1", "inflection": "^2.0.1", "inquirer": "^9.1.5", "is-git-url": "^1.0.0", "is-language-code": "^3.1.0", "isbinaryfile": "^5.0.0", "leek": "0.0.24", "lodash.template": "^4.5.0", "markdown-it": "^13.0.1", "markdown-it-terminal": "^0.4.0", "minimatch": "^7.4.3", "morgan": "^1.10.0", "nopt": "^3.0.6", "npm-package-arg": "^10.1.0", "os-locale": "^5.0.0", "p-defer": "^3.0.0", "portfinder": "^1.0.32", "promise-map-series": "^0.3.0", "promise.hash.helper": "^1.0.8", "quick-temp": "^0.1.8", "remove-types": "^1.0.0", "resolve": "^1.22.1", "resolve-package-path": "^4.0.3", "safe-stable-stringify": "^2.4.3", "sane": "^5.0.1", "semver": "^7.3.5", "silent-error": "^1.1.1", "sort-package-json": "^1.57.0", "symlink-or-copy": "^1.3.1", "temp": "0.9.4", "testem": "^3.10.1", "tiny-lr": "^2.0.0", "tree-sync": "^2.1.0", "uuid": "^9.0.0", "walk-sync": "^3.0.0", "watch-detector": "^1.0.2", "workerpool": "^6.4.0", "yam": "^1.0.0" }, "devDependencies": { "@octokit/rest": "^19.0.7", "broccoli-plugin": "^4.0.3", "broccoli-test-helper": "^2.0.0", "chai": "^4.3.7", "chai-as-promised": "^7.1.1", "chai-files": "^1.4.0", "chai-jest-snapshot": "^2.0.0", "ember-cli-blueprint-test-helpers": "^0.19.2", "ember-cli-internal-test-helpers": "^0.9.1", "eslint": "^8.44.0", "eslint-config-prettier": "^8.9.0", "eslint-plugin-chai-expect": "^3.0.0", "eslint-plugin-mocha": "^10.1.0", "eslint-plugin-n": "^16.0.1", "eslint-plugin-prettier": "^4.2.1", "fixturify": "^3.0.0", "jsdom": "^21.1.1", "latest-version": "^5.1.0", "mocha": "^10.0.0", "nock": "^13.3.0", "nyc": "^15.1.0", "prettier": "2.8.7", "release-it": "^15.10.0", "rimraf": "^3.0.2", "strip-ansi": "^6.0.0", "supertest": "^6.3.1", "testdouble": "^3.18.0", "tmp": "^0.2.1", "websocket": "^1.0.32", "which": "3.0.1", "yuidoc-ember-cli-theme": "^1.0.4", "yuidocjs": "0.10.2" }, "engines": { "node": ">= 16" }, "publishConfig": { "registry": "https://registry.npmjs.org" }, "release-it": { "git": { "tagName": "v${version}" }, "github": { "draft": true, "release": true, "tokenRef": "GITHUB_AUTH" } }, "trackingCode": "UA-49225444-1", "volta": { "node": "16.19.1", "yarn": "1.22.19" } } </ins>

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


Question: ThomasMader = "Thomas Mader <thomas.mader@gmail.com>"; thoughtpolice = "Austin Seipp <aseipp@pobox.com>"; timbertson = "Tim Cuthbertson <tim@gfxmonk.net>"; <ins> timokau = "Timo Kaufmann <timokau@zoho.com>"; </ins> titanous = "Jonathan Rudenberg <jonathan@titanous.com>"; tnias = "Philipp Bartsch <phil@grmr.de>"; tohl = "Tomas Hlavaty <tom@logand.com>";

Since Sage is huge and complicated, I figured I would make this issue to collaboratively track progress and share branches. One big issue is that Sage 7 , instead they use some with scant documentation . has the correct SHA256 for Sage 7.6 and updates a patch file. It currently fails when Sage tries to build . Some nice things to do for the future: ) cc:
thanks for picking this up
Me myself being a miserable loser who has failed to update Sage in the past, I hope you succeed… My attempt hit the following wall. It is unbearably slow to let Sage build everything, but when I had convinced it to use the system versions of majority of dependencies it began to complain cryptically about their interaction in some case.
Can you elaborate? Do you have a branch that has that work? Also, to be clear: I probably don't have the skills or time to upgrade Sage by myself, I was hoping that if we shared our knowledge and de-duplicated efforts we might be able to get closer together
I think it was 6-dot-something; it required a metric ton of adding options to the packages in NixPkgs (I have pushed that all to master long ago), and the Sage tricks are most likely too version-specific. It was long enough ago that I have since abandoned and lost the changes.
In case anybody in here is still waiting for this: I got sage to compile and run. I'm currently trying to minimize the dependencies and check that everything is working correctly (there is one doctest failure, but it was mentioned multiple times in the mailing list and apperas to be harmles -- just a timeout). I'll probably make a PR in the next couple of days.


Question: ThomasMader = "Thomas Mader <thomas.mader@gmail.com>"; thoughtpolice = "Austin Seipp <aseipp@pobox.com>"; timbertson = "Tim Cuthbertson <tim@gfxmonk.net>"; <ins> timokau = "Timo Kaufmann <timokau@zoho.com>"; </ins> titanous = "Jonathan Rudenberg <jonathan@titanous.com>"; tnias = "Philipp Bartsch <phil@grmr.de>"; tohl = "Tomas Hlavaty <tom@logand.com>";

Sage needs texlive-core-2014, which is deprecated. Run with modern nixpkgs (i.e. from git) System: NixOS: (Flounder) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version:


Question: }; url_preview_url_blacklist = mkOption { type = types.listOf types.str; <del> default = [ "127.0.0.0/8" "10.0.0.0/8" "172.16.0.0/12" "192.168.0.0/16" "100.64.0.0/10" "169.254.0.0/16" ]; </del> <ins> default = []; </ins> description = '' Optional list of URL matches that the URL preview spider is denied from accessing.


Question: patches = [ (substituteAll { src = ./libpq.patch; <del> libpq = "${postgresql.lib}/lib/libpq.so"; </del> <ins> libpq = "${postgresql.lib}/lib/libpq${stdenv.hostPlatform.extensions.sharedLibrary}"; </ins> }) ];

Steps to reproduce the behavior: -env -iA (full output here: ) 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.
The error is not in pgcli but in psycopg which tries to import a .so which does not work under darwin.


Question: <del> { lib, stdenv, fetchurl, unzip, blas, lapack, gfortran }: </del> <ins> { lib , stdenv , fetchFromGitHub , pkg-config , blas , lapack , gfortran , enableAMPL ? stdenv.isLinux, libamplsolver }: </ins> assert (!blas.isILP64) && (!lapack.isILP64); stdenv.mkDerivation rec { pname = "ipopt"; <del> version = "3.12.13"; </del> <ins> version = "3.14.5"; </ins> <del> src = fetchurl { url = "https://www.coin-or.org/download/source/Ipopt/Ipopt-${version}.zip"; sha256 = "0kzf05aypx8q5mr3sciclk926ans0yi2d2chjdxxgpi3sza609dx"; </del> <ins> src = fetchFromGitHub { owner = "coin-or"; repo = "Ipopt"; rev = "releases/${version}"; sha256 = "sha256-eqOacZGuuGAjWMs2H6RntQ+WJmGTi+EqydHUQXEpY54="; </ins> }; CXXDEFS = [ "-DHAVE_RAND" "-DHAVE_CSTRING" "-DHAVE_CSTDIO" ]; configureFlags = [ <del> "--with-blas-lib=-lblas" "--with-lapack-lib=-llapack" </del> <ins> "--with-asl-cflags=-I${libamplsolver}/include" "--with-asl-lflags=-lamplsolver" </ins> ]; <del> nativeBuildInputs = [ unzip gfortran ]; buildInputs = [ blas lapack ]; </del> <ins> nativeBuildInputs = [ pkg-config gfortran ]; buildInputs = [ blas lapack ] ++ lib.optionals enableAMPL [ libamplsolver ]; </ins> enableParallelBuilding = true;

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


Question: "-DENABLE_TESTING=${enableIf doCheck}" "-DDISABLE_META_INTEGRATION_TESTS=ON" "-DTRAVIS_DISABLE_META_CPP=ON" <del> "-DPythonModular=${enableIf pythonSupport}" </del> <ins> "-DINTERFACE_PYTHON=${enableIf pythonSupport}" </ins> "-DOpenCV=${enableIf opencvSupport}" "-DUSE_SVMLIGHT=${enableIf withSvmLight}" ];

Using Shogun as a for another CMake-based project fails because the dependent project cannot properly find the shogun library (via its installed cmake files). Steps to reproduce the behavior: to build a derivation based on shogun files are wrong Everything builds correctly I am trying to build the following derivation However I get an error at the build generation step: This indicates that shogun CMake files are not in the right place and/or are pointing towards the wrong paths.
I fixed the issue with shogun. When installing the configuration files, CMake calculates the prefix to the installed library based on the output directory, instead of the default , and I missed it when I split the derivation into multiple outputs. I wonder why it's not a more widespread issue, only a few derivations patch it. But that derivation still doesn't build: This is in macOS, though. Maybe it works on Linux.
Thanks, is the fix committed yet? The other error is unrelated and I can fix it.
I'm working on the PR.


Question: stdenv.mkDerivation rec { pname = "clojure"; <del> version = "1.10.3.855"; </del> <ins> version = "1.10.3.933"; </ins> src = fetchurl { # https://clojure.org/releases/tools url = "https://download.clojure.org/install/clojure-tools-${version}.tar.gz"; <del> sha256 = "sha256-y2PuOBRq5kZlTpPV8NwkWhspQKlNxwjl+k/Drwixk4Q="; </del> <ins> sha256 = "sha256-xsm0/HNWr8a/7iLQVC9TbUkASWvw/EI3bD0dMDhLZXA="; </ins> }; nativeBuildInputs = [

<!-- 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 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: clojure <!-- The current version can be found easily with the same process than 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: 1.10.3.855 desired version: 1.10.3.933 <!-- 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.
Opened a PR:


Question: sourceRoot = "pyside-setup-everywhere-src-${version}/sources/${pname}"; <del> patches = [ ./fix-include-qt-headers.patch ]; </del> <ins> patches = [ ./fix-include-qt-headers.patch # Remove this patch when updating to 6.8.0 (fetchpatch { name = "backwards-compatibility-with-6.6.x.patch"; url = "https://code.qt.io/cgit/pyside/pyside-setup.git/patch/?id=4f9a20e3635f4f0957e0774588b1d9156e88a572"; hash = "sha256-B2jhLWopgaSF/rUXMZFPZArDUNojlBgn7kdVyQull+I="; stripLen = 2; }) ]; </ins> nativeBuildInputs = [ cmake

Steps to reproduce the behavior: cutter Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Any news on this?


Question: <ins> commit 1b0d9bcc5f5cd78b0bb1357d6a11da5d616ad26f Author: Wout Mertens <Wout.Mertens@gmail.com> Date:   Thu Jun 11 18:08:13 2020 +0200 fix segfault when using ECDSA keys. Author: Marc Deslauriers <marc.deslauriers@canonical.com> Bug-Ubuntu: https://bugs.launchpad.net/bugs/1869512 diff --git a/ssh-ecdsa.c b/ssh-ecdsa.c index 5b13b30..5bf29cc 100644 --- a/ssh-ecdsa.c +++ b/ssh-ecdsa.c @@ -46,7 +46,7 @@ ssh_ecdsa_sign(const Key *key, u_char **sigp, u_int *lenp, u_int len, dlen; Buffer b, bb; #if OPENSSL_VERSION_NUMBER >= 0x10100005L -	BIGNUM *r, *s; +	BIGNUM *r = NULL, *s = NULL; #endif if (key == NULL || key->type != KEY_ECDSA || key->ecdsa == NULL) { @@ -137,20 +137,27 @@ ssh_ecdsa_verify(const Key *key, const u_char *signature, u_int signaturelen, /* parse signature */ if ((sig = ECDSA_SIG_new()) == NULL) -        pamsshagentauth_fatal("ssh_ecdsa_verify: DSA_SIG_new failed"); +        pamsshagentauth_fatal("ssh_ecdsa_verify: ECDSA_SIG_new failed"); pamsshagentauth_buffer_init(&b); pamsshagentauth_buffer_append(&b, sigblob, len); #if OPENSSL_VERSION_NUMBER < 0x10100005L if ((pamsshagentauth_buffer_get_bignum2_ret(&b, sig->r) == -1) || (pamsshagentauth_buffer_get_bignum2_ret(&b, sig->s) == -1)) +        pamsshagentauth_fatal("ssh_ecdsa_verify:" +            "pamsshagentauth_buffer_get_bignum2_ret failed"); #else -    DSA_SIG_get0(sig, &r, &s); +    if ((r = BN_new()) == NULL) +        pamsshagentauth_fatal("ssh_ecdsa_verify: BN_new failed"); +    if ((s = BN_new()) == NULL) +        pamsshagentauth_fatal("ssh_ecdsa_verify: BN_new failed"); if ((pamsshagentauth_buffer_get_bignum2_ret(&b, r) == -1) || (pamsshagentauth_buffer_get_bignum2_ret(&b, s) == -1)) -#endif pamsshagentauth_fatal("ssh_ecdsa_verify:" "pamsshagentauth_buffer_get_bignum2_ret failed"); +    if (ECDSA_SIG_set0(sig, r, s) != 1) +        pamsshagentauth_fatal("ssh_ecdsa_verify: ECDSA_SIG_set0 failed"); +#endif /* clean up */ memset(sigblob, 0, len); </ins>

Describe the bug After upgrading to NixOS 20.03, sudo often (but not always) segfaults: From the logs: Disabling appears to have made this problem to away, so the problem may be in . Metadata NixOS 20.03..
Maybe the patch to use a not insecure openssl is the source of the issue for you
same issue here - the sourceforge repo is way old, there's a github mirror but not maintained either, and there's a fork of the mirror which includes fixes for openssl 1.1.1:
I marked this as stale due to inactivity. →
Hmm, kinda forgot about this
I missed the fact that the "supported" branch didn't actually include the patch to fix this.


Question: denonavr = callPackage ../development/python-modules/denonavr { }; <ins> dep-logic = callPackage ../development/python-modules/dep-logic { }; </ins> dependency-injector = callPackage ../development/python-modules/dependency-injector { }; deploykit = callPackage ../development/python-modules/deploykit { };

Steps to reproduce the behavior: truststore Output of : Adding to solves this issue. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: , nodePackages, bash # Attributes inherit from specific versions <del> , version, src, meta, sourceRoot </del> <ins> , version, src, meta, sourceRoot, commandLineArgs </ins> , executableName, longName, shortName, pname, updateScript # sourceExecutableName is the name of the binary in the source archive, over # which we have no control

For Chromium, there's a convenient way to define custom flags through . However, there doesn't seem to be a similar option for . I tried setting to "--touch-events", but touchscreen scrolling is not enabled when starting VSCode from desktop launcher, while running in console works as expected. Steps to reproduce the behavior: to "--touch-events" VSCode from desktop launcher on the editor area through touchscreen The editor should scroll as I drag. system: host os: multi-user?: sandbox: version: channels(yes): channels(root): nixpkgs:


Question: gotypist = callPackage ../games/gotypist { }; <del> heroic-unwrapped = callPackage ../games/heroic { }; </del> <ins> heroic-unwrapped = callPackage ../games/heroic { # Match the version used by the upstream package. electron = electron_24; }; </ins> heroic = callPackage ../games/heroic/fhsenv.nix { };

Upon launching,  white screens without any visible errors. or the app white screen It works without white screening Since runs fine when using its pre-built AppImage, I don't suspect that there is any issue with my hardware, drivers, or software. After testing, I have found out that the issue exists on specifically. It works fine on KDE. (Note: I haven't tried on similar environments like Sway) Running produces the following output upon exiting : Hello,
I am thinking of adding a package so that any user facing this or similar issues can use pre-built binaries as a instant solution than waiting for existing nix expressions to be fixed. Please guide me if you guys think this should/can be done. (The NixOS manual doesn't provide much help with wrappers around AppImages)
Could you please run in a terminal (in the environment where the issue occurs) and paste the output in a comment, in a . I also have a few questions, you get those same errors when you run from the terminal? this X11 KDE, or Wayland KDE? is your GPU, and which drivers are you using? I don't think we should do this. If a user wants to run pre-built binaries from upstream, there are straightforward ways to do so. Since Heroic ships an AppImage, you can use .
I've already tried running heroic from a terminal and weirdly, there's absolutely no error that shows up. Which makes me think it's a purely front-end error given heroic uses electron. , I do. KDE . My driver setup is contained in Yeah, that makes sense. But how do I make sure it's always installed on my system? Do I have to run every single time I need to launch?
Update: I have tested this in Sway as well and the app does white screen with no errors in the terminal.
Try running Heroic from the branch I just pushed (command below) to see if it resolves the issue. I've changed the Electron version the package uses to match that of the upstream package, as there seems to be a regression in the latest version of Electron.
Just tested this. I don't get the white screen anymore!!
This happens for me now, trying the nix shell now.
That fixed it, thanks!


Question: homepage = https://postgis.net/; license = licenses.gpl2; maintainers = [ maintainers.marcweber ]; <del> platforms = platforms.linux; </del> <ins> inherit (postgresql.meta) platforms; </ins> }; }

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


Question: ./fix-122159.patch # https://github.com/NixOS/nixpkgs/issues/122159 ]; <ins> # Note: xposix is renamed to posix in v5. postPatch = lib.optionalString stdenv.isLinux '' substituteInPlace xpra/platform/xposix/features.py  --replace-fail "/usr/bin/xdg-open" "${xdg-utils}/bin/xdg-open" ''; </ins> INCLUDE_DIRS = "${pam}/include"; nativeBuildInputs = [

Xpra supports forwarding invocations from the server to the client. The Xpra client defaults to hardcoding as the command to invoke on the client, which does not exist in NixOS. This bug does not impact hosts other than NixOS. Steps to reproduce the behavior: somehow. The Xpra client should invoke the local . N/A. This could be fixed by setting the open command to just , but it might match the intent better to change it to something like perhaps. Presumably, the point of doing it this way is to avoid any other copies of that might appear on the , e.g. Xpra's own. I suppose we can't really rely on to exist: even if we could on NixOS, we can't on other Linux distributions running Nix, where might make more sense. It seems to me that the best compromise, then, is to hardcode a path to copy of and users can override this using the option if needed. The open command that Xpra uses is configurable on the client-side, but the default is set as a platform-specific variable. On Linux, it is set in . Because there are separate values for both Windows and Darwin hosts, patching the value to shouldn't ever break them (but of course it should still be a Linux-specific patch, otherwise it unnecessarily brings into the closure.) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: <ins> diff --git a/dolphin/mat2.desktop b/dolphin/mat2.desktop index e623962..5d69ae2 100644 --- a/dolphin/mat2.desktop +++ b/dolphin/mat2.desktop @@ -7,5 +7,5 @@ Type=Service [Desktop Action cleanMetadata] Name=Clean metadata Name[es]=Limpiar metadatos -Icon=/usr/share/icons/hicolor/scalable/apps/mat2.svg -Exec=kdialog --yesno  "$( mat2 -s %U )" --title "Clean Metadata?" && mat2 %U +Icon=@mat2svg@ +Exec=@kdialog@ --yesno  "$( @mat2@ -s %U )" --title "Clean Metadata?" && @mat2@ %U diff --git a/libmat2/bubblewrap.py b/libmat2/bubblewrap.py index 970d5dd..5d3c0b7 100644 --- a/libmat2/bubblewrap.py +++ b/libmat2/bubblewrap.py @@ -22,11 +22,7 @@ CalledProcessError = subprocess.CalledProcessError def _get_bwrap_path() -> str: -    which_path = shutil.which('bwrap') -    if which_path: -        return which_path - -    raise RuntimeError("Unable to find bwrap")  # pragma: no cover +    return '@bwrap@' def _get_bwrap_args(tempdir: str, @@ -37,16 +33,11 @@ def _get_bwrap_args(tempdir: str, # XXX: use --ro-bind-try once all supported platforms # have a bubblewrap recent enough to support it. -    ro_bind_dirs = ['/usr', '/lib', '/lib64', '/bin', '/sbin', '/etc/alternatives', cwd] +    ro_bind_dirs = ['/nix/store', cwd] for bind_dir in ro_bind_dirs: if os.path.isdir(bind_dir):  # pragma: no cover ro_bind_args.extend(['--ro-bind', bind_dir, bind_dir]) -    ro_bind_files = ['/etc/ld.so.cache'] -    for bind_file in ro_bind_files: -        if os.path.isfile(bind_file):  # pragma: no cover -            ro_bind_args.extend(['--ro-bind', bind_file, bind_file]) - args = ro_bind_args +  ['--dev', '/dev', '--proc', '/proc', diff --git a/libmat2/exiftool.py b/libmat2/exiftool.py index eb65b2a..51a0fa1 100644 --- a/libmat2/exiftool.py +++ b/libmat2/exiftool.py @@ -1,8 +1,6 @@ -import functools import json import logging import os -import shutil import subprocess from typing import Dict, Union, Set @@ -70,14 +68,5 @@ class ExiftoolParser(abstract.AbstractParser): return False return True -@functools.lru_cache() def _get_exiftool_path() -> str:  # pragma: no cover -    which_path = shutil.which('exiftool') -    if which_path: -        return which_path - -    # Exiftool on Arch Linux has a weird path -    if os.access('/usr/bin/vendor_perl/exiftool', os.X_OK): -        return '/usr/bin/vendor_perl/exiftool' - -    raise RuntimeError("Unable to find exiftool") +    return '@exiftool@' diff --git a/libmat2/parser_factory.py b/libmat2/parser_factory.py index 9965432..bd45179 100644 --- a/libmat2/parser_factory.py +++ b/libmat2/parser_factory.py @@ -8,6 +8,7 @@ from . import abstract, UNSUPPORTED_EXTENSIONS T = TypeVar('T', bound='abstract.AbstractParser') +mimetypes.init(['@mimetypes@']) mimetypes.add_type('application/epub+zip', '.epub') mimetypes.add_type('application/x-dtbncx+xml', '.ncx')  # EPUB Navigation Control XML File diff --git a/libmat2/video.py b/libmat2/video.py index b4a3232..3dd7ee5 100644 --- a/libmat2/video.py +++ b/libmat2/video.py @@ -1,6 +1,4 @@ import subprocess -import functools -import shutil import logging from typing import Dict, Union @@ -135,10 +133,5 @@ class MP4Parser(AbstractFFmpegParser): } -@functools.lru_cache() def _get_ffmpeg_path() -> str:  # pragma: no cover -    which_path = shutil.which('ffmpeg') -    if which_path: -        return which_path - -    raise RuntimeError("Unable to find ffmpeg") +    return '@ffmpeg@' </ins>

Project description Metadata proposed package name: homepage source URL: license: platforms: probably portable to all platforms which Nix supports. requires python3, exiftool, gobject introspection


Question: let pname = "osu-lazer-bin"; <del> version = "2024.312.0"; </del> <ins> version = "2024.312.1"; </ins> src = { aarch64-darwin = fetchzip { url = "https://github.com/ppy/osu/releases/download/${version}/osu.app.Apple.Silicon.zip"; <del> hash = "sha256-RwOSB/WcAqR8j0xw1QUji1IEn7iHXcHj2xOcKjnpl00="; </del> <ins> hash = "sha256-1MsZ9gHTZKArXk1b6XEBNk/ZWAUHKjbVrrn++dLulaQ="; </ins> stripRoot = false; }; x86_64-darwin = fetchzip { url = "https://github.com/ppy/osu/releases/download/${version}/osu.app.Intel.zip"; <del> hash = "sha256-Wnr7CtQIfugKrGsl72NXdHJIsF7rRNhzjV1Q+gRHK10="; </del> <ins> hash = "sha256-Xgl8lrMsL9O9YHbEx3Iwwh9fpLOnYZN0Kt28F5X5OwE="; </ins> stripRoot = false; }; x86_64-linux = fetchurl { url = "https://github.com/ppy/osu/releases/download/${version}/osu.AppImage"; <del> hash = "sha256-kWNobQXGGS2TWvPkhfheqnlbijfnxfcP36ANUeN6bW0="; </del> <ins> hash = "sha256-1dzgs1p3/pf4eCdKvQ9JxowN+oBPBNaZv5e6qHeFPEM="; </ins> }; }.${stdenv.system} or (throw "${pname}-${version}: ${stdenv.system} is unsupported.");

Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: <del> { stdenv, lib, fetchFromGitHub, kernel, writeScript, coreutils, gnugrep, jq, curl, common-updater-scripts, runtimeShell </del> <ins> { stdenv , lib , fetchFromGitHub , fetchpatch , kernel , writeScript , coreutils , gnugrep , jq , curl , common-updater-scripts , runtimeShell </ins> }: stdenv.mkDerivation rec {

Steps to reproduce the behavior: on old thinkpad Device: Thinkpad X220 <!-- 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.
greetings ! are you able to test ? an other workaround is to stick to < 6.4 kernel
for now I can't test your commit since I'm newbie and asking you to teach me would take a lot of your time Gonna stick to < 6.4 kernel and try to test commit in free time
appreciate your concerns! from looking at your setup you seem to know fair bit already, and I dont mind spending some time for as long we all learn something useful you should be able to test that PR by changing in your flake to edit: also no rush to test this
Well that was actually easy to test! PR works! I thought I need to use overlays to test it and I have zero experience with them for now.


Question: , newuidmapPath ? null # Path to SUID-ed newgidmap executable , newgidmapPath ? null <ins> # External LOCALSTATEDIR , externalLocalStateDir ? null </ins> # Remove the symlinks to `singularity*` when projectName != "singularity" , removeCompat ? false # Workaround #86349

The derivation is missing the directory to work properly. Steps to reproduce the behavior: A clear and concise description of what you expected to happen. is output without error. This can be fixed by creating the directory manually (). I guess this could be to the derivation. <!-- 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.
NixOS module provides those top-level directories. discussed with one of the main Apptainer developer in . He think it should be easy to specify a directory that will always exist at build time. Regalding this, I'm considering the possibility to put those dilectories under the derivation store path. Not sure if there would be potential problem using a store path as a mount point, but it seems to work without problem.
Could you help me take a look at ?
If you have time, please help me test the PR . It should fundamentally solve this issue. If applied, you no longer need the NixOS module or just to run images. It specifies the LOCALSTATEDIR as , making both Apptainer and Sylabs SingularityCE works without . (The image running still depends on and to run images, which might be the final obstacle to build images as a package without invoking a virtual machine. Other than that, it should not be an issue for most users, as are available on most of the UNIX/UNIX-like systems.)
I removed (the temporary fix for this issue) and ran the following and it seems to work fine: Thank you for this fix!
Glad to hear that! Would you mind ? I've heard that committers tend to merge PRs getting two approvals.
Done!


Question: checkInputs = [ sphinx numpydoc pytest ]; propagatedBuildInputs = [ python-lz4 ]; <del> # test_disk_used is broken # https://github.com/joblib/joblib/issues/57 </del> <ins> # test_disk_used is broken: https://github.com/joblib/joblib/issues/57 # test_dispatch_multiprocessing is broken only on Darwin. </ins> checkPhase = '' <del> py.test joblib -k "not test_disk_used" </del> <ins> py.test -k 'not test_disk_used${lib.optionalString (stdenv.isDarwin) " and not test_dispatch_multiprocessing"}' joblib/test </ins> ''; meta = {

Describe the bug fails on Darwin. To Reproduce Steps to reproduce the behavior: Expected behavior Package builds Additional context Error log: <details<summaryError log</summary</detailsMetadata Please run and paste the result. host os: multi-user?: sandbox: version: channels(yl): nixpkgs: Maintainer information: Possibly related to
On the master branch, I removed the derivation from the nix store with and I built it without substitutes; failed with the same message. This is not caused by , but help me discover it due to the update of the requests python package.
maintainer:
I don't have a way to test on joblib for darwin so this is why I didn't have input on this PR. Is there an easy way to test nixpkgs on darwin? Hackintosh via kvm?
There is that works with some tweaking but I wouldn't describe it as easy. Another option is to ask @ GrahamcOfBorg to do the builds on the PR if there are not too many iterations to do.


Question: <del> { pkgs, buildPackages, lib, gawk, gnused, gixy }: </del> <ins> { pkgs, buildPackages, lib, stdenv, libiconv, gawk, gnused, gixy }: </ins> with lib; rec {

Describe the bug results in the following error on : Seems like the writer expects to be executed in a stdenv environment to find instead of knowing the path to it. To Reproduce Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (rust maintainers)
This should work as long as GHC is proper dep, because libiconv is propagated.
This should be independent of GHC entirely: only relation to GHC is probably that I mistook the error for one coming from GHC initially, but this is not the case ( doesn't allow building the writers individually what confused me).
I'm facing this issue trying to build from on macOS Big Sur. (wasmer is a dependency of FastAPI, which is the package I'm actually interested in) <details<summaryLogs:</summary</details
I think adding to could also help there.
Fix here:


Question: # and often with different versions.  We write them on three lines # like this (rather than using {}) so that the updater script can # find where to edit them. <del> versions.aarch64-darwin = "5.14.10.19202"; versions.x86_64-darwin = "5.14.10.19202"; versions.x86_64-linux = "5.15.0.4063"; </del> <ins> versions.aarch64-darwin = "5.15.2.19786"; versions.x86_64-darwin = "5.15.2.19786"; versions.x86_64-linux = "5.15.2.4260"; </ins> srcs = { aarch64-darwin = fetchurl { url = "https://zoom.us/client/${versions.aarch64-darwin}/zoomusInstallerFull.pkg?archType=arm64"; name = "zoomusInstallerFull.pkg"; <del> hash = "sha256-MK6xUkS+nX7SjIieduMhhFNqEUVdc89aPiCvHI2pjDQ="; </del> <ins> hash = "sha256-vERhyaNVxam6ypi9nU2t6RfBZgtzD6YECkSrxkxl/4E="; </ins> }; x86_64-darwin = fetchurl { url = "https://zoom.us/client/${versions.x86_64-darwin}/zoomusInstallerFull.pkg"; <del> hash = "sha256-JJ6nZ8WnTF8X8R0gIlFtsTbpdHhv65J5kWts+H3QDoM="; </del> <ins> hash = "sha256-Yx5seUks6s+NEBIxgltUQiNU3tjWpmNKMJwgAj9izh4="; </ins> }; x86_64-linux = fetchurl { url = "https://zoom.us/client/${versions.x86_64-linux}/zoom_x86_64.pkg.tar.xz"; <del> hash = "sha256-DhP6LZt/G3K9YDs7iXABsJMuhpzITP4aJ0PWXrFAL3I="; </del> <ins> hash = "sha256-R6M180Gcqu4yZC+CtWnixSkjPe8CvgoTPWSz7B6ZAlE="; </ins> }; };

Package name: zoom-us Latest released version: 5.15.2.4260 <!-- Search your package here: --- Current version on the unstable channel: 5.15.0.4063 Current version on the stable/release channel: 5.14.7.2928 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.


Question: if [ -z "$newHash" ]; then nix-build --no-out-link -A "$attr.src" 2>"$attr.fetchlog" >/dev/null || true # FIXME: use nix-build --hash here once https://github.com/NixOS/nix/issues/1172 is fixed <del> newHash=$(egrep -v "killing process|dependencies couldn't be built" "$attr.fetchlog" | tail -n2 | sed "s~output path .* has .* hash ‘(.*)’ when .* was expected|fixed-output derivation produced path '.*' with .* hash '(.*)' instead of the expected hash '.*'~12~" | head -n1) </del> <ins> newHash=$(egrep -v "killing process|dependencies couldn't be built|wanted: " "$attr.fetchlog" | tail -n2 | sed "s~output path .* has .* hash ‘(.*)’ when .* was expected|fixed-output derivation produced path '.*' with .* hash '(.*)' instead of the expected hash '.*'|  got:    .*:(.*)~123~" | head -n1) </ins> fi if [ -z "$newHash" ]; then

When used with latest Nix the "new" hash is extracted incorrectly, or thereabouts. This seems to be due to Nix changing the message used to be more friendly to humans: Use an update script invoking common-updater-scripts. Sorry, LMK if repro is needed. Please run and paste the results. I don't expect this to be helpful but happy to provide anyway! system: host os: multi-user?: sandbox: version: channels(will): channels(root): nixpkgs:
It is increasingly messy, perhaps we can drop the old regexes, most people probably set instead of changing nix in overlays so this would not be affected.
What about adding a flag to nix, which turns on machine readable error messages with a guaranty that those messages will not change in a backward incompatible way? Would need someone to add that. But wouldn't that be better to parse error messages intended for human readers with shell tools?
Alternatively, if the build fails, I think we could do something like:
I'm not sure I follow, but FWIW I ran into this and I set and don't set it via overlay. Looks like the new behavior is in 2.2, the current default for : (err formatting might not work for email responses, maybe? sorry :)) I think it's reasonable to drop support for nix older than what's in the tree-- especially since you'd have to overlay to replace it and as you say would likely do via anyway. Oh... that's probably what you meant! :D
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
Any updates on this?
I marked this as stale due to inactivity. →
Should have been fixed by
Thanks!