jiebi/CodeConvo huggingface dataset:
Change:
cups-kyodialog3 = cups-kyodialog; # Added 2022-11-12 cupsBjnp = throw "'cupsBjnp' has been renamed to/replaced by 'cups-bjnp'"; # Converted to throw 2022-02-22 cups_filters = throw "'cups_filters' has been renamed to/replaced by 'cups-filters'"; # Converted to throw 2022-02-22 <ins> curl-impersonate-bin = throw "'curl-impersonate-bin' has been replaced by 'curl-impersonate'"; # Added 2022-10-08 </ins> curlcpp = throw "curlcpp has been removed, no active maintainers and no usage within nixpkgs"; # Added 2022-05-10 curaByDagoma = throw "curaByDagoma has been removed from nixpkgs, because it was unmaintained and dependent on python2 packages"; # Added 2022-01-12 curaLulzbot = throw "curaLulzbot has been removed due to insufficient upstream support for a modern dependency chain"; # Added 2021-10-23

Discussion:
Project description is like curl, but doesn't get you blocked by cloudflare and other WAPs that insist you have the TLS fingerprint of a web browser. Metadata homepage URL: source URL: license: MIT platforms: linux
the build process produces a separate 'Chrome' and 'Firefox' impersonation binary
I started packaging the firefox variant of curl-impersonate in , but it has unresolved issues, including: missing the curl-impersonate wrapper scripts; PATH conflicts with ; disabled tests; missing shell completions; possible issues with getting an HTTP response from some sites including But it does sort of work and may be useful as a starting point. (Note that I have not checked the TLS fingerprint.)
I've opened which should add a fully working build from source of curl-impersonate (with both firefox and chrome variants)
Change:
<ins> diff --git a/mruby/tasks/toolchains/gcc.rake b/mruby/tasks/toolchains/gcc.rake index f370c0ab..e5ab9f60 100644 --- a/mruby/tasks/toolchains/gcc.rake +++ b/mruby/tasks/toolchains/gcc.rake @@ -22,7 +22,7 @@ MRuby::Toolchain.new(:gcc) do |conf, _params| end conf.linker do |linker| -    linker.command = ENV['LD'] || 'gcc' +    linker.command = 'gcc' linker.flags = [ENV['LDFLAGS'] || %w()] linker.libraries = %w(m) linker.library_paths = [] </ins>

Discussion:
Project description ! Zyn-Fusion is the new GUI front-end for . I tried to modify zynaddsubfx to use the package from (which is said to have included zyn-fusion) with no avail. Metadata homepage URL: source URL: license: platforms: linux cc zynaddsubfx maintainers
I marked this as stale due to inactivity. &rarr;
Change:
# If requested enable modesetting via kernel parameter. boot.kernelParams = optional (offloadCfg.enable || cfg.modesetting.enable) "nvidia-drm.modeset=1" ++ optional cfg.powerManagement.enable "nvidia.NVreg_PreserveVideoMemoryAllocations=1" <del> ++ optional cfg.open "nvidia.NVreg_OpenRmEnableUnsupportedGpus=1"; </del> <ins> ++ optional cfg.open "nvidia.NVreg_OpenRmEnableUnsupportedGpus=1" # proprietary driver is not compiled with support for X86_KERNEL_IBT ++ optional (!cfg.open && config.boot.kernelPackages.kernel.kernelAtLeast "6.2") "ibt=off"; </ins> services.udev.extraRules = ''

Discussion:
Steps to reproduce the behavior: package is marked as broken I marked this package as broken starting with linux 6.2 because enables by default. The binary blobs included with the nvidia driver are not compiled with support for IBT and nvidia hasn't been able to update their internal toolchain to support it at this point. Rather than leave it broken, we should probably check if the driver is built using the proprietary blobs and add the kernel parameter starting with linux 6.2. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.
Change:
<ins> { config, lib, ... }: with lib; let cfg = config.programs.fuse; in { meta.maintainers = with maintainers; [ primeos ]; options.programs.fuse = { mountMax = mkOption { # In the C code it's an "int" (i.e. signed and at least 16 bit), but # negative numbers obviously make no sense: type = types.ints.between 0 32767; # 2^15 - 1 default = 1000; description = '' Set the maximum number of FUSE mounts allowed to non-root users. ''; }; userAllowOther = mkOption { type = types.bool; default = false; description = '' Allow non-root users to specify the allow_other or allow_root mount options, see mount.fuse3(8). ''; }; }; config =  { environment.etc."fuse.conf".text = '' ${optionalString (!cfg.userAllowOther) "#"}user_allow_other mount_max = ${toString cfg.mountMax} ''; }; } </ins>

Discussion:
Right now ipfs module puts in a into However if other modules also make use of fuse, how would these settings be resolved? Should there be an option for fuse settings, that all modules make use of, and can alert errors if there are conflicting entries? We need to have a centralised option for configuring the usable by all services like IPFS or SSHFS or S3FS... etc.
Sounds good. (But perhaps also have an "extraConfig" option as escape hatch.)
Was there any PR being open relating to this issue? Maybe rephrasing an issue to sound more like a feature request then a question, would be better. Also it wouldn't hurt bringing this up on the mailing list.
No PR that I know of. But yea I think there should be a new option in NixOS for this.
Do I understand correctly that there are only two options that could be specified in ? ( and )
Yeah, I can't get fuse to read my file. Is there a workaround or any progress on a final solution? I'm trying to get fuse to respect , but I can't find any way at the moment.
See The fix has been to and .
Is this issue finally resolved? Is there nixos options to set this config?
Not yet, but I've just created a PR () as it seems to become quite relevant.
Change:
multiPkgs = pkgs: with pkgs; [ # Common libsndfile libtheora libogg libvorbis libopus libGLU libpcap libpulseaudio <del> libao libusb libevdev libudev libgcrypt libxml2 libusb libpng libmpeg2 libv4l </del> <ins> libao libusb libevdev udev libgcrypt libxml2 libusb libpng libmpeg2 libv4l </ins> libjpeg libxkbcommon libass libcdio libjack2 libsamplerate libzip libmad libaio libcap libtiff libva libgphoto2 libxslt libtxc_dxtn libsndfile giflib zlib glib alsaLib zziplib bash dbus keyutils zip cabextract freetype unzip coreutils

Discussion:
Describe the bug Seems like some updates to pango broke a few packages Among the broken ones: ettercap (see ) pangox-compat (which anydesk needs) probably a few more To Reproduce Steps to reproduce the behavior: to build ettercap or anydesk from master will fail to build with some pango-related errors Expected behavior It should work Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata system: host os: multi-user?: sandbox: version: channels(maciej): nixpkgs: Maintainer information:
Also remmina is broken But doesn't seem to depend on pango directly, so unsure which dependency actually is broken
Here's an issue for pangox-compat
Lutris is broken too - not an urgent requirement but just making you fine folks aware!
Not sure why Lutris is broken, but Lutris-unwrap is fine.
It's a failure in the dependency chain, in this case .
no longer depends on on its master branch: We should probably switch to that. should not be needed in according to the README in , I suspect it was only there because we did not propagate it until ebassi also suggests switching to HEAD and says we need not worry about ABI changes:
Not having pangox_compat fixed is definitively still an issue. Can this be re-opened?
After , the only program depending on this is anydesk and openmodelica which is broken.
So it breaks anydesk thus either we mark anydesk as broken or we fix that?
Anydesk shouldn't use this deprecated library. Yes, we can mark it as broken.
Change:
inherit (buildPackages) bash; buildlddtree = "${buildPackages.pax-utils}/bin/lddtree"; }}" <del> "-Dgi_cross_use_prebuilt_gi=true" </del> "-Dgi_cross_binary_wrapper=${stdenv.hostPlatform.emulator buildPackages}" <ins> # can't use canExecute, we need prebuilt when cross ] ++ lib.optionals (stdenv.buildPlatform != stdenv.hostPlatform) [ "-Dgi_cross_use_prebuilt_gi=true" </ins> ]; doCheck = !stdenv.isAarch64;

Discussion:
Building on gives us: cc system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Change:
configureFlags = [ <del> "--with-terminfo=$terminfo/share/terminfo" </del> <ins> "--with-terminfo=${placeholder "terminfo"}/share/terminfo" </ins> "--enable-256-color" (enableFeature perlSupport "perl") (enableFeature unicode3Support "unicode3")

Discussion:
... what's doing there? I suppose it doesn't actually cause any problems given that TERMINFO_DIRS is set, but still, it shouldn't be there. Steps to reproduce the behavior: urxvt through nixpkgs () a terminal () your environment variables as above The offending line is clearly I suspect this may have worked at one point in the past, then stdenv's escaping logic was changed? The variable should be set to a directory that actually exists and has the appropriate information in it, or not set at all. I doubt it's relevant, but:
btw arch has a lot of configure options, i wonder if we should add some of them?
I'll take a look, but I suspect most of these are enabled by default.
The only options off by default that we don't enable in Nixpkgs are The first is only useful when developing urxvt, the description for the second says: I'm not sure how useful this is because I use a tiling WM. Anyway, the option is off even in Arch Linux due to a .
Change:
patches = fetchpatch { name = "cheroot-fix-setup-python3.patch"; <del> url = "https://git.archlinux.org/svntogit/community.git/plain/trunk/cheroot-fix-setup-python3.patch?h=packages/python-cheroot"; </del> <ins> url = "https://git.archlinux.org/svntogit/community.git/plain/trunk/cheroot-fix-setup-python3.patch?h=packages/python-cheroot&id=9b33cb0885b3c0d91adeacae23761a4321eb0e64"; </ins> sha256 = "1rlgz0qln536y00mfqlf0i9hz3f53id73wh47cg5q2vcsw1w2bpc"; };

Discussion:
Build The patch URL in pkgs/development/python- should maybe refer to a specific commit?
This URL seems to work to get the old patch, if that's the intention:
Fixed by , assuming the desire is to continue using the old version of the patch.
Change:
assert withPlugin -> builtins.elem hplipArch pluginArches || throw "HPLIP plugin not supported on ${stdenv.hostPlatform.system}"; <del> python3Packages.buildPythonApplication { </del> <ins> python311Packages.buildPythonApplication { </ins> inherit pname version src; format = "other";

Discussion:
Steps to reproduce the behavior: build .#hplip Looks like more fallout from Python 3.12. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
type = types.listOf nonEmptyStr; }; <ins> depends = mkOption { default = [ ]; example = [ "/persist" ]; type = types.listOf nonEmptyWithoutTrailingSlash; description = '' List of paths that should be mounted before this one. This filesystem's <option>device</option> and <option>mountPoint</option> are always checked and do not need to be included explicitly. If a path is added to this list, any other filesystem whose mount point is a parent of the path will be mounted before this filesystem. The paths do not need to actually be the <option>mountPoint</option> of some other filesystem. ''; }; </ins> }; config = {

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:
local oldInterpreterLine local newInterpreterLine <del> [ -e "$dir" ] || return 0 </del> <ins> if [ $# -eq 0 ]; then echo "No arguments supplied to patchShebangs" >0 return 0 fi </ins> local f while IFS= read -r -d $'0' f; do

Discussion:
I have been burned by this several times; and I am not alone: When calling with multiple arguments, we should either patch all of them or print an error. Ignoring arguments silently should be a crime. cc
Change:
paths = rocmLibs ++ [ rocmClang ]; }; <ins> cudaLibs = [ cudaPackages.cuda_cudart cudaPackages.libcublas cudaPackages.cuda_cccl ]; </ins> cudaToolkit = buildEnv { name = "cuda-merged"; <del> paths = [ (lib.getBin (cudaPackages.cuda_nvcc.__spliced.buildHost or cudaPackages.cuda_nvcc)) (lib.getLib cudaPackages.cuda_cudart) </del> <ins> paths = map lib.getLib cudaLibs ++ [ </ins> (lib.getOutput "static" cudaPackages.cuda_cudart) <del> (lib.getLib cudaPackages.libcublas) </del> <ins> (lib.getBin (cudaPackages.cuda_nvcc.__spliced.buildHost or cudaPackages.cuda_nvcc)) </ins> ]; };

Discussion:
Running fails when launching the runner: Steps to reproduce the behavior: with the server a model and observe that it fails Either should contain , or the wrapper should add wherever is to . When starting, also prints this warning: . I have 2x Quadro P5000s, using the closed drivers since open doesn't support them. <!-- 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]:
I'm not actually a maintainer of ollama, but there are three others who should have received the ping. That said, I wonder if this is fixed by
Sorry for the ping, I saw your PR and thought the same thing. I've tried with and without the changes from that PR and it doesn't fix the issue.
This awful hack fixes the issue for me:
I wonder if my change could be resolved by putting in LDLIBRARYPATH. I'll try and do some testing in the next couple days
Change:
}; networking.firewall.checkReversePath = lib.mkDefault "loose"; <del> services.resolved.enable = !(config.networking.networkmanager.enable); </del> <ins> services.resolved.enable = lib.mkIf (!config.networking.networkmanager.enable) true; </ins> environment.systemPackages = [ cfg.package ]; # For the CLI. };

Discussion:
The service module conflicts with manual configurations of when both and are enabled. twingate in services.resolved configurations explicitly: networking.networkmanager: a system rebuild: nixos-rebuild switch. The system should rebuild successfully, with both and enabled, and configured as described. I was encountering dns issues. I am not sure if it was because of this package but specifically was resolving to 0.0.0.0 ; I decided to manually set dns per
Let me fix this up, for now use lib.mkForce.
Change:
# currently present in PATH. Without removing the go_sdk from the marker # file, the hash of it will change anytime the Go derivation changes and # that would lead to impurities in the marker files which would result in <del> # a different sha256 for the fetch phase. </del> <ins> # a different hash for the fetch phase. </ins> rm -rf $bazelOut/external/{go_sdk,@go_sdk.marker} sed -e '/^FILE:@go_sdk.*/d' -i $bazelOut/external/@*.marker

Discussion:
Steps to reproduce the behavior: The builds are also failing on Hydra Please run and paste the result.
Several errors like this locally and in
is not set on the system outside the nix-shell and also does not seem to be set when the bazel command is executed within the nix-build. On the same system, with bazelisk, version 0.23.1 builds from source:
merge introduced a build failure (found via git bisect) which merged this change: Reverting it on master makes it work but also reverts bazel-watcher to an older version. AND only works if the is set. I assume it will not actually call the updated fetch logic at all since it just uses the fetched dependencies from the cache. Maybe can help out fixing it...
:)
The makes it hard to bisect since it will "hide" all fetch affecting changes behind that cached results. Long live fixed output derivations!
I was wrong. The fetchAttrs.sha256 hid that it was, in fact, broken before
I bisected this to the following commit: with this bisect script: Unfortunately, it is a huge merge.
Okay fetching broke when go was unpinned:
Maybe related to
: Could you maybe merge ? It would be appreciated.
Change:
name = "gd"; extraBuildInputs = [ gd ]; }; <del> haru = buildExtension { inherit gawkextlib; name = "haru"; extraBuildInputs = [ libharu ]; }; </del> <ins> # Build has been broken: https://github.com/NixOS/nixpkgs/issues/191072 # haru = buildExtension { #   inherit gawkextlib; #   name = "haru"; #   extraBuildInputs = [ libharu ]; # }; </ins> json = buildExtension { inherit gawkextlib; name = "json";

Discussion:
Steps to reproduce the behavior: -build '<nixpkgs' -A gawk-with-extensions Still fails when I used My current workaround is removing haru from gawkextlib with:
Related: and not yet updated in gawkextlib:
Change:
if line_pattern.match(line) ) <ins> def get_unit_property( self, unit: str, property: str, user: Optional[str] = None, ) -> str: status, lines = self.systemctl( f'--no-pager show "{unit}" --property="{property}"', user, ) if status != 0: raise Exception( f'retrieving systemctl property "{property}" for unit "{unit}"' + ("" if user is None else f' under user "{user}"') + f" failed with exit code {status}" ) invalid_output_message = ( f'systemctl show --property "{property}" "{unit}"' f"produced invalid output: {lines}" ) line_pattern = re.compile(r"^([^=]+)=(.*)$") match = line_pattern.match(lines) assert match is not None, invalid_output_message assert match[1] == property, invalid_output_message return match[2] </ins> def systemctl(self, q: str, user: Optional[str] = None) -> Tuple[int, str]: """ Runs `systemctl` commands with optional support for

Discussion:
The error currently does not even elaborate which unit it's been inquiring about, and overall it looks like the test driver is failing, rather than the service being tested: One can see the same behaviour in e.g. This is far from a minimal example, but it works for me: after () until you observe the driver failing with (the error isn't deterministic) The test work or fail deterministically. Instead of in the driver, a message about the unit should be displayed If applicable, add screenshots to help explain your problem. Add any other context about the problem here. I suspect the systemctl might be running into this branch and then we're not seeing the message, because the driver only captures the stdout: I couldn't confirm though. The SLURM test: Recently edited : <!-- 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.
Possibly a better reproducer: try (or any ). When I run locally/outsdie the VM I observe . It fails pretty consistently inside the VM for me
Change:
inherit lib buildEnv writeShellScriptBin extensionsFromVscodeMarketplace jq; vscodeDefault = vscode; }; <del> in </del> <ins> in </ins> { inherit fetchVsixFromVscodeMarketplace buildVscodeExtension buildVscodeMarketplaceExtension extensionFromVscodeMarketplace

Discussion:
Describe the bug A clear and concise description of what the bug is. the vscode-extensions directory has the structure so should be called with the argument instead of To Reproduce Steps to reproduce the behavior: ... ... ... Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. 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:
<ins> { stdenv, fetchurl, bitwig-studio1, xdg_utils, zenity, ffmpeg }: bitwig-studio1.overrideAttrs (oldAttrs: rec { name = "bitwig-studio-${version}"; version = "2.2.2"; src = fetchurl { url    = "https://downloads.bitwig.com/stable/${version}/bitwig-studio-${version}.deb"; sha256 = "1x4wka32xlygmhdh9rb15s37zh5qjrgap2qk35y34c52lf5aak22"; }; buildInputs = bitwig-studio1.buildInputs ++ [ ffmpeg ]; binPath = stdenv.lib.makeBinPath [ ffmpeg xdg_utils zenity ]; }) </ins>

Discussion:
There is Bitwig1 and Bitwig2. I for example have only a license for Bitwig1. And I will not pay frequently for features I don't use (because I'm not a professional musican). Right now I use the overrideAttrs to install bitwig1, but it would be smarter to provide an older version as well (most likely there will be a bitwig3 someday). I could create a pull-request, just wanted to open a quick discussion first, because I'm new to NixOs and maybe there is already a very smart thing that makes live much simpler, which I'm not aware.
See . I think we shouldn't distribute paid updates for proprietary software under the same attribute without a way to opt out (other than rollback), this heavily breaks reverse compatibility. I think that should point to the latest version, with and pointing to specific major versions. Derivation for 2.x branch may override 1.x, since it has same dependencies and layout, the only difference is additional dependency on :
Change:
, unzip , wrapGAppsHook3 , xorg <ins> , darwin </ins> }: let

Discussion:
Project description <!-- Describe the project a little: --Cypress is one of the most popular e2e testing tools. We already packaged aarch64-linux + x86-64-linux, but not darwin. Binaries for all platforms are available, see =should be easy to do Metadata homepage URL: source URL: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've had a stab at this (with help from Perplexity): Unfortunately, it does not seem to work properly, when I run the built package there's an error stating "this package is broken". I've never packaged something for darwin before, no Idea how to fix this. Happy to take pointers.
Turns out this is a quarantine thing. Apparently there's an option in the setting in the privacy options where you can allow opening these "untrusted" binaries, once done it will show "hey this is broken, do you want to open it" and if you click yes, it opens. I guess I'll send a PR then
PR is up:
Change:
, yt-dlp }: <del> mkKdeDerivation rec { </del> <ins> stdenv.mkDerivation rec { </ins> pname = "haruna"; version = "1.0.2";

Discussion:
retains references to packages, bloating the closure massively. I'd expect to see no such results. If comparing to qt5: n/a Seems related to some wrapping issue. For example: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --All examples above were built against Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Do we need the qt6 plugins for designer?
I achieved the following nix diff-closures with the diff: The patch is not perfect but maybe a starting point?
Maybe a separate output that's not $dev for those plugins?
That change brings the closure from (nominally) 1.05 GiB to 925 MiB. I think the other notably sized dependency would be which appears to add 100+ MiB of its own (as it brings along ), but it's indirectly coming from