jiebi/CodeConvo huggingface dataset:
Change:
githubId = 12491746; name = "Masato Yonekawa"; }; <ins> hyzual = { email = "hyzual@gmail.com"; github = "Hyzual"; githubId = 2051507; name = "Joris Masson"; }; </ins> hzeller = { email = "h.zeller@acm.org"; github = "hzeller";

Discussion:
Project description is a server validation tool. It lets you write assertions in YAML format and runs them really fast to ensure your server matches them, for example it lets you assert some binary is present in path or some command gives an expected result, or that some port is open, etc. I personally use it a lot to test docker images through its sub-project , for which I'll submit another request. Metadata homepage URL: source URL: license: Apache License 2.0 platforms: linux. Darwin and windows support is alpha (see the )
Per request I am bringing up the question here from : should we split into a separate package ? I assumed that since they are different binaries, they would need different packages. Both and are built and released together in the same github repository. depends on , but may be used without it.
Change:
, lib , python , fetchurl <del> , substituteAll </del> , lame , mplayer , libpulseaudio <del> , pyqt4 </del> <ins> , pyqt5 , decorator , beautifulsoup4 </ins> , sqlalchemy , pyaudio <del> , httplib2 </del> <ins> , requests , markdown </ins> , matplotlib , pytest , glibcLocales

Discussion:
With the current packaged version of Anki, downloading addons fails with an SSLCERTIFICATEVERIFYFAILED. Download any addon from the Ankiweb library. I used , but any addon causes the issue. Go to to enter the ID. Then this error shows up in a dialog box: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
The update to anki 2.1 () will close this issue, according to my testing. (Add-on downloads work perfectly.)
(oops, I'll keep it open until that PR is merged)
Given that some useful addons don't support Anki 2.1, I'd like this to be fixed for 2.0. OTOH I'm not sure how this can be done.
You can still manually install addons by dropping the files in . An example is described .
Change:
substituteInPlace "$i" --replace /usr/NX/bin $out/bin done ''; postFixup = '' makeWrapper $out/bin/nxplayer.bin $out/bin/nxplayer --set NX_SYSTEM $out/NX makeWrapper $out/bin/nxclient.bin $out/bin/nxclient --set NX_SYSTEM $out/NX

Discussion:
Describe the bug Installing nomachine-client fails To Reproduce Steps to reproduce the behavior: to environment.systemPackages Expected behavior It should build the derivation Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata Please run and paste the result. Maintainer information:
I tried overriding the hash (any tip on how to more properly do this would be appreciated), but still got build errors in my under environment.systemPackages result:
There's a PR to upgrade : I this to my and it seems to be working for me:
Yep, this is because NoMachine removes each old release as soon as they make a new one. To combat this, I'll add to the sources list when the update is done.
I was finding at the time that even overriding with the latest URL and hash from the nomachine website, that it was failing to download the whole blob. I could do it from my browser, but it seemed to abort/not download the full size via nixos
Oh, that's strange.. Thankfully, it seems to work just fine now :)
Change:
owner = "scrapinghub"; repo = "extruct"; rev = "refs/tags/v${version}"; <del> hash = "sha256-6lAb17EoR0FKyIOb9hk1jcpmPtZ7vClfuCrDZ83XBeg="; </del> <ins> hash = "sha256-CfhIqbhrZkJ232grhHxrmj4H1/Bq33ZXe8kovSOWSK0="; </ins> }; nativeBuildInputs = [ setuptools ];

Discussion:
Steps to reproduce the behavior: python311Packages.extruct on () <!-- 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]:
oops, misread the log, should be fixed by
Change:
rev = version; hash = "sha256-OfY2zc+5CgOrgbiPVnvMdT4h1S7Aek8S7iThl6azmsk="; }; <ins> patches = [ ]; </ins> }); } // (plugins self); };

Discussion:
Only happened to me on Darwin (x86_64). <!-- 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.
Can confirm that I the same issue, with essentially identical output, on x86_64-darwin.
Change:
buildPythonPackage rec { pname = "greenlet"; <del> version = "0.4.17"; </del> <ins> version = "0.4.16"; </ins> disabled = isPyPy;  # builtin for pypy src = fetchPypi { inherit pname version; <del> sha256 = "41d8835c69a78de718e466dd0e6bfd4b46125f21a67c3ff6d76d8d8059868d6b"; </del> <ins> sha256 = "6e06eac722676797e8fce4adb8ad3dc57a1bb3adfb0dd3fdf8306c055a38456c"; </ins> }; propagatedBuildInputs = [ six ];

Discussion:
Describe the bug From This currently breaks at least mercurial and haskell-language-server. Notify maintainers
Title says , Hydra says , me trying to reproduce it says . FYI it works on .
Sorry for the wrong link. I blame hydra ui. But it is broken on master. This is the same build from : It is broken there and will be broken on nixos-unstable as soon as the channel gets bumped far enough, I guess. I can reproduce the issue locally on the master branch.
This problem will be solved by .
well, it doesn't fix the underlying problem. Just removes it. I tried building dulwich from source, but it doesn't seem to fix the issue. At the beginning of the tests, it mentions "there may be some abi incompatibility" then proceeds to segfault. But I couldn't even locate where the module was coming from.
Uh, yeah, right. That's what I meant of course.
did git bisect to find offending commit:
I still run into this problem on . Was the "fix" reverted again?
Change:
<ins> { lib, fetchurl, appimageTools, }: let pname = "ytmdesktop"; version = "1.13.0"; name = "${pname}-${version}"; src = fetchurl { url = "https://github.com/ytmdesktop/ytmdesktop/releases/download/v${version}/YouTube-Music-Desktop-App-${version}.AppImage"; sha256 = "0f5l7hra3m3q9zd0ngc9dj4mh1lk0rgicvh9idpd27wr808vy28v"; }; appimageContents = appimageTools.extract { inherit name src; }; in appimageTools.wrapType2 rec { inherit name src; extraInstallCommands = '' mv $out/bin/{${name},${pname}} install -m 444  -D ${appimageContents}/youtube-music-desktop-app.desktop  -t $out/share/applications substituteInPlace  $out/share/applications/youtube-music-desktop-app.desktop  --replace 'Exec=AppRun' 'Exec=${pname}' cp -r ${appimageContents}/usr/share/icons $out/share ''; meta = with lib; { description = "A Desktop App for YouTube Music"; homepage = "https://ytmdesktop.app/"; license = licenses.cc0; platforms = platforms.linux; maintainers = [ maintainers.lgcl ]; }; } </ins>

Discussion:
Project description Add Youtube Music Desktop player Metadata homepage URL: source URL: license: Creative Commons Zero v1.0 Universal platforms: linux, MacOS Similar application to Google Play Music Desktop:
Change:
contents (lib.range 0 (lib.length contents - 1)); pathsFromGraph = ./paths-from-graph.pl; <del> } </del> <ins> } // lib.optionalAttrs makeUInitrd { uInitrdCompression = uInitrdCompression; }) </ins>

Discussion:
We found (because it broke our build in Lix) that the following nixpkgs lib test is broken. It is run through some derivation in the test suite somewhere; finding that is an exercise to the reader, but it is included underneath somewhere. Run the following on any platform; it has been observed with this command on aarch64-darwin and x8664-linux: Then you will get an infinite output deepening like the following: Eventually it will segfault or otherwise exceed the recursion limit. We checked that this reproduces on Lix , Nix 2.18, and Nix 2.22, so it is not a Nix implementation bug for any reasonable value of "nix implementation". Steps to reproduce the behavior: the above command from a checkout of nixpkgs. ??? overflow! We don't think this is a regression from , but instead, that broken stuff was exposed as broken by actually running it on other platforms than x8664-linux. Evaluate as normal as is the case for other values of . If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Not really a maintainers list as I don't see one, but people who touched the file or the infra recently: Please run and paste the result. Note that this is not a Lix bug. system: host os: multi-user?: sandbox: version: channels(jade): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Since I have aarch64-darwin and aarch64-linux and I exposed this, I'll take a look at this tonight.
Please try with , I was able to use that command until I got:
Perhaps also check that this feature. You might need to sprinkle some more in a similar way
Thank you for mentioning that, I got it to pass on Darwin
Change:
tracker = callPackage ../development/libraries/tracker { }; <del> tracy = callPackage ../development/tools/tracy { }; </del> <ins> tracy-x11 = callPackage ../by-name/tr/tracy/package.nix { withWayland = false; }; </ins> trivy = callPackage ../tools/admin/trivy { };

Discussion:
No crash n/a n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Same problem, same message, with the following system. WM: sway
Attempted hacky workaround from This changes error to Progress?
Change:
<del> { lib, stdenv, fetchurl, lzma }: </del> <ins> { lib, stdenv, fetchFromGitHub , meson, ninja, pkg-config , python3 , icu , libuuid , xapian , xz , zstd , gtest }: </ins> stdenv.mkDerivation rec { pname = "zimlib"; <del> version = "1.4"; </del> <ins> version = "6.3.0"; </ins> <del> src = fetchurl { url = "http://www.openzim.org/download/${pname}-${version}.tar.gz"; sha256 = "14ra3iq42x53k1nqxb5lsg4gadlkpkgv6cbjjl6305ajmbrghcdq"; </del> <ins> src = fetchFromGitHub { owner = "openzim"; repo = "libzim"; rev = version; sha256 = "0iy0f1clhihq277x218ccx3mszgpr3h9l0by48b9ykr115nffw3s"; </ins> }; <del> buildInputs = [ lzma ]; </del> <ins> nativeBuildInputs = [ meson pkg-config ninja python3 ]; </ins> <del> enableParallelBuilding = true; </del> <ins> propagatedBuildInputs = [ icu libuuid xapian xz zstd ]; postPatch = '' patchShebangs scripts ''; checkInputs = [ gtest ]; doCheck = true; </ins> meta = with lib; { description = "Library for reading and writing ZIM files"; homepage =  "https://www.openzim.org/wiki/Zimlib"; license = licenses.gpl2; <del> maintainers = with maintainers; [ robbinch ]; </del> <ins> maintainers = with maintainers; [ ajs124 ]; </ins> platforms = platforms.linux; }; }

Discussion:
Describe the bug Kiwix fails to build with a C++ code error. To Reproduce Steps to reproduce the behavior: , because the package is marked as insecure, Expected behavior Kiwix builds. Additional context The error: Probably this needs to be solved for . 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(mario): channels(root): nixpkgs: Maintainer information:
I marked this as stale due to inactivity. &rarr;
See
Change:
{ lib, stdenv, fetchurl, pam, xmlsec }: let <ins> # TODO: Switch to OpenPAM once https://gitlab.com/oath-toolkit/oath-toolkit/-/issues/26 is addressed upstream </ins> securityDependency = if stdenv.isDarwin then xmlsec else pam;

Discussion:
The package doesn't build on Darwin due to a dependency on which doesn't exist in OpenPAM: There is an to potentially replace the use of functions from with something else on platforms where it doesn't exist. Based on , I think the intention is not to use PAM on Darwin anyway: So a reasonable fix could be simply to pass when building on Darwin, which solves the build failure. Notify maintainers Metadata Maintainer information:
test this
Yup, works.
Change:
{ lib, stdenv, fetchurl, fetchFromGitLab, jdk17_headless, coreutils, gradle_6, git, perl <del> , makeWrapper }: </del> <ins> , makeWrapper, fetchpatch }: </ins> let pname = "signald";

Discussion:
I used to find instances of log4j v2 (possibly affected by CVE-2021-). Packages listed below contain a log4j jar. Note that shipping the log4j jar does not imply vulnerability nor exploitability. This list is not exhaustive for many reasons (using 21.11 as index; packages not cached thus not indexed). Not vulnerable means I believe 21.05/21.11/unstable is not affected. Status ------ Fixed - 21.05? Upstream fix , not packaged Upstream fix , not packaged Fixed Fixed Fixed Upstream fix - Fixed Fixed , not packaged Not vulnerable (missing 21.05 backport) Upstream: Jitsi-videobridge instances older than 2.1-504 (May 2021) with callstats enabled should be updated to 2.1-504 or newer () Fixed Fixed Fixed Fixed Fixed Fixed 8.11.1 (2.16.0), not packaged - mitigated by adding  to your configuration Upstream (2.17.0), but unreleased Upstream (2.17.0) but Fixed (2.15.0) (no 2.17.0 released planned ) Not vulnerable Mitigated
Will patch pkgs.signald tonight.
Would it be possible to hook a scanner like into some postInstall-Hook for all packages depending on JDK? Or maybe directly into Hydra?
As soon as a new release of Jmeter is released, I'm going to update it.
I a note on how to mitigate the attack for .
Note that the Log4J maintainers have made additional releases (2.16.0 and 2.12.2) which are now as the fix for CVE-2021- (instead of 2.15). It fixes a (less severe) denial of service (CVE-2021-) and disables JNDI by default. Most downstream consumers will probably make yet another release...
I'm working on updating ELK 7 and should have a PR ready soon.
PR for Jmeter already submitted (). It will probably fix too, since log4j is running version.

I currently don't have time to go through all pull requests and update the table, but it's important to note that the second CVE has had its severity raised and various bypasses for the fixes in 2.15 have surfaced; version 2.15 still appears to be susceptible to RCE depending on the exact configuration/deployment. Packages should be upgraded to log4j2 2.16 (or 2.12.2) to be considered fixed. Also note for mitigation have been updated (deleting the JNDI class instead of disabling lookups through configuration). Additional reference:
Well, we will probably need to update all again soon:
Related MRs:
Another PR for Jmeter:
mediathekview might be affected. See PR
A new version of arduino with log4j fixes has been
A new version with fixes for log4j has been released for igv .
Can we close this issue or is there any open task?
From a quick look seems that Solr is the main one missing.
Let's close this. Packages should either be patched by now, otherwise they're likely to be orphaned and suffer from other issues as well. In case of Solr it looks like it has plenty of vulnerability tags slapped onto it.
Change:
glib gst_all_1.gstreamer SDL2 SDL2_image SDL2_mixer SDL2_ttf sqlite zlib ] ++ (with gst_all_1; [ gst-libav gst-plugins-base gst-plugins-good ]); <del> patches = [ ./include-paths.patch ]; </del> configurePhase = '' cmake RetroFE/Source -BRetroFE/Build -DCMAKE_BUILD_TYPE=Release  -DVERSION_MAJOR=0 -DVERSION_MINOR=0 -DVERSION_BUILD=0  <del> -DGSTREAMER_BASE_INCLUDE_DIRS='${gst_all_1.gst-plugins-base.dev}/include/gstreamer-1.0' </del> ''; buildPhase = ''

Discussion:
Looks like it lives and now. in nixpkgs hasn't been touched in 6 years. <!-- 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: 0.6.169 desired version: ? <!-- 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:
strictDeps = true; <ins> depsBuildBuild = [ pkg-config ]; </ins> nativeBuildInputs = [ meson ninja pkg-config scdoc validatePkgConfig <ins> wayland-scanner </ins> ]; buildInputs = [

Discussion:
Steps to reproduce the behavior: scenefx <!-- 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:
, gmime, json_glib, avahi, tracker, itstool }: stdenv.mkDerivation rec { <del> name = "grilo-plugins-0.2.13"; </del> <ins> name = "grilo-plugins-0.2.16"; </ins> src = fetchurl { url = "mirror://gnome/sources/grilo-plugins/0.2/${name}.tar.xz"; <del> sha256 = "008jwm5ydl0k25p3d2fkcail40fj9y3qknihxb5fg941p8qlhm55"; </del> <ins> sha256 = "00sjmkzxc8w4qn4lp5yj65c4y83mwhp0zlvk11ghvpxnklgmgd40"; </ins> }; installFlags = [ "GRL_PLUGINS_DIR=$(out)/lib/grilo-0.2" ];

Discussion:
Launch GNOME Music 3.18 There's no artwork at all Log: System: (Flounder) Nix version: nix-env (Nix) 1.11.2
Change:
callPackage ./generic.nix ({ inherit Foundation libobjc; <del> version = "5.20.1.27"; sha256 = "15rpwxw642ad1na93k5nj7d2lb24f21kncr924gxr00178a9x0jy"; </del> <ins> version = "5.20.1.34"; sha256 = "12vw5dkhmp1vk9l658pil8jiqirkpdsc5z8dm5mpj595yr6d94fd"; </ins> enableParallelBuilding = true; })

Discussion:
Describe the bug looks frequently (and currently) broken on aarch64: Perhaps the build is flaky? ! I see some stuff like this in the log in the failing cases: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This would be fixed by , at least on my machine.
Change:
<del> import ./make-test-python.nix ({ pkgs, ... }: </del> <ins> import ./make-test-python.nix ({ pkgs, lib, ... }: </ins> let port = 1888;

Discussion:
Describe the bug Expected behavior The nixos module should be aware of the deprecated options and the resulting config should be updated. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. Maintainer information:
Change:
./hardware/tuxedo-keyboard.nix ./hardware/ubertooth.nix ./hardware/usb-wwan.nix <del> ./hardware/onlykey.nix </del> <ins> ./hardware/onlykey/default.nix </ins> ./hardware/opentabletdriver.nix ./hardware/sata.nix ./hardware/wooting.nix

Discussion:
The onlykey udev rule in is different from the one available on the onlykey documentation here The onlykey isn't recognized using the udev rules currently available on the nixpkgs tree. I don't know why the two rules are completely different... Maybe there are two different versions of the onlykey out there using different hardware? Anyway, my workaround to get the onlykey working: add the correct udev rule manually, by using the option in your
Looks like it has been mentioned in the original pull request without response from the OP: The changes appears to have been done in so maybe ask there.
I marked this as stale due to inactivity. &rarr;
Change:
fcitx-configtool = callPackage ../tools/inputmethods/fcitx/fcitx-configtool.nix { }; <ins> chewing-editor = libsForQt5.callPackage ../applications/misc/chewing-editor { }; </ins> fcppt = callPackage ../development/libraries/fcppt { }; fcrackzip = callPackage ../tools/security/fcrackzip { };

Discussion:
Project description Cross platform chewing user phrase editor Chewing editor is a widely-used bopomofo input method for traditional Chinese, and chewing-editor is the tool to edit the database of user phrases stored by the input method. Users of chewing will need chewing-editor sooner or later. NixOS have chewing include as a fcitx engine () that can be used in the module, but not chewing-editor. Metadata homepage URL: source URL: license: gpl2 platforms: unix
The corresponding pull request is merged. Closing.
Change:
cl-print = null; # builtin tle = null; # builtin advice = null; # builtin <del> seq = if lib.versionAtLeast self.emacs.version "27" then null else super.seq; </del> # Compilation instructions for the Ada executables: # https://www.nongnu.org/ada-mode/ ada-mode = super.ada-mode.overrideAttrs (old: {

Discussion:
When on tries to open magit on 23.11 you get the in the output and the commands aren’t working as expected. Steps to reproduce the behavior: to 23.11 Emacs and Magit in a Git repo of your choice. to select a commit for example. The commit diff should be shown. ! The issue is already fixed upstream but requires some changes in Nixpkgs: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I can't repro this using nix-shell -p ' (ep: [ ])' -I nixpkgs=flake:github:NixOS/nixpkgs/nixos-23.11 and then running emacs via emacs -Q on aarch64-darwin.
I tried that and it's happening as well. The screenshot is from WSL but the initial finding is from NixOS. !
I reproduced the error here - with the same seq-keep error message. try to call it with then and finally .
That's what I did; I wouldn't know how to do it differently with my example. Though note that this is on aarch64-darwin. I don't have access to GUI Linux right now. An issue as obvious as this should happen here aswell though. Does the same happen inside a terminal frame?
Have you tested it inside an already-existing local Git repo? And yes, I have tested it here and now in a XTerm via . (Of course I am using my AMD machine.)
This is still broken.
It would require updating elisp-packages on stable.
I know, isn’t that approapriate when such an important package is broken?
It became a bit too hard recently, since Emacs triggers a mass rebuild.
FYI, I proposed a fix for this:
Ah okay, makes sense.
If I understood this correctly we need this to have it working in 24.05? Going to test it then.
Fixed by and Not sure why this issue is not closed by them though.