jiebi/CodeConvo huggingface dataset:
Change:
dart = callPackage ../development/compilers/dart { }; <ins> dart-sass = callPackage ../development/tools/misc/dart-sass { }; </ins> httrack = callPackage ../tools/backup/httrack { }; httraqt = libsForQt5.callPackage ../tools/backup/httrack/qt.nix { };

Discussion:
Project description Dart Sass is a faster and more updated version of the Sass compilers Nix already supplies. Technically works, but it is . Metadata homepage URL: https://sass- source URL: license: platforms: Linux ia32 and x64, MacOS x64, and Windows ia32 and x64. You can also compile the source with .
I think is now using see homepage:
Yes, technically is compiled from dart-sass, but it is in a pure-Javascript form. One of the items in the is how the native executable of dart-sass is so much faster than the Javascript one. The reason I created this was so that the native executable would be to Nix packages.
Are there other Dart packages in nixpkgs which we could use as a reference to package dart-sass?
Here's an example getting it in nix-shell.
Change:
leo2 = callPackage ../applications/science/logic/leo2 {}; <ins> logisim = callPackage ../applications/science/logic/logisim {}; </ins> matita = callPackage ../applications/science/logic/matita { ocaml = ocaml_3_11_2; inherit (ocamlPackages_3_11_2) findlib lablgtk ocaml_expat gmetadom ocaml_http

Discussion:
Describe the bug Cannot build Android 11 AOSP on nixos without source modification To Reproduce As android is huge to download, the following could take a few hours to process, and you will need a solid machine to build android. Steps to reproduce the behavior: android Android repository - :warning: This take a lot of time, you are about to download 100GB build - it :warning: to complete the build this require a good CPU with 16GB Ram and some space disk some build process if fail for linking issue to shared library. Expected behavior Build success Additional context Since I am on nix I use this to build android. But it no longer work on AOSP 11. This is the error that happen: This is caused by the android build system creating his own environment without . I didn't find any nix tips to have it working without modifying source, so I post this issue to indicate the fhs is no longer suffisant. Here is the dirty workaround that seems to work. I do not have encounter any issues yet. In following repo: Notify maintainers I have no idea who did the original FHS nor who trigger on this Metadata Maintainer information:
The Android build system (as of Android 11) now ignores certain environment variables by default, including . You can run before building to disable this behavior. Also, in case you aren't aware of it, can also be used to build AOSP using Nix.
I wasn't aware of this ninja option. Thanks ! It way cleaner than what i did. I will put it my android FHS, but it could be something nice to add to the example on nixos Wiki. Does someone know who trigger to do so ? I am aware of the Robotnix existence since i start searching for this issue, but i do not know how it work with local source tree, as I need to do heavy modification in multiple android repo(test it, build some debug code...). Is there any possibility with Robotnix to do something like this ?
Yeah, you're right that robotnix wouldn't help as much if you intend to do AOSP development (edit / test / debug cycles). It's most useful when you have something that works and want to allow end-users to easily build it using nix.

I didn't see the commit that change it, but wiki has been update. Thank you mysterious people :+1: He/She also add some other lines needed in new android build, that's nice ! I close this issue
Change:
kactivities plasma-workspace ]; <ins> meta = { description = "Components necessary to integrate browsers into the Plasma Desktop"; homepage = "https://community.kde.org/Plasma/Browser_Integration"; }; </ins> }

Discussion:
When searching on for "plasma integration" there are 2 different packages : and . Looking further to try and find a distinction, there's additionally a requires What are all these packages? Are they related? Aliases? Copies? would probably know more. I don't know if allows adding a description, but that or a comment in the files would be greatly appreciated.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Even if I have plasma-browser-integration in my , it seems that librewolf is not able to connect to the host ! EDIT: seems to work in mainline firefox. So it's a different issue. Sorry.
Old issue, but these all have congruent kde packages: The naming in Nixpkgs is simply mirroring the KDE naming convention.
It would be great if they had descriptions. Maybe I'll find some time to add it unless somebody beats me to the punch :)
Change:
''; meta = { <del> description = "glooctl is the unified CLI for Gloo"; </del> <ins> description = "Unified CLI for Gloo, the feature-rich, Kubernetes-native, next-generation API gateway built on Envoy"; </ins> mainProgram = "glooctl"; homepage = "https://docs.solo.io/gloo-edge/latest/reference/cli/glooctl/"; <ins> changelog = "https://github.com/solo-io/gloo/releases/tag/v${version}"; </ins> license = lib.licenses.asl20; maintainers = [ ]; };

Discussion:
Steps to reproduce the behavior: on nixpkgs (nixos-unstable) or (staging-next) none (they last updated 1.16.16 -1.16.17) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Also it would be great if it was updated to 1.17.x, but that warrants a separate issue
(sorry didnt ping you in the original i didnt look so far :(
I'm just back from a trip; I'll take a look in the next 24 hours
Change:
<ins> { lib , stdenv , boost , cmake , gettext , git , libdrm , meson , ninja , openssl , pkg-config , python3 , tuxclocker }: stdenv.mkDerivation { inherit (tuxclocker) src version meta BOOST_INCLUDEDIR BOOST_LIBRARYDIR; pname = "tuxclocker-plugins"; nativeBuildInputs = [ gettext git meson ninja pkg-config (python3.withPackages(p: [ p.hwdata ])) ]; buildInputs = [ boost libdrm openssl ]; mesonFlags = [ "-Ddaemon=false" "-Dgui=false" "-Drequire-amd=true" "-Drequire-python-hwdata=true" ]; } </ins>

Discussion:
Project description TuxClocker is a hardware controlling and monitoring program. TuxClocker consists of a DBus daemon and a Qt GUI that uses the daemon. It allows you to e.g. set a custom fan curve and overclock your CPU and GPU. Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
, ninja , pkg-config , python3 <del> , systemd </del> <ins> , substituteAll , systemdMinimal </ins> , usbutils , vala , which

Discussion:
Steps to reproduce the behavior: with enabled <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This is not really a bug or a build failure, more of a feature request. The expression in nixpkgs doesn't set , as the build with it being set would fail. Someone needs to sit down and figure out why. I propose starting with the code of the two failed tests, seeing if something is missing from nativeCheckInputs. Happy to review a PR, but I don't have the bandwidth to drive this.
It's an indication that the packaging is incorrect. Incorrect packaging sounds like a packaging bug to me. See for the main tracking issue. If it's better categorised as a "bug" than a "build failure", then so be it, but it's absolutely not a "feature request." If you don't have time, that's a totally different topic, that could be just stated as is without the rest of it.
and the test for both use to get information about devices, which is not currently provided by any input. Adding (which provides ) to the check inputs makes this build without errors, even with . Since (a binary output) needs , should probably also be in the regular build inputs. (just stumbled across this randomly and thought I'd try to find out what's up)
Oh, very nice! Wondering how is currently sneaking in then :-) In any case, I'll try to add this to a PR and see how it goes!
I opened that does this, thanks!
The PR has been merged, this can be closed.
Change:
-e 's|	perl -e|	${perl}/bin/perl -e|g'  $out/libexec/git-core/{git-am,git-submodule} <ins> # Fix references to gettext. substituteInPlace $out/libexec/git-core/git-sh-i18n  --replace 'gettext.sh' '${gettext}/bin/gettext.sh' </ins> # gzip (and optionally bzip2, xz, zip) are runtime dependencies for # gitweb.cgi, need to patch so that it's found sed -i -e "s|'compressor' => ['gzip'|'compressor' => ['${gzip}/bin/gzip'|" 

Discussion:
Here's how it's possible to reproduce it: both and package using nix-env or declaration in . I've tried different git versions, all them work this way. Not sure about versions, but I'm using 0.19.6 with channel on my system. into any git repository directory or with any arguments (except options, works well). Git will do nothing and return code 0. Here's an illustration of how it works: I used strace to discover what's going on and it appeared that with and without installed gives almost identical output (differs in addresses only), except for the last ~6 lines, which are: With installed: Without:
Confirming this bug.
cc
Critical point is this: I'm not able to check if eval_gettext function is working on my system now + I don't quite understand where is defined itself.
The script just calls the binary from current , which seems a bad thing to do in the first place. We should probably patch that out.
Got a fix in progress, building and testing
There. There is also an issue with in the gettextWithExpat package. The difference with just gettext is that it's wrapped and it's probably interfering with the hacky source detection in the target script.
Change:
]; preConfigure = '' <del> echo ${version} > VERSION </del> <ins> ${ if stdenv.isDarwin && ! isCleanVer version then "echo 'not overwriting VERSION since it would upset ld'" else "echo ${version} > VERSION" } </ins> configureFlagsArray+=("--elfinterp=$(< $NIX_CC/nix-support/dynamic-linker)") '';

Discussion:
Deno no longer working on darwin due to tinycc being broken. error: Package ‘tcc-0.9.27+date=2022-01-11’ in /nix/store/4la4fc5wfn4p0784i12h0a046yqzln16- is marked as broken, refusing to evaluate. It works. Looks like this happened with the move to Deno 1.23.4: Issue related to tinycc being broken: deno: tinycc:
Thanks for raising this. I shouldn't have missed this. I'll try fix tinycc and if we can't Mac might be able to fall back to the same non-tinycc method (even if it has some performance penalties) until they migrate to asm
Thanks for being on this
if you could try out that'd be helpful
i'm on it!
succeeded for me on x86_64-darwin
Nice, it worked for me in my x8664-darwin vm but it's always good to get it checked on real hardware. Would be nice to have someone try it on aarch64-darwin As a note if you want to do a "full" test of the FFI features (the one that requires tcc now) git clone /tmp/deno cd /tmp/deno mkdir -p ./target/result cp /location/of/the/nixpkgs/result/bin/deno ./target/result/ target/release/deno bench --allow-ffi --allow-read --unstable
Ran it on my aarch64-darwin machine:
fantastic thanks
also worked for me on aarch64 (i used an EC2 m1 macos instance). Unfortunately running the FFI tests requires a to be in the directory, which I noticed is output when running outside of nix. However, on aarch64, I can't get a direct to succeed...
sorry I missed a step there try if you still have the instance
cool, that worked.

the benchmarks ran without error...
Reopening as does not resolve this issue
That PR does resolve the issue, see the comments towards the bottom to pull in the fix early The unstable channel hasn't progressed for and not in scope for this issue ~I will open a backport ticket for 22.05 though~ actually is on which is unaffected by this issue
Yes, this is confirmed by ofborg.
OMG Sorry that I didn't follow the PR correctly. Not only I missed the part you fixed on the derivation of deno, but I saw the tinycc's derivation flagged as and mistook that it is the same on deno's. The old message of the beginning of the PR ("tinycc darwin issues were a pain, there's no point holding up this update since it's already broken") also made me confused and gave an idea that this issue was closed by mistake. Sorry for confusing everyone here, and thank you very much for fixing the problem!
I'd pretty much given up on trying to make tinycc build properly on darwin but as a last-ditch effort I tried just building the static lib on it's own and to my surprise it worked just fine
Change:
cargo-hf2 = callPackage ../development/tools/rust/cargo-hf2 { inherit (darwin.apple_sdk.frameworks) AppKit; }; <ins> cargo-info = callPackage ../development/tools/rust/cargo-info { }; </ins> cargo-inspect = callPackage ../development/tools/rust/cargo-inspect { inherit (darwin.apple_sdk.frameworks) Security; };

Discussion:
Project description is a cargo subcommand, which shows crates info from See their for an output example. Metadata homepage URL: source URL: license: mit OR apache platforms: unix, linux, and darwin
Change:
"-X main.channel=stable" ]; <ins> preBuild = '' ldflags+=" -X main.buildDate=$(cat SOURCE_DATE)" ''; </ins> buildInputs = [ makeBinaryWrapper ]; postInstall = ''

Discussion:
After installing you can run . This command prints something like: Usually the date at the end is the build date. But when installed via nix it always shows the current time, so the command output is different for every second. The build date is passed here: It also has a comment saying : Steps to reproduce the behavior: symfony-cli: It should show the real build time of that release (time of last commit?). <!-- 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]:
Hello, Is this really a problem? If you really want to fix it, it is possible to add: in with a fixed date value or possibly the date of the commit tag.
Awesome, thanks for taking the time to implement this!
Change:
buildPythonPackage rec { pname = "sphinxcontrib-httpdomain"; <del> version = "1.5.0"; </del> <ins> version = "1.7.0"; </ins> src = fetchPypi { inherit pname version; <del> sha256 = "0srg8lwf4m1hyhz942fcdfxh689xphndngiidb575qmfbi89gc7a"; </del> <ins> sha256 = "ac40b4fba58c76b073b03931c7b8ead611066a6aebccafb34dc19694f4eb6335"; </ins> }; propagatedBuildInputs = [ sphinx ];

Discussion:
Ran . For some reason there are pylint tests running for ~8 minutes that eventually end up in a failure. <details<summaryPyLint test failures</summary</detailson pylint (indirectly?); running for ~10 minutes as part of package installation process.
This will need to be backported to 18.09 as the latest version released by Hydra is broken too
The tests still fails even after the above patch applied. <details<summaryHere is the log</summary</detailsHere is the patch I used: Edit: the original patch is working on the python-unstable branch so I guess it's OK
I pushed a fix to the branch: . The fix for is currently in the branch: .
Change:
<ins> { config, lib, pkgs, ... }: let cfg = config.programs.ydotool; in { meta = { maintainers = with lib.maintainers; [ quantenzitrone ]; }; options.programs.ydotool = { enable = lib.mkEnableOption '' ydotoold system service and install ydotool. Add yourself to the 'ydotool' group to be able to use it. ''; }; config = lib.mkIf cfg.enable { users.groups.ydotool = { }; systemd.services.ydotoold = { description = "ydotoold - backend for ydotool"; wantedBy = [ "multi-user.target" ]; partOf = [ "multi-user.target" ]; serviceConfig = { Group = "ydotool"; RuntimeDirectory = "ydotoold"; RuntimeDirectoryMode = "0750"; ExecStart = "${lib.getExe' pkgs.ydotool "ydotoold"} --socket-path=/run/ydotoold/socket --socket-perm=0660"; # hardening ## allow access to uinput DeviceAllow = [ "/dev/uinput" ]; DevicePolicy = "closed"; ## allow creation of unix sockets RestrictAddressFamilies = [ "AF_UNIX" ]; CapabilityBoundingSet = ""; IPAddressDeny = "any"; LockPersonality = true; MemoryDenyWriteExecute = true; NoNewPrivileges = true; PrivateNetwork = true; PrivateTmp = true; PrivateUsers = true; ProcSubset = "pid"; ProtectClock = true; ProtectControlGroups = true; ProtectHome = true; ProtectHostname = true; ProtectKernelLogs = true; ProtectKernelModules = true; ProtectKernelTunables = true; ProtectProc = "invisible"; ProtectSystem = "strict"; ProtectUser = true; RestrictNamespaces = true; RestrictRealtime = true; RestrictSUIDSGID = true; SystemCallArchitectures = "native"; SystemCallFilter = [ "@system-service" "~@privileged" "~@resources" ]; UMask = "0077"; # -> systemd-analyze security score 0.7 SAFE 😀 }; }; environment.variables = { YDOTOOL_SOCKET = "/run/ydotoold/socket"; }; environment.systemPackages = with pkgs; [ ydotool ]; }; } </ins>

Discussion:
requires to be running in order to be used otherwise it aborts and crashes (see ). It would make sense to have a NixOS configuration option in order to automatically configure to run. Some NixOS module option (perhaps ) that automatically configures and runs as a systemd service in the background.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
githubId = 106779009; name = "Slambert"; }; <ins> slashformotion = { github = "slashformotion"; githubId = 45801817; name = "slashformotion"; }; </ins> slbtty = { email = "shenlebantongying@gmail.com"; github = "shenlebantongying";

Discussion:
Project description Tbump helps you bump the version of your project easily. It is a simple cli. Metadata homepage URL: source URL: license: BSD 3-Clause platforms: Anything that run python Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<ins> { lib , rustPlatform , fetchFromGitHub }: rustPlatform.buildRustPackage rec { pname = "leptosfmt"; version = "0.1.12"; src = fetchFromGitHub { owner = "bram209"; repo = "leptosfmt"; rev = version; hash = "sha256-RR4gwmYna/mvUw5akQutWKaUCWzCjK512gynR9Pddd0="; }; cargoHash = "sha256-6du44SfH0dT1gWVFluB3+AA3GUzwN7Sjh03rKhSRKCM="; meta = with lib; { description = "A formatter for the leptos view! macro"; homepage = "https://github.com/bram209/leptosfmt"; changelog = "https://github.com/bram209/leptosfmt/blob/${src.rev}/CHANGELOG.md"; license = with licenses; [ asl20 mit ]; maintainers = with maintainers; [ figsoda ]; }; } </ins>

Discussion:
Project description A formatter for the leptos macro. Leptos is a Rust wasm framework. Metadata homepage URL: source URL: license: mit, apache platforms: unix, linux, darwin, ...
Note to contributors: It should be possible package this similar to
Change:
<ins> { lib, stdenv, fetchFromGitHub, pkg-config, cmake, ninja, yasm , libjpeg, openssl, libopus, ffmpeg, alsaLib, libpulseaudio, protobuf , xorg, libXtst }: let rev = "2d804d2c9c5d05324c8ab22f2e6ff8306521b3c3"; sha256 = "0kz0i381iwsgcc3yzsq7njx3gkqja4bb9fsgc24vhg0md540qhyn"; in stdenv.mkDerivation { pname = "tg_owt"; version = "git-${rev}"; src = fetchFromGitHub { owner = "desktop-app"; repo = "tg_owt"; inherit rev sha256; fetchSubmodules = true; }; outputs = [ "out" "dev" ]; nativeBuildInputs = [ pkg-config cmake ninja yasm ]; buildInputs = [ libjpeg openssl libopus ffmpeg alsaLib libpulseaudio protobuf xorg.libX11 libXtst ]; cmakeFlags = [ # Building as a shared library isn't officially supported and currently broken: "-DBUILD_SHARED_LIBS=OFF" ]; meta.license = lib.licenses.bsd3; } </ins>

Discussion:
, CVSSv3=5.3 (nixos-21.05, nixos-unstable) A reordering issue exists in Telegram before 7.8.1 for Android, Telegram before 7.8.3 for iOS, and Telegram Desktop before 2.8.8. An attacker can cause the server to receive messages in a different order than they were sent a client. Scanned versions: nixos-21.05: ; nixos-unstable: . Cc Cc Cc
Change:
, lib , fetchFromGitHub , fetchurl <ins> , copyDesktopItems </ins> , makeDesktopItem , python3 , libX11

Discussion:
Package name: shipwright Latest released version: 8.0.4 <!-- Search your package here: --- Current version on the unstable channel: 7.1.1 Current version on the stable/release channel: 7.0.2 <!-- 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 I tried updating myself and found 8.0.4 fails building with error I bisected to upstream commit and the file but I'm not sure how to resolve right now. <!-- 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]:
Change:
install -Dm755 OpenBoardImporter $out/bin/OpenBoardImporter ''; }; <del> in stdenv.mkDerivation rec { </del> <ins> in stdenv.mkDerivation { </ins> pname = "openboard"; version = "unstable-2022-11-28";

Discussion:
This means nearly all qt6 packages depend on gdb which is 641M on its own. Why is that the case? I can't imagine needing Valgrind for "production" qt6 builds but I have no knowledge in this domain. cc
valgrind was not in my qt6 draft in valgrind was in but valgrind or gdb dont show up in the closure of <details </summaryto compare, </detailsso ... no problem? edit: <details </summary</details
The inputs are only propagated in the output and that's what other packages use. I only came across this because I found gdb in my system closure. showed <the package-quazip -qtbase -valgrind -gdb why did you add valgrind to qt6's propagatedBuildInputs?
It should have been a build time dependency for qtbase. And as it is only referenced in dev output, it should normally not be referenced in system closures, except for issues like Edit, quazip wasn't fixed by that, let me look into it tomorrow.
... so should not be there &rarr; /nix/store/y1m61ayisqmp29ckzi0qq4fp640qfl3l-qtbase-6.4.1-dev/include/QtTest/qtestmouse.h &rarr; /nix/store/y1m61ayisqmp29ckzi0qq4fp640qfl3l-qtbase-6.4.1-dev/include/QtTest/qtestmouse.h &rarr; propagatedBuildInputs &rarr; propagatedBuildInputs also may be relevant: in , are copied to
For the , they should have been in dev output, but and do not have dev output, adding it back should be enough. For , it should be of the same problem as in , maybe we should add that in the hooks of qtbase, or we can fix this ad-hoc.
Change:
}: buildDotnetModule rec { pname = "garnet"; <del> version = "1.0.16"; </del> <ins> version = "1.0.18"; </ins> src = fetchFromGitHub { owner = "microsoft"; repo = "garnet"; rev = "v${version}"; <del> hash = "sha256-0c6iJMSB9ThJVookibZL5CoAhrVMtY6oHYn92nN0114="; </del> <ins> hash = "sha256-vKjFUa/f/nsBaBkxwIhtMox2qtbBzy+ipuqFHtLhbr4="; </ins> }; projectFile = "main/GarnetServer/GarnetServer.csproj";

Discussion:
Package name: Garnet Latest released version: 1.0.18 <!-- Search your package here: --- Current version on the unstable channel: 1.0.16 Current version on the stable/release channel: 1.0.6 <!-- 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]: