jiebi/CodeConvo huggingface dataset:
Change:
<del> {stdenv, lib, fetchFromGitHub, autoreconfHook, darwin}: </del> <ins> {stdenv, lib, fetchFromGitHub, autoreconfHook, ApplicationServices}: </ins> stdenv.mkDerivation rec { pname = "duti"; <del> version = "1.5.4pre"; </del> <ins> version = "1.5.5pre"; </ins> src = fetchFromGitHub { owner = "moretension"; repo = pname; <del> rev = "7dbcae86f99fedef5a6c4311f032a0f1ca0539cc"; sha256 = "1z9sa0yk87vs57d5338y6lvm1v1vvynxb7dy1x5aqzkcr0imhljl"; </del> <ins> rev = "fe3d3dc411bcea6af7a8cbe53c0e08ed5ecacdb2"; sha256 = "1pg4i6ghpib2gy1sqpml7dbnhr1vbr43fs2pqkd09i4w3nmgpic9"; </ins> }; nativeBuildInputs = [autoreconfHook]; <del> buildInputs = [darwin.apple_sdk.frameworks.ApplicationServices]; configureFlags = ["--with-macosx-sdk=/homeless-shelter"]; </del> <ins> buildInputs = [ApplicationServices]; configureFlags = [ "--with-macosx-sdk=/homeless-shelter" # needed to prevent duti from trying to guess our sdk # NOTE: this is different than stdenv.hostPlatform.config! "--host=x86_64-apple-darwin18" ]; </ins> meta = with lib; { description = "A command-line tool to select default applications for document types and URL schemes on Mac OS X"; longDescription = ''

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.5.4pre (rev ) desired version: 1.5.5pre (needs at least ) maintainers: The current version of duti fails to compile with: <details<summaryCompilation error with current version</summary</detailsNaively upgrading to the version linked above fails too, I believe that's because the SDK is too old (it uses 10.12.16?): <details<summaryCompilation error with new version</summary</details
Should be fixed with
Change:
, buildPythonPackage , fetchPypi , libcap <ins> , pytestCheckHook </ins> }: buildPythonPackage rec {

Discussion:
Describe the bug Recently, started failing to build due to a test failure in . To Reproduce Steps to reproduce the behavior: Expected behavior Should build succesfully Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(kira): nixpkgs: Maintainer information:
The failure seems to be caused by the recent upgrade:
Change:
platforms = stdenv.lib.platforms.linux ++ stdenv.lib.platforms.freebsd ++ <del> stdenv.lib.platforms.illumos ++ stdenv.lib.platforms.darwin; </del> <ins> stdenv.lib.platforms.illumos; </ins> }; }

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:
, xorg , zlib , buildPackages <ins> , withClipboard ? false </ins> }: rustPlatform.buildRustPackage rec { pname = "broot"; <del> version = "1.28.1"; </del> <ins> version = "1.29.0"; </ins> src = fetchFromGitHub { owner = "Canop"; repo = pname; rev = "v${version}"; <del> hash = "sha256-zq63PfKVcCLudsIBugGQIozG4Ve4vgBwYz0ID5k1J5o="; </del> <ins> hash = "sha256-Wx+hUm0y7w0+IYtaRE5X/5Ra37mMEMEliYFbl7c03Ww="; </ins> }; <del> cargoHash = "sha256-jjov7kW6iH+Tfi5XBjMFbRk0a4HRYZ7pWm+Aa0hUndM="; </del> <ins> cargoHash = "sha256-7B5Uxr1SsAx+mRpvQPSW7pemxp11WngEIK6vF2cbzh4="; </ins> nativeBuildInputs = [ installShellFiles

Discussion:
When running with a shortcut, broot shows the errror message . Can you please enable it or make it optional? add to your broot config (HJSON format). this on a file within broot. <!-- 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.
Could you please look into this (i just saw, that you did the recent updates for broot)?
Thank you!
Change:
<ins> In the nix build, COOLWSD_VERSION_HASH becomes the same as COOLWSD_VERSION, e.g. `24.04.3.5`.  The web server that serves files from `/browser/$COOLWSD_VERSION_HASH`, doesn't expect the hash to contain dots. --- a/wsd/FileServer.cpp +++ b/wsd/FileServer.cpp @@ -933,7 +933,7 @@ std::string FileServerRequestHandler::getRequestPathname(const HTTPRequest& requ std::string path(requestUri.getPath()); -    Poco::RegularExpression gitHashRe("/([0-9a-f]+)/"); +    Poco::RegularExpression gitHashRe("/([0-9a-f.]+)/"); std::string gitHash; if (gitHashRe.extract(path, gitHash)) { </ins>

Discussion:
Collabora Online Hi there, As of today, OnlyOffice is packaged in nixpkgs though it has a bug that throws SIG_ILL in x2t transformer. An alternative to onlyoffice, there is Collabora Online. It is an online version of libreoffice that can be integrated into several different portals suchs as nextcloud, moodle etc. I've decided to give it a go to package it into nixpkgs with the following shell: When I've tried to configure it looked for libreofficekit that which I am not familiar with. I've looked into the the libreoffice-collabora package and found only the followings: My question is, is it possible to get dev contents of libreoffice in nixpkgs via some output (usually it is 'dev')? I must admit I do not possess much experience with libreoffice and friends. I assume libreofficekit is a dev extension that can hook up to some functionality in libreoffice, please correct me if I am wrong. I think while the onlyoffice gets a proper fix, it is positive to initiate a conversation for an alternative that is collabora in this particular situtation. best, evrim. Metadata source URL:
Change:
, version , meta , copyDesktopItems <ins> , makeWrapper </ins> }: let

Discussion:
A few electron applications do not use environment variable to change settings. This causes a black screen when using these packages on wayland. Packages I have found not to work: postman beekeeper-studio This was made known to me by on Discord. Steps to reproduce the behavior: Black screen. ! ! A temporary work around is to run the application with the flag. I will work on this myself. <!-- 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.
If any other packages are exhibiting this behavior please let me know on this issue.
Package also seems to not respect the env
Can confirm, I'll create a new pr.
Sorry for taking so long, stuff happened
Ferdium also does not respect the env (and I assume Ferdi and Franz by looking at their sources).
For some reason the following is not working: But this is: I do have both NIXOSOZONEWL and WAYLANDDISPLAY set.
Change:
|--------|------|------------| | scripts | `<list>` | scripts to resolve (`$out`-relative paths) | | interpreter | `"none"` `<path>` | The absolute interpreter `<path>` for the script's shebang. The special value `none` ensures there is no shebang. | <del> | inputs | `<packages>` | Packages to resolve external dependencies from. | </del> <ins> | inputs | `<packages>` `<paths>` | A list of packages and string paths to directories/files to resolve external dependencies from. | </ins> | fake | `<directives>` | pretend some commands exist | | fix | `<directives>` | fix things we can't auto-fix/ignore | | keep | `<directives>` | keep things we can't auto-fix/ignore |

Discussion:
is structured in a way that makes it impossible to write a for an absolute path that’s in the Nix store. Try to build this Nix expression: It will give you this error: That Nix expression builds successfully. To workaround this problem, you can use a fake directive… …or you can use a keep directive that refers to a variable instead of an absolute path: <!-- 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.
I think it might be a misfeature to make this work the way you're trying it--you don't need to interpolate the absolute store path into the script: The API could debatably be improved here by implicitly adding to the path and generate/collect lore for those locations. (I'm not certain that'd be an improvement; I'd probably need to census existing libexec directories and see if the stuff in them is likely to clash with the contents of other directories...)
Now that I know that I can do , I’m inclined to agree. I wouldn’t add to the path by default. It would be confusing because installing or running doesn’t add to your . The thing that would have really helped me here would have been improved documentation. That quote and the code examples made me assume that I was only allowed to put packages in the list. If I had known that I could put paths to directories that contain executables, then I would have probably done that instead of trying to put an absolute store path into the script.
Thanks for this--my next question was going to be whether you had a sense of what the right breadcrumb would've been. (Left to my own devices, I would've gone off adding an admonition to the documentation for keep directives...)
Change:
dualTree = callPackage ../development/libraries/haskell/dual-tree {}; <ins> dyre = callPackage ../development/libraries/haskell/dyre {}; </ins> editDistance = callPackage ../development/libraries/haskell/edit-distance {}; editline = callPackage ../development/libraries/haskell/editline {};

Discussion:
I'm planning to use nix as a package manager for my development toolchain, but not do the actual development in nix, is that a supported use case? I've hit some issues and have been sending in PRs to resolve them, but looking into it more the issues I've been hitting might have been derivations just working as intended. explains that library derivations in Nix only work when used in a nix environment, be it nix-shell or within nixpkgs. Is the same true for all development derivations, for example compilers and build tools? Examples: ++ doesn't work outside of nix-shell on darwin, but it does on linux, and I'm not sure which of the two is correct (). creates compiler wrappers to handle the way flags from dependencies are propagated in nixpkgs, but those wrappers are unnecessary when using the compilers from profiles. the bazel derivation is a script that wraps bazel to make it use clang and java from nix, instead of resolving it from the caller's , so that it can be used from within nixpkgs, but it results in a bazel that doesn't function correctly when installed. If existing development derivations are meant to be only used in a nix environment, would it be ok to add new derivations for use outside of a nix environment?
Nixpkgs do not explicitly support C++ compilers outside Nix environment, but this is a valuable use case and it would be great if you could work towards it.
It won't be helpful if there's no convention around it, how would someone find out which specific compilers work outside a Nix environment and which don't?
Either the default compilers will work (, ), or people will discover the new compilers (e.g. ) in the list of packages, in Nixpkgs issues, on the wiki, on IRC etc.
I have managed to work around this issue by creating wrappers for the compilers tailored to the specific use cases I have. It works very well, and it seems it's what others are doing as well. I'll close this issue since it's not relevant anymore.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
services.portunus.ldap.package = pkgs.openldap.override { libxcrypt = pkgs.libxcrypt-legacy; }; ``` <ins> - The `tracy` package no longer works on X11, since it's moved to Wayland support, which is the intended default behavior by Tracy maintainers. X11 users have to switch to the new package `tracy-x11`. </ins> ## Other Notable Changes {#sec-release-24.11-notable-changes} <!-- To avoid merge conflicts, consider adding your item at an arbitrary place in the list instead. -->

Discussion:
No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Same problem, same message, with the following system. WM: sway
Attempted hacky workaround from This changes error to Progress?
Change:
rake = { source = { remotes = ["https://rubygems.org"]; <del> sha256 = "01j8fc9bqjnrsxbppncai05h43315vmz9fwg28qdsgcjw9ck1d7n"; </del> <ins> sha256 = "1idi53jay34ba9j68c3mfr9wwkg3cd9qh0fn9cg42hv72c6q8dyg"; </ins> type = "gem"; }; <del> version = "12.0.0"; </del> <ins> version = "12.3.1"; </ins> }; }  No newline at end of file

Discussion:
Latest version: 12.3.0 - October 25, 2017 (83 KB) look in master Where does that sha256 hash come from btw?
Change:
devspace = callPackage ../development/tools/misc/devspace { }; <ins> leptosfmt = callPackage ../development/tools/rust/leptosfmt { }; </ins> maturin = callPackage ../development/tools/rust/maturin { inherit (darwin.apple_sdk.frameworks) Security; };

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> { fetchzip, lib }: let version = "1.901b"; in fetchzip { name = "tibetan-machine-${version}"; url = "mirror://debian/pool/main/f/fonts-tibetan-machine/fonts-tibetan-machine_${version}.orig.tar.bz2"; sha256 = "sha256-A+RgpFLsP4iTzl0PMRHaNzWGbDR5Qa38lRegNJ96ULo="; postFetch = '' mkdir -p $out/share/fonts tar xf $downloadedFile --strip-components=1 -C $out/share/fonts ttf-tmuni-${version}/TibMachUni-${version}.ttf ''; meta = with lib; { description = "Tibetan Machine - an OpenType Tibetan, Dzongkha and Ladakhi font"; license = licenses.gpl2Plus; maintainers = with lib.maintainers; [ serge ]; platforms = platforms.all; }; } </ins>

Discussion:
Project description Add Tibetan Machine OpenType font for Tibetan, Dzongkha, and Ladakhi languages. Metadata homepage URL: source URL: mirror://debian/pool/main/f/fonts-tibetan-machine/fonts-tibetan- license: gpl2+ platforms: all
Change:
# generate the new config by merging with the NixOS config options new_cfg=$(printf '%sn' "$old_cfg" | ${pkgs.jq}/bin/jq -c '. * { <del> "devices": (${builtins.toJSON devices}${optionalString (cfg.devices == {} || ! cfg.overrideDevices) " + .devices"}), "folders": (${builtins.toJSON folders}${optionalString (cfg.folders == {} || ! cfg.overrideFolders) " + .folders"}) } * ${builtins.toJSON cfg.extraOptions}') </del> <ins> "devices": ('${escapeShellArg (builtins.toJSON devices)}'${optionalString (cfg.devices == {} || ! cfg.overrideDevices) " + .devices"}), "folders": ('${escapeShellArg (builtins.toJSON folders)}'${optionalString (cfg.folders == {} || ! cfg.overrideFolders) " + .folders"}) } * '${escapeShellArg (builtins.toJSON cfg.extraOptions)}) </ins> # send the new config curl -X PUT -d "$new_cfg" ${cfg.guiAddress}/rest/config

Discussion:
Configuring with special characters (like ) causes the Syncthing service to fail: Device names may be any string that Syncthing supports via its UI. Syncthing does support . (guessing based on ) system: - nixpkgs @
Could you confirm fixes the issue? would also fix it
Yep, fixes it. Thanks!
Change:
<del> --- old/source/rltiles/Makefile	2014-04-17 10:17:31.596400123 +0000 +++ new/source/rltiles/Makefile	2014-04-17 14:36:07.263108690 +0000 @@ -20,7 +20,8 @@ ifdef TILES ifndef CONTRIB_SDL -    SDL_CFLAGS := $(shell sdl-config --cflags 2> /dev/null || echo "-I../contrib/install/$(ARCH)/include/SDL") +    SDL_CFLAGS := $(shell sdl-config --cflags 2> /dev/null) +    SDL_IMG_CFLAGS := $(shell pkg-config --cflags-only-I SDL_image 2> /dev/null) SDL_LDFLAGS := $(shell sdl-config --libs 2> /dev/null && echo "-lSDL_image" || echo "../contrib/install/$(ARCH)/lib/libSDL.a ../contrib/install/$(ARCH)/lib/libSDLmain.a ../contrib/install/$(ARCH)/lib/libSDL_image.a") else SDL_CFLAGS := -I../contrib/install/$(ARCH)/include/SDL @@ -35,7 +36,7 @@ PNG_LIB := ../contrib/install/$(ARCH)/lib/libpng.a ../contrib/install/$(ARCH)/lib/libz.a endif -  CFLAGS += $(SDL_CFLAGS) $(PNG_INCLUDE) +  CFLAGS += $(SDL_CFLAGS) $(SDL_IMG_CFLAGS) $(PNG_INCLUDE) -I$(SDL_image)/include -I$(SDL)/include LDFLAGS += $(SDL_LDFLAGS) $(PNG_LIB) CFLAGS += -DUSE_TILE </del>

Discussion:
Here is the output from nixos-rebuild: I'm not sure if this is a known issue or not, but I made sure to upgrade as well and it is still failing.
Change:
{ stdenv, fetchurl, pkgconfig , bzip2, curl, expat, libarchive, xz, zlib, libuv, rhash <del> , majorVersion ? "3.10" </del> <ins> , majorVersion ? "3.11" </ins> # darwin attributes , ps , isBootstrap ? false

Discussion:
cmake in nixpkgs is 3.10.2. This is over 2 months old. The current version is 3.11.2. This is a problem for me as I'm trying to use cmake to build something that requires 3.11.0 or later. /cc
was merged a day ago, but isn't showing up on nixpkgs-unstable yet. It looks like it was merged into staging rather than trunk. How long does it normally take for package updates like this to make it to trunk?
I merged it into rather than because it causes ~1,000 rebuilds, so if it was merged into it would block the unstable channel from updating. After rebuilds, I will merge it into and then after a small rebuild, it will appear automatically in the unstable channel. This process could take a week if there are many other changes queued in , or a few days otherwise.
Thanks for the explanation!
Change:
, stdenv , substituteAll , fetchurl <ins> , fetchpatch2 </ins> , pkg-config , gettext , graphene

Discussion:
Nautilus shows ghost or duplicated files when moving or deleting files, leaving and returning to the folder shows the actual files. Steps to reproduce the behavior: in a folder with a few folders and files inside a file to wastebasket or into one of the other folders. different folder/file will disappear while the file intended to be moved/deleted will remain. the action will duplicate the intended file. and returning to the folder the actual file structure Show the intended file being deleted/moved. Test folder ! Attempting to remove the file ! Folder 1 disappears instead of the file ! Pressing undo and now the file is duplicated ! Leaving and returning to the folder and it returns to how it should be ! This consistently happens on 3 different machines that I use. My system flake is here <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Upstream issue: , fix should be a patch in gtk4.
Change:
okteto = callPackage ../development/tools/okteto { }; <del> onlyoffice-bin = callPackage ../applications/office/onlyoffice-bin { }; </del> <ins> onlyoffice-bin_7_2 = callPackage ../applications/office/onlyoffice-bin/7_2.nix { }; onlyoffice-bin_7_4 = callPackage ../applications/office/onlyoffice-bin/7_4.nix { }; onlyoffice-bin = onlyoffice-bin_7_2; onlyoffice-bin_latest = onlyoffice-bin_7_4; </ins> onmetal-image = callPackage ../tools/virtualization/onmetal-image { };

Discussion:
Package name: onlyoffice-bin Latest released version: 7.3.3 <!-- Search your package here: --- Current version on the unstable channel: 7.2.0 Current version on the stable/release channel: 7.2.0 <!-- 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.
OnlyOffice 7.4.0 is out now It can be built with the following modifications, however the ability to install plugins such as or is not working, not sure how to resolve that. EDIT: the error message I thought was coming from OO was actually a mesa related error, not plugin related.
It looks as though plugins can still be manually installed, so perhaps is an issue with OnlyOffice being unable to download them into a temporary location
Any thoughts on why the marketplace might be failing or updating onlyoffice-bin in general?
Change:
let <del> jbr = jetbrains.jdk-no-jcef; </del> <ins> jbr = jetbrains.jdk-no-jcef-17; </ins> ideaSrc = fetchFromGitHub { owner = "jetbrains";

Discussion:
Steps to reproduce the behavior: Add any other context about the problem here. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Maybe we should just wait and see whether 2024.02 also has the same problem (that should be around the corner, see ) For now rolling back to to get unstuck.
I'm skeptical about IDEA 2024.2 would use JRE 21, as in the following comment From https://intellij-
Change:
# do not use "''${qemu_kvm}/bin/qemu-kvm" to avoid bound VMs to particular qemu derivations substituteInPlace src/lxc/lxc_conf.c  --replace 'lxc_path,' '"/run/libvirt/nix-emulators/libvirt_lxc",' <ins> substituteInPlace build-aux/meson.build  --replace "gsed" "sed"  --replace "gmake" "make"  --replace "ggrep" "grep" </ins> patchShebangs . '' + (lib.concatStringsSep "n" (lib.mapAttrsToList patchBuilder overrides));

Discussion:
was introduced via , fixing the tarball in wasn't enough.
Are you able to add whichever dependencies are needed?, I do not have a darwin system so i cannot test it myself.
Change:
cargoHash = "sha256-mRi0NUETTdYE/oM+Jo7gW/zNby8dPAKl6XhzP0Qzsf0="; doCheck = false; <del> nativeBuildInputs = [ pkg-config ]; </del> <ins> nativeBuildInputs = [ installShellFiles pkg-config ]; </ins> buildInputs = [ openssl libsodium xxHash ] ++ (lib.optionals gitImportSupport [ libgit2 ]) ++ (lib.optionals stdenv.isDarwin (with darwin.apple_sdk.frameworks; [

Discussion:
Project description can produce completions for a range of shells, including Bash. These should be integrated with the pijul package to improve usability. Metadata homepage URL: source URL: license: gpl2 platforms: all
Change:
stdenvNoCC.mkDerivation rec { pname = "mint-cursor-themes"; <del> version = "1.0.1"; </del> <ins> version = "1.0.2"; </ins> src = fetchFromGitHub { owner = "linuxmint"; repo = pname; # They don't really do tags, this is just a named commit. <del> rev = "e17f8a4620827235dabbe5221bd0ee8c44dad0d5"; hash = "sha256-yLUmIVh884uDVkNil7qxf6t/gykipzBvPgzwmY3zvQk="; </del> <ins> rev = "d2c1428b499a347c291dafb13c89699fdbdd4be7"; hash = "sha256-i2Wf+OKwal9G5hkcAdmGSgX6txu1AHajqqPJdhpJoA0="; </ins> }; installPhase = ''

Discussion:
To reproduce, here is an example: The related code is at Some nice to have: As suggested  should be something that can be accessible by everything and we are likely going to put our "" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.