jiebi/CodeConvo huggingface dataset:
Change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: mednafen <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.26.1 (dated November 10, 2020) desired version: 1.29.0 (dated January 19, 2022) <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
<del> { lib, stdenv, fetchurl, pkg-config, freeglut, libGLU, libGL, libcdio, libjack2 , libsamplerate, libsndfile, libX11, SDL2, SDL2_net, zlib, alsa-lib }: </del> <ins> { lib , stdenv , fetchurl , SDL2 , SDL2_net , alsa-lib , flac , freeglut , libGL , libGLU , libX11 , libcdio , libjack2 , libsamplerate , libsndfile , pkg-config , zlib }: </ins> stdenv.mkDerivation rec { pname = "mednafen"; <del> version = "1.26.1"; </del> <ins> version = "1.29.0"; </ins> src = fetchurl { url = "https://mednafen.github.io/releases/files/${pname}-${version}.tar.xz"; <del> sha256 = "1x7xhxjhwsdbak8l0iyb497f043xkhibk73w96xck4j2bk10fac4"; </del> <ins> hash = "sha256-2j+88Ch3+b4PAov6XRy1npU6QEm5D+fjk4ijOG2fNi4="; </ins> }; nativeBuildInputs = [ pkg-config ]; buildInputs = [ <ins> SDL2 SDL2_net alsa-lib flac </ins> freeglut <del> libGLU libGL </del> <ins> libGL libGLU libX11 </ins> libcdio libjack2 <del> alsa-lib </del> libsamplerate libsndfile <del> libX11 SDL2 SDL2_net </del> zlib ];

''; meta = with lib; { <ins> homepage = "https://mednafen.github.io/"; </ins> description = "A portable, CLI-driven, SDL+OpenGL-based, multi-system emulator"; longDescription = '' Mednafen is a portable, utilizing OpenGL and SDL,

- Sega Saturn (experimental, x86_64 only) - Sony PlayStation ''; <del> homepage = "https://mednafen.github.io/"; license = licenses.gpl2; </del> <ins> license = licenses.gpl2Plus; </ins> maintainers = with maintainers; [ AndersonTorres ]; platforms = platforms.linux; };
Change:
On current master () and at least since : Importing fixes the first part, but breaks the vm build :disappointed: ... which is kind of expected. Importing fixes all the warnings. Is this the expected behavior? What has changed from one month ago where everything went fine without imports? nixos-version: (Flounder) nix-env --version: nix-env (Nix) 1.11.2 nix-instantiate --eval '<nixpkgs' -A lib.nixpkgsVersion: "16.09pre82105." /cc as you master the module import system :-).
No this is not the expected behaviour. This is indeed weird, as is the only module to define and options. Also, this module is supposed to be included by default in of . Are you able to bisect the config , and isolate the minimal set which cause the same error? And then bisect nixpkgs to find which commit cause this change?
I can reproduce it with . Git bisect points at , which look innocuous, but the commit contains a discussion about it triggering an infinite recursion, so maybe it induces a subtle breakage ?
Lost interest in this one... Let's close it for now.
Yes, the bisect sounds wrong.

Discussion:
See <xref linkend="sec-booting-from-pxe" /> for documentation.</para> </listitem> <ins> <listitem> <para>Xorg-server-1.18.*. If you choose <literal>"ati_unfree"</literal> driver, 1.17.* is still used due to ABI incompatibility.</para> </listitem> </ins> </itemizedlist> <para>The following new services were added since the last release:</para>
Change:
is broken on aarch64-darwin. This breaks packages like Relevant hydra build: Log from my own machine: <!-- 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.
Let's disable the broken test for now :

Discussion:
] ++ lib.optionals (stdenv.isDarwin && stdenv.isAarch64) [ # Flaky test: https://github.com/MagicStack/uvloop/issues/412 "--deselect" "tests/test_tcp.py::Test_UV_TCPSSL::test_shutdown_timeout_handler_not_set" <ins> # Broken: https://github.com/NixOS/nixpkgs/issues/160904 "--deselect" "tests/test_context.py::Test_UV_Context::test_create_ssl_server_manual_connection_lost" </ins> ]; disabledTestPaths = [
Change:
When you are installing NixOS and running , if you specify i.e. when current directory is , the script does not resolve the absolute path to the specified directory, so it does not generate file systems paths in . Steps to reproduce the behavior: to install NixOS how it's described in the guide the step with , proceed to directory and run instead Script resolves the path of argument and generates proper <img width="933" alt="Снимок экрана 2022-02-20 в 17 14 50" src="https://user-"Not applicable

Discussion:
$n++; $rootDir = $ARGV[$n]; die "$0: ‘--root’ requires an argumentn" unless defined $rootDir; <ins> die "$0: no need to specify `/` with `--root`, it is the defaultn" if $rootDir eq "/"; </ins> $rootDir =~ s//*$//; # remove trailing slashes <ins> $rootDir = File::Spec->rel2abs($rootDir); # resolve absolute path </ins> } elsif ($arg eq "--force") { $force = 1;

if ($showHardwareConfig) { print STDOUT $hwConfig; } else { <del> $outDir = "$rootDir$outDir"; </del> <ins> if ($outDir eq "/etc/nixos") { $outDir = "$rootDir$outDir"; } else { $outDir = File::Spec->rel2abs($outDir); $outDir =~ s//*$//; # remove trailing slashes } </ins> my $fn = "$outDir/hardware-configuration.nix"; print STDERR "writing $fn...n";
Change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.5.1 desired version: 1.7.8 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
buildGoModule rec { pname = "ghorg"; <del> version = "1.5.1"; </del> <ins> version = "1.7.8"; </ins> src = fetchFromGitHub { owner = "gabrie30"; repo = "ghorg"; <del> rev = version; sha256 = "sha256-HkOMG7VG8jyvr1W1T/62murtNYE8wyT/p3lDtuxfm5M="; </del> <ins> rev = "v${version}"; sha256 = "sha256-NZlPcr13onxgbmKPdv0ODOhYDT5T+OeSvHE8VGOGyo4="; </ins> }; doCheck = false;
Change:
After switching from 21.11 to unstable and a clean reboot ts3client crashes as soon as it tries to access the microphone. Steps to reproduce the behavior: to current unstable ts3client to a server or click Options -Recording -Test Not crash when using microphone Attached the coredump i am receiving. I am using pipewire in this context, but i can't circumscribe the issue on pipewire as other applications still work and are able to record without issues, also switching pipewire out and use pulseaudio seem not to solve the issue. I tried to overlay the package with libForQt512 (just playing around with it) as one of the differences between stable and unstable are version changes on qt libraries. But that did not fix anything. I have also tried the flatpack version, to check it there is something wrong with my pipewire config, but the flatpack version runs fine. Switching back the nixpkg from unstable to 21.11 and rebooting fixes the issue, so at least would tackle it down to changes related with changes in unstable. As stable and unstable ship the same ts3client version it has to be somehow related in between, or (hopefully not) just on my machine. I would not rule out that the issue is somewhere on my side. Please run and paste the result.
Running the version of a previous nixpkgs works just fine, even with an up-to-date environment. It must be a problem with the ts3 drv itself. I'll hopefully have time to run a bisect later.
Bad is which is a staging-next merge. Bisecting staging-next now...
Bad is . (Note: Injecting a cached qtwebengine saves a lot of time here and doesn't falsify results.)

Discussion:
{ lib, stdenv, fetchurl, makeWrapper, makeDesktopItem, zlib, glib, libpng, freetype, openssl , xorg, fontconfig, qtbase, qtwebengine, qtwebchannel, qtsvg, qtwebsockets, xkeyboard_config <del> , alsa-lib, libpulseaudio ? null, libredirect, quazip, which, unzip, llvmPackages, writeShellScriptBin </del> <ins> , alsa-lib, libpulseaudio ? null, libredirect, quazip, which, unzip, llvmPackages_10, writeShellScriptBin </ins> }: let

[ zlib glib libpng freetype xorg.libSM xorg.libICE xorg.libXrender openssl xorg.libXrandr xorg.libXfixes xorg.libXcursor xorg.libXinerama xorg.libxcb fontconfig xorg.libXext xorg.libX11 alsa-lib qtbase qtwebengine qtwebchannel qtsvg <del> qtwebsockets libpulseaudio quazip llvmPackages.libcxx llvmPackages.libcxxabi </del> <ins> qtwebsockets libpulseaudio quazip llvmPackages_10.libcxx llvmPackages_10.libcxxabi # llvmPackages_11 and higher crash https://github.com/NixOS/nixpkgs/issues/161395 </ins> ]; desktopItem = makeDesktopItem {
Change:
When using file picker in calibre e.g. on first launch after install that pops up file picker to select library path or by clicking "Add books" in menu calibre will crash with error Steps to reproduce the behavior: not yet crashed - select "Add books" item in menu Calibre should work without issues From i figured adding to solves problem, so running it like this works: Please run and paste the result.

Discussion:
, xdg-utils , removeReferencesTo , libstemmer <ins> , wrapGAppsHook </ins> }: mkDerivation rec { pname = "calibre"; <del> version = "5.34.0"; </del> <ins> version = "5.37.0"; </ins> src = fetchurl { url = "https://download.calibre-ebook.com/${version}/${pname}-${version}.tar.xz"; <del> hash = "sha256-1NQB7vrcU0hR308/8keUn/rHhdvJk5Ab0pOMPyiU1+M="; </del> <ins> hash = "sha256-x2u4v0k05WMATSsuo76NnqChIz8BcTuZfPkZa0uLnMY="; </ins> }; # https://sources.debian.org/patches/calibre/${version}+dfsg-1

dontUseQmakeConfigure = true; <del> nativeBuildInputs = [ pkg-config qmake removeReferencesTo ]; </del> <ins> nativeBuildInputs = [ pkg-config qmake removeReferencesTo wrapGAppsHook ]; </ins> buildInputs = [ chmlib

# Wrap manually dontWrapQtApps = true; <del> dontWrapGApps = true; </del> # Remove some references to shrink the closure size. This reference (as of # 2018-11-06) was a single string like the following:

for program in $out/bin/*; do wrapProgram $program  ''${qtWrapperArgs[@]}  <del> ''${gappsWrapperArgs[@]}  </del> --prefix PYTHONPATH : $PYTHONPATH  --prefix PATH : ${poppler_utils.out}/bin done
Change:
It appears to me that a number of cabal-install commands in cabal install 1.24 have a side effect of attempting to create which gets expanded to which fails. For example, installing fails with I am not entirely sure. Many Haskell libraries install just fine. I think the issue only occurs with things like ghcjs which attempt to invoke itself. This is the patch to cabal-install which I believe is responsible: In particular, is changed to call and is responsible for trying to create . A second data point is my helper: Previous I was able to use it in my to ensure that only files listed in the file were to the src But that also started failing with an error about not being able to create . I have no suggestions for a fix or a work around at this time.
I typically set to work around these kind of issues.
Does this issue still exist?
The issue still exists: If you write a Nix package that runs , you're going to have to be aware of it and apply the workaround. I opened a . If they're not interested in fixing it there, then I think we ought to reopen this as a documentation issue here.
Why would anyone call inside of a Nix build? Just run to achieve the same effect with way less moving parts involved.
Because one didn't know you could do that! Either way, documentation issue? :smiley:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

Discussion:
--replace "@CC@"     "${stdenv.cc}/bin/cc" ''; preBuild = '' <ins> export HOME="$TMP" </ins> local topDir=$out/lib/ghcjs-${version} mkdir -p $topDir
Change:
fails to build since The log produced is Build succeeds 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. --

Discussion:
, scipy , pytest , pybind11 <ins> , setuptools-scm </ins> }: buildPythonPackage rec {

sha256 = "48d9be622049d8363cda84125c45d18b89e0ab7d99be5a93c0246f375ebad344"; }; <ins> nativeBuildInputs = [ setuptools-scm ]; </ins> propagatedBuildInputs = [ numpy scipy

pybind11 ]; <del> preBuild = '' export HOME=$(mktemp -d) ''; </del> <ins> # failed with "ModuleNotFoundError: No module named 'pyamg.amg_core.evolution_strength'" doCheck = false; # taken from https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=python-pyamg#n27 # checkPhase = '' #   PYTHONPATH="$PWD/build/lib.linux-*:$PYTHONPATH" ${python3.interpreter} -c "import pyamg; pyamg.test()" # ''; pythonImportsCheck = [ "pyamg" "pyamg.amg_core.evolution_strength" ]; </ins> meta = with lib; { description = "Algebraic Multigrid Solvers in Python";
Change:
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

Discussion:
<ins> { lib , mkDerivation , fetchurl , extra-cmake-modules , kirigami2 , ktextwidgets , libksane , qtquickcontrols2 }: mkDerivation rec { pname = "skanpage"; version = "1.0.0"; src = fetchurl { url = "mirror://kde/stable/skanpage/${version}/${pname}-${version}.tar.xz"; hash = "sha256-kPVAG64oPkKF3ztHB4V7M2xc1AcvwiHnYpMMLMQNYGA="; }; nativeBuildInputs = [ extra-cmake-modules ]; buildInputs = [ kirigami2 ktextwidgets libksane qtquickcontrols2 ]; meta = with lib; { description = "KDE utility to scan images and multi-page documents"; homepage = "https://apps.kde.org/skanpage"; license = licenses.gpl2Plus; maintainers = with maintainers; [ samuelgrf ]; platforms = platforms.linux; }; } </ins>

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;
Change:
does not build as the dependency is not supported on . With set to true the dependency fails to build. System: OS X Darwin 15.5.0 x8664 Nix version: 1.11.2 Nixpkgs version: 16.09pre-git /cc

Discussion:
{ stdenv, fetchFromGitHub, cmake, gettext, glib, libmsgpack, libtermkey <del> , libtool, libuv, lua, luajit, luaPackages, man, ncurses, perl, pkgconfig </del> <ins> , libtool, libuv, luajit, luaPackages, man, ncurses, perl, pkgconfig </ins> , unibilium, makeWrapper, vimUtils, xsel , withPython ? true, pythonPackages, extraPythonPackages ? []

glib libtermkey libuv <del> # For some reason, `luajit` has to be listed after `lua`. See # https://github.com/NixOS/nixpkgs/issues/14442 lua luajit </del> libmsgpack ncurses neovimLibvterm unibilium <del> luaPackages.lpeg luaPackages.mpack luaPackages.luabitop ] ++ optional withJemalloc jemalloc; </del> <ins> luajit luaPackages.lua ] ++ optional withJemalloc jemalloc ++ lualibs; </ins> nativeBuildInputs = [ cmake

pkgconfig ]; <del> LUA_CPATH = "${luaPackages.lpeg}/lib/lua/${lua.luaversion}/?.so;${luaPackages.mpack}/lib/lua/${lua.luaversion}/?.so;${luaPackages.luabitop}/lib/lua/${lua.luaversion}/?.so"; </del> <ins> LUA_PATH = stdenv.lib.concatStringsSep ";" (map luaPackages.getLuaPath lualibs); LUA_CPATH = stdenv.lib.concatStringsSep ";" (map luaPackages.getLuaCPath lualibs); lualibs = [ luaPackages.mpack luaPackages.lpeg luaPackages.luabitop ]; </ins> <del> configureFlags = [ "-DCMAKE_BUILD_TYPE=RelWithDebInfo" "-DENABLE_JEMALLOC=ON" </del> <ins> cmakeFlags = [ "-DLUA_PRG=${luaPackages.lua}/bin/lua" </ins> ]; preConfigure = ''

inherit rev; sha256 = "1h3pbmykm69gfyi0wz647gz5836a6f3jc4azzll7i3mkpc11gcrd"; }; <ins> LIBTOOL = "libtool"; </ins> buildInputs = [ libtool ]; installPhase = '' mkdir -p $out/lib/libmpack

inherit lua; inherit (stdenv.lib) maintainers; <ins> # helper functions for dealing with LUA_PATH and LUA_CPATH getPath       = lib : type : "${lib}/lib/lua/${lua.luaversion}/?.${type};${lib}/share/lua/${lua.luaversion}/?.${type}"; getLuaPath    = lib : getPath lib "lua"; getLuaCPath   = lib : getPath lib "so"; </ins> #define build lua package function buildLuaPackage = callPackage ../development/lua-modules/generic lua;

preInstall = '' mkdir -p $out/lib/lua/${lua.luaversion} ''; <ins> NIX_CFLAGS_COMPILE = "-Wno-error -fpic"; </ins> installFlags = [ "USE_SYSTEM_LUA=yes" "LUA_VERSION_MAJ_MIN="
Change:
Is it possible to load additional python libraries when using sage. For example, if I want to load , how do I do so? <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Possible solution

Discussion:
{ pkgs , withDoc ? false <ins> , requireSageTests ? true , extraPythonPackages ? ps: [] </ins> }: # Here sage and its dependencies are put together. Some dependencies may be pinned

rpy2 sphinx pillow <del> ]; </del> <ins> ] ++ extraPythonPackages python3.pkgs; </ins> pythonEnv = python3.buildEnv.override { extraLibs = pythonRuntimeDeps;

# A wrapper around sage that makes sure sage finds its docs (if they were build). callPackage ./sage.nix { inherit sage-tests sage-with-env sagedoc jupyter-kernel-definition; <del> inherit withDoc; </del> <ins> inherit withDoc requireSageTests; </ins> }

, jupyter-kernel , sagedoc , withDoc <ins> , requireSageTests </ins> }: # A wrapper that makes sure sage finds its docs (if they were build) and the

buildInputs = [ makeWrapper <ins> ] ++ lib.optionals requireSageTests [ </ins> # This is a hack to make sure sage-tests is evaluated. It doesn't acutally # produce anything of value, it just decouples the tests from the build. sage-tests
Change:
libkrb5 (which is a rather central package in the dependency tree, unfortunately) fails to compile on Debian. That's because the system installation of tcl is (but cannot) be used: (this repeats hundreds of times) E.g. or or System: /etc/debian_version: 8.5 Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: (this command fails to run for me)
triage: does it still fail?

Discussion:
sha256 = "0z0jxm6ppbxi9anv2h12nrb5lpwl95f96kw6dx7sn268fhkpad7x"; }; <del> configureFlags = optional stdenv.isFreeBSD ''WARN_CFLAGS=""''; </del> <ins> configureFlags = [ "--with-tcl=no" ] ++ optional stdenv.isFreeBSD ''WARN_CFLAGS=""''; </ins> nativeBuildInputs = [ pkgconfig perl yacc ] # Provides the mig command used by the build scripts
Change:
libkrb5 (which is a rather central package in the dependency tree, unfortunately) fails to compile on Debian. That's because the system installation of tcl is (but cannot) be used: (this repeats hundreds of times) E.g. or or System: /etc/debian_version: 8.5 Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: (this command fails to run for me)
triage: does it still fail?

Discussion:
nativeBuildInputs = [ autoconf automake libtool bison ]; buildInputs = [ pcre ]; <ins> configureFlags = "--without-tcl"; </ins> postPatch = '' # Disable ccache documentation as it need yodl sed -i '/man1/d' CCache/Makefile.in
Change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: desired version: <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Discussion:
<del> { lib, stdenv </del> <ins> { lib , stdenv </ins> , fetchurl , rpmextract , patchelf

stdenv.mkDerivation rec { pname = "snowsql"; majorVersion = "1.2"; <del> version = "${majorVersion}.9"; </del> <ins> version = "${majorVersion}.21"; </ins> src = fetchurl { url = "https://sfc-repo.snowflakecomputing.com/snowsql/bootstrap/${majorVersion}/linux_x86_64/snowflake-snowsql-${version}-1.x86_64.rpm"; <del> sha256 = "1k9dyr4vyqivpg054kbvs0jdwhbqbmlp9lsyxgazdsviw8ch70c8"; </del> <ins> sha256 = "10pzxqk71amvaz951jl666ia6v0z22bgpvr108l3q62950hhhwmn"; </ins> }; nativeBuildInputs = [ rpmextract makeWrapper ];
Change:
I'm using NixOS "/ on tmpfs" mode, so I persist my dconf by using a module of home-manager. When I persist the state of GNOME app drawer, I need to write down desktop file name to .nix config. But currently, Android Studio's desktop contains a string of version, this because contains . Details: I also notice used in icon too, which will cause icon file contains version string, I think we can remove them too. If maintainer agrees, I will make a PR to deal with this. Also, I noticed another maintainer deleted the account: Maybe I can send him / her an E-mail for asking what happened, and drop the maintainer info.

Discussion:
}; desktopItem = makeDesktopItem { <del> name = drvName; </del> <ins> name = pname; </ins> exec = pname; <del> icon = drvName; </del> <ins> icon = pname; </ins> desktopName = "Android Studio (${channel} channel)"; comment = "The official Android IDE"; categories = [ "Development" "IDE" ];

echo -n "$startScript" > $out/bin/${pname} chmod +x $out/bin/${pname} <del> ln -s ${androidStudio}/bin/studio.png $out/share/pixmaps/${drvName}.png </del> <ins> ln -s ${androidStudio}/bin/studio.png $out/share/pixmaps/${pname}.png </ins> ln -s ${desktopItem}/share/applications $out/share/applications ''
Change:
when trying to build steam for aarch64 a bad error in another place is thrown Steps to reproduce the behaviour: accidentally add steam on aarch64-linux the trace ends up somewhere in the fhs builder bubble wrap scripts (happens when trying to add sublime to the set) i suspect setting platforms might work

Discussion:
{ makeScopeWithSplicing, generateSplicesForMkScope <del> , stdenv, buildFHSEnv, pkgsi686Linux </del> <ins> , stdenv, buildFHSEnv, pkgsi686Linux, glxinfo </ins> }: let

steam-runtime-wrapped = callPackage ./runtime-wrapped.nix { }; steam = callPackage ./steam.nix { }; steam-fhsenv = callPackage ./fhsenv.nix { <del> glxinfo-i686 = pkgsi686Linux.glxinfo; </del> <ins> glxinfo-i686 = if self.steamArch == "amd64" then pkgsi686Linux.glxinfo else glxinfo; </ins> steam-runtime-wrapped-i686 = if self.steamArch == "amd64" then pkgsi686Linux.steamPackages.steam-runtime-wrapped