Question:
only returns the hostname, even when both and are set. Steps to reproduce the behavior: and . . should return the FQDN defined by and . The breakage happens when is used, which is now the default in NixOS after Stopping causes to return the correct value. reproduces the issue. It broke at , which is when became enabled by default. It's still broken on which is at time of writing. Possibly related issues:
This seems to happen because the resolution flow (when nscd is running) looks like: calls , which uses the nodename (), which is the short hostname then calls , which invokes the nss machinery gets the request and processes the request according to the NSS rules; on my NixOS system this is (from systemd) doesn't match (from systemd) does match, and returns a synthesized record; systemd internally determines the hostname for this using only the nodename, so unless the nodename is already the FQDN then we fail here, and it does this before checking /etc/hosts. I wonder if we can fix this by patching out the support in systemd-resolved for looking up the nodename, which will make it fall back to the result from /etc/hosts instead; on NixOS we can (probably) always assume that /etc/hosts will actually have the correct system hostname in it.
No, this is most likely We wanted to polish that PR in the next days, and once merged, bump our nixpkgs pin (and resurrect the upstreaming attempts). If you want, can you check if using nsncd from this PR fixes the problem for you?
Ah, actually, I think I'm just talking out of my ass. systemd-resolved seems to be able to cope with this properly when I query it over DNS, so it probably isn't to blame.
tests fail at that PR. Setting gets a successful build, which then passes the test in , but it fails on the test.
This is a pretty weird behavior. What's (likely) failing here is the IPv6 resolution of . The test does pass on some NixOS setup, like my desktop (and the Ubuntu CI) but does fail on my laptop. I'm still not sure what's happening, is present in . There's something wrong with some NixOS setup, it'd be nice to fix that as well. By any chance, did you disable systemd-resolved? Thanks for the heads up wrt. . I'll have a look today.
The behavior I described is from the Nix build environment. I used the nixpkgs derivation for nsncd and updated the source to the PR.

rustPlatform.buildRustPackage rec { pname = "nsncd"; <del> version = "unstable-2022-11-14"; </del> <ins> version = "unstable-2023-10-26"; # https://github.com/twosigma/nsncd/pull/71 has not been upstreamed # to twosigma/nsncd yet. Using the nix-community fork in the # meantime. </ins> src = fetchFromGitHub { owner = "nix-community"; repo = "nsncd"; <del> rev = "47e580f1db99603df6e212a2e62f18cc970cef40"; hash = "sha256-Nv3MYZcuYgD66BAGs3Tg37s086HAGsaDBFvELqQF3Tk="; </del> <ins> rev =  "d6513421f420e407248c6d0aee39ae2f861a7cec"; hash = "sha256-PykzwpPxMDHJOr2HubXuw+Krk9Jbi0E3M2lEAOXhx2M="; </ins> }; <del> cargoSha256 = "sha256-c1L6nEUBHw1YegmoRrI3WU/bF80Nzbz13hsGlNyBR9o="; </del> <ins> cargoSha256 = "sha256-cUM7rYXWpJ0aMiurXBp15IlxAmf/x5uiodxEqBPCQT0="; </ins> meta = with lib; { description = "the name service non-caching daemon";


Question:
Another security release for Exim: 4.96.2. See CC maintainers:
Part of the report also concerns libspf2. (For some reason, it has been filed against Exim instead...) The patch(es) should probably be cherry-picked as well onto helsinki-systems/libspf2 (the fork that we're using).

stdenv.mkDerivation rec { pname = "exim"; <del> version = "4.96.1"; </del> <ins> version = "4.96.2"; </ins> src = fetchurl { url = "https://ftp.exim.org/pub/exim/exim4/${pname}-${version}.tar.xz"; <del> hash = "sha256-k6wHVcMX4f276ozLcKhoh2vfMUhpKJHHKtD+gWdnAz0="; </del> <ins> hash = "sha256-A44yfo0ek9AFusm7Bv0irsRNUCiTDW2+iBetRLv8HeY="; </ins> }; enableParallelBuilding = true;


Question:
Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc
You can puts secrets in an additionnal initrd readable by root only, and use See
There is more generic option now, . We probably want to merge those.

a stable URL for Nixpkgs to use to package this proprietary software. </para> </listitem> <ins> <listitem> <para> The GRUB specific option <option>boot.loader.grub.extraInitrd</option> has been replaced with the generic option <option>boot.initrd.secrets</option>. This option creates a secondary initrd from the specified files, rather than using a manually created initrd file. </para> </listitem> </ins> </itemizedlist> </section>


Question:
Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc
You can puts secrets in an additionnal initrd readable by root only, and use See
There is more generic option now, . We probably want to merge those.

let efiSysMountPoint = if args.efiSysMountPoint == null then args.path else args.efiSysMountPoint; efiSysMountPoint' = replaceChars [ "/" ] [ "-" ] efiSysMountPoint; <ins> initrdSecrets = config.boot.initrd.secrets != {}; </ins> in pkgs.writeText "grub-config.xml" (builtins.toXML { splashImage = f cfg.splashImage;


Question:
Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc
You can puts secrets in an additionnal initrd readable by root only, and use See
There is more generic option now, . We probably want to merge those.

storePath = config.boot.loader.grub.storePath; bootloaderId = if args.efiBootloaderId == null then "NixOS${efiSysMountPoint'}" else args.efiBootloaderId; timeout = if config.boot.loader.timeout == null then -1 else config.boot.loader.timeout; <del> inherit efiSysMountPoint; </del> <ins> inherit efiSysMountPoint initrdSecrets; </ins> inherit (args) devices; inherit (efi) canTouchEfiVariables; inherit (cfg) version extraConfig extraPerEntryConfig extraEntries forceInstall useOSProber <del> extraEntriesBeforeNixOS extraPrepareConfig extraInitrd configurationLimit copyKernels </del> <ins> extraEntriesBeforeNixOS extraPrepareConfig configurationLimit copyKernels </ins> default fsIdentifier efiSupport efiInstallAsRemovable gfxmodeEfi gfxmodeBios; path = (makeBinPath ([ pkgs.coreutils pkgs.gnused pkgs.gnugrep pkgs.findutils pkgs.diffutils pkgs.btrfs-progs


Question:
Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc
You can puts secrets in an additionnal initrd readable by root only, and use See
There is more generic option now, . We probably want to merge those.

''; }; <del> extraInitrd = mkOption { type = types.nullOr types.path; default = null; example = "/boot/extra_initramfs.gz"; description = '' The path to a second initramfs to be supplied to the kernel. This ramfs will not be copied to the store, so that it can contain secrets such as LUKS keyfiles or ssh keys. This implies that rolling back to a previous configuration won't rollback the state of this file. ''; }; </del> useOSProber = mkOption { default = false; type = types.bool;


Question:
Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc
You can puts secrets in an additionnal initrd readable by root only, and use See
There is more generic option now, . We probably want to merge those.

{ path = "/boot"; inherit (cfg) devices; inherit (efi) efiSysMountPoint; } ]; <ins> boot.loader.supportsInitrdSecrets = true; </ins> system.build.installBootLoader = let install-grub-pl = pkgs.substituteAll {


Question:
Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc
You can puts secrets in an additionnal initrd readable by root only, and use See
There is more generic option now, . We probably want to merge those.

my $extraPerEntryConfig = get("extraPerEntryConfig"); my $extraEntries = get("extraEntries"); my $extraEntriesBeforeNixOS = get("extraEntriesBeforeNixOS") eq "true"; <del> my $extraInitrd = get("extraInitrd"); </del> <ins> my $initrdSecrets = get("initrdSecrets"); </ins> my $splashImage = get("splashImage"); my $configurationLimit = int(get("configurationLimit")); my $copyKernels = get("copyKernels") eq "true";


Question:
Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc
You can puts secrets in an additionnal initrd readable by root only, and use See
There is more generic option now, . We probably want to merge those.

if ($copyKernels == 0) { $grubStore = GrubFs($storePath); } <del> my $extraInitrdPath; if ($extraInitrd) { if (! -f $extraInitrd) { print STDERR "Warning: the specified extraInitrd " . $extraInitrd . " doesn't exist. Your system won't boot without it.n"; } $extraInitrdPath = GrubFs($extraInitrd); } </del> # Generate the header. my $conf .= "# Automatically generated.  DO NOT EDIT THIS FILE!n";


Question:
Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc
You can puts secrets in an additionnal initrd readable by root only, and use See
There is more generic option now, . We probably want to merge those.

my $kernel = copyToKernelsDir(Cwd::abs_path("$path/kernel")); my $initrd = copyToKernelsDir(Cwd::abs_path("$path/initrd")); <del> if ($extraInitrd) { $initrd .= " " .$extraInitrdPath->path; </del> <ins> # Include second initrd with secrets if ($initrdSecrets) { # Get last element of path $initrd =~ //([^/]+)$/; my $initrdSecretsPath = "$bootPath/kernels/$1-secrets"; $initrd .= " $initrd-secrets"; my $oldUmask = umask; # Make sure initrd is not world readable (won't work if /boot is FAT) umask 0137; my $initrdSecretsPathTemp = File::Temp::mktemp("$initrdSecretsPath.XXXXXXXX"); system("$path/append-initrd-secrets", $initrdSecretsPathTemp) == 0 or die "failed to create initrd secretsn"; rename $initrdSecretsPathTemp, $initrdSecretsPath or die "failed to move initrd secrets into placen"; umask $oldUmask; $copied{$initrdSecretsPath} = 1; </ins> } my $xen = -e "$path/xen.gz" ? copyToKernelsDir(Cwd::abs_path("$path/xen.gz")) : undef; # FIXME: $confName


Question:
Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc
You can puts secrets in an additionnal initrd readable by root only, and use See
There is more generic option now, . We probably want to merge those.

if ($copyKernels == 0) { $conf .= $grubStore->search . "n"; } <del> if ($extraInitrd) { $conf .= $extraInitrdPath->search . "n"; } </del> $conf .= "  $extraPerEntryConfign" if $extraPerEntryConfig; $conf .= "  multiboot $xen $xenParamsn" if $xen; $conf .= "  " . ($xen ? "module" : "linux") . " $kernel $kernelParamsn";


Question:
Package name: mautrix-googlechat Latest released version: 0.5.1 <!-- Search your package here: --- Current version on the unstable channel: 0.5.0 Current version on the stable/release channel: 0.5.0 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Thanks

, enableSqlite ? true }: python3.pkgs.buildPythonApplication rec { pname = "mautrix-googlechat"; <del> version = "unstable-2023-07-16"; </del> <ins> version = "0.5.1"; </ins> src = fetchFromGitHub { owner = "mautrix"; repo = "googlechat"; <del> rev = "f4cddafd474b12be09efd15c6652c04d0650458e"; sha256 = "sha256-WMJVAX5oUdYYuXoJKk7OoERR0LJM0Er5444xwqIUTm8="; </del> <ins> rev = "refs/tags/v${version}"; hash = "sha256-a/EWz/aCkBE6XdDpmZcx2Q7/xKNwGCiZUhZc9YIIDhU="; </ins> }; patches = [


Question: introduced a deprecation warning for the option. Upon following the warning and moving all options out of the option and removing it, the build fails with the following error: Steps to reproduce the behavior: the service without using the option the configuration Build succeeds. As a temporary workaround, I tried setting to an empty set but then borgmatic fails to parse the config file. <!-- 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.

config = mkIf cfg.enable { warnings = [] <del> ++ optional (cfg.settings != null && cfg.settings.location != null) </del> <ins> ++ optional (cfg.settings != null && cfg.settings ? location) </ins> "`services.borgmatic.settings.location` is deprecated, please move your options out of sections to the global scope" ++ optional (catAttrs "location" (attrValues cfg.configurations) != []) "`services.borgmatic.configurations.<name>.location` is deprecated, please move your options out of sections to the global scope"


Question:
Attempting to upgrade to kernel v6.5.x results in the arm64 prl-tools package (18.3.0-) failing to compile. Steps to reproduce the behavior: NixOS in a Parallels VM from kernel version v6.4.x to v6.5.x nixos-rebuild to complete without error Using allows an upgrade to succeed with no tools installed. Attempting an upgrade with the unstable version of (19.0.0-) results in a similar build error. Please run and paste the result.
Just noticed a new DMG is available with Linux 6.5 mentioned in the : Not sure how to patch locally to test this.
I've already opened for that.

in stdenv.mkDerivation (finalAttrs: { pname = "prl-tools"; <del> version = "19.0.0-54570"; </del> <ins> version = "19.1.0-54729"; </ins> # We download the full distribution to extract prl-tools-lin.iso from # => ${dmg}/Parallels Desktop.app/Contents/Resources/Tools/prl-tools-lin.iso src = fetchurl { url = "https://download.parallels.com/desktop/v${lib.versions.major finalAttrs.version}/${finalAttrs.version}/ParallelsDesktop-${finalAttrs.version}.dmg"; <del> hash = "sha256-y7UC+E5i2cxkOJ9nVI6aQAFJ5kTXv9uaZoMO4/SCS6k="; </del> <ins> hash = "sha256-Qo/6EuILu5i3hjhxecf3qfoMFEJHJZVY19tDIXDJiag="; </ins> }; hardeningDisable = [ "pic" "format" ];


Question:
Steps to reproduce the behavior: , or anything depending on it (my failure specifically was triggered by udiskie). Looks like the exact same issue that is being reported in Hydra, on the same hash: Seems similar to reports that it was generated with cython 0.29.3. Unfortunately also seems to be archived and a cursory check does not seem to show a fork floating around.
Related:
Update: I was able to rebuild udiskie successfully by changing its build input (and all respective downstream references) to , so I'm guessing this might have only surfaced now with the recent cut to python 3.11 (maybe ?)
Another comment looks like . I'm guessing we could do the same here.

<del> { lib, buildPythonPackage, fetchFromGitHub, keyutils, pytest-runner, pytest }: </del> <ins> { lib , buildPythonPackage , cython , fetchFromGitHub , keyutils , pytestCheckHook }: </ins> buildPythonPackage rec { pname = "keyutils";


Question:
Steps to reproduce the behavior: , or anything depending on it (my failure specifically was triggered by udiskie). Looks like the exact same issue that is being reported in Hydra, on the same hash: Seems similar to reports that it was generated with cython 0.29.3. Unfortunately also seems to be archived and a cursory check does not seem to show a fork floating around.
Related:
Update: I was able to rebuild udiskie successfully by changing its build input (and all respective downstream references) to , so I'm guessing this might have only surfaced now with the recent cut to python 3.11 (maybe ?)
Another comment looks like . I'm guessing we could do the same here.

substituteInPlace setup.py --replace '"pytest-runner"' "" ''; <ins> preBuild = '' cython keyutils/_keyutils.pyx ''; preCheck = '' rm -rf keyutils ''; </ins> buildInputs = [ keyutils ]; <del> nativeCheckInputs = [ pytest pytest-runner ]; </del> <ins> nativeBuildInputs = [ cython ]; nativeCheckInputs = [ pytestCheckHook ]; </ins> meta = { description = "A set of python bindings for keyutils";


Question: Package name: cardinal Latest released version: 23.10 Current version on the unstable channel: 23.09 Current version on the stable/release channel: 22.12 Notify maintainers Note for maintainers: Please tag this issue in your PR.

stdenv.mkDerivation rec { pname = "cardinal"; <del> version = "23.09"; </del> <ins> version = "23.10"; </ins> src = fetchurl { url = "https://github.com/DISTRHO/Cardinal/releases/download/${version}/cardinal+deps-${version}.tar.xz"; <del> hash = "sha256-q42ry47y4tTkUbejv6iN5jXcadXSSTPQ3omhMUevfqU="; </del> <ins> hash = "sha256-6Wt2sC7vdrz2Fkl08bNLfnGu+pAV7b5lZUmsx1wtJRE="; </ins> }; prePatch = ''


Question:
Vesktop opens up to a white screen. It cannot update from tray to latest version. I tried completely removing config files from Vencord but it doesn't change anything. Running Vesktop with flag --disable-gpu makes the Vesktop stuck at loading Steps to reproduce the behavior: Vesktop Launching Vesktop should open up the app normally ! Kernel: 6.5.7-xanmod1 Gpu: AMD (mesa 23.1.7)
vencorddesktop command doesn't output any logs. When doing update from the gui, it doesn't show anything. Only time it shows something is when i try updating from tray icon. The output is the following:
This is a problem with Vencord. It is currently broken with the curren versions of Discord (including the web app) We have to wait for upstream to fix these issues and release a new version of vencord
Alright, thank you for the fast response! Cheers
I encountered the same issue, and can confirm it is fixed when the system version of vencord is 1.6.0.

, buildWebExtension ? false }: let <del> version = "1.5.8"; gitHash = "544edce"; </del> <ins> version = "1.6.0"; gitHash = "ffe6bb1"; </ins> in buildNpmPackage rec { pname = "vencord";


Question:
Vesktop opens up to a white screen. It cannot update from tray to latest version. I tried completely removing config files from Vencord but it doesn't change anything. Running Vesktop with flag --disable-gpu makes the Vesktop stuck at loading Steps to reproduce the behavior: Vesktop Launching Vesktop should open up the app normally ! Kernel: 6.5.7-xanmod1 Gpu: AMD (mesa 23.1.7)
vencorddesktop command doesn't output any logs. When doing update from the gui, it doesn't show anything. Only time it shows something is when i try updating from tray icon. The output is the following:
This is a problem with Vencord. It is currently broken with the curren versions of Discord (including the web app) We have to wait for upstream to fix these issues and release a new version of vencord
Alright, thank you for the fast response! Cheers
I encountered the same issue, and can confirm it is fixed when the system version of vencord is 1.6.0.

owner = "Vendicated"; repo = "Vencord"; rev = "v${version}"; <del> hash = "sha256-cJ+8CKCET7Z2MebyrW5OQr50tvbDM3mkvEQQm3zSbdU="; </del> <ins> hash = "sha256-t4+8ybPzqcCtTSukBBgvbD7HiKG4K51WPVnJg0RQbs8="; </ins> }; ESBUILD_BINARY_PATH = lib.getExe (esbuild.overrideAttrs (final: _: {


Question:
Vesktop opens up to a white screen. It cannot update from tray to latest version. I tried completely removing config files from Vencord but it doesn't change anything. Running Vesktop with flag --disable-gpu makes the Vesktop stuck at loading Steps to reproduce the behavior: Vesktop Launching Vesktop should open up the app normally ! Kernel: 6.5.7-xanmod1 Gpu: AMD (mesa 23.1.7)
vencorddesktop command doesn't output any logs. When doing update from the gui, it doesn't show anything. Only time it shows something is when i try updating from tray icon. The output is the following:
This is a problem with Vencord. It is currently broken with the curren versions of Discord (including the web app) We have to wait for upstream to fix these issues and release a new version of vencord
Alright, thank you for the fast response! Cheers
I encountered the same issue, and can confirm it is fixed when the system version of vencord is 1.6.0.

npmRebuildFlags = [ "|| true" ]; makeCacheWritable = true; <del> npmDepsHash = "sha256-JeJjjrCfJMuxP9sVVkKJQ7bRCGu0jbGfiw78jS0r2Sg="; </del> <ins> npmDepsHash = "sha256-H2f6xdAa7fNETbQhIv+InCB7+O4nq0bx+RILjGjqXdY="; </ins> npmFlags = [ "--legacy-peer-deps" ]; npmBuildScript = if buildWebExtension then "buildWeb" else "build"; npmBuildFlags = [ "--" "--standalone" "--disable-updater" ];


Question:
Vesktop opens up to a white screen. It cannot update from tray to latest version. I tried completely removing config files from Vencord but it doesn't change anything. Running Vesktop with flag --disable-gpu makes the Vesktop stuck at loading Steps to reproduce the behavior: Vesktop Launching Vesktop should open up the app normally ! Kernel: 6.5.7-xanmod1 Gpu: AMD (mesa 23.1.7)
vencorddesktop command doesn't output any logs. When doing update from the gui, it doesn't show anything. Only time it shows something is when i try updating from tray icon. The output is the following:
This is a problem with Vencord. It is currently broken with the curren versions of Discord (including the web app) We have to wait for upstream to fix these issues and release a new version of vencord
Alright, thank you for the fast response! Cheers
I encountered the same issue, and can confirm it is fixed when the system version of vencord is 1.6.0.

{ "name": "vencord", <del> "version": "1.5.8", </del> <ins> "version": "1.6.0", </ins> "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "vencord", <del> "version": "1.5.8", </del> <ins> "version": "1.6.0", </ins> "license": "GPL-3.0-or-later", "dependencies": { "@sapphi-red/web-noise-suppressor": "0.3.3",


Question:
Vesktop opens up to a white screen. It cannot update from tray to latest version. I tried completely removing config files from Vencord but it doesn't change anything. Running Vesktop with flag --disable-gpu makes the Vesktop stuck at loading Steps to reproduce the behavior: Vesktop Launching Vesktop should open up the app normally ! Kernel: 6.5.7-xanmod1 Gpu: AMD (mesa 23.1.7)
vencorddesktop command doesn't output any logs. When doing update from the gui, it doesn't show anything. Only time it shows something is when i try updating from tray icon. The output is the following:
This is a problem with Vencord. It is currently broken with the curren versions of Discord (including the web app) We have to wait for upstream to fix these issues and release a new version of vencord
Alright, thank you for the fast response! Cheers
I encountered the same issue, and can confirm it is fixed when the system version of vencord is 1.6.0.

} }, "node_modules/@eslint-community/regexpp": { <del> "version": "4.9.1", "resolved": "https://registry.npmjs.org/@eslint-community/regexpp/-/regexpp-4.9.1.tgz", "integrity": "sha512-Y27x+MBLjXa+0JWDhykM3+JE+il3kHKAEqabfEWq3SDhZjLYb6/BHL/JKFnH3fe207JaXkyDo685Oc2Glt6ifA==", </del> <ins> "version": "4.10.0", "resolved": "https://registry.npmjs.org/@eslint-community/regexpp/-/regexpp-4.10.0.tgz", "integrity": "sha512-Cu96Sd2By9mCNTx2iyKOmq10v22jUVQv0lQnlGNy16oE9589yE+QADPbrMGCkA51cKZSg3Pu/aTJVTGfL/qjUA==", </ins> "dev": true, "engines": { "node": "^12.0.0 || ^14.0.0 || >=16.0.0"


Question:
Vesktop opens up to a white screen. It cannot update from tray to latest version. I tried completely removing config files from Vencord but it doesn't change anything. Running Vesktop with flag --disable-gpu makes the Vesktop stuck at loading Steps to reproduce the behavior: Vesktop Launching Vesktop should open up the app normally ! Kernel: 6.5.7-xanmod1 Gpu: AMD (mesa 23.1.7)
vencorddesktop command doesn't output any logs. When doing update from the gui, it doesn't show anything. Only time it shows something is when i try updating from tray icon. The output is the following:
This is a problem with Vencord. It is currently broken with the curren versions of Discord (including the web app) We have to wait for upstream to fix these issues and release a new version of vencord
Alright, thank you for the fast response! Cheers
I encountered the same issue, and can confirm it is fixed when the system version of vencord is 1.6.0.

"dev": true }, "node_modules/@types/node": { <del> "version": "18.18.6", "resolved": "https://registry.npmjs.org/@types/node/-/node-18.18.6.tgz", "integrity": "sha512-wf3Vz+jCmOQ2HV1YUJuCWdL64adYxumkrxtc+H1VUQlnQI04+5HtH+qZCOE21lBE7gIrt+CwX2Wv8Acrw5Ak6w==", "dev": true </del> <ins> "version": "18.18.7", "resolved": "https://registry.npmjs.org/@types/node/-/node-18.18.7.tgz", "integrity": "sha512-bw+lEsxis6eqJYW8Ql6+yTqkE6RuFtsQPSe5JxXbqYRFQEER5aJA9a5UH9igqDWm3X4iLHIKOHlnAXLM4mi7uQ==", "dev": true, "dependencies": { "undici-types": "~5.26.4" } </ins> }, "node_modules/@types/normalize-package-data": { "version": "2.4.3",


Question:
Vesktop opens up to a white screen. It cannot update from tray to latest version. I tried completely removing config files from Vencord but it doesn't change anything. Running Vesktop with flag --disable-gpu makes the Vesktop stuck at loading Steps to reproduce the behavior: Vesktop Launching Vesktop should open up the app normally ! Kernel: 6.5.7-xanmod1 Gpu: AMD (mesa 23.1.7)
vencorddesktop command doesn't output any logs. When doing update from the gui, it doesn't show anything. Only time it shows something is when i try updating from tray icon. The output is the following:
This is a problem with Vencord. It is currently broken with the curren versions of Discord (including the web app) We have to wait for upstream to fix these issues and release a new version of vencord
Alright, thank you for the fast response! Cheers
I encountered the same issue, and can confirm it is fixed when the system version of vencord is 1.6.0.

"dev": true }, "node_modules/@types/react": { <del> "version": "18.2.31", "resolved": "https://registry.npmjs.org/@types/react/-/react-18.2.31.tgz", "integrity": "sha512-c2UnPv548q+5DFh03y8lEDeMfDwBn9G3dRwfkrxQMo/dOtRHUUO57k6pHvBIfH/VF4Nh+98mZ5aaSe+2echD5g==", </del> <ins> "version": "18.2.33", "resolved": "https://registry.npmjs.org/@types/react/-/react-18.2.33.tgz", "integrity": "sha512-v+I7S+hu3PIBoVkKGpSYYpiBT1ijqEzWpzQD62/jm4K74hPpSP7FF9BnKG6+fg2+62weJYkkBWDJlZt5JO/9hg==", </ins> "dev": true, "dependencies": { "@types/prop-types": "*",


Question:
Vesktop opens up to a white screen. It cannot update from tray to latest version. I tried completely removing config files from Vencord but it doesn't change anything. Running Vesktop with flag --disable-gpu makes the Vesktop stuck at loading Steps to reproduce the behavior: Vesktop Launching Vesktop should open up the app normally ! Kernel: 6.5.7-xanmod1 Gpu: AMD (mesa 23.1.7)
vencorddesktop command doesn't output any logs. When doing update from the gui, it doesn't show anything. Only time it shows something is when i try updating from tray icon. The output is the following:
This is a problem with Vencord. It is currently broken with the curren versions of Discord (including the web app) We have to wait for upstream to fix these issues and release a new version of vencord
Alright, thank you for the fast response! Cheers
I encountered the same issue, and can confirm it is fixed when the system version of vencord is 1.6.0.

"through": "^2.3.8" } }, <ins> "node_modules/undici-types": { "version": "5.26.5", "resolved": "https://registry.npmjs.org/undici-types/-/undici-types-5.26.5.tgz", "integrity": "sha512-JlCMO+ehdEIKqlFxk6IfVoAUVmgz7cU7zD/h9XZ0qzeosSHmUJVOzSQvvYSYWXkFXC+IfLKSIffhv0sVZup6pA==", "dev": true }, </ins> "node_modules/union-value": { "version": "1.0.1", "resolved": "https://registry.npmjs.org/union-value/-/union-value-1.0.1.tgz",


Question:
So, whenever I open Player, it starts installing Roblox, finishes, and does nothing. Even when launched from the website, starts installing, finishes, and most likely just exits. Logs show nothing important. However, when trying open Studio, the error saying " not found". Steps to reproduce the behavior: the grapejuice package (just write grapejuice in the with pkgs section) wine-wayland package (not sure if it is required, however I did) Grapejuice (I used rofi (drun), but I suppose $ would work) the message box that pops out (from wine), press "Install" to install the wine-mono thingy press the Open RobloxPlayer button, or go into Player, Initialize and Install Roblox, the behavior is the same Roblox installing and doing nothing... I expected RobloxPlayer to actually open, not install and exit... <!-- --
This is already tracked in issue

<del> { lib , buildGoModule , fetchFromGitHub , makeBinaryWrapper , pkg-config , libGL , libxkbcommon , xorg , wayland , vulkan-headers , wine64Packages , fetchpatch , fetchFromGitLab , fetchurl , }: let stagingPatch = fetchFromGitLab { sha256 = "sha256-VQ4j4PuXRoXbCUZ16snVO+jRvuKD4Rjn14R7bhwdAco="; domain = "gitlab.winehq.org"; owner = "wine"; repo = "wine-staging"; rev = "v9.2"; }; wine = wine64Packages.staging.overrideDerivation (oldAttrs: { prePatch = '' patchShebangs tools cp -r ${stagingPatch}/patches ${stagingPatch}/staging . chmod +w patches patchShebangs ./patches/gitapply.sh python3 ./staging/patchinstall.py --destdir="$PWD" --all ''; patches = (oldAttrs.patches or [ ]) ++ [ (fetchurl { name = "childwindow.patch"; hash = "sha256-u3mDvlbhQnfh2tUKb8jNJA0tTcLIaKVLfY8ktJmeRns="; url = "https://raw.githubusercontent.com/flathub/org.vinegarhq.Vinegar/9f43ce33a691afb50562d95adfc6719a3b58ddb7/patches/wine/childwindow.patch"; }) (fetchpatch { name = "mouselock.patch"; hash = "sha256-0AGA4AQbxTL5BGVbm072moav7xVA3zpotYqM8pcEDa4="; url = "https://raw.githubusercontent.com/flathub/org.vinegarhq.Vinegar/9f43ce33a691afb50562d95adfc6719a3b58ddb7/patches/wine/mouselock.patch"; }) (fetchpatch { name = "segregrevert.patch"; hash = "sha256-+3Nld81nG3GufI4jAF6yrWfkJmsSCOku39rx0Hov29c="; url = "https://raw.githubusercontent.com/flathub/org.vinegarhq.Vinegar/9f43ce33a691afb50562d95adfc6719a3b58ddb7/patches/wine/segregrevert.patch"; }) ]; src = fetchFromGitLab rec { sha256 = "sha256-GlPH34dr9aHx7xvlcbtDMn/wrY//DP58ilXjhQXgihQ="; domain = "gitlab.winehq.org"; owner = "wine"; repo = "wine"; rev = "wine-9.2"; }; }); in buildGoModule rec { pname = "vinegar"; version = "1.7.5"; src = fetchFromGitHub { owner = "vinegarhq"; repo = "vinegar"; rev = "v${version}"; hash = "sha256-eU6xlmgz8X7q51GSkQlz/kEQgTzzXYw5P6Yr47f7hbs="; }; vendorHash = "sha256-O2AQFcJmYY3FtLXB3BPdzsplFbthYEyasfctpPOQVhs="; nativeBuildInputs = [ pkg-config makeBinaryWrapper ]; buildInputs = [ libGL libxkbcommon xorg.libX11 xorg.libXcursor xorg.libXfixes wayland vulkan-headers wine ]; buildPhase = '' runHook preBuild make PREFIX=$out runHook postBuild ''; installPhase = '' runHook preInstall make PREFIX=$out install runHook postInstall ''; postInstall = '' wrapProgram $out/bin/vinegar  --prefix PATH : ${lib.makeBinPath [wine]} ''; meta = with lib; { description = "Open-source, minimal, configurable, fast bootstrapper for running Roblox on Linux"; homepage = "https://github.com/vinegarhq/vinegar"; changelog = "https://github.com/vinegarhq/vinegar/releases/tag/v${version}"; mainProgram = "vinegar"; license = licenses.gpl3Only; platforms = [ "x86_64-linux" ]; maintainers = with maintainers; [ nyanbinary ]; }; } </del>


Question:
So, whenever I open Player, it starts installing Roblox, finishes, and does nothing. Even when launched from the website, starts installing, finishes, and most likely just exits. Logs show nothing important. However, when trying open Studio, the error saying " not found". Steps to reproduce the behavior: the grapejuice package (just write grapejuice in the with pkgs section) wine-wayland package (not sure if it is required, however I did) Grapejuice (I used rofi (drun), but I suppose $ would work) the message box that pops out (from wine), press "Install" to install the wine-mono thingy press the Open RobloxPlayer button, or go into Player, Initialize and Install Roblox, the behavior is the same Roblox installing and doing nothing... I expected RobloxPlayer to actually open, not install and exit... <!-- --
This is already tracked in issue

<del> { lib , fetchFromGitLab , gobject-introspection , pciutils , python3Packages , gtk3 , wrapGAppsHook3 , glib , cairo , desktop-file-utils , xdg-utils , xdg-user-dirs , gettext , winetricks , wine , glxinfo , xrandr , bash }: python3Packages.buildPythonApplication rec  { pname = "grapejuice"; version = "7.20.11"; src = fetchFromGitLab { owner = "BrinkerVII"; repo = "grapejuice"; rev = "v${version}"; hash = "sha256-sDw67Xseeak1v5x0daznfdeNQahDTj21AVvXmuZlsgg="; }; nativeBuildInputs = [ gobject-introspection desktop-file-utils glib wrapGAppsHook3 python3Packages.pip ]; buildInputs = [ cairo gettext gtk3 bash ]; propagatedBuildInputs = with python3Packages; [ psutil dbus-python pygobject3 packaging wheel setuptools requests unidecode click pydantic ]; dontWrapGApps = true; makeWrapperArgs = [ "--prefix PATH : ${lib.makeBinPath [ xdg-user-dirs wine winetricks pciutils glxinfo xrandr ]}" # make xdg-open overrideable at runtime "--suffix PATH : ${lib.makeBinPath [ xdg-utils ]}" ]; postPatch = '' substituteInPlace src/grapejuice_common/assets/desktop/grapejuice.desktop  --replace $GRAPEJUICE_EXECUTABLE "$out/bin/grapejuice"  --replace $GRAPEJUICE_GUI_EXECUTABLE "$out/bin/grapejuice-gui"  --replace $GRAPEJUICE_ICON grapejuice substituteInPlace src/grapejuice_common/assets/desktop/roblox-player.desktop  --replace $GRAPEJUICE_EXECUTABLE "$out/bin/grapejuice"  --replace $PLAYER_ICON "grapejuice-roblox-player" substituteInPlace src/grapejuice_common/assets/desktop/roblox-app.desktop  --replace $GRAPEJUICE_EXECUTABLE "$out/bin/grapejuice"  --replace $PLAYER_ICON "grapejuice-roblox-player" substituteInPlace src/grapejuice_common/assets/desktop/roblox-studio.desktop src/grapejuice_common/assets/desktop/roblox-studio-auth.desktop  --replace $GRAPEJUICE_EXECUTABLE "$out/bin/grapejuice"  --replace $STUDIO_ICON "grapejuice-roblox-studio" substituteInPlace src/grapejuice_common/paths.py  --replace 'return local_share() / "locale"' 'return Path("${placeholder "out"}/share/locale")' substituteInPlace src/grapejuice_common/models/settings_model.py  --replace 'default_wine_home: Optional[str] = ""' 'default_wine_home: Optional[str] = "${wine}"' substituteInPlace src/grapejuice_packaging/builders/linux_package_builder.py  --replace '"--no-dependencies",' '"--no-dependencies", "--no-build-isolation",' substituteInPlace src/grapejuice_packaging/packaging_resources/bin/grapejuice src/grapejuice_packaging/packaging_resources/bin/grapejuice-gui  --replace "/usr/bin/env python3" "${python3Packages.python.interpreter}" ''; installPhase = '' runHook preInstall PYTHONPATH=$(pwd)/src:$PYTHONPATH python3 -m grapejuice_packaging linux_package mkdir -p "$out" "$out/${python3Packages.python.sitePackages}" tar -xvf ./dist/linux_package/grapejuice-''${version}.tar.gz --strip-components=1 -C "$out" mv "$out/lib/python3/dist-packages/"* "$out/${python3Packages.python.sitePackages}" rmdir --ignore-fail-on-non-empty -p "$out/lib/python3/dist-packages" runHook postInstall ''; postFixup = '' patchShebangs "$out/bin/grapejuice{,-gui}" buildPythonPath "$out $pythonPath" for bin in grapejuice grapejuice-gui; do wrapProgram "$out/bin/$bin"  --prefix PYTHONPATH : "$PYTHONPATH:$(toPythonPath $out)"  ''${makeWrapperArgs[@]}  ''${gappsWrapperArgs[@]} done ''; # No tests doCheck = false; pythonImportsCheck = [ "grapejuice" ]; meta = with lib; { homepage = "https://gitlab.com/brinkervii/grapejuice"; description = "Simple Wine+Roblox management tool"; license = licenses.gpl3Plus; platforms = platforms.linux; maintainers = with maintainers; [ artturin helium ]; }; } </del>


Question:
So, whenever I open Player, it starts installing Roblox, finishes, and does nothing. Even when launched from the website, starts installing, finishes, and most likely just exits. Logs show nothing important. However, when trying open Studio, the error saying " not found". Steps to reproduce the behavior: the grapejuice package (just write grapejuice in the with pkgs section) wine-wayland package (not sure if it is required, however I did) Grapejuice (I used rofi (drun), but I suppose $ would work) the message box that pops out (from wine), press "Install" to install the wine-mono thingy press the Open RobloxPlayer button, or go into Player, Initialize and Install Roblox, the behavior is the same Roblox installing and doing nothing... I expected RobloxPlayer to actually open, not install and exit... <!-- --
This is already tracked in issue

gradle_5 = throw "gradle_5 has been removed because it's no longer being updated"; # Added 2023-01-17 grafana_reporter = grafana-reporter; # Added 2024-06-09 gr-ais = throw "'gr-ais' has been renamed to/replaced by 'gnuradio3_7.pkgs.ais'"; # Converted to throw 2023-09-10 <ins> grapefruit = throw "'grapefruit' was removed due to being blocked by Roblox, rendering the package useless"; # Added 2024-08-23 </ins> graylog = throw "graylog is now available in versions 3.3 up to 5.0. Please mind the upgrade path and choose the appropriate version. Direct upgrading from 3.3 to 4.3 or above is not supported"; # Added 2023-04-24 graylog-3_3 = throw "graylog 3.x is EOL. Please consider downgrading nixpkgs if you need an upgrade from 3.x to latest series."; # Added 2023-10-09 graylog-4_0 = throw "graylog 4.x is EOL. Please consider downgrading nixpkgs if you need an upgrade from 4.x to latest series."; # Added 2023-10-09


Question:
So, whenever I open Player, it starts installing Roblox, finishes, and does nothing. Even when launched from the website, starts installing, finishes, and most likely just exits. Logs show nothing important. However, when trying open Studio, the error saying " not found". Steps to reproduce the behavior: the grapejuice package (just write grapejuice in the with pkgs section) wine-wayland package (not sure if it is required, however I did) Grapejuice (I used rofi (drun), but I suppose $ would work) the message box that pops out (from wine), press "Install" to install the wine-mono thingy press the Open RobloxPlayer button, or go into Player, Initialize and Install Roblox, the behavior is the same Roblox installing and doing nothing... I expected RobloxPlayer to actually open, not install and exit... <!-- --
This is already tracked in issue

vikunja-frontend = throw "'vikunja-frontend' has been replaced by 'vikunja'"; # Added 2024-02-19 vimHugeX = vim-full; # Added 2022-12-04 vim_configurable = vim-full; # Added 2022-12-04 <ins> vinegar = throw "'vinegar' was removed due to being blocked by Roblox, rendering the package useless"; # Added 2024-08-23 </ins> virtmanager = throw "'virtmanager' has been renamed to/replaced by 'virt-manager'"; # Converted to throw 2023-09-10 virtmanager-qt = throw "'virtmanager-qt' has been renamed to/replaced by 'virt-manager-qt'"; # Converted to throw 2023-09-10 vivaldi-widevine = throw "'vivaldi-widevine' has been renamed to/replaced by 'widevine-cdm'"; # Added 2023-02-25


Question:
So, whenever I open Player, it starts installing Roblox, finishes, and does nothing. Even when launched from the website, starts installing, finishes, and most likely just exits. Logs show nothing important. However, when trying open Studio, the error saying " not found". Steps to reproduce the behavior: the grapejuice package (just write grapejuice in the with pkgs section) wine-wayland package (not sure if it is required, however I did) Grapejuice (I used rofi (drun), but I suppose $ would work) the message box that pops out (from wine), press "Install" to install the wine-mono thingy press the Open RobloxPlayer button, or go into Player, Initialize and Install Roblox, the behavior is the same Roblox installing and doing nothing... I expected RobloxPlayer to actually open, not install and exit... <!-- --
This is already tracked in issue

qtads = qt5.callPackage ../games/qtads { }; <del> grapejuice = callPackage ../games/grapejuice { wine = wineWowPackages.unstable; }; </del> graphwar = callPackage ../games/graphwar { }; gtypist = callPackage ../games/gtypist { };


Question:
I'm trying to use from nixpkgs on my laptop and use remote builders (buildbarn). This fails due to patches that are applied in nixpkgs. Vanilla Bazel has a hardcoded fallback path for bash () . This has the downside of not producing a working fallback for (bash from nixpkgs will default initialize as ). The workaround for this is to default initialize the path variables somewhere else. Currently, this is done . This works fine for local execution, since this is where this function is called. However, this function is never called for remote execution (it is a hack to override things for the local execution environment only). So when using Bazel from nixpkgs locally and enabling remote execution, the shell is set to a bash from nixpkgs during the analysis phase but the variable is explicitly left unset by many actions, leading to the PATH in bash being and resulting in errors when executing tools in a script. I think there are two possible solutions: when using remote execution, do not replace the hardcoded (this is probably not a great fix since it only works for FHS executors) instead of replacing with a regular bash from nixpkgs, add a little helper script that adds shell utils to . This way, any shell rule created by bazel has a minimal set of tools. use when turning on remote execution. This has the downside of only working when the remote builder has a shell in that path. See this for a detailed reproducer: Using bazel from nixpkgs should work with remote execution. Using this version of bazel with remote execution is becoming more viable due to <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- [^1]: [^2]:
got reverted, I'll reopen it.
Could we also remove the related patch here -, or is it still needed for some reason ?
To the best of my understanding, it should be sufficient to use a prepared bash (with tools in the PATH) and remove the patch you mentioned. Probably still a good idea to test this in practice!

, file , substituteAll , writeTextFile <ins> , writeShellApplication </ins> }: let


Question:
I'm trying to use from nixpkgs on my laptop and use remote builders (buildbarn). This fails due to patches that are applied in nixpkgs. Vanilla Bazel has a hardcoded fallback path for bash () . This has the downside of not producing a working fallback for (bash from nixpkgs will default initialize as ). The workaround for this is to default initialize the path variables somewhere else. Currently, this is done . This works fine for local execution, since this is where this function is called. However, this function is never called for remote execution (it is a hack to override things for the local execution environment only). So when using Bazel from nixpkgs locally and enabling remote execution, the shell is set to a bash from nixpkgs during the analysis phase but the variable is explicitly left unset by many actions, leading to the PATH in bash being and resulting in errors when executing tools in a script. I think there are two possible solutions: when using remote execution, do not replace the hardcoded (this is probably not a great fix since it only works for FHS executors) instead of replacing with a regular bash from nixpkgs, add a little helper script that adds shell utils to . This way, any shell rule created by bazel has a minimal set of tools. use when turning on remote execution. This has the downside of only working when the remote builder has a shell in that path. See this for a detailed reproducer: Using bazel from nixpkgs should work with remote execution. Using this version of bazel with remote execution is becoming more viable due to <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- [^1]: [^2]:
got reverted, I'll reopen it.
Could we also remove the related patch here -, or is it still needed for some reason ?
To the best of my understanding, it should be sufficient to use a prepared bash (with tools in the PATH) and remove the patch you mentioned. Probably still a good idea to test this in practice!

defaultShellPath = lib.makeBinPath defaultShellUtils; <ins> bashWithDefaultShellUtils = writeShellApplication { name = "bash"; runtimeInputs = defaultShellUtils; text = '' if [[ "$PATH" == "/no-such-path" ]]; then export PATH=${defaultShellPath} fi exec ${bash}/bin/bash "$@" ''; }; </ins> platforms = lib.platforms.linux ++ lib.platforms.darwin; system = if stdenv.hostPlatform.isDarwin then "darwin" else "linux";


Question:
I'm trying to use from nixpkgs on my laptop and use remote builders (buildbarn). This fails due to patches that are applied in nixpkgs. Vanilla Bazel has a hardcoded fallback path for bash () . This has the downside of not producing a working fallback for (bash from nixpkgs will default initialize as ). The workaround for this is to default initialize the path variables somewhere else. Currently, this is done . This works fine for local execution, since this is where this function is called. However, this function is never called for remote execution (it is a hack to override things for the local execution environment only). So when using Bazel from nixpkgs locally and enabling remote execution, the shell is set to a bash from nixpkgs during the analysis phase but the variable is explicitly left unset by many actions, leading to the PATH in bash being and resulting in errors when executing tools in a script. I think there are two possible solutions: when using remote execution, do not replace the hardcoded (this is probably not a great fix since it only works for FHS executors) instead of replacing with a regular bash from nixpkgs, add a little helper script that adds shell utils to . This way, any shell rule created by bazel has a minimal set of tools. use when turning on remote execution. This has the downside of only working when the remote builder has a shell in that path. See this for a detailed reproducer: Using bazel from nixpkgs should work with remote execution. Using this version of bazel with remote execution is becoming more viable due to <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- [^1]: [^2]:
got reverted, I'll reopen it.
Could we also remove the related patch here -, or is it still needed for some reason ?
To the best of my understanding, it should be sufficient to use a prepared bash (with tools in the PATH) and remove the patch you mentioned. Probably still a good idea to test this in practice!

# If you add more replacements here, you must change the grep above! # Only files containing /bin are taken into account. substituteInPlace "$path"  <del> --replace /bin/bash ${bash}/bin/bash  --replace "/usr/bin/env bash" ${bash}/bin/bash  </del> <ins> --replace /bin/bash ${bashWithDefaultShellUtils}/bin/bash  --replace "/usr/bin/env bash" ${bashWithDefaultShellUtils}/bin/bash  </ins> --replace "/usr/bin/env python" ${python3}/bin/python  --replace /usr/bin/env ${coreutils}/bin/env  --replace /bin/true ${coreutils}/bin/true


Question:
I'm trying to use from nixpkgs on my laptop and use remote builders (buildbarn). This fails due to patches that are applied in nixpkgs. Vanilla Bazel has a hardcoded fallback path for bash () . This has the downside of not producing a working fallback for (bash from nixpkgs will default initialize as ). The workaround for this is to default initialize the path variables somewhere else. Currently, this is done . This works fine for local execution, since this is where this function is called. However, this function is never called for remote execution (it is a hack to override things for the local execution environment only). So when using Bazel from nixpkgs locally and enabling remote execution, the shell is set to a bash from nixpkgs during the analysis phase but the variable is explicitly left unset by many actions, leading to the PATH in bash being and resulting in errors when executing tools in a script. I think there are two possible solutions: when using remote execution, do not replace the hardcoded (this is probably not a great fix since it only works for FHS executors) instead of replacing with a regular bash from nixpkgs, add a little helper script that adds shell utils to . This way, any shell rule created by bazel has a minimal set of tools. use when turning on remote execution. This has the downside of only working when the remote builder has a shell in that path. See this for a detailed reproducer: Using bazel from nixpkgs should work with remote execution. Using this version of bazel with remote execution is becoming more viable due to <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- [^1]: [^2]:
got reverted, I'll reopen it.
Could we also remove the related patch here -, or is it still needed for some reason ?
To the best of my understanding, it should be sufficient to use a prepared bash (with tools in the PATH) and remove the patch you mentioned. Probably still a good idea to test this in practice!

# bazel test runner include references to /bin/bash substituteInPlace tools/build_rules/test_rules.bzl  <del> --replace /bin/bash ${bash}/bin/bash </del> <ins> --replace /bin/bash ${bashWithDefaultShellUtils}/bin/bash </ins> for i in $(find tools/cpp/ -type f) do substituteInPlace $i  <del> --replace /bin/bash ${bash}/bin/bash </del> <ins> --replace /bin/bash ${bashWithDefaultShellUtils}/bin/bash </ins> done # Fixup scripts that generate scripts. Not fixed up by patchShebangs below. substituteInPlace scripts/bootstrap/compile.sh  <del> --replace /bin/bash ${bash}/bin/bash </del> <ins> --replace /bin/bash ${bashWithDefaultShellUtils}/bin/bash </ins> # add nix environment vars to .bazelrc cat >> .bazelrc <<EOF


Question:
I'm trying to use from nixpkgs on my laptop and use remote builders (buildbarn). This fails due to patches that are applied in nixpkgs. Vanilla Bazel has a hardcoded fallback path for bash () . This has the downside of not producing a working fallback for (bash from nixpkgs will default initialize as ). The workaround for this is to default initialize the path variables somewhere else. Currently, this is done . This works fine for local execution, since this is where this function is called. However, this function is never called for remote execution (it is a hack to override things for the local execution environment only). So when using Bazel from nixpkgs locally and enabling remote execution, the shell is set to a bash from nixpkgs during the analysis phase but the variable is explicitly left unset by many actions, leading to the PATH in bash being and resulting in errors when executing tools in a script. I think there are two possible solutions: when using remote execution, do not replace the hardcoded (this is probably not a great fix since it only works for FHS executors) instead of replacing with a regular bash from nixpkgs, add a little helper script that adds shell utils to . This way, any shell rule created by bazel has a minimal set of tools. use when turning on remote execution. This has the downside of only working when the remote builder has a shell in that path. See this for a detailed reproducer: Using bazel from nixpkgs should work with remote execution. Using this version of bazel with remote execution is becoming more viable due to <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- [^1]: [^2]:
got reverted, I'll reopen it.
Could we also remove the related patch here -, or is it still needed for some reason ?
To the best of my understanding, it should be sufficient to use a prepared bash (with tools in the PATH) and remove the patch you mentioned. Probably still a good idea to test this in practice!

in lib.optionalString stdenv.hostPlatform.isDarwin darwinPatches + genericPatches; <del> buildInputs = [buildJdk] ++ defaultShellUtils; </del> <ins> buildInputs = [buildJdk bashWithDefaultShellUtils] ++ defaultShellUtils; </ins> # when a command can’t be found in a bazel build, you might also # need to add it to `defaultShellPath`.


Question:
Building the python 3 protobuf package fails for me on macOS. Digging in (by launching ), the cause seems to be that calls instead of . The call above fails, but the same call works after replacing by . Similarly, works fine. That in turn matters because of in the / wrappers, because the system include path is missing in the case. System: mac OS 10.12.5 Nix version: nix-env (Nix) 1.11.8 Nixpkgs version: "17.09pre108299." Sandboxing enabled: grep: No such file or directory :) When digging in, I used a checkout of nixpkgs with hash , but it seems to make no difference.
seems related.
uses Python on Darwin and might help here.
I've had a look at the python setup tools: The relevant line is (rather: appears to be, I haven't tested this) which causes C++ source files to be compile with . Not sure whether this is the right or wrong thing to do... I see two reasonable ways to fix this bug, in a more principled way than : python distutils to compile C++ files using nixpkg to treat like with respect to and friends If 1. is the right thing to do, it might still be nice to work around the bug in another way for now.
I've also been bitten by this problem once: The core problem is that setuptools pretty much ignores the difference between CC and CXX. This however is not a problem on a standard mac xcode installation, as both and link the C++ standard library there. However our nix-clang does not link against the C++ standard library (and probably should not) and that's why you will encounter this problem every once in a while when dealing with darwin and c++ python extensions. I'm not an expert on the darwin-stdenv, so I wouldn't know how to fix this in a way that does not require hacking our ways around that problem. To hack around this problem you simply have to grep the pythonPackages for . There are a few packages that use a workaround that involves adding to the C-compile flags: See e.g. here:
However our nix-clang does not link against the C++ standard library (and probably should not) and that's why you will encounter this problem every once in a while when dealing with darwin and c++ python extensions. any clue how to solve this issue?
The problem does not seem all-too widespread, but there are a few instances:
Any reason we can't just change to use ? Seems like it would work on Linux just fine, and fix a bunch of other stuff.
I knew this was an issue in general (), but assumed the problem was something more complicated.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

{ stdenv, python, buildPythonPackage <del> , protobuf, google_apputils, pyext </del> <ins> , protobuf, google_apputils, pyext, libcxx </ins> , disabled, doCheck ? true }: with stdenv.lib;


Question:
Building the python 3 protobuf package fails for me on macOS. Digging in (by launching ), the cause seems to be that calls instead of . The call above fails, but the same call works after replacing by . Similarly, works fine. That in turn matters because of in the / wrappers, because the system include path is missing in the case. System: mac OS 10.12.5 Nix version: nix-env (Nix) 1.11.8 Nixpkgs version: "17.09pre108299." Sandboxing enabled: grep: No such file or directory :) When digging in, I used a checkout of nixpkgs with hash , but it seems to make no difference.
seems related.
uses Python on Darwin and might help here.
I've had a look at the python setup tools: The relevant line is (rather: appears to be, I haven't tested this) which causes C++ source files to be compile with . Not sure whether this is the right or wrong thing to do... I see two reasonable ways to fix this bug, in a more principled way than : python distutils to compile C++ files using nixpkg to treat like with respect to and friends If 1. is the right thing to do, it might still be nice to work around the bug in another way for now.
I've also been bitten by this problem once: The core problem is that setuptools pretty much ignores the difference between CC and CXX. This however is not a problem on a standard mac xcode installation, as both and link the C++ standard library there. However our nix-clang does not link against the C++ standard library (and probably should not) and that's why you will encounter this problem every once in a while when dealing with darwin and c++ python extensions. I'm not an expert on the darwin-stdenv, so I wouldn't know how to fix this in a way that does not require hacking our ways around that problem. To hack around this problem you simply have to grep the pythonPackages for . There are a few packages that use a workaround that involves adding to the C-compile flags: See e.g. here:
However our nix-clang does not link against the C++ standard library (and probably should not) and that's why you will encounter this problem every once in a while when dealing with darwin and c++ python extensions. any clue how to solve this issue?
The problem does not seem all-too widespread, but there are a few instances:
Any reason we can't just change to use ? Seems like it would work on Linux just fine, and fix a bunch of other stuff.
I knew this was an issue in general (), but assumed the problem was something more complicated.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

inherit (protobuf) name src; inherit disabled doCheck; <ins> # work around python distutils compiling C++ with $CC NIX_CFLAGS_COMPILE = stdenv.lib.optionalString stdenv.isDarwin "-I${libcxx}/include/c++/v1"; </ins> propagatedBuildInputs = [ protobuf google_apputils ]; buildInputs = [ google_apputils pyext ];


Question: Project description Gruvbox Plus icon pack for Linux desktops based on Gruvbox color theme. Metadata homepage URL: source URL: license: GPL-3.0 platforms: linux

githubId = 2147649; name = "Euan Kemp"; }; <ins> eureka-cpu = { email = "github.eureka@gmail.com"; github = "eureka-cpu"; githubId = 57543709; name = "Chris O'Brien"; }; </ins> evalexpr = { name = "Jonathan Wilkins"; email = "nixos@wilkins.tech";


Question: Project description Gruvbox Plus icon pack for Linux desktops based on Gruvbox color theme. Metadata homepage URL: source URL: license: GPL-3.0 platforms: linux

<ins> { lib , stdenvNoCC , fetchFromGitHub , gtk3 , breeze-icons , gnome-icon-theme , hicolor-icon-theme }: stdenvNoCC.mkDerivation { pname = "gruvbox-plus-icons"; version = "unstable-2023-12-07"; src = fetchFromGitHub { owner = "SylEleuth"; repo = "gruvbox-plus-icon-pack"; rev = "f3109979fe93b31ea14eb2d5c04247a895302ea0"; sha256 = "sha256-EijTEDkPmcDcMhCuL6fOWjU9eXFUwmeOEwfGlxadb1U="; }; nativeBuildInputs = [ gtk3 ]; propagatedBuildInputs = [ breeze-icons gnome-icon-theme hicolor-icon-theme ]; installPhase = '' runHook preInstall mkdir -p $out/share/icons cp -r Gruvbox-Plus-Dark $out/share/icons/ gtk-update-icon-cache $out/share/icons/Gruvbox-Plus-Dark runHook postInstall ''; dontDropIconThemeCache = true; dontBuild = true; dontConfigure = true; meta = with lib; { description = "Icon pack for Linux desktops based on the Gruvbox color scheme"; homepage = "https://github.com/SylEleuth/gruvbox-plus-icon-pack"; license = licenses.gpl3Only; platforms = platforms.linux; maintainers = with maintainers; [ eureka-cpu RGBCube ]; }; } </ins>


Question:
Currently we build with support for . Sonnet typically looks in for dictionaries That means it won't be able to find any dictionaries and thus spellchecking won't work.
Is this still a problem? It seems that hunspell paths are not hardcoded in hunspelldict.h anymore: But they are still hardcoded in
Yes, this is still a problem. It seems like we should disable hunspell and use aspell, which is configured correctly in NixOS.
I marked this as stale due to inactivity. →
I marked this with "good first bug" because I think we need only to change to depend on , and do some testing.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

{ mkDerivation, lib , extra-cmake-modules <del> , hunspell, qtbase, qttools </del> <ins> , aspell, qtbase, qttools </ins> }: mkDerivation {


Question:
Currently we build with support for . Sonnet typically looks in for dictionaries That means it won't be able to find any dictionaries and thus spellchecking won't work.
Is this still a problem? It seems that hunspell paths are not hardcoded in hunspelldict.h anymore: But they are still hardcoded in
Yes, this is still a problem. It seems like we should disable hunspell and use aspell, which is configured correctly in NixOS.
I marked this as stale due to inactivity. →
I marked this with "good first bug" because I think we need only to change to depend on , and do some testing.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

broken = builtins.compareVersions qtbase.version "5.7.0" < 0; }; nativeBuildInputs = [ extra-cmake-modules ]; <del> buildInputs = [ hunspell qttools ]; </del> <ins> buildInputs = [ aspell qttools ]; </ins> propagatedBuildInputs = [ qtbase ]; }


Question:
Lily and I talked about this in Matrix, this is the requested issue. Basically it all narrows down to this package lock: Steps to reproduce the behavior: it it hangs forever lock it works It should either give an error or just work. If it helps narrowing the npm version down, the package- was created in September of 2020 and was last changed in September of 2021.
To clarify a bit, this isn't something specific to older lockfiles, it just looks like there is a version spec format that our fetcher does not currently support, but probably should

packages.into_par_iter().try_for_each(|package| { eprintln!("{}", package.name); <del> let tarball = package.tarball()?; </del> <ins> let tarball = package .tarball() .map_err(|e| anyhow!("couldn't fetch {} at {}: {e:?}", package.name, package.url))?; </ins> let integrity = package.integrity().map(ToString::to_string); cache


Question:
Lily and I talked about this in Matrix, this is the requested issue. Basically it all narrows down to this package lock: Steps to reproduce the behavior: it it hangs forever lock it works It should either give an error or just work. If it helps narrowing the npm version down, the package- was created in September of 2020 and was last changed in September of 2021.
To clarify a bit, this isn't something specific to older lockfiles, it just looks like there is a version spec format that our fetcher does not currently support, but probably should

} if let UrlOrString::Url(v) = &package.version { <del> for (scheme, host) in [ ("github", "github.com"), ("bitbucket", "bitbucket.org"), ("gitlab", "gitlab.com"), ] { if v.scheme() == scheme { package.version = { let mut new_url = initial_url.clone(); new_url.set_host(Some(host))?; if v.path().ends_with(".git") { new_url.set_path(v.path()); } else { new_url.set_path(&format!("{}.git", v.path())); } new_url.set_fragment(v.fragment()); UrlOrString::Url(new_url) }; break; </del> <ins> if v.scheme() == "npm" { if let Some(UrlOrString::Url(ref url)) = &package.resolved { package.version = UrlOrString::Url(url.clone()); } } else { for (scheme, host) in [ ("github", "github.com"), ("bitbucket", "bitbucket.org"), ("gitlab", "gitlab.com"), ] { if v.scheme() == scheme { package.version = { let mut new_url = initial_url.clone(); new_url.set_host(Some(host))?; if v.path().ends_with(".git") { new_url.set_path(v.path()); } else { new_url.set_path(&format!("{}.git", v.path())); } new_url.set_fragment(v.fragment()); UrlOrString::Url(new_url) }; break; } </ins> } } }


Question:
Lily and I talked about this in Matrix, this is the requested issue. Basically it all narrows down to this package lock: Steps to reproduce the behavior: it it hangs forever lock it works It should either give an error or just work. If it helps narrowing the npm version down, the package- was created in September of 2020 and was last changed in September of 2021.
To clarify a bit, this isn't something specific to older lockfiles, it just looks like there is a version spec format that our fetcher does not currently support, but probably should

#[cfg(test)] mod tests { use super::{ <del> get_initial_url, to_new_packages, Hash, HashCollection, OldPackage, Package, UrlOrString, </del> <ins> get_initial_url, packages, to_new_packages, Hash, HashCollection, OldPackage, Package, UrlOrString, </ins> }; use std::{ cmp::Ordering,


Question:
Lily and I talked about this in Matrix, this is the requested issue. Basically it all narrows down to this package lock: Steps to reproduce the behavior: it it hangs forever lock it works It should either give an error or just work. If it helps narrowing the npm version down, the package- was created in September of 2020 and was last changed in September of 2021.
To clarify a bit, this isn't something specific to older lockfiles, it just looks like there is a version spec format that our fetcher does not currently support, but probably should

Some(Hash(String::from("sha512-foo"))) ); } <ins> #[test] fn parse_lockfile_correctly() { let packages = packages( r#"{ "name": "node-ddr", "version": "1.0.0", "lockfileVersion": 1, "requires": true, "dependencies": { "string-width-cjs": { "version": "npm:string-width@4.2.3", "resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz", "integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==", "requires": { "emoji-regex": "^8.0.0", "is-fullwidth-code-point": "^3.0.0", "strip-ansi": "^6.0.1" } } } }"#).unwrap(); assert_eq!(packages.len(), 1); assert_eq!( packages[0].resolved, Some(UrlOrString::Url( Url::parse("https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz") .unwrap() )) ); } </ins> }


Question: Package name: gdtoolkit Latest released version: 4.1.0 <!-- Search your package here: --- Current version on the unstable channel: 3.3.1 Current version on the stable/release channel: 3.3.1 <!-- 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 It's a bit of an odd situation because both Godot 3 and 4 are in use, so maybe this one should be renamed to gdtoolkit3 or the opposite for the time being. Haven't had any success yet trying to override the package on my own. <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.

<ins> { lib , python3 , fetchFromGitHub }: let python = python3.override { packageOverrides = self: super: { lark = super.lark.overridePythonAttrs (old: rec { # gdtoolkit needs exactly this lark version version = "0.8.0"; src = fetchFromGitHub { owner = "lark-parser"; repo = "lark"; rev = version; hash = "sha256-KN9buVlH8hJ8t0ZP5yefeYM5vH5Gg7a7TEDGKJYpozs="; fetchSubmodules = true; }; patches = [ ]; }); }; }; in python.pkgs.buildPythonApplication rec { pname = "gdtoolkit3"; version = "3.5.0"; # If we try to get using fetchPypi it requires GeoIP (but the package dont has that dep!?) src = fetchFromGitHub { owner = "Scony"; repo = "godot-gdscript-toolkit"; rev = version; hash = "sha256-cMGD5Xdf9ElS1NT7Q0NPB//EvUO0MI0VTtps5JRisZ4="; }; disabled = python.pythonOlder "3.7"; propagatedBuildInputs = with python.pkgs; [ docopt lark pyyaml setuptools ]; doCheck = true; nativeCheckInputs = with python.pkgs; [ pytestCheckHook hypothesis ]; preCheck = '' # The tests want to run the installed executables export PATH=$out/bin:$PATH # gdtoolkit tries to write cache variables to $HOME/.cache export HOME=$TMP ''; # The tests are not working on NixOS disabledTests = [ "test_cc_on_empty_file_succeeds" "test_cc_on_file_with_single_function_succeeds" ]; pythonImportsCheck = [ "gdtoolkit" "gdtoolkit.formatter" "gdtoolkit.linter" "gdtoolkit.parser" ]; meta = with lib; { description = "Independent set of tools for working with Godot's GDScript - parser, linter and formatter"; homepage = "https://github.com/Scony/godot-gdscript-toolkit"; license = licenses.mit; maintainers = with maintainers; [ shiryel tmarkus ]; }; } </ins>


Question: Package name: gdtoolkit Latest released version: 4.1.0 <!-- Search your package here: --- Current version on the unstable channel: 3.3.1 Current version on the stable/release channel: 3.3.1 <!-- 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 It's a bit of an odd situation because both Godot 3 and 4 are in use, so maybe this one should be renamed to gdtoolkit3 or the opposite for the time being. Haven't had any success yet trying to override the package on my own. <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.

<ins> { lib , python3 , fetchFromGitHub }: let python = python3.override { packageOverrides = self: super: { lark = super.lark.overridePythonAttrs (old: rec { # gdtoolkit needs exactly this lark version version = "1.1.9"; src = fetchFromGitHub { owner = "lark-parser"; repo = "lark"; rev = version; hash = "sha256-vDu+VPAXONY8J+A6oS7EiMeOMgzGms0nWpE+DKI1MVU="; fetchSubmodules = true; }; patches = [ ]; }); }; }; in python.pkgs.buildPythonApplication rec { pname = "gdtoolkit"; version = "4.2.2"; src = fetchFromGitHub { owner = "Scony"; repo = "godot-gdscript-toolkit"; rev = version; hash = "sha256-SvEKKuDnfxV+5AArg5ssrQzgIwRITdek4KYEs3d0n4Y="; }; disabled = python.pythonOlder "3.7"; propagatedBuildInputs = with python.pkgs; [ docopt lark pyyaml setuptools ]; doCheck = true; nativeCheckInputs = with python.pkgs; [ pytestCheckHook hypothesis ]; preCheck = '' # The tests want to run the installed executables export PATH=$out/bin:$PATH # gdtoolkit tries to write cache variables to $HOME/.cache export HOME=$TMP ''; # The tests are not working on NixOS disabledTestPaths = [ "tests/generated/test_expression_parsing.py" "tests/gdradon/test_executable.py" ]; pythonImportsCheck = [ "gdtoolkit" "gdtoolkit.formatter" "gdtoolkit.linter" "gdtoolkit.parser" ]; meta = with lib; { description = "Independent set of tools for working with Godot's GDScript - parser, linter and formatter"; homepage = "https://github.com/Scony/godot-gdscript-toolkit"; license = licenses.mit; maintainers = with maintainers; [ squarepear ]; }; } </ins>


Question: Package name: gdtoolkit Latest released version: 4.1.0 <!-- Search your package here: --- Current version on the unstable channel: 3.3.1 Current version on the stable/release channel: 3.3.1 <!-- 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 It's a bit of an odd situation because both Godot 3 and 4 are in use, so maybe this one should be renamed to gdtoolkit3 or the opposite for the time being. Haven't had any success yet trying to override the package on my own. <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.

<del> { lib , python3 , fetchFromGitHub , godot3-server }: let python = python3.override { packageOverrides = self: super: { lark = super.lark.overridePythonAttrs (old: rec { # gdtoolkit needs exactly this lark version version = "0.8.0"; src = fetchFromGitHub { owner = "lark-parser"; repo = "lark"; rev = version; hash = "sha256-KN9buVlH8hJ8t0ZP5yefeYM5vH5Gg7a7TEDGKJYpozs="; fetchSubmodules = true; }; patches = [ ]; }); }; }; in python.pkgs.buildPythonApplication rec { pname = "gdtoolkit"; version = "3.3.1"; # If we try to get using fetchPypi it requires GeoIP (but the package dont has that dep!?) src = fetchFromGitHub { owner = "Scony"; repo = "godot-gdscript-toolkit"; rev = version; sha256 = "13nnpwy550jf5qnm9ixpxl1bwfnhhbiys8vqfd25g3aim4bm3gnn"; }; disabled = python.pythonOlder "3.7"; propagatedBuildInputs = with python.pkgs; [ docopt lark pyyaml setuptools ]; doCheck = true; nativeCheckInputs = with python.pkgs; [ pytestCheckHook hypothesis godot3-server ]; preCheck = let godotServerMajorVersion = lib.versions.major godot3-server.version; gdtoolkitMajorVersion = lib.versions.major version; msg = '' gdtoolkit major version ${gdtoolkitMajorVersion} does not match godot-server major version ${godotServerMajorVersion}! gdtoolkit needs a matching godot-server for its tests. If you see this error, you can either: - disable doCheck for gdtoolkit, or - provide a compatible godot-server version to gdtoolkit" ''; in lib.throwIf (godotServerMajorVersion != gdtoolkitMajorVersion) msg '' # The tests want to run the installed executables export PATH=$out/bin:$PATH # gdtoolkit tries to write cache variables to $HOME/.cache export HOME=$TMP # Work around https://github.com/godotengine/godot/issues/20503 # Without this, Godot will complain about a missing project file touch project.godot # Remove broken test case # (hard to skip via disabledTests since the test name contains an absolute path) rm tests/potential-godot-bugs/multiline-subscription-expression.gd ''; pythonImportsCheck = [ "gdtoolkit" "gdtoolkit.formatter" "gdtoolkit.linter" "gdtoolkit.parser" ]; meta = with lib; { description = "Independent set of tools for working with Godot's GDScript - parser, linter and formatter"; homepage = "https://github.com/Scony/godot-gdscript-toolkit"; license = licenses.mit; maintainers = with maintainers; [ shiryel tmarkus ]; }; } </del>


Question: Package name: gdtoolkit Latest released version: 4.1.0 <!-- Search your package here: --- Current version on the unstable channel: 3.3.1 Current version on the stable/release channel: 3.3.1 <!-- 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 It's a bit of an odd situation because both Godot 3 and 4 are in use, so maybe this one should be renamed to gdtoolkit3 or the opposite for the time being. Haven't had any success yet trying to override the package on my own. <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.

godot-headless = throw "godot-headless has been renamed to godot3-headless to distinguish from version 4"; # Added 2023-07-16 godot-server = throw "godot-server has been renamed to godot3-server to distinguish from version 4"; # Added 2023-07-16 <ins> gdtoolkit = throw "gdtoolkit has been renamed to gdtoolkit_3 to distinguish from version 4"; # Added 2024-02-17 </ins> google-chrome-beta = throw "'google-chrome-beta' has been removed due to the lack of maintenance in nixpkgs. Consider using 'google-chrome' instead."; # Added 2023-10-18 google-chrome-dev = throw "'google-chrome-dev' has been removed due to the lack of maintenance in nixpkgs. Consider using 'google-chrome' instead."; # Added 2023-10-18 google-gflags = throw "'google-gflags' has been renamed to/replaced by 'gflags'"; # Converted to throw 2023-09-10


Question: Package name: gdtoolkit Latest released version: 4.1.0 <!-- Search your package here: --- Current version on the unstable channel: 3.3.1 Current version on the stable/release channel: 3.3.1 <!-- 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 It's a bit of an odd situation because both Godot 3 and 4 are in use, so maybe this one should be renamed to gdtoolkit3 or the opposite for the time being. Haven't had any success yet trying to override the package on my own. <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.

gdmap = callPackage ../tools/system/gdmap { }; <del> gdtoolkit = callPackage ../development/tools/gdtoolkit { }; </del> gef = callPackage ../development/tools/misc/gef { }; gelasio = callPackage ../data/fonts/gelasio { };


Question:
Package name: gitea Latest released version: 1.21.1 () <!-- Search your package here: --- Current version on the unstable channel: 1.20.5 Current version on the stable/release channel: 1.19.4 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers: <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
thanks. I've created:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

existing process, but will need to start that process from gdb (so it is a child). Or you can set `boot.kernel.sysctl."kernel.yama.ptrace_scope"` to 0. <ins> - Gitea 1.21 upgrade has several breaking changes, including: - Custom themes and other assets that were previously stored in `custom/public/*` now belong in `custom/public/assets/*` - New instances of Gitea using MySQL now ignore the `[database].CHARSET` config option and always use the `utf8mb4` charset, existing instances should migrate via the `gitea doctor convert` CLI command. </ins> - The `hardware.pulseaudio` module now sets permission of pulse user home directory to 755 when running in "systemWide" mode. It fixes [issue 114399](https://github.com/NixOS/nixpkgs/issues/114399).


Question:
Package name: gitea Latest released version: 1.21.1 () <!-- Search your package here: --- Current version on the unstable channel: 1.20.5 Current version on the stable/release channel: 1.19.4 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers: <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
thanks. I've created:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:

buildGoModule rec { pname = "gitea"; <del> version = "1.20.5"; </del> <ins> version = "1.21.1"; </ins> # not fetching directly from the git repo, because that lacks several vendor files for the web UI src = fetchurl { url = "https://dl.gitea.com/gitea/${version}/gitea-src-${version}.tar.gz"; <del> hash = "sha256-cH/AHsFXOdvfSfj9AZUd3l/RlYE06o1ByZu0vvGQuXw="; </del> <ins> hash = "sha256-5WEHUMQsQNgrglS+xJ4IWHUl0a6RLLPyx0l+ECJ4R9g="; </ins> }; vendorHash = null;


Question:
ssh2john produce error while trying to process ssh key Steps to reproduce the behavior: john in any way - ssh key with password - KALI: Please run and paste the result.
This seems like an upstream issue. See
This issue 2 years long! Can we bundle older python with john or apply workaround stated in mentioned issue?
In the meantime, I believe you should be able to work around this by overriding the python version locally:

{ lib, stdenv, fetchFromGitHub, openssl, nss, nspr, libkrb5, gmp, zlib, libpcap, re2 <del> , gcc, python3Packages, perl, perlPackages, makeWrapper, fetchpatch }: </del> <ins> , gcc, python3Packages, perl, perlPackages, makeWrapper, }: </ins> stdenv.mkDerivation rec { pname = "john"; <del> version = "1.9.0-jumbo-1"; </del> <ins> version = "rolling-2404"; </ins> src = fetchFromGitHub { owner = "openwall"; <del> repo = pname; rev = "1.9.0-Jumbo-1"; sha256 = "sha256-O1iPh5QTMjZ78sKvGbvSpaHFbBuVc1z49UKTbMa24Rs="; </del> <ins> repo = "john"; rev = "f9fedd238b0b1d69181c1fef033b85c787e96e57"; hash = "sha256-zvoN+8Sx6qpVg2JeRLOIH1ehfl3tFTv7r5wQZ44Qsbc="; </ins> }; <del> patches = [ (fetchpatch { name = "fix-gcc-11-struct-allignment-incompatibility.patch"; url = "https://github.com/openwall/john/commit/154ee1156d62dd207aff0052b04c61796a1fde3b.patch"; sha256 = "sha256-3rfS2tu/TF+KW2MQiR+bh4w/FVECciTooDQNTHNw31A="; }) (fetchpatch { name = "improve-apple-clang-pseudo-intrinsics-portability.patch"; url = "https://github.com/openwall/john/commit/c9825e688d1fb9fdd8942ceb0a6b4457b0f9f9b4.patch"; excludes = [ "doc/*" ]; sha256 = "sha256-hgoiz7IgR4f66fMP7bV1F8knJttY8g2Hxyk3QfkTu+g="; }) ]; </del> postPatch = '' sed -ri -e ' s!^(#defines+CFG_[A-Z]+_NAMEs+).*/!1"'"$out"'/etc/john/!


Question:
ssh2john produce error while trying to process ssh key Steps to reproduce the behavior: john in any way - ssh key with password - KALI: Please run and paste the result.
This seems like an upstream issue. See
This issue 2 years long! Can we bundle older python with john or apply workaround stated in mentioned issue?
In the meantime, I believe you should be able to work around this by overriding the python version locally:

description = "John the Ripper password cracker"; license = licenses.gpl2Plus; homepage = "https://github.com/openwall/john/"; <del> maintainers = with maintainers; [ offline matthewbauer ]; </del> <ins> maintainers = with maintainers; [ offline matthewbauer cherrykitten ]; </ins> platforms = platforms.unix; }; }


Question:
Package name: handbrake Latest released version: 1.7.3 Current version on the unstable channel: 1.6.1 Current version on the stable/release channel: 1.6.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Revised to 1.7.2 release
Revised to 1.7.3

, numactl , writeText # Processing, video codecs, containers <del> , ffmpeg_5-full </del> <ins> , ffmpeg-full </ins> , nv-codec-headers , libogg , x264


Question:
Package name: handbrake Latest released version: 1.7.3 Current version on the unstable channel: 1.6.1 Current version on the stable/release channel: 1.6.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Revised to 1.7.2 release
Revised to 1.7.3

# for now we disable GTK GUI support on Darwin. (It may be possible to remove # this restriction later.) , useGtk ? !stdenv.isDarwin <ins> , bzip2 , desktop-file-utils , meson , ninja </ins> , wrapGAppsHook , intltool , glib


Question:
Package name: handbrake Latest released version: 1.7.3 Current version on the unstable channel: 1.6.1 Current version on the stable/release channel: 1.6.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Revised to 1.7.2 release
Revised to 1.7.3

}: let <del> version = "1.6.1"; </del> <ins> version = "1.7.3"; </ins> src = fetchFromGitHub { owner = "HandBrake"; repo = "HandBrake"; rev = version; <del> sha256 = "sha256-0MJ1inMNA6s8l2S0wnpM2c7FxOoOHxs9u4E/rgKfjJo="; </del> <ins> hash = "sha256-4Q//UU/CPgWvhtpROfNPLzBvZlB02hbFe9Z9FA7mX04="; </ins> }; # Handbrake maintains a set of ffmpeg patches. In particular, these # patches are required for subtitle timing to work correctly. See: # https://github.com/HandBrake/HandBrake/issues/4029 <del> ffmpeg-version = "5.1.2"; ffmpeg-hb = ffmpeg_5-full.overrideAttrs (old: { </del> <ins> # base ffmpeg version is specified in: # https://github.com/HandBrake/HandBrake/blob/master/contrib/ffmpeg/module.defs ffmpeg-version = "6.1"; ffmpeg-hb = ffmpeg-full.overrideAttrs (old: { </ins> version = ffmpeg-version; src = fetchurl { url = "https://www.ffmpeg.org/releases/ffmpeg-${ffmpeg-version}.tar.bz2"; <del> hash = "sha256-OaC8yNmFSfFsVwYkZ4JGpqxzbAZs69tAn5UC6RWyLys="; </del> <ins> hash = "sha256-632j3n3TzkiplGq0R6c0a9EaOoXm77jyws5jfn9UdhE="; </ins> }; <del> patches = old.patches or [ ] ++ [ "${src}/contrib/ffmpeg/A01-qsv-libavfilter-qsvvpp-change-the-output-frame-s-width-a.patch" "${src}/contrib/ffmpeg/A02-qsv-configure-ensure-enable-libmfx-uses-libmfx-1.x.patch" "${src}/contrib/ffmpeg/A03-qsv-configure-fix-the-check-for-MFX_CODEC_VP9.patch" "${src}/contrib/ffmpeg/A04-qsv-remove-mfx-prefix-from-mfx-headers.patch" "${src}/contrib/ffmpeg/A05-qsv-load-user-plugin-for-MFX_VERSION-2.0.patch" "${src}/contrib/ffmpeg/A06-qsv-build-audio-related-code-when-MFX_VERSION-2.0.patch" "${src}/contrib/ffmpeg/A07-qsvenc-support-multi-frame-encode-when-MFX_VERSION-2.patch" "${src}/contrib/ffmpeg/A08-qsvenc-support-MFX_RATECONTROL_LA_EXT-when-MFX_VERSI.patch" "${src}/contrib/ffmpeg/A09-qsv-support-OPAQUE-memory-when-MFX_VERSION-2.0.patch" "${src}/contrib/ffmpeg/A10-qsv-configure-add-enable-libvpl-option.patch" "${src}/contrib/ffmpeg/A11-qsv-use-a-new-method-to-create-mfx-session-when-usin.patch" "${src}/contrib/ffmpeg/A12-qsv-fix-decode-10bit-hdr.patch" "${src}/contrib/ffmpeg/A13-mov-read-name-track-tag-written-by-movenc.patch" "${src}/contrib/ffmpeg/A14-movenc-write-3gpp-track-titl-tag.patch" "${src}/contrib/ffmpeg/A15-mov-read-3gpp-udta-tags.patch" "${src}/contrib/ffmpeg/A16-movenc-write-3gpp-track-names-tags-for-all-available.patch" "${src}/contrib/ffmpeg/A17-FFmpeg-devel-amfenc-Add-support-for-pict_type-field.patch" "${src}/contrib/ffmpeg/A18-dvdsubdec-fix-processing-of-partial-packets.patch" "${src}/contrib/ffmpeg/A19-ccaption_dec-return-number-of-bytes-used.patch" "${src}/contrib/ffmpeg/A20-dvdsubdec-return-number-of-bytes-used.patch" "${src}/contrib/ffmpeg/A21-dvdsubdec-use-pts-of-initial-packet.patch" "${src}/contrib/ffmpeg/A22-matroskaenc-aac-extradata-updated.patch" "${src}/contrib/ffmpeg/A23-ccaption_dec-fix-pts-in-real_time-mode.patch" "${src}/contrib/ffmpeg/A24-fix-eac3-dowmix.patch" "${src}/contrib/ffmpeg/A25-enable-truehd-pass.patch" "${src}/contrib/ffmpeg/A26-Update-the-min-version-to-1.4.23.0-for-AMF-SDK.patch" "${src}/contrib/ffmpeg/A27-avcodec-amfenc-Fixes-the-color-information-in-the-ou.patch" "${src}/contrib/ffmpeg/A28-avcodec-amfenc-HDR-metadata.patch" # This patch is not applying since ffmpeg 5.1.1, probably it was backported by upstream # "${src}/contrib/ffmpeg/A30-svt-av1-backports.patch" (fetchpatch { name = "vulkan-remove-extensions.patch"; url = "https://git.ffmpeg.org/gitweb/ffmpeg.git/commitdiff_plain/eb0455d64690"; hash = "sha256-qvLrb7b+9/bel8A2lZuSmBiJtHXsABw0Lvgn1ggnmCU="; }) </del> <ins> patches = (old.patches or [ ]) ++ [ "${src}/contrib/ffmpeg/A01-mov-read-name-track-tag-written-by-movenc.patch" "${src}/contrib/ffmpeg/A02-movenc-write-3gpp-track-titl-tag.patch" "${src}/contrib/ffmpeg/A03-mov-read-3gpp-udta-tags.patch" "${src}/contrib/ffmpeg/A04-movenc-write-3gpp-track-names-tags-for-all-available.patch" "${src}/contrib/ffmpeg/A05-dvdsubdec-fix-processing-of-partial-packets.patch" "${src}/contrib/ffmpeg/A06-dvdsubdec-return-number-of-bytes-used.patch" "${src}/contrib/ffmpeg/A07-dvdsubdec-use-pts-of-initial-packet.patch" "${src}/contrib/ffmpeg/A08-ccaption_dec-fix-pts-in-real_time-mode.patch" "${src}/contrib/ffmpeg/A09-matroskaenc-aac-extradata-updated.patch" "${src}/contrib/ffmpeg/A10-amfenc-Add-support-for-pict_type-field.patch" "${src}/contrib/ffmpeg/A11-amfenc-Fixes-the-color-information-in-the-ou.patch" "${src}/contrib/ffmpeg/A12-amfenc-HDR-metadata.patch" "${src}/contrib/ffmpeg/A13-libavcodec-amfenc-Fix-issue-with-missing-headers-in-.patch" "${src}/contrib/ffmpeg/A14-avcodec-add-ambient-viewing-environment-packet-side-.patch" "${src}/contrib/ffmpeg/A15-avformat-mov-add-support-for-amve-ambient-viewing-en.patch" "${src}/contrib/ffmpeg/A16-videotoolbox-dec-h264.patch" # patch to fix <https://github.com/HandBrake/HandBrake/issues/5011> # commented out because it causes ffmpeg's filter-pixdesc-p010le test to fail. # "${src}/contrib/ffmpeg/A17-libswscale-fix-yuv420p-to-p01xle-color-conversion-bu.patch" "${src}/contrib/ffmpeg/A18-qsv-fix-decode-10bit-hdr.patch" "${src}/contrib/ffmpeg/A19-ffbuild-common-use-gzip-n-flag-for-cuda.patch" </ins> ]; }); <ins> x265-hb = x265.overrideAttrs (old: { # nixpkgs' x265 sourceRoot is x265-.../source whereas handbrake's x265 patches # are written with respect to the parent directory instead of that source directory. # patches which don't cleanly apply are commented out. postPatch = (old.postPatch or "") + '' pushd .. # patch -p1 < ${src}/contrib/x265/A00-crosscompile-fix.patch patch -p1 < ${src}/contrib/x265/A01-threads-priority.patch patch -p1 < ${src}/contrib/x265/A02-threads-pool-adjustments.patch patch -p1 < ${src}/contrib/x265/A03-sei-length-crash-fix.patch patch -p1 < ${src}/contrib/x265/A04-ambient-viewing-enviroment-sei.patch # patch -p1 < ${src}/contrib/x265/A05-memory-leaks.patch popd ''; }); </ins> versionFile = writeText "version.txt" '' BRANCH=${versions.majorMinor version}.x DATE=1970-01-01 00:00:01 +0000


Question:
Package name: handbrake Latest released version: 1.7.3 Current version on the unstable channel: 1.6.1 Current version on the stable/release channel: 1.6.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Revised to 1.7.2 release
Revised to 1.7.3

# Use the Nix-provided libxml2 instead of the system-provided one. substituteInPlace libhb/module.defs  --replace /usr/include/libxml2 ${libxml2.dev}/include/libxml2 <ins> '' + optionalString useGtk '' substituteInPlace gtk/module.rules  --replace-fail '$(MESON.exe)' 'meson'  --replace-fail '$(NINJA.exe)' 'ninja'  # Force using nixpkgs dependencies substituteInPlace gtk/meson.build  --replace-fail "cc.find_library('bz2', dirs: hb_libdirs)" "cc.find_library('bz2')"  --replace-fail "cc.find_library('mp3lame', dirs: hb_libdirs)" "cc.find_library('mp3lame')"  --replace-fail  "hb_incdirs = include_directories(hb_dir / 'libhb', hb_dir / 'contrib/include')"  "hb_incdirs = include_directories(hb_dir / 'libhb')"  </ins> ''; nativeBuildInputs = [


Question:
Package name: handbrake Latest released version: 1.7.3 Current version on the unstable channel: 1.6.1 Current version on the stable/release channel: 1.6.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Revised to 1.7.2 release
Revised to 1.7.3

pkg-config python3 ] <del> ++ optionals useGtk [ intltool wrapGAppsHook ]; </del> <ins> ++ optionals useGtk [ desktop-file-utils intltool meson ninja wrapGAppsHook ]; </ins> buildInputs = [ a52dec


Question:
Package name: handbrake Latest released version: 1.7.3 Current version on the unstable channel: 1.6.1 Current version on the stable/release channel: 1.6.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Revised to 1.7.2 release
Revised to 1.7.3

speex svt-av1 x264 <del> x265 </del> <ins> x265-hb </ins> xz zimg ] ++ optional (!stdenv.isDarwin) numactl ++ optionals useGtk [ <ins> bzip2 </ins> dbus-glib glib gst_all_1.gst-plugins-base


Question:
Package name: handbrake Latest released version: 1.7.3 Current version on the unstable channel: 1.6.1 Current version on the stable/release channel: 1.6.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Revised to 1.7.2 release
Revised to 1.7.3

configureFlags = [ "--disable-df-fetch" "--disable-df-verify" <del> "--disable-gtk-update-checks" </del> ] ++ optional (!useGtk) "--disable-gtk" ++ optional useFdk "--enable-fdk-aac"


Question:
Package name: handbrake Latest released version: 1.7.3 Current version on the unstable channel: 1.6.1 Current version on the stable/release channel: 1.6.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Revised to 1.7.2 release
Revised to 1.7.3

# NOTE: 2018-12-27: Check NixOS HandBrake test if changing NIX_LDFLAGS = [ "-lx265" ]; <ins> # meson/ninja are used only for the subprojects, not the toplevel dontUseMesonConfigure = true; dontUseMesonInstall = true; dontUseNinjaBuild = true; dontUseNinjaInstall = true; </ins> makeFlags = [ "--directory=build" ]; <del> passthru.tests = { basic-conversion = </del> <ins> passthru = { # for convenience inherit ffmpeg-hb x265-hb; tests.basic-conversion = </ins> let # Big Buck Bunny example, licensed under CC Attribution 3.0. testMkv = fetchurl {


Question:
Package name: handbrake Latest released version: 1.7.3 Current version on the unstable channel: 1.6.1 Current version on the stable/release channel: 1.6.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Revised to 1.7.2 release
Revised to 1.7.3

HandBrakeCLI -i ${testMkv} -o test.mkv -e x264 -q 20 -B 160 test -e test.mkv ''; <del> version = testers.testVersion { package = self; command = "HandBrakeCLI --version"; }; </del> <ins> tests.version = testers.testVersion { package = self; command = "HandBrakeCLI --version"; }; </ins> }; meta = with lib; {


Question:
Package name: handbrake Latest released version: 1.7.3 Current version on the unstable channel: 1.6.1 Current version on the stable/release channel: 1.6.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Revised to 1.7.2 release
Revised to 1.7.3

license = licenses.gpl2Only; maintainers = with maintainers; [ Anton-Latukha wmertens ]; platforms = with platforms; unix; <del> broken = stdenv.isDarwin && lib.versionOlder stdenv.hostPlatform.darwinMinVersion "10.13"; </del> <ins> broken = stdenv.isDarwin;  # https://github.com/NixOS/nixpkgs/pull/297984#issuecomment-2016503434 </ins> }; }; in


Question:
Hi there I installed but the driver is not available on CUPS; the printer (Brother HL-1223WE) is detected correctly. My system is on . Steps to reproduce the behavior: to to add the printer on CUPS.
Submitted a with a fix for this issue.

substituteInPlace $out/opt/brother/Printers/HL1210W/cupswrapper/brother_lpdwrapper_HL1210W --replace /opt "$out/opt" <del> mkdir -p $out/lib/cups/filter </del> <ins> mkdir -p $out/lib/cups/filter $out/share/cups/model </ins> ln -s $out/opt/brother/Printers/HL1210W/cupswrapper/brother_lpdwrapper_HL1210W $out/lib/cups/filter/brother_lpdwrapper_HL1210W <del> ln -s $out/opt/brother/Printers/HL1210W/cupswrapper/brother-HL1210W-cups-en.ppd $out/lib/cups/filter/brother-HL1210W-cups-en.ppd </del> <ins> ln -s $out/opt/brother/Printers/HL1210W/cupswrapper/brother-HL1210W-cups-en.ppd $out/share/cups/model/ </ins> # cp brcupsconfig4 $out/opt/brother/Printers/HL1110/cupswrapper/ ln -s $out/opt/brother/Printers/HL1210W/cupswrapper/brcupsconfig4 $out/lib/cups/filter/brcupsconfig4


Question:
Package name: vcv-rack Latest released version: 2.4.1 Current version on the unstable channel: 2.4.0 Current version on the stable/release channel: 2.3.0 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]:
may be trying something with so I'll wait a bit
Honestly I have no idea what vcv-rack is, I just looked for a package I can update to test out a new feature for `nix-update. If you can, take this from from, feel free to update it.
Not sure if I'll have time in the next few weeks, so this is free to pick

, curl , fetchFromBitbucket , fetchFromGitHub <del> , fetchzip </del> , ghc_filesystem , glew , glfw


Question:
Package name: vcv-rack Latest released version: 2.4.1 Current version on the unstable channel: 2.4.0 Current version on the stable/release channel: 2.3.0 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]:
may be trying something with so I'll wait a bit
Honestly I have no idea what vcv-rack is, I just looked for a package I can update to test out a new feature for `nix-update. If you can, take this from from, feel free to update it.
Not sure if I'll have time in the next few weeks, so this is free to pick

, libjack2 , libpulseaudio , libsamplerate <del> , libXext , libXi </del> , makeDesktopItem , makeWrapper , pkg-config


Question:
Package name: vcv-rack Latest released version: 2.4.1 Current version on the unstable channel: 2.4.0 Current version on the stable/release channel: 2.3.0 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]:
may be trying something with so I'll wait a bit
Honestly I have no idea what vcv-rack is, I just looked for a package I can update to test out a new feature for `nix-update. If you can, take this from from, feel free to update it.
Not sure if I'll have time in the next few weeks, so this is free to pick

}; in stdenv.mkDerivation rec { <del> pname = "VCV-Rack"; version = "2.4.0"; </del> <ins> pname = "vcv-rack"; version = "2.4.1"; </ins> desktopItems = [ (makeDesktopItem {


Question:
Package name: vcv-rack Latest released version: 2.4.1 Current version on the unstable channel: 2.4.0 Current version on the stable/release channel: 2.3.0 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]:
may be trying something with so I'll wait a bit
Honestly I have no idea what vcv-rack is, I just looked for a package I can update to test out a new feature for `nix-update. If you can, take this from from, feel free to update it.
Not sure if I'll have time in the next few weeks, so this is free to pick

owner = "VCVRack"; repo = "Rack"; rev = "v${version}"; <del> sha256 = "0azrqyx5as4jmk9dxb7cj7x9dha81i0mm9pkvdv944qyccqwg55i"; </del> <ins> hash = "sha256-Gn/sFltLXX2mLv4dDqmr/UPd+JBXVkIZGwMI6Rm0Ih4="; </ins> }; patches = [


Question:
Package name: vcv-rack Latest released version: 2.4.1 Current version on the unstable channel: 2.4.0 Current version on the stable/release channel: 2.3.0 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]:
may be trying something with so I'll wait a bit
Honestly I have no idea what vcv-rack is, I just looked for a package I can update to test out a new feature for `nix-update. If you can, take this from from, feel free to update it.
Not sure if I'll have time in the next few weeks, so this is free to pick

cp -r ${fundamental-source} plugins/Fundamental/ chmod -R +rw plugins/Fundamental # will be used as build dir substituteInPlace plugin.mk --replace ":= all" ":= dist" <ins> substituteInPlace plugins/Fundamental/src/Logic.cpp  --replace  "LightButton<VCVBezelBig, VCVBezelLightBig<WhiteLight>>"  "struct rack::componentlibrary::LightButton<VCVBezelBig, VCVBezelLightBig<WhiteLight>>" </ins> # Fix reference to zenity substituteInPlace dep/osdialog/osdialog_zenity.c


Question: Building on macOS fails in the test phase, since the path to the nix-daemon's socket is longer than the maximum 108 characters. This is a combination of macOS (long TMPDIR set to the build directory). I'm not really sure whether this is more of a nixpkgs or a nix issue. The problem can be worked around by setting TMPDIR=/tmp manually, but it seems to me that that should not be required... Compare nix commit , which removed a workaround for this limitation. System: Darwin 16.6.0 Nix version: 1.11.11 (building nix-1.12pre5413_b4b1f452) Nixpkgs version: master as of 2017-07-04 Sandboxing enabled: no

doInstallCheck = true; <ins> # socket path becomes too long otherwise preInstallCheck = lib.optional stdenv.isDarwin "export TMPDIR=/tmp"; </ins> separateDebugInfo = stdenv.isLinux; crossAttrs = {