jiebi/CodeConvo huggingface dataset:
Change:
[Resolve] ${optionalString (config.networking.nameservers != []) "DNS=${concatStringsSep " " config.networking.nameservers}"} <del> ${optionalString (cfg.fallbackDns != []) </del> <ins> ${optionalString (cfg.fallbackDns != null) </ins> "FallbackDNS=${concatStringsSep " " cfg.fallbackDns}"} ${optionalString (cfg.domains != []) "Domains=${concatStringsSep " " cfg.domains}"}

Discussion:
is empty as a default value, and has the description of: A list of IPv4 and IPv6 addresses to use as the fallback DNS servers. If this option is empty, a compiled-in list of DNS servers is used instead. The "compiled-in list" seems to be: This means that if somebody wanted to intentionally set the list to an empty value, the person will need to try some workarounds. Just set the compiled value as the default value, and stop relying on the compiled-in list. This affects , , and versions of at least .
I marked this as stale due to inactivity. &rarr;
set to empty value is not empty, it affects . For me it's security issue, I don't want my server to contact public DNS without being explicitly allowed to do so.
Relevant upstream issue: Looks like they don't care to change it. This value only seems to be used as a last resort when the isn't set and "if none could be learnt via dhcp or ppp".
Oh, he cares. He cares so much and has a strong oppinion on how this should be done that he refuses to change it. Don't mistake Poetterings answer for not caring. He cares deeply.
Note that overriding default values is indeed possible using a single statement with no value. In fact this would be supported by the NixOS module if it weren't for the default being injected on an empty list. This would be a breaking change for a select few I assume, but to be and to and to be then providing as a value (from a user perspective) would set the config value to which would override the upstream behaviour to use no fallback servers. As a stopgap measure you can use this in your config, but being able to use this without extraConfig would be nice considering there is an actual option for this kind of thing. Edit: gonna send a pull request
Change:
environment.NEXTCLOUD_CONFIG_DIR = "${datadir}/config"; serviceConfig.Type = "oneshot"; serviceConfig.User = "nextcloud"; <del> serviceConfig.ExecStart = "${phpPackage}/bin/php -f ${cfg.package}/cron.php"; </del> <ins> serviceConfig.ExecStart = "${phpPackage}/bin/php -f ${webroot}/cron.php"; </ins> }; nextcloud-update-plugins = mkIf cfg.autoUpdateApps.enable { after = [ "nextcloud-setup.service" ];

Discussion:
The extraApp called displays as blank. This was working fine on nextcloud27. Rest of the site is working fine. Steps to reproduce the behavior: am currently on to webpage is blank on: Firefox Chrome Edge It should display the normal forms page. ! Found non-nixos issue relating to it here: Seems it may be a related issue? <!-- 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:
<ins> { lib , stdenv , fetchFromGitHub , buildNpmPackage }: buildNpmPackage rec { pname = "mw"; version = "unstable-2023-08-04"; src = fetchFromGitHub { owner = "mark-when"; repo = "mw"; rev = "a8676da1c7812a051456fabcb980c52a72f6e75e"; hash = "sha256-i95WuTH8qY+0PYQA9kOykQL+4d4oB2Hlvg9sfGtDeCo="; }; npmDepsHash = "sha256-D1hTaoM4j81qrrLMoKJ7OxJTfRoht3/yqgJs95EFxY4="; # correctly substitute the usage message postPatch = '' substituteInPlace src/index.ts  --replace  '.usage("$0' '.usage("mw' ''; meta = { changelog = "https://github.com/mark-when/mw/blob/${src.rev}/CHANGELOG.md"; description = "Markwhen CLI"; homepage = "https://github.com/mark-when/mw"; license = lib.licenses.mit; longDescription = '' Markwhen is an interactive text-to-timeline tool. Write markdown-ish text and it gets converted into a nice looking cascading timeline. ''; mainProgram = "mw"; maintainers = with lib.maintainers; [ dit7ya ]; }; } </ins>

Discussion:
A CLI program that renders Markdown timeline as HTML Announced: <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ...
Since upstream has a this should be pretty simple using .
Change:
pyindego = callPackage ../development/python-modules/pyindego { }; <ins> pyinstaller = callPackage ../development/python-modules/pyinstaller { }; pyinstaller-hooks-contrib = callPackage ../development/python-modules/pyinstaller-hooks-contrib { }; </ins> pyinstaller-versionfile = callPackage ../development/python-modules/pyinstaller-versionfile { }; pyisemail = callPackage ../development/python-modules/pyisemail { };

Discussion:
Project description Freeze (package) Python programs into stand-alone executables. Metadata homepage URL: source URL: license: gpl2 platforms: unix, linux, darwin
I would love to see it packaged too.
So, I did some digging on previous attempts at and found some abandoned PRs: packaged in itself but got abandoned due to complexity. was in partial effort of packaging by packaging one of its dependencies. also as a dependency for another package . Perhaps someone coming to this issue looking for the package can try it themselves using these attempts as a base.
I would also love to figure out how to build pyinstaller projects as a nix derivation
I believe you're looking for ? This issue is requesting to package itself and not packaging projects using .
Change:
maintainers = with maintainers; [ schneefux bachp globin fpletz ma27 ]; license = licenses.agpl3Plus; platforms = with platforms; unix; <del> knownVulnerabilities = optional insecure "Nextcloud version ${version} is EOL"; </del> <ins> knownVulnerabilities = extraVulnerabilities ++ (optional eol "Nextcloud version ${version} is EOL"); </ins> }; }; in {

Discussion:
, CVSSv3=8.1 (nixos-20.09, nixos-unstable) CVSSv3=4.4 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc Cc Cc Cc Cc
Upstream gives the following advisory: If there will be no patch for 19.x I think it would be best to mark as in both 20.09 and unstable.
I feed a bit uneasy about Nextcloud's product update policy but this is nothing NixOS can change
So, it's not very clear to me where the issue got fixed: e.g. states that the issue is in , however there were a few releases after it. As I don't really get where the issue got fixed, I can't just check if the relevant patches got backported. Also, the recommendation to upgrade to v20 seems a bit weird to me since their states that v19 is supposed to be supported until June 2021. I guess, I'll just contact their support and ask about that. After that I'd file an update PR here :)
OK, apparently I'm not the only one who was a bit confused by their way of handling these issues: :D Will file an update PR now. Since is rated as "High" (in contrast to their website where the impact is rated as "Low") and I just checked that the affected encryption feature actually works on NixOS, I guess I'll mark v19 as insecure.
Change:
with stdenv.lib; let <del> version = "2.11.1"; sha256 = "1jrcff0szyjxc3vywyiclwdzk0xgq4cxvjbvmcfyjcpdrq9j5pyr"; </del> <ins> version = "2.12.0"; sha256 = "17377xxbmwbrnh895a108z944pqi39hzrbw4jzgj8pcipi3s3x69"; </ins> audio = optionalString (hasSuffix "linux" stdenv.system) "alsa," + optionalString pulseSupport "pa," + optionalString sdlSupport "sdl,";

Discussion:
Qemu 2.12.0 has released today. We need to update package. Please run and paste the results.
Change:
runHook postInstall ''; <del> outputHashAlgo = "sha256"; outputHashMode = "recursive"; outputHash = "0v5pdhysa2460sh400cpq11smcfsi9g1lbfzx8nj1w5a21d811cz"; </del> meta = with stdenv.lib; { description = "Bloody variant of the Ant theme"; homepage = "https://github.com/EliverLara/${themeName}";

Discussion:
Describe the bug While building ant-theme 3.0 with latest master the following error occurs: To Reproduce Steps to reproduce the behavior: ant-theme Expected behavior builds 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): channels(root): nixpkgs: Maintainer information:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
buildPythonPackage rec { pname = "langchain-community"; <del> version = "0.0.32"; </del> <ins> version = "0.0.33"; </ins> pyproject = true; disabled = pythonOlder "3.8";

Discussion:
In this was to the list of . As is linux-only this breaks the build for and all of it's dependencies on other platforms such as The package also seems to build without this dependency (at least on ) -- I hope I didn't overlook something here (also sadly can't check right now). Thank you! Steps to reproduce the behavior: or Add any other context about the problem here. <!-- 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:
gparted = callPackage ../tools/misc/gparted { }; <ins> gpt4all-cuda = gpt4all.override { cudaSupport = true; }; </ins> gpt2tc = callPackage ../tools/text/gpt2tc { }; gptcommit = callPackage ../development/tools/gptcommit {

Discussion:
Package name: gpt4all Latest released version: 2.8.0 <!-- Search your package here: --- Current version on the unstable channel: 2.7.5 Current version on the stable/release channel: N/A <!-- 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]:
Change:
in stdenv.mkDerivation rec { pname = "warpinator"; <del> version = "1.6.2"; </del> <ins> version = "1.6.3"; </ins> src = fetchFromGitHub { owner = "linuxmint"; repo = pname; rev = version; <del> hash = "sha256-crGW1FBfTEiKqx981EzG414we4icyBv/keGtMlr8UFc="; </del> <ins> hash = "sha256-iCq2cwZgsq5/bJqjYuZ6dZLqz2nIpgHCrIQeMVxJNXY="; </ins> }; nativeBuildInputs = [

Discussion:
To reproduce, here is an example: The related code is at Some nice to have: As suggested  should be something that can be accessible by everything and we are likely going to put our "" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.
Change:
<ins> # Not everyone has a suitable remote builder set up, so the cross-compilation # tests that _include_ running the result are separate. That way, most people # can run the majority of the test suite without the extra setup. import ./make-test-python.nix ({ pkgs, ... }: let remoteSystem = if pkgs.system == "aarch64-linux" then "x86_64-linux" else "aarch64-linux"; remoteCrossPkgs = import ../.. /*nixpkgs*/ { # NOTE: This is the machine that runs the build -  local from the #       'perspective' of the build script. localSystem = remoteSystem; # NOTE: Since this file can't control where the test will be _run_ we don't #       cross-compile _to_ a different system but _from_ a different system crossSystem = pkgs.system; }; hello1 = remoteCrossPkgs.dockerTools.buildImage { name = "hello1"; tag = "latest"; contents = remoteCrossPkgs.hello; }; hello2 = remoteCrossPkgs.dockerTools.buildLayeredImage { name = "hello2"; tag = "latest"; contents = remoteCrossPkgs.hello; }; in { name = "docker-tools"; meta = with pkgs.stdenv.lib.maintainers; { maintainers = [ roberth ]; }; nodes = { docker = { ... }: { virtualisation = { diskSize = 2048; docker.enable = true; }; }; }; testScript = '' docker.wait_for_unit("sockets.target") with subtest("Ensure cross compiled buildImage image can run."): docker.succeed( "docker load --input='${hello1}'" ) assert "Hello, world!" in docker.succeed( "docker run --rm ${hello1.imageName} hello", ) docker.succeed( "docker rmi ${hello1.imageName}", ) with subtest("Ensure cross compiled buildLayeredImage image can run."): docker.succeed( "docker load --input='${hello2}'" ) assert "Hello, world!" in docker.succeed( "docker run --rm ${hello2.imageName} hello", ) docker.succeed( "docker rmi ${hello2.imageName}", ) ''; }) </ins>

Discussion:
Describe the bug It seems generates images with the wrong architecture set. ( began setting these values, but the values before were also wrong) To Reproduce Compared to the current version of : If you actually run the image on arm, Docker complains. Expected behavior Architectures embedded in the image configuration should match those generated by Docker. Additional context The warning message printed by Docker if the running platform doesn't match the image's platform. The operating system, architecture, and variant are determined by and . (If the image's architecture is "arm" and the variant is empty, as it almost always is, it is normalized to "v7", see ) Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(terin): nixpkgs: Maintainer information:
The specification is a bit loose, but the examples given all follow and . If we take a look at the specification, the fields should be and . Every officiall and semi-official image I've looked at, included the pre-multiarch manifest "legacy" images referenced at follow this pattern.
Change:
description = "Open Source library for accessing popular graphics image file formats"; homepage = "http://freeimage.sourceforge.net/"; license = "GPL"; <del> maintainers = with lib.maintainers; [viric]; </del> <ins> maintainers = with lib.maintainers; [viric l-as]; </ins> platforms = with lib.platforms; unix; <del> # see https://github.com/NixOS/nixpkgs/issues/77653 broken = stdenv.isAarch64; </del> }; }

Discussion:
Describe the bug I am trying to build for . is one giving me difficulty. Originally I filed an issue on : But the issue is instead with the libpng inside freeimage: Basically, libpng applies an incorrect ARM optimization to aarch64 that isn't actually available. From briefly looking at in nixpkgs, it seems that we patch with patches (and skimming that, it looks like it has a relevant aarch64 patch). So, my goal is to patch the vendored inside FreeImage, similar to how we patch itself. So far I've not had luck. I've tried with both the CRLF and LF patches from the 'apng' project and the regular patch used from the 'libpng-apng' project that is used in nixpkg's libpng. They all fail to apply and some complain about line endings, regardless of if I pipe the patch through dos2unix (or unix2dos) or not.
I seem to have fixed this by patching libpng inside of the freeimage source using the same patch as the derivation.. I'm just debating whether or not to allow it to be toggle-able as it is in the libpng derivation.
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
still important to me
I marked this as stale due to inactivity. &rarr;
still important to me
You can close this I think
Change:
cmakeFlags = [ "-DRSTUDIO_TARGET=Desktop" ]; <ins> desktopItem = makeDesktopItem { name = name; exec = "rstudio %F"; icon = "rstudio"; desktopName = "RStudio"; genericName = "IDE"; comment = meta.description; categories = "Development;"; mimeType = "text/x-r-source;text/x-r;text/x-R;text/x-r-doc;text/x-r-sweave;text/x-r-markdown;text/x-r-html;text/x-r-presentation;application/x-r-data;application/x-r-project;text/x-r-history;text/x-r-profile;text/x-tex;text/x-markdown;text/html;text/css;text/javascript;text/x-chdr;text/x-csrc;text/x-c++hdr;text/x-c++src;"; }; </ins> postInstall = '' wrapProgram $out/bin/rstudio --suffix PATH : ${gnumake}/bin <ins> mkdir $out/share cp -r ${desktopItem}/share/applications $out/share mkdir $out/share/icons ln $out/rstudio.png $out/share/icons </ins> ''; meta = with stdenv.lib;

Discussion:
No file is provided by Rstudio so system menus in KDE (and presumably any DE) don't show it. System: Nix version: (run ) Nixpkgs version: (run )
Change:
<ins> { lib , python3 , fetchFromGitHub }: python3.pkgs.buildPythonApplication rec { pname = "doq"; version = "0.9.1"; format = "setuptools"; src = fetchFromGitHub { owner = "heavenshell"; repo = "py-doq"; rev = "refs/tags/${version}"; hash = "sha256-6ff7R/2Jo4jYm1hA70yopjklpKIMWlj7DH9eKxOlfgU="; }; propagatedBuildInputs = with python3.pkgs; [ jinja2 parso toml ]; nativeCheckInputs = with python3.pkgs; [ parameterized unittestCheckHook ]; pythonImportsCheck = [ "doq" ]; meta = with lib; { description = "Docstring generator for Python"; homepage = "https://github.com/heavenshell/py-doq"; changelog = "https://github.com/heavenshell/py-doq/releases/tag/${src.rev}"; license = licenses.bsd3; maintainers = with maintainers; [ natsukium ]; }; } </ins>

Discussion:
Project description python docstring generator <!-- Describe the project a little: --Metadata homepage URL: source URL: license: bsd platforms: unix, linux, darwin, ...
Change:
<del> { stdenv, fetchurl, meson, ninja, pkgconfig, gettext, libxml2, desktop-file-utils, python3, wrapGAppsHook , gtk, gnome3, gnome-autoar, glib-networking, shared-mime-info, libnotify, libexif, libseccomp , exempi, librsvg, tracker, tracker-miners, gnome-desktop, gexiv2, libselinux, gdk_pixbuf }: </del> <ins> { stdenv, fetchurl, meson, ninja, pkgconfig, gettext, libxml2 , desktop-file-utils, python3, wrapGAppsHook , gtk, gnome3, gnome-autoar , glib-networking, shared-mime-info, libnotify, libexif, libseccomp , exempi , librsvg, tracker, tracker-miners, gexiv2, libselinux, gdk_pixbuf , substituteAll, bubblewrap }: </ins> let pname = "nautilus";

Discussion:
Thumbnails do not get generated for files. Instead, a 1x1 png file gets written to Here's the relevant terminal output: I'm guessing this is caused by and . Open nautilus in a folder containing images. Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Fixed in
I think the fix wasn't sufficient on 3.30 :/ I'm able to reproduce on master at least. IIRC I only checked the fix worked with 3.28.
It seems that patch may need to be applied directly to Nautilus too as it now seems to bundle that code? -
Change:
mv ../resources $out/share ''; <del> propagatedBuildInputs = lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.Cocoa ]; </del> meta = with lib; { description = "A free 2D physics sandbox game"; homepage = "http://powdertoy.co.uk/";

Discussion:
the-powder-toy segfaults when trying to execute it on aarch64-darwin. It should run and launch the game.
It is fixed upstream from snapshot-231. Should we bump the version or make a patch?
fix (update to latest commit) in
Change:
<ins> { fetchFromGitHub, lib, sway-unwrapped }: sway-unwrapped.overrideAttrs (oldAttrs: rec { pname = "swayfx"; version = "0.2"; src = fetchFromGitHub { owner = "WillPower3309"; repo = "swayfx"; rev = version; sha256 = "sha256-nVy7GdAnheWhjevcCPE407xWSLN8F4Le0uq2RDwv/Zc="; }; meta = with lib; { description = "A Beautiful Sway Fork"; homepage = "https://github.com/WillPower3309/swayfx"; maintainers = with maintainers; [ ricarch97 ]; license = licenses.mit; platforms = platforms.linux; longDescription = '' Fork of Sway, an incredible and one of the most well established Wayland compositors, and a drop-in replacement for the i3 window manager for X11. SwayFX adds extra options and effects to the original Sway, such as rounded corners, shadows and inactive window dimming to bring back some of the Picom X11 compositor functionality, which was commonly used with the i3 window manager. ''; }; }) </ins>

Discussion:
Project description SwayFX is a fork of the Sway window manager that includes popular eye-candy features including rounded corners, shadows, dimming (and a WIP blur). Metadata homepage URL: source URL: license: mit platforms: linux, bsd
We already have a working nix flake: , but I am unsure how maintainers would prefer to have SwayFX packaged.
Change:
<del> { lib, stdenv, fetchurl, freetype, libGL, libGLU, OpenGL }: let name = "ftgl-2.1.3-rc5"; in stdenv.mkDerivation { inherit name; </del> <ins> { lib , stdenv , fetchurl , freetype , libGL , libGLU , OpenGL }: stdenv.mkDerivation rec { pname = "ftgl"; version = "2.1.3-rc5"; </ins> src = fetchurl { <del> url = "mirror://sourceforge/ftgl/${name}.tar.gz"; sha256 = "0nsn4s6vnv5xcgxcw6q031amvh2zfj2smy1r5mbnjj2548hxcn2l"; </del> <ins> url = "mirror://sourceforge/${pname}-${version}.tar.gz"; hash = "sha256-VFjWISJFSGlXLTn4qoV0X8BdVRgAG876Y71su40mVls="; </ins> }; <del> buildInputs = [ freetype ] ++ (if stdenv.isDarwin then [ OpenGL ] else [ libGL libGLU ]) ; </del> <ins> buildInputs = [ freetype ] ++ (if stdenv.isDarwin then [ OpenGL ] else [ libGL libGLU ]); </ins> <del> configureFlags = [ "--with-ft-prefix=${lib.getDev freetype}" ]; </del> <ins> configureFlags = [ "--with-ft-prefix=${lib.getDev freetype}" ]; </ins> enableParallelBuilding = true; <del> meta = { </del> <ins> meta = with lib; { </ins> homepage = "https://sourceforge.net/apps/mediawiki/ftgl/"; description = "Font rendering library for OpenGL applications"; <del> license = lib.licenses.gpl3Plus; </del> longDescription = '' <del> FTGL is a free cross-platform Open Source C++ library that uses Freetype2 to simplify rendering fonts in OpenGL applications. FTGL supports bitmaps, pixmaps, texture maps, outlines, polygon mesh, and extruded polygon rendering modes. </del> <ins> FTGL is a free cross-platform Open Source C++ library that uses Freetype2 to simplify rendering fonts in OpenGL applications. FTGL supports bitmaps, pixmaps, texture maps, outlines, polygon mesh, and extruded polygon rendering modes. </ins> ''; <del> platforms = lib.platforms.unix; maintainers = []; </del> <ins> license = licenses.gpl3Plus; maintainers = with maintainers; [ AndersonTorres ]; platforms = platforms.unix; </ins> }; }

Discussion:
Project description This package is available in the Gentoo package repository: ; (the ebuild isn't for the latest released version, tho) Metadata homepage URL: http://chromium- source URL: gentoo url, nixos has an equivalent to the sourceforge mirrors, but I don't know how to translate it. see also: license: (according to gentoo) , (according to project homepage) platforms: unix. requires OpenGL
Please do the honors,
Change:
vttest = callPackage ../tools/misc/vttest { }; <del> wasm-pack = callPackage ../development/tools/wasm-pack { }; </del> <ins> wasm-pack = callPackage ../development/tools/wasm-pack { inherit (darwin.apple_sdk.frameworks) Security; }; </ins> wavegain = callPackage ../applications/audio/wavegain { };

Discussion:
Describe the bug To Reproduce Steps to reproduce the behavior: -env -i wasm-pack Expected behavior Should install wasm-pack Additional context After add and to buildInputs works well Metadata