jiebi/CodeConvo huggingface dataset:
Change:
Project description <!-- Describe the project a little: --A dynamic output configuration tool for wlroots that automatically detects and configures connected outputs based on a set of profiles. Metadata homepage URL: source URL: license: mit platforms: linux
I already got the package made in my config, will see about sending a pr tomorrow
Sorry, I didn't notice your post and submitted a PR. Could you please check it? Also, would you like to become a maintainer?
No worries, I will get around checking it today. Yeah I would not mind doing so, it was partially why I took a stab at writing a pkg config in the first place.
just to update, everything works. Did not know whether to post here or on the PR. Also since the PR is already posted and it works, is there anything extra on my end that you would like me to do about maintaining it?
Sorry, I'm late. Thanks for your confirmation. Since it seems difficult to edit this branch with you, could you please add yourself to the maintainer-list in another PR? Once it is merged, I will add you to the maintainers.
Done will be waiting for the merge.

Discussion:
<ins> { lib , rustPlatform , fetchFromGitLab , installShellFiles , pandoc }: rustPlatform.buildRustPackage rec { pname = "shikane"; version = "0.2.0"; src = fetchFromGitLab { owner = "w0lff"; repo = "shikane"; rev = "v${version}"; hash = "sha256-S55elFZQT234fKlISFi21QJtnf2yB0O2u2vSNFhzgBg="; }; cargoHash = "sha256-4wisXVaZa2GBFKywl48beQgg4c+lawL3L/837ZU1Y94="; nativeBuildInputs = [ installShellFiles pandoc ]; postBuild = '' bash ./scripts/build-docs.sh man ''; postInstall = '' installManPage ./build/shikane.* ''; # upstream has no tests doCheck = false; meta = with lib; { description = "A dynamic output configuration tool that automatically detects and configures connected outputs based on a set of profiles"; homepage = "https://gitlab.com/w0lff/shikane"; changelog = "https://gitlab.com/w0lff/shikane/-/tags/v${version}"; license = licenses.mit; maintainers = with maintainers; [ michaelpachec0 natsukium ]; platforms = platforms.linux; }; } </ins>

oguri = callPackage  ../tools/wayland/oguri { }; <ins> shikane = callPackage ../tools/wayland/shikane { }; </ins> shotman = callPackage ../tools/wayland/shotman { }; slurp = callPackage ../tools/wayland/slurp { };
Change:
was recently updated to use LLVM 4.0, which is rather good news for my use cases. Can we update our version to use this? It also seems they now so perhaps we should switch to using that as well? (maintainer)--LMK your thoughts and if you want to tackle it or want me to (I'd probably get to it this weekend). Thanks!
I'm pretty busy these days but if you're interested in updating it feel free :+1:
Sure thing! Although actually we'll need to actually add LLVM 4.0 first, forgot that wasn't in-tree yet :innocent:. Maybe I'll give that a go as well :+1: (cc )

Discussion:
<ins> --- souper-1be75fe6a96993b57dcba038798fe6d1c7d113eb-src/CMakeLists.txt.orig     2017-01-20 13:55:14.783632588 -0600 +++ souper-1be75fe6a96993b57dcba038798fe6d1c7d113eb-src/CMakeLists.txt  2017-01-20 13:55:20.505728456 -0600 @@ -33,7 +33,10 @@ OUTPUT_VARIABLE LLVM_SYSTEM_LIBS OUTPUT_STRIP_TRAILING_WHITESPACE ) -set(LLVM_LIBS "${LLVM_LIBS} ${LLVM_SYSTEM_LIBS}") + +if (LLVM_SYSTEM_LIBS) +  set(LLVM_LIBS "${LLVM_LIBS} ${LLVM_SYSTEM_LIBS}") +endif() execute_process( COMMAND ${LLVM_CONFIG_EXECUTABLE} --ldflags </ins>

{ stdenv, fetchFromGitHub, cmake, makeWrapper <del> , llvmPackages_39, hiredis, z3_opt, gtest </del> <ins> , llvmPackages_4, hiredis, z3_opt, gtest </ins> }: let klee = fetchFromGitHub { <del> owner = "klee"; </del> <ins> owner = "rsas"; </ins> repo  = "klee"; <del> rev   = "a743d7072d9ccf11f96e3df45f25ad07da6ad9d6"; sha256 = "0qwzs029vlba8xz362n4b00hdm2z3lzhzmvix1r8kpbfrvs8vv91"; </del> <ins> rev   = "57cd3d43056b029d9da3c6b3c666c4153554c04f"; sha256 = "197wb7nbirlfpx2jr3afpjjhcj7slc4dxxi02j3kmazz9kcqaygz"; </ins> }; in stdenv.mkDerivation { <del> name = "souper-unstable-2017-01-05"; </del> <ins> name = "souper-unstable-2017-03-07"; </ins> src = fetchFromGitHub { owner  = "google"; repo   = "souper"; <del> rev    = "1be75fe6a96993b57dcba038798fe6d1c7d113eb"; sha256 = "0r8mjb88lwz9a3syx7gwsxlwfg0krffaml04ggaf3ad0cza2mvm8"; </del> <ins> rev    = "5faed54ddc4a0e0e12647a0eac1da455a1067a47"; sha256 = "1v8ml94ryw5wdls9syvicx4sc9l34yaq8r7cf7is6x7y1q677rps"; </ins> }; nativeBuildInputs = [

]; buildInputs = [ <del> llvmPackages_39.llvm llvmPackages_39.clang-unwrapped </del> <ins> llvmPackages_4.llvm llvmPackages_4.clang-unwrapped </ins> hiredis gtest ]; <ins> patches = [ ./cmake-fix.patch ]; </ins> enableParallelBuilding = true; preConfigure = ''
Change:
Steps to reproduce the behavior: Notable part: @ lines 43..48: Looks like a cmake incompatibility?? possibly connected to ? <!-- 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. system: host os: multi-user?: sandbox: version: channels(root): channels(anna): nixpkgs:
Can you try building it manually against the latest nixpkgs-unstable revision using ?
This is really weird. Looks like something went and replace the first occurrence of in the source files with in . This is how it's supposed to look:
This was already built against the latest at the time, around an hour ago. My system flake registry pins to it. I get the same result with .
this looks completely normal. what is going on?
I have done a bisection and it appears that the first bad commit was
After bisecting Meson, this bug was introduced by and is still present in master.
Yes, I am writing a fix right now
has been merged, but do you think you could make a PR to master to have prismlauncher use its own overriden meson and another PR to staging to undo that change, so that way prismlauncher is at least fixed in the master branch sooner than a few weeks from now and when staging hits master, it won't have that temp fix anymore? Thank you again!
Note that the package that's actually broken here is . But yes using a fixed version of Meson for this sounds like a good idea.

Discussion:
version = "14.11.5"; src = fetchurl { <del> url = "http://www.schedmd.com/download/latest/slurm-${version}.tar.bz2"; </del> <ins> url = "http://www.schedmd.com/download/archive/slurm-${version}.tar.bz2"; </ins> sha256 = "0xx1q9ximsyyipl0xbj8r7ajsz4xrxik8xmhcb1z9nv0aza1rff2"; };
Change:
Steps to reproduce the behavior: Notable part: @ lines 43..48: Looks like a cmake incompatibility?? possibly connected to ? <!-- 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. system: host os: multi-user?: sandbox: version: channels(root): channels(anna): nixpkgs:
Can you try building it manually against the latest nixpkgs-unstable revision using ?
This is really weird. Looks like something went and replace the first occurrence of in the source files with in . This is how it's supposed to look:
This was already built against the latest at the time, around an hour ago. My system flake registry pins to it. I get the same result with .
this looks completely normal. what is going on?
I have done a bisection and it appears that the first bad commit was
After bisecting Meson, this bug was introduced by and is still present in master.
Yes, I am writing a fix right now
has been merged, but do you think you could make a PR to master to have prismlauncher use its own overriden meson and another PR to staging to undo that change, so that way prismlauncher is at least fixed in the master branch sooner than a few weeks from now and when staging hits master, it won't have that temp fix anymore? Thank you again!
Note that the package that's actually broken here is . But yes using a fixed version of Meson for this sounds like a good idea.

Discussion:
"docs/yaml/objects/dep.yaml" ]; }) <ins> # Fix regression in precomputing CMAKE_SIZEOF_VOID_P # See https://github.com/mesonbuild/meson/pull/11761 (fetchpatch { url = "https://github.com/mesonbuild/meson/commit/7c78c2b5a0314078bdabb998ead56925dc8b0fc0.patch"; sha256 = "sha256-vSnHhuOIXf/1X+bUkUmGND5b30ES0O8EDArwb4p2/w4="; }) </ins> ]; setupHook = ./setup-hook.sh;
Change:
Steps to reproduce the behavior: Notable part: @ lines 43..48: Looks like a cmake incompatibility?? possibly connected to ? <!-- 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. system: host os: multi-user?: sandbox: version: channels(root): channels(anna): nixpkgs:
Can you try building it manually against the latest nixpkgs-unstable revision using ?
This is really weird. Looks like something went and replace the first occurrence of in the source files with in . This is how it's supposed to look:
This was already built against the latest at the time, around an hour ago. My system flake registry pins to it. I get the same result with .
this looks completely normal. what is going on?
I have done a bisection and it appears that the first bad commit was
After bisecting Meson, this bug was introduced by and is still present in master.
Yes, I am writing a fix right now
has been merged, but do you think you could make a PR to master to have prismlauncher use its own overriden meson and another PR to staging to undo that change, so that way prismlauncher is at least fixed in the master branch sooner than a few weeks from now and when staging hits master, it won't have that temp fix anymore? Thank you again!
Note that the package that's actually broken here is . But yes using a fixed version of Meson for this sounds like a good idea.

Discussion:
{ lib , stdenv <del> , meson </del> <ins> , buildPackages </ins> , cmake , ninja , fetchFromGitHub <ins> , fetchpatch </ins> }: <ins> # Fix regression in precomputing CMAKE_SIZEOF_VOID_P # See https://github.com/mesonbuild/meson/pull/11761 let fixedMeson = buildPackages.meson.overrideAttrs ( {patches ? [], ...}: { patches = patches ++ [ (fetchpatch { url = "https://github.com/mesonbuild/meson/commit/7c78c2b5a0314078bdabb998ead56925dc8b0fc0.patch"; sha256 = "sha256-vSnHhuOIXf/1X+bUkUmGND5b30ES0O8EDArwb4p2/w4="; }) ]; } ); in </ins> stdenv.mkDerivation rec { pname = "tomlplusplus"; version = "3.3.0";

hash = "sha256-INX8TOEumz4B5coSxhiV7opc3rYJuQXT2k1BJ3Aje1M="; }; <del> nativeBuildInputs = [ meson cmake ninja ]; </del> <ins> nativeBuildInputs = [ fixedMeson cmake ninja ]; </ins> meta = with lib;{ homepage = "https://github.com/marzer/tomlplusplus";
Change:
Building the manpages for this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: (please share the relevant fragment of the diffoscope output here, and any additional analysis you may have done)

Discussion:
"-Ddocs-build=true" ]; <ins> preConfigure = '' export KBUILD_BUILD_TIMESTAMP="$(date -u -d @$SOURCE_DATE_EPOCH)" ''; </ins> doCheck = true; meta = with lib; {
Change:
none Please run and paste the result.
I started to bisect this with at nix started to download ~4GB of derivations and I aborted the process. The is
it seems like the issue already got fixed upstream in but there is no new release yet. We either have to target commit which contains the fix, or wait for the new release.
you are right, pdfpc/pdfpc fixes this. I tried it with this patch on nixpkgs:

Discussion:
{ lib, stdenv, fetchFromGitHub, cmake, pkg-config, vala, gtk3, libgee , poppler, libpthreadstubs, gstreamer, gst-plugins-base, gst-plugins-good, gst-libav, gobject-introspection, wrapGAppsHook <del> , qrencode, webkitgtk, discount, json-glib }: </del> <ins> , qrencode, webkitgtk, discount, json-glib, fetchpatch }: </ins> stdenv.mkDerivation rec { pname = "pdfpc";

json-glib ]; <ins> patches = [ # needed for compiling pdfpc 4.6.0 with vala 0.56.7, see # https://github.com/pdfpc/pdfpc/issues/686 # https://github.com/pdfpc/pdfpc/pull/687 (fetchpatch { url = "https://github.com/pdfpc/pdfpc/commit/d38edfac63bec54173b4b31eae5c7fb46cd8f714.diff"; hash = "sha256-KC2oyzcwU2fUmxaed8qAsKcePwR5KcXgpVdstJg8KmU="; }) ]; </ins> cmakeFlags = lib.optional stdenv.isDarwin "-DMOVIES=OFF"; meta = with lib; {
Change:
The simply doesn't work for me. The problem seems to be in binary not being able to find Clipboard's own libraries. When running in debug mode some useful information comes out: However, those libraries are physically present: I also tried to modify to point to the lib directory, that didn't help either. to do literally anything with , like copy and paste something. Notifying as they are a maintainer. clipboard-jh version: 0.6.0, . Xorg, KDE Plasma
From the debug logs it seems like it should fail on Wayland as well - however it works fine on my Wayland machine. I will take a proper look later.
I'm not proficient at compiling and building software at all, but maybe what I paste below will make sense. So, it seems like the required libraries are missing from runtime path of ? And here's another interesting line which I found in nix logs (during the install phase): The rhs path seems broken to me. Maybe I should add the full log?
<details<summaryAnd here is the full log</summary</details
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
For me, adding the following to the derivation fixes the issue: Now when I think about it: maybe this problem occurs only with the target. I thought there were an issue with (the one in the package) but it's completely unrelated to this problem. If no one actually wants to run , there's no issue at all, at least that's my guess.
adding the solution you provided in your comment seems to fix the issue where is unable to copy/paste content to system clipboard. Might want to submit that change to the nix-package.
oh, cool, it wasn't just me being silly, someone else has this issue as well. Now, I need to figure out how to contribute to nixpkgs...
I think is the original package maintainer for this one
you don't need to be the maintainer to update the package btw. We all have the ability to submit a change and have it reviewed!
steps to submit the PR: nixpkgs necessary changes without changing formating of the current package (for diff) commit with the following message template: changes to your fork. PR to nixpkgs with description of changes.

Discussion:
, cmake , libffi , pkg-config <ins> , patchelf </ins> , wayland-protocols , wayland , xorg

"-DINSTALL_PREFIX=${placeholder "out"}" ]; <ins> postFixup = lib.optionalString stdenv.isLinux '' patchelf $out/bin/cb --add-rpath $out/lib ''; </ins> meta = with lib; { description = "Cut, copy, and paste anything, anywhere, all from the terminal"; homepage = "https://github.com/Slackadays/clipboard";
Change:
Python package betterproto is missing setuptools as a run time dependency This is my fixing the issue Give me some feedback if this is not properly reported, I'm a newbie when it comes to reporting issues
see

Discussion:
, jinja2 , isort , python <ins> , pydantic </ins> , pytestCheckHook , pytest-asyncio , pytest-mock

buildPythonPackage rec { pname = "betterproto"; <del> version = "2.0.0b5"; </del> <ins> version = "2.0.0b6"; </ins> format = "pyproject"; disabled = pythonOlder "3.7"; src = fetchFromGitHub { owner = "danielgtaylor"; repo = "python-betterproto"; <del> rev = "v${version}"; hash = "sha256-XyXdpo3Yo4aO1favMWC7i9utz4fNDbKbsnYXJW0b7Gc="; </del> <ins> rev = "v.${version}"; hash = "sha256-ZuVq4WERXsRFUPNNTNp/eisWX1MyI7UtwqEI8X93wYI="; </ins> }; nativeBuildInputs = [ poetry-core ];

pythonImportsCheck = [ "betterproto" ]; nativeCheckInputs = [ <ins> pydantic </ins> pytestCheckHook pytest-asyncio pytest-mock

# the protoc-gen-python_betterproto script from the package to be on PATH. preCheck = '' export PATH=$PATH:$out/bin <ins> patchShebangs src/betterproto/plugin/main.py </ins> ${python.interpreter} -m tests.generate '';
Change:
Trying to execute the binary from the derivation gives the following error message: Setting DISABLEQT5COMPAT=1 yields the same error message, without the first couple of lines about Qt5. Steps to reproduce the behavior: nixos-unstable, or nixpkgs-master Anki would start normally I'm currently running nixos-unstable, and using KDE as my desktop environment. Please run and paste the result.
Just noticed that the derivation has been updated and seems to work, so I can switch to that in the meantime
I'll check it out as soon as I have time. They seem to be using a new version of Qt now.
This should be now superseded by

Discussion:
name = null; # Appimage sets it to "appimage-env" # Dependencies of anki <del> targetPkgs = pkgs: (with pkgs; [ xorg.libxkbfile krb5 ]); </del> <ins> targetPkgs = pkgs: (with pkgs; [ xorg.libxkbfile xcb-util-cursor-HEAD krb5 ]); </ins> runScript = writeShellScript "anki-wrapper.sh" '' exec ${unpacked}/bin/anki ${ lib.strings.escapeShellArgs commandLineArgs }
Change:
Package name: textual Latest released version: 0.23.0 <!-- Search your package here: --- Current version on the unstable channel: 0.15.1 Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
Does resolve this?
As far as I can tell: yes. Would be great to have it merged into master (so it shows up in nixpkgs-unstable at some point).
And of course there have been two new releases in the meantime....
Was fixed, closing.

Discussion:
, pygments , typing-extensions , pytestCheckHook <ins> , setuptools </ins> # for passthru.tests , enrich

buildPythonPackage rec { pname = "rich"; <del> version = "13.3.1"; </del> <ins> version = "13.3.5"; </ins> format = "pyproject"; disabled = pythonOlder "3.7";

owner = "Textualize"; repo = pname; rev = "refs/tags/v${version}"; <del> hash = "sha256-1soeb3aD4wB4stILvfOga/YZtyH6jd0XvnxkLmbW4G0="; </del> <ins> hash = "sha256-PnyO5u0gxfYKT6xr0k3H0lbLl9wKPl6oxR1mM9A0Hys="; </ins> }; <del> nativeBuildInputs = [ poetry-core ]; </del> <ins> nativeBuildInputs = [ poetry-core ]; </ins> propagatedBuildInputs = [ markdown-it-py pygments <ins> setuptools </ins> ] ++ lib.optionals (pythonOlder "3.9") [ typing-extensions ];

buildPythonPackage rec { pname = "textual"; <del> version = "0.15.1"; </del> <ins> version = "0.23.0"; </ins> format = "pyproject"; disabled = pythonOlder "3.7";

owner = "Textualize"; repo = pname; rev = "refs/tags/v${version}"; <del> hash = "sha256-UT+ApD/TTb5cxIdgK+n3B2J3z/nEwVXtuyPHpGCv6Tg="; </del> <ins> hash = "sha256-XgJ43yyiwzSH22NzidJ7z+Qh6+pOuAdfL7ZxabJkd3U="; </ins> }; nativeBuildInputs = [ poetry-core ]; <del> postPatch = '' substituteInPlace pyproject.toml  --replace 'importlib-metadata = "^4.11.3"' 'importlib-metadata = "*"' ''; </del> propagatedBuildInputs = [ rich markdown-it-py

meta = with lib; { description = "TUI framework for Python inspired by modern web development"; homepage = "https://github.com/Textualize/textual"; <ins> changelog = "https://github.com/Textualize/textual/releases/tag/v${version}"; </ins> license = licenses.mit; maintainers = with maintainers; [ joelkoen ]; };
Change:
Project description <!-- Describe the project a little: --Frogmouth is a Markdown viewer / browser for your terminal, built with . Metadata homepage URL: source URL: license: MIT platforms: Linux, Python
Likely depends on

Discussion:
"textual" ]; <ins> __darwinAllowLocalNetworking = true; </ins> meta = with lib; { description = "TUI framework for Python inspired by modern web development"; homepage = "https://github.com/Textualize/textual";

<ins> { lib , python3 , fetchFromGitHub }: python3.pkgs.buildPythonApplication rec { pname = "frogmouth"; version = "0.5.0"; format = "pyproject"; src = fetchFromGitHub { owner = "Textualize"; repo = "frogmouth"; rev = "v${version}"; hash = "sha256-5MNQ78zwjtenHDjy2g1rjiq4HvFie7uUSlMwZu6RmXg="; }; nativeBuildInputs = [ python3.pkgs.poetry-core python3.pkgs.pythonRelaxDepsHook ]; propagatedBuildInputs = with python3.pkgs; [ httpx textual typing-extensions xdg ]; pythonRelaxDeps = [ "xdg" ]; pythonImportsCheck = [ "frogmouth" ]; meta = with lib; { description = "A Markdown browser for your terminal"; homepage = "https://github.com/Textualize/frogmouth"; changelog = "https://github.com/Textualize/frogmouth/blob/${src.rev}/ChangeLog.md"; license = licenses.mit; maintainers = with maintainers; [ figsoda ]; }; } </ins>

frei = callPackage ../tools/misc/frei { }; <ins> frogmouth = callPackage ../tools/text/frogmouth { }; </ins> fselect = callPackage ../tools/misc/fselect { }; fsmon = callPackage ../tools/misc/fsmon { };
Change:
The Hack font is the recommended monospaced font for KDE since plasma 5.8. Currently, Hack isn't installed with KDE and the first available font is used by KDE (arimo in my case). Install KDE on a fresh NixOS installation. Noto is installed but not Hack. System: NixOS: Nix version: nix-env (Nix) 1.11.6 Nixpkgs version: "17.03pre101267."

Discussion:
then { GDK_PIXBUF_MODULE_FILE = "${pkgs.librsvg.out}/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache"; } else { }); <del> fonts.fonts = [ (kde5.oxygen-fonts or pkgs.noto-fonts) ]; </del> <ins> fonts.fonts = [ (kde5.oxygen-fonts or pkgs.noto-fonts) pkgs.hack-font ]; </ins> programs.ssh.askPassword = "${kde5.ksshaskpass.out}/bin/ksshaskpass";
Change:
Steps to reproduce the behavior: from latest master I have not seen this build successfully on my machine since before March 18. I imagine there was some wide-reaching change merged in from that caused this. Please run and paste the result.
This was caused by , The texinfo package could be overridden in for mitscheme to use texinfo6

Discussion:
mitama-cpp-result = callPackage ../development/libraries/mitama-cpp-result { }; <del> mitscheme = callPackage ../development/compilers/mit-scheme { texLive = texlive.combine { inherit (texlive) scheme-small epsf texinfo; }; }; </del> <ins> mitscheme = callPackage ../development/compilers/mit-scheme { texLive = texlive.combine { inherit (texlive) scheme-small epsf texinfo; }; texinfo = texinfo6; }; </ins> mitschemeX11 = mitscheme.override { enableX11 = true;