jiebi/CodeConvo huggingface dataset:
Change:
<ins> { lib, stdenv, fetchurl, jre, wrapGAppsHook, nix-update-script, }: stdenv.mkDerivation rec { pname = "biglybt"; version = "3.5.0.0"; src = fetchurl { url = "https://github.com/BiglySoftware/BiglyBT/releases/download/v${version}/GitHub_BiglyBT_unix.tar.gz"; hash = "sha256-ToTCIjunj/ABi3wVSmeddLGBdQlv+CfK2jGRjixJd0w="; }; nativeBuildInputs = [ wrapGAppsHook ]; configurePhase = '' runHook preConfigure sed -e 's/AUTOUPDATE_SCRIPT=1/AUTOUPDATE_SCRIPT=0/g'  -i biglybt || die runHook postConfigure ''; installPhase = '' runHook preInstall install -d $out/{share/{biglybt,applications,icons/hicolor/scalable/apps},bin} cp -r ./* $out/share/biglybt/ ln -s $out/share/biglybt/biglybt.desktop $out/share/applications/ ln -s $out/share/biglybt/biglybt.svg $out/share/icons/hicolor/scalable/apps/ wrapProgram $out/share/biglybt/biglybt  --prefix PATH : ${lib.makeBinPath [ jre ]} ln -s $out/share/biglybt/biglybt $out/bin/ runHook postInstall ''; passthru.updateScript = nix-update-script { extraArgs = [ "--version-regex" "^(v[0-9.]+)$" ]; }; meta = { changelog = "https://github.com/BiglySoftware/BiglyBT/releases/tag/v${version}"; description = "A BitTorrent client based on the Azureus that supports I2P darknet for privacy"; downloadPage = "https://github.com/BiglySoftware/BiglyBT"; homepage = "https://www.biglybt.com/"; license = lib.licenses.gpl3Plus; platforms = lib.platforms.unix; sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ]; mainProgram = "biglybt"; maintainers = with lib.maintainers; [ raspher ]; }; } </ins>

Discussion:
Project description A torrent downloader written in Java, with support for almost all things related to torrent (i2p, tor, dht, mainline dht, etc. see homepage) Vuze development stopped 4 years ago, BiglyBT is continuation of Vuze. Metadata homepage URL: source URL: license: GPL-2.0 platforms: it's java - Windows, Linux, MacOS (legacy too), BSD, Android ... _(it should probably work even on haiku)
This pull request is closed, because i are banned.
I marked this as stale due to inactivity. &rarr;
I've worked on it a little, got working package. There might be problems with autoupdate - shared plugins cannot self-update as they're builded into package. Auto-updating can be disabled in settings, which are saved per user in
Change:
inherit (python3Packages) bedup; <ins> bolt = callPackage ../os-specific/linux/bolt { }; </ins> bridge-utils = callPackage ../os-specific/linux/bridge-utils { }; busybox = callPackage ../os-specific/linux/busybox { };

Discussion:
As described in , GNOME 3 needs the to handle authenticating Thunderbolt 3 devices. This is not yet packaged for NixOS. I've bolt myself but have thus far been unsuccessful. Start a Gnome 3 session Navigate to Settings → Devices → Thunderbolt Expected Results: A nice GUI as . Actual Results: An error message: ! (Note: The error message is slightly misleading. Thunderbolt 3 is supported and working on my laptop, albeit with authorization disabled, but without GNOME doesn't know that.) system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Can you share the errors you have encountered when packaging? Perhaps we can point you to solution.
Right now I'm hitting two roadblocks with bolt itself: the man pages fails somewhere inside asciidoc: I'm not sure how to get more information / further work on that. I disable manpage generation (), everything compiles and links just fine but then fails with:
Yeah, meson sometimes gives incredibly useless error messages. The problem is the build trying to install files in and , which it looks up through pkgconfig. Adding these fixes these: We'll also need to knock out as it tries to create a directory in . This fixed the build for me:
You can try to add flag to the asciidoc command in the meson file (I recommend setting to the local checkout of the project in question). As for the second error, Meson only calls when it fails to write to install destination, which means that some is probably wrong.
There ought to be a message Perhaps you can find it in build directory under if you run with .
Woohoo! ! Now I just have to: things up out how to get the systemd unit file linked out how to properly test a patch against this repo request!
We'll have to make module, something like this: Will probably need too.
Change:
ldflags = [ "-s" "-w" "-X" "main.Version=${version}" ]; <ins> tags = [ "netgo" "osusergo" "static_build" ]; postInstall = '' mkdir -p $out/share/oh-my-posh cp -r ${src}/themes $out/share/oh-my-posh/ ''; </ins> meta = with lib; { description = "A prompt theme engine for any shell"; homepage = "https://ohmyposh.dev";

Discussion:
The package is missing the theme files that are provided by the source. The theme files should be included in the nix store. As an example of how to do it, look at the from
I took the liberty to create a PR for this. Could you please review?
Change:
hyperrogue = callPackage ../games/hyperrogue { }; <ins> ibmcloud-cli = callPackage ../tools/admin/ibmcloud-cli { stdenv = stdenvNoCC; }; </ins> icbm3d = callPackage ../games/icbm3d { }; infra = callPackage ../tools/admin/infra { };

Discussion:
Project description <!-- Describe the project a little: --The command line client for . Metadata homepage URL: source URL: license: ? platforms: linux
Change:
]; preFixup = '' <del> gappsWrapperArgs+=(--prefix PATH : "${lib.makeBinPath [ mtools cdrkit libcdio qemu-utils ]}") </del> <ins> gappsWrapperArgs+=(--prefix PATH : "${lib.makeBinPath [ mtools cdrkit libcdio qemu-utils qemu ]}") </ins> ''; postPatch = ''

Discussion:
When creating a new VM and reaching "Review and create" step buttons "Create" and "Customize" do nothing (i.e. VM cannot be created). Judging from console logs, it tries to find QEMU binary at and predictably fails. Steps to reproduce the behavior: on stable on "+" and run "Create a Virtual Machine" wizard. any OS source. the step "Express Installation" select whatever settings. the step "Review and Create" no actual properties are displayed, buttons "Customize" and "Create" do nothing. VM can be created, VM properties can be viewed and customized. ! Console log: <!-- 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. Maintainer information:
Try
Change:
<ins> { cabal, cereal, deepseq, mtl, primitive, transformers, vector , zlib }: cabal.mkDerivation (self: { pname = "JuicyPixels"; version = "1.3"; sha256 = "07wljfag4ylw16wdi7znjb61pfihdik5d7p4h2lmz6xirm4mjzrm"; buildDepends = [ cereal deepseq mtl primitive transformers vector zlib ]; meta = { homepage = "https://github.com/Twinside/Juicy.Pixels"; description = "Picture loading/serialization (in png, jpeg and bitmap)"; license = self.stdenv.lib.licenses.bsd3; platforms = self.ghc.meta.platforms; }; }) </ins>

Discussion:
buildNimPackage example in unstable docs is wrong Should be I am not sure, since doc mismatched, if it was intended to be that way or not. <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Related PR: Introduced by Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
hash = "sha256-BOGh+QBTO7hrHohh+RqjSF8eHQH8jVBPjG/k4eyFaaM="; }; <ins> patches = [ # Fix build with Darwin SDK 11 ./0001-fix-darwin-build.patch ]; </ins> postPatch = lib.concatStringsSep "n" [ # Don't reference compile time dependencies or create a build outputs cycle # between out and dev

Discussion:
Steps to reproduce the behavior: latest It was reported originally in , it seems to be an issue with the version of Swift that's being used. <!-- 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]:
Change:
<del> diff --git a/test/run b/test/run index 43a57312..398be8d8 100755 --- a/test/run +++ b/test/run @@ -148,21 +148,17 @@ file_size() { objdump_cmd() { local file="$1" -    if $HOST_OS_APPLE; then -        xcrun dwarfdump -r 0 "$file" -    elif $HOST_OS_WINDOWS || $HOST_OS_CYGWIN; then +    if $HOST_OS_WINDOWS || $HOST_OS_CYGWIN; then # For some reason objdump only shows the basename of the file, so fall # back to brute force and ignorance. strings "$1" else -        objdump -W "$file" +        @objdump@ -W "$file" fi } objdump_grep_cmd() { -    if $HOST_OS_APPLE; then -        grep -Fq ""$1"" -    elif $HOST_OS_WINDOWS || $HOST_OS_CYGWIN; then +    if $HOST_OS_WINDOWS || $HOST_OS_CYGWIN; then grep -Fq "$1" else grep -Fq ": $1" </del>

Discussion:
fails to build while cross-compiling on a host from . Steps to reproduce the behavior: from on a host Maintainer information:
I don't have any problems building , the tests are disabled in a cross compilation build. Are you doing anything extra to enable them? It seems like the failure can be fixed by replacing with , but I'm not sure how you've enabled the tests, so I can't verify if it works.
Yes, I'm surprised the tests are running at all in a cross-compilation scenario. Maybe you are already on a 32-bit build machine, but forcing the cross-compilation pathway with pkgsCross? Also, unrelated to this specific issue, if you are trying to build 32-bit binaries on an x86 host you may have better luck with , which tends to be more reliable as it builds natively.
Well, I did a quick test using in this configuration. I am not using it anymore and, as you mentioned, it probably was some kind of misconfiguration on my side. I will re-open the issue in case this is actually an issue. As a side note, that's what I was doing but I had to cross-compile in the end. Thanks for the suggestion! Sorry for bothering you and thank you for your prompt response!
I've encountered the same issue - not with , but with , more precisely (ccache wrapper correctly uses buildPackages). Edit: fixed
Change:
buildPythonPackage rec { pname = "scikit-learn"; <del> version = "0.21.2"; </del> <ins> version = "0.21.3"; </ins> # UnboundLocalError: local variable 'message' referenced before assignment disabled = stdenv.isi686;  # https://github.com/scikit-learn/scikit-learn/issues/5534 src = fetchPypi { inherit pname version; <del> sha256 = "1nvj9j16y1hz9gm0qwzpnx2zmz55c63k1fai643migsyll9c7bqa"; </del> <ins> sha256 = "eb9b8ebf59eddd8b96366428238ab27d05a19e89c5516ce294abc35cea75d003"; </ins> }; buildInputs = [

Discussion:
Describe the bug scikit-learn fails to build when is set for numpy. To Reproduce Steps to reproduce the behavior: full output:
Unfortunately, scikit-learn is breaking again when built with MKL--possibly due to Weirdly, I can't see the output of what test is failing:
Change:
}); asciidoctor = callPackage ../tools/typesetting/asciidoctor { <del> # kindlegen is unfree, don't enable by default kindlegen = null; </del> # epubcheck pulls in Java, which is problematic on some platforms epubcheck = null; };

Discussion:
. Consequently, the is broken. I suppose we need to choose whether to remove the package or find a mirror? CC maintainer: Side notes: Sadly, its replacement, , has no Linux support. But on a more positive note, there are other programs that can produce mobi files, some mentioned in .
I suggest we just drop it. Considering that kindlegen was under an unfree license, we're probably not allowed to distribute it, so let's just blow it away with a release note entry that mentions some alternatives.
I marked this as stale due to inactivity. &rarr;
My current recommendation for NixOS is to use calibre for conversion. It also has commandline tools for scripting.
Change:
{ config, lib, pkgs, ... }: <del> with lib; </del> let <del> toStr = value: if true == value then "yes" else if false == value then "no" else toString value; </del> <ins> inherit (lib.attrsets) optionalAttrs; inherit (lib.generators) toINIWithGlobalSection; inherit (lib.lists) optional; inherit (lib.modules) mkIf; inherit (lib.options) literalExpression mkEnableOption mkOption; inherit (lib.strings) escape; inherit (lib.types) attrsOf bool int lines oneOf str submodule; </ins> cfg = config.services.davfs2; <del> format = pkgs.formats.toml { }; configFile = let settings = mapAttrsToList (n: v: "${n} = ${toStr v}") cfg.settings; in pkgs.writeText "davfs2.conf" '' ${concatStringsSep "n" settings} ${cfg.extraConfig} ''; </del> <ins> escapeString = escape [""" ""]; formatValue = value: if true == value then "1" else if false == value then "0" else if builtins.isString value then ""${escapeString value}"" else toString value; configFile = pkgs.writeText "davfs2.conf" ( if (cfg.settings != { }) then (toINIWithGlobalSection { mkSectionName = escapeString; mkKeyValue = k: v: "${k} ${formatValue v}"; } cfg.settings) else cfg.extraConfig ); </ins> in { options.services.davfs2 = { <del> enable = mkOption { type = types.bool; default = false; description = lib.mdDoc '' Whether to enable davfs2. ''; }; </del> <ins> enable = mkEnableOption "davfs2"; </ins> davUser = mkOption { <del> type = types.str; </del> <ins> type = str; </ins> default = "davfs2"; <del> description = lib.mdDoc '' </del> <ins> description = '' </ins> When invoked by root the mount.davfs daemon will run as this user. Value must be given as name, not as numerical id. ''; }; davGroup = mkOption { <del> type = types.str; </del> <ins> type = str; </ins> default = "davfs2"; <del> description = lib.mdDoc '' </del> <ins> description = '' </ins> The group of the running mount.davfs daemon. Ordinary users must be member of this group in order to mount a davfs2 file system. Value must be given as name, not as numerical id.

Discussion:
The most recent for davfs2 adds an (equal sign) between keys/values in should be According to the man page: This causes the following error : Steps to reproduce the behavior: in systemd mount: `/etc/davfs2/secrets file using sops-nix or creating the file. Except to see the webdav mount successfully mounted at /mnt/nextcloud without any log errors. N/A Just looks like an inadvertent change in the latest PR. Please run and paste the result.
Change:
install -D -m 755 out_linux/Release/mozc_server $out/lib/mozc/mozc_server install    -m 755 out_linux/Release/mozc_tool   $out/lib/mozc/mozc_tool <ins> wrapQtApp $out/lib/mozc/mozc_tool </ins> install -d        $out/share/doc/mozc install -m 644    data/installer/*.html         $out/share/doc/mozc/

Discussion:
Related to doesn't work as intended, instead closing immediately with return code 255. This is caused by the usage of instead of in , as is an Qt application. I tried to do this: And in : But apparently must be compiled with clang only: I tried adding to , but ( is branch of ) Same applies for and probably to the rest of Qt applications with non-default . Maybe I'm doing something wrong, but I'm not sure how to fix this. To reproduce : 1) Open 2) Choose "Input Method" 3) Add - Japanese - Mozc 4) Choose "Japanese - Mozc" 5) Click "Preferences" A menu must appear, but nothing happens. Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(zepsy): nixpkgs:
Don't think it matters, but switching to doesn't help. Also, installing fixes the problem. Obviously that's not a proper solution but it can be used as a temporary workaround.
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
Wow, it actually got fixed. Thanks!
Change:
# Eclipse /pkgs/applications/editors/eclipse @rycee <ins> # https://github.com/NixOS/nixpkgs/issues/31401 /lib/maintainers.nix @ghost </ins>

Discussion:
and are listed as code owners for . That means they are requested for review whenever a new maintainer is to the list. Last matching pattern is used, so if is on its own line without any users, this would be fixed. Feel free to close if this is intended.
Is there a way to specify any empty list of reviewers? Otherwise, we could make it a bot, which checks that the patch is only adding lines, and that the files evaluate properly.
I think just listing no users would work but to make sure that it parses user can be .
Change:
disabledTests = [ # probably failing because of an encoding related issue "test_create_wrong_encoding" <ins> ] ++ lib.optionals (stdenv.isDarwin && !stdenv.isAarch64) [ "test_delete" </ins> ]; disabledTestPaths = [

Discussion:
Describe the bug upgraded to 2.0.0, but this version is broken on darwin: It appears this is because ' macOS SDK is 10.12, but the symbols that cause problems in 2.0.0 are only available in 10.13+:
Issue regarding newer SDK
I'm also seeing watchdog as a blocker for installing some packages. e.g., installing was-sam-cli is broken: Any work-around or fix?
Still happens with watchdog
Yeah, unfortunately, I think nothing is going to change on this issue until someone has time to upgrade the macOS SDK ()
That's happening at as part of
What if the package uses sdk_11 for now?
It needs , so maybe fine.
Talking to this doesn't seem so simple. The 11 SDK is only available through the Aarch64 stdenv IIUC. So maybe this package doesn't need to be marked broken for Aarch64 Darwin, could someone using native Nix on an M1 mac confirm this? Making it available on x86_64 properly would entail as much work as bumping the SDK to 10.13 does because we have as much as possible depend on the Apple source releases rather than the SDK. So I don't think this'd be an easy workaround. would be better able to judge how practical the idea is though.
<details<summaryHere's what I tried, from a checkout of master: </summary</detailsI suspect the problem is trying to with the 10.12 darwin-stubs, which could explain missing dylibs. The usual 10.12 expression explicitly depends on but does not so I'm not able to override it. I'm not sure why this is,
Maybe it's using impure stubs from the host? Would be cool if someone running Big Sur could confirm or deny whether the above works for them.
I ran into the same issue on Big Sur.
Just coming into this but I see this has been merged? Is there anything to be done here? Thanks A
sorry for causing confusion. That PR became just a bump of LLVM and the bit that was merged is just the small bootstrap-tools bump the work depends on. So this has no impact on this issue. I continue to work on both getting LLVM updated and the Apple SDK. You can keep an eye on or the Discourse thread for updates.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I marked this as stale due to inactivity. &rarr;
Package ‘python3.9-watchdog-2.1.6’ in /nix/store/16znkxs25xghynrdrrcf3asczxh3hdm3-nixpkgs-22.05pre346850./nixpkgs/pkgs/development/python- is marked as broken, refusing to evaluate.
Hi all, is there a recommended workaround for this?
I used to create a Python virtualenv with my , then just install directly with inside that virtualenv: I mainly use this for , and it WAS working correctly. I don't have a mac currently, so can't say if it still works, but you can give it a try.
Change:
flux = callPackage ../development/compilers/flux { }; <del> fido2luks = callPackage ../tools/security/fido2luks { }; </del> fierce = callPackage ../tools/security/fierce { }; figlet = callPackage ../tools/misc/figlet { };

Discussion:
Steps to reproduce the behavior: Enable or run <!-- 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 seems to still be an issue
Issue filed upstream, fix was a simple update to as well as a for good measure.
(I kinda figured the reference as rendered by GitHub immediately above my comment would be sufficient)
shimunn has responded on the issue on the upstream repo, and is asking us to start using 0.3. I'd personally suggest we stick with 0.2 and either vendor it or patch it. The changed files are just and , which I'm attaching both of as confirmed working. I'm not sure the preferred way to address it, but I hope this helps.
Change:
preStart = '' <del> # Create data directory. </del> if ! test -e ${cfg.dataDir}/PG_VERSION; then <del> mkdir -m 0700 -p ${cfg.dataDir} </del> <ins> # Cleanup the data directory. </ins> rm -f ${cfg.dataDir}/*.conf <del> chown -R postgres:postgres ${cfg.dataDir} fi ''; # */ script = '' # Initialise the database. if ! test -e ${cfg.dataDir}/PG_VERSION; then </del> <ins> # Initialise the database. </ins> initdb -U ${cfg.superUser} ${concatStringsSep " " cfg.initdbArgs} # See postStart! touch "${cfg.dataDir}/.first_startup" fi ln -sfn "${configFile}" "${cfg.dataDir}/postgresql.conf" ${optionalString (cfg.recoveryConfig != null) '' ln -sfn "${pkgs.writeText "recovery.conf" cfg.recoveryConfig}"  "${cfg.dataDir}/recovery.conf" ''} <del> ${optionalString (!groupAccessAvailable) '' # postgresql pre 11.0 doesn't start if state directory mode is group accessible chmod 0700 "${cfg.dataDir}" ''} exec postgres </del> ''; <del> serviceConfig = </del> <ins> serviceConfig = mkMerge [ </ins> { ExecReload = "${pkgs.coreutils}/bin/kill -HUP $MAINPID"; User = "postgres"; Group = "postgres"; <del> PermissionsStartOnly = true; </del> RuntimeDirectory = "postgresql"; Type = if versionAtLeast cfg.package.version "9.6" then "notify"

Discussion:
Describe the bug A clear and concise description of what the bug is. I have The error I got when starting the service is:
The folder is owned by user postgres:
what are the permissions on ?
it's
it works if I set it to but is created by the build/installation. why doesn't it set the right permission?
Looks line should be a one time required step and you're good to go :+1: Looks like with both and together pushes permissions up to all new parent directories. The module is still using (which is deprecated) so the module should be updated to remove that and fix your issue at the same time. Thanks for reporting!
Thank you for your help!
Change:
buildPythonPackage rec { pname = "catboost"; <del> version = "1.1.1"; </del> <ins> version = "1.0.5"; </ins> disabled = pythonOlder "3.4"; src = fetchFromGitHub { owner = "catboost"; repo = "catboost"; <del> rev = "refs/tags/v${version}"; sha256 = "sha256-bqnUHTTRan/spA5y4LRt/sIUYpP3pxzdN/4wHjzgZVY="; </del> <ins> rev = "v${version}"; sha256 = "ILemeZUBI9jPb9G6F7QX/T1HaVhQ+g6y7YmsT6DFCJk="; </ins> }; nativeBuildInputs = [ clang_12 ];

Discussion:
has a Nix patch that doesn't apply. We can update the patch in the obvious-but-not-enough way with but this produces a failing build. with the above patch. A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. system: host os: multi-user?: sandbox: version: nixpkgs:
Change:
<del> { stdenv, buildPythonPackage, fetchPypi, isPy27, nose, six, colorama, termstyle }: </del> <ins> { stdenv, buildPythonPackage, fetchPypi, isPy27, pythonAtLeast , nose, six, colorama, termstyle }: </ins> buildPythonPackage rec { pname = "rednose";

Discussion:
Describe the bug fails to build. The issue appears to be with failing tests. To Reproduce Steps to reproduce the behavior: results in: Expected behavior The build is successful 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 system: host os: multi-user?: sandbox: version: channels(matt): channels(root): nixpkgs: Maintainer information: