jiebi/CodeConvo huggingface dataset:
Change:
--replace "opencc.2" "opencc" ''; <del> nativeBuildInputs = [ pkg-config qmake wrapQtAppsHook ]; </del> <ins> nativeBuildInputs = [ pkg-config qmake wrapQtAppsHook wrapGAppsHook ]; </ins> buildInputs = [ qtbase qtsvg qtwebkit qttools libvorbis hunspell xz lzo

Discussion:
Currently, most functions work without problem. However, when I try to add new paths to search dictionaries, it crashes with the following error message: Steps to reproduce the behavior: goldendict Edit Dictionaries Source Add crashes A dialog should pop up to select the path. Reproduced using the latest master branch of this repo. Using startx and qtile as the window manager I've submitted a PR to fix this issue (see ) <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Change:
${node_webkit}/bin/nw ${onlykey}/lib/node_modules/${onlykey.packageName}/build ''; in <del> runCommand "${onlykey.packageName}-${onlykey.version}" { } '' mkdir -p $out/bin ln -s ${script} $out/bin/onlykey '' </del> <ins> stdenv.mkDerivation { pname = "${onlykey.packageName}"; inherit (onlykey) version; dontUnpack = true; nativeBuildInputs = [ wrapGAppsHook copyDesktopItems ]; desktopItems = [ (makeDesktopItem { name = onlykey.packageName; exec = script; icon = "${onlykey}/lib/node_modules/${onlykey.packageName}/resources/onlykey_logo_128.png"; desktopName = onlykey.packageName; genericName = onlykey.packageName; }) ]; installPhase = '' runHook preInstall mkdir -p $out/bin ln -s ${script} $out/bin/onlykey runHook postInstall ''; } </ins>

Discussion:
The onlykey package crashes when a file dialog should open ("Save as" / "Choose file") Steps to reproduce the behavior: onlykey to the Firmware / Backup Tab "Choose file" or "Save as" A select file window should open, not crash. ! ! I have nautilus and LF installed, which is successfully used by other programs (firefox etc). Already tried installing gsettings-desktop-schemas and setting XDGDATADIRS as described . I use dwm and no Gnome and no Gnome Packages except nautilus. I would guess it needs to use wrapGAppsHook as nativeBuildInputs but I have no idea how/where to add that. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- [username nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs:
Have you cloned nixpkgs? Did you find the nix file where the package recipe is defined?
Yes, the uses node2nix which I do not really understand. It doesn't look like other .nix files. According to this , wrapGAppsHook can be like in . But I can't find , the hook or even just the part where it is supposed to be .
the important parts of are and runCommand so you could replace the call with the usual
Change:
<ins> diff --git a/extension.js b/extension.js index 60396f8..b044872 100644 --- a/extension.js +++ b/extension.js @@ -20,6 +20,8 @@ /* exported init, enable, disable */ +imports.gi.GIRepository.Repository.prepend_search_path('@gtop_path@'); + let depFailures = []; let missingLibs = []; </ins>

Discussion:
installs, but doesn't work. It shows the no-entry-permitted icon and the error message when clicking: to in out / log in It should work. Error message: ! Add any other context about the problem here. Using flakes for configuration management. <!-- 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.
The following addition to my has worked for me on Xorg, but not on Wayland: (via )
Most GNOME Shell extensions are automatically packaged so they might not work when they depend on other libraries. Then, they need to be patched . The preferred way is to patch the extension in Nixpkgs so that it works out of the box for other people as well. But it is a bit involved process: cc
The already packaged extension system-monitor also uses Gtop, so looking at that might be a good point to start. In the patches that we apply, I see
Doing this results in a new error:
Change:
description = "Library supporting deferred execution for GNOME and GTK"; homepage = "https://gitlab.gnome.org/GNOME/libdex"; maintainers = teams.gnome.members; <del> platforms = platforms.linux; </del> <ins> platforms = platforms.linux ++ platforms.darwin; </ins> license = licenses.lgpl21Plus; }; <del> } </del> <ins> }) </ins>

Discussion:
Package name: Latest released version: 46.0 <!-- Search your package here: --- Current version on the unstable channel: 46.0 Current version on the stable/release channel: 46.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. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: Fixes very annoying bug for users with nvidia dGPU notebooks on gnome using external displays. Reports of the Bug:
Change:
, pip , testers , cve-bin-tool <del> # pinned packaging , pyparsing , fetchPypi , buildPythonPackage , pretend , pythonOlder , wheel </del> }: <del> let # pin packaging to < 22 until issue related to https://github.com/intel/cve-bin-tool/pull/2436 are resolved by upstream (post-3.2) packaging_21_3 = buildPythonPackage rec { inherit (packaging) pname passthru meta; version = "21.3"; format = "pyproject"; disabled = pythonOlder "3.6"; src = fetchPypi { inherit pname version; sha256 = "sha256-3UfEKSfYmrkR5gZRiQfMLTofOLvQJjhZcGQ/nFuOz+s="; }; nativeBuildInputs = [ setuptools wheel ]; propagatedBuildInputs = [ pyparsing ]; nativeCheckInputs = [ pytestCheckHook pretend ]; doCheck = false; }; in </del> buildPythonApplication rec { pname = "cve-bin-tool"; <del> version = "3.2"; </del> <ins> version = "3.3"; </ins> format = "setuptools"; src = fetchFromGitHub { owner = "intel"; repo = "cve-bin-tool"; rev = "refs/tags/v${version}"; <del> hash = "sha256-QOnWt6iit0/F6d/MfZ8qJqDuT3IHh0Qjs6BcJkI/CBw="; </del> <ins> hash = "sha256-A5w4U5EDX+UZWNMuz8GTOcubo8N2KfDlVV0aRNsO8/E="; </ins> }; <del> patches = [ # Not needed as python dependency, should just be on the PATH ./no-gsutil-python-dependency.patch # Already merged upstream, to be removed post-3.2 # https://github.com/intel/cve-bin-tool/pull/2524 (fetchpatch { name = "cve-bin-tool-version-success.patch"; url = "https://github.com/intel/cve-bin-tool/commit/6f9bd565219932c565c1443ac467fe4163408dd8.patch"; hash = "sha256-Glj6qiOvmvsuetXn4tysyiN/vrcOPFLORh+u3BoGzCI="; }) ]; </del> # Wants to open a sqlite database, access the internet, etc doCheck = false;

Discussion:
Project description A Python library to create SBOM files in several formats including SPDX and CycloneDX. Metadata homepage URL: source URL: license: Apache-2.0 platforms: Python
The expression for this can probably be automatically generated with a tool like nix-init, would you be down to maintain this package if I add it to nixpkgs?
Here's a generated expression, I can't get the test to pass though.
Change:
<ins> { version, src, pname, pnpm, meta, buildNpmPackage, }: buildNpmPackage { inherit version src meta; pname = "${pname}-webui"; npmDepsHash = "sha256-oHBFuX65D/FgnGa03jjpIKAdH8Q4c2NrpD64bhfe720="; buildPhase = '' runHook preBuild node --max_old_space_size=1024000 ./node_modules/vite/bin/vite.js build runHook postBuild ''; installPhase = '' runHook preInstall cp -r dist $out runHook postInstall ''; } </ins>

Discussion:
Project description is a GUI for jj users. It is a Tauri app. I believe that is working on some stuff to assist packaging Tauri apps in nixpkgs. I wanted to open a 'tracking' issue, maybe to coordinate efforts and keep an eye on things, rather than constantly bugging them in the JJ Discord. (jj is awesome, if you're reading this, you might find it neat to checkout!) Metadata homepage URL: source URL: license: apl2 platforms: unix, linux, darwin, ... ?? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
New version has just come out. But my build still fails with: Anyone got any ideas?
I ran into similar problem when trying to add build using . FWIW I believe problem is in the duplicate (i.e. is a valid directory, is not). This is caused by paths in cargo config being relative to config itself (). Temporary fix is to patch in with an absolute path, but a long-term solution would be to fix (Incomplete) solution can be found at - I'm right now stuck at building frontend part, due to problems with rollup missing its native dependencies: which I believe is tracked .
Update: I have a working build for 0.15.3 in if anyone needs inspiration. Unfortunately it took some tweaking of by hand to make it build and so it probably won't work on anything other than . Probably next step would be to stop using and instead let correctly resolve all the dependencies by itself.
any chance for an update to 0.20.0?
done: notes: custom npm package-lock is no longer needed (upstream works fine), so the build should now work even on linux / x64 darwin, there is still an issue with upstream Cargo.{toml,lock} - for some reason cargo tries to download new deps during build process. I suspect this is caused by tauri enabling certain features, which add extra dependencies during build and/or using custom . But I don't know Rust build process enough to suggest a solution other than declaring these extra dependencies outright in and regenerating lockfile to reflect that. I'm no longer using daily so not a good fit for maintaining that ;)
Change:
homepage = "http://mattmahoney.net/dc/zpaq.html"; license = licenses.gpl3Plus ; maintainers = with maintainers; [ raskin ]; <del> platforms = platforms.linux; </del> <ins> platforms = platforms.unix; </ins> mainProgram = "zpaq"; }; }

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:
fetchSubmodules = true; }; <del> patches = [ ./seastar-configure-script-paths.patch ]; </del> <ins> patches = [ ./seastar-configure-script-paths.patch ./configure-etc-osrelease.patch ]; </ins> nativeBuildInputs = [ pkgconfig

Discussion:
seems to be broken in more than one way. I get (also on ) Pinging maintainer:
That is, a build against current master with succeeds for me on NixOS 18.09 Will work on fixing that, but in the meantime you have a workaround.
Not able to reproduce this one yet
Mh yeah I wrote a patch for to handle the case of not being present and after that, this error log showed up. Edit: I found my patch. Its really simple, just to fix the error. By building with that patch, I get the error log shown above.
i build scylladb under redhat7(3.10.0-693.17.1.el7.x86_64) it fail with following information: i have enough disk for it, but i don't understand why it occupy so huge size.
The final build is for me. Haven't looked into why that is, yet. Could you open a separate issue for that? Thanks!
Change:
import ./make-test-python.nix ({ pkgs, ...} : { name = "lxd-nftables"; meta = with pkgs.stdenv.lib.maintainers; { maintainers = [ patryk27 ]; };

Discussion:
Please find stable urls for the lxd container tests these fail to download now and are causing test failures: cc
Thanks for pinging - I will fix it later today :-)
Change:
meta = with lib; { description = "OBS Studio plugin for adding LiveSplit One as a source"; <del> homepage = "https://github.com/CryZe/obs-livesplit-one"; </del> <ins> homepage = "https://github.com/LiveSplit/obs-livesplit-one"; </ins> license = with licenses; [ asl20 mit ]; maintainers = [ maintainers.Bauke ]; platforms = obs-studio.meta.platforms;

Discussion:
Package name: Latest released version: 0.3.4 <!-- Search your package here: --- Current version on the unstable channel: 0.2.0 Current version on the stable/release channel: 0.2.0 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The repo has moved to .
Working on a PR now.
Getting errors with having Git dependencies. I need to find the hash of the new file, but Nix isn't giving it to me when I provide a fake hash.
I can't get a hash, so I'm stopping for now. If anyone else wants to pick it up, it would be appreciated.
Change:
nativeBuildInputs = [ setuptools-scm-git-archive <del> setuptools_scm </del> <ins> setuptools-scm </ins> ]; checkInputs = [ attrs hypothesis <del> pillow pytestCheckHook </del> pytest-helpers-namespace pytest-timeout <del> pytest_xdist pytestrunner </del> <ins> pytest-xdist psutil pytest-cov pytestCheckHook </ins> python-dateutil python-xmp-toolkit ]; <del> propagatedBuildInputs = [ defusedxml lxml ]; postPatch = '' sed -i  -e 's/^pytest .*/pytest/g'  -e 's/^attrs .*/attrs/g'  -e 's/^hypothesis .*/hypothesis/g'  requirements/test.txt ''; </del> <ins> propagatedBuildInputs = [ defusedxml lxml pillow ]; </ins> preBuild = '' HOME=$TMPDIR ''; <ins> pythonImportsCheck = [ "pikepdf" ]; </ins> meta = with lib; { homepage = "https://github.com/pikepdf/pikepdf"; description = "Read and write PDFs with Python, powered by qpdf";

Discussion:
Describe the bug fails to build on master and unstable Notify maintainers
could you please take a look at ?
Thanks
Change:
configurePhase = '' export GYP_DEFINES="document_dir=$out/share/doc/mozc use_libzinnia=1 use_libprotobuf=1" <del> python src/build_mozc.py gyp --gypdir=${gyp}/bin --server_dir=$out/lib/mozc  python src/unix/fcitx/fcitx.gyp gyp --gypdir=${gyp}/bin ''; preBuildPhase = '' head -n 29 src/server/mozc_server.cc > LICENSE </del> <ins> cd src && python build_mozc.py gyp --gypdir=${gyp}/bin --server_dir=$out/lib/mozc </ins> ''; buildPhase = '' <del> python src/build_mozc.py build -c Release  unix/fcitx/fcitx.gyp:fcitx-mozc  </del> <ins> PYTHONPATH="$PWD:$PYTHONPATH" python build_mozc.py build -c Release  </ins> server/server.gyp:mozc_server  <del> gui/gui.gyp:mozc_tool ''; checkPhase = '' python src/build_mozc.py runtests -c Release </del> <ins> gui/gui.gyp:mozc_tool  unix/fcitx/fcitx.gyp:fcitx-mozc </ins> ''; installPhase = '' <del> install -d        $out/share/licenses/fcitx-mozc/ install -m 644    LICENSE src/data/installer/*.html     $out/share/licenses/fcitx-mozc/ </del> <ins> install -d        $out/share/licenses/fcitx-mozc head -n 29 server/mozc_server.cc > $out/share/licenses/fcitx-mozc/LICENSE install -m 644    data/installer/*.html             $out/share/licenses/fcitx-mozc/ </ins> install -d        $out/share/doc/mozc <del> install -m    644 src/data/installer/*.html             $out/share/doc/mozc/ </del> <ins> install -m    644 data/installer/*.html             $out/share/doc/mozc/ </ins> <del> install -D -m 755 src/out_linux/Release/mozc_server     $out/lib/mozc/mozc_server install    -m 755 src/out_linux/Release/mozc_tool       $out/lib/mozc/mozc_tool </del> <ins> install -D -m 755 out_linux/Release/mozc_server     $out/lib/mozc/mozc_server install    -m 755 out_linux/Release/mozc_tool       $out/lib/mozc/mozc_tool </ins> <del> install -D -m 755 src/out_linux/Release/fcitx-mozc.so   $out/lib/fcitx/fcitx-mozc.so install -D -m 644 src/unix/fcitx/fcitx-mozc.conf        $out/share/fcitx/addon/fcitx-mozc.conf install -D -m 644 src/unix/fcitx/mozc.conf              $out/share/fcitx/inputmethod/mozc.conf </del> <ins> install -D -m 755 out_linux/Release/fcitx-mozc.so   $out/lib/fcitx/fcitx-mozc.so install -D -m 644 unix/fcitx/fcitx-mozc.conf        $out/share/fcitx/addon/fcitx-mozc.conf install -D -m 644 unix/fcitx/mozc.conf              $out/share/fcitx/inputmethod/mozc.conf </ins> install -d        $out/share/doc/mozc <del> for mofile in src/out_linux/Release/gen/unix/fcitx/po/*.mo </del> <ins> for mofile in out_linux/Release/gen/unix/fcitx/po/*.mo </ins> do filename=`basename $mofile` lang=$filename.mo

Discussion:
after a , fcitx cannot switch to mozc only in chromium. journalctl gives me System: (NixOS: , Ubuntu/Fedora: , ...) 09pre106117. (Hummingbird) Nix version: (run ) nix-env (Nix) 1.11.8 Nixpkgs version: (run ) "17.09pre106117." fcitx version: 4.2.9.1 Chromium 57.0.2987.133
Thanks for reporting! Will look into this.
Change:
use Cwd 'abs_path'; use Time::HiRes; <del> my $nsenter = "@utillinux@/bin/nsenter"; </del> my $su = "@su@"; # Ensure a consistent umask.

Discussion:
Currently nixos- uses to attach to containers. However this methods miss out some container context and does not create a pseudo tty. is the offical method recommended by upstream: Previous there was an attempt to use , which does not return the exit code. cc System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run ) Sandboxing enabled: (run )
Previous opinion on this:
Can be fixed by adding .
and don't give the complete container environment, so I'd consider and broken as of now. I agree with using for and for , which is also what systemd themselves recommend. From the : There is still a problem with merging / as , but I don't think that it's currently resolvable, since other container tools also just use a pty.
It is possible by using with the latest systemd release: However I still don't think exposing raw stdin/stdout by default is a good idea for the reason I have given here:
UPDATE I just read it possible to use and in conjunction and uses the more appropriate depending on the context.
Change:
(import ./wayland-session.nix { inherit lib pkgs; enableXWayland = cfg.xwayland.enable; <del> enableWlrPortal = false; # Hyprland has its own portal, wlr is not needed </del> <ins> enableWlrPortal = lib.mkDefault false; # Hyprland has its own portal, wlr is not needed </ins> }) ]);

Discussion:
It is impossible to have both sway and hyprland enabled at the same time. then nixos-rebuild results in: Have a system with both sway and hyprland available simultaneously. Caused by . <!-- 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:
Additional syntax extensions are available, all of which can be used in NixOS option documentation. The following extensions are currently used: <ins> - []{#ssec-contributing-markup-tables} Tables, using the [GitHub-flavored Markdown syntax](https://github.github.com/gfm/#tables-extension-). </ins> - []{#ssec-contributing-markup-anchors} Explicitly defined **anchors** on headings, to allow linking to sections. These should be always used, to ensure the anchors can be linked even when the heading text changes, and to prevent conflicts between [automatically assigned identifiers](https://github.com/jgm/commonmark-hs/blob/master/commonmark-extensions/test/auto_identifiers.md).

Discussion:
There are syntax elements, like which are used in the manual but undocumented in the . the generic syntax is document , but a few more non-admonition variations have been implemented recently that aren't yet documented in the manual. Originally posted by in
Change:
Using config.services.nextcloud.poolConfig is deprecated and will become unsupported in a future release. Please migrate your configuration to config.services.nextcloud.poolSettings. '') <ins> ++ (optional (cfg.config.dbtableprefix != null) '' Using `services.nextcloud.config.dbtableprefix` is deprecated. Fresh installations with this option set are not allowed anymore since v20. If you have an existing installation with a custom table prefix, make sure it is set correctly in `config.php` and remove the option from your NixOS config. '') </ins> ++ (optional (versionOlder cfg.package.version "25") (upgradeWarning 24 "22.11")) ++ (optional (versionOlder cfg.package.version "26") (upgradeWarning 25 "23.05")) ++ (optional (versionOlder cfg.package.version "27") (upgradeWarning 26 "23.11"))

Discussion:
Steps to reproduce the behavior: a minimal config file with Nextcloud In console In (most revelent part) In we can find <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
is this a fresh install or did you try to modify an existing install?
From a fresh install
I didn't expect that, but reproducible for me with mysql and wouldn't be surprised if postgresql has the same issue. Incidentally, this is done by default for the sqlite test and it works fine there. Will take a look ~tomorrowish, need some sleep now.
See , this doesn't seem supported anymore, I just forgot tot ake care of the deprecation, sorry! deprecates this, from now on you'll get a warning when trying to do this.
Thanks for the quick correction. I have one last question. I want to migrate an existing Nextcloud instance that has this prefix. So if this option disappears from the NixOs options, what do I do?
So the module warning points out that you should add the option manually in . Possibly it could also work that you define it via and this will land indirectly in the over the generated
My observation is that the should already be in because nextcloud explicitly writes that into this file on install. Please check if that's the case and if so, you can just remove the option from your system config as explained in the warning. The suggestion to add it on your own is mostly there because I'm not sure if that's the case in all installations and I wanted to make sure people don't break their setup over this.
I have a different prefix than the default ("nc" VS "oc"), so I'll test with At worst, I'll export/import data of each app through their interface, hoping it's possible and goes well.