jiebi/CodeConvo huggingface dataset:
Change:
pylru pyyaml sarge feedparser netifaces click websocket_client scandir chainmap future dateutil futures wrapt monotonic emoji frozendict <del> ]; </del> <ins> ] ++ lib.optionals stdenv.isDarwin [ py.pkgs.appdirs ]; </ins> checkInputs = with py.pkgs; [ nose mock ddt ];

Discussion:
The tests for python27Packages.jinja2 fail and thereby the derivation fails to evaluate. (Full log below) I'm crosscompiling an aarch64 sd image with . I'm crosscompiling aarch64 with nixpkgs .
I had the same issue too, this fixes it for me.
Fixed by
Change:
<ins> diff --color --unified --recursive --text a/Core/VolumeCreator.h b/Core/VolumeCreator.h --- a/Core/VolumeCreator.h	2021-06-20 20:54:50.725210056 +0300 +++ b/Core/VolumeCreator.h	2021-06-20 20:58:46.117742419 +0300 @@ -77,12 +77,12 @@ switch (fsType) { #if defined (TC_LINUX) -				case VolumeCreationOptions::FilesystemType::Ext2:		return "mkfs.ext2"; -				case VolumeCreationOptions::FilesystemType::Ext3:		return "mkfs.ext3"; -				case VolumeCreationOptions::FilesystemType::Ext4:		return "mkfs.ext4"; -				case VolumeCreationOptions::FilesystemType::NTFS:		return "mkfs.ntfs"; -				case VolumeCreationOptions::FilesystemType::exFAT:		return "mkfs.exfat"; -				case VolumeCreationOptions::FilesystemType::Btrfs:		return "mkfs.btrfs"; +				case VolumeCreationOptions::FilesystemType::Ext2:		return "@ext2@"; +				case VolumeCreationOptions::FilesystemType::Ext3:		return "@ext3@"; +				case VolumeCreationOptions::FilesystemType::Ext4:		return "@ext4@"; +				case VolumeCreationOptions::FilesystemType::NTFS:		return "@ntfs@"; +				case VolumeCreationOptions::FilesystemType::exFAT:		return "@exfat@"; +				case VolumeCreationOptions::FilesystemType::Btrfs:		return "@btrfs@"; #elif defined (TC_MACOSX) case VolumeCreationOptions::FilesystemType::MacOsExt:	return "newfs_hfs"; case VolumeCreationOptions::FilesystemType::exFAT:		return "newfs_exfat"; </ins>

Discussion:
I think the package should depend on e.g. and similar so that creation of such file systems from the GUI works out of the box, instead of requiring that they are on the user's PATH. CC
I marked this as stale due to inactivity. &rarr;
Still relevant
Change:
"--enable-library-for-ghci" # TODO: Should this be configurable? ] ++ optionals (enableDeadCodeElimination && (stdenv.lib.versionOlder "8.0.1" ghc.version)) [ "--ghc-option=-split-sections" <ins> ] ++ optionals dontStrip [ "--disable-library-stripping" "--disable-executable-stripping" </ins> ] ++ optionals isGhcjs [ "--ghcjs" ] ++ optionals isCross ([

Discussion:
Passing to a Haskell package has no effect, the resulting binary is . CC
I have checked that at the time runs, shows as but shows as .
The solution seems to be to pass  in when is given.
PR with the fix at
Change:
kcmutils kcrash kdbusaddons kparts kwindowsystem akonadi grantleetheme kontactinterface kpimtextedit mailcommon libkdepim pimcommon <ins> akregator kaddressbook kmail knotes korganizer zanshin </ins> ]; }

Discussion:
After installing , the interface that shows up is completely Steps to reproduce the behavior: to systemPackages in See the standard Kontact interface will all the apps: ! Actual result ! The "Kontact Suite" promises, , to That means the package should depend on: kmail kaddressbook korganizer akregator Additionally, there's a package that has no executable binary yet seems related to . What is is for? Please run and paste the result.
Possibly related to
Looks like grantleetheme is looking in the wrong directory for resources. The files do exist in . Other package managers would just write the files to the global messageviewer path, but that doesn't work with nix. There must be some way to make grantlee theme look in the right directory.
See and
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
<ins> { buildPythonPackage, docopt, fetchFromGitHub, lib, markdown2, pytest-cov-stub, pytestCheckHook, setuptools, weasyprint, }: buildPythonPackage rec { pname = "md2pdf"; version = "1.0.1"; pyproject = true; src = fetchFromGitHub { owner = "jmaupetit"; repo = "md2pdf"; rev = "refs/tags/${version}"; hash = "sha256-9B1vVfcBHk+xdE2Xouu95j3Hp4xm9d5DgPv2zKwCvHY="; }; postPatch = '' substituteInPlace setup.py  --replace-fail '"pytest-runner",' "" ''; build-system = [ setuptools ]; dependencies = [ docopt markdown2 weasyprint ]; pythonImportsCheck = [ "md2pdf" ]; nativeCheckInputs = [ pytest-cov-stub pytestCheckHook ]; preCheck = '' export PATH="$out/bin:$PATH" ''; meta = { changelog = "https://github.com/jmaupetit/md2pdf/blob/${src.rev}/CHANGELOG.md"; description = "Markdown to PDF conversion tool"; homepage = "https://github.com/jmaupetit/md2pdf"; license = lib.licenses.mit; mainProgram = "md2pdf"; maintainers = with lib.maintainers; [ dotlambda ]; }; } </ins>

Discussion:
Project description <!-- Describe the project a little: --Convert Markdown files to PDF with styles. Metadata homepage URL: source URL: license: mit platforms: linux. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
lib, stdenv, fetchurl, <ins> fetchgit, </ins> linkFarm, dub, ldc,

Discussion:
fails to build a lockfile with dependencies in the format (). Here's the error: any repository whose contains a dependency that fetches from Git, e.g. , e.g. . a few moments, then see error. A generated lockfile containing the Git dependency. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for reporting this bug, I'll try to extend the lockfile logic later today, (the current one is pretty primitive, as you might have seen)
Change:
stdenv.mkDerivation rec { pname = "fcitx-libpinyin"; <del> version = "0.5.3"; </del> <ins> version = "0.5.4"; </ins> src = fetchurl { url = "http://download.fcitx-im.org/fcitx-libpinyin/${pname}-${version}.tar.xz"; <del> sha256 = "196c229ckib3xvafkk4n3n3jk9rpksfcjsbbwka6a9k2f34qrjj6"; </del> <ins> sha256 = "1wvsc21imbgq3chlxfw4aycmkb2vi1bkjj9frvhga2m5b5pq82k5"; </ins> }; nativeBuildInputs = [ cmake pkg-config  ];

Discussion:
After updating to the latest NixOS unstable channel, when running , the process will fail when building fcitx-libpinyin. Can repro this in a fresh installed NixOS using , adding the following lines: channel: : process will fail when building .....-fcitx-libpinyin- with exit code 2. The rebuild process should succeed without failure. !
Updating to 0.5.4 seems to fix it:
Change:
ceph-client; ceph-dev = ceph; <del> inherit (callPackages ../tools/security/certmgr { }) certmgr certmgr-selfsigned; </del> cfdg = callPackage ../tools/graphics/cfdg { }; cglm = callPackage ../development/libraries/cglm { };

Discussion:
Steps to reproduce the behavior: build certmgr-selfsigned, eg Caused by this by by this out of date shar and also detected Please run and paste the result. Add a to . Thanks!
Change:
<ins> { lib , stdenv , fetchFromGitHub , boost , cmake , ninja , pkg-config , sqlite , zlib }: stdenv.mkDerivation { name = "libdjinterop"; version = "unstable"; src = fetchFromGitHub { owner = "xsco"; repo = "libdjinterop"; rev = "0.20.1"; hash = "sha256-/iXSRJVFPWqUTVz7z0BNWCq5LOqdNuTI+wx/34JAZfc="; }; nativeBuildInputs = [ cmake ninja pkg-config ]; outputs = [ "out" "dev" ]; buildInputs = [ boost sqlite zlib ]; meta = with lib; { homepage = "https://github.com/xsco/libdjinterop"; description = "C++ library for access to DJ record libraries"; license = licenses.lgpl3; maintainers = with maintainers; [ benley ]; platforms = platforms.unix; }; } </ins>

Discussion:
Package name: mixxx Latest released version: 2.4.0 Current version on the unstable channel: 2.3.6 Current version on the stable/release channel: 2.3.5 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]:
1 is now out, pinging:
Change:
barman = python3Packages.callPackage ../tools/misc/barman { }; <ins> bashate = python3Packages.callPackage ../development/tools/bashate { }; </ins> bash-my-aws = callPackage ../tools/admin/bash-my-aws { }; bashcards = callPackage ../tools/misc/bashcards { };

Discussion:
Project description A pep8 equivalent for bash scripts This program attempts to be an automated style checker for bash scripts to fill the same part of code review that pep8 does in most OpenStack projects. It started from humble beginnings in the DevStack project, and will continue to evolve over time. Metadata homepage URL: source URL: license: Apache2.0 platforms: unix, linux, darwin
Change:
<del> <section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="sec-language-coq"> <title>Coq</title> <para> Coq libraries should be installed in <literal>$(out)/lib/coq/${coq.coq-version}/user-contrib/</literal>. Such directories are automatically added to the <literal>$COQPATH</literal> environment variable by the hook defined in the Coq derivation. </para> <para> Some extensions (plugins) might require OCaml and sometimes other OCaml packages. The <literal>coq.ocamlPackages</literal> attribute can be used to depend on the same package set Coq was built against. </para> <para> Coq libraries may be compatible with some specific versions of Coq only. The <literal>compatibleCoqVersions</literal> attribute is used to precisely select those versions of Coq that are compatible with this derivation. </para> <para> Here is a simple package example. It is a pure Coq library, thus it depends on Coq. It builds on the Mathematical Components library, thus it also takes <literal>mathcomp</literal> as <literal>buildInputs</literal>. Its <literal>Makefile</literal> has been generated using <literal>coq_makefile</literal> so we only have to set the <literal>$COQLIB</literal> variable at install time. </para> <programlisting> { stdenv, fetchFromGitHub, coq, mathcomp }: stdenv.mkDerivation rec { name = "coq${coq.coq-version}-multinomials-${version}"; version = "1.0"; src = fetchFromGitHub { owner = "math-comp"; repo = "multinomials"; rev = version; sha256 = "1qmbxp1h81cy3imh627pznmng0kvv37k4hrwi2faa101s6bcx55m"; }; buildInputs = [ coq ]; propagatedBuildInputs = [ mathcomp ]; installFlags = "COQLIB=$(out)/lib/coq/${coq.coq-version}/"; meta = { description = "A Coq/SSReflect Library for Monoidal Rings and Multinomials"; inherit (src.meta) homepage; license = stdenv.lib.licenses.cecill-b; inherit (coq.meta) platforms; }; passthru = { compatibleCoqVersions = v: builtins.elem v [ "8.5" "8.6" "8.7" ]; }; } </programlisting> </section> </del>

Discussion:
This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! in this issue that you intend to work on it. (Please also post if you stop working on it) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.
I can also look at this.
Change:
{ stdenv , lib , fetchFromGitHub <del> , fetchpatch </del> , wrapQtAppsHook , qmake , pkg-config

Discussion:
Package name: fritzing Latest released version: 1.0.1 (not tagged, it appears to be ) <!-- Search your package here: --- Current version on the unstable channel: unstable-2022-07-01 Current version on the stable/release channel: unstable-2022-07-01 <!-- 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]:
Thanks! Updated to in
Change:
maintainers = [ lib.maintainers.ttuegel ]; }; nativeBuildInputs = [ extra-cmake-modules ]; <del> buildInputs = [ ffmpeg_3 kio taglib ]; </del> <ins> buildInputs = [ ffmpeg_4 kio taglib ]; </ins> }

Discussion:
Describe the bug Dolphin does not generate video thumbnails on unstable after the update to v20.12.1 . Removing in change appears to have resulted in dropping compatibility with ffmpeg 3. Updating the to reference instead of fixes the issue. To Reproduce Steps to reproduce the behavior: dolphin, ffmpegthumbs video thumbnails in dolphin Expected behavior See thumbnail generated for video files Notify maintainers
Change:
source = if url == null then src else fetchurl { url = url; <del> inherit md5 sha1 sha256 sha512 hash; </del> <ins> inherit sha1 sha256 sha512 hash; </ins> }; in stdenv.mkDerivation {

Discussion:
tries to send (empty) md5 hashes to fetchurl, which doesn't accept md5 hashes it seems Steps to reproduce the behavior: enter the following command: The firefox plugin builds successfully <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --git revision tags of both NUR and nixpkgs are in the command given above
Can you try , I tested with your repro cmd changing to in nixpkgs src with the patch.
This works correctly, thank you very much!
Change:
if [[ -z $buildingAttribute ]]; then exec nix repl --file $buildFile $attr "${extraBuildFlags[@]}" elif [[ -z $flake ]]; then <del> exec nix repl '<nixpkgs/nixos>' "${extraBuildFlags[@]}" </del> <ins> exec nix repl --file '<nixpkgs/nixos>' "${extraBuildFlags[@]}" </ins> else if [[ -n "${lockFlags[0]}" ]]; then # nix repl itself does not support locking flags

Discussion:
doesn't work with channel configuration. Output: Only with channels. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
That should be enough to fix it, I think?
Did you try it and did it work? If so, feel free to shoot a PR with that patch.
works for me. I didn't check any other flag combinations though. But I guess working sometimes is better than working never.
It'd be great if you could create a PR then :)
Change:
systemd.services.riemann-health = { wantedBy = [ "multi-user.target" ]; <ins> path = [ procps ]; </ins> serviceConfig = { User = "riemanntools"; ExecStart = "${healthLauncher}/bin/riemann-health";

Discussion:
Build NixOS with , and journald ends up with a lot of log entries like this:
The service was fixed by in master and in 16.09, though as notes, the riemann-tools package itself ought to be fixed.
Change:
qtmultimedia qtlocation qqc2-desktop-style <ins> kirigami-addons </ins> kirigami2 <ins> kio </ins> knotifications <ins> kquickimageedit </ins> zxing-cpp qxmpp sonnet

Discussion:
Steps to reproduce the behavior: kaidan <!-- 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]:
Thanks for notifying me!
Change:
githubId = 24496705; name = "Scott Hamilton"; }; <ins> ShamrockLee = { name = "Shamrock Lee"; email = "44064051+ShamrockLee@users.noreply.github.com"; github = "ShamrockLee"; githubId = 44064051; }; </ins> shanemikel = { email = "shanepearlman@pm.me"; github = "shanemikel";

Discussion:
Project description Cross platform chewing user phrase editor Chewing editor is a widely-used bopomofo input method for traditional Chinese, and chewing-editor is the tool to edit the database of user phrases stored by the input method. Users of chewing will need chewing-editor sooner or later. NixOS have chewing include as a fcitx engine () that can be used in the module, but not chewing-editor. Metadata homepage URL: source URL: license: gpl2 platforms: unix
The corresponding pull request is merged. Closing.
Change:
<ins> { stdenv , lib , fetchgit }: stdenv.mkDerivation rec { pname = "nv-codec-headers"; version = "12.0.16.0"; src = fetchgit { url = "https://git.videolan.org/git/ffmpeg/nv-codec-headers.git"; rev = "n${version}"; sha256 = "sha256-8YZU9pb0kzat0JBVEotaZUkNicQvLNIrIyPU9KTTjwg="; }; makeFlags = [ "PREFIX=$(out)" ]; meta = with lib; { description = "FFmpeg version of headers for NVENC"; homepage = "https://git.videolan.org/?p=ffmpeg/nv-codec-headers.git"; license = licenses.mit; maintainers = with maintainers; [ MP2E ]; platforms = platforms.all; }; } </ins>

Discussion:
Package name: jellyfin-ffmpeg Latest released version: 6.0-3 Current version on the unstable channel: 5.1.2-8 Current version on the stable/release channel: 5.1.2-8 <!-- 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.
Change:
description = "John the Ripper password cracker"; license = licenses.gpl2; homepage = https://github.com/magnumripper/JohnTheRipper/; <del> maintainers = with maintainers; [ offline ]; platforms = [ "x86_64-linux" "x86_64-darwin"]; </del> <ins> maintainers = with maintainers; [ offline matthewbauer ]; platforms = platforms.unix; </ins> }; }

Discussion:
Describe the bug I installed john the ripper from the binary cache, and executing it fails with: I have a recent laptop (Thinkpad T480s) with i7-8550U CPUs, but apparently that's not good enough. It would be good to compile john with less demanding requirements for the benefit of most users, and maybe output a message how to compile it yourself on nix systems.
Yeah it looks like one of the builders has this feature so the configure script requires it: It looks like we need to pass the flag.
cc maintainer
backported to 19.09 in .
Change:
buildPythonApplication rec { pname = "trytond"; <del> version = "6.2.1"; </del> <ins> version = "6.2.2"; </ins> format = "setuptools"; disabled = pythonOlder "3.6"; src = fetchPypi { inherit pname version; <del> sha256 = "418f16c45b7130555447af901639b92bb188d39f46ce7fe4dfcd941c5959ed7e"; </del> <ins> sha256 = "9494016dd8b4da5a06dccdd1afbd918248d42da9f2c19b1eb8958052c747e193"; </ins> }; # Tells the tests which database to use

Discussion:
Upgrading fails, seemingly because the existing systemd version is newer in 21.11 than unstable. Steps to reproduce the behavior: NixOS 21.11 21.11 channel, add unstable channel NixOS upgrades from 21.11 to unstable. is the commit upgrading systemd to 249.7, cherry picks it to 21.11. Adding the flag to the invocation would also solve this issue, albeit leaving the newer EFI files in place. <!-- 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.
I think the corresponding PR is
As pointed out above by this will be fixed when staging-next gets merged ().
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
<ins> { lib , stdenv , fetchFromGitHub , cmake , codec2 , libsamplerate , libsndfile , lpcnetfreedv , portaudio , speexdsp , hamlib , wxGTK31-gtk3 }: stdenv.mkDerivation rec { pname = "freedv"; version = "1.6.1"; src = fetchFromGitHub { owner = "drowe67"; repo = "freedv-gui"; rev = "v${version}"; sha256 = "1dzhf944vgla9a5ilcgwivhzgdbfaknqnwbpb071a0rz8rajnv0q"; }; nativeBuildInputs = [ cmake ]; buildInputs = [ codec2 libsamplerate libsndfile lpcnetfreedv portaudio speexdsp hamlib wxGTK31-gtk3 ]; cmakeFlags = [ "-DUSE_INTERNAL_CODEC2:BOOL=FALSE" "-DUSE_STATIC_DEPS:BOOL=FALSE" ]; meta = with lib; { homepage = "https://freedv.org/"; description = "Digital voice for HF radio"; license = licenses.lgpl21; maintainers = with maintainers; [ mvs ]; }; } </ins>

Discussion:
Project description Codec2 GUI for ham radio Metadata homepage URL: source URL: license: lgpl 2.1 platforms: unix, linux, darwin
Thanks!
Change:
, fetchurl , autoreconfHook , enableMail ? false <ins> , gnused </ins> , mailutils , inetutils , IOKit

Discussion:
I noticed that was failing to run warning scripts after enabling it. This appears to be caused by : Steps to reproduce the behavior: in status of smart with : successfully generated a notification. I tried to fix this in in smartmontools stops hardcoding PATH if you specify . This can be done when is false. <!-- 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.
Maybe you need ? I use this config and do get notifications (by email at least -- the machine is now headless so I don't know about the x11 notifications): And I don't have "sed: command not found" in my system log.
Do you have the set to true for  (or , which also overrides it for )? is correctly specified in that case. Is set in ? It should be located in .
I don't have in my (Unless it's being set indirectly via some other option.) I happen to have other smartmontools store paths on this machine (because it's a binary cache for my machines), with different PATH=:
Unfortunately I'm still seeing this after : This is what my looks like (the environment variables are set by overriding : I have set to false. only fixes the script bin path if is true (as far as I can tell).
Sorry I didn't see your comment on the original PR. should fix it for you.
Thanks!
Change:
substituteInPlace $out/share/applications/Mattermost.desktop  --replace /share/mattermost-desktop/mattermost-desktop /bin/mattermost-desktop <del> makeWrapper '${lib.getExe electron_28}' $out/bin/${pname}  </del> <ins> makeWrapper '${lib.getExe electron}' $out/bin/${pname}  </ins> --set-default ELECTRON_IS_DEV 0  --add-flags $out/share/${pname}/app.asar  --add-flags "''${NIXOS_OZONE_WL:+''${WAYLAND_DISPLAY:+--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations}}"

Discussion:
Steps to reproduce the behavior: mattermost-desktop Electron 28 and has it as an explicit dependency: I patched it in my own fork of nixpkgs to just use instead of hardcoding the version and that seems to work fine. Is there a reason why it is pinned to a specific electron version? <!-- 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]: