jiebi/CodeConvo huggingface dataset:
Change:
<ins> import ../make-test-python.nix ({pkgs, ...}: { name = "php-httpd-test"; meta.maintainers = with pkgs.stdenv.lib.maintainers; [ etu ]; machine = { config, lib, pkgs, ... }: { services.httpd = { enable = true; adminAddr = "admin@phpfpm"; virtualHosts."phpfpm" = let testdir = pkgs.writeTextDir "web/index.php" "<?php phpinfo();"; in { documentRoot = "${testdir}/web"; locations."/" = { index = "index.php index.html"; }; }; enablePHP = true; }; }; testScript = { ... }: '' machine.wait_for_unit("httpd.service") # Check so we get an evaluated PHP back response = machine.succeed("curl -vvv -s http://127.0.0.1:80/") assert "PHP Version ${pkgs.php.version}" in response, "PHP version not detected" # Check so we have database and some other extensions loaded for ext in ["json", "opcache", "pdo_mysql", "pdo_pgsql", "pdo_sqlite"]: assert ext in response, f"Missing {ext} extension" ''; }) </ins>

Discussion:
Describe the bug When I enable PHP in httpd using , the file when visited can only see 11 extensions instead of the 52 I get when I run it through php CLI command. To Reproduce A failing NixOS test: Additional context Likely caused by the great refactor: Notify maintainers
Yep, the refactor relies on a configuration file with all the extensions to load being present and specified. For the binary, we have a wrapper that just tells PHP to look in the right folder for the config, but with the module, it looks like that's not used, since it loads PHP as an extension. The solution would probably be to inherit the config from the package as the first thing put into the it already generates; it should be accessible as .
Change:
passthru = { incdir = "/avr/include"; <del> libdir = "/avr/lib"; </del> }; meta = with lib; {

Discussion:
Steps to reproduce the behavior: on any platform () n/a Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Broken by .
Ping (author), (committer).
might fix it? Will test when I'm home tonight.
Can confirm that it will fix this.
Yes, because part of is reverting the offending commit.
Change:
libDir = "share/ghcjs/${ghcArch}-${version}-${ghc.version}/ghcjs"; ghcjsBoot = fetchgit { url = git://github.com/ghcjs/ghcjs-boot.git; <del> rev = "8bf1a2c665d42a66354f17220c7dfb1c8b44c0ea"; # 7.10 branch sha256 = "18bm6sfa9c9kwsmv3lz6j27ng6jl0ck3ifgqbwwa8myfy7fw4il7"; </del> <ins> rev = "ab8765edcb507b8b810e3c324fd5bd5af2b69d8f"; # 7.10 branch sha256 = "63b69a1d131cf3c7088e0f28d14750c81361dcc276fa113ad80dcccf73df5343"; </ins> fetchSubmodules = true; }; shims = fetchgit {

Discussion:
someone has push -f'ed a ghcjs-boot subrepo and the current commit commited to file is no longer buildable. i am submitting a pr with my proposed solution atm
Change:
"${cfg.package}/lib/systemd/systemd-fsck" "${cfg.package}/lib/systemd/systemd-hibernate-resume" "${cfg.package}/lib/systemd/systemd-journald" <del> (lib.mkIf needMakefs "${cfg.package}/lib/systemd/systemd-makefs") </del> <ins> "${cfg.package}/lib/systemd/systemd-makefs" </ins> "${cfg.package}/lib/systemd/systemd-modules-load" "${cfg.package}/lib/systemd/systemd-remount-fs" "${cfg.package}/lib/systemd/systemd-shutdown"

Discussion:
currently has a conditional: is defined as this: However, this is only one part of the picture. I can also add the option to a entry to cause a dependency on (or just do it explicitly by ). ~ is also missing entirely~ dealt with online in stage 2 I think we should ship by default with systemd-in-initrd. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This is intentional: systemd-growfs is an online operation. We do it during stage 2 when is enabled.
oh, but I see, you're saying we should add in case users add the fstab option themselves and don't use the NixOS option. I think that makes sense. The point of the previous comment stands though; growfs is intentionally not in stage 1.
Makes sense, and I even reviewed this PR :laughing: sorry. Yes, in case the fstab options contain we should also (or just add it unconditionally)
Yea, I don't mind adding it unconditionally. It's a negligible size increase, and I think there's ways to trigger its use on the cmdline anyway.
PR up at
Change:
buildKodiBinaryAddon rec { pname = "inputstream-ffmpegdirect"; namespace = "inputstream.ffmpegdirect"; <del> version = "20.5.0"; </del> <ins> version = "unstable-20.5.0"; </ins> src = fetchFromGitHub { owner = "xbmc"; repo = "inputstream.ffmpegdirect"; <del> rev = "${version}-${rel}"; sha256 = "sha256-2Xa5q+o/AYDwG+JYeXTUfMTJk/kln16J8KRcXILNE6c="; </del> <ins> rev = rel; sha256 = "sha256-+u28Wzp2TonL5jaa5WJUr9igR6KiaxizZAX9jqqBUns="; </ins> }; extraBuildInputs = [ bzip2 zlib kodi.ffmpeg ];

Discussion:
Steps to reproduce the behavior: kodi-inputstream-ffmpegdirect on the unstable channel log here if short otherwise a link to a gist ` 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. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
upstream fix:
Change:
{ stdenv, lib, makeDesktopItem , unzip, libsecret, libXScrnSaver, libxshmfence, wrapGAppsHook <del> , gtk2, atomEnv, at-spi2-atk, autoPatchelfHook </del> <ins> , atomEnv, at-spi2-atk, autoPatchelfHook </ins> , systemd, fontconfig, libdbusmenu, glib, buildFHSUserEnvBubblewrap , writeShellScriptBin

Discussion:
Describe the bug Running on vscode binary says that it depends only on gtk3: While the package depends on both gtk2 and gtk3: Probably there are some packaging issue? To Reproduce Steps to reproduce the behavior: vscode Expected behavior It depends only on gtk3 Notify maintainers Metadata Maintainer information:
Also gconf vs. dconf and libgnome-keyring vs. libsecret. See also
Hmm yeah, I removed and from , and both vscode and vscodium seem to still run fine. Not sure where the gconf/dconf thing is determined, possibly that that's an Atom issue
libsecret is the replacement for libgnome-keyring, not the other way around. It will probably be used at runtime when it needs to access keyring. dconf is used by GTK, gconf should not be used at all.
I marked this as stale due to inactivity. &rarr;
Still an issue
Change:
inherit (lib) optionals types <del> concatLists mapAttrsToList </del> mkOption ;

Discussion:
has an assertion on enableSSL that requires certFile, keyFile, and caFile, but caFile is optional with SSL and only used for client certificate validation. ttyd is able to serve over SSL with valid certificates Steps to reproduce the behavior: builds with the provided options Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've committed a fixed file to my own flake that fixes the assertion (as well as adding the "--ssl" flag, which was missing)
please view
Change:
pycritty = with python3Packages; toPythonApplication pycritty; <del> qtcreator = libsForQt5.callPackage ../development/tools/qtcreator { }; </del> <ins> qtcreator = libsForQt5.callPackage ../development/tools/qtcreator { inherit (linuxPackages) perf; }; </ins> qxmledit = libsForQt5.callPackage ../applications/editors/qxmledit {} ;

Discussion:
Describe the bug Qt Creator profiling tools are not working because of a missing prerequisite: . To Reproduce Steps to reproduce the behavior: Qt Creator with a simple C/C++ project the Analyze menu choose the Performance Analyzer command get the following error: is indeed missing. Expected behavior The program gets profiled. Notify maintainers Metadata Please run and paste the result.
For what it's worth, on a different distro I had this same problem which was resolved by installing elfutils-devel and then recompiling qt-creator. The build silently skips building this tool if this dependency is absent.
I marked this as stale due to inactivity. &rarr;
still an issue
would you be able to point me in the general direction of making this happen on NixOS?
Test
I still get "Could not start the perfparser utility program. Make sure a working Perf parser is available at the location given by the PERFPROFILERPARSERFILEPATH environment variable."
try now
updated, cancel the build and try again
... I still get "Could not start the perfparser utility program. Make sure a working Perf parser is available at the location given by the PERFPROFILERPARSERFILEPATH environment variable." What am I doing wrong?
Which channel are you following, if unstable then have you updated
I'm using from (which is the first commit that includes the patch)
try this
It still doesn't work for me :(
looks like perfparser is actually a program built by qtcreator i've switched the pr to be a update pr so that we get perfparser
Change:
makeFlags = [ "local=1" "VC=${vc}" <del> # vlang seems to want to write to $HOME/.vmodules , so lets give # it a writable HOME "HOME=$TMPDIR" </del> ]; <ins> prePatch = '' export HOME=$(mktemp -d) cp cmd/tools/vcreate_test.v $HOME/vcreate_test.v ''; </ins> installPhase = '' runHook preInstall mkdir -p $out/{bin,lib,share} cp -r examples $out/share cp -r {cmd,vlib,thirdparty} $out/lib <del> mv v $out/lib </del> <ins> cp v $out/lib </ins> ln -s $out/lib/v $out/bin/v wrapProgram $out/bin/v --prefix PATH : ${lib.makeBinPath [ stdenv.cc ]} <ins> mkdir -p $HOME/.vmodules; ln -sf ${markdown} $HOME/.vmodules/markdown $out/lib/v -v build-tools $out/lib/v -v $out/lib/cmd/tools/vdoc $out/lib/v -v $out/lib/cmd/tools/vast $out/lib/v -v $out/lib/cmd/tools/vvet # Return the pre-patch vcreate_test.v now that we no longer need the alteration. cp $HOME/vcreate_test.v $out/lib/cmd/tools/vcreate_test.v </ins> runHook postInstall '';

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: <!-- 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: weekly.2021.51 desired version: weekly.2022.19 maintainers: Could some sort of auto-updater be in for this?
Current PR regarding this is
I saw that PR, but for some of my projects I need the latest version as it has some features I need. Thought I'd make an issue. What about auto-updating, btw?
I'm not sure, superficially I think it would be okay though. vlang is rather fast-moving, and that's both a good reason to auto-update, and a bad reason as there may be breaking changes regarding packaging it.
Yeah, good point. I still think that auto-updating is just a good idea so that issues like this don't have to be created.
Change:
, vala , gobject-introspection , gnome <ins> , gtk-mac-integration </ins> }: stdenv.mkDerivation rec {

Discussion:
Project description CherryTree by Giuspen, currently, we are using version 0.39.4, meanwhile the latest application is on 0.99.37. There's a weird jump of version from 0.39.4 to 0.99.13. I don't know why this happens. Metadata homepage URL: source URL: license: GPL3 + platforms: Linux
Package request is the wrong issue type for this, Out-of-date package report would've been better. ! The package is sadly orphaned so there's no maintainer to ping for this.
Change:
''; license     = licenses.gpl2; maintainers = [ maintainers.matthiasbeyer ]; <del> platforms   = platforms.linux; </del> <ins> platforms   = platforms.unix; </ins> }; }

Discussion:
is currently set to just , but I was able to build it fine with on macos (10.14.3) and haven't run into any issues running very basic commands so far.
Would you mind making a pull request?
I don't, but I'm not in the loop and won't be of much use if it's any more involved than changing it to .
So perhaps should be just .
Change:
<del> --- old/source/Makefile	2014-05-05 23:22:48.051952484 +0200 +++ new/source/Makefile	2014-05-05 23:20:46.576617833 +0200 @@ -71,6 +71,9 @@ GAME = crawl + +CFLAGS := $(NIX_CFLAGS_COMPILE) + # Disable GNU Make implicit rules and variables. Leaving them enabled will slow # down MinGW and Cygwin builds by a very VERY noticeable degree. Besides, we have # _explicit_ rules defined for everything. So we don't need them. @@ -979,7 +983,7 @@ ifdef ANDROID CFLAGS   := $(CFOPTIMIZE) $(CFOTHERS) $(CFWARN) $(CFLAGS) else -CFLAGS   := $(CFOPTIMIZE) $(CFOTHERS) $(CFWARN) +CFLAGS   := $(CFOPTIMIZE) $(CFOTHERS) $(CFWARN) $(CFLAGS) endif CFLAGS_L := $(CFOPTIMIZE_L) $(DEFINES_L) $(CFWARN_L) $(INCLUDES_L) $(CFOTHERS_L) ALL_CFLAGS := $(CFLAGS) $(CFLAGS_L) @@ -1392,7 +1396,7 @@ $(RM) -r $(DOXYGEN_HTML_GEN) $(GAME): $(OBJECTS) $(EXTRA_OBJECTS) $(CONTRIB_LIBS) dat/dlua/tags.lua -	+$(QUIET_LINK)$(CXX) $(LDFLAGS) $(EXTRA_OBJECTS) $(OBJECTS) -o $(GAME) $(LIBS) +	g++ $(LDFLAGS) $(EXTRA_OBJECTS) $(OBJECTS) -o $(GAME) $(LIBS) debug: all debug-lite: all @@ -1492,7 +1496,7 @@ $(QUIET_GEN)util/gen-luatags.pl mi-enum.h: mon-info.h util/gen-mi-enum -	$(QUIET_GEN)util/gen-mi-enum +	perl util/gen-mi-enum $(RLTILES)/dc-unrand.txt: art-data.h </del>

Discussion:
Here is the output from nixos-rebuild: I'm not sure if this is a known issue or not, but I made sure to upgrade as well and it is still failing.
Change:
{ lib, stdenv, fetchurl, zlib, interactive ? false, readline ? null, ncurses ? null , python3Packages <ins> , enableDeserialize ? false </ins> }: assert interactive -> readline != null && ncurses != null;

Discussion:
, CVSSv3=7.5 (nixos-unstable) Fossil before 2.14.2 and 2.15.x before 2.15.2 often skips the hostname check during TLS certificate validation. Scanned versions: nixos-unstable: . Cc Cc
Change:
<del> { lib , stdenv , callPackage , fetchFromGitHub , testers , enableE57 ? lib.meta.availableOn stdenv.hostPlatform libe57format , cmake , curl , gdal , hdf5-cpp , LASzip , libe57format , libgeotiff , libtiff , libxml2 , openscenegraph , pkg-config , postgresql , tiledb , xercesc , zlib , zstd }: stdenv.mkDerivation (finalAttrs: { pname = "pdal"; version = "2.5.6"; src = fetchFromGitHub { owner = "PDAL"; repo = "PDAL"; rev = finalAttrs.version; sha256 = "sha256-JKwa89c05EfZ/FxOkj8lYmw0o2EgSqafRDIV2mTpZ5E="; }; nativeBuildInputs = [ cmake pkg-config ]; buildInputs = [ curl gdal hdf5-cpp LASzip libgeotiff libtiff libxml2 openscenegraph postgresql tiledb xercesc zlib zstd ] ++ lib.optionals enableE57 [ libe57format ]; cmakeFlags = [ "-DBUILD_PLUGIN_E57=${if enableE57 then "ON" else "OFF"}" "-DBUILD_PLUGIN_HDF=ON" "-DBUILD_PLUGIN_PGPOINTCLOUD=ON" "-DBUILD_PLUGIN_TILEDB=ON" "-DWITH_TESTS=ON" "-DBUILD_PGPOINTCLOUD_TESTS=OFF" # Plugins can probably not be made work easily: "-DBUILD_PLUGIN_CPD=OFF" "-DBUILD_PLUGIN_FBX=OFF" # Autodesk FBX SDK is gratis+proprietary; not packaged in nixpkgs "-DBUILD_PLUGIN_GEOWAVE=OFF" "-DBUILD_PLUGIN_I3S=OFF" "-DBUILD_PLUGIN_ICEBRIDGE=OFF" "-DBUILD_PLUGIN_MATLAB=OFF" "-DBUILD_PLUGIN_MBIO=OFF" "-DBUILD_PLUGIN_MRSID=OFF" "-DBUILD_PLUGIN_NITF=OFF" "-DBUILD_PLUGIN_OCI=OFF" "-DBUILD_PLUGIN_RDBLIB=OFF" # Riegl rdblib is proprietary; not packaged in nixpkgs "-DBUILD_PLUGIN_RIVLIB=OFF" ]; doCheck = true; disabledTests = [ # Tests failing due to TileDB library implementation, disabled also # by upstream CI. # See: https://github.com/PDAL/PDAL/blob/bc46bc77f595add4a6d568a1ff923d7fe20f7e74/.github/workflows/linux.yml#L81 "pdal_io_tiledb_writer_test" "pdal_io_tiledb_reader_test" "pdal_io_tiledb_time_writer_test" "pdal_io_tiledb_time_reader_test" "pdal_io_tiledb_bit_fields_test" "pdal_io_e57_read_test" "pdal_io_e57_write_test" "pdal_io_stac_reader_test" # Segfault "pdal_io_hdf_reader_test" # Failure "pdal_app_plugin_test" ]; checkPhase = '' runHook preCheck # tests are flaky and they seem to fail less often when they don't run in # parallel ctest -j 1 --output-on-failure -E '^${lib.concatStringsSep "|" finalAttrs.disabledTests}$' runHook postCheck ''; passthru.tests = { version = testers.testVersion { package = finalAttrs.finalPackage; command = "pdal --version"; version = "pdal ${finalAttrs.finalPackage.version}"; }; pkg-config = testers.testMetaPkgConfig finalAttrs.finalPackage; }; meta = with lib; { description = "PDAL is Point Data Abstraction Library. GDAL for point cloud data"; homepage = "https://pdal.io"; license = licenses.bsd3; maintainers = teams.geospatial.members; platforms = platforms.all; pkgConfigModules = [ "pdal" ]; }; }) </del>

Discussion:
Steps to reproduce the behavior: with latest master branch is building with the older version of (2.5), because it can't build with the latest version (see: ). Build of started to fail after recent update to version . Notify Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
check-jsonschema = callPackage ../development/tools/check-jsonschema { }; <del> pypi2nix = callPackage ../development/tools/pypi2nix { }; </del> pypi-mirror = callPackage ../development/tools/pypi-mirror { }; setupcfg2nix = python3Packages.callPackage ../development/tools/setupcfg2nix { };

Discussion:
Steps to reproduce the behavior: Command should execute without an error None? Please run and paste the result.
Change:
<ins> { stdenv , buildGoModule , fetchFromGitHub }: buildGoModule rec { pname = "gdu"; version = "2.0.0"; src = fetchFromGitHub { owner = "dundee"; repo = pname; rev = "v${version}"; sha256 = "0239ppiilr8d43z9v27c9h7b5xkj2n9aacpf5a0h3rz4j0dkcwf7"; }; vendorSha256 = "1jqbsda9bch3awdq816w4jybv7wz9mfflmvs5y2wsa2qnhn9nbyp"; meta = with stdenv.lib; { description = "Disk usage analyzer with console interface"; longDescription = '' Gdu is intended primarily for SSD disks where it can fully utilize parallel processing. However HDDs work as well, but the performance gain is not so huge. ''; homepage = "https://github.com/dundee/gdu"; license = with licenses; [ mit ]; maintainers = [ maintainers.fab ]; platforms = platforms.unix; }; } </ins>

Discussion:
Project description Pretty fast disk usage analyzer written in Go. Gdu is intended primarily for SSD disks where it can fully utilize parallel processing. However HDDs work as well, but the performance gain is not so huge. Metadata homepage URL: source URL: license: mit, platforms: Linux
Change:
dictd = 105; couchdb = 106; #searx = 107; # dynamically allocated as of 2020-10-27 <del> kippo = 108; </del> <ins> #kippo = 108; # removed 2021-10-07, the kippo package was removed in 1b213f321cdbfcf868b96fd9959c24207ce1b66a during 2021-04 </ins> jenkins = 109; systemd-journal-gateway = 110; #notbit = 111; # unused

Discussion:
kippo is an SSH honeypot service, here is the module definition: And of course, it needs the kippo package : But now the module is broken because the was removed : ( Here is the commit: and corresponding PR: Should we remove the broken module or re-pachaging the ...? Steps to reproduce the behavior: line to error log says is not exists. I'm not found any maintainers from the module, the deleted package's maintainer is Maintainer information:
I am no longer a regular user of kippo so i didn't mind if the module is deprecated along with the package.
Maybe I can make a PR to remove the module, sorry for bothering you.
Change:
# again when it deletes link-local addresses.) Ideally we'd # turn off the DHCP server, but qemu does not have an option # to do that. <del> my $startCommand = "qemu-kvm -m 768"; </del> <ins> my $startCommand = "qemu-kvm -m 1024"; </ins> $startCommand .= " -device virtio-net-pci,netdev=vlan0"; $startCommand .= " -netdev 'user,id=vlan0,net=169.0.0.0/8,guestfwd=tcp:169.254.169.254:80-cmd:${pkgs.micro-httpd}/bin/micro_httpd ${metaData}'"; $startCommand .= " -drive file=$diskImage,if=virtio,werror=report";

Discussion:
Describe the bug On current master (), the ec2 tests don't work: Expected behavior They should work in order to be portable to python, see CCing contributors who wrote/touched this code:
Change:
<del> { lib, stdenv, fetchFromGitHub, python39 }: </del> <ins> { lib, stdenv, fetchFromGitHub, fetchpatch, python3 }: </ins> stdenv.mkDerivation { pname = "monoid";

Discussion:
Steps to reproduce the behavior: nixos from flake on with the current unstable commit with steam enabled () Sorry I can't figure out a better way to pair this down since the standard nix-build command for this seems to still work fine. full log The previous head of unstable that I can find () has this failure happen as well. Previous commit seems to be the most recent one where my systems seems to continue to build. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi, thanks for the report. Adding the specific commits helped a lot. I'm able to reproduce by building the attribute, which is required by the Monoid font. Every other configuration of fontforge seems to be unaffected. Monoid seems to be unable to build with a more recent Python version, pinging the maintainer:
Is it possible that you have the Monoid font installed manually? I can't find any other reference to it in Nixpkgs. I'll likely have to restrict Fontforge to not build with Python 3.9, which is just going to break that font and similar packages.
This insight is great! How you were able to estimate that the installation of monoid might the problem here? I was stuck since weeks to not be able to upgrade on flake based rolling release against unstable, since everytime i failed in the python312Packages.fontforge package to build. Removing monoid from requested fonts did solve the topic here, thanks a lot!
Happy to be of help :) I noticed it as a reverse dependency in the build log posted and then saw that it directly depended on fontforge.
Change:
hash = "sha256-AYH9fW20/p+mq6lxR1lcCV1BQ/kgcsjHncpMvYWXnWA="; }; <del> # Propagate sddm theme dependencies to user env otherwise sddm does # not find them. Putting them in buildInputs is not enough. propagatedUserEnvPkgs = [ kdeclarative.bin plasma-framework plasma-workspace ]; </del> <ins> outputs = [ "out" "sddm" ]; </ins> postPatch = '' patchShebangs install.sh

Discussion:
shouldn't install KDE Plasma as a dependency, it can be used with Kvantum Steps to reproduce the behavior: dependencies with Kvantum and KDE Plasma should be optional dependencies of . I recently noticed that KDE Plasma was installed on my system for no reason, after some research I found the culprit, Colloid-kde installs the entire desktop environment as a dependency. I use this theme with and so I don't need KDE.
It is not a bug. Without the dependencies the sddm theme does not work.
Maybe one solution in order to avoid those kde dependencies needed only for the sddm theme is to have a separate output for the sddm theme, and keep the dependencies only for it. Something like what is already done for (the nordic sddm theme).
Change:
in buildPythonApplication rec { pname = "ocrmypdf"; <del> version = "12.3.0"; </del> <ins> version = "12.5.0"; </ins> src = fetchFromGitHub { owner = "jbarlow83"; repo = "OCRmyPDF"; rev = "v${version}"; <del> sha256 = "122yv3p0v4fbx30zgppcznwnm7svg97gv0sa103xb6zcld68ggn2"; </del> <ins> sha256 = "sha256-g80WedX+TGHE9EJ/RSgOc53PM17V3WZslUNaHoqKTo0="; </ins> }; nativeBuildInputs = with python3Packages; [

Discussion:
ocrmypdf in versions <12.4.0 has a dependency on pluggy <1.0, but pluggy in nixpkgs-unstable is 1.0.0 as of . ocrmypdf on latest unstable fails with: build succeeds Ocrmypdf as of 12.4.0 has validated that it's compatible with pluggy=1.0: As of 12.5.0, it has a build failure fixed with pikepdf 3.0 (see ) on an old python: Please run and paste the result. Maintainer information: