jiebi/CodeConvo huggingface dataset:
Change:
sha256 = "0313xb2j6a4wihrw9gfd4rnyqw7zzv6wf3rfh2gglgnv356ic2kw"; }; <del> buildInputs = [ utillinux /* provides getopt */ libcap ]; </del> <ins> # patchset from brew patches = stdenv.lib.optionals stdenv.isDarwin [ (fetchpatch { name = "0001-Implement-openat-2-wrapper-which-handles-optional-ar.patch"; url = "https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=0001-Implement-openat-2-wrapper-which-handles-optional-ar.patch;att=1;bug=766649"; sha256 = "1m6ggrqwqy0in264sxqk912vniipiw629dxq7kibakvsswfk6bkk"; }) (fetchpatch { name = "0002-OS-X-10.10-introduced-id_t-int-in-gs-etpriority.patch"; url = "https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=0002-OS-X-10.10-introduced-id_t-int-in-gs-etpriority.patch;att=2;bug=766649"; sha256 = "0rhayp42x4i1a6yc4d28kpshmf7lrmaprq64zfrjpdn4kbs0rkln"; }) (fetchpatch { name = "fakeroot-always-pass-mode.patch"; url = "https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=766649;filename=fakeroot-always-pass-mode.patch;msg=20"; sha256 = "0i3zaca1v449dm9m1cq6wq4dy6hc2y04l05m9gg8d4y4swld637p"; }) ]; buildInputs = [ getopt ] ++ stdenv.lib.optional (!stdenv.isDarwin) libcap ; </ins> postUnpack = '' for prog in getopt; do

Discussion:
does not appear to be supported on ; this is possible via , and works with no issue, so it does not appear to be a technical limitation. I am not familiar enough with Nix to port over the homebrew packaging, but was planning on taking a stab if this issue does not get traction. or and System: Nix version: Nixpkgs version:
Change:
wisper (2.0.1) PLATFORMS <del> x86_64-linux </del> <ins> ruby </ins> DEPENDENCIES pdk (= 3.0.1)

Discussion:
I'm using nix-darwin on Mac OS. Installing the works, but running it afterwards throws the following error: Steps to reproduce the behavior: pdk from nixpkgs on macOS The command should run without error Building the package locally, and changing this line to say instead of x86_64-linux results in a package with a functional command. Apologies for any missing info or incorrect terminology, I'm new to nix.
Change:
, nixosTests }: <del> python3.pkgs.buildPythonApplication rec { </del> <ins> python311Packages.buildPythonApplication rec { </ins> pname = "guake"; version = "3.10";

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: lack of directory with executables In contrast this command works as expected: Create directory with executables to invoke Guake. Observe that nixpkgs 24.05 has and in the "Programs provided" section. <img width="989" alt="image" src=""And unstable does not despite both claiming to have version 3.10 of Guake: <img width="1201" alt="image" src=""And both branches provide the same package definition. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Seems like the cause is the below. Oddly the command fails but the build doesn't.
Change:
, writeShellScript , fetchFromGitHub , fetchpatch <ins> , nixosTests </ins> , freetype , libjpeg

Discussion:
Steps to reproduce the behavior: darling with Full 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
pangocairo = "${pango.out}/lib/libpangocairo-1.0${stdenv.hostPlatform.extensions.sharedLibrary}"; harfbuzz = "${harfbuzz.out}/lib/libharfbuzz${stdenv.hostPlatform.extensions.sharedLibrary}"; }) <del> # Disable tests for new Ghostscript # Remove when next version is released (fetchpatch { url = "https://github.com/Kozea/WeasyPrint/commit/e544398b00d76bc0317ea7e2abe40dc46b380910.patch"; sha256 = "sha256-oQO3j9Mo1x98WaLPROxsOn0qkeYRJrCx5QWWKoHvabE="; }) </del> ]; nativeBuildInputs = [

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process as 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: 54.3 desired version: 57.0 <!-- 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:
stdenv.mkDerivation rec { pname = "faustlive"; <del> version = "2.5.4"; </del> <ins> version = "unstable-dev-2020-08-03"; </ins> src = fetchFromGitHub { owner = "grame-cncm"; repo = "faustlive"; <del> rev = version; sha256 = "0npn8fvq8iafyamq4wrj1k1bmk4xd0my2sp3gi5jdjfx6hc1sm3n"; </del> <ins> rev = "c16565dc1b616ac0aad7c303c1997fa9e57177ab"; sha256 = "1ys661lp1xwz21vy12kwkg248jvjq1z9w433knkh0ldyy2igvmd5"; </ins> fetchSubmodules = true; };

Discussion:
Describe the bug To Reproduce Notify maintainers
I was informed that the dev branch has a commit that fixes this problem.
This is the fix, I guess: Can we add it to the derivative as a patch?
I tested the latest commit on the dev branch, and that builds and runs. Shall I do a PR? I guess a patch might work as well, but what would be the advantages of going that route? I can see not wanting to use a dev version of important libs and programs, but imho it's fine in this case.
Sure.
Change:
owner = "google"; repo = "jax"; # google/jax contains tags for jax and jaxlib. Only use jax tags! <del> rev = "refs/tags/jaxlib-v${version}"; </del> <ins> rev = "refs/tags/jax-v${version}"; </ins> hash = "sha256-poQQo2ZgEhPYzK3aCs+BjaHTNZbezJAECd+HOdY1Yok="; };

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags:
This was caused by your commit . Could you please revert or push a fix?
I kindly ask you to help the python-updates runs which make the python package set maintainable by fixing this build failure by updating the ignored test list and considering to support python-updates runs in the future and proactively updating the packages you maintain. Thank you.
As evidenced by this issue, python-updates is breaking packages... the opposite of increasing maintainability! It is incumbent on commit authors to test their changes before merging and produce fixes/rollbacks when their changes result in breakages.
Having a severely outdated package set is also increasing the burden on everyone and maintaining packages harder which outweighs the occasional breakage. This is not always possible, otherwise merging any update to a package that has more than a few hundred reverse deps becomes impossible and we are basically halting nixpkgs to a grind.
Change:
buildInputs = [ setuptools_scm ]; <del> checkInputs = [ backports_unittest-mock codecov coverage objgraph pathpy pytest pytest-sugar pytestcov ]; </del> <ins> checkInputs = [ backports_unittest-mock objgraph pathpy pytest pytestcov ]; </ins> checkPhase = '' LANG=en_US.UTF-8 pytest

Discussion:
has a test failure and won't install.
That's a known upstream issue:
I guess you didn't initially try to build pytest-sugar but some other package. That one should build fine once is merged.
thanks for looking into this. :)
Change:
stdenv.mkDerivation rec { pname = "solr"; <del> version = "8.6.1"; </del> <ins> version = "8.6.3"; </ins> src = fetchurl { url = "mirror://apache/lucene/${pname}/${version}/${pname}-${version}.tgz"; <del> sha256 = "0ds6zjsnwgpcmivzi7d6yqdmyn2mhf3k8g7xp26yfpm7f12gpq4g"; </del> <ins> sha256 = "0mbbmamajamxzcvdlrzx9wmv26kg9nhg9bzazk176dhhx3rjajf2"; </ins> }; nativeBuildInputs = [ makeWrapper ];

Discussion:
, CVSSv3=9.8 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc Cc
Change:
<del> { lib, buildGoModule, fetchurl </del> <ins> { lib, buildGoModule, fetchFromSourcehut </ins> , ncurses, notmuch, scdoc , python3, w3m, dante }:

Discussion:
Describe the bug Sources from archives from fail to download with hash mismatches. To Reproduce Expected behavior The hash should match and the source should download. Additional context It sounds like , causing changes to all generated archives (to come in-line with GNU gzip). I've determined some packages which this affects (listed in "Maintainer information") by . I'm happy to have a go making a PR for all of these packages with the following process: archive from cache (by with subsituters) archive from both and confirm tar files are identical hash according to newly retrieved archive But if there's a better process, please let me know :) Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Sounds good
I think it is preferable to switch all affected derivations to fetchzip. This should prevent this from happening again, if the actual content of the tarball is the same. Even better, you could add a fetchFromSourceHut function which uses fetchzip under the hood, like fetchFromGitHub and fetchFromGitLab. This would encourage people not to use fetchurl to fetch procedurally generated tarballs from sourcehut.
From a quick look at the ticket, this is supposed to be a one-time change to make the hash the same as in other forges though
I think getting the new hashes with e.g. should be enough (fetches securely via HTTPS and we should be able to trust that the contents remain unchanged). +1, that seems like the best (long-term) solution. Edit: And IMO we should keep using archives (e.g. because it's consistent with the GitHub and GitLab fetchers) and should indeed be fine now:
the point is: with fetchzip, we don't have to trust this pinky promise (I mean, I'm sure that they intend to keep it, but it could break unwillingly). That's exactly why fetchzip exists in the first place. So on fixes keeping fetchurl.
oh, my bad, I didn't read your comment carefully enough :o I thought you've meant vs. (which didn't make much sense) but realized now that it was vs. . :+1: for that then :)
Hah, same. too then
is merged now so you could submit a PR to switch the affected attributes/packages to the new (s. ). I can also take care of it if you want.
Change:
inherit sha256; }); <ins> xsa = import ./xsa-patches.nix { inherit fetchpatch; }; </ins> qemuDeps = [ udev pciutils xorg.libX11 SDL pixman acl glusterfs spice_protocol usbredir alsaLib

Discussion:
is no longer operational so the following expressions will break: System: 17.09.1789. (Hummingbird) Nix version: nix-env (Nix) 1.11.15 Nixpkgs version: 17.09.1789. Sandboxing enabled: build-use-sandbox = false
Change:
libxshmfence elfutils expat <del> libffi </del> <ins> libffi_3_3 </ins> libselinux # libudev is not listed in any dependencies, but is loaded dynamically udev

Discussion:
Steps to reproduce the behavior: libffi-3.3 Fails as a dependency of amdgpu-pro Please run and paste the result.
Both and build fine for me. does fail.
Oh:
I would say the problem is not in , but in . Proposed the possible fix as
/cc
Change:
<ins> { stdenv, lib, fetchFromGitHub, fetchpatch, cmake, mesa, libGLU, glfw, libX11, libXi, libXcursor, libXrandr, libXinerama, alsaSupport ? stdenv.hostPlatform.isLinux, alsaLib, pulseSupport ? stdenv.hostPlatform.isLinux, libpulseaudio, includeEverything ? true }: stdenv.mkDerivation rec { pname = "raylib"; version = "3.5.0"; src = fetchFromGitHub { owner = "raysan5"; repo = pname; rev = version; sha256 = "0syvd5js1lbx3g4cddwwncqg95l6hb3fdz5nsh5pqy7fr6v84kwj"; }; patches = [ # fixes examples not compiling in 3.5.0 (fetchpatch { url = "https://patch-diff.githubusercontent.com/raw/raysan5/raylib/pull/1470.patch"; sha256 = "1ff5l839wl8dxwrs2bwky7kqa8kk9qmsflg31sk5vbil68dzbzg0"; }) ]; nativeBuildInputs = [ cmake ]; buildInputs = [ mesa libGLU glfw libX11 libXi libXcursor libXrandr libXinerama ] ++ lib.optional alsaSupport alsaLib ++ lib.optional pulseSupport libpulseaudio; # https://github.com/raysan5/raylib/wiki/CMake-Build-Options cmakeFlags = [ "-DUSE_EXTERNAL_GLFW=ON" "-DSHARED=ON" "-DBUILD_EXAMPLES=OFF" ] ++ lib.optional includeEverything "-DINCLUDE_EVERYTHING=ON"; # fix libasound.so/libpulse.so not being found preFixup = '' ${lib.optionalString alsaSupport "patchelf --add-needed ${alsaLib}/lib/libasound.so $out/lib/libraylib.so.${version}"} ${lib.optionalString pulseSupport "patchelf --add-needed ${libpulseaudio}/lib/libpulse.so $out/lib/libraylib.so.${version}"} ''; meta = with lib; { description = "A simple and easy-to-use library to enjoy videogames programming"; homepage = "http://www.raylib.com/"; license = licenses.zlib; maintainers = with maintainers; [ adamlwgriffiths ]; platforms = platforms.linux; }; } </ins>

Discussion:
Project description raylib is a simple and easy-to-use library to enjoy videogames programming. raylib is highly inspired by Borland BGI graphics lib and by XNA framework and it's specially well suited for prototyping, tooling, graphical applications, embedded systems and education. Metadata homepage URL: source URL: license: zlib platforms: unix, linux, darwin, android, webasm
I've got a PR I'm preparing which adds this.
Change:
, stdenv , fetchurl , makeWrapper <ins> , wrapGAppsHook </ins> , alsa-lib , at-spi2-atk , at-spi2-core

Discussion:
When trying to attach a file to a secret, 1password exits with an error: Steps to reproduce the behavior: 1password a password to attach a file File dialog opens If applicable, add screenshots to help explain your problem. I managed to solve it (in a pretty much trial and error, not fully understanding) by overriding the attributes as described here: also adding gtk to the buildInputs: The file open dialog shows but it's not the same as in the rest of the system <!-- 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.
Change:
<del> { lib , stdenvNoCC , fetchFromGitHub , rename </del> <ins> { lib, stdenvNoCC, fetchFromGitHub, rename, unstableGitUpdater, </ins> }: stdenvNoCC.mkDerivation { pname = "material-symbols"; <del> version = "unstable-2023-11-17"; </del> <ins> version = "4.0.0-unstable-2024-05-17"; </ins> src = fetchFromGitHub { owner = "google"; repo = "material-design-icons"; <del> rev = "a90037f80d7db37279a7c1d863559e247ed81b05"; hash = "sha256-96nEvc9eBuAncPUun3JBeg+KW2GqT3mQNgdOCVdhEM0="; </del> <ins> rev = "ace1af08508a6562ef05055a606cf44ea583ce3b"; hash = "sha256-d5lojgYCXCcvcSfLWfcSKFsBGKB6Si/XreRqpkEKsa0="; </ins> sparseCheckout = [ "variablefont" ]; };

Discussion:
Package name:material-symbols Latest released version: 2024.05.04 <!-- Search your package here: --- Current version on the unstable channel: 2023.11.17 Current version on the stable/release channel: 2023.11.17 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Are there any relevant changes in the font definition?
there should be some new symbols or some symbols' code changed.
please do replace OLDVERSION and NEWVERSION in the issue title with the actual version names. In this case this would be like:
Change:
sha256 = "1qw554jbdnqkg6pjjl4cqkgsalq3398kzvww2naw30vykcz752bm"; }; <del> buildInputs = [ fontforge pythonPackages.fonttools python ]; </del> <ins> buildInputs = [ fontforge python3Packages.fonttools python3 ]; </ins> installPhase = '' find . -name '*Narrow*.ttf' -exec install -m444 -Dt $out/share/fonts/truetype {} ;

Discussion:
Describe the bug Trying to rebuild from git master and it complains about fonttools and python version mismatch. To Reproduce Metadata Please run and paste the result. root nix run -c nix-info -m system: host os: multi-user?: sandbox: version: nixpkgs: channels(root): Maintainer information:
Looks like an issue with trying to build it with Python 2.7.x. The code isn't entirely compatible with Python 3.x nevertheless.
The issue seems to be with nototools which we currently have disabled for python3. The last nototools release is apparently fully compatible with python3. I'm working on a fix for this, however, the build now has a strange relationship with noto-fonts that I haven't quite figured out yet.
In the latest release nototools seems to still fail, or at least does on mine. The only relationship I found is that nototools is a dependency on noto-fonts.
you mean when running , or something similar? That's expected since nototools has been disabled for python3 (python3 support has only recently been upstream). I believe the relationship is actually that nototools is a dep of noto-fonts-emoji. The current nototools seems to require noto-fonts as a dep. I've gotten most of the way to a fix I think (changed nototools version and enabled py3 and what we fetch with the fetchZip in noto-fonts). However, the way that nototools expects noto-fonts is pretty strange (as an example look at the top level makefile where it looks for the noto-fonts repo in nototools' parent directory). I'm having a bit of trouble getting noto-fonts in the form nototools expects. I'm trying not to just copy the entire noto-fonts source into nototools source which seems like it should be unnecessary. Once nototools is fixed for python3 the rest should be easy bc we can just change noto-fonts etc to use python3. If you have any thoughts on how to fix nototools I'd love to hear them, or if you think I'm missing something here pls do let me know.
should be a dependency of the derivation. I'm not sure where you're seeing the fact that needs as a dependency.

The farthest I've gotten is removing all the errors from the configuration but the build still fails with .
You mean that it should be a dependency of or it is currently? In regard to "is currently" I don't see it as currently being a dependency. The only place appears in noto- is in the following lines as part of derivation. If you mean it should be, then how you get to build on its own? If you change the nototools version to 0.2.0 which adds python3 support I get errors about missing font directories (these directories come from noto-fonts). What am I missing here?
Proposed fix Still building though...
, and have the same error.
Change:
karchive kcmutils kconfig kdnssd kguiaddons kinit kirigami2 knewstuff knotifyconfig ktexteditor kwindowsystem phonon plasma-framework threadweaver curl fftw ffmpeg gdk-pixbuf libaio liblastfm libmtp loudmouth lz4 lzo mysql57.server mysql57.server.static <del> pcre snappy taglib taglib_extras </del> <ins> pcre snappy taglib taglib_extras breeze-icons </ins> ]; enableParallelBuilding = true;

Discussion:
nixos 16.03 nix-env -i amarok :( (I'm not using kde, I'm using xfce+gtk)
(triage) still missing?
Still the case on 18.09pre140958.
ping maintainer
Amarok for Qt4/KDE4 was dropped some time ago (despite there being a recent release) so are you seeing this with the qt4 or the qt5 version?
(triage) still an issue at
Missing from where exactly? It's working here.
This is how amarok looks for me: ! I believe there should be some icons there. The icon in the system tray is also missing. (Tested with awesome wm.)
That's not right. On KDE however, it's fine. I will take a look at this but I cannot promise you when.
Still an issue at any chance for you to look into this?
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 . on the on .
I haven't been using amarok in ages - is this still a problem for you on 20.03 ?
Never used Amarok myself. One from nixpkgs unstable seems to grow a couple of icons but most are still missing. I don't use KDE, so that might be the reason. !
So it's expecting to find the icons in the global environment - it's basically an impurity. I'm realistically not going to be working on this but it's very much a legit issue.
I marked this as stale due to inactivity. &rarr;
Please revisit this again. !
Still no icons on non-KDE (this time EXWM). what DE/WM do you use? !
Apologies. I didn't see part. I'm on KDE right now. Looking through stale issues.

thank you for reviewing stale issues! I can confirm issue still exists. It's little better on latest unstable, there are some icons like on screenshot.
Installing the package fixed this for me on unstable.
I marked this as stale due to inactivity. &rarr;
Change:
# generation is the attribute version suffix such as 3_11 in pkgs.cassandra_3_11 , generation , version, sha256 <ins> , extraMeta ? {} </ins> , ... }:

Discussion:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
See also , ,
Change:
email = "j.loos@posteo.net"; githubId = 57965027; }; <ins> josephst = { name = "Joseph Stahl"; email = "hello@josephstahl.com"; github = "josephst"; githubId = 1269177; }; </ins> joshniemela = { name = "Joshua Niemelä"; email = "josh@jniemela.dk";

Discussion:
Project description A command-line application that will automatically synchronize recommended settings from the to your Sonarr/Radarr instances. Metadata homepage URL: source URL: license: mit platforms: linux