jiebi/CodeConvo huggingface dataset:
Change:
outputs = [ "out" "dev" ]; <del> nativeBuildInputs = [ meson ninja pkgconfig gobject-introspection ] </del> <ins> nativeBuildInputs = [ meson ninja pkgconfig gobject-introspection makeWrapper ] </ins> # Fixup rpaths because of meson, remove with meson-0.47 ++ stdenv.lib.optional stdenv.isDarwin fixDarwinDylibNames; buildInputs = [ dbus glib libX11 libXtst libXi ];

Discussion:
It seems that all nix expressions for gnome3 applications need revision regarding environment variables wrapping. For instance on my unstable NixOS system I have on on my configuration. All of them (except , which I have already fixed), when run outside of gnome3, are giving error messages like I think they may be fixed by replacing uses of to explicitly fix binaries, by , which automatically fixes them wrapping environment variables. EDIT: In some cases it also needs to add a dependency on .
Related: (also includes a few fixes)
cc
I think the last instances of this were fixed by
In the core GNOME, I only came across two not wrapped executables. from package and from . Unfortunately the former cannot be wrapped due to depending on .
Change:
, ... } @ args: let <del> version = "5.10.186-rt91"; # updated by ./update-rt.sh </del> <ins> version = "5.10.180-rt89"; # updated by ./update-rt.sh </ins> branch = lib.versions.majorMinor version; kversion = builtins.elemAt (lib.splitString "-" version) 0; in buildLinux (args // {

Discussion:
Mounting NFS volumes stopped working without configuration change other than updates. Steps to reproduce the behavior: updated system as of 2023-09-18 from stable to mount a nfs volume Get the error The volume to be mounted Please run and paste the result.
I am having the same issue, with very similar messages: I am running: It happened between ..., the only suspicious changes are kernel changes. In particular, both 6.5.2-6.5.3 and 6.1.52-6.1.53 include the patch "vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing" which I think seems suspicious, but I don't know enough to dig any further. Any help would be appreciated.
Gentoo . In that bug, someone bisected the kernel and identified the patch that mentioned as the culprit. This link to a kernel patch that fixes the issue was also posted and verified to work:
I hit this as well, hoping it gets fixed promptly. For now I've worked around it by using an older stable kernel on affected clients:
I am guessing it will be fixed in upstream soonish, will it be fixed in NixOS like the gentoo folks did? For now, I have confirmed the above patch works on my configuration: nevivurn/nixos-config
The patch worked for me, didn't know it was that easy to apply one
cc
This patch works great! This issue still appears in , but the patch still seems to works if applied to that version.
Change:
# base_version is of the form major.minor.patch # vc_version is of the form YYMMDDCC # version corresponds to the tag on GitHub <del> base_version = "8.2.1"; vc_version = "24030407"; </del> <ins> base_version = "8.3.1"; vc_version = "24090601"; </ins> version = "${base_version}.${vc_version}"; in stdenv.mkDerivation {

Discussion:
Package name: renpy Latest released version: 8.3.2 <!-- Search your package here: --- Current version on the unstable channel: 8.2.1. Current version on the stable/release channel: 8.2.1. <!-- 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:
<ins> { lib , buildGoModule , fetchFromGitHub }: buildGoModule rec { pname = "bitmagnet"; version = "0.0.6"; src = fetchFromGitHub { owner = "bitmagnet-io"; repo = "bitmagnet"; rev = "v${version}"; hash = "sha256-+KAIHg8M2CM+GRRv+htmev8MFe/Y1sJ8p+um/c7kI7c="; }; vendorHash = "sha256-ydiZ3KMEiVkmdzhHjYYLJ7wuiKmwlMEn4OWrKSOnaSo="; ldflags = [ "-s" "-w" ]; meta = { description = "A self-hosted BitTorrent indexer, DHT crawler, and torrent search engine"; longDescription = '' A self-hosted BitTorrent indexer, DHT crawler, content classifier and torrent search engine with web UI, GraphQL API and Servarr stack integration. ''; homepage = "https://bitmagnet.io/"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ eclairevoyant ]; mainProgram = "bitmagnet"; }; } </ins>

Discussion:
Project description A self-hosted BitTorrent indexer, DHT crawler, content classifier and torrent search engine with web UI, GraphQL API and Servarr stack integration. The DHT crawler is bitmagnet’s killer feature that (currently) makes it unique. … DHT’s lesser known feature is that it allows you to crawl the info hashes it knows about. This is how bitmagnet’s DHT crawler works works - it crawls the DHT network, requesting metadata about each info hash it discovers. It then further enriches this metadata by attempting to classify it and associate it with known pieces of content, such as movies and TV shows. It then allows you to search everything it has indexed. This means that bitmagnet is not reliant on any external trackers or torrent indexers. It’s a self-contained, self-hosted torrent indexer, connected via DHT to a global network of peers and constantly discovering new content. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin
Change:
'') ]; meta = with lib; { <ins> mainProgram = "fortune"; </ins> description = "A program that displays a pseudorandom message from a database of quotations"; license = licenses.bsdOriginal; platforms = platforms.unix;

Discussion:
I run the command I expect it to give me a fortune cookie However, I get this error ! Steps to reproduce the behavior: ?? Maintainer information:
Fix is to add in
Change:
<del> { stdenv, fetchFromGitHub, cmake, bison }: </del> <ins> { stdenv, fetchFromGitHub, cmake, bison, spirv-tools, jq }: </ins> stdenv.mkDerivation rec { name = "glslang-git-${version}"; <del> version = "2017-08-31"; </del> <ins> version = "2018-02-05"; </ins> # `vulkan-loader` requires a specific version of `glslang` as specified in # `<vulkan-loader-repo>/external_revisions/glslang_revision`. src = fetchFromGitHub { owner = "KhronosGroup"; repo = "glslang"; <del> rev = "3a21c880500eac21cdf79bef5b80f970a55ac6af"; sha256 = "1i15m17r0acmzjrkybris2rgw15il05a4w5h7vhhsiyngcvajcyn"; </del> <ins> rev = "2651ccaec8"; sha256 = "0x5x5i07n9g809rzf5jgw70mmwck31ishdmxnmi0wxx737jjqwaq"; </ins> }; <del> buildInputs = [ cmake bison ]; </del> <ins> buildInputs = [ cmake bison jq ] ++ spirv-tools.buildInputs; </ins> enableParallelBuilding = true; <ins> patchPhase = '' cp --no-preserve=mode -r "${spirv-tools.src}" External/spirv-tools ln -s "${spirv-tools.headers}" External/spirv-tools/external/spirv-headers ''; preConfigure = '' HEADERS_COMMIT=$(jq -r < known_good.json '.commits|map(select(.name=="spirv-tools/external/spirv-headers"))[0].commit') TOOLS_COMMIT=$(jq -r < known_good.json '.commits|map(select(.name=="spirv-tools"))[0].commit') if [ "$HEADERS_COMMIT" != "${spirv-tools.headers.rev}" ] || [ "$TOOLS_COMMIT" != "${spirv-tools.src.rev}" ]; then echo "ERROR: spirv-tools commits do not match expected versions"; exit 1; fi ''; </ins> meta = with stdenv.lib; { inherit (src.meta) homepage; description = "Khronos reference front-end for GLSL and ESSL";

Discussion:
Tried to make a system upgrade, got this: Obviously, upgrade can't be completed. have in . run Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
This looks like the offending line: This could be related to what file system you are using?
Actually this looks like unrelated to glslang. Works on master:
Change:
# build-tools , bootPkgs , autoconf, automake, coreutils, fetchurl, fetchpatch, perl, python3, m4, sphinx <ins> , bash </ins> , libiconv ? null, ncurses

Discussion:
The shebang line for is using instead of a path from the nix store. Here is a minimal example, showing the problem appearing between and : By using , I landed on , and I think the problematic commit is This commit reverts a previous reversal, The initial reversal mentions problems with shebangs for packages using bootstrap . cc who both worked on the pull request and did the various reversals.
Thank you and for the speedy fix.
Change:
inherit (nixosTests) ceph-multi-node ceph-single-node <del> ceph-single-node-bluestore; </del> <ins> ceph-single-node-bluestore ceph-single-node-bluestore-dmcrypt; </ins> }; }; };

Discussion:
The fix rolled out in lacks the third patch () described in . Without that patch it is still not possible to use ceph-volume with a dmcrypt'd volume. Steps to reproduce the behavior: on a bluestore OSD using LUKS Volume is activated. As there is still a stack trace that can be fixed by applying the above (and in the other issue thread) mentioned patch. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Is there any chance you could add a NixOS VM test that exercises cryptsetup/dmcrypt? Then your setup would be guarded by that for any future NixOS changes.
That's on my todo list for when I have enough spoons, but it is there and I will probably get to it within the next few weeks.
Change:
meta = with lib; { homepage = "https://pdm-project.org"; changelog = "https://github.com/pdm-project/pdm/releases/tag/${version}"; <del> description = "A modern Python package manager with PEP 582 support"; </del> <ins> description = "A modern Python package and dependency manager supporting the latest PEP standards"; </ins> license = licenses.mit; maintainers = with maintainers; [ cpcloud ]; mainProgram = "pdm";

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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 It would be great to get this updated as introduces the ability to manage python versions. Will require: to be updated to to be to dependencies to be packaged and to dependencies <!-- 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]:
Also pinging since it seems you have provided the most recent updates.
Change:
echo "$VCSVersion" > lib/Basic/VCSVersion.inc ''; <ins> passthru = { isClang = true; inherit llvm; }; </ins> meta = with lib; { description = "ROCm fork of the clang C/C++/Objective-C/Objective-C++ LLVM compiler frontend"; homepage = "https://llvm.org/";

Discussion:
Describe the bug fails to build this is a dependency of this prevents building nixos with rocm openCL support To Reproduce Steps to reproduce the behavior: alternatively the following (from ) to a nixos config and try to build nixos from (this is my use case and may catch additional issues) Expected behavior to build, and nothing else to fail towards building my nixos Notify maintainers (thanks for upstreaming btw) Metadata Maintainer information:
Change:
install -Dm 444 data/mat2.svg -t "$out/share/icons/hicolor/scalable/apps" install -Dm 444 doc/mat2.1 -t "$out/share/man/man1" install -Dm 444 nautilus/mat2.py -t "$out/share/nautilus-python/extensions" <del> buildPythonPath "$out $pythonPath" </del> <ins> buildPythonPath "$out $pythonPath $propagatedBuildInputs" </ins> patchPythonScript "$out/share/nautilus-python/extensions/mat2.py" '' + lib.optionalString dolphinIntegration '' install -Dm 444 dolphin/mat2.desktop -t "$out/share/kservices5/ServiceMenus"

Discussion:
When starting : Steps to reproduce the behavior: nautilus on console No error and the context-menu is shown <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- maybe could help?
Look at the top of . You will need something like that in to find dependencies.
Also linking for context.
Actually, looks like it is there, only incomplete. For some reason does not contain the contents of . In the worse case, you can add it manually: but then it will fail differently: so you need to fix the typelib as mentioned in the manual:
I think i followed your suggestions: but I am still getting the same error :confused:
As you can see from the error, you need Poppler, not Gmenu typelib. And possibly some other.
i can confirm, that the entry is now visible, but two times. Might be, that my configuration is weird.
Change:
<del> diff --git a/main.cpp b/main.cpp index a51568d..5a9f683 100644 --- a/main.cpp +++ b/main.cpp @@ -152,7 +152,9 @@ int main(int argc, char *argv[]) </del> <ins> diff --git a/src/main/main.cpp b/src/main/main.cpp index c5210e5f..45794d72 100644 --- a/src/main/main.cpp +++ b/src/main/main.cpp @@ -220,6 +220,9 @@ int main(int argc, char *argv[]) </ins> QCommandLineOption logPathOption(QStringList() << "l" << "log-file", QCoreApplication::translate("main", "Log to specified file"), QCoreApplication::translate("main", "file")); <del> - </del> +    logPathOption.setDefaultValue( +        QStandardPaths::writableLocation(QStandardPaths::CacheLocation) +        + "/monero-wallet-gui.log"); <del> parser.addOption(logPathOption); parser.addHelpOption(); parser.process(app); </del> <ins> QCommandLineOption testQmlOption("test-qml"); testQmlOption.setFlags(QCommandLineOption::HiddenFromHelp); </ins>

Discussion:
Describe the bug monero-gui fails to build, it was part of my . I am on nixos-unstable. To Reproduce Steps to reproduce the behavior: Expected behavior Build success. Metadata
Change:
libadwaita-paperplane tdlib-paperplane rlottie-paperplane <ins> gst_all_1.gstreamer gst_all_1.gst-libav gst_all_1.gst-plugins-base gst_all_1.gst-plugins-good </ins> ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.Foundation ];

Discussion:
Application crashes with when scrolling back chat to images/videos. I'm not really sure what exactly triggers a crash, but the project's README says that when viewing media. Steps to reproduce the behavior: . a chat room with images/videos. a crash No crash. Nope. I've also tried overriding the package locally by adding gst plugins to , and when it didn't work, to like so: but that didn't help. <!-- 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: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
owner = "huggingface"; repo = "huggingface_hub"; rev = "refs/tags/v${version}"; <del> hash = "sha256-uw64JnXx790S4snLjANU0aLI3r7AMPec+IQentTZOdU="; </del> <ins> hash = "sha256-+BtXi+O+Ef4p4b+8FJCrZFsxX22ZYOPXylexFtsldnA="; </ins> }; propagatedBuildInputs = [ filelock <ins> fsspec </ins> packaging pyyaml requests <del> ruamel-yaml </del> tqdm typing-extensions ] ++ lib.optionals (pythonOlder "3.8") [

Discussion:
Package name: python3Packages.huggingface_hub Latest released version: 0.14.1 <!-- Search your package here: --- Current version on the unstable channel: 0.12.1 Current version on the stable/release channel: 0.11.0 <!-- 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. -- (tagged as last updated package) Note for maintainers: Please tag this issue in your PR.
Change:
</listitem> </varlistentry> <ins> <varlistentry><term><option>--max-jobs</option></term> <term><option>-j</option></term> <listitem><para>Sets the maximum number of build jobs that Nix will perform in parallel to the specified number. The default is <literal>1</literal>. A higher value is useful on SMP systems or to exploit I/O latency.</para></listitem> </varlistentry> <varlistentry><term><option>--cores</option></term> <listitem><para>Sets the value of the <envar>NIX_BUILD_CORES</envar> environment variable in the invocation of builders.  Builders can use this variable at their discretion to control the maximum amount of parallelism.  For instance, in Nixpkgs, if the derivation attribute <varname>enableParallelBuilding</varname> is set to <literal>true</literal>, the builder passes the <option>-j<replaceable>N</replaceable></option> flag to GNU Make. The value <literal>0</literal> means that the builder should use all available CPU cores in the system.</para></listitem> </varlistentry> <varlistentry><term><option>--option</option> <replaceable>name</replaceable> <replaceable>value</replaceable></term> <listitem><para>Set the Nix configuration option <replaceable>name</replaceable> to <replaceable>value</replaceable>.</para></listitem> </varlistentry> </ins> <varlistentry> <term><option>--show-trace</option></term> <listitem>

Discussion:
It would speed up the installation if supported or parameter
Probably best to generalize so anything can be passed to
Change:
<ins> { buildGoModule , fetchFromGitHub , lib , libX11 , pam , stdenv }: buildGoModule rec { pname = "emptty"; version = "0.9.0"; src = fetchFromGitHub { owner = "tvrzna"; repo = pname; rev = "v${version}"; hash = "sha256-iT7wdxHC+/3fvBbSrHHuqNYWiqwL48NYzFmtmgVaFik="; }; buildInputs = [ pam libX11 ]; vendorHash = "sha256-tviPb05puHvBdDkSsRrBExUVxQy+DzmkjB+W9W2CG4M="; meta = with lib; { description = "Dead simple CLI Display Manager on TTY"; homepage = "https://github.com/tvrzna/emptty"; license = licenses.mit; maintainers = with maintainers; [ urandom ]; # many undefined functions broken = stdenv.isDarwin; }; } </ins>

Discussion:
Project description A simple to use cli display manager Metadata source URL: license: MIT platforms: linux
I got a video on adding a package to nixpgks here: Go applications are generally easy to add
Is that free for grabs? I'ld like to start contributing to NixOS, this one looks pretty straightforward to start with.
Seems so. :+1::rocket: Shall I assign the issue to you?
Yes, please.
Change:
<programlisting> <xref linkend="opt-security.acme.acceptTerms" /> = true; <xref linkend="opt-security.acme.email" /> = "admin+acme@example.com"; <ins> # /var/lib/acme/.challenges must be writable by the ACME user # and readable by the Nginx user. The easiest way to achieve # this is to add the Nginx user to the ACME group. <link linkend="users.users._name_.extraGroups">users.users.nginx.extraGroups</link> = [ "acme" ]; </ins> services.nginx = { <link linkend="opt-services.nginx.enable">enable</link> = true; <link linkend="opt-services.nginx.virtualHosts">virtualHosts</link> = { "acmechallenge.example.com" = { # Catchall vhost, will redirect users to HTTPS for all vhosts <link linkend="opt-services.nginx.virtualHosts._name_.serverAliases">serverAliases</link> = [ "*.example.com" ]; <del> # /var/lib/acme/.challenges must be writable by the ACME user # and readable by the Nginx user. # By default, this is the case. </del> locations."/.well-known/acme-challenge" = { <link linkend="opt-services.nginx.virtualHosts._name_.locations._name_.root">root</link> = "/var/lib/acme/.challenges"; };

Discussion:
The NixOS manual says This no longer appears to be the default case in NixOS 20.09. I had to add the user to the group.
any chance you have capacity to update in a PR?
I could probably do it in a few days, if nobody else wants to.
ping in case anyone is motivated.
I'll update that today, thanks for pointing it out.
Change:
buildPythonApplication click future six; }; <ins> pru = callPackage ../tools/text/pru { }; </ins> prospector = callPackage ../development/tools/prospector { }; protobuf = protobuf3_19;

Discussion:
Project description Pipeable Ruby - forget about grep / sed / awk / wc ... use pure, readable Ruby Metadata homepage URL: source URL: license: mit platforms: ruby
Looks like you got this in
Change:
{ lib <ins> , stdenv </ins> , buildPythonPackage , fetchFromGitHub <del> , fetchpatch </del> , pytestCheckHook , p7zip , cabextract

Discussion:
At the moment it is not possible to install on my Mac M1 cause is not available at the moment. It would be awsome if I could disable installation of by overriding the . I also could be that I am missing how to do that. Steps to reproduce the behavior: Install Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
in listToAttrs (map formatDevice (filter (fs: fs.autoFormat) fileSystems)); <ins> systemd.tmpfiles.rules = [ "Z /run/keys 0750 root ${toString config.ids.gids.keys}" ]; </ins> # Sync mount options with systemd's src/core/mount-setup.c: mount_table. boot.specialFileSystems = { "/proc" = { fsType = "proc"; options = [ "nosuid" "noexec" "nodev" ]; };

Discussion:
Currently NixOS has some special support for creating a RAM FS for . Unfortunately even though it lives in NixOS and NixOS includes a special "keys" group that is supposed to have access to that folder, support for the feature is sort of neutered without NixOps, which then applies this logic: To actually make the folder usable to members of the "keys" group. It seems like that logic should live on the NixOS side for those of us who want a reasonable place in RAM to drop certain keys, but don't use NixOps. cc since I don't really understand the NixOS/NixOps intricacies.
Wow, stumbled over that just now. Currently is owned by : This currently breaks some assumptions in the NixOS module system when not deployed with NixOps (like when deploying with morph, or autoscaling VMs at cloud providers setting up secrets in ). It'll also become more and more of a problem if we run less services as root, and assume users in the group have access to some secrets. I assume we might want to fix permission of the folder by adding a rule into nixpkgs - turning 2 of the three lines in nixops into a no-op. cc
Totally agree. :+1: to add a tmpfiles rule and remove that thing from nixops.
I'd still like to find out what makes special, and if we can remove things there without breaking anything ;-)
IIRC are the things that are mounted in the . i.e. they're used to generate the in and for some arbitrary reason also which seems the odd one out ;) Perhaps there is some usecase of loading secrets in initrd? Systemd's initrd has a similar procedure called
Yes, enabling sshd in initrd, unlock the root volume by having nixops send over the keys.
So, I did some digging. While assembling stage 1 and 2 scripts, the generated already contains the parameter. However, it seems like the kernel only honors this option for , not . I opened which removes this and uses tmpfiles to do the chgrp when necessary.
Change:
, shiboken2 }: <ins> # Only build when Python<=3.10 # See https://bugreports.qt.io/browse/PYSIDE-1864 # "There are no plans to support Python versions > 3.10 in the 5.15 branch." disabledIf (pythonAtLeast "3.11") ( </ins> stdenv.mkDerivation rec { pname = "pyside2"; version = "5.15.5";

Discussion:
The python3 package appears to be missing the submodule. Steps to reproduce the behavior: The python statement to succeed.