jiebi/CodeConvo huggingface dataset:
Change:
in stdenv.mkDerivation rec { pname = "briar-desktop"; <del> version = "0.3.1-beta"; </del> <ins> version = "0.4.0-beta"; </ins> src = fetchurl { <del> url = "https://desktop.briarproject.org/jars/linux/0.3.1-beta/briar-desktop-linux-0.3.1-beta.jar"; sha256 = "841dc198101e6e8aa6b5ab6bd6b80e9c6b2593cb88bc3b2592f947baf963389d"; </del> <ins> url = "https://desktop.briarproject.org/jars/linux/${version}/briar-desktop-linux-${version}.jar"; hash = "sha256-7zeIWsdPvROHGaf5igodlZss6Gow3kp6PX+QAzmxMnw="; </ins> }; dontUnpack = true;

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- 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! --- name: briar-desktop <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 0.2.1-beta desired version: 0.4.0-beta (31 January 2023) maintainers: Please tag this issue in your PR.
Change:
}: stdenv.mkDerivation rec { <del> version = "3.2.0"; </del> <ins> version = "3.3-20230626"; commit = "783141fb694f3bd1f8bd8a783670dd25a53b9fc1"; </ins> pname = "libsearpc"; src = fetchFromGitHub { owner = "haiwen"; repo = "libsearpc"; <del> rev = "v${version}"; sha256 = "18i5zvrp6dv6vygxx5nc93mai2p2x786n5lnf5avrin6xiz2j6hd"; </del> <ins> rev = commit; sha256 = "sha256-nYYp3EyA8nufhbWaw4Lv/c4utGYaxC+PoFyamUEVJx4="; </ins> }; nativeBuildInputs = [ autoreconfHook pkg-config <del> ]; buildInputs = [ </del> python3 ];

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- 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! --- name: legacyPackages.x86_64-linux.seafile-client <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 8.0.7 desired version: 8.0.10 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Change:
mkDerivation rec { pname = "gmic-qt${lib.optionalString (variant != "standalone") "-${variant}"}"; <del> version = "3.2.0"; </del> <ins> version = "3.2.1"; </ins> src = fetchFromGitHub { owner = "c-koi"; repo = "gmic-qt"; rev = "v.${version}"; <del> sha256 = "sha256-I5XC7zbDyBPFj4zul9rshoyeVV0hRQQ3aZQzEvYrgdc="; </del> <ins> sha256 = "sha256-z+GtYLBcHVufXwdeSd8WKmPmU1+/EKMv26kNaEgyt5w="; </ins> }; nativeBuildInputs = [

Discussion:
Steps to reproduce the behavior: gmic from There are more of those function arity errors, but just a small sample since they're the same. I'm going to assume pull in today has something to do with it. no maintainer? merged and it shows failures for gmic. gmic is used for me in GIMP and darktable. Please run and paste the result.
I will revert this preventively. There are many strange bugs happening.
Change:
mkDerivation rec { pname = "mixxx"; <del> version = "2.3.6"; </del> <ins> version = "2.4.0"; </ins> src = fetchFromGitHub { owner = "mixxxdj"; repo = "mixxx"; rev = version; <del> hash = "sha256-VdgCsd/7vMFUleOU0ESoZDQ8yhQSsLZADVi4XI76Ouw="; </del> <ins> hash = "sha256-JSWUzerm7D6AKq6g/9eRrt3EE2movRdM+VLUg07sLHo="; </ins> }; nativeBuildInputs = [ cmake pkg-config ];

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:
sha256 = "BVOumk2xj3vmwmm4KwiktQhWyTuUA2OFwYXNR6HgwyM="; }; <ins> preConfigure = '' substituteInPlace qt5/platforminputcontext/CMakeLists.txt  --replace $"{CMAKE_INSTALL_QT5PLUGINDIR}" $out/${qtbase.qtPluginPrefix} ''; </ins> cmakeFlags = [ "-DENABLE_QT4=0" <ins> "-DENABLE_QT6=0" </ins> ]; nativeBuildInputs = [

Discussion:
Describe the bug fcitx5 does not emerge after pressed <kbdCtrl</kbd+ <kbdSpace</kbdin qt applications. Relevant information from : Additional context IIUC, fcitx5-qt should provide as a qt plugin. However, the current output does not contain this file: Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(berberman): channels(root): nixpkgs: Maintainer information:
Change:
) fwd.loopbackIPs) forwardPorts); <del> fwdLoopDnatMap = toFwdLoopDnatMap fwdPorts; fwdLoopDnatRangeMap = toFwdLoopDnatMap fwdPortsRange; </del> # nftables set for port forward loopback snat # daddr . l4proto . dport

Discussion:
A NAT port forwarding rule fails to build with nftables when ranges are used. This is also the entirety of nix log /nix/store/sir8pvbk65zk4j6rqcj8sgwi0y78s3kc-nftables- Steps to reproduce the behavior: The nfables-rules derivation should compile. Using a single port rule, or disabling nftables results in a successful build. Please run and paste the result.
Change:
kplotting ktextwidgets mediainfo <del> mlt </del> <ins> mlt-full </ins> phonon-backend-gstreamer qtdeclarative qtmultimedia

Discussion:
kdenlive can't encode to AV1 due to missing access to libaom-av1 Steps to reproduce the behavior: a new project. → Render → Ultra-High Definition (4K) WebM-AV1/Opus (libre) is available. instead it is disabled. ! This is strange because the package appears to try an use the : I also have ffmpeg installed in my PATH with libaom-av1 support: <details<summary<code% ffmpeg -help encoder=libaom-av1</code</summary</details The exact package I am using is which is available in system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Can reproduce.
Is this related to ?
I'm not sure, but it might be that the encoding libraries are actually not limited by the that uses, but by , which uses and not .
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Yes, this seems to be the issue.
Hi there :) I updated my channels and then rebuild, and still haven't gotten this fix. It still shows the same error, as in the original screenshot. I even libaom by hand, still the same.
Which channels have you updated, and to which versions?
11 and with nix-channel --update
Ah ok, as you see the issue was reported after release of 23.11, so it is fixed only in (and the next release).
I am on NixOS unstable () and Kdenlive 24.02.2 still reports "Unsupported video codec: libaom-av1".
Yes, it seems to have regressed for me as well.
I can't easily bisect the kdenlive derivation itself as it fails to load pipewire shared libraries probably due to skew between my base system and the built kdenlive. However I ran a bisection on with the override and found to be the culprit. At first glance this seems like it should be unrelated. <details<summarybisect script</summary</details
So before this change depends on both ffmpeg 4 and 6. After this change only 6 is in the dependency graph. Maybe 4 was somehow being used and that is needed for to work?
does have libaom-av1.

So presumably something isn't working with ffmpeg 6. Reverting to 4 for now is a possible solution but likely has a lot of downsides as well.
It is worth noting that ffmpeg 6 does have libaom support. So it is possibly an incompatibility between mlt and ffmpeg.
I do see that we are linking two versions of ffmpeg. -full and non-full. So possibly what is happening is that when the other version was 4 it wasn't getting used, so full was. But now that both are 6 the wrong one happens to get used.
This fixes the issue. Maybe the best solution is updating to use the same as . However this makes me think that this isn't the best solution in general.
Created to propagate the ffmpeg version through . I don't know if this fix is the most maintainable solution, but it solves this problem and doesn't harm maintainability.
Change:
<ins> { lib , stdenv , cmake , fetchFromGitHub }: stdenv.mkDerivation rec { pname = "grpc-tools"; version = "1.10.0"; src = fetchFromGitHub { owner = "grpc"; repo = "grpc-node"; rev = "3a094f01711942f79abd8a536c45a91b574d626f"; # version 1.10.0 was not tagged sha256 = "1a7l91kxc3g7mqfqvhc3nb7zy0n21ifs5ck0qqg09qh3f44q04xm"; fetchSubmodules = true; }; sourceRoot = "source/packages/grpc-tools"; nativeBuildInputs = [ cmake ]; installPhase = '' install -Dm755 -t $out/bin grpc_node_plugin install -Dm755 -t $out/bin deps/protobuf/protoc ''; meta = with lib; { description = "Distribution of protoc and the gRPC Node protoc plugin for ease of installation with npm"; longDescription = '' This package distributes the Protocol Buffers compiler protoc along with the plugin for generating client and service objects for use with the Node gRPC libraries. ''; homepage = "https://github.com/grpc/grpc-node/tree/master/packages/grpc-tools"; license = licenses.asl20; platforms = platforms.all; maintainers = [ maintainers.nzhang-zh ]; }; } </ins>

Discussion:
Project description The repository has a number of GRPC related packages usable in the Node ecosystem. In particular the tries to bring and for generating JS code from protobuf spec. However it's using C++ code inside, and it's not really built by the . It only uses that to download a precompiled binary hosted on node-precompiled- So this package doesn't work just be overriding from output. The above does not work, with , and just produces: So we need some help packaging the C++ in Nix. Metadata homepage URL: source URL: license: APL2 platforms: unix, linux, darwin, ...
I marked this as stale due to inactivity. &rarr;
Attempting to do this with: Didn't work... Some cmake errors.
Change:
<del> {lib, stdenv, packages}: stdenv.mkDerivation { name = "xlibs-wrapper"; dontBuild = true; installPhase = "mkdir -p $out"; unpackPhase = "sourceRoot=."; propagatedBuildInputs = packages; preferLocalBuild = true; # For compatability with XFree86. passthru.buildClientLibs = true; meta = { platforms = lib.platforms.unix; }; } </del>

Discussion:
In I noticed unusual behaviour of when is overridden. That PR handles override part. But I think should just disappear. Where should be no reason (for example) for to depend on at build time. is just the wrapper around a few libraries. Quoting : Mechanically we can replace with the list of packages it provides. Even better would be to audit needed libraries for each user and use only a subset of them. Example fix: [x] perlPackages.X11Protocol: [x] pulseaudio: More packages to fix: [x] Xaw3d: [x] emacs: [x] fox16: [x] geant4: [x] [x] gtk2: [x] [x] haskellPackages.greenclip: [x] [x] lesstif: [x] monotoneViz: [x] motif: [x] mythtv: [x] ocaml- [x] [x] [x] pypy2, pypy3: [x] qgis: [x] qgis-ltr: [x] [x] qt6Packages.qtwayland: [x] rPackages.Cairo: [x] rPackages.devEMF: [x] [x] rPackages,rgl: [x] tightvnc: [x] weston: Fixed packages: [x] astromenace: [x] catclock: [x] clanlib: [x] conky: [x] elinks: [x] fox: [x] freeglut: [x] ghostscript, ghostscriptX: [x] gnome2.libgnomeui: [x] glbinding: [x] glew, glew-egl: [x] glew110: [x] imhex: [x] imlib2,

imlib2Full: [x] ion3: [x] libagar: [x] libstroke: [x] lirc: [x] mitschemeX11: [x] ncview: [x] nedit: [x] notion: [x] oneko: [x] openrw: [x] pasystray: [x] pcb: [x] povray: [x] pythonFull: [x] qemacs: [x] qmmp: [x] rss-glx: [x] scrot: [x] soxt: [x] survex: [x] synergy: [x] ted: [x] unclutter: [x] unclutter-xfixes: [x] vlc: [x] voxelands: [x] wordnet: [x] xautolock: [x] xfe: [x] x11sshaskpass: [x] xfig: [x] xidlehook: [x] xine-ui: [x] xinputcalibrator: [x] xmountains: [x] xspim: [x] xtrlock-pam: [x] xwinwrap: [x] xxgdb: [x] zoom:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
nativeBuildInputs = [ extra-cmake-modules kdoctools ]; buildInputs = [ <ins> isocodes libdbusmenu libSM libXcursor pam wayland ]; propagatedBuildInputs = [ </ins> baloo kactivities kcmutils kconfig kcrash kdbusaddons kdeclarative kdelibs4support kdesu kglobalaccel kidletime kjsembed knewstuff knotifyconfig kpackage krunner ktexteditor ktextwidgets kwallet kwayland kwin kxmlrpcclient libkscreen libksysguard networkmanager-qt phonon <del> plasma-framework qtgraphicaleffects qtquickcontrols qtquickcontrols2 qtscript qtx11extras solid isocodes libdbusmenu libSM libXcursor pam wayland </del> <ins> plasma-framework solid qtgraphicaleffects qtquickcontrols qtquickcontrols2 qtscript qtx11extras </ins> ]; patches = copyPathsToStore (lib.readPathsFromFile ./. ./series);

Discussion:
On NixOS 17.03, the in the system configuration with Plasma 5 enabled, has and in its runtime closure, which causes unnecessary bloat. This is because has: then causes the directories of and to be to the wrapper script. (Automatically adding everything with a directory to the wrapper seems pretty drastic BTW.) System: NixOS Nix version: 1.12pre5073_1cf4801
KDE upstream is slightly careless about implicit runtime dependencies. I spent hours trying to figure out which runtime dependencies needed to be in . By the way, you have to guess at this because SDDM doesn't log error messages. Could we drop ? Probably. Can I answer that question for any of the other dependencies? Not a chance. So I nuked it from orbit. Guessing the correct setting would be a good project for a first-time contributor with a lot of free time. At the moment, I'm trying to get rid of entirely. This problem may go away as a happy accident, but that won't help this release. I'm open to other suggestions.
Change:
platforms = platforms.linux; license = licenses.gpl2Plus; maintainers = with maintainers; [ zeratax donovanglover ]; <ins> mainProgram = "srb2"; </ins> }; })

Discussion:
Package name: srb2 Latest released version: 2.2.13 <!-- Search your package here: --- Current version on the unstable channel: 2.2.11 Current version on the stable/release channel: 2.2.10 <!-- 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.
Looks like there were a bunch of CMake changes so the build needs to be changed. See: Not sure how to make this work in Nix yet so it might take some time before I figure things out.
Looks like openSUSE patched 2.2.13 with these changes: Will investigate more later.
The PR hasn't been merged yet, but you can play SRB2 with the following: Feel free to leave an approving review if it works for you.
been using it for a few days now, also I don't know how to review since i've never done it before could I be pointed to the relevant docs?
Here's the . Thanks in advance!
Change:
}; }.${stdenv.system} or (throw "${pname}-${version}: ${stdenv.system} is unsupported."); <del> # Don't blame about this. WeChat requires some binary from here to work properly uosSrc = { x86_64-linux = fetchurl { url = "https://pro-store-packages.uniontech.com/appstore/pool/appstore/c/com.tencent.weixin/com.tencent.weixin_2.1.5_amd64.deb"; hash = "sha256-vVN7w+oPXNTMJ/g1Rpw/AVLIytMXI+gLieNuddyyIYE="; }; aarch64-linux = fetchurl { url = "https://pro-store-packages.uniontech.com/appstore/pool/appstore/c/com.tencent.weixin/com.tencent.weixin_2.1.5_arm64.deb"; hash = "sha256-XvGFPYJlsYPqRyDycrBGzQdXn/5Da1AJP5LgRVY1pzI="; }; loongarch64-linux = fetchurl { url = "https://pro-store-packages.uniontech.com/appstore/pool/appstore/c/com.tencent.weixin/com.tencent.weixin_2.1.5_loongarch64.deb"; hash = "sha256-oa6rLE6QXMCPlbebto9Tv7xT3fFqYIlXL6WHpB2U35s="; }; }.${stdenv.system} or (throw "${pname}-${version}: ${stdenv.system} is unsupported."); </del> inherit uosLicense; nativeBuildInputs = [ dpkg ];

Discussion:
the package wechat uos is still using OpenSSL 1.1 which is end of life on 2023/09/11, so it is marked as insecure now. not sure if we need to wait for wechat-uos or we can just bump it up in here. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
As far as I know, only from depends on OpenSSL 1.1. Seems like we may replace it with to completely remove dependency. I will try to fix that in the next PR when I have free time.
Would it be offensive if I could submit a patch about it now.
Feel free to do so. I would be happy to review your pr :)
Change:
openmodelica = recurseIntoAttrs (callPackage ../applications/science/misc/openmodelica {}); <ins> prowlarr = callPackage ../servers/prowlarr { }; </ins> qarte = libsForQt5.callPackage ../applications/video/qarte { }; qlcplus = libsForQt5.callPackage ../applications/misc/qlcplus { };

Discussion:
Project description Prowlarr is an indexer manager/proxy built on the popular arr .net/reactjs base stack to integrate with your various PVR apps. Prowlarr supports management of both Torrent Trackers and Usenet Indexers. Metadata homepage URL: source URL: license: GPL 3 platforms: Unix
I would like to package this software but I am still trying to learn how to properly create derivations as I have never done one. Help / guidance appreciated!
I have a WIP PR for this against my fork The package builds fine, but I am still trying to figure out how to test the NixOS module in my dotfiles repo using flakes and overlays :sweat_smile:
I actually got this working much quicker than expected. Here is my PR to this repo
Thank you very much
Change:
<del> { lib, stdenv, fetchFromGitHub </del> <ins> { lib , stdenv , fetchFromGitHub , cmake </ins> }: stdenv.mkDerivation rec {

Discussion:
llama build uses pkg-config to discover the include path of opencl-header. Sadly, the current package only copies the headers files, not the pc file. It is supposed to be generated by cmake from a , but we currently do not call it. I would happily propose a patch but the interactions between cmake, nix and pkg-config is out of my league :) Thanks for looking into it!
Change:
<del> { lib, stdenv, fetchgit, flex, bison, python3, autoconf, automake, gnulib, libtool </del> <ins> { lib, stdenv, fetchurl, flex, bison, python3, autoreconfHook, gnulib, libtool, bash </ins> , gettext, ncurses, libusb-compat-0_1, freetype, qemu, lvm2, unifont, pkg-config , buildPackages , fetchpatch

Discussion:
After upgrading to 21.05, when running , I get the following warning: Everything else seems to work fine, but it's unclear what has gone wrong here, or if I should be worried. Metadata Maintainer information:
discussed here a bit you can safely ignore it to hide it we could add to the or to
Not sure if my case is related, but I had the same error after : The overall install didn't error. Attempting to reboot, it would be unable to boot:
My boot got fixed after converting my MBR to GPT and creating an ESP partition and setting it to use systemd-boot instead of GRUB. If GRUB continues to work with people that see this warning, it's unlikely that my boot problems are related. (But, still, a different bug; if MBR got deprecated, there should have been an announcement.)
But the issue is quite severe (I just lost hours on it because it happened on a remote server which boots very slowly on a web-mounted rescue iso), and I could only get my system running again by reverting to . I'd propose to throw out the new version () for now. I can't do GPT, because the system only has a legacy BIOS (no UEFI), it appears that this is the reason this issue has flown under the radar? Same error referenced , it appears to be an issue with the grub package itself. EDIT: since OP defined a "parallel" but much less severe bug, I made a new report here:
Change:
sha256 = "1lvb14qclrx0qf6qqx8a8hkx5akk5lk3dvcqz8760v9hya52pnfv"; }; }); <ins> guessit = super.guessit.overridePythonAttrs (old: rec { version = "2.1.4"; src = old.src.override { inherit version; sha256 = "90e6f9fb49246ad27f34f8b9984357e22562ccc3059241cbc08b4fac1d401c56"; }; }); </ins> }; in

Discussion:
Flexget refused to work after upgrade. I noticed the problem was guessit. Having a look at the .nix files I noticed that was actually updated to use guessit 3.0. However guessit 3.0 uses different stuff and flexget breaks when using guessit 3.0. For me, I can't really understand why a file named uses guessit 3.0. Try to install and run flexget from nixos unstable or nixos unstable small. Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(hyper): channels(root): nixpkgs:
Can you please check whether fixes your problem?
That's because of an accidental version update. I'm merging because it's a step in the right direction and closing this.
yep, that works fine now. Thx
Change:
patchShebangs ompi/mpi/fortran/base/gen-mpi-sizeof.pl ''; <ins> postInstall = '' rm -f $out/lib/*.la ''; </ins> meta = { homepage = http://www.open-mpi.org/; description = "Open source MPI-2 implementation";

Discussion:
openmpi nix package do not strip the .la files coming from libtool. This generate dependency issues for other project using libtool and nix, due to libtool trying to link against the dependencies of openmpi itself ( e.g libibverbs ) when it should not. This issue has been encountered here It is a general good practice to strip libtool .la file in package. System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )
closed with
Change:
{ lib , stdenvNoCC <del> , fetchurl </del> <ins> , requireFile </ins> , undmg , pname , version

Discussion:
Steps to reproduce the behavior: 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. -- system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
there is now a captcha on the page at "" <img width="381" alt="image" src=""
Looks like it's the original website request captcha, I've submitted a PR to prompt it.
The captcha seems to have been removed.
Change:
<ins> { lib , rustPlatform , fetchFromGitHub , cmake , pkg-config , expat , fontconfig , freetype }: rustPlatform.buildRustPackage rec { pname = "cicero-tui"; version = "0.1.4"; src = fetchFromGitHub { owner = "eyeplum"; repo = "cicero-tui"; rev = "v${version}"; sha256 = "1bz2y37qf9c3fxc73chb42rffdivp5krczhgd9rnwq5r6n6bdgq7"; }; nativeBuildInputs = [ cmake pkg-config ]; buildInputs = [ expat fontconfig freetype ]; cargoSha256 = "04359gf9mirczqwh8jv3rf0cc4pp05r8ncqyz0n8r7x5qv77kgcp"; meta = with lib; { description = "Unicode tool with a terminal user interface"; homepage = "https://github.com/eyeplum/cicero-tui"; license = with licenses; [ gpl3Plus ]; maintainers = with maintainers; [ shamilton ]; platforms = platforms.linux; }; } </ins>

Discussion:
Project description Unicode tool with a terminal user interface. (similar in functionality to fontfor, see ) Metadata homepage URL: source URL: license: GPLv3 platforms: linux, darwin