jiebi/CodeConvo huggingface dataset:
Change:
termbox = callPackage ../development/libraries/termbox { }; <del> tevent = callPackage ../development/libraries/tevent { python = python2; }; </del> <ins> tevent = callPackage ../development/libraries/tevent { }; </ins> tet = callPackage ../development/tools/misc/tet { };

Discussion:
Describe the bug build of failed. To Reproduce Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(gtgteq): nixpkgs: Maintainer information:
Looks like regression in . We need to build talloc with Python 3 too.
It might also need
Change:
basename = if bleedingEdgeVersion then "gdb-7.3.20110726" <del> else "gdb-7.4"; </del> <ins> else "gdb-7.4.1"; </ins> # Whether (cross-)building for GNU/Hurd.  This is an approximation since # having `stdenv ? cross' doesn't tell us if we're building `hostDrv' and

Discussion:
Describe the bug Thunderbird 78.2.1 is working. master (Thunderbird 78.2.2) has rendering issues (see screenshot). Most buttons do not react to clicks and the menu is also not reacting. To Reproduce Switch to the mentioned commit and rebuild. Expected behavior Normally working thunderbird. Screenshots ! Notify maintainers Metadata
This was also a bug in Ubuntu, it was fixed there with:
Upstream bug appears to be
Btw temporary workaround would be to switch to thunderbird-bin-78 if you are not opposed to binaries
Change:
<ins> { lib, stdenv, fetchFromGitHub, fetchpatch, cmake, pkg-config , libpng, libtiff, lcms2, jpylyzer , mj2Support ? true # MJ2 executables , jpwlLibSupport ? true # JPWL library & executables , jpipLibSupport ? false # JPIP library & executables , jpipServerSupport ? false, curl ? null, fcgi ? null # JPIP Server #, opjViewerSupport ? false, wxGTK ? null # OPJViewer executable , openjpegJarSupport ? false # Openjpeg jar (Java) , jp3dSupport ? true # # JP3D comp , thirdPartySupport ? false # Third party libraries - OFF: only build when found, ON: always build , testsSupport ? true , jdk ? null }: assert jpipServerSupport -> jpipLibSupport && curl != null && fcgi != null; #assert opjViewerSupport -> (wxGTK != null); assert (openjpegJarSupport || jpipLibSupport) -> jdk != null; let inherit (lib) optional optionals; mkFlag = optSet: flag: "-D${flag}=${if optSet then "ON" else "OFF"}"; in stdenv.mkDerivation rec { pname = "openjpeg"; version = "2.4.0"; # don't forget to change passthru.incDir src = fetchFromGitHub { owner = "uclouvain"; repo = "openjpeg"; rev = "v${version}"; sha256 = "143dvy5g6v6129lzvl0r8mrgva2fppkn0zl099qmi9yi9l9h7yyf"; }; patches = [ ./fix-cmake-config-includedir.patch (fetchpatch { url = "https://patch-diff.githubusercontent.com/raw/uclouvain/openjpeg/pull/1321.patch"; sha256 = "1cjpr76nf9g65nqkfnxnjzi3bv7ifbxpc74kxxibh58pzjlp6al8"; }) ]; outputs = [ "out" "dev" ]; cmakeFlags = [ "-DCMAKE_INSTALL_NAME_DIR=${CMAKE_INSTALL_PREFIX}/lib" "-DBUILD_SHARED_LIBS=ON" "-DBUILD_CODEC=ON" (mkFlag mj2Support "BUILD_MJ2") (mkFlag jpwlLibSupport "BUILD_JPWL") (mkFlag jpipLibSupport "BUILD_JPIP") (mkFlag jpipServerSupport "BUILD_JPIP_SERVER") #(mkFlag opjViewerSupport "BUILD_VIEWER") "-DBUILD_VIEWER=OFF" (mkFlag openjpegJarSupport "BUILD_JAVA") (mkFlag jp3dSupport "BUILD_JP3D") (mkFlag thirdPartySupport "BUILD_THIRDPARTY") (mkFlag testsSupport "BUILD_TESTING") "-DOPENJPEG_INSTALL_INCLUDE_DIR=${placeholder "dev"}/include/${passthru.incDir}" "-DOPENJPEG_INSTALL_PACKAGE_DIR=${placeholder "dev"}/lib/${passthru.incDir}" ]; nativeBuildInputs = [ cmake pkg-config ]; buildInputs = [ ] ++ optionals jpipServerSupport [ curl fcgi ] #++ optional opjViewerSupport wxGTK ++ optional (openjpegJarSupport || jpipLibSupport) jdk; propagatedBuildInputs = [ libpng libtiff lcms2 ]; doCheck = (testsSupport && !stdenv.isAarch64); # tests fail on aarch64-linux checkPhase = '' substituteInPlace ../tools/ctest_scripts/travis-ci.cmake  --replace "JPYLYZER_EXECUTABLE=" "JPYLYZER_EXECUTABLE="${jpylyzer}/bin/jpylyzer" # " OPJ_SOURCE_DIR=.. ctest -S ../tools/ctest_scripts/travis-ci.cmake ''; passthru = { incDir = "openjpeg-2.4"; }; meta = with lib; { description = "Open-source JPEG 2000 codec written in C language"; homepage = "https://www.openjpeg.org/"; license = licenses.bsd2; maintainers = with maintainers; [ codyopel ]; platforms = platforms.all; }; } </ins>

Discussion:
, CVSSv3=7.8 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
See also: ,
Change:
"upperdir=/nix/.rw-store/store" "workdir=/nix/.rw-store/work" ]; <ins> depends = [ "/nix/.ro-store" "/nix/.rw-store/store" "/nix/.rw-store/work" ]; </ins> }; boot.initrd.availableKernelModules = [ "squashfs" "iso9660" "uas" "overlay" ];

Discussion:
Describe the bug Edit: After looking at it for a while, it seems the real problem is that this function is too strict: I think it should be something like this instead: To Reproduce Because comes before alphabetically, it's mounted first (which fails). You can read the file using: Expected behavior The list of file systems to be topologically sorted. Additional context Originally found this while trying to try out root-on-tmpfs. Notify maintainers Couldn't find anyone. <!-- 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(root): channels(jakob): nixpkgs: Maintainer information:
This is also a problem when using since the dependencies are specified in not or and for this problem is not enough to fix the issue. The option sugested by in would solve it. Actually the only reason the current ISO and netboot images aren't broken because of this (they use ) is solely because and comes alphabetically before .
I marked this as stale due to inactivity. &rarr;
This is still an issue, and for me a fairly big one, since I can't generate secrets with agenix with my current setup:
Change:
# Necessary for BTF DEBUG_INFO                = mkMerge [ (whenOlder "5.2" (if (features.debug or false) then yes else no)) <del> (whenAtLeast "5.2" yes) </del> <ins> (whenBetween "5.2" "5.18" yes) </ins> ]; <ins> DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT = whenAtLeast "5.18" yes; </ins> DEBUG_INFO_BTF            = whenAtLeast "5.2" (option yes); BPF_LSM                   = whenAtLeast "5.7" (option yes); DEBUG_KERNEL              = yes;

Discussion:
Steps to reproduce the behavior: Tail of the build log The build failure seems related to these unused options. I tried removing the corresponding lines (in a local directory - so I changed my url to the filesystem path). in but it didn't fix anything. It seems that kernel 5.18 phased out some options. Instead of warning us, there's an explicit error. I have no idea how to fix this since is great for adding lines to the kernel config, but not great at removing them. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (I'm not exactly sure who to notify about this so I just kind of scanned s of and . Please let me know if there's someone more appropriate to notify.) Please run and paste the result. Not sure how to do this for this specific package (no ).
Can you check if fixes this?
. But, it still fails:
Should be fixed by
I can confirm that fixes this! Thanks !
Change:
unstable = fetchurl rec { # NOTE: Don't forget to change the SHA256 for staging as well. <del> version = "7.10"; </del> <ins> version = "7.12"; </ins> url = "https://dl.winehq.org/wine/source/7.x/wine-${version}.tar.xz"; <del> sha256 = "sha256-P+skzYWYwQ9q9xHnSsK10kQrtNO4wHj506JTroc2SA0="; </del> <ins> sha256 = "sha256-gJzsE3FmNubq/Uw9pzEkVqhE0xYCClV4YRvNuiEGnGg="; </ins> inherit (stable) gecko32 gecko64 patches; mono = fetchurl rec {

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: winePackages.{unstable,staging} <!-- 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: 7.10 desired version: 7.12 <!-- 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.
cc
PR at , needs to be tested still. My last attempts at updating have been held back by the fact that there are so many variants that building everything is prohibitively time consuming on my machine, and PRs that were ready have been lingering so long that I've had to update them with one or two even newer wine versions before they were merged, so I was not particularly motivated.
Change:
inherit version; }; } // lib.optionalAttrs withLibvirt (import ./gemset_libvirt.nix)); <ins> # This replaces the gem symlinks with directories, resolving this # error when running vagrant (I have no idea why): # /nix/store/p4hrycs0zaa9x0gsqylbk577ppnryixr-vagrant-2.2.6/lib/ruby/gems/2.6.0/gems/i18n-1.1.1/lib/i18n/config.rb:6:in `<module:I18n>': uninitialized constant I18n::Config (NameError) postBuild = '' for gem in "$out"/lib/ruby/gems/*/gems/*; do cp -a "$gem/" "$gem.new" rm "$gem" mv "$gem.new" "$gem" done ''; </ins> }; in buildRubyGem rec {

Discussion:
Describe the bug Vagrant no longer works; every operation fails with an error . I bisected this regression to commit “ruby: rubygems 3.0.6 -3.1.2” (). To Reproduce Expected behavior Metadata Maintainer information: cc
I note that the “smoke test” in was not sufficient to catch this problem, although would have. Perhaps would be even better?
Just took a look at this as well (please note that I'm not a ruby developer, so I may be missing something). 3.1.x seems to require bundler now[1] and vendors bundler 2.1.2[2] in version 3.1.2, however ruby 2.6 vendors bundler 1.17, so there's probably some kind of mismatch when using rubygems 3.1.2. Not sure, but would it make sense to add different rubygems versions for different ruby versions? [1] [2]
Change:
bingo = callPackage ../development/tools/bingo { }; <ins> bin2c = callPackage ../development/tools/bin2c { }; </ins> binserve = callPackage ../servers/binserve { inherit (darwin.apple_sdk.frameworks) CoreServices; };

Discussion:
Project description bin2c can be used to embed binary & text files inside C binaries. Metadata homepage URL: source URL: license: apache platforms: unix, linux, darwin, ...
Change:
with subtest("Home screen loads"): machine.succeed( <del> "curl -sSfL http://localhost:8000 | grep '<title>Sign In'" </del> <ins> "curl -sSfL http://localhost:8000 | grep '<title>Log In'" </ins> ) with subtest("Setting SITE_NAME via freeform option works"):

Discussion:
I'm running (this specific package) on (config at ). This happened after upgrading from . Seems like a recent (?) django update has caused the service to fail due to breaking changes on django 5.1: Not really sure if this needs a specific upgrade path since it seems to be from migrations, but after the fix (see below) no migrations were run, so perhaps this happens every time. Steps to reproduce the behavior: healthchecks with that has failed (maybe?) should complete successfully. The error seems related to a , where they removed from . adds support for Django 5.1, so an upgrade to that version should fix the issue. Unfortunately, the automatic PR seems to be failing tests (). This is the fix upstream: I'm currently applying this fix to my config, see the commit ; it fixes the issue for now, and can run successfully: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for the report. Update is easy, it was just the test failing due to a slight change in wording on the site tested. See
Change:
wantedBy = [ "multi-user.target" ]; serviceConfig = { <del> ExecStart = "${pkgs.atuin}/bin/atuin server start"; </del> <ins> ExecStart = "${lib.getExe cfg.package} server start"; </ins> RuntimeDirectory = "atuin"; RuntimeDirectoryMode = "0700"; DynamicUser = true;

Discussion:
The options do not yet feature a to set the package. This might be helpful for people that want to pin to a specific version. This is helpful because enforces (from 18.0.0 on, AFAIK) that the sync server version and the client version match (as in "are the same"). For people running nixos unstable on their end-user device but nixos stable on their server, this might be helpful. I think this is a rather simple one, if someone wants to learn how to do that, I am here to help.
Change:
${config.services.mysql.package}/bin/mysql < ${pkg}/share/zoneminder/db/zm_create.sql touch "/var/lib/${dirName}/db-created" fi <ins> ${zoneminder}/bin/zmupdate.pl -nointeractive </ins> ''; serviceConfig = { User = user;

Discussion:
Zoneminder, but it seems there is no code that handles upgrades, while that is provided by upstream and for example the Ubuntu packaging. It seems to be more of a developer preview version on NixOS than something that could be used by end-users in a production environment. I would have a flag like that needs to be set to true before it does something for that reason. I welcome the progress that has been made, but it doesn't appear to be in good enough shape to compete with other solutions. I will open another issue for adding declarative camera support (), because there was another user who also wanted to have that, which should also make this issue smaller.
Looking at zoneminder_1.30.4+dfsg- in debian/TODO.Debian it says: and there is no mention of the in the scripts. Are you sure Ubuntu has support for this? My personal opinion is that automatic upgrades are not such a great thing. While there are provided migrations to upgrade the database, there doesn't seem to be an official way to downgrade. This conflicts with the nature of Nix where we expect seamless version changes in any direction. Having user manually run ensures that they are aware of the upgrade and prepared for consequences.
has recently changed, but I have seen it upgrade automatically and there was at some point some code for doing it automatically. The manual part here only seems to be the ppa configuration. The main point is that the effort required on Ubuntu is less than on NixOS.
Yes, I see that this PPA with an unofficial zoneminder package (from Ubuntu standpoint) does indeed run in its zoneminder.postinst script.
I wasn't aware of this issue until just now, hence the rather late reply. That is correct - so far we have only released a single version in nixpkgs but of course it will come back and bite us. Things can break in unstable - nothing new there and unless we hit security issues, new versions will not be back-ported, so that at least gives us to 19.09 to sort out. What other options (packaged for NixOS) do we have? I personally have very strong reservations about the architectural choices the ZM developers have made, but I am not aware of any real alternative ATM. Declarative camera support is definitely a good idea.

I support for ZM because I needed it and it solves my problem right now (until we need to update of course), but any PR would be very much welcome.
The is already part of the package - we just don't do anything with it and according to the comment in the header: But then of course it does have functionality for dealing with a number of changes. So the short version - someone just has to write (and test) how it behaves when upgraded and ensure this runs. I am realistically not going to work on that right now though.
Change:
lapack blas ] ++ lists.optionals cudaSupport [ <del> cuda_joined </del> <ins> cuda-redist </ins> ] ++ lists.optionals rocmSupport [ hip hipblas

Discussion:
Per , assuming NVIDIA continues with its current compute capability naming scheme, will run into issues with the launch of Blackwell. This is a followup from <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
<del> { fetchurl, stdenv, pkgconfig, libdaemon, dbus, perlPackages </del> <ins> { fetchurl, fetchpatch, stdenv, pkgconfig, libdaemon, dbus, perlPackages </ins> , expat, gettext, intltool, glib, libiconv , gtk3Support ? false, gtk3 ? null , qt4 ? null

Discussion:
, (nixos-unstable, nixos-19.03, nixos-18.09) Scanned versions: nixos-unstable: ; nixos-19.03: ; nixos-18.09: . May contain false positives.
Change:
"--enable-udev" "--with-scanbdconfdir=/etc/scanbd" "--with-systemdsystemunitdir=$out/lib/systemd/system" <ins> ] ++ lib.optionals (stdenv.hostPlatform != stdenv.buildPlatform) [ # AC_FUNC_MALLOC is broken on cross builds. "ac_cv_func_malloc_0_nonnull=yes" "ac_cv_func_realloc_0_nonnull=yes" </ins> ]; enableParallelBuilding = true;

Discussion:
Steps to reproduce the behavior: This is the same problem as addressed here for cifs-utils:
Change:
notebook = callPackage ../development/python-modules/notebook { }; <ins> notebook-shim = callPackage ../development/python-modules/notebook-shim { }; </ins> notedown = callPackage ../development/python-modules/notedown { }; notifications-python-client = callPackage ../development/python-modules/notifications-python-client { };

Discussion:
Steps to reproduce the behavior: I have this in my home-manager config packages, and the build only fails if jupyterlab is uncommented. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Looks like it's broken because of : Looking at the commit range in the evaluation, it seems that it was broken by in
Already reported:
Right, thanks for the info. So I close the issue.

Steps to reproduce the behavior: This is a dependency of jupyterlab which prevents me from using the latest jupyterlab in jupyterWith I think this just needs somewhere but I'm not experienced enough with nixpkgs to inject it in the correct place.
Note: I tried to fix this using but it didn't work... idk why.
Change:
''; }; <ins> llama-cpp-rpc = (llama-cpp-grpc.overrideAttrs (prev: { name = "llama-cpp-rpc"; cmakeFlags = prev.cmakeFlags ++ [ (lib.cmakeBool "LLAMA_AVX" false) (lib.cmakeBool "LLAMA_AVX2" false) (lib.cmakeBool "LLAMA_AVX512" false) (lib.cmakeBool "LLAMA_FMA" false) (lib.cmakeBool "LLAMA_F16C" false) (lib.cmakeBool "LLAMA_RPC" true) ]; postPatch = prev.postPatch + '' sed -i examples/rpc/CMakeLists.txt  -e '$ainstall(TARGETS rpc-server RUNTIME)' ''; })).override { cudaSupport = false; openclSupport = false; blasSupport = true; # TODO: set to false, when dropping 23.11 support }; </ins> llama-cpp-grpc = (llama-cpp.overrideAttrs (final: prev: { name = "llama-cpp-grpc"; src = fetchFromGitHub { owner = "ggerganov"; repo = "llama.cpp"; <del> rev = "c12452c7aec8a02264afc00196a13caa591a13ac"; hash = "sha256-Kji8dlz7OfhPeNXnYgBHzpGGMhCsRLJ9d+EFf77Q6Co="; </del> <ins> rev = "74f33adf5f8b20b08fc5a6aa17ce081abe86ef2f"; hash = "sha256-hSdHhsC5Q8pLEC2bj8Gke4/ffCts5l7LtYa9RDrpGBI="; </ins> fetchSubmodules = true; }; postPatch = prev.postPatch + ''

Discussion:
Package name: local-ai Latest released version: 2.16.0 <!-- Search your package here: --- Current version on the unstable channel: 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! --- On nixos-unstable, I currently have with so I thought I would try an update even though it's probably going to change nothing. Notify maintainers I was wondering if you had a script to update pkgs/by-name/lo/local- ? I've started doing it manually but it's annoying. Might be worth adding one, would you accept one ? Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
$out/libexec/darling/usr/libexec/darling/mldr ''; <ins> passthru.tests.nixos = nixosTests.darling; </ins> meta = with lib; { description = "Open-source Darwin/macOS emulation layer for Linux"; homepage = "https://www.darlinghq.org";

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:
, fixDarwinDylibNames, cctools, CoreServices, less , numactl # NUMA Support , withStorageMroonga ? true, kytea, msgpack, zeromq <del> , withoutClient ? false </del> }: with stdenv.lib;

Discussion:
Describe the bug Erorr first init mysql databases if use package builded To Reproduce Steps to reproduce the behavior: this patch command Expected behavior Error running this command Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: cc
Thanks for reporting Any of the , , , options require a client so I'm guessing the best we can do is document this. Any other ideas
is an argument that is only available for the derivation, and is not exposed in - so it's hard people stumble over this by accident. They need to explicitly set a global package override. Also, as error message by itself should already be clear enough, especially when looking at the system configuration. I don't consider this a bug. It works as intended - if you override mysql globally to not contain the client components, you'd have to expect client operations to fail. given you by yourself in , and it doesn't really work properly anyways, what about removing that argument?
When I made this parameter, I did not test database creation on first run. I wanted to split mariadb into components - server and client. Example in another distribution: But due to the different file locations, occur such errors. Is this variant bad? (Not worked witn MySQL 8.0)
If you use then there no reason to split package because you install both anyways. Arch Linux probably doesn't offer option so it makes sense.
What was the initial idea of having a server without the client binaries? Closure size reduction? In that case pulling in the client anyways in a separate derivation doesn't make much sense. I understand we want to have a separate client without pulling in server components (and we have that for mariadb), but I having the server without client isn't much of use. There's usually enough storage space on the database server to also ship the client binaries, and they are needed for most options in the mysql module, as well as for local administration / backups anyways. I'm pretty much for removing the argument. It causes a lot of confusion when uses for arguable benefit.