jiebi/CodeConvo huggingface dataset:
Change:
## `symlinkJoin` {#trivial-builder-symlinkJoin} This can be used to put many derivations into the same directory structure. It works by creating a new derivation and adding symlinks to each of the paths listed. It expects two arguments, `name`, and `paths`. `name` is the name used in the Nix store path for the created derivation. `paths` is a list of paths that will be symlinked. These paths can be to Nix store derivations or any other subdirectory contained within. <ins> Here is an example: ```nix # adds symlinks of hello and stack to current build and prints "links added" symlinkJoin { name = "myexample"; paths = [ pkgs.hello pkgs.stack ]; postBuild = "echo links added"; } ``` This creates a derivation with a directory structure like the following: ``` /nix/store/sglsr5g079a5235hy29da3mq3hv8sjmm-myexample |-- bin |   |-- hello -> /nix/store/qy93dp4a3rqyn2mz63fbxjg228hffwyw-hello-2.10/bin/hello |   `-- stack -> /nix/store/6lzdpxshx78281vy056lbk553ijsdr44-stack-2.1.3.1/bin/stack `-- share |-- bash-completion |   `-- completions |       `-- stack -> /nix/store/6lzdpxshx78281vy056lbk553ijsdr44-stack-2.1.3.1/share/bash-completion/completions/stack |-- fish |   `-- vendor_completions.d |       `-- stack.fish -> /nix/store/6lzdpxshx78281vy056lbk553ijsdr44-stack-2.1.3.1/share/fish/vendor_completions.d/stack.fish ... ``` </ins> ## `writeReferencesToFile` {#trivial-builder-writeReferencesToFile}

Discussion:
In my config I have and when building it gives me the following error: However if I replace it with it builds without errors. Even weirder, If I do it works without problems. The configuration builds normally system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
Tried surrounding the path in quotes?
wouldn't that make a string and not include the file in the store? As it stands, the files does get included in the store because succeds without problems.
Change:
doCheck = !stdenv.isFreeBSD; <del> makeFlags = [ "PREFIX=$(out)" "INSTALLPREFIX=$(out)" ]; </del> <ins> makeFlags = [ "PREFIX=$(out)" ]; </ins> postInstall = '' <del> chmod +x "$out"/lib/libminiupnpc${stdenv.hostPlatform.extensions.sharedLibrary} </del> <ins> chmod +x $out/lib/libminiupnpc${stdenv.hostPlatform.extensions.sharedLibrary} # for some reason cmake does not install binaries and manpages # https://github.com/miniupnp/miniupnp/issues/637 mkdir -p $out/bin cp -a upnpc-static $out/bin/upnpc cp -a ../external-ip.sh $out/bin/external-ip mkdir -p $out/share/man cp -a ../man3 $out/share/man </ins> ''; meta = with lib; {

Discussion:
package used to provide the binary. Now it only contains library files. is available. Previous working build (before ): If applicable, add screenshots to help explain your problem. Seems that this was introduced by <!-- 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.
This change broke my scripts on nixos stable that expected and commands to be present.
Fix in can you please check whether this PR fixes your issue?
Just checked, everything seems to be there and the binary works. Thanks!
merged Backport in
Change:
wantedBy = [ "multi-user.target" ]; serviceConfig = { User = cfg.user; <ins> Group = cfg.group; </ins> ExecStart = "${pkgs.shairport-sync}/bin/shairport-sync ${cfg.arguments}"; RuntimeDirectory = "shairport-sync"; };

Discussion:
shairport-sync module creates the user without a default group, running into enabling causes the following error:
Change:
patches = [ (fetchpatch { <del> url = "https://raw.githubusercontent.com/buildroot/buildroot/master/package/expect/0001-enable-cross-compilation.patch"; </del> <ins> url = "https://raw.githubusercontent.com/buildroot/buildroot/c05e6aa361a4049eabd8b21eb64a34899ef83fc7/package/expect/0001-enable-cross-compilation.patch"; </ins> sha256 = "1jwx2l1slidvcpahxbyqs942l81jd62rzbxliyd9lwysk38c8b6b"; }) ];

Discussion:
Describe the bug expect cannot be cross compiled on master of as of writing. To Reproduce Steps to reproduce the behavior: -build -A pkgsCross.aarch64- Additional context Do you have any idea?
Has this ever worked? This looks like an error message saying they explicitly don't support cross-compilation. Alternatively, it looks like a ton of people are already patching around this:
Probably not. Looking for a patch.
Change:
<ins> { config, pkgs, lib, ... }: with lib; let cfg = config.services.readarr; in { options = { services.readarr = { enable = mkEnableOption (lib.mdDoc "Readarr"); dataDir = mkOption { type = types.str; default = "/var/lib/readarr/"; description = lib.mdDoc "The directory where Readarr stores its data files."; }; package = mkOption { type = types.package; default = pkgs.readarr; defaultText = literalExpression "pkgs.readarr"; description = lib.mdDoc "The Readarr package to use"; }; openFirewall = mkOption { type = types.bool; default = false; description = lib.mdDoc '' Open ports in the firewall for Readarr ''; }; user = mkOption { type = types.str; default = "readarr"; description = lib.mdDoc '' User account under which Readarr runs. ''; }; group = mkOption { type = types.str; default = "readarr"; description = lib.mdDoc '' Group under which Readarr runs. ''; }; }; }; config = mkIf cfg.enable { systemd.tmpfiles.rules = [ "d '${cfg.dataDir}' 0700 ${cfg.user} ${cfg.group} - -" ]; systemd.services.readarr = { description = "Readarr"; after = [ "network.target" ]; wantedBy = [ "multi-user.target" ]; serviceConfig = { Type = "simple"; User = cfg.user; Group = cfg.group; ExecStart = "${cfg.package}/bin/Readarr -nobrowser -data='${cfg.dataDir}'"; Restart = "on-failure"; }; }; networking.firewall = mkIf cfg.openFirewall { allowedTCPPorts = [ 8787 ]; }; users.users = mkIf (cfg.user == "readarr") { readarr = { description = "Readarr service"; home = cfg.dataDir; group = cfg.group; isSystemUser = true; }; }; users.groups = mkIf (cfg.group == "readarr") { readarr = { }; }; }; } </ins>

Discussion:
Readarr Readarr is a ebook collection manager for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new books from your favorite authors and will interface with clients and indexers to grab, sort, and rename them. Metadata homepage URL: source URL: license: GNU GPL v3 platforms: Windows, Linux, macOS, Raspberry Pi, etc.
As you bundled some of the *arr software earlier, I'd be interested in trying out to package readarr, however I have 0 experience with these kind of package and the dotnet environment. Would one of you be willing to help me?
Pretty much the same tbh, I'd honestly just start with a copy of one of the existing snippets and change the appropriate parts.
Change:
installPhase = '' for f in Products/Release/*; do if [ -f $f ]; then <del> install -D $file $out/bin/$(basename $f) </del> <ins> install -D $f $out/bin/$(basename $f) </ins> fi done

Discussion:
Describe the bug The  package fails to build on both , and . Hydra: To Reproduce Metadata Please run and paste the result. Maintainer information: CC
It seems that these derivations are on the nix cache so it used to build at some point in the past.
I marked this as stale due to inactivity. &rarr;
Change:
plujain-ramp = callPackage ../applications/audio/plujain-ramp { }; <del> inherit (callPackages ../servers/plik { }) </del> <ins> inherit (callPackage ../servers/plik { }) </ins> plik plikd; plex = callPackage ../servers/plex { };

Discussion:
The NixOS tests for netbox are failing to evaluate: It seems like the module tries to override the package to pass in the plugins that are configured in the module, but for some reason it's overriding the function in instead of the one in . The former doesn't have a plugins argument, so that causes this error. You can also replicate this in : I don't really know what changed to cause this to happen, as it doesn't seem like it should. Steps to reproduce the behavior: The system configuration should evaluate. <!-- 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]:
Possibly related issue with an which used to work: Ping
The thing these packages have in common seems to be that they use to pull in a few different versions into . It seems like something changed about recently.
I think you're right, That commit changes to for a bunch of packages, including citrix_workspace and netbox.
Change:
hddfancontrol = handleTest ./hddfancontrol.nix {}; hedgedoc = handleTest ./hedgedoc.nix {}; herbstluftwm = handleTest ./herbstluftwm.nix {}; <ins> homebox = handleTest ./homebox.nix {}; </ins> homepage-dashboard = handleTest ./homepage-dashboard.nix {}; honk = runTest ./honk.nix; installed-tests = pkgs.recurseIntoAttrs (handleTest ./installed-tests {});

Discussion:
Project description Like a simpler Snipe-IT for home usage. Keep track of inventories, warranties, and manuals. Metadata homepage URL: https://hay- source URL: license: APL3 platforms: presumably Go's platforms? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It makes use of , so is technically a blocker. I'm hoping it will work with to bypass that issue.
homebox was archived:
feel free to reopen if there's maintained, viable fork.
I see picking up activity, tentatively re-opening the issue for now. Will revisit to see if it keeps being maintained long term.
There's an active repo being worked on here:
Change:
<ins> { lib, buildGoModule, fetchFromGitHub, fetchpatch, installShellFiles }: buildGoModule rec { pname = "ets"; version = "0.2.1"; src = fetchFromGitHub { owner = "zmwangx"; repo = pname; rev = "v${version}"; sha256 = "sha256-XWIDo5msTMTLr60x1R9cwsiZIDG6G+uHWx8idt4F2iA="; }; # https://github.com/zmwangx/ets/pull/18/ patches = [ (fetchpatch { url = "https://github.com/zmwangx/ets/commit/600ec17a9c86ca63cd022d00439cdc4978e2afa9.patch"; sha256 = "sha256-SGCISHkWNFubgKkQYx8Vf5/fknNDfPNYkSuw1mMhZaE="; }) ]; vendorSha256 = "sha256-+8dXfqOu8XTw2uEx3GAynQSHtzifejZtddr1CdxrupA="; ldflags = [ "-s" "-w" "-X main.version=v${version}-nixpkgs" ]; nativeBuildInputs = [ installShellFiles ]; preBuild = '' rm -rf fixtures ''; postInstall = '' installManPage ets.1 ''; doCheck = false; meta = with lib; { description = "Command output timestamper"; homepage = "https://github.com/zmwangx/ets/"; license = licenses.mit; maintainers = with maintainers; [ cameronfyfe ]; }; } </ins>

Discussion:
Project description is a command output timestamper similar to in moreutils. Primary advantages over are the non-conflicting command name and its handling of progress bars. See "Comparison to moreutils ts" section in source repo for more complete comparison. Metadata homepage URL: source URL: license: mit platforms: linux, darwin
Change:
<ins> --- a/src/core/config/common.pri +++ b/src/core/config/common.pri @@ -47,3 +47,5 @@ !qtConfig(webengine-nodejs10): gn_args += use_rollup=false gn_args += enable_ipc_logging=false + +gn_args += link_pulseaudio=true </ins>

Discussion:
I found this bug while trying to create a package for (mentioned in ), but it seems all qtwebengine-based browsers like Qutebrowser and Falkon have the same issue. These browsers are able to pick up my microphone just fine, but any virtual devices created via pipewire do not show up. discord-screenaudio creates a virtual source to pipe desktop audio through, which then is meant to be detected as an audio input inside a qtwebengine window linked to Creating virtual devices manually via (following ) also doesn't work, as they do not show up in Qutebrowser or Falkon. They do show up in Firefox, Chromium, and the native Discord client, however. pipewire running as the audio server a virtual audio device using to on Falkon or Qutebrowser and see that does not show up in the input list. does show up in Falkon or Qutebrowser One final difference I see is within the Helvum program, where I can see how audio devices are connected. When Firefox, Chromium and Discord use my microphone a connection is made in Helvum, but when Qutebrowser, Falkon, or discord-screenaudio do no connection is visible. To me it seems that qtwebengine-based browsers must not be connecting to pipewire or pipewire-pulse at all, but talking to the audio devices directly somehow. (qtwebengine) Please run and paste the result.
I'm unsure if I should also mention the maintainers of Falkon and Qutebrowser here since it seems the issue lies with qtwebengine
You should, I think it's safe to say qtwebengine is pretty much maintained for qutebrowser alone. I don't use pipewire/pulse but I think does.
Alright then: falkon's maintainer is other qutebrowser maintainers that have not been mentioned yet are
I do use pipewire, but not virtual audio devices. Have you ensured that you have xdg-desktop-portal-wlr setup correctly? I have to run this sequence of commands in order to get screensharing to work, for example: Where is set to Of course, if you are not using wayland then you'd want instead of
Weird. I'm on X11, not wayland.

I both wireplumber and xdg-desktop-portal via the nixos configuration options and it still doesn't make a difference, even when running those commands before running these browsers
Is xdg-desktop-portal required for pipewire audio support in qtwebengine?
I don't think so since the mic was working even when video capture is not (and the later does requre it). However there appears to have been a regression recently, I just bumped my pin just yesterday and now my mic is not working at all in qutebrowser.
Can you paste the code for creating the package you have so far?
This still seems like an issue, see further attempts at packaging discord-screenaudio in .
The issue has indeed been fixed!
Change:
vscodeDefault = vscode; }; vscodeExts2nix = import ./vscodeExts2nix.nix { inherit lib writeShellScriptBin; vscodeDefault = vscode;

Discussion:
Describe the bug A clear and concise description of what the bug is. the vscode-extensions directory has the structure so should be called with the argument instead of To Reproduce Steps to reproduce the behavior: ... ... ... Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run and paste the result. Maintainer information:
Change:
enable = true; startAt = "20:00"; }; <ins> phpExtraExtensions = all: [ all.bz2 ]; </ins> }; environment.systemPackages = [ cfg.services.nextcloud.occ ];

Discussion:
Many nextcloud extensions like need additional php extensions that are not part of the . It would be great to either: Provide an option to override the php package nextcloud uses, i.e. Or: Provide an option , and make the current extension selection its default value I'm opening this as an issue to get some feedback on what the better option is, and to get the naming right. CC maintainers
Meta: I'm not sure all labels I've applied make sense here. Feel free to remove inappropriate ones. Also: There is no PHP label?
cc
Change:
gdk-pixbuf gtk3 libX11 <ins> libexif # image properties page </ins> libgudev libnotify libxfce4ui libxfce4util <del> pcre </del> <ins> pcre2 # search & replace renamer xfce4-panel # trash panel applet plugin </ins> xfconf ];

Discussion:
Originally reported in , the "regular expression" checkbox in Thunar's bulk renamer is disabled. multiple files. -Click → Rename. "Search & Replace" The "Regular Expression" option can be checked. It looks to me like Thunar now wants wants pcre2, not pcre. <!-- 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]:
Change:
nativeBuildInputs = [ cmake <del> ] ++ lib.optionals withGstreamer [ </del> <ins> ] ++ lib.optionals (withGstreamer || withOmemo) [ </ins> pkg-config ]; buildInputs = lib.optionals withGstreamer (with gst_all_1; [

Discussion:
Steps to reproduce the behavior: kaidan <!-- 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]:
Thanks for notifying me!
Change:
, hamlib , wxGTK31-gtk3 , pulseSupport ? config.pulseaudio or stdenv.isLinux <ins> , AppKit , AVFoundation , Cocoa , CoreMedia </ins> }: stdenv.mkDerivation rec {

Discussion:
Building freedv on darwin fails. Steps to reproduce the behavior: It builds. This is the error message from the build: Seems the maintainer doesn't exist or is not a github name. Please run and paste the result.
As a first step, I created to mark the build broken on darwin.
I’ll assign the issue to for now as they were already investigating the matter.
I'm still seeing the issue, even after : This is on: system: host os: multi-user?: sandbox: version: channels(nknezevi1): nixpkgs:
Change:
qtWrapperArgs+=(--prefix GST_PLUGIN_SYSTEM_PATH_1_0 : "$GST_PLUGIN_SYSTEM_PATH_1_0") ''; <ins> passthru = { updateScript = nix-update-script { attrPath = pname; }; }; </ins> meta = with lib; { description = "Sayonara music player"; homepage = "https://sayonara-player.com/";

Discussion:
Describe the bug A clear and concise description of what the bug is. The and python scripts in need their interpreter to be patched (and the module available). To Reproduce Steps to reproduce the behavior: Expected behavior A clear and concise description of what you expected to happen. They should work :stuckouttongue:. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(bt1cn): nixpkgs: Maintainer information:

<!-- 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: sayonara <!-- 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.6.0-beta6 desired version: 1.6.0-beta7 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Change:
, python, pygobject3, gtk3, gnome3, substituteAll , at-spi2-atk, at-spi2-core, pyatspi, dbus, dbus-python, pyxdg , xkbcomp, procps, lsof, coreutils, gsettings-desktop-schemas <del> , speechd, brltty, setproctitle, gst_all_1, gst-python </del> <ins> , speechd, brltty, liblouis, setproctitle, gst_all_1, gst-python </ins> }: buildPythonApplication rec {

Discussion:
has been broken on master for a while now, blocking orca. I opened an but they are not sure how to fix it.
I removed it from orca in
Change:
liblbfgs = callPackage ../development/libraries/science/math/liblbfgs { }; openblas = callPackage ../development/libraries/science/math/openblas { }; <ins> openblas_2_14 = callPackage ../development/libraries/science/math/openblas/0.2.14.nix { }; </ins> # A version of OpenBLAS using 32-bit integers on all platforms for compatibility with # standard BLAS and LAPACK. openblasCompat = openblas.override { blas64 = false; }; <ins> openblasCompat_2_14 = openblas_2_14.override { blas64 = false; }; </ins> openlibm = callPackage ../development/libraries/science/math/openlibm {};

Discussion:
But we cannot upgrade to openblas 0.2.15 either, due to runtime issues (segfault?). Possible fix is to package the openblas 'develop' branch. See discussions: CC
Did you try with 2.15 yourself? We could also go back to Atlast + Lapack. It would mean changing and the same line in . And of course
I just built numpy with openblas 0.2.15 and did . Nothing more. (numpy is just being pulled in as a dependency on my system, I don't really have any specific use for it at the moment.) If upstream makes a new release in a week, I can wait for that.
Good. I think we do need to have a solution for the new stable.
They put out an RC:
I'm now testing the RC. , do you know whether would hide processor information?
I'm pretty sure it doesn't.
Evaluation with openblas 0.2.15: Evaluation with openblas 0.2.16.rc1: We get a segfault with scikitlearn when using 0.2.15, but not anymore with 0.2.16.rc1. , could you try building the current PR?
That is, this one
I've evaluated numpy/scipy/scikitlearn without issues using openblas 0.2.17. See
Because we use openblas 0.2.17 now I am closing this.

When I try to install openblas I get following failure:
Are you building with chroot environments enabled or disabled?
I'm not sure if I'm building with chroot environments enabled or disabled, how could I figure out? I've installed the nix package manager on an ubuntu install to manage packages with nix.
What does your file say?
I don't have an My is here:
If you don't have it, then the builds should be non-chrooted. Anyway, that's the most likely explanation why it succeeds on Hydra and not for you (we could still fix it, but it's not a high priority for me as chrooting solves many problems).
'Detecting CPU failed' happened to me as well, on a machine with intel broadwell CPU. I made an upstream issue and was told to build from their 'develop' branch (I don't think they use 'master'). The develop branch worked. We should prod them to make a new release.
This is not currently affecting me.
This is still an issue for nix installations outside of /nix (which seem unchrootable). Explicitly adding TARGET=NEHALEM just like in the travis build seems to work:
Change:
, xz , e2fsprogs , libsoup <ins> , glib-networking , wrapGAppsHook </ins> , gpgme , which , makeWrapper

Discussion:
Describe the bug When I try to pull from a remote repository using ostree, it fails. Note that flatpak is not affected, just ostree. To Reproduce Steps to reproduce the behavior: Expected behavior It would download the source files of org.freedesktop.Sdk (actually I'm not sure I'm doing that part right, but the TLS error seems like a Nix problem) Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(qolen): nixpkgs: Maintainer information:
This is a problem with not getting set properly. Should we wrap the ostree binary?
When I set in the derivation, as i've seen suggsted, I get "Failed to load TLS database: Failed to load system trust store: Error while reading file." instead
(seems to be the same issue as )