jiebi/CodeConvo huggingface dataset:
Change:
UDF_FS              = module; NFSD_V2_ACL            = yes; <del> NFSD_V3                = yes; </del> <ins> NFSD_V3                = whenOlder "5.18" yes; </ins> NFSD_V3_ACL            = yes; NFSD_V4                = yes; NFSD_V4_SECURITY_LABEL = 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:
fullName  = "CeCILL-C Free Software License Agreement"; }; <ins> cockroachdb-community-license = { fullName = "CockroachDB Community License Agreement"; url = "https://www.cockroachlabs.com/cockroachdb-community-license/"; free = false; }; </ins> cpal10 = { spdxId = "CPAL-1.0"; fullName = "Common Public Attribution License 1.0";

Discussion:
Cockroachdb releases 23.1 and newer will stop using BSL and instead use the proprietary CockroachDB licenses. Please update to reflect that.
IIUC BSL is not replaced but CockroachDB license is now on top.
Change:
package = hy; command = "hy -v"; }; <del> # also for backwards compatibility with removed pkgs/development/interpreters/hy withPackages = python-packages: (toPythonApplication hy).override { hyDefinedPythonPackages = python-packages; }; </del> <ins> # For backwards compatibility with removed pkgs/development/interpreters/hy # Example usage: #   hy.withPackages (ps: with ps; [ hyrule requests ]) withPackages = python-packages: python.withPackages (ps: (python-packages ps) ++ [ ps.hy ]); </ins> }; meta = with lib; {

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: 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:
nativeBuildInputs = [ autoreconfHook <del> makeWrapper </del> pkg-config <ins> wrapGAppsHook </ins> ]; buildInputs = [

Discussion:
Trying to run and interacting with the GUI in any meaningful matter results in this error: Steps to reproduce the behavior: from the terminal press or . <!-- 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.
It seems I cannot add you as reviewer, but could you take a look at the fix in ?
I sadly cannot test it right now. The earliest is start of October.
Change:
<ins> { stdenv , fetchFromGitHub , lib , autoPatchelfHook , cmake , tbb , llvmPackages_latest , xxHash , zlib , openssl }: stdenv.mkDerivation rec { pname = "mold"; version = "0.9.2"; src = fetchFromGitHub { owner = "rui314"; repo = pname; rev = "v${version}"; sha256 = "sha256-2LXOPirhjAifKYPgngUJwEdGrKMYsRySr5TL2x2p8J0="; }; buildInputs = [ tbb zlib openssl ]; nativeBuildInputs = [ autoPatchelfHook cmake xxHash ]; dontUseCmakeConfigure = true; EXTRA_LDFLAGS = "-fuse-ld=${llvmPackages_latest.lld}/bin/ld.lld"; LTO = 1; makeFlags = [ "PREFIX=${placeholder "out"}" ]; meta = with lib; { description = "A high performance drop-in replacement for existing unix linkers"; homepage = "https://github.com/rui314/mold"; license = lib.licenses.agpl3Plus; maintainers = with maintainers; [ nitsky ]; broken = stdenv.isAarch64; }; } </ins>

Discussion:
Project description Metadata homepage URL: source URL: license: GNU AGPL v3 platforms: unix, linux, darwin
Change:
with stdenv.lib; stdenv.mkDerivation rec { name = "${type}krb5-${version}"; <del> majorVersion = "1.18"; </del> <ins> majorVersion = "1.18"; # remove patches below with next upgrade </ins> version = majorVersion; src = fetchurl {

Discussion:
After (krb5: 1.17 -1.18) is merged, doesn't build with anymore. The error is: Since is a dependency of , this affects significant number of downstream packages. To Reproduce cc
Change:
<ins> import ./make-test-python.nix ({ pkgs, lib, ... }: { name = "containers-unified-hierarchy"; meta = { maintainers = with lib.maintainers; [ farnoy ]; }; nodes.machine = { ... }: { containers = { test-container = { autoStart = true; config = { }; }; }; }; testScript = '' machine.wait_for_unit("default.target") machine.succeed("echo 'stat -fc %T /sys/fs/cgroup/ | grep cgroup2fs' | nixos-container root-login test-container") ''; }) </ins>

Discussion:
Containers spawned by nixos-container fall back to old cgroup hierarchy, which does not support proper delegation of resource limits to processes running in that container. Steps to reproduce the behavior: will show Tainted: cgroupsv1 will show a mount This will be allowed to consume all memory of the machine until it runs out, the 4G cap is not enforced I expected the container to use a unified cgroup hierarchy, same as on the host, with full delegation and control over its subtree.
This is the log from , using declarative containers: I thought it could be relevant, but after googling around, these seem like errors that happen after systemd decided to use cgroupv1. I'm not sure how to debug its decision to use legacy cgroups inthe first place.
According to , systemd-nspawn tries to detect the systemd-version used in the container by locating a shared library with the version of systemd in the name. you can see the paths searched. The lookup fails on nix-based containers and systemd-nspawn falls back to legacy cgroups. You can test this yourself by symlinking from your Nix store to in your container. After restarting, reports .
Thanks, that was it. I also noticed this in the code But the following is not enough to enable it: Running didn't help either, so I'm not sure how you're supposed to use it. Should we add a symlink as a workaround? I think it'd make sense to fix it for all users of nixos-containers by defining it somewhere around here:
According to , This is not what we want. The environment variable is a good find though. I'm not sure why did not work for you, but adding to the following line worked. Can you reproduce this fix? PS: A PR fixing this issue would ideally include a regression test (almost like ) checking if the container runs with .
That worked! I can see with that the container is no longer tainted. Working on a PR now
Change:
postPatch = '' substituteInPlace requirements.txt  <del> --replace "aiohttp==3.6.2" "aiohttp>=3.6.2"  --replace "py-cpuinfo==7.0.0" "py-cpuinfo>=8.0.0" </del> <ins> --replace "aiohttp==3.7.4" "aiohttp>=3.7.4"  --replace "Jinja2==3.0.1" "Jinja2>=3.0.1"  --replace "sentry-sdk==1.3.1" "sentry-sdk>=1.3.1"  --replace "async-timeout==3.0.1" "async-timeout>=3.0.1"  </ins> ''; propagatedBuildInputs = with python.pkgs; [

Discussion:
On nixos-unstable, the package does not install: is installed No maintainer but pinging who last touched Please run and paste the result.
was updated to 4.0.1 a while back. is pinning most of it's dependencies thus the issue. Looks like that could need an update (available 2.2.18, upstream 2.2.27).
So I can build the upgraded package with the following: But it doesn't look right. I guess we shouldn't blindly replace pinned versions with incompatible versions. How does nixpkgs usually deals with this?
Change:
{ lib, stdenv, fetchurl, fetchzip, makeWrapper, runCommand, makeDesktopItem , xonotic-data, copyDesktopItems , # required for both <del> unzip, libjpeg, zlib, libvorbis, curl </del> <ins> unzip, libjpeg, zlib, libvorbis, curl, freetype, libpng, libtheora </ins> , # glx libX11, libGLU, libGL, libXpm, libXext, libXxf86vm, alsa-lib , # sdl

Discussion:
instead of UTF-8 characters there are often rectangles, spaces and random symbols ! ! ! !
Same here. Xonotic should have its own Xolonium font, but somewhy that one on screenshots is used instead.
Change:
gossipSecretFile = mkOption { type = types.path; description = mdDoc '' <del> File containing the shared secret key to use for gossip encryption. Required if `enableGossipEncryption` is set. </del> <ins> File containing the gossip secret, a shared secret key to use for gossip encryption.  Required if `enableGossipEncryption` is set.  This file may contain any arbitrary-length utf8 string.  To generate a new gossip secret, use a command such as `openssl rand -base64 32`. </ins> ''; }; enablePersistence = mkOption {

Discussion:
Module provides an option with the description "File containing the shared secret key to use for gossip encryption. [...].". But there is no information about what the shared secret entails. For example, can it be any string or does it have to be a of a specific format? The upstream repo does also not provide this information. <!-- describe your problem --Give a brief sentence describing the format of the shared secret that needs to be stored in that file. E.g., "Can contain any string of arbitrary length" (assuming that's the case). <!-- make sure this issue is not redundant or obsolete --- [X] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [X] checked [open documentation issues] for possible duplicates [X] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]:
Change:
owner = "swoole"; repo = "swoole-src"; rev = "v${version}"; <del> sha256 = "sha256-xadseYMbA+llzTf9JFIitJK2iR0dN8vAjv3n9/e7FGs="; </del> <ins> hash = "sha256-WTsntvauiooj081mOoFcK6CVpnCCR/cEQtJbsOIJ/wo="; </ins> }; buildInputs = [ pcre2 ] ++ lib.optionals (!stdenv.isDarwin) [ valgrind ]; <del> doCheck = true; checkTarget = "tests"; </del> <ins> # tests require internet access doCheck = false; </ins> <del> meta = with lib; { </del> <ins> meta = { </ins> changelog = "https://github.com/swoole/swoole-src/releases/tag/v${version}"; description = "Coroutine-based concurrency library for PHP"; <del> license = licenses.asl20; homepage = "https://www.swoole.co.uk/"; maintainers = teams.php.members; </del> <ins> homepage = "https://www.swoole.com"; license = lib.licenses.asl20; maintainers = lib.teams.php.members; </ins> }; }

Discussion:
Package name: Latest released version: 5.1.1 <!-- Search your package here: --- Current version on the unstable channel: 5.0.3 Current version on the stable/release channel: 5.0.3 <!-- 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]:
Version 5.1.0 fixed compatibility of this extension with PHP 8.3, so the current version 5.0.3 is unusable with PHP 8.3. It outputs these build warnings/errors
Could you please provide the PR to update this? I think it's a matter of changing 2 lines. Actually, creating the PR would have been faster than creating this issue :)
Change:
{ buildDunePackage <ins> , lib , stdenv </ins> , dune-configurator , eio , fmt

Discussion:
Steps to reproduce the behavior: on x8664-darwin Package is a dependency of . Builds fine on linux and aarch64-darwin, just fails on x86_64-darwin. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
if you submit a patch, I will review it, but I don’t own any Darwin hardware to test…
Pinging to see if anyone can help on this issue as it's outside my area of expertise. Otherwise will mark which depends on this as broken for darwin x86_64. Many thanks!
Can test later, but it looks like there is a workaround for this exact error at
Thanks. I tried that flag earlier, which turns the error into a warning and allows to build (with warnings). But then when I try and build which depends on this I get linker errors,
and were in 11.0. It should use to override the stdenv to use the 11.0 SDK with an 11.0 deployment target. Edit: It uses , so probably something like (untested):
Many thanks, that worked! Much appreciated.

nix shell nixpkgs#docfd Wanted to try out but it failed to build. I noticed the package is not on the . Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi thanks for the report. I currently have a PR for version 4.0.0, but this same build error occurs there too, so it's unrelated to version. Strangely docfd builds fine on aarch64-darwin. The problem is with x8664-darwin, and specifically with the ocaml dependency which fails to build as your error message shows. I'm going to open an issue for that an ping the maintainer.
Change:
<del> { lib, stdenv, fetchFromGitHub, meson, ninja, pkg-config </del> <ins> { lib, stdenv, fetchFromGitHub, meson, ninja, pkg-config, wrapGAppsNoGuiHook, gobject-introspection </ins> , glib, systemd, udev, libevdev, gitMinimal, check, valgrind, swig, python3 , json-glib, libunistring }:

Discussion:
it's impossible to use due to an import error: Steps to reproduce the behavior: to run eg ratbagctl "shows something". (i.e. current mouse hardware/mapping etc.) (no gui, cli only) I (may) need because it has infos/options that are not yet fully implemented in Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:

When trying to launch whipper it instead fails with the following trace: Steps to reproduce the behavior: or any equivalent way of running the whipper program Clearly, I expect the program to execute without an error. I bisected the error and the bug was introduced in which bumped . <!-- 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]:
Note: Adding to double-wraps all executables, but allows to run successfully.
Also no double-wrapping.

As title says, openrazer-daemon no longer work after update. Steps to reproduce the behavior: system -daemon fail to start. Openrazer-daemon start on boot. If applicable, add screenshots to help explain your problem. Manually calling openrazer-daemon -Fv print me this: <!-- 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]:
overlay fix for anyone who have this issue.
This overlay fix worked for me, thank you!
Change:
# https://github.com/snapframework/xmlhtml/pull/37 xmlhtml = doJailbreak super.xmlhtml; <ins> # https://github.com/NixOS/nixpkgs/issues/46467 safe-money-aeson = super.safe-money-aeson.override { safe-money = self.safe-money_0_7; }; safe-money-store = super.safe-money-store.override { safe-money = self.safe-money_0_7; }; safe-money-cereal = super.safe-money-cereal.override { safe-money = self.safe-money_0_7; }; safe-money-serialise = super.safe-money-serialise.override { safe-money = self.safe-money_0_7; }; safe-money-xmlbf = super.safe-money-xmlbf.override { safe-money = self.safe-money_0_7; }; </ins> } // import ./configuration-tensorflow.nix {inherit pkgs haskellLib;} self super

Discussion:
In commit was to the hackage package set, which splits up into However, instead of updating the hash of the original derivation, a new derivation was introduced named and all the packages now wrongly depend on instead of , breaking the builds. I'm not very familiar with the whole tooling, so I'm wonderng why it created a new package instead of updating the existing one? And how would I make update the original package, instead of creating a new derivation name? CC This is currently blocking
I think I found out why. It's because of this line. if I just change that file, will it work as expected again?
isn't in any Stackage LTS snapshot yet. so another option we could choose is to remove the packages for now.
The whole package set is based on some Stackage LTS the 0.6 version remains the default and the 0.7 version is opt-in. The way to fix this is to modify and add something like
Change:
wxGTK31-gtk2 = wxGTK31.override { withGtk2 = true; }; wxGTK31-gtk3 = wxGTK31.override { withGtk2 = false; }; <ins> wxGTK32 = callPackage ../development/libraries/wxwidgets/wxGTK32.nix { inherit (darwin.stubs) setfile; inherit (darwin.apple_sdk.frameworks) AGL Carbon Cocoa Kernel QTKit AVFoundation AVKit WebKit; }; </ins> wxSVG = callPackage ../development/libraries/wxSVG { wxGTK = wxGTK30-gtk3; inherit (darwin.apple_sdk.frameworks) Cocoa;

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: 3.1.5 desired version: 3.2.1 Tried packaging wxPython 4.2.0 and it seems to require wxGTk 3.2, because it is missing some header files. <!-- 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.
created a to add wxgtk32
Change:
, darwin , asciidoctor <ins> , botan2 </ins> , curl <del> , glibcLocales </del> , libXi , libXtst , libargon2 <del> , libgcrypt , libgpg-error , libsodium , libyubikey </del> <ins> , libusb1 , minizip , pcsclite </ins> , pkg-config , qrencode , qtbase , qtmacextras , qtsvg , qtx11extras <del> , quazip </del> , readline , wrapGAppsHook , wrapQtAppsHook <del> , yubikey-personalization </del> , zlib , withKeePassBrowser ? true , withKeePassKeeShare ? true <del> , withKeePassKeeShareSecure ? true </del> , withKeePassSSHAgent ? true , withKeePassNetworking ? true , withKeePassTouchID ? true <ins> , withKeePassYubiKey ? true </ins> , withKeePassFDOSecrets ? true , nixosTests

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: keepassxc <!-- 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: 2.6.6 desired version: 2.7.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.
There's a PR now:
Thanks for the information
Change:
elmPackages = (import ./packages/elm-srcs.nix); versionsDat = ./versions.dat; }; <ins> patches = [ (fetchpatch { url = "https://github.com/elm/compiler/pull/1886/commits/39d86a735e28da514be185d4c3256142c37c2a8a.patch"; sha256 = "0nni5qx1523rjz1ja42z6z9pijxvi3fgbw1dhq5qi11mh1nb9ay7"; }) ]; </ins> buildTools = drv.buildTools or [] ++ [ makeWrapper ]; jailbreak = true; postInstall = ''

Discussion:
An update of zip-archive package from 0.3.3 to 0.4 in is causing a runtime error in elm compiler (). It would be good to set the elm's dependency on zip-archive to version < 0.4 until this gets fixed.
probably best to patch it
I think fixes it, will try to find more time to test tomorrow morning.
Shoot, I forgot all about this -- I did confirm that commit fixes it, I will clean up and open a PR soon.
Change:
mimetic = callPackage ../development/libraries/mimetic { }; <del> minetime = callPackage ../applications/office/minetime { }; </del> minio-client = callPackage ../tools/networking/minio-client { }; minio-certgen = callPackage ../tools/security/minio-certgen { };

Discussion:
is "no longer maintained" or distributed, and the releases are unavailable: <!-- 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. Maintainer information:
A closed source substituting another one? Well, it can be fixed by aliasing them to a failure.
Change:
<ins> { lib, fetchurl }: let pname = "open-fonts"; version = "0.7.0"; in fetchurl { name = "${pname}-${version}"; url = "https://github.com/kiwi0fruit/open-fonts/releases/download/${version}/open-fonts.tar.xz"; downloadToTemp = true; recursiveHash = true; sha256 = "sha256-bSP9Flotoo3E5vRU3eKOUAPD2fmkWseWYWG4y0S07+4="; postFetch = '' tar xf $downloadedFile mkdir -p $out/share/fonts/truetype install open-fonts/*.ttf $out/share/fonts/truetype ''; meta = with lib; { description = "A collection of beautiful free and open source fonts"; homepage = "https://github.com/kiwi0fruit/open-fonts"; license = licenses.mit; platforms = platforms.all; maintainers = with maintainers; [ fortuneteller2k ]; }; } </ins>

Discussion:
Project description Italic in Roboto Mono has different width so the Robotization Mono fork is simply a renamed monospacified version of Roboto Mono. Metadata homepage URL: source URL: license: mit platforms: multi-platform