jiebi/CodeConvo huggingface dataset:
Change:
runHook postBuild ''; <ins> postInstall = '' wrapProgram "$out/bin/wtf" --prefix PATH : "${ncurses.dev}/bin" ''; </ins> meta = with lib; { description = "The personal information dashboard for your terminal"; homepage = "https://wtfutil.com/";

Discussion:
Describe the bug wtf uses the tcell module () for terminal manipulation. For many terminals, this Go module has "terminfo" information build in for most frequently used terminals. For non-supported terminals, it calls out to ncurses' tool and parses it's output. This fails when you happen to use such a terminal. To Reproduce Steps to reproduce the behavior: # official termcap entry Expected behavior It should be able to find and start. Additional context Same as fixed by . Metadata Please run and paste the result.
Change:
homepage = "http://subversion.apache.org/"; maintainers = with maintainers; [ eelco lovek323 ]; platforms = platforms.linux ++ platforms.darwin; <ins> inherit knownVulnerabilities; </ins> }; } // stdenv.lib.optionalAttrs stdenv.isDarwin {

Discussion:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc Cc
See also:
This effectively needs a patch for the package in as far as I can see. It would be nice to have a label or something like that :)
Without knowing the internals of the subversion source well, I don't think it's going to be particularly easy to patch. The location to add the nullptr check is easy enough to find, but it's unclear what the right action to take is when the null is detected. The 1.10.x patch in that case calls a function that doesn't exist in 1.9. Without learning more about the subversion internals I'd be afraid of turning a null pointer dereference into something much worse. Or throwing an error that basically just terminates the process anyway, which wouldn't make the situation a whole lot better.
In that case it might make sense to mark it as known vulnerable?
Probably.
This doesn't affect nixos-unstable since has been removed there. Why did you scan a commit from March 19 for nixos-unstable?
Change:
"1.2.2.5" = { hash = "sha256-lU7iK4DWuC/U3s1Ct/rq2Gr3w4F2U7RYYgpmF05bibY="; }; <del> "1.3.1.3" = { hash = "sha256-mNlVnabB2IC3HnYY0mb06RLqQzDxN9ePGVeBy3hkBC8="; </del> <ins> "1.5.0.3" = { hash = "sha256-T96+lPC6OTOkIs/z3QWg73oYVSyidN0SVkBWmT9VRx0="; </ins> }; }; inherit (final) cudaMajorMinorVersion cudaMajorVersion; cutensor = buildCuTensorPackage rec { <del> version = if cudaMajorMinorVersion == "10.1" then "1.2.2.5" else "1.3.1.3"; </del> <ins> version = if cudaMajorMinorVersion == "10.1" then "1.2.2.5" else "1.5.0.3"; </ins> inherit (cuTensorVersions.${version}) hash; # This can go into generic.nix libPath = "lib/${if cudaMajorVersion == "10" then cudaMajorMinorVersion else cudaMajorVersion}";

Discussion:
From what I could tell this was only mentioned in some comment of a closed PR. This is blocking me from wrapping up a flake for Invoke AI (a Stable Diffusion webui). Any help/advice would be appreciated. This was described on Discourse by :
What commit of nixpkgs are you using? I might have some cycles this weekend to spend on this.
Looks like the cause is an outdated version of cutensor. It appears cupy is the only dependent of that so hopefully an upgrade is simple. I am working on a patch now.
Change:
./programs/wayland/hyprlock.nix ./programs/wayland/hyprland.nix ./programs/wayland/labwc.nix <ins> ./programs/wayland/miracle-wm.nix </ins> ./programs/wayland/river.nix ./programs/wayland/sway.nix ./programs/wayland/waybar.nix

Discussion:
Project description A Mir-based Wayland compositor like , but tiling instead of floating. ! More Mir testers, more better. Requesting this from myself so I don't forget about this. Needs a very new Mir, newer than we currently provide (depends on ). Metadata homepage URL: source URL: license: gpl3+ platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
''; postFixup = '' <ins> makeWrapperArgs+=("''${gappsWrapperArgs[@]}") </ins> wrapPythonProgramsIn "$out/share/xfce4/panel/plugins" "$out $pythonPath" ''; meta = with lib; { homepage = "https://github.com/xuzhen/xfce4-dockbarx-plugin"; <del> description = "A plugins to embed DockbarX into xfce4-panel"; </del> <ins> description = "Plugins to embed DockbarX into xfce4-panel"; </ins> license = licenses.mit; platforms = platforms.linux; <del> maintainers = [ maintainers.volth ]; </del> <ins> maintainers = [ maintainers.romildo ]; </ins> }; }

Discussion:
Describe the bug xfce-dockbarx plugin fails to work due to missing library 'gi'; it shows nothing insdide the xfce panel. To Reproduce Steps to reproduce the behavior: xfce installed xfce.xfce4-dockbarx-plugin and dockbarx installed add dockbarx to the panel of XFCE the xfce panel 4-panel to show the error Expected behavior dockbarx shows up on the menu, with no errors in the terminal, with a taskbar in the panel Additional context Terminal output: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(james): nixpkgs: Maintainer information:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
LD_LIBRARY_PATH=$libPath $TBB_IN_STORE/TorBrowser/Tor/tor --version >/dev/null echo "Checking tor-browser wrapper ..." <del> DISPLAY="" MOZ_ENABLE_WAYLAND="" WAYLAND_DISPLAY="" XAUTHORITY=""  XCURSOR_PATH="" XDG_RUNTIME_DIR="" XDG_SESSION_TYPE=""  DBUS_SESSION_BUS_ADDRESS="" TBB_HOME=$(mktemp -d)  </del> <ins> TBB_HOME=$(mktemp -d)  </ins> $out/bin/tor-browser --version >/dev/null '';

Discussion:
On startup, Tor Browser doesn't start if some variables about Wayland aren't set. Steps to reproduce the behavior: and (if set) Tor Browser in a terminal and see the error message. Tor Browser should start. This issue was caused by . currently does not fix the problem. In the meantime, an easy fix would be : <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Notifying peoples from the aforementioned PRs instead. Please run and paste the result.
I can confirm this issue
thanks !
Change:
<del> { stdenv, fetchFromGitHub, autoreconfHook, pkgconfig, libuv, sqlite-replication }: </del> <ins> { stdenv, fetchFromGitHub, autoreconfHook, pkgconfig, file, libco-canonical , libuv, raft-canonical, sqlite-replication }: </ins> with stdenv.lib; stdenv.mkDerivation rec { pname = "dqlite"; <del> version = "0.2.6"; </del> <ins> version = "1.0.0"; </ins> src = fetchFromGitHub { <del> owner = "CanonicalLtd"; </del> <ins> owner = "canonical"; </ins> repo = pname; rev = "v${version}"; <del> sha256 = "13l7na5858v2ah1vim6lafmzajgkymfi5rd6bk14cm4vcnxc40wb"; </del> <ins> sha256 = "0670c1c84lcf5vl3h6mlff00fz2fnm766bzlk526sjjzysx3zjya"; </ins> }; <del> nativeBuildInputs = [ autoreconfHook pkgconfig ]; </del> <ins> nativeBuildInputs = [ autoreconfHook file pkgconfig ]; buildInputs = [ libco-canonical.dev libuv raft-canonical.dev sqlite-replication ]; </ins> <del> buildInputs = [ libuv sqlite-replication ]; </del> <ins> preConfigure= '' substituteInPlace configure --replace /usr/bin/ " " ''; doCheck = true; outputs = [ "dev" "out" ]; </ins> meta = { <del> description = "Expose a SQLite database over the network and replicate it across a cluster of peers"; </del> <ins> description = '' Expose a SQLite database over the network and replicate it across a cluster of peers ''; </ins> homepage = https://github.com/CanonicalLtd/dqlite/; license = licenses.asl20; maintainers = with maintainers; [ joko ];

Discussion:
Describe the bug I'm not able to start any (freshly created) container in lxd. To Reproduce Steps to reproduce the behavior: Expected behavior Container starts without issues. Additional context Log gathered via Regarding the not enough space, I'm quiet sure that the report is wrong: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(wucke13): nixpkgs: Maintainer information:
Maybe updating helps? I started working on a PR, though I depend on a which fails to build.
tested with merged on top inside a nogui VM
Wrong commit?
yip
Change:
glew = glew110; }; <del> bitcoinarmory = callPackage ../applications/misc/bitcoinarmory { pythonPackages = python2Packages; }; </del> bitkeeper = callPackage ../applications/version-management/bitkeeper { gperf = gperf_3_0; };

Discussion:
After installing , this happens: from — . . System: 17.03.1844. (Gorilla) Nix version: nix-env (Nix) 1.11.14 Nixpkgs version: "17.03.1844." Sandboxing enabled: build-use-sandbox = true
Also, upstream made 2 releases since, one with a critical vuln.
I'm getting the same on 0.96.3, but will look some more. What specifically is the vulnerability, out of curiosity?
The upstream build process in still quite messy, with embedded libraries concretely integrated into build files. I've got a modified nix expression that replaces some of the deps with libs in the store, but with both variants I still get either a SegFault in ArmoryDB or a SIGILL in I don't know if I can invest much more time in fixing this. I suspect the issues originate upstream, FWIW. Personally, I'm running a gcrooted-closure that I've kept unchanged for some months now.
I’m not sure, 0.96.3 works fine with from your original commit, i.e. . The vulnerability was related to fragmented backups. Well, I guess I’ll just stay with Bitcoin Core. I just wanted to try this one. ¯()/¯
Oh, interesting. This isn't the first time I've seen a newer glibc cause segfaults and other nastiness, but I lack the skill to fix these types of problems efficiently. Armory's great for the offline wallet stuff, but the original devs left the source tree in a poor state. I'll eventually get it working on the master branch again, probably.
I don’t get that, really. Is everything compiled from source in this derivation? Does upstream include binary blobs in the repo? :
Both that SIGSEGV at the very beginning, and failure, and SIGILL would suggest a linking error to me. You shouldn’t need to use on programs cleanly built from source. Hmm.
Even less so, to remove a reference? What is this upstream build script doing? :grin: sighs
It's building the lib deps from source. fcgi is a git-submodule and the rest are checked into the repo.

I've already begun to try to excise them during the patch phase: This still yields the same problems, however, along with some new ones (fcgi version mismatch, i think), but it's on the path to getting a cleanly linked binary. I welcome any amendments to get this working reliably and linked properly.
Let me try that, but that upstream repo is a total mess.
:arrow_up: fixed above.
Change:
customMemoryManagement = false; }).overrideAttrs (args: { # only a stripped down version is build which takes a lot less resources to build <del> requiredSystemFeatures = null; </del> <ins> requiredSystemFeatures = [ ]; </ins> });

Discussion:
When someone wants to set on their system configuration the evaluation fails with the following error. Steps to reproduce the behavior: any system config (or any other arch) the aboves error Everything builds just fine. My fantastic bisect skills (be aware of the sarcasm) nailed it down to . The PR sets which breaks the evaluation. Possibly a is another solution here and that seems to fix eval for me (but i am not purposing the change as i am absolut unaware of side-effects), or the mkDerivation code needs to be changed to support in case someone sets (as you are the author of the PR that possibly broke the eval) beside that i sadly dont know whom to ping. Please run and paste the result.
My pr didn't add the requiredSystemFeatures line so it must have been broken since
Ah sorry you are right, i had multiple PRs open and I must have picked the wrong one. :(
Change:
<del> Date: 2017-09-02 13:03:15.353403096 +0200 From: Jan Engelhardt <jengelh@inai.de> Stop redefining libc definitions that cause build failures under glibc-2.26. [   46s] In file included from /usr/include/sys/types.h:156:0, [   46s]                  from /usr/include/stdlib.h:279, [   46s]                  from malloc.c:15: [   46s] /usr/include/bits/stdint-intn.h:27:19: error: conflicting types for 'int64_t' [   46s]  typedef __int64_t int64_t; [   46s]                    ^~~~~~~ [   46s] In file included from ../include/aal/libaal.h:17:0, [   46s]                  from malloc.c:6: [   46s] ../include/aal/types.h:35:33: note: previous declaration of 'int64_t' was here [   46s]  typedef long long int           int64_t; --- include/aal/types.h |   48 ++---------------------------------------------- 1 file changed, 2 insertions(+), 46 deletions(-) Index: libaal-1.0.6/include/aal/types.h =================================================================== --- libaal-1.0.6.orig/include/aal/types.h +++ libaal-1.0.6/include/aal/types.h @@ -26,24 +26,7 @@ #undef ESTRUCT #define ESTRUCT                 50 -#ifndef __int8_t_defined -#define __int8_t_defined -typedef signed char             int8_t; -typedef short int               int16_t; -typedef int                     int32_t; -__extension__ -typedef long long int           int64_t; -#endif - -typedef unsigned char           uint8_t; -typedef unsigned short int      uint16_t; -#ifndef __uint32_t_defined -#define __uint32_t_defined -typedef unsigned int            uint32_t; -__extension__ -typedef unsigned long long int  uint64_t; -#endif - +#include <stdint.h> #define MAX_UINT8  ((uint8_t)~0) #define MAX_UINT16 ((uint16_t)~0) #define MAX_UINT32 ((uint32_t)~0) @@ -53,36 +36,9 @@ typedef unsigned long long int  uint64_t because we don't want use gcc builtins in minimal mode for achive as small binary size as possible. */ -#ifndef ENABLE_MINIMAL #  include <stdarg.h> -#else -#ifndef _VA_LIST_ -#define _VA_LIST_ -typedef char *va_list; -#endif -#undef va_arg -#undef va_end -#undef va_start - -#define va_end(ap)        -        do {} while(0); - -#define va_start(ap, p)   -        (ap = (char *)(&(p)+1)) - -#define va_arg(ap, type)  -        ((type *)(ap += sizeof(type)))[-1] -#endif - -/* As libaal may be used without any standard headers, we need to declare NULL -   macro here in order to avoid compilation errors. */ -#undef NULL -#if defined(__cplusplus) -#  define NULL 0 -#else -#  define NULL ((void *)0) -#endif +#include <stdio.h> /* Simple type for direction denoting */ enum aal_dir { </del>

Discussion:
Package name: libaal Latest released version: 1.0.7 released in 2017 <!-- Search your package here: --- Current version on the unstable channel: 1.0.6 Current version on the stable/release channel: 1.0.6 Notify maintainers Please backport the changes into stable, its used for out of tree reiser4fs. Thank you! <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
Change:
}; <del> config = mkIf cfg.enable { inherit warnings; </del> <ins> config = lib.mkIf cfg.enable { </ins> system.requiredKernelConfig = with config.lib.kernelConfig; [ (isModule "ZRAM")

Discussion:
Project description In the author says, In 2020 the zram-generator doesn't seem to have had any releases. In the meantime, it's gone from initial release version 0.2.0 up to the somewhat-mature version 1.1.2. It's probably a good time to port this to zram-generator. Metadata homepage URL: source URL: license: mit platforms: linux
Change:
owner = "influxdata"; repo = "flux"; rev = "v${libflux_version}"; <del> hash = "sha256-4Z6Vfdyh0zimQlE47plSIjTWBYiju0Qu09M+MgMQOL4="; </del> <ins> hash = "sha256-XHT/+JMu5q1cPjZT2x/OKEPgxFJcnjrQKqn8w9/Mb3s="; </ins> }; patches = [ <del> # https://github.com/influxdata/flux/pull/5440 # fix compile error with Rust 1.72.0 </del> <ins> # Fix build on Rust 1.78 (included after v0.195.0) </ins> (fetchpatch { <del> url = "https://github.com/influxdata/flux/commit/8d1d6c8b485eb7e15b6a5f57762d1f766b17defd.patch"; </del> <ins> name = "fix-build-on-rust-1.78.patch"; url = "https://github.com/influxdata/flux/commit/68c831c40b396f0274f6a9f97d77707c39970b02.patch"; </ins> stripLen = 2; extraPrefix = ""; <del> hash = "sha256-BDBmGKsC2RWMyObDm7dPwFq/3cVIdBKF8ZVaCL+uftw="; includes = [ "flux/src/lib.rs" ]; </del> <ins> excludes = [ ]; hash = "sha256-6LOTgbOCfETNTmshyXgtDZf9y4t/2iqRuVPkz9dYPHc="; </ins> }) <ins> ../influxdb2/fix-unsigned-char.patch </ins> ]; sourceRoot = "${src.name}/libflux"; <del> cargoHash = "sha256-925U9weBOvMuyApsTOjtQxik3nqT2UpK+DPM64opc7c="; </del> <ins> cargoHash = "sha256-O+t4f4P5291BuyARH6Xf3LejMFEQEBv+qKtyjHRhclA="; </ins> nativeBuildInputs = [ rustPlatform.bindgenHook ]; buildInputs = lib.optional stdenv.isDarwin libiconv; pkgcfg = ''

Discussion:
Steps to reproduce the behavior: There appears to be a cache miss, because starts to be compiled, but it fails. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
the maintainers to tag would be for v2 and and for v1 (all share the same build failure). v2 will be addressed via
Apologies. Thank you.
Change:
buildPythonPackage rec { pname = "sphinxcontrib-spelling"; <del> version = "2.2.0"; </del> <ins> version = "4.2.0"; </ins> src = fetchPypi { inherit pname version; <del> sha256 = "1f0fymrk4kvhqs0vj9gay4lhacxkfrlrpj4gvg0p4wjdczplxd3z"; </del> <ins> sha256 = "44a9445b237ade895ae1fccbe6f41422489b1ffb2a026c1b78b0c1c1c229f9bf"; </ins> }; propagatedBuildInputs = [ sphinx pyenchant pbr ];

Discussion:
Ran . For some reason there are pylint tests running for ~8 minutes that eventually end up in a failure. <details<summaryPyLint test failures</summary</detailson pylint (indirectly?); running for ~10 minutes as part of package installation process.
This will need to be backported to 18.09 as the latest version released by Hydra is broken too
The tests still fails even after the above patch applied. <details<summaryHere is the log</summary</detailsHere is the patch I used: Edit: the original patch is working on the python-unstable branch so I guess it's OK
I pushed a fix to the branch: . The fix for is currently in the branch: .
Change:
cairomm = callPackage ../development/libraries/cairomm { }; <del> pango = callPackage ../development/libraries/pango { }; </del> <ins> pango = callPackage ../development/libraries/pango { harfbuzz = harfbuzz.override { withCoreText = stdenv.isDarwin; }; }; </ins> pangolin = callPackage ../development/libraries/pangolin { inherit (darwin.apple_sdk.frameworks) Carbon Cocoa;

Discussion:
Describe the bug Pango now requires harfbuzz to build built with coretext, which is fine because we have harfbuzzFull. However, pango's include path for it is just when it should be I'm not sure how to tell meson to use a different include path :/ To Reproduce on darwin: Expected behavior builds Maintainer information:
..... nice, not sure why i didn't think of that :(
Change:
celery channels channels-redis <ins> codespell </ins> colorama dacite <del> daphne </del> deepmerge defusedxml django

Discussion:
When the upload functionallity is enabled (when is a mountpoint), the library is unconditionally imported even when no s3 storage is used. This library is missing from the dependencies: Uploading a file generates an event with the following error: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
{ stdenv, fetchurl, ncurses, openssl, aspell, gnutls , zlib, curl , pkgconfig, libgcrypt <del> , cmake, makeWrapper, libobjc, libiconv </del> <ins> , cmake, makeWrapper, libobjc, libresolv, libiconv </ins> , asciidoctor # manpages , guileSupport ? true, guile , luaSupport ? true, lua5

Discussion:
WeeChat fails to build on OS X with the below error System: macOS Sierra Nix version: 1.11.4 Nixpkgs version: 17.03pre93141.
I've see the missing symbol thing before, but haven't had a chance to track down where it should be and why it isn't there. If anyone wants to poke around and answer those questions, I'd appreciate it!
I didn't know how to read the message, I was searching for . Searching for I think it comes from on Darwin searching around. I can see listed in , and . Only just started using nixpkgs so not sure how to pull it in to the Weechat derivation and test etc.
Got it building. Here's the changes . I'll raise a PR at the weekend after I've read
^ This change works for me!
once you submit the PR, I think we can simultaneously close this and and .
Change:
<ins> module github.com/nwg-piotr/nwg-look go 1.20 require ( github.com/gotk3/gotk3 v0.6.2 github.com/sirupsen/logrus v1.9.3 ) require golang.org/x/sys v0.6.0 // indirect </ins>

Discussion:
Project description A GTK3 settings editor adapted to work in the wlroots environment, a part of the nwg-shell project. <!-- Describe the project a little: --Metadata homepage URL: https://nwg- source URL: license: MIT platforms: Linux
I am happy to work on this and I am currently working a pr to implement it!
Change:
<ins> { lib , bash , fetchFromGitHub , installShellFiles , coreutils , gawk , gnugrep , gnused , openssh , resholve , rsync , which , zfs }: resholve.mkDerivation rec { pname = "zxfer"; version = "1.1.7"; src = fetchFromGitHub { owner = "allanjude"; repo = pname; rev = "v${version}"; hash = "sha256-11SQJcD3GqPYBIgaycyKkc62/diVKPuuj2Or97j+NZY="; }; nativeBuildInputs = [ installShellFiles ]; # these may point to paths on remote systems, calculated at runtime, thus we cannot fix them # we can only set their initial values, and let them remain dynamic postPatch = '' substituteInPlace zxfer  --replace 'LCAT=""'                'LCAT=${coreutils}/bin/cat'  --replace 'LZFS=$( which zfs )'    'LZFS=${zfs}/bin/zfs' ''; installPhase = '' runHook preInstall installManPage zxfer.1m zxfer.8 install -Dm755 zxfer -t $out/bin/ runHook postInstall ''; solutions.default = { scripts = [ "bin/zxfer" ]; interpreter = "${bash}/bin/sh"; inputs = [ coreutils gawk gnugrep gnused openssh rsync which ]; fake.external = [ "kldload" # bsd builtin "kldstat" # bsd builtin "svcadm" # solaris builtin ]; keep = { "$LCAT" = true; "$LZFS" = true; "$PROGRESS_DIALOG" = true; "$RZFS" = true; "$input_optionts" = true; "$option_O" = true; "$option_T" = true; }; fix = { "$AWK" = [ "awk" ]; "$RSYNC" = [ "rsync" ]; }; execer = [ "cannot:${rsync}/bin/rsync" ]; }; meta = with lib; { description = "A popular script for managing ZFS snapshot replication"; homepage = "https://github.com/allanjude/zxfer"; changelog = "https://github.com/allanjude/zxfer/releases/tag/v${version}"; license = licenses.bsd2; maintainers = with lib.maintainers; [ urandom ]; }; } </ins>

Discussion:
Project description A popular script in BSD-land for managing ZFS snapshot replication. It allows the easy and reliable backup, restore or transfer of ZFS filesystems, either locally or remotely. Metadata homepage URL: source URL: license: bsd-2clause platforms: unix Package example FreeBSD ports: AUR:
??
Change:
./programs/dublin-traceroute.nix ./programs/ecryptfs.nix ./programs/environment.nix <ins> ./programs/envision.nix </ins> ./programs/evince.nix ./programs/extra-container.nix ./programs/fcast-receiver.nix

Discussion:
Project description UI for building, configuring and running Monado, the open source OpenXR runtime. Metadata homepage URL: source URL: license: agpl3 platforms: unix, linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
To my information, software without a stable release isnt accepted yet.
Not even in unstable? Fair enough, I guess.
unstable automatically becomes stable, so yes :) I think once a release is done (even 0.x), it can be packaged, but don't take my word as the ultimate truth, please :sweat_smile:
This appears to be incorrect. was merged targeting a specific commit (despite actually having stable releases).
This is indeed incorrect; there are even specific rules for the attribute of unreleased versions.