jiebi/CodeConvo huggingface dataset:
Change:
libthai libdrm libdatrie <del> valgrind </del> udev # Text rendering fontconfig

Discussion:
This means nearly all qt6 packages depend on gdb which is 641M on its own. Why is that the case? I can't imagine needing Valgrind for "production" qt6 builds but I have no knowledge in this domain. cc
valgrind was not in my qt6 draft in valgrind was in but valgrind or gdb dont show up in the closure of <details </summaryto compare, </detailsso ... no problem? edit: <details </summary</details
The inputs are only propagated in the output and that's what other packages use. I only came across this because I found gdb in my system closure. showed <the package-quazip -qtbase -valgrind -gdb why did you add valgrind to qt6's propagatedBuildInputs?
It should have been a build time dependency for qtbase. And as it is only referenced in dev output, it should normally not be referenced in system closures, except for issues like Edit, quazip wasn't fixed by that, let me look into it tomorrow.
... so should not be there &rarr; /nix/store/y1m61ayisqmp29ckzi0qq4fp640qfl3l-qtbase-6.4.1-dev/include/QtTest/qtestmouse.h &rarr; /nix/store/y1m61ayisqmp29ckzi0qq4fp640qfl3l-qtbase-6.4.1-dev/include/QtTest/qtestmouse.h &rarr; propagatedBuildInputs &rarr; propagatedBuildInputs also may be relevant: in , are copied to
For the , they should have been in dev output, but and do not have dev output, adding it back should be enough. For , it should be of the same problem as in , maybe we should add that in the hooks of qtbase, or we can fix this ad-hoc.
Change:
ldconfig = writeShellScriptBin "ldconfig" '' # due to a glibc bug, 64-bit ldconfig complains about patchelf'd 32-bit libraries, so we're using 32-bit ldconfig <del> exec ${pkgsi686Linux.glibc.bin}/bin/ldconfig -f /etc/ld.so.conf -C /etc/ld.so.cache "$@" </del> <ins> exec ${if stdenv.isx86_64 && stdenv.isLinux then pkgsi686Linux.glibc.bin else pkgs.glibc.bin}/bin/ldconfig -f /etc/ld.so.conf -C /etc/ld.so.cache "$@" </ins> ''; etcProfile = writeText "profile" '' export PS1='${name}-chrootenv:u@h:w$ '

Discussion:
Steps to reproduce the behavior: : lock file: to build the nixosConfiguration: I'm building an aarch64-linux NixOS system on x8664-linux system. It last wokred a few weeks ago on and currently works on . Currently it doesn't work on and . Only recent change mentioning plex I found is , maybe that's the cause? <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- system: host os: multi-user?: sandbox: version: nixpkgs:
Experiencing the esame too. This PR might be related too:
yeah, this also happens with everything under the cross compilation set like wine and steam, even when using pkgsCross. Any ideas about the rest?
Updated my nixpkgs to include and that fixed it for me - so I no longer need to use an overlay with the bugfix.

and can not be installed on aarch64-linux. Steps to reproduce the behavior: That may be installed on aarch64-linux. The following command which install vscode without fhs works:
Change:
python2Packages.buildPythonApplication rec { name = "certbot-${version}"; <del> version = "0.11.1"; </del> <ins> version = "0.19.0"; </ins> src = fetchFromGitHub { owner = "certbot"; repo = "certbot"; rev = "v${version}"; <del> sha256 = "0f8s6wzj69gnqld6iaskmmwyg5zy5v3zwhp1n1izxixm0vhkzgrq"; </del> <ins> sha256 = "14i3q59v7j0q2pa1dri420fhil4h0vgl4vb471hp81f4y14gq6h7"; </ins> }; propagatedBuildInputs = with python2Packages; [

Discussion:
ACME certificates cannot be provisioned automatically, even though run in manual mode succeeds. This seems to occur whenever allocating a new certificate, and possibly when renewing one. System: (Flounder) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: "16.03.1168."
Hi guys; if any of you know what's going on here, it'd be greatly appreciated. From what I can tell, the Terms of Service are out of date for nixpkgs's version of letsencrypt - and this makes the service pretty much unusable. If you have any ideas about how we can fix this, I'll be happy to investigate further and make a fix.
Luckily only happens when creating a new account, so renews are not affected. Thanks for reporting. Fixed. :beers:
Awesome; thanks for the very fast fix! I'm wondering if there's a more permanent way to solve this - being unable to deploy new servers whenever letsencrypt releases a new TOS seems a bit fragile. Maybe we could add a configuration option to set the TOS hash on the command line when invoking simp_le?
That's a good idea. Also as we're right before releasing 16.09 we should add that option before the release so NixOS users can easily update the hash themselves if needed.
Hi! Even if the new configuration option to set the TOSH hash would only appear in (makes sense, it's a new feature), is the hash fix () going to reach ? It doesn't seem to be there for now:
Thanks for the reminder. I'll look at it. The only potential problem is that is at another version in 16.03. The patch should apply cleanly, though.
any news? If someone need a fix, just add the following snippet to your configuration to override the package with a patched one: Then you can use the options as usual! But I hope the patch will soon be available in :)
Ah, thanks for testing that! In that case I'll simply backport that patch.
Ok, backported. Will be in the 16.03 channel soon. I'll keep this issue open because I want an to add an option for 16.09 to specify the TOS hash in the module.
Confirmed to work on ! Thanks a lot!

are you still planning on doing this in time for 16.09?
what are actionables here for 16.09?
We won't implement this for now because we need to replace simp_le anyway.
This is happening again?
That fix worked for me. I've no idea if it breaks anything else for others.
Change:
<ins> { lib , rustPlatform , fetchFromGitLab , pkg-config , fontconfig , libxkbcommon , wayland }: rustPlatform.buildRustPackage rec { pname = "salut"; version = "unstable-2022-12-17"; src = fetchFromGitLab { owner = "snakedye"; repo = "salut"; rev = "aa57c4d190812908a9c32cd49cff14390c6dfdcb"; hash = "sha256-W0lhhImSXtYJDeMbxyEioYu/Bh7ZclwR1/5DzNbxM8o="; }; cargoLock = { lockFile = ./Cargo.lock; outputHashes = { "msg-api-0.1.0" = "sha256-SGEr9kitvD+KZPGejwDAISK6ERk7G2uskxX8ljiJ2To="; "smithay-client-toolkit-0.16.0" = "sha256-kiTO+BZIgpuwAr6gs9FCqz81jRg+3dV4NxzOX9kbJOc="; "snui-0.1.4" = "sha256-jJL9ukSOczHjPM2EAXcXcz620SK4DQfr+xAT8v7fp9o="; "snui-adwaita-0.1.0" = "sha256-pILhLMzqnhLZfGAXT8QQn6x+IvwG7CSa96wZqq1yrLY="; }; }; nativeBuildInputs = [ pkg-config ]; buildInputs = [ fontconfig libxkbcommon wayland ]; meta = { description = "A sleek notification daemon for Wayland"; homepage = "https://gitlab.com/snakedye/salut/-/wikis/Home"; license = lib.licenses.mpl20; maintainers = with lib.maintainers; [ eclairevoyant ]; mainProgram = "salut"; platforms = lib.platforms.linux; }; } </ins>

Discussion:
Project description A sleek notification daemon for Wayland compositors. Metadata homepage URL: source URL: license: mpl platforms: unix, linux, darwin, ...
PR:
Change:
homepage = "https://www.syslog-ng.com"; description = "Next-generation syslogd with advanced networking and filtering capabilities"; license = with licenses; [ gpl2Plus lgpl21Plus ]; <del> maintainers = with maintainers; [ ]; </del> <ins> maintainers = with maintainers; [ vifino ]; </ins> platforms = platforms.linux; }; }

Discussion:
I tried to update it, but it seems like it wants to build a virtualenv and fetch dependencies. Not sure how to to properly fix it. Maybe just customizing the python and adding the deps will be enough. Package name: syslogng Latest released version: 4.1.1 <!-- Search your package here: --- Current version on the unstable channel: 3.38.1 Current version on the stable/release channel: 3.38.1 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.
will be fixed by
Change:
{ stdenv, buildPythonPackage, fetchPypi <del> , pytest, pytest-sugar, pytest-warnings, setuptools_scm , tempora }: </del> <ins> , pytest, setuptools_scm, tempora }: </ins> buildPythonPackage rec { <del> name = "${pname}-${version}"; </del> pname = "portend"; version = "2.2"; <del> buildInputs = [ pytest pytest-sugar pytest-warnings setuptools_scm ]; propagatedBuildInputs = [ tempora ]; </del> src = fetchPypi { inherit pname version; sha256 = "bc48d3d99e1eaf2e9406c729f8848bfdaf87876cd3560dc3ec6c16714f529586"; }; <ins> nativeBuildInputs = [ setuptools_scm ]; propagatedBuildInputs = [ tempora ]; checkInputs = [ pytest ]; checkPhase = '' py.test ''; </ins> meta = with stdenv.lib; { description = "Monitor TCP ports for bound or unbound states"; homepage = https://github.com/jaraco/portend;

Discussion:
has a test failure and won't install.
That's a known upstream issue:
I guess you didn't initially try to build pytest-sugar but some other package. That one should build fine once is merged.
thanks for looking into this. :)
Change:
hg-git = buildPythonPackage rec { name = "hg-git-${version}"; <del> version = "0.8.5"; </del> <ins> version = "0.8.10"; disabled = isPy3k; </ins> src = pkgs.fetchurl { url = "mirror://pypi/h/hg-git/${name}.tar.gz"; <del> sha256 = "10j7l1p2wx7s5nb6s35z1f3mcz2svz9ilcm26f3la9h9c76b7jpm"; </del> <ins> sha256 = "03dzcs4l7hzq59sgjhngxgmi34xfyd7jcxyjl0f68rwq8b1yqrp3"; </ins> }; propagatedBuildInputs = with self; [ dulwich ];

Discussion:
hggit shipped with nixos support mercurial 3.7,while mercurial shipped with nixos is 4.3.2 Install package - result: System: Nixos 18.03pre117013. (Impala) Nix version:nix-env (Nix) 1.12pre5619_346aeee1 Nixpkgs version:18.03pre117013. Sandboxing enabled: true
This is a bug in hg-git upstream
Change:
{ lib , fetchFromGitHub , fetchpatch <del> , python3 </del> <ins> , python311 , python311Packages </ins> , glibcLocales , gobject-introspection , wrapGAppsHook3

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: lack of directory with executables In contrast this command works as expected: Create directory with executables to invoke Guake. Observe that nixpkgs 24.05 has and in the "Programs provided" section. <img width="989" alt="image" src=""And unstable does not despite both claiming to have version 3.10 of Guake: <img width="1201" alt="image" src=""And both branches provide the same package definition. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Seems like the cause is the below. Oddly the command fails but the build doesn't.
Change:
, glib, kbd, libxslt, coreutils, libgcrypt , kexectools, libmicrohttpd, linuxHeaders, libseccomp , autoreconfHook, gettext, docbook_xsl, docbook_xml_dtd_42, docbook_xml_dtd_45 <del> , pythonPackages ? null, pythonSupport ? false </del> , enableKDbus ? false }: assert stdenv.isLinux; <del> assert pythonSupport -> pythonPackages != null; </del> stdenv.mkDerivation rec { version = "228"; name = "systemd-${version}";

Discussion:
with current current unstable channel, the fail2ban package misses its etc path. The package hasn't been updated for some time and the out path is apparently generated by rewriting pathes in its : This suggests that the breakage might be related to the recent python packaging rework, so /cc as well as pkg maintainers
Change:
<del> {stdenv, fetchurl, which, autoreconfHook, pkgconfig, curl, vala, python, intltool, fuse, ccnet}: </del> <ins> {stdenv, fetchFromGitHub, which, autoreconfHook, pkgconfig, curl, vala, python, intltool, fuse, ccnet}: </ins> stdenv.mkDerivation rec { <del> version = "6.1.0"; </del> <ins> version = "6.2.1"; </ins> name = "seafile-shared-${version}"; <del> src = fetchurl { url = "https://github.com/haiwen/seafile/archive/v${version}.tar.gz"; sha256 = "03zvxk25311xgn383k54qvvpr8xbnl1vxd99fg4ca9yg5rmir1q6"; </del> <ins> src = fetchFromGitHub { owner = "haiwen"; repo = "seafile"; rev = "v${version}"; sha256 = "199ivh6fbz4sgbz15mr6m8985yky5n3z6vpcpnh2ldjx4277gq68"; </ins> }; nativeBuildInputs = [ pkgconfig which autoreconfHook vala intltool ];

Discussion:
seafile-client 6.1.8 fails to build at cmake configuration step with the following error message: run
I've tried updating Seafile to 6.2.0, which supports Qt 5.11, here: However, I ran into an issue:
With Qt 5.11.1, the error is gone, but the current version is still incompatible with Qt 5.11.x:
Change:
(mkEnable true                "pinentry-tty") (mkEnable (gtk2 != null)      "pinentry-gtk2") (mkEnable (gcr != null)       "pinentry-gnome3") <del> (mkEnable (qt4 != null)       "pinentry-qt") </del> <ins> (mkEnable (qt != null)        "pinentry-qt") </ins> ]; nativeBuildInputs = [ pkgconfig ]; <del> meta = { </del> <ins> meta = with stdenv.lib; { </ins> homepage = http://gnupg.org/aegypten2/; <del> description = "GnuPG's interface to passphrase input"; license = stdenv.lib.licenses.gpl2Plus; platforms = stdenv.lib.platforms.all; </del> <ins> description = "GnuPG’s interface to passphrase input"; license = licenses.gpl2Plus; platforms = platforms.all; </ins> longDescription = '' Pinentry provides a console and (optional) GTK+ and Qt GUIs allowing users to enter a passphrase when `gpg' or `gpg2' is run and needs it. ''; <del> maintainers = [ stdenv.lib.maintainers.ttuegel ]; </del> <ins> maintainers = [ maintainers.ttuegel ]; </ins> }; }

Discussion:
Setting breaks . The reason being that defines and as follows: Which then overrides with, Resulting in an infinite loop. This appears to be a regression due to . Set , try to build . Using .
This is downfall from
what should be done about this?
Did not we fix this in Anyway, should fix pinentry for good.
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
how does the situation look like now? Is this specific issue fixed?
I marked this as stale due to inactivity. &rarr;
Closing due to inactivity. Please reopen if it's still broken.
Change:
}; }; <ins> weather = mkTmuxPlugin { pluginName = "weather"; version = "unstable-2020-02-08"; src = fetchFromGitHub { owner = "xamut"; repo = "tmux-weather"; rev = "28a5fbe75bb25a408193d454304e28ddd75e9338"; hash = "sha256-of9E/npEsF1JVc9ttwrbC5WkIAwCNBJAgTfExfj79i4="; }; meta = with lib; { homepage = "https://github.com/xamut/tmux-weather"; description = "Shows weather in the status line"; license = licenses.mit; platforms = platforms.unix; maintainers = with maintainers; [ jfvillablanca ]; }; }; </ins> yank = mkTmuxPlugin { pluginName = "yank"; version = "unstable-2021-06-20";

Discussion:
Project description Tmux plugin for showing weather in status bar. Presumably the Nix package name would be Metadata source URL: mit platforms: wherever tmux, bash, curl, and sed are supported
I would like to try this out.
Change:
} $CONFIG = [ 'apps_paths' => [ <del> ${optionalString (cfg.extraApps != { }) "[ 'path' => '${cfg.home}/nix-apps', 'url' => '/nix-apps', 'writable' => false ],"} [ 'path' => '${cfg.home}/apps', 'url' => '/apps', 'writable' => false ], [ 'path' => '${cfg.home}/store-apps', 'url' => '/store-apps', 'writable' => true ], </del> <ins> ${concatStrings (mapAttrsToList mkAppStoreConfig appStores)} </ins> ], ${optionalString (showAppStoreSetting) "'appstoreenabled' => ${renderedAppStoreSetting},"} 'datadirectory' => '${datadir}/data',

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:
shellFor = { packages, withHoogle ? false, ... } @ args: let selected = packages self; <del> packageInputs = builtins.map getHaskellBuildInputs selected; </del> <ins> packageInputs = builtins.map getBuildInputs selected; </ins> haskellInputs = builtins.filter (input: pkgs.lib.all (p: input.outPath != p.outPath) selected)

Discussion:
now aborts with on switch between commits (last working) and (introduces the error for me) use this and Please run and paste the results.
Change:
emacsWithPackages = emacs.pkgs.withPackages; # Added 2020-12-18 enblendenfuse = throw "'enblendenfuse' has been renamed to/replaced by 'enblend-enfuse'"; # Converted to throw 2022-02-22 <ins> enchant1 = throw "enchant1 has been removed from nixpkgs, as it was unmaintained"; # Added 2023-01-18 </ins> encryptr = throw "encryptr was removed because it reached end of life"; # Added 2022-02-06 envdir = throw "envdir has been dropped due to the lack of maintenance from upstream since 2018"; # Added 2022-06-03 envelope = throw "envelope has been removed from nixpkgs, as it was unmaintained"; # Added 2021-08-05

Discussion:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. &rarr;
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to
Change:
{ fetchurl, fetchpatch, substituteAll, stdenv, pkgconfig, gnome3, gettext, gobject-introspection, upower, cairo <del> , pango, cogl, clutter, libstartup_notification, zenity, libcanberra-gtk3 </del> <ins> , pango, cogl, json-glib, libstartup_notification, zenity, libcanberra-gtk3 </ins> , ninja, xkeyboard_config, libxkbfile, libxkbcommon, libXtst, libinput , gsettings-desktop-schemas, glib, gtk3, gnome-desktop , geocode-glib, pipewire, libgudev, libwacom, xwayland, meson

Discussion:
Capability wrappers are somewhat limited. They require the capability be part of the ambient set for it to survive execv's, ie. when the wrapper executes the source binary (). This means any program spawned from a wrapped binary will also inherit the capabilities. We really don't want programs launched from gnome-shell to inherit capsysnice obviously. In particular bubblewrap fails to work if it possess any extra caps, breaking at least flatpaks and epiphany. So as far as I can see we have two options: Actually copy to wrapperDir and set capsysnic=+ep. This should be pretty easy, but also quite ugly (see for context). Patch mutter to drop inheritable, we could probably adopt . This should probably work as the ambient set only propagates if inheritable is set. cc
Patching mutter to drop inheritable works :tada:, will make a PR :)
Does the rationale for not merging it not apply to us?
No it shouldn't. We only drop inheritable to prevent the ambient set being passed on, while keeping effective and permitted for gnome-shell. (it might be possible to drop the ambient set with , but I went with just clearing inheritable):
Change:
<del> { lib, buildGoModule, fetchFromGitHub, installShellFiles, git, testers, git-town, makeWrapper }: </del> <ins> { lib, buildGoModule, fetchFromGitHub, fetchpatch, installShellFiles, git, testers, git-town, makeWrapper }: </ins> buildGoModule rec { pname = "git-town"; <del> version = "7.7.0"; </del> <ins> version = "7.8.0"; </ins> src = fetchFromGitHub { owner = "git-town"; repo = "git-town"; rev = "v${version}"; <del> sha256 = "sha256-FpBEBx2gb33fGDndvZmvG1A61NoJ4Qy4V3YQSb+Ugsc="; </del> <ins> sha256 = "sha256-g9ooMIMN8DN2FcWYkDC1hICCleQYdHf30PYMCit/NMI="; </ins> }; <ins> patches = [ # Fix "go vet" when building using Go 1.18. (fetchpatch { name = "fix-go-vet-in-go-1.18.patch"; url = "https://github.com/git-town/git-town/commit/23eb0aca7b28c6a0afc21db553aa0e35d35891aa.patch"; sha256 = "sha256-EyfhKVrQxRJNrYqaZI04dJogaXs1J+bbOIu7p8g2Clc="; }) ]; </ins> vendorSha256 = null; nativeBuildInputs = [ installShellFiles makeWrapper ];

Discussion:
Steps to reproduce the behavior: git-town on MacOS Please run and paste the result.
Change:
<del> { lib, stdenv, fetchFromGitHub, meson, luajit, ninja, pkg-config , python3, SDL2, lua, fftwFloat, zlib, bzip2, curl, darwin }: </del> <ins> { lib , stdenv , fetchFromGitHub , meson , ninja , pkg-config , python3 , SDL2 , bzip2 , curl , fftwFloat , lua , luajit , zlib , Cocoa }: </ins> stdenv.mkDerivation rec { pname = "the-powder-toy"; <del> version = "96.2.350"; </del> <ins> version = "unstable-2022-08-30"; </ins> src = fetchFromGitHub { owner = "The-Powder-Toy"; repo = "The-Powder-Toy"; <del> rev = "v${version}"; sha256 = "sha256-OAy/Hd2UksNiIfTdpA+u9NzIq1pfe8RYG3slI4/LNnM="; </del> <ins> rev = "9e712eba080e194fc162b475f58aaed8f4ea008e"; sha256 = "sha256-44xUfif1E+T9jzixWgnBxOWmzPPuVZy7rf62ig/CczA="; </ins> }; nativeBuildInputs = [ meson ninja pkg-config python3 ]; <del> buildInputs = [ luajit SDL2 lua fftwFloat zlib bzip2 curl ]; </del> <ins> buildInputs = [ SDL2 bzip2 curl fftwFloat lua luajit zlib ] ++ lib.optionals stdenv.isDarwin [ Cocoa ]; </ins> installPhase = '' install -Dm 755 powder $out/bin/powder

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