jiebi/CodeConvo huggingface dataset:
Change:
meta.homepage = "https://github.com/steelsojka/pears.nvim/"; }; <ins> persisted-nvim = buildVimPlugin { pname = "persisted.nvim"; version = "2024-04-04"; src = fetchFromGitHub { owner = "olimorris"; repo = "persisted.nvim"; rev = "ca9900c31ee6e254a0ba7011ba49f48ebf4c8db2"; sha256 = "0s9g1jmq1qzkxi1gcvmyf0nmwgqrh11r0swy9pl32916k37zvqzl"; }; meta.homepage = "https://github.com/olimorris/persisted.nvim/"; }; </ins> persistence-nvim = buildVimPlugin { pname = "persistence.nvim"; version = "2023-10-15";

Discussion:
Project description <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
type = types.str; description = '' Name of the config adapter to use. <del> See https://caddyserver.com/docs/config-adapters for the full list. </del> <ins> See <link xlink:href="https://caddyserver.com/docs/config-adapters"/> for the full list. <note><para> Any value other than <literal>caddyfile</literal> is only valid when providing your own <option>configFile</option>. </para></note> </ins> ''; };

Discussion:
Describe the bug When i try to import a config file, i get an error: When i copy the exact same text in , it does work. The file does exist and i can read it, even with the caddy user! So this seem to be a bug. To Reproduce Steps to reproduce the behavior: ... ... ... Expected behavior A clear and concise description of what you expected to happen. Additional context Add any other context about the problem here. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Without knowing anything about my first guess would be this: Is it possible this command is evaluating your configuration? If so, the issue is that the command is being run sandboxed so has no access outside the sandbox to your file. Build time commands can be tough.
That would make sense. So NixOS brakes the import feature.
Out of curiosity can you please paste your relevant config?
what exactly do you want to see? For a workaround, i just copied everything into the NixOS option: But in some cases, it's nice to have the webserver config. together with the website sourcecode:
Thanks for posting. The context helps. I think this is what you want:
It could make sense to add an off-by-default option to opt-out build-time configuration check.
Given my above solution, I'm not sure what value it would offer in this scenario. What scenario did you have in mind Can this config file hold secrets maybe?
Then you don't have to use such a workaround on NixOS and can just use it as described in it's documentation. There can be secrets in it, but i don't see how that's relevant here:
Hi, module maintainer here. I was the person who made the original PR for adapting s for Caddy 2, and I had no idea about the directive at the time. The motivation was to generate TLS settings from the module options and merge them with JSON-ified . Please use as suggested for now, and I'll see how I can make this easier in the future.
I marked this as stale due to inactivity. &rarr;
Change:
, libXxf86vm , libGL , nixosTests <ins> , buildGoModule </ins> }: <del> stdenv.mkDerivation rec { </del> <ins> buildGoModule rec { </ins> pname = "darktile"; <del> version = "0.0.10"; </del> <ins> version = "0.0.11"; </ins> src = fetchFromGitHub { owner = "liamg"; repo = "darktile"; rev = "v${version}"; <del> sha256 = "0pdj4yv3qrq56gb67p85ara3g8qrzw5ha787bl2ls4vcx85q7303"; </del> <ins> hash = "sha256-M3vySAyYwqscR9n0GGXp1ttO/mhdSCponZNYJRBBI18="; </ins> }; <del> nativeBuildInputs = [ go pkg-config ]; </del> <ins> vendorHash = null; nativeBuildInputs = [ pkg-config ]; </ins> buildInputs = [ libX11

Discussion:
Package name: darktile Latest released version: 0.0.11 <!-- Search your package here: --- Current version on the unstable channel: 0.0.10 Current version on the stable/release channel: 0.0.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.
Hi! Unfortunately, I'm no longer using NixOS. It should still be pretty trivial to create a PR, but I won't be able to test it. If I create a draft PR for this, will you be willing to download it and test whether it works?
Also, I'd appreciate it if you became the maintainer of this package instead of me (only if you want to, of course). There are pretty much no updates to it, so you'll rarely have to do anything
Sure, I would be happy to test the draft PR and become the maintainer of the package. Please let me know if there's anything else you need from me to proceed.
ok, well, foremost, it seems like the hash of the package can't get obtained on systems without Nix. Could you please run and post the output here?
Sure. Here:
I opened a draft PR which updates the package and makes you the maintainer. Please test if the updated package works.
Change:
, mesa-demos , pciutils , udev <ins> , vulkan-loader </ins> , libusb1 , msaClientID ? null

Discussion:
If you try to use in Minecraft it will fail to open, as the package seems to expect the game to only need OpenGL I assume at least. I think to fix this the package needs to be included in the build. Since this is a mod it doesn't effect the base game, so adding support for this might be debatable but I would like to see it work to compare the renderers and try RT mods that uses hardware RT. Steps to reproduce the behavior: Vulkan mod to run the game that it crashes and cannot find vulkan-loader The game loads with Vulkan mod installed The error: Tried this as well but didn't work due to a build error, likely user error on my part Also, I imagine that this effects Multimc so it's package should be updated as well. I have also tested on the unwrapped package, same issue there as well :/ <!-- 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]:
First of all, to add additional libraries to the game's search path, you need to override . After I did that, I was getting a SIGSEGV from though.
Mod loads for me with the following
This works for me too, I guess this can be closed in favor of the MR
Change:
]; doCheck = stdenv.isDarwin;  # TODO: a couple tests still fail on *-linux internalDeps = [ php.extensions.session ]; <del> patches = lib.optionals (lib.versions.majorMinor php.version == "8.2" && lib.versionOlder php.version "8.2.22") [ </del> <ins> patches = lib.optionals (lib.versions.majorMinor php.version == "8.1") [ # Fix tests with libxml2 2.12 (fetchpatch { url = "https://github.com/php/php-src/commit/061058a9b1bbd90d27d97d79aebcf2b5029767b0.patch"; hash = "sha256-0hOlAG+pOYp/gUU0MUMZvzWpgr0ncJi5GB8IeNxxyEU="; excludes = [ "NEWS" ]; }) # Backport of PHP_LIBXML_IGNORE_DEPRECATIONS_START and PHP_LIBXML_IGNORE_DEPRECATIONS_END # Required for libxml2 2.13 compatibility patch. ../development/interpreters/php/php81-fix-libxml2-2.13-compatibility.patch # Fix build with libxml2 2.13+. Has to be applied after libxml2 2.12 patch. (fetchpatch { url = "https://github.com/php/php-src/commit/9b4f6b09d58a4e54ee60443bf9a8b166852c03e0.patch"; hash = "sha256-YC3I0BQi3o3+VmRu/UqpqPpaSC+ekPqzbORTHftbPvY="; }) ] ++ lib.optionals (lib.versions.majorMinor php.version == "8.2" && lib.versionOlder php.version "8.2.22") [ </ins> # Fixes compatibility with libxml2 2.13. Part of 8.3.10RC1+, 8.2.22RC1+ (fetchpatch { url = "https://github.com/php/php-src/commit/4fe821311cafb18ca8bdf20b9d796c48a13ba552.diff?full_index=1";

Discussion:
Steps to reproduce the behavior: php-simplexml-8.1.2 This happen after latest flake update Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hydra build : and seem fine: Probably related: (fixes for 8.2 and 8.3 with same error) 1 is out of active support, so there was no backport for from upstream PS you did not ping any maintainers for that package, so they would need to notice this issue (which is unlikely)
Also causes an lsp-plugins build failure. Gonna ping maintainers.
this is fixed in master
forgive my ignorance, but what needs to happen for the fix on master to make its way to the unstable channel? I would love to be able to rebuild my system soon
fixed "lsp-plugins build failure" (it does not depend on php 8.1 version now) If your system update depends on in some other way it won't help. does not build on current master as of (2024-07-30T19:50:23Z)
Well if you only need to rebuild your system again and you don't necessarily care about the updates you're missing out on, you can try using a previous version of your file
Change:
homepage = "https://github.com/clojure-lsp/clojure-lsp"; license = licenses.mit; maintainers = with maintainers; [ ericdallo babariviere ]; <del> # Depends on datalevin that is x86_64 only # https://github.com/juji-io/datalevin/blob/bb7d9328f4739cddea5d272b5cd6d6dcb5345da6/native/src/java/datalevin/ni/Lib.java#L86-L102 broken = !stdenv.isx86_64; </del> }; }

Discussion:
Recently, clojure-lsp build started to fail on unstable and master check out or A clear and concise description of what you expected to happen. Bisecting suggests, that this is because of a recent update to graalvm -22.0.0.2 graalvm17 changing command line parameters to match updating clojure-lsp (already is at latest version) system: host os: multi-user?: sandbox: version: channels(root): channels(herwig): nixpkgs:
this is related with graalvm bump, but I'm aware of it, next clojure-lsp version which is soon should fix the issue since we will stop using datalevin to use transit as the db
Change:
setuid = true; owner = "root"; group = "root"; <del> source = "${pkgs.pam}/sbin/unix_chkpwd.orig"; </del> <ins> source = "${pkgs.pam}/bin/unix_chkpwd"; </ins> }; };

Discussion:
The package seems to have dangling symlinks created for in system-path. Steps to reproduce the behavior: a NixOS system For dangling symlinks not to be created. Build logs: n/a Please run and paste the result.
Change:
++ lib.optional withExamples SDL2 ++ lib.optionals useVulkan [ libplacebo vulkan-loader vulkan-headers ]; <del> mesonFlags= [ </del> <ins> mesonFlags = [ </ins> "-Denable_tools=${lib.boolToString withTools}" "-Denable_examples=${lib.boolToString withExamples}" ];

Discussion:
Steps to reproduce the behavior: qt6.qtmultimedia for mingw (windows) hostPlatform I am slowly adding mingw support for qt6.qtmultimedia. Will reference this issue when I open a PR for a cross build dependency. May open some drafts in a effort to get help from the community. Here is an image of the dependency tree from msys2. ! Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Upstreaming my changes to nixpkgs is taking longer than I expected. Here is the publication of my overlays. Hopefully other members of the community can help me upstream these packages to get qtbase and qtmultimedia cross compiling.
Builds qt6.qtmultimedia for mingw32. Thank you and anyone else I forgot to mention, for helping with reviews. My experience of contributing to nixpkgs was very positive, and it's thanks to all you incredibly bright and generous people. Closing as resolved.
Thank you for putting in all the hard work, very much appreciated!

Steps to reproduce the behavior: qt6 for mingw (windows) hostPlatform I have this building on my local machine using overlays. Here is the dependency tree. ! My plan is to open PR's for each dependency until I can add mingw support for qt6. If you are a maintainer of a package that I am making a PR for, please keep in mind a may be blocked upstreaming mingw support for qt6 if PRs linger for a prolonged period of time. <!-- 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. system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Upstreaming my changes to nixpkgs is taking longer than I expected. Here is the publication of my overlays. Hopefully other members of the community can help me upstream these packages to get qtbase and qtmultimedia cross compiling.
Change:
./services/search/meilisearch.nix ./services/search/opensearch.nix ./services/search/qdrant.nix <ins> ./services/search/typesense.nix </ins> ./services/security/aesmd.nix ./services/security/authelia.nix ./services/security/certmgr.nix

Discussion:
Project description Fast, typo tolerant, in-memory fuzzy Search Engine for building delightful search experiences. Metadata homepage URL: source URL: license: gpl3 platforms: linux, darwin
Change:
version = { aarch64-darwin = "5.10.4.6592"; x86_64-darwin = "5.10.4.6592"; <del> x86_64-linux = "5.10.4.2845"; </del> <ins> x86_64-linux = "5.10.6.3192"; </ins> }.${system} or throwSystem; srcs = {

Discussion:
I notice zoom-us from nixpkgs-unstable gets killed by SIGILL shortly after the application window is shown. This does not occur when running zoom-us from NixOS 21.11. A strace ends with the following output: Observe that the zoom process is killed by SIGILL shortly after the application window is shown. The Zoom application proceeds to run without crashing. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
I stepped through commits that touched zoom-us. The behavior appears to start with (no launch), resp. with (SIGILL observed).
I can‘t reproduce this issue, at least I get into a video call and to making faces at myself for a minute without issues. I am running zoom 5.10.4, on x86_64-linux with kernel 5.17.9.
I didn't see this on my system using the version from nixpkgs . It's expected that would not launch (it's fixed by the commits after). These should really have been one commit, or in another order to allow bisection, but oh well.
From what I can muster, SIGILL is caught while in It looks like is part of the binary distribution of Zoom and not built as part of nixpkgs? But I figure if can run it with no crash it’s more likely an application bug rather than some ABI issue?
I now notice that one Zoom invocation results in two coredumps. The other one is a SIGSYS arising from libc. I’m not really versed in such dark magics, but FWIW:
I really don't expect to be able to debug this, but could you post the output of and (and maybe if the output is short, particularly around the marker) from gdb on the SIGILL core? To me this really feels like a zoom problem. You don't happen to be using an ancient or unusual processor do you?
It looks like version 5.10.6 (3192) is out for linux now, so it might be worth trying that too.
Cheers, that seems to resolve the problem. Not really, it’s an i9-10885H. In case you’re still curious for whatever reason, I’ve attached the information copied from gdb.

Otherwise I’d say this issue is obsoleted by the new Zoom release. (NB just said “No function contains program counter for selected frame.”)
my zoom is dying too, I got it working for now with
Thanks, that's pretty interesting; something jumps into the middle of an instruction. Good that updating it works anyway.
Change:
, python3Packages , ffmpeg , flac <ins> , librsvg </ins> , gobject-introspection , gtk3 , libnotify

Discussion:
Hi, hope I have completed the correct fields! <!-- Initial version of 6.7.1 with updated version at 7.01 --- <!-- There is currently no PR in for this update. --- The Linux desktop music player from the future Name: tauonVersion: 6.7.1Licenses: nix-env -iA current version: 6.7.1 desired version: 7.0.1 HI any update to tauon if you have time, would be greatly appreciated :) I also do not get a tauon icon showing up in gnome 4.x.x and have to exec from the command line instead...wondered if this was by design :)
Tried it out and updated the derivation while at it. I don't think I'll be using this in the long run though, since it seems to have problems with wayland and replaygain inconsistencies between file formats.
I guess it doesn't show up in the gnome dashboard because the derivation does not install a desktop file. There seems to be one in the extra/ dir in the upstream repo but that needs some adapting to work on NixOS.
Thanks for trying, although it seems to be working fine on one of my arch machines running wayland? Don't use replaygain so can't comment. In what way does the desktop file need adjusting, as, in my experience, the tauon dev has been very receptive and amenable in the past. Is the way to test?
It mostly works but I have a mixed-DPI setup and running with the X11 backend in Xwayland is notoriously blurry on scaled monitors which is a bit annoying. The native wayland backend in SDL does not have that problem but SDL also does not handle DPI changes in any way so when moving between screens with different scaling factors, first the viewport goes out of sync with window size and once it relayouts itself it does not rescale for the new DPI. I reported the replaygain issue and that indeed got fixed in a matter of hours. I usually just fetch and build PRs manually but yes, from a glance at the docs seems to do all that in one command.
Thanks for creating heads up v7.1 out overnight if you still have the pull out
v7.1.1 is out and appears to have some of your requested changes included already ...
It indeed is:
Hope the new stuff works
Change:
, ninja , pkg-config , python3 <ins> , zlib , coreutils </ins> , substituteAll }: python3.pkgs.buildPythonApplication rec { pname = "meson"; <del> version = "0.64.1"; </del> <ins> version = "1.0.0"; </ins> src = python3.pkgs.fetchPypi { inherit pname version; <del> hash = "sha256-Oo4DDCM094IIX4FicGLMbUpnce3zHgVf/jdPnmsImrk="; </del> <ins> hash = "sha256-qlCkukVXwl59SERqv96FeVfc31g4X/++Zwug6O+szgU="; </ins> }; patches = [

Discussion:
Hi, I can't see an update on master or a pull request. Mesa 23.0.0 seems to need a meson feature that appears to only be in meson-1.0.0 which is out. I realize bumping meson is probably a large task though, so I'm raising a flag for it now. cc: (recent committers to our meson package)
reference for mesa: without that patch the mesa-23 RC does not build (missing valgrind.h), with the patch, meson whines that its too old of a release.
Change:
gst_all_1.gstreamer gst_all_1.gst-plugins-ugly gst_all_1.gst-plugins-base <ins> json-glib # paradox launcher (Stellaris) </ins> libdrm libxkbcommon # paradox launcher mono

Discussion:
Describe the bug json-glib seems to be a new transitive dependency of tracker/gtk, which the Paradox launcher needs. Somehow it isn't being pulled into the Steam container. To Reproduce Steps to reproduce the behavior: Steam a Paradox game (eg. Stellaris) to start the game Expected behavior Instead of the launcher working as usual, it doesn't launch at all. Launching it directly yields the following error: Additional context Adding json-glib to steam's fhs wrapper libraries is sufficient to start the launcher, but should it be propagated by gtk implicitly? Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. Maintainer information:
which game? I tried eu4 and CK3 and both launch fine
Stellaris. Funny that it seems to work with the others, I suppose it could be something specific to my system?
Unlikely, steam games run in a bubblewrap sandbox, so your host system doesn't matter much.
Change:
### DEVELOPMENT / LIBRARIES <del> a52dec = callPackage ../development/libraries/a52dec { }; </del> aalib = callPackage ../development/libraries/aalib { }; abseil-cpp_202103 = callPackage ../development/libraries/abseil-cpp/202103.nix {

Discussion:
try to build from source with substitutes off I've had this override in place for a few weeks now and I don't think I have the original failed build log any more but I don't think anything has changed. Working mirror: This taking it from some BLFS mirror because that's the first reasonable source I found it at. I think the files are gone from sourceforge or some api change at sourceforge is preventing download for the src defined in nixpkgs. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I'm not the maintainer of , but I can possibly bump it to 0.8.0.
oh is it just one of those that deletes old versions when a new one is released ? I don't know why people do that
Change:
# multiarch offset one-liner using same method as AppImage # see https://gist.github.com/probonopd/a490ba3401b5ef7b881d5e603fa20c93 <del> offset=$(readelf -h "$src" | awk 'NR==13{e_shoff=$5} NR==18{e_shentsize=$5} NR==19{e_shnum=$5} END{print e_shoff+e_shentsize*e_shnum}') </del> <ins> offset=$(LC_ALL=C readelf -h "$src" | awk 'NR==13{e_shoff=$5} NR==18{e_shentsize=$5} NR==19{e_shnum=$5} END{print e_shoff+e_shentsize*e_shnum}') </ins> echo "Uncompress $(basename "$src") of type $appimageType @ offset $offset" unsquashfs -q -d "$out" -o "$offset" "$src" chmod go-w "$out"

Discussion:
Describe the bug appimage-run can't run appimages containing /bin/sh for example the one in attachment. it was created with nix-bundle and works with ubuntu. To Reproduce Steps to reproduce the behavior: the appimage: Expected behavior Hello world Additional context Works with the appimage-run in 20.03: Also works if the link to /bin/sh is omitted. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(symphorien): nixpkgs: Maintainer information:
Maybe we need in some of the fhsUserenv's in ?
Mhm. That should be the case usually: I don't know what the issue is here.
the fact that offset is 0 looks wrong
oh the problem is fixed by exporting LANG=C
Change:
<ins> # From NUR https://github.com/nix-community/nur-combined/blob/6bddae47680482383b5769dd3aa7d82b88e6cbc8/repos/renesat/pkgs/normcap/default.nix { lib, stdenv, python3, fetchFromGitHub, tesseract4, leptonica, wl-clipboard }: python3.pkgs.buildPythonApplication rec { pname = "normcap"; version = "0.4.4"; format = "pyproject"; src = fetchFromGitHub { owner = "dynobo"; repo = "normcap"; rev = "v${version}"; hash = "sha256-dShtmoqS9TC3PHuwq24OEOhYfBHGhDCma8Du8QCkFuI="; }; buildInputs = [ wl-clipboard ]; nativeBuildInputs = with python3.pkgs; [ poetry-core ]; propagatedBuildInputs = with python3.pkgs; [ tesseract4 leptonica pyside6 # Test toml pytest-qt ]; postPatch = '' substituteInPlace pyproject.toml --replace 'PySide6-Essentials = "6.5.1"' "" ''; meta = with lib; { description = "OCR powered screen-capture tool to capture information instead of images"; homepage = "https://dynobo.github.io/normcap/"; license = licenses.gpl3Plus; maintainers = with maintainers; [ cafkafk ]; }; } </ins>

Discussion:
Project description OCR-powered screenshot tool to capture text instead of images.  Metadata homepage URL: source URL: license: GPL3 platforms: unix example package: ()
I started working on this but I'm stuck at how to package with qt
This seems to be a poetry-based project, meaning you should set and add as a nativeBuildInput. If adding the python qt libraries is not sufficient, then try using the for Qt applications.
I'll try to make a PR with this, ty
Is it possible that causes issues in recent NixOS?
Fixed by which reaches unstable in a few fays