jiebi/CodeConvo huggingface dataset:
Change:
<ins> { lib , buildPythonPackage , fetchFromGitHub , pythonOlder , pdm-backend , httpx , zstandard }: buildPythonPackage rec { pname = "pbs-installer"; version = "2024.4.1"; pyproject = true; disabled = pythonOlder "3.8"; src = fetchFromGitHub { owner = "frostming"; repo = "pbs-installer"; rev = version; hash = "sha256-0LuajPD/sM0LoyRoCkGJ9medUcWNEPqvY76GgK2rIac="; }; build-system = [ pdm-backend ]; optional-dependencies = { all = optional-dependencies.install ++ optional-dependencies.download; download = [ httpx ]; install = [ zstandard ]; }; pythonImportsCheck = [ "pbs_installer" ]; # upstream has no test doCheck = false; meta = with lib; { description = "Installer for Python Build Standalone"; homepage = "https://github.com/frostming/pbs-installer"; changelog = "https://github.com/frostming/pbs-installer/releases/tag/${version}"; license = licenses.mit; maintainers = with maintainers; [ ]; }; } </ins>

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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 would be great to get this updated as introduces the ability to manage python versions. Will require: to be updated to to be to dependencies to be packaged and to dependencies <!-- 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]:
Also pinging since it seems you have provided the most recent updates.
Change:
repo,branch,alias <del> https://codeberg.org/FelipeLema/cmp-async-path/,, </del> https://github.com/euclidianAce/BetterLua.vim/,, https://github.com/vim-scripts/BufOnly.vim/,, https://github.com/jackMort/ChatGPT.nvim/,HEAD,

Discussion:
An uncaught exception is raised when running the vimPluginUpdater script Steps to reproduce the behavior: the vim plugin update script with The script should not raise an exception Eception: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This is because the file has been corrupted by . I’ll send a PR to fix this in a bit.
Change:
{ stdenv, fetchFromGitHub }: <ins> /* This derivation is impure: it relies on an Xcode toolchain being installed and available in the expected place. The values of sandboxProfile are copied pretty directly from the MacVim derivation, which is also impure. In order to build you at least need the `sandbox` option set to `relaxed` or `false`. */ </ins> stdenv.mkDerivation rec { pname = "iterm2"; <del> version = "3.0.14"; </del> <ins> version = "3.3.9"; </ins> src = fetchFromGitHub { owner = "gnachman"; repo = "iTerm2"; rev = "v${version}"; <del> sha256 = "03m0ja11w9910z96yi8fzq3436y8xl14q031rdb2w3sapjd54qrj"; </del> <ins> sha256 = "06mq3gfjgy8jw2f3fzdsi3pbfkdijfzzlhlw6ixa5bfb4hbcgn5j"; </ins> }; patches = [ ./disable_updates.patch ]; postPatch = '' sed -i -e 's/CODE_SIGN_IDENTITY = "Developer ID Application"/CODE_SIGN_IDENTITY = ""/g' ./iTerm2.xcodeproj/project.pbxproj ''; preConfigure = "LD=$CC"; <del> makeFlagsArray = ["Deployment"]; </del> <ins> makeFlagsArray = ["Nix"]; </ins> installPhase = '' <del> mkdir -p "$out/Applications" mv "build/Deployment/iTerm2.app" "$out/Applications/iTerm.app" </del> <ins> mkdir -p $out/Applications mv Build/Products/Deployment/iTerm2.app $out/Applications/iTerm.app ''; sandboxProfile = '' (allow file-read* file-write* process-exec mach-lookup) ; block homebrew dependencies (deny file-read* file-write* process-exec mach-lookup (subpath "/usr/local") (with no-log)) </ins> ''; <del> meta = { </del> <ins> meta = with stdenv.lib; { </ins> description = "A replacement for Terminal and the successor to iTerm"; homepage = https://www.iterm2.com/; <del> license = stdenv.lib.licenses.gpl2; platforms = stdenv.lib.platforms.darwin; </del> <ins> license = licenses.gpl2; maintainers = with maintainers; [ tricktron ]; platforms = platforms.darwin; hydraPlatforms = []; </ins> }; }

Discussion:
Describe the bug I've tried building two packages from source on my new MacBook Air running macOS 10.15/Catalina ( and a custom expression for ), and both times I get the same set of errors involving Xcode/iOS simulator/permissions/etc. It never seems to start to the build. Example: I don't know for sure whether it has to do with Catalina, but I never received these errors when using 10.14/Mojave. To Reproduce Steps to reproduce the behavior: Nix on a Mac running Catalina. I used the instructions . to install a package that has a source-based build for Darwin such as . Expected behavior The package should install or at least give me errors related to the build rather than Xcode/iOS simulator/permissions/etc. errors. Metadata Maintainer information:
iterm2 is currently broken on Catalina. I remember to have it fixed locally months ago but didn't find the time to open a pull request.
I was just using iterm2 as an example. The errors I'm receiving are generic and occur for any source build using Xcode on my new computer running Catalina. Separately, I also remember iterm2 being broken while I was using Mojave. These are different errors.
Could you test my pull request that should fix this issue (at least for iterm2)?
just tested and it works, thanks! But what are and ? I can't find those documented anywhere.
Change:
''; installPhase = '' <ins> # Fix references from man page https://github.com/lsof-org/lsof/issues/66 substituteInPlace Lsof.8  --replace ".so ./00DIALECTS" ""  --replace ".so ./version" ".ds VN ${version}" </ins> mkdir -p $out/bin $out/man/man8 cp Lsof.8 $out/man/man8/lsof.8 cp lsof $out/bin

Discussion:
Describe the bug To Reproduce Steps to reproduce the behavior: release-19.09 branch lsof to systemPackages Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information: cc
Change:
https://github.com/alvarosevilla95/luatab.nvim/,, https://github.com/rktjmp/lush.nvim/,, https://github.com/mkasa/lushtags/,, <del> https://github.com/nvim-neorocks/lz.n/,, </del> https://github.com/WhiteBlackGoose/magma-nvim-goose/,HEAD, https://github.com/winston0410/mark-radar.nvim/,HEAD, https://github.com/iamcco/markdown-preview.nvim/,,

Discussion:
Package name: Latest released version: 1.4.3 Current version on the unstable channel: 1.4.2-1-unstable-2024-07-10 Current version on the stable/release channel: none 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]:
Change:
<ins> { buildPythonPackage , fetchPypi , lib , pytest-asyncio , pytest-cov , pytestCheckHook }: buildPythonPackage rec { pname = "aiorwlock"; version = "1.3.0"; src = fetchPypi { inherit pname version; sha256 = "sha256-g/Eth99LlyiguP2hdWWFqw1lKxB7q1nGCE4bGtaSq0U="; }; checkInputs = [ pytestCheckHook pytest-asyncio ]; pythonImportsCheck = [ "aiorwlock" ]; meta = with lib; { description = "Read write lock for asyncio"; homepage = "https://github.com/aio-libs/aiorwlock"; license = licenses.asl20; maintainers = with maintainers; [ billhuang ]; }; } </ins>

Discussion:
Project description Ray is a fast and simple framework for building and running distributed applications. It is packaged with RLlib, a scalable reinforcement learning library. The project provides a wheel at , but according to NixOs is by default not compatible. Metadata homepage URL: source URL: license: apache2 platforms: unix, linux
I'm interested in this as well, when I try to use any sort of non-local mode with ray installed in a nix-shell environment via pip, it throws errors launching redis. Even though redis-server exists at the aforemention path. It fails to launch when I attempt to execute redis directly.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I haven't tested, but since manylinux1 is available by default now (), does it work on your machine on the latest unstable?
I still have the issue with redis unfortunately
this seems to work
I see, the s fixed it.
I marked this as stale due to inactivity. &rarr;
Still important to me.
I marked this as stale due to inactivity. &rarr;
In case anyone is still looking for this - it is packaged in python-on-nix
Change:
<xi:include href="functions/library.xml" /> <xi:include href="functions/generators.xml" /> <xi:include href="functions/debug.section.xml" /> <del> <xi:include href="functions/prefer-remote-fetch.xml" /> </del> <ins> <xi:include href="functions/prefer-remote-fetch.section.xml" /> </ins> <xi:include href="functions/nix-gitignore.section.xml" /> </chapter>

Discussion:
This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.
I'll work on this.
Change:
''; nativeBuildInputs = [ pythonEnv ]; <del> depsBuildBuild = [ buildPackages.stdenv.cc buildPackages.util-linux buildPackages.bash ]; </del> <ins> depsBuildBuild = [ buildPackages.stdenv.cc buildPackages.bash ]; depsHostHost = [ libuuid ]; </ins> strictDeps = true; # trick taken from https://src.fedoraproject.org/rpms/edk2/blob/08f2354cd280b4ce5a7888aa85cf520e042955c3/f/edk2.spec#_319 <del> ${"GCC5_${targetArch}_PREFIX"}=stdenv.cc.targetPrefix; </del> <ins> ${"GCC5_${targetArch}_PREFIX"} = stdenv.cc.targetPrefix; </ins> makeFlags = [ "-C BaseTools" ];

Discussion:
Steps to reproduce the behavior: pkgsCross.aarch64-multiplatform.edk2 Full log here: Few last lines: EDK2 package was updated in nixpkgs, and after that cross-compilation from x86_64 to aarch64 stopped working. The issue appeared in latest update commit: The package has no maintainers set in meta. The breaking change was introduced by: I see cross-compilation fixes have been made previously by: Other contributors who have contributed over the past year, I got from and : "Sandro Jäckel" and Please run and paste the result.
Actually I had binfmt for aarch64-linux emulated, I disabled it and now build fails even earlier when it tries to run antlr built for aarch64-linux:
Unable to reproduce: I just cross compiled EDK2 with .
Wait, I had a dinosaur nixpkgs there on a feature branch, testing again.
I concur, antlr is trying to be executed but it's not a binary for the right platform. This seems to be a breakage upstream as they seem to ship their own ANTLR binaries.
I won't have time to tackle it as I have too much on my plate right now.
Any change on looking at this now as we are going towards NixOS 23.11?
Thank you!
Change:
owner = "googlefonts"; repo = "noto-cjk"; inherit rev sha256; <ins> sparseCheckout = "${typeface}/OTC"; </ins> }; installPhase = '' install -m444 -Dt $out/share/fonts/opentype/noto-cjk ${typeface}/OTC/*.ttc ''; <ins> passthru.tests.noto-fonts = nixosTests.noto-fonts; </ins> meta = with lib; { description = "Beautiful and free fonts for CJK languages"; homepage = "https://www.google.com/get/noto/help/cjk/";

Discussion:
When building my NixOS configuration, failed to build. I’m using as my nixpkgs branch. <details<summaryError logs (click to expand) </summary</detailsBuild the flake The system is buildt <!-- 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.
Looks like a download error, the fonts built fine locally for me. I would just try rerunning it. That might be helpful. But more importantly IMO is that the builds are failing on due to the Github archive download being too big. CC Maybe there is some way to limit tar to extracting only the stuff we care about, or we can download only specific files from the repository.
I’ve re-run the thing at least thrice now, it consistently fails
Is run before checking the hash or after?
It's , it unpacks and then hashes.
Hm. It’s still erroring out… !
The font package itself is the same in and !
I too believe you're having problems with the download. The size of download indicated by your initial log output is 413MB, while in the next screenshot, it goes down to 274MB. Both are far too small considering that the total size of the unpacked archive is around 4GB. For reference, .
I see. I will try again later, maybe the internet was too spotty.
Since the combined size of Noto Sans CJK and Noto Serif CJK is roughly 300MB, it would probably be best to download the files individually. I could create a PR for this, but first I would have to get some sleep ;-)
I am currently having the same issue with the same packages not downloading correctly.
After this merged, this kind of problems can be largely solved by using .
IIRC for GitHub http is preferred to git, because it's somewhat faster (git has more protocol overhead). But in general sparseCheckout could be useful.
Change:
SKYDNS_NAMESERVERS = concatStringsSep "," cfg.nameservers; }; serviceConfig = { <del> ExecStart = "${cfg.package}/bin/skydns"; </del> <ins> ExecStart = "${cfg.package.bin}/bin/skydns"; </ins> }; };

Discussion:
NixOS services that depend on binaries are now broken (eg ) after This is because the attribute path for binaries has now changed. For example should now be .
I can do it tomorrow.
Change:
./nixbuild.patch # Load libraries at runtime by absolute path <ins> ./extra-mangling.patch # Mangle store paths of modules to prevent runtime dependence. </ins> ] ++ lib.optional (!stdenv.hostPlatform.isWindows) ./toLocation.patch; configurePhase = ''

Discussion:
Nim programs contain a full-path reference to the Nim standard library, which pulls the Nim compiler into the programs' store closure. Steps to reproduce the behavior: nix path-info -rsSh nixpkgs#nimPackages.c2nim less nix path-info -rsSh nixpkgs#nimmm | sort -nk3
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
libaal = callPackage ../development/libraries/libaal { }; <ins> libabigail = callPackage ../development/libraries/libabigail { }; </ins> libaccounts-glib = callPackage ../development/libraries/libaccounts-glib { }; libacr38u = callPackage ../tools/security/libacr38u { };

Discussion:
Project description Framework which aims at helping developers and software distributors to spot some ABI-related issues like interface incompatibility in ELF shared libraries by performing a static analysis of the ELF binaries at hand. Metadata homepage URL: source URL: license: platforms: linux or unix
I created the initial packaging here: The configuration is here: but still the build ends up with: Please advise: which disabled features do you want to have enabled (by adding required dependences)? have you seen the missing earlier?
Thank you for taking a look at this. Bash-completions would be nice. I do not also see a reason not to use C++11, looking at the source code it might add some extra tools for visualization. I have no idea why it fails with the error but since I cannot grep hardened in , perhaps it is an artefact of the tarball. Perhaps try adding to to re-generate the script. And while at it, could you move there as well?
I won't have time for any changes until the end of this week, so in case you need it sooner, I suggest you take what I already have and build on top of that.
Change:
preInstall = '' mkdir -p $doc cp -r ${nginx-doc}/* $doc <ins> # TODO: make it unconditional when `openresty` and `nginx` are not # sharing this code. if [[ -e man/nginx.8 ]]; then installManPage man/nginx.8 fi </ins> ''; disallowedReferences = map (m: m.src) modules;

Discussion:
I would prefer package to install man pages in some form. The command should show manpage from shipped in release tarball. I tried a trivial implementation, but it seems to be entangled with : . Would be nice to make derivation more amenable to such changes without the breakage.
Change:
<ins> # This file was generated by https://github.com/kamilchm/go2nix v1.3.0 [ { goPackagePath = "github.com/hashicorp/yamux"; fetch = { type = "git"; url = "https://github.com/hashicorp/yamux"; rev = "2f1d1f20f75d5404f53b9edf6b53ed5505508675"; sha256 = "1fga3p6j2g24ip9qjfwn3nqjr00m4nnjz92app7ms3sz7vgq2a7s"; }; } { goPackagePath = "github.com/howeyc/gopass"; fetch = { type = "git"; url = "https://github.com/howeyc/gopass"; rev = "bf9dde6d0d2c004a008c27aaee91170c786f6db8"; sha256 = "1jxzyfnqi0h1fzlsvlkn10bncic803bfhslyijcxk55mgh297g45"; }; } { goPackagePath = "github.com/sternhenri/interact"; fetch = { type = "git"; url = "https://github.com/sternhenri/interact"; rev = "dfeb9ef2030483f98cee2c86f5775fe6c729f10b"; sha256 = "00b09fyy9zhv11mbzm18ngg765g0gyb23bmr4fc83i09w912if7j"; }; } { goPackagePath = "golang.org/x/sys"; fetch = { type = "git"; url = "https://go.googlesource.com/sys"; rev = "04f50cda93cbb67f2afa353c52f342100e80e625"; sha256 = "0hmfsz9y1ingwsn482hlzzmzs7kr3cklm0ana0mbdk70isw2bxnw"; }; } { goPackagePath = "golang.org/x/crypto"; fetch = { type = "git"; url = "https://github.com/StanfordSNR/crypto"; rev = "e451cabda2acd7a416728ee89b75975b8b0c90d7"; sha256 = "0aj6fc0i1dm6rdgr1mlv2pl4s0i6sj821k2p4gig45h5mn06mhpz"; }; } { goPackagePath = "github.com/jessevdk/go-flags"; fetch = { type = "git"; url = "https://github.com/jessevdk/go-flags"; rev = "c0795c8afcf41dd1d786bebce68636c199b3bb45"; sha256 = "0xsmr17mrpm9kx34zfzzirwy0n459h975x49p41fs2f6ly6lk9vp"; }; } ] </ins>

Discussion:
Package Request: is a way of being able to do agent forwarding when using mosh. It also allows verifying commands being executed. I don't fully understand how it works, but it seems valuable, especially as I shift back to using on high-latency links.
This project looks abandoned, it has been released as as beta in 2017.
Hm, disappointing, but good point. I opened this to confirm:
I'm not really sure if we should proceed. I was going to close it, based on the response to the issue I filed on the guardian-agent repo, but I see you have a PR open now...
while I thought the same, I changed my mind because of two things. First of all there is sadly no alternative to this and mosh won't implement one, they own recommendation is actually using guardian-agent (as per ). And in the second place, the author of the project, Dima Kogan, did reply to my mail almost instantly, so while this is marked as beta, I think we should ship it with NixOS and help catch any outstanding bugs/problems with it.
Change:
bimmer-connected = callPackage ../development/python-modules/bimmer-connected { }; <ins> binary = callPackage ../development/python-modules/binary { }; </ins> binaryornot = callPackage ../development/python-modules/binaryornot { }; bincopy = callPackage ../development/python-modules/bincopy { };

Discussion:
This is a continuation of the topic from the initial "upgrade datadog-agent to v7" ticket - see for details on that. The is a metrics and log collection agent intended to run on linux systems for use with 's paid service. On other linux distributions, installing the datadog-agent includes the integration/plugin code, there is no separate install for those, or post-install steps to install the plugins (only config to activate/configure them). Configure the in , and add some extra integration, such as the docker integration. and look at the installed, the plugins are not available. You should see logs from the agent about those. When configuring the datadog-agent, the standard integrations/plugins (docker, nginx, apache, postgres, etc, etc) should be installed and available to the agent if the agent is configured to use them. Please run and paste the result.
There's still something wrong with the Python environment.
Most likely we need to use pyproject to build it properly: That results into missing ddtrace package, which needs to be .
Looks like setuptools wasn't building the and modules. and should fix the integrations. Datadog is planning on dropping setuptools, so we should switch over to pyproject. The blocker is that there are a number of missing dependencies that aren't on nixpkgs yet, but I've started working on that. the Docker integration was rewritten in Go and is now built together with the . You can enable it with: I have no idea why they're now called Yeah, we need to rethink how these integrations are enabled. Now that some of them are part of the , it's become quite a pain to set up.
Fixed in
Thanks! Note that, to get this to run for me, nixpkgs needed an overlay specifying that all packages wanting would get . That looks liked: It seems that, while is deprecated and python 3 is "the default", the package maps to , so a lot of packages effectively default to python 2. Thanks to for coming up with that workaround. I haven't yet see the docker integration work, but I've seen the plugins and such install, so that is promising, and it's likely the last bits are in my config to sort out.
are you on an older release of nixpkgs?

has been set to for the datadog integrations since .
We determined the evaluation error came from here: Did we mess that up somehow?
There's a good chance that can be removed from there with no impact. We recently did so for the systemd service.
is a vestige of the old agent. It was a python wrapper that launched that jmx java thing. can most definitely be removed check is broken. I imagine we'd need to package
Change:
phonenumbers = callPackage ../development/python-modules/phonenumbers { }; <ins> photutils = callPackage ../development/python-modules/photutils { }; </ins> pkgutil-resolve-name = callPackage ../development/python-modules/pkgutil-resolve-name { }; pkg-about = callPackage ../development/python-modules/pkg-about { };

Discussion:
Project description Photutils is an Astropy package for detection and photometry of astronomical sources. Metadata homepage URL: source URL: license: 3-clause BSD platforms: unix, linux, darwin, Linux, Darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I could to built here withou errors from source, just the 1.11.0 version, it is not the latest one. My nix block: