jiebi/CodeConvo huggingface dataset:
Change:
"--with-ksba-prefix=${libksba.dev}" "--with-npth-prefix=${npth}" ] ++ lib.optional guiSupport "--with-pinentry-pgm=${pinentry}/${pinentryBinaryPath}" <del> ++ lib.optional withTpm2Tss "--with-tss=intel"; </del> <ins> ++ lib.optional withTpm2Tss "--with-tss=intel" ++ lib.optional stdenv.isDarwin "--disable-ccid-driver"; </ins> postInstall = if enableMinimal then '' rm -r $out/{libexec,sbin,share}

Discussion:
gnupg worked fine on 2.2.x; pinned nixpkgs-unstable to on my flake. Steps to reproduce the behavior: gnupg from current nixpkgs-unstable, e.g rev & the usual it break: When signing something, you should get pinentry asking you to insert the smartcard - re-plugging has no effect. & signing work etc. If applicable, add screenshots to help explain your problem. <details<summarygpg 2.3.x --version output</summary</details<details<summarygpg 2.2.x --version output</summary</details<!-- 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.
Adding to fixes smart card support.
Had to do this too. For anyone else finding this:
your fix worked for me. Thank you.
it seems that this has been fixed by . Feel free to reopen if not.
FYI issue was actually not about that error message (and its . However,  provided a fix for described smartcard support. I am still unsure why builtin CCID driver fails to handle smartcards now. This issue should stay open for further investigation.
Sorry for the misunderstanding.
This is still an issue for me with gpg 2.3.3. The line in workaround does work for me to get working, but it breaks commands (eg, ). I this snippet to remove the file and reload before invocations and put it back after. If there's more contents in it will not get recreated, so be wary of that if this snippet is used. It feels very hacky but I couldn't find a better way to get both and working at the same time.
You're probably missing udev rules or whatever the mac equivalent is. I covered this and provided lots of various working/non-working configurations, with/without "disable-ccid" when I did the gpg23 PR.
See: .
I'm facing this problem with gpg 2.3.7 on Darwin, and in doesn't fix it. After downgrading to 2.3.6 it works again (only with though).

On 2.3.7, with the card does light up when I run , but then I get: Without , the card doesn't even light up (and output is the same).
I don't think this new issue is related to . I'm on Linux and works without issues (I don't have ), however when upgrading to it is broken. I don't get any errors/warnings when running . But the card is not properly recognized: 2.3.6 2.3.7 Edit, link other related issue:
This is the upstream bug in GPG:
Change:
{ config, pkgs, lib, ... }: let <del> inherit (lib) any boolToString concatStringsSep isBool isString literalExpression mapAttrsToList mkDefault mkEnableOption mkIf mkOption optionalAttrs types; </del> <ins> inherit (lib) any boolToString concatStringsSep isBool isString mapAttrsToList mkDefault mkEnableOption mkIf mkMerge mkOption optionalAttrs types; </ins> package = pkgs.dolibarr.override { inherit (cfg) stateDir; }; cfg = config.services.dolibarr; <del> vhostCfg = config.services.nginx.virtualHosts."${cfg.domain}"; </del> <ins> vhostCfg = lib.optionalAttr (cfg.nginx != null) config.services.nginx.virtualHosts."${cfg.domain}"; </ins> mkConfigFile = filename: settings: let

Discussion:
I would like to use the dolibarr module without nginx. I plan to use caddy instead. In my NixOS configuration, I have . All the nginx-related settings in the dolibarr module are ignored if which is good. However, this line is not: I get the following output: This happens with simply adding to my config.
Opened for the fix, as I do not use any other web server beyond NGINX, I have no plan to maintain advanced integrations of other web servers, if you are interested into this, I will need another co-maintainer :).
Change:
tfswitch = callPackage ../applications/networking/cluster/tfswitch { }; <ins> tfupdate = callPackage ../applications/networking/cluster/tfupdate { }; </ins> tgswitch = callPackage ../applications/networking/cluster/tgswitch { }; tilt = callPackage ../applications/networking/cluster/tilt { };

Discussion:
Project description Update version constraints in your Terraform configurations Metadata homepage URL: source URL: license: mit platforms: darwinarm64, linuxarm64, windows_arm64 Release page: Copied install info from readme: If you are a macOS user, you can install via either or : Download the latest compiled binaries and put it anywhere in your executable path. If you have Go 1.19+ development environment:
Change:
unwrapped = stdenv.mkDerivation rec { pname = "knot-resolver"; <del> version = "5.4.3"; </del> <ins> version = "5.4.4"; </ins> src = fetchurl { url = "https://secure.nic.cz/files/knot-resolver/${pname}-${version}.tar.xz"; <del> sha256 = "488729eb93190336b6bca10de0d78ecb7919f77fcab105debc0a644aa7d0a506"; </del> <ins> sha256 = "588964319e943679d391cc9c886d40ef858ecd9b33ae160023b4e2b5182b2cea"; </ins> }; outputs = [ "out" "dev" ]; <del> patches = [ (fetchpatch { # https://gitlab.nic.cz/knot/knot-resolver/-/merge_requests/1237 name = "console.aws.amazon.com-fix.patch"; url = "https://gitlab.nic.cz/knot/knot-resolver/-/commit/f4dabfbec9273703.diff"; sha256 = "3J+FDwNQ6CqIGo9pSzhrQZlHX99vXFDpPOBpwpCnOxs="; }) ]; </del> # Path fixups for the NixOS service. postPatch = '' patch meson.build <<EOF

Discussion:
However, the following input is is rejected as "*: incorrect address specification": I expected kresd to listen on fe80::1 on port 53 on the ofborg interface, as the documentation suggests should be possible. I don't mind that it is impossible, but the documentation for this option isn't correct anymore. nixos-unstable-small, rev
Well, it no longer uses systemd sockets anymore, and instead there are a few in-nix regexps that convert them. It might not be perfect. Either way, the interface spec should surely be part of the IPv6 already, i.e. &ndash; and I think that should work (the generated lua config looks OK).
Ah, I see that systemd is weird here, at least in docs. So I don't know what we'll do with it. Either shuffle it in the in-nix regexps or document as a deviation, I suppose.
Change:
managesieve = callPackage ../development/python-modules/managesieve { }; <ins> mando = callPackage ../development/python-modules/mando { }; </ins> mandown = callPackage ../development/python-modules/mandown { }; manhole = callPackage ../development/python-modules/manhole { };

Discussion:
Project description Compute metrics on Python code (e.g. cyclomatic complexity) Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin
Change:
<ins> diff --git a/CMakeLists.txt b/CMakeLists.txt index 7065538..1946574 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -19,14 +19,8 @@ set(EXECUTABLE_OUTPUT_PATH "${PROJECT_BINARY_DIR}") set(VS_STARTUP_PROJECT ${EXECUTABLE_NAME}) # Configure options -if (WIN32 OR APPLE) -  set(QT_VERSION "6") -else () -  set(QT_VERSION "5" CACHE STRING "Qt major version to use (5 or 6).") -  if (NOT (QT_VERSION STREQUAL "5" OR QT_VERSION STREQUAL "6")) -    message(FATAL_ERROR "Unsupported Qt version '${QT_VERSION}'. Only 5 and 6 are supported") -  endif () -endif () +set(QT_VERSION "6") + if (APPLE) option(DMG "Make deployable DMG" OFF) endif () </ins>

Discussion:
Project description From the project GitHub: Easy Audio Sync is an audio library syncing and conversion utility. The intended use is syncing an audio library with many lossless files to a mobile device with limited storage. The program's design is inspired by the utility. It supports folder-based source to destination syncing, with audio transcoding capability, and is GUI-based instead of CLI-based. Metadata homepage URL: source URL: license: Public Domain (Unlicense) platforms: Linux, Windows, and macOS Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
buildPythonPackage rec { pname = "qiling"; <del> version = "1.4.1"; </del> <ins> version = "1.4.2"; </ins> format = "setuptools"; <ins> disabled = pythonOlder "3.7"; </ins> src = fetchPypi { inherit pname version; <del> sha256 = "e72dc5856cbda975f962ddf063063a32bd6c3b825f75e0795e94ba6840a7d45f"; </del> <ins> hash = "sha256-myUGzNP4bf90d2gY5ZlYbVlTG640dj/Qha8/aMydvuw="; </ins> }; propagatedBuildInputs = [

Discussion:
seems to be missing a dependency which was introduced in 1.4.1 (the current version in nixpkgs, 1.4.2 has already been released, so probably should be updated). The build fails: I am puzzled how this slipped past the checks. Steps to reproduce the behavior: A clear and concise description of what you expected to happen. I am building on Fedora. system: multi-user?: sandbox: version: channels(): nixpkgs:
Change:
hash = "sha256-WeAzlC1yT+0nPSuB278z8T0XvPjbre051f/Rva5ujAk="; }; <ins> nativeBuildInputs = [ hatchling ]; </ins> propagatedBuildInputs = [ requests ]; nativeCheckInputs = [ pytestCheckHook ]; postPatch = '' <del> substituteInPlace setup.cfg  --replace "--cov=kiss_headers --doctest-modules --cov-report=term-missing -rxXs" "--doctest-modules -rxXs" </del> <ins> substituteInPlace pyproject.toml  --replace-fail "--cov=kiss_headers --doctest-modules --cov-report=term-missing -rxXs" "--doctest-modules -rxXs" </ins> ''; disabledTestPaths = [

Discussion:
Steps to reproduce the behavior: in nixos-unstable chanale <!-- 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]:
According to the logs, the component that is not building is . This is being fixed on
Can confirm that builds and launches successfully after the fix to is applied.
Change:
twinkle = qt5.callPackage ../applications/networking/instant-messengers/twinkle { }; <ins> terminal-stocks = callPackage ../applications/misc/terminal-stocks { }; </ins> terminal-typeracer = callPackage ../applications/misc/terminal-typeracer { inherit (darwin.apple_sdk.frameworks) Security; };

Discussion:
Project description Fetch stock information, market summary right in your terminal. Metadata homepage URL: source URL: license: mit linux
PR made: .
Change:
}; postInstall = '' <ins> unlink $out/libexec/vieb/deps/vieb/node_modules ln -s $out/libexec/vieb/node_modules $out/libexec/vieb/deps/vieb/node_modules find $out/libexec/vieb/node_modules/7zip-bin -name 7za -exec ln -s -f ${p7zip}/bin/7za {} ';' </ins> install -Dm0644 {${desktopItem},$out}/share/applications/vieb.desktop pushd $out/libexec/vieb/node_modules/vieb/app/img/icons

Discussion:
The Vieb web browser is supposed to have () support for installing Chrome extensions (such as Dark Reader). When I try to do this, it gives me an error. Steps to reproduce the behavior: Vieb via nixpkgs. to open Dark Reader extension. to try to install extension. This leads to an error. It should install the extension. Please run and paste the result. Maintainer information:
I did some digging around and found that problem happens when Vieb tries to unzip the extension. One of Vieb's extensions is the package, which comes with precompiled binaries that aren't patched: Directly executing this executable leads to an error. I tried patching the nix file myself: After this, the 7z binary build by the patched derivation was able to execute without problems, but I was still unable to install any extensions in Vieb.
Please submit a PR.
to be clear, this still does not work even after that patch. But I will submit a PR and go from there.
Change:
librealsenseWithCuda = callPackage ../development/libraries/librealsense { cudaSupport = true; <ins> # librealsenseWithCuda doesn't build on gcc11. CUDA 11.3 is the last version # to use pre-gcc11, in particular gcc9. cudaPackages = cudaPackages_11_3; stdenv = gcc9Stdenv; </ins> }; librealsenseWithoutCuda = callPackage ../development/libraries/librealsense {

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking python3Packages.jaxlibWithCuda. python3Packages.jaxlibWithCuda maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
I'm observing this error with many more packages (e.g. ). I'd expect it would've been introduced introduced elsewhere than in openscad commit?
I just bisected a similar bug (dm-tree failure) to
I'm not sure what to do about this... It seems like the kinda of thing people won't want to rollback, but it's also breaking a loooooot of things. cc
Can't reproduce, no build failure on my end. Hydra also has a cached built copy.
I think it's only the version that's failing
I'll see what happens if we bump in
Hopefully it is only a gcc mismatch issue.
RE: Ok, actually tensorflow and jaxlib are still pinned to and override to , so they're all pulling in . Idk about unpinning tensorflow, but I'm pretty sure we should be safe to switch jaxlib to the default cuda packages
As far as the error message goes it seems like it wants LLVM clang rather than GNU g++.
That's a good point. I think we should unpin jax from needing to use the same versions as TF. This seemed like a good idea at the time (I advocated for it), but it's proven to be a PITA since then. TF's version constraints are just so outdated. would you be opposed? I suspect that this was caused by the GCC bump, but I'm not 100% certain yet. I'm currently bisecting a different failure, but once that's done I'll try to debug this further!
Unpinning jax from the old cudaPackages and bumping the new cuda packages to gcc11 I get no more missing symbols, but I fail with:
Thanks for taking a stab at that Just to confirm: is that error within glibc or is it indicating a misuse of glibc APIs?
would you mind the derivation that you've been using? I'm curious to reproduce
good catch, the error was from: I was trying to build with updating and removing for jaxlib and jaxlib-build
Created an issue upstream:
Change:
in fetchurl { url = "https://download.zotero.org/client/beta/${escapedVersion}/Zotero-${escapedVersion}_linux-x86_64.tar.bz2"; <del> hash = "sha256-wqew12/Icv4XS+IJRVcf1Rh/ipqBhe8QGkP8ErfS4J0="; </del> <ins> hash = "sha256-pZsmS4gKCT8UAjz9IJg5C7n4kk7bWT/7H5ONF20CzPM="; </ins> }; dontPatchELF = true;

Discussion:
Package name: zotero-beta Latest released version: 7.0.0-111 <!-- Search your package here: --- Current version on the unstable channel: 7.0.0-83 Current version on the stable/release channel: 7.0.0-83 <!-- 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]:
Hi I wanted to test out the latest beta so did a PR as I was using it anyway. Not sure who the correct person to tag in this is.
Change:
}; description = lib.mdDoc "Set configuration for system-wide bluetooth (/etc/bluetooth/main.conf)."; }; <ins> input = mkOption { type = cfgFmt.type; default = { }; example = { General = { IdleTimeout = 30; ClassicBondedOnly = true; }; }; description = lib.mdDoc "Set configuration for the input service (/etc/bluetooth/input.conf)."; }; network = mkOption { type = cfgFmt.type; default = { }; example = { General = { DisableSecurity = true; }; }; description = lib.mdDoc "Set configuration for the network service (/etc/bluetooth/network.conf)."; }; </ins> }; };

Discussion:
BlueZ is currently setup to read auxiliary config files (i.e. , ) from its package directory, which makes it hard to write to them properly on a NixOS system. These configuration files are the only way to configure certain behaviours of , such as in , which is an important setting for device power saving. It's not possible to specify these options in . And it's not possible to specify the path of at runtime. Steps to reproduce the behavior: a file, either manually or from a nix configuration. with . hasn't loaded any settings from . (It's easy to test if you fill with trash since it should log: ). It should be possible to configure all aspects of in the same way. BlueZ loads from a hardcoded path: The same is try for : The define is set to the package directory by default. For a symlink is setup, however no such link is setup for or : I wonder if a fix for this might be adding to the of BlueZ? There's no maintainer listed in , so I'm pinging the people who last touched it :) , Please run and paste the result.
I feel like this could be easily fixed rather in the by adding 2 more options for and under (?) Let me see if I can carve out some time later this week..
Fixed in
Change:
enable = true; configDir = "/var/db/slapd.d"; }; <ins> users.ldap = ldapClientConfig; </ins> }; testScript = let

Discussion:
The system-wide LDAP client configuration in is ignored by Openldap client programs. Steps to reproduce the behavior: settings into via or any other Openldap client Openldap client programs should obey the system-wide configuration file in . strace shows it's reading the example configuration from the package instead: Since commit the openldap package no longer passes to configure, it only passes to make instead. Please run and paste the result.
It seems a bit dodgy, but this might be a solution: plus corresponding changes to all the packages and tests that refer to . I'm just rebuilding a gazillion packages on my system from source, so I can check if that works properly...
you probably meant to ping and instead
Oops, sorry about that. I forgot that the maintainer handles listed in the package do not necessarily correspond to their Github usernames.
I realised that changing is probably unwise. Not only does it break some other packages (like python-ldap) and some Nixos tests, it will also break any users who have configured slapd to refer to the schemas under , as I myself have: And changing is not necessary to fix the bug anyway. It seems that the approach of passing differently in compile and install works. I'll send a PR for it.
Change:
<del> { fetchFromGitHub, lib, gobject-introspection, gtk3, python3Packages }: </del> <ins> { fetchFromGitHub , lib , gobject-introspection , gtk3 , python3Packages , wrapGAppsHook , gdk-pixbuf , libappindicator , librsvg }: </ins> # Although we copy in the udev rules here, you probably just want to use # logitech-udev-rules instead of adding this to services.udev.packages on NixOS

Discussion:
Describe the bug Solaar crashes with the following error: Notify maintainers
thanks for report, I can reproduce it. I'll try to find some time to investigate, it looks like it cannot find an icon?
can you elaborate how you run this? I was able to reproduce the issue with , but when I install in the system with it works. It's something with xdg and icons discovery and I wasn't able to fix this, probably some specific XDG variable or desktop environment variable must be set to properly discover icons.
Yes, it seems like it was indeed the problem with icons. Installing KDE fixes the issue even without using it.
The wiki has a small section on this: But on a side note The package is out of date
thanks. Locally I updated to latest version and it didn't change much. If I have a sec I'll try debug little more.
Same error, here's the output i get when running I'm running i3 as my desktop environment
same problem with + . how you investigation progress?
Change:
# - use MakeAvailable instead of the low-level Populate, # - use Eigen3::Eigen as the target name (as declared by libeigen/eigen). ./0001-eigen-allow-dependency-injection.patch <ins> ] ++ lib.optionals cudaSupport [ # We apply the referenced 1064.patch ourselves to our nix dependency. #  FIND_PACKAGE_ARGS for CUDA was added in https://github.com/microsoft/onnxruntime/commit/87744e5 so it might be possible to delete this patch after upgrading to 1.17.0 ./nvcc-gsl.patch </ins> ]; nativeBuildInputs = [

Discussion:
Project description ONNX Runtime: cross-platform, high performance ML inferencing and training accelerator . Onnxruntime is already packaged. I would like to have the version with gpu support to be able to package obs-backgroundremoval with gpu support (). Related: Metadata homepage URL: source URL: license: mit platforms: linux
Obs-backgroundremoval includes tensorrtproviderfactory.h to build
need it, too
Is it possible to add gpu support to the obs-backgroundremoval as this issue is closed?
It may be possible. If anyone wants to open a PR for that, please base it on the current update PR
Change:
"--port=${toString cfg.port}" "--configpath=${cfg.configpath}" "--scanconfig=${cfg.scanconfig}" <ins> "--log=all:${cfg.logs.all}" </ins> "--log=main:${cfg.logs.main}" "--log=network:${cfg.logs.network}" "--log=bus:${cfg.logs.bus}" "--log=update:${cfg.logs.update}" "--log=other:${cfg.logs.other}" <del> "--log=all:${cfg.logs.all}" </del> ] ++ lib.optionals cfg.readonly [ "--readonly" ] ++ lib.optionals cfg.mqtt.enable [

Discussion:
logging config doesn't seem to be applied to the invocation of Steps to reproduce the behavior: the following : info-level logs coming through (despite the config) No info-level logs appear in the service log, config is applied. I suspect the final is overriding all previous log configs, going off how and this appears to then . Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I see this more as an issue with the . Their are clear, it should work: I do see your issue and I'm wondering if it would be better to leave out the directive (since we specified all others).
Thanks yes I'm thinking the final directive is overriding all the others, so I guess it is a quirk of the upstream. I like the idea of leaving it out, or we could have it at the start of the , which will allow configuration of an level, with the ability to override it for specific areas, as subsequent arguments. Wdyt? (although having said that, I guess we always pass the other areas, so perhaps dropping is simpler, leaving the nixos config to default each area) I'm happy to make the PR if you'd be ok with either of those approaches
go ahead and make the PR, you can tag me as reviewer! Thx a lot.
Change:
NET_FC             = yes; # Fibre Channel driver support # GPIO on Intel Bay Trail, for some Chromebook internal eMMC disks PINCTRL_BAYTRAIL   = yes; <ins> # GPIO for Braswell and Cherryview devices # Needs to be built-in to for integrated keyboards to function properly PINCTRL_CHERRYVIEW = yes; </ins> # 8 is default. Modern gpt tables on eMMC may go far beyond 8. MMC_BLOCK_MINORS   = freeform "32";

Discussion:
The integrated keyboard on my Acer Chromebook R11 does not work with NixOS' Linux kernel. Steps to reproduce the behavior: NixOS on an Acer Chromebook R11, from either a live USB or installation. The integrated keyboard should work. From dmesg: After looking around, I think this is probably because CONFIGPINCTRLCHERRYVIEW is built as a kernel module instead of being built into the kernel: I would modify my kernel configuration and test this, but the Chromebook is too underpowered to compile the kernel. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
From , I think that it needs to be built in. I've verified that doesn't resolve the issue.
I assumed it was stuck in , I don't see why I assumed this. I guess enabling it is okay... Though I don't like how this seems to be an issue that is becoming more and more common, drivers either working only built-in, or only as modules, due to misbehaviour. Enabling it would be done . With the reasoning behind enabling as built-in. , no need to gate behind specific kernel versions I suppose.