jiebi/CodeConvo huggingface dataset:
Change:
pefile pyelftools python-registry <ins> pyyaml </ins> unicorn ];

Discussion:
seems to be missing a dependency which was introduced in 1.4.1 (the current version in nixpkgs, 1.4.2 has already been released, so probably should be updated). The build fails: I am puzzled how this slipped past the checks. Steps to reproduce the behavior: A clear and concise description of what you expected to happen. I am building on Fedora. system: multi-user?: sandbox: version: channels(): nixpkgs:
Change:
<ins> Submodule libultraship contains modified content diff --git a/libultraship/cmake/dependencies/common.cmake b/libultraship/cmake/dependencies/common.cmake index 596158c..c62d7b2 100644 --- a/libultraship/cmake/dependencies/common.cmake +++ b/libultraship/cmake/dependencies/common.cmake @@ -47,10 +47,6 @@ set(stormlib_optimizations_patch git apply ${CMAKE_CURRENT_SOURCE_DIR}/cmake/dep endif() #=================== STB =================== -set(STB_DIR ${CMAKE_BINARY_DIR}/_deps/stb) -file(DOWNLOAD "https://github.com/nothings/stb/raw/0bc88af4de5fb022db643c2d8e549a0927749354/stb_image.h" "${STB_DIR}/stb_image.h") -file(WRITE "${STB_DIR}/stb_impl.c" "#define STB_IMAGE_IMPLEMENTATIONn#include "stb_image.h"") - add_library(stb STATIC) target_sources(stb PRIVATE </ins>

Discussion:
Project description It's Shipwright but for Majora's Mask <!-- Describe the project a little: --Metadata homepage URL: source URL: license: cc0, unfree platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've got it to build, but the audio is all garbled and it crashes after a few seconds on the main menu. Will check against staging-next as upstream builds their binaries with SDL 2.30.3
For me it works flawlessly. Downloaded the appimage and used appimage-run though
My initial experiences were exactly what both prior comments described. Identical audio glitches and crash when building manually; flawless execution with the prebuilt appimage and appimage-run. Obviously I'd prefer to get the former working as well as the latter, but at least we know it is capable of running at all under the right conditions. We just need to figure out what exactly those conditions are.
It may have something to do with the software they're using. For example they use OpenGL for rendering, so digging into what they use for audio and then tinkering with it might help. I can't remember it off the top of my head, but it's certainly in the context menu if you emulate majora.
Weirdly enough, after installing home-manager with it, the appimage-run method sort of breaks it. It asks for the rom to be put in your home directory but then can't find it. Weird.
Using sudo on appimage-run gave a horrendous audio "host is down" error. I had to close kitty to stop it.
My bad, ALSA gave that error. It can't launch sdl_openaudio.
Doing it without sudo simply crashes it with an error message to send it to the discord.
Moved it back to documents. Cd'd into it. No sudo. Works!!! I was probably being stupid or something lmao
I'm using steam-run instead of appimage-run and it's working great with no obvious issues, but I'm by no means a Zelda expert. !
I've been able to reproduce this crash on Fedora 40. It's a slightly different traceback than building on NixOS, but involves the audio stack. Let's see what upstream thinks.
2ship doesn't segfault when built with :satisfied: Please test
Just built the pull request. Appears to run flawlessly.
Change:
++ optional noSysDirs ../no-sys-dirs.patch ++ optional langFortran ../gfortran-driving.patch ++ [ ../struct-ucontext.patch ../struct-sigaltstack-4.9.patch ] # glibc-2.26 <del> ; </del> <ins> # Retpoline patches pulled from the branch hjl/indirect/gcc-4_9-branch (by H.J. Lu, the author of GCC upstream retpoline commits) ++ builtins.map ({commit, sha256}: fetchpatch {url = "https://github.com/hjl-tools/gcc/commit/${commit}.patch"; inherit sha256;}) [{ commit = "e623d21608e96ecd6b65f0d06312117d20488a38"; sha256 = "1ix8i4d2r3ygbv7npmsdj790rhxqrnfwcqzv48b090r9c3ij8ay3"; } { commit = "2015a09e332309f12de1dadfe179afa6a29368b8"; sha256 = "0xcfs0cbb63llj2gbcdrvxim79ax4k4aswn0a3yjavxsj71s1n91"; } { commit = "6b11591f4494f705e8746e7d58b7f423191f4e92"; sha256 = "0aydyhsm2ig0khgbp27am7vq7liyqrq6kfhfi2ki0ij0ab1hfbga"; } { commit = "203c7d9c3e9cb0f88816b481ef8e7e87b3ecc373"; sha256 = "0wqn16y7wy5kg8ngfcni5qdwfphl01axczibbk49bxclwnzvldqa"; } { commit = "f039c6f284b2c9ce97c8353d6034978795c4872e"; sha256 = "13fkgdb17lpyxfksz1zanxhgpsm0jrss9w61nbl7an4im22hz7ci"; } { commit = "ed42606bdab1c5d9e5ad828cd6fe1a0557f193b7"; sha256 = "0gdnn8v3p03imj3qga2mzdhpgbmjcklkxdl97jvz5xia2ikzknxm"; } { commit = "5278e062ef292fd2fbf987d25389785f4c5c0f99"; sha256 = "0j81x758wf8v7j4rx5wc1cy7yhkvhlhv3wmnarwakxiwsspq0vrs"; } { commit = "76f1ffbbb6cd9f6ecde6c82cd16e20a27242e890"; sha256 = "1py56y6gp7fjf4f8bbsfwh5bs1gnmlqda1ycsmnwlzfm0cshdp0c"; } { commit = "4ca48b2b688b135c0390f54ea9077ef10aedd52c"; sha256 = "15r019pzr3k0lpgyvdc92c8fayw8b5lrzncna4bqmamcsdz7vsaw"; } { commit = "98c7bf9ddc80db965d69d61521b1c7a1cec32d9a"; sha256 = "1d7pfdv1q23nf0wadw7jbp6d6r7pnzjpbyxgbdfv7j1vr9l1bp60"; } { commit = "3dc76b53ad896494ca62550a7a752fecbca3f7a2"; sha256 = "0jvdzfpvfdmklfcjwqblwq1i22iqis7ljpvm7adra5d7zf2xk7xz"; } { commit = "1e961ed49b18e176c7457f53df2433421387c23b"; sha256 = "04dnqqs4qsvz4g8cq6db5id41kzys7hzhcaycwmc9rpqygs2ajwz"; } { commit = "e137c72d099f9b3b47f4cc718aa11eab14df1a9c"; sha256 = "1ms0dmz74yf6kwgjfs4d2fhj8y6mcp2n184r3jk44wx2xc24vgb2"; }]; </ins> javaEcj = fetchurl { # The `$(top_srcdir)/ecj.jar' file is automatically picked up at

Discussion:
Currently, the retpoline mitigation is only available in gcc7 . However, it still exists some old kernels that only compile with , such as those in Ubuntu Trusty LTS (kernel 3.13). Moreover, kernel modules loaded on these kernel have also to be compiled with the retpoline mitigation. Ubuntu (and Debian) integrated retpoline mitigation in their releases . Latest Ubuntu 3.13 kernel now requires kernel modules compiled with retpoline mitigation. They can no longer be built with Nix gcc toolchain. What do you think about backporting these patches? Someone could help on this?
sounds good to me.
Change:
# nix name, luarocks name, server, version,luaversion,maintainers <ins> alt-getopt,,,,,arobyn </ins> ansicolors,,,,, argparse,,,,, basexx,,,,,

Discussion:
In the process of trying to install pgmoon, I discovered than moonc wasn't available. Indeed, I can't find any reference in nixpkgs to except for an emacs mode. I can probably package this up, but I'm shocked to find that it's not already available; it's fairly obscure, but Nix has pretty good coverage. So I'll check to see if I'm just missing it (or if anyone has a nix expression for it handy) before spending the effort on it. Please run and paste the results. Odd....
Change:
Settlers II". It has a single player campaign mode, as well as a networked multiplayer mode. ''; <ins> changelog = "https://github.com/widelands/widelands/releases/tag/v1.1"; mainProgram = "widelands"; </ins> license = licenses.gpl2Plus; maintainers = with maintainers; [ raskin jcumming ]; platforms = platforms.linux;

Discussion:
name: widelands current version: 1.0 desired version: 1.1 maintainers: The widelands devs sent us an email about the release. I think this is a first for me.
I'm working on a PR for this (and once I figure out the github UI, I'll assign it to myself)..
Closing since fixes this. Please reopen if I'm wrong.
Change:
mesa nspr nss <del> opencv4 </del> <ins> opencv4' </ins> openssl' pango speex

Discussion:
Steps to reproduce the behavior: out current unstable: citrix-workspace: This also affects citrixworkspace23090 and citrixworkspace23070. system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Yeah, I ran into the same, unfortunately opencv is a massive expression, and the diff for the recent change was also massive, so inlining and overriding are IMO out. I ended up pulling opencv from a working commit ().
I observed the same issue yesterday and reached the same conclusion as Unfortunately, there is no newer version of Citrix Workspace available, leaving us with the November 2023 release that requires OpenCV 4.7. I attempted to use to enable compatibility with OpenCV 4.9, but alas without success. For now, it seems I will have to mark these packages as broken.
for anyone who has not had to mix nixpkgs versions before.
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:
Change:
heroic-unwrapped = callPackage ../games/heroic { # Match the version used by the upstream package. <del> electron = electron_29; </del> <ins> electron = electron_31; </ins> }; heroic = callPackage ../games/heroic/fhsenv.nix { };

Discussion:
Package name: heroic Latest released version: 2.15.1 <!-- Search your package here: --- Current version on the unstable channel: 2.14.1 Current version on the stable/release channel: 2.14.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 <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Need to wait for to be merged, because upstream depends on Electron 31, but the latest currently in nixpkgs is 30.
you can make draft PR and wait :D
Also does UMU need to be packaged for this release?
I think so. Even though Heroic 2.15 downloads UMU, the version it fetches is outdated, (according to one of the developers, in the project discord server).
Actually, given that , and Heroic can download a working version, just without the latest fixes, I am opting to not package UMU in nixpkgs.

Stardew Valley isn't opening in the nixpkgs' Heroic Launcher, and I think there're missing dependencies. Steps to reproduce the behavior: the Heroic Launcher and installs Stardew Valley from GOG running the game The game would open as usual The logs: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Stardew Valley depends on an outdated version of OpenSSL that is insecure IIRC (see also ) I just play the Windows version via Wine, also from Heroic Launcher (on the Steam Deck) and that works just fine, if it's acceptable to you I'd just do that instead of trying to hunt down an ancient version of a library.
Thanks for the explanation! Installing the Windows version worked as expected.
That turns out not to be the case here. I happen to own the GOG version of this game, so I was able to test this. It complains about missing ICU; once I that to the Heroic FHS environment, it launched just fine. Will submit a PR.
Change:
<del> { lib, stdenv, fetchFromGitHub, cmake, pkg-config </del> <ins> { lib, stdenv, fetchFromGitHub, cmake, pkg-config, fetchpatch </ins> , libusb1, rtl-sdr, soapysdr-with-plugins }:

Discussion:
, CVSSv3=5.5 (nixos-unstable) rtl433 21.12 was discovered to contain a stack overflow in the function acurite00275rm_decode at /devices/acurite.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted file. Scanned versions: nixos-unstable: . Cc
See also:
Change:
sha256 = "0nspf1bfq8zv7zmcmvkbgg3c90k10qcd56gyg8ln5z64nadvha9d"; }; <del> buildInputs = [ cmake pkgconfig libelf zlib curl elfutils python libiberty binutils ]; </del> <ins> preConfigure = "patchShebangs src/bin-to-c-source.py"; buildInputs = [ cmake pkgconfig zlib curl elfutils python libiberty binutils ]; </ins> meta = with stdenv.lib; { description = "code coverage tester for compiled programs, Python scripts and shell scripts";

Discussion:
The kcov package in nixpkgs is currently broken, as it is unable to find the dwarf debugging sections of executables. See this issue in kcov and notice that the problems happens whether using kcov through nixpkgs, or compiling it by hand on a nixos machine (so fixupPhase is not the culprit).
Change:
stdenv.mkDerivation rec { pname = "jetty"; <del> version = "9.4.41.v20210516"; </del> <ins> version = "9.4.43.v20210629"; </ins> src = fetchurl { url = "https://repo1.maven.org/maven2/org/eclipse/jetty/jetty-distribution/${version}/jetty-distribution-${version}.tar.gz"; <del> sha256 = "sha256-hFQC1UiqZbbvyMf1FC3eqvVga3QdPWh0fbotatkVHBI="; </del> <ins> sha256 = "sha256-AfrmVLCZMuRGAZqoWeevbgXifbreErVM17rjJJ/HI9k="; </ins> }; dontBuild = true;

Discussion:
, CVSSv3=5.3 (nixos-21.05, nixos-unstable) For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the content of the WEB-INF directory and/or bypass some security constraints. This is a variation of the vulnerability reported in CVE-2021-/GHSA-v7ff-8wcx-gmc5. Scanned versions: nixos-21.05: ; nixos-unstable: . Cc
Change:
libX11 = super.libX11.overrideAttrs (attrs: { outputs = [ "out" "dev" "man" ]; configureFlags = attrs.configureFlags or [] <del> ++ malloc0ReturnsNullCrossFlag; </del> <ins> ++ malloc0ReturnsNullCrossFlag ++ lib.optional (stdenv.targetPlatform.useLLVM or false) "ac_cv_path_RAWCPP=cpp"; </ins> depsBuildBuild = [ buildPackages.stdenv.cc ] ++ lib.optionals stdenv.hostPlatform.isStatic [

Discussion:
Steps to reproduce the behavior: Discovered via the Nixpkgs LLVM Workspace project. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --No maintainers, CC last person who touched Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
caFile = mkOption { type = types.nullOr types.path; default = null; <del> description = lib.mdDoc "SSL CA file path for client certificate verification."; </del> <ins> description = "SSL CA file path for client certificate verification."; </ins> }; logLevel = mkOption { type = types.int; default = 7; <del> description = lib.mdDoc "Set log level."; </del> <ins> description = "Set log level."; </ins> }; }; }; ###### implementation <del> config = mkIf cfg.enable { </del> <ins> config = lib.mkIf cfg.enable { </ins> assertions = [ { assertion = cfg.enableSSL -> cfg.certFile != null && cfg.keyFile != null && cfg.caFile != null; message = "SSL is enabled for ttyd, but no certFile, keyFile or caFile has been specified."; } <ins> { assertion = cfg.writeable != null; message = "services.ttyd.writeable must be set"; } </ins> { assertion = ! (cfg.interface != null && cfg.socket != null); message = "Cannot set both interface and socket for ttyd."; } { assertion = (cfg.username != null) == (cfg.passwordFile != null);

Discussion:
After a recent upgrade ( followed by ) the browser-based terminal in my setup, served with ttyd, no longer accepts user input (i.e. where the user can type and enter commands through the browser). Normally you are greeted with a terminal login screen and can enter username/password and log in, but it is now no longer possible to type or submit either. After researching, there is a breaking change in ttyd version =1.7.4, where the terminal is now readonly by default, users must pass or to get an interactive terminal. Note that the release notes appear to incorrectly indicate a lower-case flag, upper-case is needed. Consulting both the listed and the nixpkgs , there is no currently no way to pass this option. I am unsure who if anyone is the maintainer of this service, although I see that maintains the ttyd package. I will attempt to fix and submit a PR.
Change:
${values.preSetup} <del> ${ipPreMove} link add dev ${name} type wireguard ${optionalString (values.interfaceNamespace != null && values.interfaceNamespace != values.socketNamespace) "${ipPreMove} link set ${name} netns ${ns}"} </del> <ins> ${ipPreMove} link add dev "${name}" type wireguard ${optionalString (values.interfaceNamespace != null && values.interfaceNamespace != values.socketNamespace) ''${ipPreMove} link set "${name}" netns "${ns}"''} </ins> ${concatMapStringsSep "n" (ip: <del> "${ipPostMove} address add ${ip} dev ${name}" </del> <ins> ''${ipPostMove} address add "${ip}" dev "${name}"'' </ins> ) values.ips} <del> ${wg} set ${name} private-key ${privKey} ${ optionalString (values.listenPort != null) " listen-port ${toString values.listenPort}"} </del> <ins> ${concatStringsSep " " ( [ ''${wg} set "${name}" private-key "${privKey}"'' ] ++ optional (values.listenPort != null) ''listen-port "${toString values.listenPort}"'' )} </ins> <del> ${ipPostMove} link set up dev ${name} </del> <ins> ${ipPostMove} link set up dev "${name}" </ins> ${values.postSetup} ''; postStop = '' <del> ${ipPostMove} link del dev ${name} </del> <ins> ${ipPostMove} link del dev "${name}" </ins> ${values.postShutdown} ''; };

Discussion:
On NixOS 20.09, steps to reproduce the behavior: setting up wireguard, change to another port still shows the old port:
This seems to be fixed by my PR
Change:
substituteInPlace hooks/dhcpcd-run-hooks.in --replace /bin/sh ${runtimeShell} ''; <ins> patches = [ (fetchpatch { url = "https://roy.marples.name/cgit/dhcpcd.git/patch/?id=114870290a8d3d696bc4049c32eef3eed03d6070"; sha256 = "0kzpwjh2gzvl5lvlnw6lis610p67nassk3apns68ga2pyxlky8qb"; }) ]; </ins> preConfigure = "patchShebangs ./configure"; configureFlags = [

Discussion:
Describe the bug
cc
says the first bad commit is “dhcpcd: 8.1.2 -8.1.4” ().
And on dhcpcd says the first bad commit is rsmarples/dhcpcd “Linux: prefer ms RA times”.
cc
Sent a proposed fix upstream as rsmarples/dhcpcd.
And sent the fix here as .
Change:
<ins> { stdenvNoCC , lib , fetchurl , undmg , writeScript , callPackage }: let appName = "LibreOffice.app"; scriptName = "soffice"; version = "7.3.3"; common = import ../common.nix { inherit lib; }; dist = { aarch64-darwin = rec { arch = "aarch64"; archSuffix = arch; url = "https://download.documentfoundation.org/libreoffice/stable/${version}/mac/${arch}/LibreOffice_${version}_MacOS_${archSuffix}.dmg"; sha256 = "50ed3deb8d9c987516e2687ebb865bca15486c69da79f1b6d74381e43f2ec863"; }; x86_64-darwin = rec { arch = "x86_64"; archSuffix = "x86-64"; url = "https://download.documentfoundation.org/libreoffice/stable/${version}/mac/${arch}/LibreOffice_${version}_MacOS_${archSuffix}.dmg"; sha256 = "fb2f9bb90eee34a22af3a2bf2854ef5b76098302b3c41d13d4f543f0d72b994f"; }; }; in stdenvNoCC.mkDerivation { inherit version; inherit (import ../common.nix { inherit lib; }) meta; pname = "libreoffice"; src = fetchurl { inherit (dist.${stdenvNoCC.hostPlatform.system} or (throw "Unsupported system: ${stdenvNoCC.hostPlatform.system}")) url sha256; }; nativeBuildInputs = [ undmg ]; sourceRoot = "${appName}"; installPhase = '' runHook preInstall mkdir -p $out/{Applications/${appName},bin} cp -R . $out/Applications/${appName} cat > $out/bin/${scriptName} << EOF #!${stdenvNoCC.shell} open -na $out/Applications/${appName} --args "$@" EOF chmod +x $out/bin/${scriptName} runHook postInstall ''; passthru.updateScript = let inherit (import ./update-utils.nix { inherit lib; }) getLatestStableVersion getSha256; newVersion = getLatestStableVersion; newAarch64Sha256 = getSha256 dist."aarch64-darwin".url version newVersion; newX86_64Sha256 = getSha256 dist."x86_64-darwin".url version newVersion; currentFile = builtins.toString ./default.nix; in writeScript "update-libreoffice.sh" '' #!/usr/bin/env nix-shell #!nix-shell -i bash -p common-updater-scripts set -eou pipefail # reset version first so that both platforms are always updated and in sync update-source-version libreoffice 0 ${lib.fakeSha256} --file=${currentFile} --system=aarch64-darwin update-source-version libreoffice ${newVersion} ${newAarch64Sha256} --file=${currentFile} --system=aarch64-darwin update-source-version libreoffice 0 ${lib.fakeSha256} --file=${currentFile} --system=x86_64-darwin update-source-version libreoffice ${newVersion} ${newX86_64Sha256} --file=${currentFile} --system=x86_64-darwin ''; } </ins>

Discussion:
Apparently the DMG download is 404'ing - see below. Perhaps a different mirror should be used:
Apparently they remove older versions. Maintainer:
Maybe we can use to avoid 404's.
Good input. I'll update the version and have a look at it tomorrow.
is 404'ing again: . Should we re-open this issue?
I can't see version 7.2.5 in any supported nixpkgs branch anymore. If you're using an old commit, you'll be getting old bugs, of course.
Change:
<ins> { lib, stdenv, fetchFromGitHub }: stdenv.mkDerivation rec { pname = "await"; version = "0.999"; src = fetchFromGitHub { owner = "slavaGanzin"; repo = "await"; rev = "v${version}"; hash = "sha256-z178TKA0x6UnpBQaA8dig2FLeJKGxPndfvwtmylAD90="; }; buildPhase = '' runHook preBuild $CC await.c -o await -l pthread runHook postBuild ''; installPhase = '' runHook preInstall install -Dm755 await -t $out/bin install -Dm444 LICENSE -t $out/share/licenses/await install -Dm444 README.md -t $out/share/doc/await runHook postInstall ''; meta = with lib; { description = "Small binary that runs a list of commands in parallel and awaits termination"; homepage = "https://await-cli.app"; license = licenses.mit; maintainers = with maintainers; [ chewblacka ]; platforms = platforms.all; mainProgram = "await"; }; } </ins>

Discussion:
Project description "28Kb, small memory footprint, single binary that run list of commands in parallel and waits for their termination" Metadata homepage URL: https://await- source URL: license: mit platforms: linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
machine.wait_for_unit("multi-user.target") <ins> machine.wait_for_open_port(80) </ins> machine.succeed(f"curl -d '{msg}' localhost:80/test") notif = json.loads(machine.succeed("curl -s localhost:80/test/json?poll=1"))

Discussion:
NixOS test for the ntfy-sh module is failling. I suspect that in some cases the curl command in performed before ntfy-sh is actually listening on port 80. Failure looks non-deterministic, meaning there is probably a race between ntfy-sh and the test. Ping
Change:
# Please keep the version x.y.0.z and do not update to x.y.76.z because the # source of the latter disappears much faster. <del> version = "8.58.0.93"; </del> <ins> version = "8.59.0.77"; </ins> rpath = stdenv.lib.makeLibraryPath [ alsaLib

Discussion:
Describe the bug doesn't contains To Reproduce Steps to reproduce the behavior: to nixos-20.03 channel. skypeforlinux into environment.systemPackages sudo nixos-rebuild switch Expected behavior Skype installed. Metadata these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked): /nix/store/0rbnlnd1pvlpii8p72ybvvg672j2wc2f-bash-interactive-4.4-p23-dev copying path '/nix/store/0rbnlnd1pvlpii8p72ybvvg672j2wc2f-bash-interactive-4.4-p23-dev' from ''... system: host os: multi-user?: sandbox: version: channels(nick): channels(root): nixpkgs:
I don't know if you absolutely need the dropbox client but you could consider as an alternative until this is fixed.
DropBox? This issue is about Skype. What do you mean?
Sorry, brain fart here.
Is sthis still an issue after
Fixed.
Change:
tarMinimal = gnutar.override { acl = null; }; busyboxMinimal = busybox.override { <del> useMusl = with stdenv.targetPlatform; !isRiscV && (system == "powerpc64-linux" -> parsed.abi.name != "elfv1"); </del> <ins> useMusl = !stdenv.targetPlatform.isRiscV; </ins> enableStatic = true; enableMinimal = true; extraConfig = ''

Discussion:
Describe the bug broke parsing of powerpc64 abi-specific configs and . Previously these ad hoc ELF ABI specifiers passed through fine. Since (cc they error with: () It's possible this only worked due to gnu-config being permissive with its parsing. The abi suffix is just a convention I came up with for powerpc64 weirdness, so I'm open to changing the way this is specified, if there is a more established convention for this. To Reproduce