Question: libevent zlib pcre <ins> libb64 libutp miniupnpc dht libnatpmp </ins> ] ++ lib.optionals enableQt [ qt5.qttools qt5.qtbase ] ++ lib.optionals enableGTK3 [ gtk3 xorg.libpthreadstubs ]

Project description Fragments is a modern, responsive and graphical Gnome bittorrent client Metadata homepage URL: source URL: license: gpl3 platforms: linux The new version of Fragments depends on libutp which hopefully gets merged soon. I've opened a pull request for it . for Fragments.
We have transmission and torrential. Maybe that's something for you.
That's true but Fragments is a really neat, easy and modern looking torrent client. It has an adaptive interface which would also work quite well on mobile devices, for example NixOS mobile :+1:


Question: <del> { lib, stdenv, fetchFromGitHub, buildLinux, ... } @ args: </del> <ins> { lib, stdenv, fetchFromGitHub, buildLinux, variant, ... } @ args: </ins> let # These names are how they are designated in https://xanmod.org. # NOTE: When updating these, please also take a look at the changes done to # kernel config in the xanmod version commit <del> ltsVariant = { version = "6.6.46"; hash = "sha256-ZtXFIHRM5YCb+5Ry3zcQt44OBqfhCI/Ig32jETUBrJo="; variant = "lts"; }; mainVariant = { version = "6.10.5"; hash = "sha256-tETGtCNNgYj1IUNuI/Am5kimFndUC4O+cZwZzlPitFA="; variant = "main"; </del> <ins> variants = { lts = { version = "6.6.46"; hash = "sha256-ZtXFIHRM5YCb+5Ry3zcQt44OBqfhCI/Ig32jETUBrJo="; }; main = { version = "6.10.5"; hash = "sha256-tETGtCNNgYj1IUNuI/Am5kimFndUC4O+cZwZzlPitFA="; }; </ins> }; <del> xanmodKernelFor = { version, suffix ? "xanmod1", hash, variant }: buildLinux (args // rec { </del> <ins> xanmodKernelFor = { version, suffix ? "xanmod1", hash }: buildLinux (args // rec { </ins> inherit version; pname = "linux-xanmod"; modDirVersion = lib.versions.pad 3 "${version}-${suffix}";

Mainline / hardened / testing / ... kernels can be painlessly modified via : Sadly, this does not work with a bunch of other kernel variants: All kernels should honor I am not entirely sure how dynamic binding is implemented in kernel stuff, however slightly changing xanmod parts this way seems to fix : zen and lqx look similar to xanmod, no idea about libre Pinging people who seem to update affected packages often Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
same underlying issue as it seems
Can confirm that this patch fix the issue for zen and lqx kernels:
have you submitted these changes as a PR that I can review?
sorry for the late response. I created a new PR with this changes.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:


Question: enableFeatures = optionals enableVideoAcceleration [ "VaapiVideoDecoder" "VaapiVideoEncoder" ] ++ optional enableVulkan "Vulkan"; <ins> disableFeatures = [ "OutdatedBuildDetector" ] # disable automatic updates </ins> # The feature disable is needed for VAAPI to work correctly: https://github.com/brave/brave-browser/issues/20935 <del> disableFeatures = optional enableVideoAcceleration "UseChromeOSDirectVideoDecoder"; </del> <ins> ++ optionals enableVideoAcceleration  [ "UseChromeOSDirectVideoDecoder" ]; </ins> in stdenv.mkDerivation rec {

Brave browser keeps reporting a failed autoupdate. ! It should be possible to avoid it just adding a CLI option in the entry: install the package open "Brave Web Browser" from the Gnome applications menu click the menu button (it is displaying an alert even before clicking) Please run and paste the result.
Btw, this is much less relevant, but all icons are missing from the package.
The icons are there. They are symlinks to the directory.
Indeed, I realized right after writing it, but then forgot to update: I thought I was two directories upper in the hierarchy (I could have realized, simply noticing it was missing ...). My bad.
I was checking out the above PR, but I cant seem to recreate the issue. right now I've got brave 1.62.162, and the latest version available online is 1.62.165. It doesn't seem to be checking for updates. Is there a trick to getting it to check, or is it just sorta auto-updating for you?
Exploring Brave issues, like the one linked above, apparently the auto-update is a Chromium feature, even not so easy to mask for the Brave crew. However, within Nix, Brave is prevented to auto-update, so that's not an issue on its own. But it's attempting to, and just reporting the failure. So, no trick. I will soon check the version and report, but in case it helps, I'm using through a flake: and installing through NixOS:
Yeah, that's what I mean, it doesn't even appear to be trying to update when I try it.
Since I provided the whole flake (and I'm also not doing anything other than requesting the package), I'm not sure what else can I do to improve reproducibility. In case, I could provide further screenshots. But the one above is essentially the issue on its own.
Recreated with the flake :+1:
Do you understand why is it showing up with the flake and not without?
Didn't bother figuring it out. Figuring it's probably just that my version wasn't out-of-date enough.


Question: sipp = callPackage ../development/tools/misc/sipp { }; <ins> skanpage = libsForQt5.callPackage ../applications/graphics/skanpage { }; </ins> soci = callPackage ../development/libraries/soci { }; socialscan = with python3.pkgs; toPythonApplication socialscan;

Project description Skanpage is a simple no-frills scanner KDE application that is a bit more comprehensive than skanlite. Most importantly, it has multi page support, that skanlite is painfully lacking. cc Metadata homepage URL: source URL: license: gpl2+ platforms: KDE


Question: libsoup glib-networking graphicsmagick_q16 <ins> hiredis libusb libva </ins> ]; unpackPhase = ''

Package name: aws-workspaces Latest released version: 4.5.0 <!-- Search your package here: --- Current version on the unstable channel: 4.1.0.1523 Current version on the stable/release channel: 4.1.0.1523 <!-- 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: stdenv.mkDerivation rec { pname = "git-open"; <del> version = "2.1.0"; </del> <ins> version = "3.0.0"; </ins> src = fetchFromGitHub { owner = "paulirish"; repo = "git-open"; rev = "v${version}"; <del> sha256 = "11n46bngvca5wbdbfcxzjhjbfdbad7sgf7h9gf956cb1q8swsdm0"; </del> <ins> sha256 = "sha256-Bag2rI2uR7ilkg2ozjR8tPXqKz5XjiY7WAUJKTVTXd8="; </ins> }; nativeBuildInputs = [ installShellFiles makeWrapper pandoc ];

Package name: git-open Latest released version: 3.0.0 <!-- Search your package here: --- Current version on the unstable channel: 2.1.0 Current version on the stable/release channel: 2.1.0 <!-- 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.
The latest version of listed on the project's is (Dec 3, 2018), however was released on the project's (Jul 18, 2022).


Question: ] ++ lib.optional bluetoothSupport bluez5 # for bluetooth configuration and control ++ lib.optional pulseSupport libpulseaudio # for proper audio device control and redirection <ins> ++ lib.optionals waylandSupport [ wayland-protocols xwayland ] </ins> ; patches = [

I'm trying out NixOS 19.09 and notice that Enlightenment is still being built under X. Enlightenment 23.0 have some highlight. One of them being "Massive improvements to Wayland support".
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 .
It would be nice to hear about the recent progress.


Question: ''; }; <del> executable = writeShellScriptBin "gnome-flashback-${wmName}" '' if [ -z $XDG_CURRENT_DESKTOP ]; then export XDG_CURRENT_DESKTOP="GNOME-Flashback:GNOME" fi export XDG_DATA_DIRS=${wmApplication}/share:${gnomeSession}/share:${gnome-flashback}/share:${gnome-panel}/share:$XDG_DATA_DIRS </del> <ins> # gnome-panel will only look for applets in a single directory so symlink them into here. panelModulesEnv = buildEnv { name = "gnome-panel-modules-env"; # We always want to find the built-in panel applets. paths = [ gnome-panel gnome-flashback ] ++ panelModulePackages; pathsToLink = [ "/lib/gnome-panel/modules" ]; }; </ins> <del> exec ${gnome-session}/bin/gnome-session --session=gnome-flashback-${wmName} "$@" ''; </del> <ins> executable = stdenv.mkDerivation { name = "gnome-flashback-${wmName}"; nativeBuildInputs = [ glib wrapGAppsHook ]; buildInputs = [ gnome-flashback ] ++ lib.optionals enableGnomePanel ([ gnome-panel ] ++ panelModulePackages); # We want to use the wrapGAppsHook mechanism to wrap gnome-session # with the environment that gnome-flashback and gnome-panel need to # run, including the configured applet packages. This is only possible # in the fixup phase, so turn everything else off. dontUnpack = true; dontConfigure = true; dontBuild = true; dontInstall = true; dontWrapGApps = true; # We want to do the wrapping ourselves. # gnome-flashback and gnome-panel need to be added to XDG_DATA_DIRS so that their .desktop files can be found by gnome-session. preFixup = '' makeWrapper ${gnome-session}/bin/gnome-session $out  --add-flags "--session=gnome-flashback-${wmName}"  --set-default XDG_CURRENT_DESKTOP 'GNOME-Flashback:GNOME'  --prefix XDG_DATA_DIRS : '${lib.makeSearchPath "share" ([ wmApplication gnomeSession gnome-flashback ] ++ lib.optional enableGnomePanel gnome-panel)}'  "''${gappsWrapperArgs[@]}"  ${lib.optionalString enableGnomePanel "--set NIX_GNOME_PANEL_MODULESDIR '${panelModulesEnv}/lib/gnome-panel/modules'"} ''; }; </ins> in writeTextFile

Panel applets are being picked up from environment variable in and a completely hardcoded path in . First, we will need to patch the latter manager to use an environment variable as well. Second, we will need to do something similar to what . Or better, create  derivation. Originally posted by in
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 .
I'd like to tackle this, do you have any pointers? We need to get it to pick up at least right?


Question: # If one wishes to use a different src or name for a very custom build , overrideSrc ? {} , pname ? "gnuradio" <del> , version ? "3.10.7.0" </del> <ins> , version ? "3.10.8.0" </ins> }: let <del> sourceSha256 = "sha256-7fIQMcx90wI4mAZmR26/rkBKPKhNxgu3oWpJTV3C+Ek="; </del> <ins> sourceSha256 = "sha256-4BoJciL3ffd9Dgk3HxXCOOwnGHqCEVuo+a1AtzJG4IY="; </ins> featuresInfo = { # Needed always basic = {

Package name: gnuradio Latest released version: 3.10.8.0 <!-- Search your package here: --- Current version on the unstable channel: 3.10.7.0 Current version on the stable/release channel:3.10.7.0 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]:
Tnx. Update is proposed at


Question: inherit (pkgs) alsaUtils; <ins> pulseaudioEnabled = config.hardware.pulseaudio.enable; </ins> in {

Setting to while setting to any non-empty value will cause a build failure because and both attempt to create The correct result would be for the contents of to be written out at the end of , after the stanzas provided by pulseaudio. Somewhat relatedly, the in and in pulseaudio's generated config doesn't make a whole lot of sense. means "override", currently there is nothing for it to override, and we would like user config to override generated config, not the other way around. However, as long as user config is placed in the file after generated config then I don't think the actually makes any difference.
I am having this issue as well. Easily replicated by setting those two options.
Can you make a pull request?
Should be fixed with . If there still is a problem, please reopen this issue.


Question: buildInputs = [ gtk2-x11 lesstif cfitsio python27Env ]; <del> patches = [ ./wrapper.patch ./return-error-code.patch ./clang.patch ./aarch64.patch ]; </del> <ins> patches = [ ./wrapper.patch ./return-error-code.patch ./clang.patch ./aarch64.patch ./gag-font-bin-rule.patch ]; NIX_CFLAGS_COMPILE = stdenv.lib.optionalString stdenv.cc.isClang "-Wno-unused-command-line-argument"; </ins> configurePhase='' substituteInPlace admin/wrapper.sh --replace '%%OUT%%' $out

On Darwin the wrapper adds a number of unused arguments that are passed along to . displays a warning for each of these arguments: This makes the build log of some packages extremely large, and in turn it can cause because of the log size limit is exceeded. /cc system: host os: multi-user?: sandbox: version: channels(smaret): nixpkgs:
I think that fortran on darwin is a rather under-maintained combination in nixpkgs ATM.
for packages that use and on Darwin: Could this be implemented in the wrapper itself rather than in each package that uses the wrapper?
This needs to be propagated to everything that uses gfortran? I think using for gfortran packages might be a better in that case, it's less likely to cause other problems.
I think auto-passing such an option is slightly risky over the long term, as it may hide other errors, e.g. user typos. (No strong opinion.) I wonder if using gfortran with clang is actually a "supported" combination upstream; I guess might be better, as you write.


Question: allowAddonSideload = true; # Must match the contents of `browser/config/version.txt` in the source tree <del> version = "115.12.0"; </del> <ins> version = "115.13.0"; </ins> src = fetchFromGitHub { owner = "Floorp-Projects"; repo = "Floorp"; fetchSubmodules = true; rev = "v${packageVersion}"; <del> hash = "sha256-9EDTVckSqv/nyDi4qjMd54I69WiqM8v6om7zQLT+pQc="; </del> <ins> hash = "sha256-PhI+hIypPF6W5RJIXhCAXblSJNwgYavfCgdQozDSXG0="; </ins> }; extraConfigureFlags = [

Steps to reproduce the behavior: floorp Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi, Please elaborate - there does not seem to be any actual build failure here. What's the actual error? Are you sure your build machine has enough resources? A browser build is pretty demanding and can take even multiple hours on low-to-mid-end machines. Can you please also post the complete derivation log, as obtained using ?
I have the same problem (with floorp and floorp-unwrapped). Here’s the error: ! That feature was removed in February, so either update the qcms crate to 0.3 or downgrade the rust compiler version (1.76 could work).
is the log in the link not enough ?
Oh, I see, Github just truncated the file in the UI. That's what you get from hosting projects on crappy, proprietary software .. Pointing out the exact error too from the get-go would have been helpful in any case. Anyway - seems it broke with a recent rustc upgrade in nixpkgs. This is already fixed with 11.14.1, as it updates the firefox base source. See .
Okay, I will host my opengist instance for the next time ;) Thanks for your prompt response, waiting for your pr to be merged.
Any ETA on the PR merge?
Floorp is now in version 11.14.1 on unstable.


Question: allowAddonSideload = true; # Must match the contents of `browser/config/version.txt` in the source tree <del> version = "115.12.0"; </del> <ins> version = "115.13.0"; </ins> src = fetchFromGitHub { owner = "Floorp-Projects"; repo = "Floorp"; fetchSubmodules = true; rev = "v${packageVersion}"; <del> hash = "sha256-9EDTVckSqv/nyDi4qjMd54I69WiqM8v6om7zQLT+pQc="; </del> <ins> hash = "sha256-PhI+hIypPF6W5RJIXhCAXblSJNwgYavfCgdQozDSXG0="; </ins> }; extraConfigureFlags = [

When installing a PWA using the Floorp browser (experimental toggle in settings), the installed desktop file uses /usr/bin/floorp as the path for the browser to run said PWA. Steps to reproduce the behavior: Floorp experimental PWAs in settings a PWA, e.g. Github or Excalidraw the newly spawned PWA window to launch the same PWA from your DE's application launcher The PWA opens. ! , using flakes, installed via <!-- 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]:
Thanks for reporting! As well as the upstream report! I can look into it what we can do as I get time. But as I'm the only maintainer for Floorp and currently pretty much out of time due to university and $dayjob, I cannot promise any timeline unfortunately. But happy to review patches, of course, if you'd like to fix it yourself. Can you provide such a generated file for further investigation?
sure, one such generated desktop file with the example of excalidraw can be found (github doesn't allow for drag and drop of .desktop files)
Hello! I don't have experience maintaining and modifying large packages like Firefox (floorp), and I currently don't have much free time. However, I've discovered how floorp generates the .desktop file for PWA applications: Maybe it will be helpful to you.
Thanks, that is indeed helpful! Should be relatively easy patchable by us then, from the looks of it.
upstream has and now it will use the path it was in at the time of creating the PWA. It may not be too big of an issue if what they say about fixing it in the next version is true but now the patching will probably fail.


Question: <ins> { lib , buildGoModule , fetchFromGitHub }: buildGoModule rec { pname = "sshed"; version = "1.2.0"; src = fetchFromGitHub { owner = "trntv"; repo = pname; rev = version; hash = "sha256-y8IQzOGs78T44jLcNNjPlfopyptX3Mhv2LdawqS1T+U="; }; vendorHash = "sha256-21Vh5Zaja5rx9RVCTFQquNvMNvaUlUV6kfhkIvXwbVw="; postFixup = '' mv $out/bin/cmd $out/bin/sshed ''; meta = with lib; { description = "ssh config editor and bookmarks manager"; homepage = "https://github.com/trntv/sshed"; license = licenses.asl20; maintainers = with maintainers; [ ocfox ]; }; } </ins>

Project description So basically it is a simple ssh config manager. Metadata homepage URL: source URL: license: Apache-2.0 platforms:


Question: stdenv.mkDerivation rec { pname = "uutils-coreutils"; <del> version = "0.0.25"; </del> <ins> version = "0.0.27"; </ins> src = fetchFromGitHub { owner = "uutils"; repo = "coreutils"; rev = version; <del> hash = "sha256-25jmlGxMWzAaJEmMHruA6H+nqx2QHnYX9c9SKqrQRE4="; </del> <ins> hash = "sha256-6MbX3C5NVwiOwXW5xJO2X3qKMh3pUSALR9aK2IbgaaU="; </ins> }; cargoDeps = rustPlatform.fetchCargoTarball { inherit src; name = "${pname}-${version}"; <del> hash = "sha256-lQoOkiSga2aS8GNgLcHdid1/1u3johYEcGi9oOVsdJs="; </del> <ins> hash = "sha256-JowORfYHxN8GqvWeUm0ACnHNM3uZviYbhR7BOeAfphw="; </ins> }; nativeBuildInputs = [ rustPlatform.cargoSetupHook sphinx ];

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

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


Question: sha256 = "sha256-kPjS+otVZ8aJmDDd7ywD88J5YLEayiIvoXqnrGE8KJA="; }; <ins> # https://github.com/svaarala/duktape/issues/2464 LDFLAGS = [ "-lm" ]; </ins> nativeBuildInputs = [ validatePkgConfig ]; <del> postPatch = '' substituteInPlace Makefile.sharedlibrary  --replace 'gcc' '${stdenv.cc.targetPrefix}cc'  --replace 'g++' '${stdenv.cc.targetPrefix}c++' substituteInPlace Makefile.cmdline  --replace 'gcc' '${stdenv.cc.targetPrefix}cc'  --replace 'g++' '${stdenv.cc.targetPrefix}c++' ''; </del> buildPhase = '' make -f Makefile.sharedlibrary make -f Makefile.cmdline ''; installPhase = '' install -d $out/bin install -m755 duk $out/bin/

Steps to reproduce the behavior: The regression is directly caused by , and the root cause is the library is not properly linked, upstream issue: <!-- 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.


Question: owner = "ful1e5"; repo = "clickgen"; rev = "refs/tags/v${version}"; <del> hash = "sha256-qDaSfIeKCbyl3C2iKz9DYQc1oNwTe5xDlGg/yYhakSw="; </del> <ins> hash = "sha256-mSaltlX2eNRLJ09zN5Tim8mW8mnjPi10W4QIEpiBQvI="; </ins> }; <del> propagatedBuildInputs = [ pillow toml numpy ]; </del> <ins> propagatedBuildInputs = [ pillow toml numpy pyyaml ]; </ins> nativeCheckInputs = [ pytestCheckHook ];

Package name: clickgen Latest released version: 2.1.9 <!-- Search your package here: --- Current version on the unstable channel: 2.1.3 Current version on the stable/release channel: 2.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! --- 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: swapview = callPackage ../os-specific/linux/swapview { }; <ins> swc = callPackage ../development/tools/swc { }; </ins> swtpm = callPackage ../tools/security/swtpm { }; svnfs = callPackage ../tools/filesystems/svnfs { };

Project description swc is the "speedy web compiler" fast alternative to tsc, to compile typescript to javascript without type-checking swc is mentioned in a different context in adds 150 MByte to node_modules so it makes sense to factor-out swc to a global package example use: () on a 2x2GHz machine, swc is 10x faster than tsc = 2 minutes vs 20 minutes is a lightweight wrapper (1 MByte or so) but has as peer-dependency, so npm will install both Metadata homepage URL: source URL: license: apl2 platforms: all


Question: /pkgs/top-level/stage.nix                        @nbp @Ericson2314 @matthewbauer /pkgs/top-level/splice.nix                       @Ericson2314 @matthewbauer /pkgs/top-level/release-cross.nix                @Ericson2314 @matthewbauer <del> /pkgs/stdenv/generic                             @Ericson2314 @matthewbauer </del> <ins> /pkgs/stdenv/generic                             @Ericson2314 @matthewbauer @cab404 </ins> /pkgs/stdenv/cross                               @Ericson2314 @matthewbauer /pkgs/build-support/cc-wrapper                   @Ericson2314 @orivej /pkgs/build-support/bintools-wrapper             @Ericson2314 @orivej

I tried to build a package with debug symbols today and failed. NixOS wiki and nixpkgs repository comments say the following should work: Please run and paste the result.
It worked in Aug 2018: Bisected down to breakage at : Looks like it stems from the fact that does not expose anymore, only . /cc
Woah. master and both work for me with nix stable.
That's surprising. Here is my attempt at current master checkout: I tried removing and seeing the same failure. I wonder why it works for you. Might be a different stdenv?
Does it mean and are the same object?
i can reproduce
I can also reproduce with stable Nix (2.3.14):
Hmm, the issue is that / slaps the on after is defined, closing over the old . In Smalltalk paralance, this would be an issue of insufficiently "late binding".
Still reproducible on current master ()
I ran into this.
Bump, ran into this while updating the Nixpkgs pin on a project of mine.
There should be a test for this :)
Gonna spend next hour or two trying to fix this.
Things that are also missing:
So, this function is not executed on passed through stdenv. Not yet sure why.
Yeah, I've fixed it (thanks, for being there :heart:)
Post-mortem: always read threads. Solution was kinda already provided in , but I delved right in without knowing that)
atleast you now know more about stdenv :slightlysmilingface:
How is the PR looking? I've been waiting on this for a couple of weeks to debug an intermittent crash I'm having with xfce4-sesion :)


Question: buildInputs = [ bzip2 libxml2 libzip boost lua luabind tbb expat ]; <ins> patches = [ ./darwin.patch ]; </ins> env.NIX_CFLAGS_COMPILE = toString [ # Needed with GCC 12 "-Wno-error=stringop-overflow"

Steps to reproduce the behavior: FWIW: my fix is here, - but it is using a fork of . If somebody has the time to create a minimal patch on top of the current source, please feel free to. Please run and paste the result.
Looks like you are on a good path. Unfortunately I have no access to Apple hardware at all, but would be happy to merge a PR.
Yes, is working on it. There is a more active fork of luabind here: - how about we switch to using it? It'll obviate a bunch of patches as well.
I agree, sounds sensible.


Question: libnotify libX11 libXcomposite <ins> libunity </ins> libuuid libXcursor libXdamage

I never really noticed this until today, but apparently the discord task bar icon (if you have one, I am on KDE) is supposed to have a notification badge, I have included a screenshot. The discord task bar icon should include a badge for the number of unread notifications ! Today I was setting up a system for someone else who was new to Linux, I installed Discord via flatpak, and then they asked me about the badge (since it is present on Windows but not on the ). From a little searching, it seems that Discord needs to ba available in the system, so on Kubuntu this was fixed by doing . Since is already in , it might just be a matter of adding it to the ?
Huh. I don't think I ever knew one was supposed to be there either. I see an unread indicator (red circle in the top corner, no number), so that works fine, but I don't think I've ever seen a number. Assuming that would be all it would take, sounds like a pretty simple PR that would be a good addition.
I have made a clone of and it does seem that all that was need was to add the library to . I found it to be a bit ugly myself since I had over 1000 unread notifications, and it seems disabling it is only possible outside the application. On for example, you have to go to and tick off "Show notification badges". Running the current from afterwords does not remove the badges, it only freezes them in place, as in marking notifications as read will not update the number, so this is also cached somewhere outside , meaning this couldn't be a toggleable functionality via an .


Question: , closureInfo , coreutils , e2fsprogs <del> , fakechroot </del> <ins> , proot </ins> , fakeNss , fakeroot , go

Relevant snippet while building it fails with I copied over the for debugging, this is the full output: Steps to reproduce the behavior: snippet as flake default output Build should succeed and images should be loadable via Patching the as follows: fixes the problem, but would probably hide other cp errors. Maybe the behavior of coreutils/cp changed in the recent versions. At least the current manual states it will fail silently. I'm using a linux-builder on my machine.
Thank you for reporting this. I’ll try to replicate this locally. The lines do not look like errors to me. It looks like is informing that those files already exist in the output and thus are skipped (--no-clobber). However, if the build is failing there’s something going wrong.
Thank you for linking the manual. It looks like will exit with a non-zero status code in case of files that are already present now. The coreutils changelog states that now reproduces the behavior had at the time I wrote the mergeImages script. I was able to build by changing to . I don't know how to best go about obtaining the behavior everywhere, should the flag be dependent on the version of somehow? Maybe we can just assume that in will be a new version from now so that we can use everywhere? Given that all files that are present in both docker images apart from the and repositories files should be content addressed the only issue with removing is that time is spent unnecessarily writing content that's already present, so removing the flag altogether might make sense.
Thanks for investigating! I'm not familiar with the backward compatibility policy of the nix ecosystem, but I would assume that the most recent version of can assume most recent coreutils. Might happen that someone is overlaying old coreutils but then you might just need to overlay the old too, if you can pinpoint it down to coreutils cp.
True, but then apparently they have a legacy software problem, in which case they should use overrides only where it is necessary, instead of a blanket override in an overlay. It is not realistic to expect all of Nixpkgs to work with arbitrary changes. The cost of such compat logic isn't worth it; certainly not in this case, until proven otherwise. If they contribute a full time maintainer it is worth it, and if they have a legacy software problem they probably can.


Question: { stdenv, lib, buildPackages <del> , fetchurl, zlib, autoreconfHook </del> <ins> , fetchurl, zlib, autoreconfHook, gettext </ins> # Enabling all targets increases output size to a multiple. , withAllTargets ? false, libbfd, libopcodes , enableShared ? true

I'm not really sure why this would happen or how to go about dealing with this. Any tips?
(triage) still a problem?
Unsure, I don't use nix on my mac anymore.
This was a coreutil, right? If so, it’s probably fixed by now.
Probably safe to assume so.
I'm actually hitting the same thing right now.


Question: done ''; <del> doInstallCheck = true; </del> <ins> doInstallCheck = !stdenv.hostPlatform.isAarch64; # tests are flaky for aarch64-linux on hydra </ins> installCheckTarget = "testall"; preInstallCheck = ''

Steps to reproduce the behavior: I came up with the idea of building julia19 for that platform as a possible resort as the binary artifact does not work as is on my hardware, causing a , see also . <!-- 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 failure is also reproducible on hydra: , looks like the flaky tests that have been plaguing us for a long time.


Question: , target ? null # Select whether DYNAMIC_ARCH is enabled or not. , dynamicArch ? null <ins> # enable AVX512 optimized kernels. # These kernels have been a source of trouble in the past. # Use with caution. , enableAVX512 ? false </ins> , enableStatic ? stdenv.hostPlatform.isStatic , enableShared ? !stdenv.hostPlatform.isStatic }:

Describe the bug In the AVX512 support was turned back on in openblas, allowing for the use of dynamic, AVX512 optimized compute kernels. started to discover problems with AVX512 while working on the and I can confirm that this problem affects multiple packages that are built against openblas. The problem already manifest itself in that packages fail their unit tests, when build on an AVX512 enabled machine (see for a detailed list). The tests either fail due to a wrong result or time out. I could indentify 5 different packages which are affected by this bug, leading to the conclusions this very likely affects many more packages. Affected versions of openblas, which I have tested, are 0.3.13 (master/release-21.05) and 0.3.15 (in staging at the moment). The problem disappears when: is complied with in is injected into the test phase or just set at runtime. Note that any core type that does not use AVX512 works fine here (tested: , or , but , which uses AVX512 fails). is turned off at openblas build time and is set to a non-AVX512 target (see point 2). you seem to be making use AVX512 optimizations. Did you notice any problems? I suggest to revert and thus re-introduce the makeFlag in openblas. To Reproduce an affected program which is linked against openblas on an Intel CPU that supports AVX512 instructions (e.g. Xeon Scalable) and check the results. In nixpkgs it is at least that is affected (delivers wrong results). , for example, on an Intel CPU with AVX512: the self tests/unit tests never finish in this case. external packages fail to run their tests on and AVX512 enabled machine: Notify maintainers CC Metadata This should affect since (~January 2021) and . The tests I have carried out were run with versions from the ~last week.
Sorry to hear that :(. Then we should indeed revert that change again.
Can this be closed?
The PR has been merged into staging. Should we wait to close the issue until the fix reaches master?


Question: stdenv.mkDerivation rec { pname = "spirv-tools"; <del> # Update spirv-headers rev in lockstep according to DEPs file version = "2021.3"; </del> <ins> version = "1.2.198.0"; </ins> src = fetchFromGitHub { owner = "KhronosGroup"; repo = "SPIRV-Tools"; <del> rev = "v${version}"; sha256 = "sha256-skpsxpgl6hR5uiKfphKFQJfh+LJvhGvDW/t2u5AhXzk="; </del> <ins> rev = "sdk-${version}"; sha256 = "sha256-8EJbTPY5dvsqx32POf2HcCV3j2fA68GtGZA66l9V4TI="; </ins> }; nativeBuildInputs = [ cmake python3 ];

name: All packages in current version: 1.2.189.1 desired version: 1.2.200 maintainers: Please tag this issue in your PR.


Question: <del> { config, lib, ... }: </del> <ins> { config, pkgs, lib, ... }: </ins> with lib; let

Describe the bug Most of my programs is unable resolve DNS after I updated my system to (from the last time nixos-ustables was updated which is approximately 14 days ago). This includes curl, chrome, resolvectl and nix which basically makes my system unusable. One really weird exception is the tool which is actually able to query both a remote server (such as 8.8.8.8) and the local systemd-resolved server to resolve DNS (which indicates that this is probably not the fault of systemd). There's also a error message in systemd-resolved's that said "Failed to escape hostname: Invalid argument". I also tried to edit my file to change the nameserver to 8.8.8.8 and that didn't change anything. here are some examples of the errors returned by those programs: To Reproduce I don't really know how to reproduct this issue Expected behavior DNS should be working properley on all programs Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run and paste the result. Maintainer information:
Programs which are broken are using the libc calls to resolve the hostname, looks like the nss module from systemd-resolved can't resolve the hostname either. This looks to be some kind of failure within systemd-resolved, since systemd-resolve on the CLI fails with . We should also open an upstream bug unless we find some evidence that this is caused by NixOS.
This bug affects me too. Same error and same logs.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Same bug on my end.
I think I figured out what's the problem here. I opened an upstream issue: Can you try if the following patch works around the issue?
that worked! (though I have to manually edit the service file since automatic GC kicked in and I cannot rebuild my system:facepalm:) Also, I feel like there should be a basic network connectivity test to prevent bugs like this from being merged into the unstable channel.
And thanks for the quick action ! I agree, but I thought we actually have them for unstable?


Question: <del> { config, lib, ... }: </del> <ins> { config, pkgs, lib, ... }: </ins> with lib; let

I've the following to my : and I can confirm systemd-resolved works again. Now, how do you get to rebuild your system if like you don't have a working system to rollback to? I did (as root): to force using that file in order to be able to run .
aw man I did not know that if you stop systemd-resolved it will resolve normally. I removed the symlink and created a new directory there, copied everything from to there, manually edited systemd-resolved.service, and ran and after that restarted systemd-resolved. method is definitely more superior.
So... for now we push this workaround to nixpkgs master?
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I'd say yes. Especially if there's no quick upstream fix in perspective. Hopefully this problem only affects users following unstable.
Stable doesn't get systemd updates, so it shouldn't be affected (based on flokli's analysis).
PR at


Question: url = "https://code.qt.io/cgit/qt/qtwayland.git/patch/?id=6fe83f6076423068b652fa4fcb0b5adbd297f2a8"; hash = "sha256-TlZozKezpYm90B9qFP9qv76asRdIt+5bq9E3GcmFiDc="; }) <ins> # Fix potential crash issues when some submenus are expanded # https://codereview.qt-project.org/c/qt/qtwayland/+/519344/ (fetchpatch { url = "https://code.qt.io/cgit/qt/qtwayland.git/patch/?id=aae65c885d8e38d8abc2959cded7b5e9e5fc88b3"; hash = "sha256-FD1VaiTgl9Z1y+5EDpWYShM1ULoFdET86FoFfqDmjyo="; }) </ins> ]; }

Submenus (rendered as popups) in some qt apps (happens a lot in telegram-desktop) can make the app crash if one clicks outside while they are shown. It's a bug in qt6.6 that is foxed by this patch: Other distros (Arch at least) include the patch already.


Question: let ss = opt.type.getSubOptions opt.loc; in if ss != {} then optionAttrSetToDocList' opt.loc ss else []; in <del> [ docOption ] ++ subOptions) (collect isOption options); </del> <ins> [ docOption ] ++ optionals docOption.visible subOptions) (collect isOption options); </ins> /* This function recursively removes all derivation attributes from

Describe the bug When renaming a submodule, the makes the child options reappear in the docs at the old location. This did not happen before (ping I've encountered the problem in the arion docs when its tooling to nixpkgs 20.03. The move is -. The regression makes the docs start with a mountain of legacy options comprising just under half of all options. Reverting fixes the problem. To Reproduce Steps to reproduce the behavior: an option to is in the docs, despite Expected behavior The option docs should have at most one entry per renamed option. Any suboptions should be omitted. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata Please run and paste the result. Maintainer information:


Question: jobs = recursiveUpdateMany [ (mapTestOn { haskellPackages = packagePlatforms pkgs.haskellPackages; <del> haskell.compiler = packagePlatforms pkgs.haskell.compiler; </del> <ins> haskell.compiler = packagePlatforms pkgs.haskell.compiler // (lib.genAttrs [ "ghcjs" "ghcjs810" ] (ghcjsName: { # We can't build ghcjs itself, since it exceeds 3GB (Hydra's output limit) due # to the size of its bundled libs. We can however save users a bit of compile # time by building the bootstrap ghcjs on Hydra. For this reason, we overwrite # the ghcjs attributes in haskell.compiler with a reference to the bootstrap # ghcjs attribute in their bootstrap package set (exposed via passthru) which # would otherwise be ignored by Hydra. bootGhcjs = (packagePlatforms pkgs.haskell.compiler.${ghcjsName}.passthru).bootGhcjs; })); </ins> tests.haskell = packagePlatforms pkgs.tests.haskell;

As a fallout of the migration to GHC 9.0.2 got marked as broken, as it failed to build with GHC 9.0.2 and the Stackage LTS 19 package set we now have. It would be necessary to investigate if survived this (i.e. if it still builds) and if not to get it to work again. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc
should compile again. The bootstrap is additionally built by Hydra, so only the GHC bundled libraries will need to be compiled (which is an improvement to before at least).


Question: ''; nativeBuildInputs = [ <del> pythonRelaxDepsHook </del> which ]; <del> pythonRelaxDeps = [ "pyre-extensions" ]; </del> propagatedBuildInputs = [ numpy torch <del> pyre-extensions </del> ]; pythonImportsCheck = [ "xformers" ];

Package name: Latest released version: 0.0.22.post7 <!-- Search your package here: --- Current version on the unstable channel: (This version never existed but whatever!) Current version on the stable/release channel: None <!-- 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. Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
let me know if you have time to test


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

package lists and as dependencies but upstream uses instead. Steps to reproduce the behavior: dependencies of package it to the dependencies listed by upstream and should not be in the dependencies list, but should n/a <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
That's a bot.
Thank you for the quick turnaround!


Question: # These assertions can be removed in NixOS 24.11, when all users have been # warned once. { <del> assertion = (cfg.settings ? replication_factor || cfg.settings ? replication_mode) || lib.versionOlder cfg.package.version "1.0.0"; </del> <ins> assertion = (cfg.settings ? replication_factor || cfg.settings ? replication_mode) || lib.versionOlder cfg.package.version "1.0.0"; </ins> message = '' Garage 1.0.0 requires an explicit replication factor to be set. Please set replication_factor to 1 explicitly to preserve the previous behavior.

Steps to reproduce the behavior: -rebuild test on settings.datadir = "/mnt/garage0"; resolves fine Tested on nixos24.05 but code of the module is unchanged in nixos_unstable. I'm using flakes as well Please run and paste the result.
Looks like doesn't apply, maybe should tinker a bit on my own
It looks like the option type was adjusted, but not the other code in the module that checks that value. Shouldn't be too hard to fix.


Question: ./programs/light.nix ./programs/mosh.nix ./programs/mininet.nix <ins> ./programs/msmtp.nix </ins> ./programs/mtr.nix ./programs/nano.nix ./programs/nm-applet.nix

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


Question: homepage = http://gnunet.org/; <del> license = stdenv.lib.licenses.gpl2Plus; </del> <ins> license = licenses.gpl2Plus; </ins> <del> maintainers = with stdenv.lib.maintainers; [ viric ]; platforms = stdenv.lib.platforms.gnu; </del> <ins> maintainers = with maintainers; [ viric vrthra ]; platforms = platforms.gnu; </ins> }; }

Not sure if this is known, but I'm seeing the following error when trying to do . System: Fedora 23 Nix version: 1.11.2 Nixpkgs version: 16.09pre81657.


Question: # an AppArmor profile is provided to get a confinement based upon paths and rights. builtins.storeDir "/etc" <del> "/run" </del> ] ++ optional (cfg.settings.script-torrent-done-enabled && cfg.settings.script-torrent-done-filename != null)

I have transmission running inside a Nixos container which has been working without issue until I recently updated the system. It now fails to start inside the container, I have tried deleting the container and all its data but the same issue exists when creating a new one. I have also tried creating the path "" on both the host and container but it doesn't seem to care. Steps to reproduce the behavior: Run transmission inside of a container Transmission service starts and runs without issue Service status Here's where I have the container and transmission defined in my config. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Same here, not sure if it's an upstream or nixpkgs issue
For the time being and since it's inside a container anyway I'm overriding the root dir of the systemd unit:
Thanks your fix is working for me!
The problem is that is listed in : Which got introduced in to The original problem was that was not in the chroot. I'd say mounting all of as read-only is going too far, so a better fix would be to just mount and only if is true. It also seems weird to have this logic be part of Transmission, but whatever. So a workaround is: (And I'm not sure why this wasn't a problem for 3 years)
I've stumbled upon this issue as well, and wondering if there is anything we can do about it regarding the Transmission service. I had to disable the following is well, before it played nicely in my setup.
indeed, adding only was one the alternatives suggested in , so we can try your suggestion. IMHO disabling or should not be the default, we could make them use though, would that be enough for you?
This is actually still an issue and it isn't limited to containers. Adding the params that posted, unfortunately, does not work for me ;/


Question: stdenv.mkDerivation rec { pname = "lean"; <del> version = "3.4.2"; </del> <ins> version = "3.5.1"; </ins> src = fetchFromGitHub { <del> owner  = "leanprover"; </del> <ins> owner  = "leanprover-community"; </ins> repo   = "lean"; rev    = "v${version}"; <del> sha256 = "0zpnfg6kyg120rrdr336i1lymmzz4xgcqpn96iavhzhlaanmx55l"; </del> <ins> sha256 = "0m7knf1hfbn2v6p6kmqxlx8c40p5nzv8d975w2xwljaccc42j1yp"; </ins> }; nativeBuildInputs = [ cmake ];

Describe the bug It is not able to build 3.4.2 with To Reproduce Steps to reproduce the behavior: Expected behavior Successfully build Additional context It looks like there is a build issue with 3.4.2 (, , ). It would be better to update to version 3.5.1 from Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(jjc93): nixpkgs: Maintainer information:
I tried to update it locally, and failed. It still gives me .


Question: NIX_CFLAGS_COMPILE = "-DG_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS"; postPatch = '' <ins> # See https://github.com/NixOS/nixpkgs/issues/132259 substituteInPlace meson.build  --replace "x11_enabled = false" "" </ins> files=( build-aux/meson/post-install.py demos/gtk-demo/geninclude.py

is built without X11 support on darwin because the Meson build file disables it. The GTK build system was changed to Meson by , and it removed the configure flags that enabled X11 on darwin: But the file of GTK3 disables X11 support on darwin, and : should provide X11 support on darwin. I was trying to fix on darwin and I found that is marked as broken () because of a missing GKT/X11 header. It seems that it is the same problem that motivated to change Vim to use "gtk2" (same missing header ). Maintainer information:
In that case I'd probably take the discussion upstream.
It was disabled in 3.24.9 by commit , without much explanation. But that commit never landed into master and GTK 4.x does build with X11 support as I understand ( and ).


Question: NIX_CFLAGS_COMPILE = "-DG_ENABLE_DEBUG -DG_DISABLE_CAST_CHECKS"; postPatch = '' <ins> # See https://github.com/NixOS/nixpkgs/issues/132259 substituteInPlace meson.build  --replace "x11_enabled = false" "" </ins> files=( build-aux/meson/post-install.py demos/gtk-demo/geninclude.py

Describe the bug peek fails to build on macOS To Reproduce Clone then Notify maintainers Log
I marked this as stale due to inactivity. →
sadly its not supported though getting keybinder3 to compile would be good
I marked this as stale due to inactivity. →


Question: python3.pkgs.buildPythonApplication rec { pname = "dvc"; <del> version = "3.5.0"; </del> <ins> version = "3.5.1"; </ins> format = "pyproject"; src = fetchFromGitHub { owner = "iterative"; repo = pname; rev = "refs/tags/${version}"; <del> hash = "sha256-AQE8KQ5j/EgN1P2HFghWXgQJbBc+KYu8kwNeV0Tktho="; </del> <ins> hash = "sha256-1kVc7+36rvIpoSinpyxMMs1/nhZrwv1pPWJsruFd1N8="; </ins> }; pythonRelaxDeps = [

Steps to reproduce the behavior: X Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.


Question: buildNpmPackage rec { pname = "asf-ui"; <del> version = "f84a296f0ab029e56baba3cca45e5cf21129fd76"; </del> <ins> version = "b341e7f78f1f73fb3a11a3f3cfbfbed929242606"; </ins> src = fetchFromGitHub { owner = "JustArchiNET";

Package name: ArchiSteamFarm Latest released version: 5.5.2.3 <!-- Search your package here: --- Current version on the unstable channel: 5.5.0.11 Current version on the stable/release channel: 5.4.12.5 <!-- 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]:
It helps if I also open the PR when doing the update


Question: +install_requires.append(pywin32_req + " ; sys_platform == 'win32'") dev_extras = [ <del> 'astroid==1.6.5', </del> <ins> 'coverage', </ins> -- 2.24.1

Update certbot Current packaged version is 0.39.0, upstream version is 1.2.0.
Fix in


Question: process = self.process_1_6_20_0; })); <ins> Cabal_3_12_0_0 = doDistribute (super.Cabal_3_12_0_0.override ({ Cabal-syntax = self.Cabal-syntax_3_12_0_0; } // lib.optionalAttrs (lib.versionOlder self.ghc.version "9.2.5") { # Use process core package when possible process = self.process_1_6_20_0; })); </ins> # cabal-install needs most recent versions of Cabal and Cabal-syntax, # so we need to put some extra work for non-latest GHCs inherit (

currently fails It requires 3.12. I believe this in pinned to 3.10 somewhere in NixPkgs, but do not know where. Add any other context about the problem here. No maintainers Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
please add "Haskell" label
fixed here


Question: # Hardened linux hardenedLinuxPackagesFor = kernel: linuxPackagesFor (kernel.override { <ins> features.ia32Emulation = false; </ins> extraConfig = import ../os-specific/linux/kernel/hardened-config.nix { inherit stdenv; inherit (kernel) version;

I currently cannot execute any 32 bit Linux binaries on my 64 bit system and this breaks updates, since I have 32 bit support enabled in the nix options: I remember that this worked about a week ago, so something has changed. I am new to NixOS, so its possible that I have done something wrong. I used ArchLinux for about 9 years before that and now NixOS for just 3 months and its concepts are still foreign for me. As a long term linux user (about 15 years) I do feel a bit out of place in NixOS. So I am not sure how to fix that myself. Not sure. I have wine installed and support for 32 bit games enabled. Then I normally do just 'nixos-rebuild switch --upgrade' to upgrade, and sometimes 'nix-channel --update'. I also regularly do 'nix-collect-garbage -d'. No idea if that is reproducible or not.
This might be from Could you see if it works without that commit? Also verify that /nix/store/4qj9vzggfzsc34ci79ckaim5cjrwc6ns-bash-4.4-p23/bin/bash executes. I can run it on my system. You can run this to verify that your store is not corrupted:
I solved it now for me. Instead of using the 'linuxPackagestestinghardened' 4.20 linux kernel I switched back to 'linuxPackages419' 4.19.2 kernel and now executing 32 binaries work again. So I guess the hardened kernel does not support executing 32 bit binaries. Does it make sense to have some kind of visible warning here? I normally would not have used the hardened kernel, if that wouldn't have been the only 4.20 version is I get. Its not clear to me when and how those changes in master appear in my nixpkgs/nixos channel (I am on unstable). I would like to use the master branch directly, but I haven't figured out how to best do that yet.
The same here, hardened kernel 4.18.17 and build failed.


Question: # Hardened linux hardenedLinuxPackagesFor = kernel: linuxPackagesFor (kernel.override { <ins> features.ia32Emulation = false; </ins> extraConfig = import ../os-specific/linux/kernel/hardened-config.nix { inherit stdenv; inherit (kernel) version;

building '/nix/store/6h9asn7rc93dbwfcs6xaj3k0qgxmg0vh-libtxcdxtn-'... while setting up the build environment: executing '/nix/store/xgf4vra77qrww0n228hd80jsdccdp54w-bash-4.4-p23/bin/bash': Exec format error builder for '/nix/store/6h9asn7rc93dbwfcs6xaj3k0qgxmg0vh-libtxcdxtn-' failed with exit code 1 building '/nix/store/cfwj5yjby2xvagyj69zd1yx8hdhi27ay-'... cannot build derivation '/nix/store/maynq4fxxjc217figygdrgg5q9xnw6yy-mesa-drivers+txc-': 1 dependencies couldn't be built cannot build derivation '/nix/store/wv9b4ayvgnpkvwz81zkk0lm9w4v5pd1y-opengl-drivers-': 1 dependencies couldn't be built cannot build derivation '/nix/store/q61vc27rdbcsrhxifiw89w1qdjax1amh-nixos-system-brix-': 1 dependencies couldn't be built error: build of '/nix/store/q61vc27rdbcsrhxifiw89w1qdjax1amh-nixos-system-brix-' failed Thanks
Maybe the hardened kernel shouldn't set when NixOS' is an ?
It should be 64 bit for the x86_64-linux stdenv. But some packages use the i686 stdenv.
I am not too familiar with stdenv. Is this expected behaviour that a 64-bit system uses 32-bit binaries? This issue is reproducible building as well.
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.


Question: # Hardened linux hardenedLinuxPackagesFor = kernel: linuxPackagesFor (kernel.override { <ins> features.ia32Emulation = false; </ins> extraConfig = import ../os-specific/linux/kernel/hardened-config.nix { inherit stdenv; inherit (kernel) version;

Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This should be resolved by - please reopen if there's still a problem.


Question: locale = "${if stdenv.isDarwin then darwin.adv_cmds else lib.getBin stdenv.cc.libc}/bin/locale"; }) <del> ] ++ lib.optionals stdenv'.hostPlatform.isMusl [ # Fixes for musl libc # These patches are not properly guarded and should NOT be enabled everywhere (fetchpatch { url = "https://git.alpinelinux.org/aports/plain/main/postgresql14/disable-test-collate.icu.utf8.patch?id=56999e6d0265ceff5c5239f85fdd33e146f06cb7"; hash = "sha256-pnl+wM3/IUyq5iJzk+h278MDA9R0GQXQX8d4wJcB2z4="; }) </del> <ins> ] ++ lib.optionals (stdenv'.hostPlatform.isMusl && atLeast "12") [ </ins> (fetchpatch { url = "https://git.alpinelinux.org/aports/plain/main/postgresql14/icu-collations-hack.patch?id=56999e6d0265ceff5c5239f85fdd33e146f06cb7"; hash = "sha256-Yb6lMBDqeVP/BLMyIr5rmR6OkaVzo68cV/+cL2LOe/M="; }) <del> ] ++ lib.optionals stdenv'.isLinux [ </del> <ins> ] ++ lib.optionals (stdenv'.hostPlatform.isMusl && atLeast "13") [ (if olderThan "14" then fetchpatch { url = "https://git.alpinelinux.org/aports/plain/main/postgresql13/disable-test-collate.icu.utf8.patch?id=69faa146ec9fff3b981511068f17f9e629d4688b"; hash = "sha256-IOOx7/laDYhTz1Q1r6H1FSZBsHCgD4lHvia+/os7CCo="; } else fetchpatch { url = "https://git.alpinelinux.org/aports/plain/main/postgresql14/disable-test-collate.icu.utf8.patch?id=56999e6d0265ceff5c5239f85fdd33e146f06cb7"; hash = "sha256-pnl+wM3/IUyq5iJzk+h278MDA9R0GQXQX8d4wJcB2z4="; }) ] ++ lib.optionals stdenv'.isLinux  [ </ins> (if atLeast "13" then ./patches/socketdir-in-run-13.patch else ./patches/socketdir-in-run.patch) ];

Beginning around commit , postgres < 14 will not build with musl: Postgresql successfully builds Here is the full output: The patches introduced in the above commit appear to be specific to Postgresql 14.x <!-- 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.


Question: echo "-arch ${targetPlatform.darwinArch}" >> $out/nix-support/libc-ldflags '' <ins> ## ## GNU specific extra strip flags ## # TODO(@sternenseemann): make a generic strip wrapper? + optionalString (bintools.isGNU or false) '' wrap ${targetPrefix}strip ${./gnu-binutils-strip-wrapper.sh}  "${bintools_bin}/bin/${targetPrefix}strip" '' </ins> ### ### Remove LC_UUID ###

The Linux stdenv sets But that flag is specific to GNU strip, and LLVM's strip will fail if passed it. Conveniently, we silence all errors from stripping, so this has gone unnoticed until now: I noticed this while trying to fix . One of the reasons it doesn't work is that it has in , and strip should be removing that reference but isn't. What I'm not sure about here is the best way to fix this. There's nothing platform-specific about this option, so it shouldn't live in the Linux stdenv. (Other platforms like NetBSD use GNU binutils by default.) Ideally it would be a conditional in the strip setup hook, but we don't really have a bash equivalent to . So where (in Nix) should we check this and set the variable? cc
With what we have at the moment, I can only think of hacky workarounds like checking if ends in . However such an approach (and even checking ) is actually incorrect: and don't have to be matched, e. g. with as linker and GNU bintools is quite common actually. Looking at prior art in nixpkgs, I'm quite convinced that the cleanest solution for now would be to bite the bullet and extend to also wrap . In fact, we already seem to have a strip wrapper for darwin.
Hmm, I don't like the idea of globally adding a flag only to remove it again in a wrapper. Another idea I had was to do this in the definition of make- — the hardening flags are precedent for doing manipulation of environment variables for setup hooks in there. We could add an isGNU attribute to the possible values of , and use that? I don't much like this idea either, but I like it better than adding the flag globally and then wrapping to remove it. What do you think?
Since this flag is unconditionally in general, I think we can just remove it from the linux hook and instead add it in the binutils-wrapper. This should also solve the issue of this being binutils-specific and not linux-specific AIUI.
Oh, you mean wrap GNU binutils' strip to add this flag? That sounds fine to me.
If I understand correctly this is now done:


Question: <ins> { lib, stdenv, fetchurl, makeWrapper, makeDesktopItem, copyDesktopItems, unzip , appimage-run }: stdenv.mkDerivation rec { pname = "ldtk"; version = "1.1.3"; src = fetchurl { url = "https://github.com/deepnight/ldtk/releases/download/v${version}/ubuntu-distribution.zip"; sha256 = "sha256-qw7+4k4IH2+9DX4ny8EBbSlyXBrk/y91W04+zWPGupk="; }; nativeBuildInputs = [ unzip makeWrapper copyDesktopItems appimage-run ]; buildInputs = [ appimage-run ]; unpackPhase = '' runHook preUnpack unzip $src appimage-run -x src 'LDtk ${version} installer.AppImage' runHook postUnpack ''; installPhase = '' runHook preInstall install -Dm644 'LDtk ${version} installer.AppImage' $out/share/ldtk.AppImage makeWrapper ${appimage-run}/bin/appimage-run $out/bin/ldtk  --add-flags $out/share/ldtk.AppImage install -Dm644 src/ldtk.png $out/share/icons/hicolor/1024x1024/apps/ldtk.png runHook postInstall ''; desktopItems = [ (makeDesktopItem { name = "ldtk"; exec = "ldtk"; icon = "ldtk"; terminal = false; desktopName = "LDtk"; comment = "2D level editor"; categories = [ "Utility" ]; mimeTypes = [ "application/json" ]; }) ]; meta = with lib; { homepage = "https://ldtk.io/"; description = "Modern, lightweight and efficient 2D level editor"; license = licenses.mit; platforms = [ "x86_64-linux" ]; maintainers = with maintainers; [ felschr ]; sourceProvenance = with sourceTypes; [ binaryBytecode ]; }; } </ins>

Project description LDtk is an open source level editor that's used to make video games such as Dead Cells. It's just reached a big milestone and recently hit 1.0.0 release (now on 1.1.1). I apologise to the people of nixpkgs for requesting for so many new packages today! Metadata homepage URL: source URL: license: mit platforms: linux, mac, windows


Question: environment.systemPackages = [ pkgs.sx ]; services.xserver = { exportConfiguration = true; <del> displayManager = { job.execCmd = ""; lightdm.enable = mkForce false; }; </del> logFile = mkDefault null; }; <del> systemd.services.display-manager.enable = false; </del> }; meta.maintainers = with maintainers; [ figsoda ];

I believe that this prevents the use of other display managers -Don't force it?
if you enable a another dm you wouldn't get this error i submitted a pr so that this error does not happen when lightdm is disabled but a another dm isn't enabled


Question: ) super.ocaml-ng; python27 = super.python27.override { static = true; }; <del> python35 = super.python35.override { static = true; }; </del> python36 = super.python36.override { static = true; }; python37 = super.python37.override { static = true; }; python38 = super.python38.override { static = true; };

According to the 3.5 life-cycle () , the final release has already occurred and is now considered EOL. The jump from 3.5 to 3.6 has already happened in the majority of python packages and should not be a similar situation in which we had to extend python2's life long after its official EOL date.


Question: <ins> { lib, stdenv, fetchFromGitLab, cmake, }: stdenv.mkDerivation (finalAttrs: { pname = "openmesh"; version = "11.0.0"; src = fetchFromGitLab { domain = "gitlab.vci.rwth-aachen.de:9000"; owner = "OpenMesh"; repo = "OpenMesh"; rev = "OpenMesh-${lib.versions.majorMinor finalAttrs.version}"; fetchSubmodules = true; sha256 = "sha256-1FmAieCaskKaaAWjgEXr/CWpFxrhB2Rca1sXpxLrQHw="; }; nativeBuildInputs = [ cmake ]; meta = with lib; { homepage = "https://www.graphics.rwth-aachen.de/software/openmesh/"; description = "Generic and efficient polygon mesh data structure"; maintainers = with maintainers; [ yzx9 ]; platforms = platforms.all; license = licenses.bsd3; }; }) </ins>

Request for a new nix package for openmesh : library for polygonal meshes Thank you. OpenMesh is a generic and efficient data structure for representing and manipulating polygonal meshes. OpenMesh is developed at the Computer Graphics Group, RWTH Aachen. It was funded by the German Ministry for Research and Education ( BMBF). It was designed with the following goals in mind: Flexibility : provide a basis for many different algorithms without the need for adaptation. Efficiency : maximize time efficiency while keeping memory usage as low as possible. Ease of use : wrap complex internal structure in an easy-to-use interface.
I think it would help if you described why you need the library packaged. Do you plan to include any software that uses the library into the distribution?
Yes it will be feasible later. At the moment I would like to develop and launch continuous integration with Nix. I have 7/8 libraries and I need this last one under Nix to start. Note that this library is very stable, recognized in the domain of meshes, simpler than CGAL, small, without dependency... It is also on Mac with HomeBrew for example.
I don't want to maintain it, but this derivation will get you up off the ground:
Thanks a lot, I will look that maybe after summer and maybe I will propose to be the maintainer of this package, we will see ! Thanks
I marked this as stale due to inactivity. →
Have you tried to package this?
No time for the moment. But I will look that when I can... or or
Modified from version to fit the URL for versions 10.0: Hi I saw your comment about the PR. If you have time now, that would be great. If not, I'd be happy to help and create the PR.
Hi No time sorry, so you can do that. Thanks !


Question: homepage = "https://github.com/JustArchiNET/ArchiSteamFarm"; license = licenses.asl20; mainProgram = "ArchiSteamFarm"; <del> maintainers = with maintainers; [ SuperSandro2000 lom ]; </del> <ins> maintainers = with maintainers; [ SuperSandro2000 ]; </ins> }; }


Question: "APPDATA_INSTALL_PATH=${placeholder "out"}/share/appdata" ]; <ins> env = { # Fix build due to missing `std::option`. NIX_CFLAGS_COMPILE = "-std=c++17"; }; </ins> meta = with lib; { description = "A tabbed document viewer"; license = licenses.gpl2Plus;

Steps to reproduce the behavior: nixpkgs master (currently ) This seems to be directly caused by introduced in No update of is availble upstream. (author of the PR) ( maintainer) Please run and paste the result.


Question: inherit (darwin.apple_sdk.frameworks) CoreServices; }; <ins> devspace = callPackage ../development/tools/misc/devspace { }; </ins> maturin = callPackage ../development/tools/rust/maturin { inherit (darwin.apple_sdk.frameworks) Security; };

Project description DevSpace is an open-source developer tool for Kubernetes that lets you develop and deploy cloud-native software faster. Metadata homepage URL: source URL: license: apache2 platforms: linux, darwin


Question: # Generate build symbols once after the final build # https://firefox-source-docs.mozilla.org/crash-reporting/uploading_symbol.html <del> preInstall = '' </del> <ins> preInstall = lib.optionalString crashreporterSupport '' </ins> ./mach buildsymbols mkdir -p $symbols/ cp mozobj/dist/*.crashreporter-symbols.zip $symbols/ <ins> '' + '' </ins> cd mozobj '';

Steps to reproduce the behavior: librewolf from nixpkgs master Add any other context about the problem here. Please run and paste the result.
I have the exact same issue but my machine is a little slower :|. Also this means (not just Git ) is now broken.
I also reproduced this on master.
I think it's related to . I'm guessing the crash reporter symbols aren't generated because we disable the crash reporter. Running some tests to confirm.
is the first broken commit on master.
I'm going to close this. The PR by fixes the problem.


Question: <ins> { lib , stdenv , fetchFromGitHub , boca , smooth , systemd }: stdenv.mkDerivation rec { pname = "freac"; version = "1.1.3"; src = fetchFromGitHub { owner = "enzo1982"; repo = "freac"; rev = "v${version}"; sha256 = "1sdrsc5pn5901bbds7dj02n71zn5rs4wnv2xxs8ffql4b7jjva0m"; }; buildInputs = [ boca smooth systemd ]; makeFlags = [ "prefix=$(out)" ]; meta = with lib; { description = "The fre:ac audio converter project"; license = licenses.gpl2Plus; homepage = "https://www.freac.org/"; maintainers = with maintainers; [ shamilton ]; platforms = platforms.linux; }; } </ins>

Project description fre:ac is a free audio converter and CD extractor for Microsoft Windows, Linux, macOS and FreeBSD, distributed under the GNU General Public License.[1] Besides extracting audio from compact discs (with various features including hidden track detection), fre:ac can also convert audio files from one format to another or to the same format but a lower bitrate. fre:ac is compatible with many audio formats such as Ogg Vorbis, FLAC, MP3, MP4/M4A, AAC, WAV, WMA and more.[2][3] fre:ac uses the CDex library to convert from CDs and uses freedb to retrieve artist/song information from the internet which is written to the files as various types of ID3 tags; this library supports cdparanoia which aims to improve audio quality.[4] The user interface is multilingual with 43 languages and is able to be a portable install on a USB drive. Metadata homepage URL: source URL: license: GNU General Public License v2.0 platforms: Windows, macOS, Linux, FreeBSD, HaikuOS
freac is already available on my nur repo If you want to avoid building it, it should be on my cachix https://scott- (for nixos-20.9, nixpkgs-unstable and nixos-unstable)


Question: , libiconv ? null, ncurses <del> , enableDwarf ? !stdenv.targetPlatform.isDarwin && !stdenv.targetPlatform.isWindows, elfutils # for DWARF support </del> , # GHC can be built with system libffi or a bundled one. libffi ? null

Our can no longer link executables. For example: This issue is present in current versions of . Compiling and linking works fine with an older revision, say . It looks like this might be related to some change in binutils, maybe?
This is probably from
Yes, it is. came to the same conclusion.
This probably is GHC bug though. Things like gmp and libiconv get their paths hardcoded so this isn't a problem. I would expect the same treatment for elfutils. should provide a arg.
/cc
I guess now I know why there's a patch in branch.
I'll reopen the PR fixing the linking issues.
I opened while we wait on upstream fix.
Which one, from
Yes, although it doesn't help. See
Yes, it would have surprised me a bit if it helped against that symptom -- my patch fixes that DWARF-enabling is skipped completely.
I'm surprised this worked for you back then and now there are linking errors.


Question: , tables , xlwt , runtimeShell <ins> , isPy38 </ins> , libcxx ? null }:

Describe the bug I cannot make a shell with pandas installed. To Reproduce Expected behavior A shell opens and works. Additional context <details<summaryI get this error message:</summary</detailsNotify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(noah): nixpkgs: Maintainer information:


Question: preFixup = '' patchelf --replace-needed liblttng-ust.so.0 liblttng-ust.so $out/lib/libcoreclrtraceptprovider.so patchelf --replace-needed libGraphicsMagick++-Q16.so.12 libGraphicsMagick++.so.12 $out/usr/lib/x86_64-linux-gnu/pcoip-client/vchan_plugins/libvchan-plugin-clipboard.so <ins> patchelf --replace-needed libhiredis.so.0.14 libhiredis.so $out/lib/libpcoip_core.so </ins> ''; installPhase = ''

Package name: aws-workspaces Latest released version: 4.5.0 <!-- Search your package here: --- Current version on the unstable channel: 4.1.0.1523 Current version on the stable/release channel: 4.1.0.1523 <!-- 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> systemd.user.generators = mkOption { type = types.attrsOf types.path; default = {}; example = { systemd-gpt-auto-generator = "/dev/null"; }; description = '' Definition of systemd generators; see {manpage}`systemd.generator(5)`. For each `NAME = VALUE` pair of the attrSet, a link is generated from `/etc/systemd/user-generators/NAME` to `VALUE`. ''; }; </ins> systemd.additionalUpstreamUserUnits = mkOption { default = []; type = types.listOf types.str;

Unable to use Podman's quadlets feature for a user, since the service unit files are not generated by systemd. Steps to reproduce the behavior: a quadlet file in (say, ) . Systemd says that no unit files were found. Caddy service should have been generated and its status displayed. This issue is caused by not symlinking the provided by the package to . Does not occur at the system level, since is already symlinked to Fix: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Confirmed the quadlet systemd user generator is not found in /etc/systemd. I'm gonna take this one and try to come up with a fix in NixOS module.


Question: runHook preBuild mvnDeps=$(cp -dpR ${fetchedMavenDeps}/.m2 ./ && chmod +w -R .m2 && pwd) <del> mvn package --offline "-Dmaven.repo.local=$mvnDeps/.m2" -P desktop,all-platforms </del> <ins> mvn package --offline "-Dmaven.repo.local=$mvnDeps/.m2" ${mvnParameters} </ins> runHook postBuild '';

The dbeaver package does not build on . Steps to reproduce the behavior: Dbeaver should build <details<summaryTruncated build log</summary<br</details


Question: , babel , buildPythonPackage , fetchFromGitLab <ins> , fetchpatch </ins> , pythonRelaxDepsHook , html2text , lxml

When used through the command line, complains about imports and fails. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've opened but haven't had the time to test it quite yet. If you get around to it before me feel free to merge it
I suggest another fix in


Question: systemd.services.garage = { description = "Garage Object Storage (S3 compatible)"; <del> after = [ "network.target" "network-online.target" ]; wants = [ "network.target" "network-online.target" ]; </del> <ins> after = [ "network.target" "network-online.target" ]; wants = [ "network.target" "network-online.target" ]; </ins> wantedBy = [ "multi-user.target" ]; <del> restartTriggers = [ configFile ] ++ (lib.optional (cfg.environmentFile != null) cfg.environmentFile); </del> <ins> restartTriggers = [ configFile ] ++ (lib.optional (cfg.environmentFile != null) cfg.environmentFile); </ins> serviceConfig = { ExecStart = "${cfg.package}/bin/garage server"; <del> StateDirectory = mkIf (hasPrefix "/var/lib/garage" cfg.settings.data_dir || hasPrefix "/var/lib/garage" cfg.settings.metadata_dir) "garage"; </del> <ins> StateDirectory = mkIf ( anyHasPrefix "/var/lib/garage" cfg.settings.data_dir || hasPrefix "/var/lib/garage" cfg.settings.metadata_dir ) "garage"; </ins> DynamicUser = lib.mkDefault true; ProtectHome = true; NoNewPrivileges = true;

Steps to reproduce the behavior: -rebuild test on settings.datadir = "/mnt/garage0"; resolves fine Tested on nixos24.05 but code of the module is unchanged in nixos_unstable. I'm using flakes as well Please run and paste the result.
Looks like doesn't apply, maybe should tinker a bit on my own
It looks like the option type was adjusted, but not the other code in the module that checks that value. Shouldn't be too hard to fix.


Question: <del> { stdenv, fetchurl, libpng }: </del> <ins> { stdenv, fetchurl, libpng, perl, perlPackages, makeWrapper }: </ins> stdenv.mkDerivation rec { name = "icoutils-0.31.0";

icoutils' extresso missing perl dependencies. install pkgs.icoutils and execute "extresso" in shell. This works(): NixOS 16.03


Question: patchExecutable genymotion patchExecutable player <del> patchExecutable qemu/x86_64/bin/qemu-img patchExecutable qemu/x86_64/bin/qemu-system-x86_64 </del> <ins> patchInterpreter qemu/x86_64/bin/qemu-img patchInterpreter qemu/x86_64/bin/qemu-system-x86_64 </ins> patchTool adb patchTool aapt

I used Genymotion for a long time on macOS but with Virtualbox. I switch to Linux/nixOS about 5 months ago and was pleasantly surprised to read Genymotion now supported the QEMU engine. Alas, myself and a few other of my friends were never able to get Genymotion to work using QEMU, which is the preferred Hypervisor. I've tried to source some help at but to no avail. Steps to reproduce the behavior: a running working QEMU installation. Presumably with at least 1 functional VM too Genymotion Genymotion, ensure QEMU is selected as the Hypervisor a random Android device, add it and run it. 'll first get a 'can't start virtual device' error trying to start the Android device again gives a 'Another QEMU process appears to be using the same resources' error I'd expect Genymotion to start the Android device using QEMU, naturally If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: ! !
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
! !
Duplicate of . Does the workaround in work for you?
I'm not really sure this is a duplicate but that's up to you. I'm not a coder so had no idea what to do with that old 'work-around' either. I had a colleague who kindly looked at it, spent some time, and turned it in to a flake which can be found at And now the broken Genymotion functions great with QEMU. Perhaps the flake code can help in fixing the package. Thanks for the pointer to the old work-around


Question: patchExecutable genymotion patchExecutable player <del> patchExecutable qemu/x86_64/bin/qemu-img patchExecutable qemu/x86_64/bin/qemu-system-x86_64 </del> <ins> patchInterpreter qemu/x86_64/bin/qemu-img patchInterpreter qemu/x86_64/bin/qemu-system-x86_64 </ins> patchTool adb patchTool aapt

Steps to reproduce the behavior: ... ... ... A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.
Hey have you ever made Genymotion work under Wayland ? For instance, on any other distribution ? I'm not sure the support for Wayland has dropped quite officially for Genymotion or I might be wrong, maybe there is no need since it's a QT based graphic interface and platform plugins do exist for Wayland nowadays. EDIT: To add more information, on ArchLinux, here is what I'm getting as an error you might want to share your exact genymotion logs I'm running Sway and I have the following env variables set : QTQPAPLATFORMTHEME="qt5ct" QTQPAPLATFORM=wayland #QTWAYLANDFORCEDPI=physical #QTWAYLANDDISABLEWINDOWDECORATION=1 XDGSESSIONTYPE=wayland XDGSESSIONDESKTOP=sway XDGCURRENTDESKTOP=sway
Okay so I made it work on my end but I'm not under NixOS/not using Genymotion installed from Nix, try
I have run with , but still get error. and this is the QT relate envs and this is XDG relate envs
Could you give a try and use every single platform listed here :
Also please share your genymotion logs, there might be more to the error in there And finally, please let us know your exact Desktop Environnement, Wayland is being used, I suppose.
One more thing, could you retry using xcb as a platform after having installed in the environnement ? EDIT : Also set So to sum up run :
I am using wayland + plasma, so I think the dependencies is ok and this is
This may not fix your issue, but try it with this : ! EDIT: Also are you running with an Nvidia GPU or not Wayland ? If yes, you should try everything related as well.


Question: patchExecutable genymotion patchExecutable player <del> patchExecutable qemu/x86_64/bin/qemu-img patchExecutable qemu/x86_64/bin/qemu-system-x86_64 </del> <ins> patchInterpreter qemu/x86_64/bin/qemu-img patchInterpreter qemu/x86_64/bin/qemu-system-x86_64 </ins> patchTool adb patchTool aapt

EDIT2: I've found this so I believe it should work, but something may be wrong, I may need to look at the Nix definition of the package and compare with the way it is packaged for ArchLinux and see if there is anything that could explain what's going on. ! There could be also issues regarding Wayland + Plasma : If you could try another desktop environment, maybe Sway if possible, if you cannot, I will give this a try in a VM under the latest NixOS when I have some time.
See this commit too this maybe a fix, that you don't have yet, maybe you have it already because it's been backported.
Could you please the run of the command ? And uploads the logs to a GitHub Gist. If you can't or are busy, let me know, I'll try to reproduce inside a VM and investigate.
This is the log
I know what causes this problem, because I have different qt version, so I have to add to , and it works for me, thanks for your patience and help
Should I make a PR?
Hm I'm not familiar with the process but I believe you should make a PR if you can or maybe let's tag the maintainer of Genymotion here ? I believe it is
Let's wait a week or 2, if he answers back and can make the PR then you can wait to close this issue once the PR gets merged.
Still relevant. Genymotion tries to load some Qt plugins from nixpkgs and fails for whatever reason. I was able to workaround it by doing . used to work before too but is failing now (and it's unclear why, since its effects are similar to , I guess genymotion still picks something from env vars besides plugins)
Hi! I'm there is seems no this issue on unstable, but I've found another one - Can't start virtual device: qemu libpixmin not found. Here is log: Should I create another issue?
That's weird, I believe you should open a new issue yes however I'm not sure if including as a dependency in the derivation of might fix your issue : Running outputs :
as the maintainer of genymotion's package in Nixpkgs any advice/idea, what's going wrong ?
Seems like you were trying to launch genymotion with qemu instead of virtualbox.


Question: patchExecutable genymotion patchExecutable player <del> patchExecutable qemu/x86_64/bin/qemu-img patchExecutable qemu/x86_64/bin/qemu-system-x86_64 </del> <ins> patchInterpreter qemu/x86_64/bin/qemu-img patchInterpreter qemu/x86_64/bin/qemu-system-x86_64 </ins> patchTool adb patchTool aapt

A while ago I managed to make qemu version working (at least on my machine) by adding some bloaty dependencies: I didn't test it on latest unstable, but you could give it a shot. It also workarounds that Qt issue via in wrapper.


Question: , gtk3 , libextractor , libgcrypt <ins> , libsodium </ins> , libxml2 , pkg-config , wrapGAppsHook

Describe the bug To Reproduce Steps to reproduce the behavior: ... ... ... Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Notify maintainers and edited it last Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
I really have no idea, contains it, even bumping gnunet-gtk to be the same release version still doesn't fix it.
Have you tried applying


Question: attr bash btrfs-progs <ins> cdrkit </ins> criu dnsmasq <ins> e2fsprogs getent </ins> gnutar gptfdisk gzip iproute2 iptables <ins> kmod lvm2 minio nftables </ins> qemu_kvm qemu-utils rsync squashfsTools <ins> thin-provisioning-tools </ins> util-linux virtiofsd xz

When tries to create a volume of type=block, it cannot be created due to the occurrence of . This is because is not registered in . Steps to reproduce the behavior: Create block type volume. If you check nixpkgs for lxd 5.20, you can see other package dependencies that are not present in incus. For example with lvm, this is expected to severely impact the lvm backend. (Currently, it cannot be confirmed because there is no lvm drive.) Can we change it in the same way as lxd? <!-- 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]:
Opened a PR to fix. Sorry about that. Not sure why I dropped these...


Question: mkdir -p $out/share/powershell cp -r * $out/share/powershell makeWrapper $out/share/powershell/pwsh $out/bin/pwsh --prefix ${platformLdLibraryPath} : "${stdenv.lib.makeLibraryPath libraries}"  <del> --set TERM xterm --set POWERSHELL_TELEMETRY_OPTOUT 1 </del> <ins> --set TERM xterm --set POWERSHELL_TELEMETRY_OPTOUT 1 --set DOTNET_CLI_TELEMETRY_OPTOUT 1 </ins> ''; dontStrip = true;

Cc (PowerShell maintainer) Describe the bug Powershell uses telemetry unless explicitly told not to do it. In addition to its own environment variable (already set in the wrapper), it should require another one to disable telemetry from the underlying .NET platform, i.e. should be set to To Reproduce Steps to reproduce the behavior: powershell with (assumes you have the unstable channel installed) it with and verify that it's not set (i.e. no output) Expected behavior should be set to : Additional context Example of PowerShell's own CI config that disables telemetry on Linux: This should be fairly easy to change here: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: Maintainer information:


Question: export TZ="$new_TZ" fi fi <ins> # udev event notifications don't work reliably inside containers. # SDL2 already tries to automatically detect flatpak and pressure-vessel # and falls back to inotify-based discovery [1]. We make SDL2 do the # same by telling it explicitly. # # [1] <https://github.com/libsdl-org/SDL/commit/8e2746cfb6e1f1a1da5088241a1440fd2535e321> export SDL_JOYSTICK_DISABLE_UDEV=1 </ins> '' + extraProfile; runScript = writeScript "steam-wrapper.sh" ''

Describe the bug I'm trying to get Steam big picture to work with , xbox wireless adapter and a couple of xbox controllers. But if Steam is already running and I turn on my controllers, they successfully connect to the dongle, but steam doesn't detect them. If i first turn on the controllers, and then i start Steam, it recognizes them and they work fine. xow: I couldn't use the service file provided by the package because it would never start. I read somewhere that systemd is picky with symlinks, so i defined it myself, now it's starting fine. I also had to blacklist else xow would crash. Steam: To Reproduce Steps to reproduce the behavior: sure xow is running fine Steam on steam controllers to see if they work (they dont) Additional context I think xow is working fine. I tried the latest version (0.5) and the last commit, importing udev rules from the package and adding them to I also tried adding my user to the group. It doesn't matter if steam is running in big picture or not, i also tried steam native, still not working. Metadata Edit: Steam won't detect controllers even when using the wire. And also i tested the controllers with and and they work as expected. So i'm pretty sure the issue must be with steam.
This might be an upstream problem with , have you tried using it on a non NixOS system? I also maintain (a kernel driver for Xbox controllers) and I don't have this problem with Steam. Maybe try to test if there's still a problem on your system with xpadneo?
You might also want to try enabling xow using the NixOS module instead of writing a custom service:
Yes, i have another system with Arch and it's working fine there. Steam detects controller connections even when it's already running. That's what i tried at first, but xow wouldn't start, the service was hanging in an state. And I think it might be because when importing the service from the package, nix is creating a symlink to the service and it might cause some issues.


Question: export TZ="$new_TZ" fi fi <ins> # udev event notifications don't work reliably inside containers. # SDL2 already tries to automatically detect flatpak and pressure-vessel # and falls back to inotify-based discovery [1]. We make SDL2 do the # same by telling it explicitly. # # [1] <https://github.com/libsdl-org/SDL/commit/8e2746cfb6e1f1a1da5088241a1440fd2535e321> export SDL_JOYSTICK_DISABLE_UDEV=1 </ins> '' + extraProfile; runScript = writeScript "steam-wrapper.sh" ''

Also I did some more tests with xow and controllers are working fine, , , this website https://gamepad- everywhere it works as expected, even Stardew Valley is able to detect them, but not Steam (well unless i restart it with controllers connected, then they are detected and working). It's really weird, I am able to pair them, xpadneo detects them, but they are totally unresponsive, everywhere. I uninstalled xow, and removed the wireless dongle when i tested this. Since xow it's working fine in browser with https://gamepad- and with some games, then udev rules should be fine , right? I would say it's an upstream issue with Steam, but it's working fine on Arch, so there might be some issues with some libs?
The xow NixOS module is fixed now. The problem was that NixOS specifically bypasses the Install section of service files and the module wasn't setting WantedBy for the service explicitly.
I am wih something similar here, I am using the gamepad via USB , before the config all software detected the control, and I was able to play without problems except for steam, which prevented me from using the big picture, after enabling this option I have the same behavior as steam for all applications, if I plug in the control it does not work until the next reboot. Any suggestions on where to debug to understand why this behavior? Dmesg and lsusb look ok.
Having a similar issue, since I'm not using xow or anything but kernel drivers: Steam isn't able to detect a hotplugged Xbox one wired controller. It works perfectly fine if I plug it in before starting Steam. I can also confirm this behavior works on Arch.
that's my situation too
I guess no news on this? :(
i'll take a look, probably something to do with udev rules. i dont have a xbox controller though, only a steam controller
This problem sufficiently annoys me at this point that if there are any instructions I can follow to provide information I'm happy to do so. Thanks for offering to look. I am currently in possession of 2 xbox controllers, several controllers that show up as xbox controllers, and some controllers that don't show up as xbox controllers. I have this issue with all these controllers to the best of my recollection.


Question: export TZ="$new_TZ" fi fi <ins> # udev event notifications don't work reliably inside containers. # SDL2 already tries to automatically detect flatpak and pressure-vessel # and falls back to inotify-based discovery [1]. We make SDL2 do the # same by telling it explicitly. # # [1] <https://github.com/libsdl-org/SDL/commit/8e2746cfb6e1f1a1da5088241a1440fd2535e321> export SDL_JOYSTICK_DISABLE_UDEV=1 </ins> '' + extraProfile; runScript = writeScript "steam-wrapper.sh" ''

the steam udev rules are almost the same as on other distros, though arch does i'll try borrowing a xbox controller. does this happen with only the xbox one or does it happen with 360 too
sadly i can't find a xbox one controller. the udev rules provided by the steam package are the same as on other distros, maybe it has something to do with our other udev rules. may also have something to do with bubblewrap
It seems to be related to linux usernamespaces which to my understanding remaps the id of the sender of udev events (from 0 to a big number) leading udev to ignore these messages if it's not zero. Running directly on my system and under (running as root and as a normal user) led me to believe this (). This issue may need to be fixed with bubblewrap, I don't think something can be done here. Unfortunately I don't have a solution :sweatsmile: PS : I don't know if fixing this issue will make everything work, .
these look related
I merged someone who has this issue please look into using the patched systemd with the steam fhsenv
I've just tested on latest NixOS unstable. A hotplugged Xbox One controller was successfully detected by Steam Big Picture. Thank you!
i haven't done anything that would have fixed this
Well that is exceptionally weird! Because it's definitely working for me, looks like an unrelated PR fixed it? This is straight out of my terminal, after starting Steam with no controller, disconnecting and connecting again:
This must be a change to how steam recognizes controllers. The program from still does not show events when started within There is still something odd: My joystick Logitech X52 HOTAS is recognized as a gamepad, while when I run steam packages on flatpak, it works properly. I don't know what they do differently in the flatpak version to get it working. Maybe using libgudev or a flatpak specific version of udev in the runtime packages? I have tested adding patched systemd to the fhs of steam, but this did not change anything (maybe some other udev library version was shadowing it)
I marked this as stale due to inactivity.