jiebi/CodeConvo huggingface dataset:
Change:
for f in $(grep -Rl /usr/bin/ .) ; do substituteInPlace $f --replace /usr/bin/ "" done <ins> '' + lib.optionalString stdenv.isDarwin '' substituteInPlace src/ui/cli/CMakeLists.txt --replace "uuid" "" </ins> ''; installFlags = [ "PREFIX=${placeholder "out"}" ];

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 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! --- : when I search the pulls for , I see . It's not obvious to me why this is relevant, but see below name: <!-- The current version can be found easily with the same process than 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: 3.53.0 desired version: <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: This fails to build for me, crashing out on the build of (which is presumably where the link to pull comes from). Given this is apparently a failure in a dependency, it may be that will automatically start building again once this is resolved. If that's so, then this report is redundant; in which case, apologies. But I'll add it nonetheless in case the fix is not that automatic (I'm a bit vague about how fixes propagate around the wonderful wonderland of Nix).

clang++ -mmacosx-version-min=10.7 -c -o htmldllhelpdata.o -DWXOSXCOCOA -DWXBUILDING -I./src/regex -DWXUSINGDLL -DWXMAKINGDLLHTML -dynamic -fPIC -DPIC -Wall -Wundef -Wunused-parameter -Wno-ctor-dtor-privacy -Woverloaded-virtual -Wno-deprecated-declarations -DFILEOFFSETBITS=64 -I/private/tmp/nix-build-wxwidgets- -I./include -DASSERTMACROSDEFINEVERSIONSWITHOUTUNDERSCORES=1 -O2 -fno-strict-aliasing -fno-common -fvisibility=hidden -fvisibility-inlines-hidden fatal error: 'AVFoundation/AVFoundation.h' file not found #import <AVFoundation/AVFoundation.h^~~~~ 1 error generated. make: [Makefile:: mediadllosxcocoa_mediactrl.o] Error 1 make: Waiting for unfinished jobs.... builder for '/nix/store/wm81bmbkzk2ziyk5v3spdz4647n1v5vn-wxwidgets-' failed with exit code 2 cannot build derivation '/nix/store/y5b7m6vlp8l5046sf7g41bz88w2dv9gn-pwsafe-': 1 dependencies couldn't be built error: build of '/nix/store/y5b7m6vlp8l5046sf7g41bz88w2dv9gn-pwsafe-' failed This is with the unstable channel fully updated: $ nix-env -qa --drv-path --out-path pwsafe pwsafe-3.53.0 /nix/store/y5b7m6vlp8l5046sf7g41bz88w2dv9gn-pwsafe- /nix/store/lvikq70mprd98ny90glpsh04llzs77nz-pwsafe-3.53.0 Platform: macOS 10.15.7 (Catalina). Please tag this issue in your PR.
I just tested it on Linux, there it works just fine. Thank you for your report, and sorry that I cannot be of further assistance!
I marked this as stale due to inactivity. &rarr;
Change:
inherit version; src = fetchurl { url = dmgUrl; <del> sha256 = "0xqkl4yds0n9fdjvnk0v5mj382q02crry6wm2q7j3ncdqwsv02sv"; </del> <ins> sha256 = "0s8crlh8rvpanzk1w4z3hich0a3mw0m5xhpcg07bxy02calhpdk1"; </ins> curlOpts = "-r ${dmgRange}"; };

Discussion:
I don't really know why my system configuration for an XPS 13 is pulling this in, either: EDIT: I had set in my system configuration, thus causing me to (fail to) build .
I have the same problem on 3 laptops As mentioned in above post issue is related to enableAllFirmware = true; Chnaging to enableRedistributableFirmware = true; fixed the issue for now another example
cc maintainers:
I think, the new url could be found on this page
I'll try to find time over the weekend to update new offsets and hashes for the new download path. In the meantime, facetimehd users can extract the firmware from their OSX partition with this override: ``
See
Change:
path = [ pkgs.simp_le ]; preStart = '' mkdir -p '${cfg.directory}' <del> chown '${data.user}:${data.group}' '${cfg.directory}' </del> <ins> chown -R '${data.user}:${data.group}' '${cfg.directory}' </ins> if [ ! -d '${cpath}' ]; then mkdir '${cpath}' fi

Discussion:
I was upgrading from nixos-17.03 prerelase (commit ) to the newly released nixos-17.03 stable (commit ). Deploying with nixops, it got stuck when activating the systemd service for ACME. In , first: then 5 minutes later the failure:
Looking at , I see , but the dir it wants to write to is writable only by root:
I guess the question is where comes from. I haven't figured out yet where that gets set to nginx; in my settings, I use:
I think it's : where is from above:
Ah, I think I understand what is happening: See how is owned by but the subdir is owned by ? Commit to the pre-start script, but since it doesn't use , it is possible that there are older existing subdirs (like from my example) that are owned to from before that commit went it. I believe that should be . do you agree?
Yes :)
Adding , my nixops deploy has finsihed now. It took a long time though (hanging at the systemd service activation for ~10 minutes or so). In , the line which is much later than when the systemd service activation started at around
PR for at to fix the permissions error (but not the delay problem). Should I make a PR for too?
Please :)
Change:
<del> { pcre, pcre2, picom, lib, fetchFromGitHub }: </del> <ins> { pcre, pcre2, libXinerama, picom, lib, fetchFromGitHub }: </ins> picom.overrideAttrs (oldAttrs: rec { pname = "picom-next"; <del> version = "unstable-2022-12-23"; buildInputs = [ pcre2 ] ++ lib.remove pcre oldAttrs.buildInputs; </del> <ins> version = "unstable-2023-01-29"; buildInputs = [ pcre2 ] ++ lib.remove libXinerama (lib.remove pcre oldAttrs.buildInputs); </ins> src = fetchFromGitHub { owner = "yshui"; repo = "picom"; <del> rev = "60ac2b64db78363fe04189cc734daea3d721d87e"; sha256 = "09s8kgczks01xbvg3qxqi2rz3lkzgdfyvhrj30mg6n11b6xfgi0d"; </del> <ins> rev = "cee12875625465292bc11bf09dc8ab117cae75f4"; sha256 = "sha256-lVwBwOvzn4ro1jInRuNvn1vQuwUHUp4MYrDaFRmW9pc="; </ins> }; meta.maintainers = with lib.maintainers; oldAttrs.meta.maintainers ++ [ GKasparov ]; })

Discussion:
Package name: picom-next-unstable Latest released version: 2023-01-29 <!-- Search your package here: --- Current version on the unstable channel: 2022-12-23 Current version on the stable/release channel: 2022-09-29 <!-- 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:
++ optional enableGDBJITSupport "-DLUAJIT_USE_GDBJIT" ++ optional enableAPICheck "-DLUAJIT_USE_APICHECK" ++ optional enableVMAssertions "-DLUAJIT_USE_ASSERT" <ins> ++ optional deterministicStringIds "-DLUAJIT_SECURITY_STRID=0" </ins> ; in stdenv.mkDerivation rec {

Discussion:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: Looks like symbol ordering differences:
Change:
<ins> { lib, stdenv, fetchFromGitHub, autoconf, libtool, automake, cyrus_sasl }: stdenv.mkDerivation rec { pname = "cyrus-sasl-xoauth2"; version = "0.2"; src = fetchFromGitHub { owner = "moriyoshi"; repo = "cyrus-sasl-xoauth2"; rev = "v${version}"; sha256 = "sha256-lI8uKtVxrziQ8q/Ss+QTgg1xTObZUTAzjL3MYmtwyd8="; }; nativeBuildInputs = [ autoconf libtool automake ]; buildInputs = [ cyrus_sasl ]; preConfigure = "./autogen.sh"; configureFlags = [ "--with-cyrus-sasl=${placeholder "out"}" ]; meta = with lib; { homepage = "https://github.com/moriyoshi/cyrus-sasl-xoauth2"; description = "XOAUTH2 mechanism plugin for cyrus-sasl"; platforms = platforms.unix; license = licenses.mit; maintainers = with lib.maintainers; [ wentasah ]; }; } </ins>

Discussion:
Add XOAUTH2 plugin to cyrus sasl suite of auth mechanisms adding a plugin to cyrussasl Let's add for example this plugin to the list of authentication mechanisms. One example use case is to allow mbsync (isync) to authenticate against outlook office365's IMAP server, or Google's. As mentions: So there's a trick to make the plugin auto-discovered, I can see some options: “augment” the cyrussasl package with extra entries in the dev output (sort of clunky) create a stable entry under to group all plugin libs Metadata homepage URL: source URL: license: MIT platforms: linux, darwin, ...
Second this. A simple cannot do the trick because will look for . Can we override this with using, say, a patch to the original package?
In the meantime, I use the following hack to get plugin working for now: a copy of since it is a dependency of plugin plugin (I use ) an overlay of with libraries symlinking to : This hack is not ideal (has to build a separate just for building library). But it gets the job done.
~ do you have a link to a full setup? Or do you remember what are you using for~ ? edit: remove question add link
cyrus sasl has a SASL_PATH environment variable for specifying a colon separated list of directories to search for plugins. I don't know if this is the best way, but I've put the following in an overlay, and other than having to compile the cyrus-sasl-xoauth2 plugin, nothing else needs to be build:
looks to be working, I've used it to glue in XOAUTH2 plugin from to , so KMail can receive mail from Gmail: It probably should propagate somehow from .
Here's the full overlay i use, based on the example above, including compilation of : In combination with this enables in mbsync!
Hey I've been following this issue for a while but don't really see how I'd setup my config to use xoauth2 with the updates from Are there any docs/examples on using the new setup? Or another issue to follow?
I use this in a wrapper of /, as can be seen in . It would be good idea to integrate this directly into expression, as parameter. I'll look at that.
Change:
<del> {stdenv, fetchurl, automake, autoconf, pkgconfig, libtool, python2Packages, glib, jansson}: </del> <ins> {stdenv, fetchFromGitHub, automake, autoconf, pkgconfig, libtool, python2Packages, glib, jansson}: </ins> <del> stdenv.mkDerivation rec { version = "3.0.7"; seafileVersion = "6.1.0"; </del> <ins> stdenv.mkDerivation rec { version = "3.0.8"; </ins> name = "libsearpc-${version}"; <del> src = fetchurl { url = "https://github.com/haiwen/libsearpc/archive/v${version}.tar.gz"; sha256 = "0fdrgksdwd4qxp7qvh75y39dy52h2f5wfjbqr00h3rwkbx4npvpg"; </del> <ins> src = fetchFromGitHub { owner = "haiwen"; repo = "libsearpc"; # Tag is missing: https://github.com/haiwen/libsearpc/commit/12a01268825e9c7e17794c58c367e3b4db912ad9 rev = "12a01268825e9c7e17794c58c367e3b4db912ad9"; sha256 = "00ck1hl1x0pn22q3ba32dq3ckc4nrsg58irsmrnmalqbsffhcim0"; </ins> }; patches = [ ./libsearpc.pc.patch ];

Discussion:
seafile-client 6.1.8 fails to build at cmake configuration step with the following error message: run
I've tried updating Seafile to 6.2.0, which supports Qt 5.11, here: However, I ran into an issue:
With Qt 5.11.1, the error is gone, but the current version is still incompatible with Qt 5.11.x:
Change:
''; platforms = with platforms; linux ++ darwin; <del> maintainers = with maintainers; [ ylh ]; </del> <ins> maintainers = with maintainers; [ PopeRigby ylh ]; mainProgram = "vkquake"; </ins> }; }

Discussion:
Package name: vkquake Latest released version: 1.22.3 Current version on the unstable channel: 1.22.3 Current version on the stable/release channel: 1.22.3 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]:
Change:
{ stdenv , lib , fetchFromGitHub <ins> , fetchpatch </ins> , fetchurl , cmake , ninja

Discussion:
We broke gmic-qt during the bump. After contacting upstream, it seems like the cmake build is not maintained anymore: They migrated to . We should align with them and rewrite a qmake derivation for gmic-qt. Edit: jtojnar advise not to migrate to qmake but instead fix the cmake issue.
Any idea what I can do so I can build my system while this is a WIP?
Install the build from an older version of nixpkgs where the package you want still builds properly. The version in branch should be building properly. For Flakes: For Non-Flake:
Thank you so much!! That section of the wiki described exactly what I was trying to do!
I just posted an upstream PR to fix this:
I've opened with a proper fix if anyone here would like to do some testing (it works for me now)

Steps to reproduce the behavior: Full log: Package built successfully in . Package failed in . I assume package failed to built somewhere in between these two pull request. Please run and paste the result.
Possibly needs update like
tried but had a compilation issue: Error:
Change:
<ins> { stdenv, lib, fetchFromGitHub, cmake, scdoc, }: stdenv.mkDerivation (finalAttrs: { pname = "wl-restart"; version = "0.2.0"; src = fetchFromGitHub { owner = "Ferdi265"; repo = "wl-restart"; rev = "refs/tags/v${finalAttrs.version}"; hash = "sha256-pMsYLU9pjN2cgz7FxJJwkDHKJt1mIAuagJSBjrPUMAM="; }; cmakeFlags = [ (lib.cmakeBool "INSTALL_DOCUMENTATION" true) ]; nativeBuildInputs = [ scdoc cmake ]; meta = { description = "Simple tool that restarts your compositor when it crashes"; homepage = "https://github.com/Ferdi265/wl-restart"; changelog = "https://github.com/Ferdi265/wl-restart/releases/tag/v${finalAttrs.version}"; license = lib.licenses.gpl3Plus; mainProgram = "wl-restart"; maintainers = with lib.maintainers; [ bot-wxt1221 ]; platforms = lib.platforms.linux; }; }) </ins>

Discussion:
wl-restart is a simple tool that restarts your compositor when it crashes. It also creates and destroys the Wayland socket for the compositor, so that clients that support seamless compositor reconnects (most KDE programs, e.g. konsole) don't die with it when your compositor crashes. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: GPL3 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
pixelnuke = callPackage ../applications/graphics/pixelnuke { }; <del> pixelorama = callPackage ../applications/editors/pixelorama { }; </del> pixeluvo = callPackage ../applications/graphics/pixeluvo { }; pixinsight = qt6Packages.callPackage ../applications/graphics/pixinsight { };

Discussion:
Package name: Pixelorama Latest released version: 1.0 <!-- Search your package here: --- Current version on the unstable channel: 0.11.4 Current version on the stable/release channel: 0.11.4 <!-- 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]:
Change:
platforms = lib.platforms.linux; }; }) <ins> # TODO: investigate failure when using __structuredAttrs </ins>

Discussion:
Generated desktop file for package is missing categories. It can be easily solved by adding to and deleting list. I tested it, it works. But perhaps it would be better to patch desktop file to use /nix/store path as I saw other people do. It would be better to use provided desktop file, or at least recreate it. It is not a bug, but rather improvement request. I need categories set for my desktop, and it would be nice to have them out of the box. And I think it is better to use provided desktop file instead of creating a new one if possible. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
]); checkPhase = '' <del> # Temporarily disable a test failing after a patch imagemagick update. # It might only due to the reporting and matching used in the test. # See https://github.com/NixOS/nixpkgs/issues/223446 # See https://sourceforge.net/p/gscan2pdf/bugs/417/ # #   Failed test 'valid TIFF created' #   at t/131_save_tiff.t line 44. #                   'test.tif TIFF 70x46 70x46+0+0 8-bit sRGB 10024B 0.000u 0:00.000 # ' #     doesn't match '(?^:test.tif TIFF 70x46 70x46+0+0 8-bit sRGB [7|9][.d]+K?B)' rm t/131_save_tiff.t </del> # Temporarily disable a dubiously failing test: # t/169_import_scan.t ........................... 1/1 # #   Failed test 'variable-height scan imported with expected size'

Discussion:
: can not open Edit-Preferences : can not open Edit-Preferences A dialogue should happen This is the debug log: 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]:
Hi! I'm afraid I could not reproduce the issue; the Preferences dialogue shows up fine for me. I tried with on NixOS 23.11 with Sway.
Thank you for your fast reply. Does the dialogue connect to some service that must be running?
Quoting Jens Getreu (2024-03-03 14:46:03) The whole app might be trying to connect to SANE when it starts, but I don't think anything is needed for that particular dialogue.
works fine. All other dialogues open correctly. When I try to open Preferences the second time, a tiny little empty window opens. On the console the above error is dumped.
I am running the i3 window manager. Gnome has a settings deamon. I tried: with but it did not help. I still get and no Edit-Preferences dialogue appears.
I'm having the same issue - gscan2pdf v2.13.2, GNOME 45.3, kernel 6.6.16-1-lts
Same for me on KDE on current master with v2.13.2: EDIT: Upstream seems to be ware of the issue:
This should be fixed with Please test and review.
Change:
"systemctl start restic-backups-remote-from-file-backup.service", 'restic-remote-from-file-backup snapshots --json | ${pkgs.jq}/bin/jq "length | . == 1"', <ins> # test that remote-noinit-backup produces a snapshot "systemctl start restic-backups-remote-noinit-backup.service", 'restic-remote-noinit-backup snapshots --json | ${pkgs.jq}/bin/jq "length | . == 1"', </ins> # test that restoring that snapshot produces the same directory "mkdir /tmp/restore-2", "${pkgs.restic}/bin/restic -r ${remoteRepository} -p ${passwordFile} restore latest -t /tmp/restore-2",

Discussion:
Recent changes to the assume the presence of the list even when it is not in use (it defaults to null). This prevents the service from running. Problem line: Steps to reproduce the behavior: a backup service without the 'dynamicFilesFrom' option that is included in the service's ExecStart service failing due to error Argument should not be passed if is not in use <!-- 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.
cc
Please provide the relevant part of your configuration hughobrien am Mi., 1. Nov. 2023, 01:07:
The problematic section is unconditional so I do not believe the config matters. Nevertheless
Ah, I see. I'll send a fix in the evening. In the meantime, you can work around the problem by setting (which does not change anything if the repository already exists). hughobrien am Mi., 1. Nov. 2023, 15:08:
Change:
(mkRemovedOptionModule [ "services" "osquery" ] "The osquery module has been removed") (mkRemovedOptionModule [ "services" "fourStore" ] "The fourStore module has been removed") (mkRemovedOptionModule [ "services" "fourStoreEndpoint" ] "The fourStoreEndpoint module has been removed") <ins> (mkRemovedOptionModule [ "services" "mathics" ] "The Mathics module has been removed") </ins> (mkRemovedOptionModule [ "programs" "way-cooler" ] ("way-cooler is abandoned by its author: " + "https://way-cooler.org/blog/2020/01/09/way-cooler-post-mortem.html")) (mkRemovedOptionModule [ "services" "xserver" "multitouch" ] ''

Discussion:
The mathics test does not work because: /cc (commit history)
I see the same error with on the 20.03 beta channel. I think it also happens on Master. It used to work (maybe a few weeks ago? if I have time I'll bisect).
I removing mathics.
Change:
}, "CudaText-lexers": { "owner": "Alexey-T", <del> "rev": "2020.08.10", "sha256": "1gzs2psyfhb9si1qyacxzfjb3dz2v255hv7y4jlkbxdxv0kckqr6" </del> <ins> "rev": "2021.01.16", "sha256": "13zyg0cm1c1662l3f7sy462pbc39l1cwm5214nx8ijngf8kgn2zh" </ins> }, "bgrabitmap": { "owner": "bgrabitmap",

Discussion:
For this patch I to CudaText the global variable which you can change to False. to disable "Help / Check for updates".
OK, I will use it with next release.
Change:
# programs to be wrapped. SETUID_PATH=${config.system.path}/bin:${config.system.path}/sbin <del> rm -f ${wrapperDir}/* # */ </del> <ins> mkdir -p /run/setuid-wrapper-dirs wrapperDir=$(mktemp --directory --tmpdir=/run/setuid-wrapper-dirs setuid-wrappers.XXXXXXXXXX) </ins> ${concatMapStrings makeSetuidWrapper setuidPrograms} <ins> if [ -d ${wrapperDir} ]; then mv --no-target-directory ${wrapperDir} ${wrapperDir}-old ln --symbolic $wrapperDir ${wrapperDir} rm --force --recursive ${wrapperDir}-old elif [ -L ${wrapperDir} ]; then ln --symbolic --force --no-dereference $wrapperDir ${wrapperDir}-tmp old=$(readlink ${wrapperDir}) mv --no-target-directory ${wrapperDir}-tmp ${wrapperDir} rm --force --recursive $old else ln --symbolic $wrapperDir ${wrapperDir} fi </ins> ''; };

Discussion:
It's currently possible to cancel between deletion of previous setuid wrappers and population of new ones. And yes, I've been able to lock myself out of machine (almost, if I didn't have root ssh key). Current implementation: Proposed implementation (see at the bottom of blog post):
so this was failing because it's ready a tmpfs upon install: So, if we want to be a tmpfs and a symlink that won't work. My proposal would be to make a tmpfs and move conents to which could then be a symlink. This would be a backwards incompatible change, but we can fix it in nixpkgs and document it. Thoughts?
I think it would be better to just not have /var/setuid-wrappers be a tmpfs since we're symlinking to a tmpfs anyway.
Well, we can just change nixos-install not to create that tmpfs, right? Not sure why it's doing that anyway...
I'll have a PR ready soon, fixing a bug atm.
Change:
<del> source "https://rubygems.org" do gem 'compass' end </del> <ins> source 'https://rubygems.org' gem 'compass' </ins>

Discussion:
After building , I tried to run it, but got an error (see Screenshots). Steps to reproduce the behavior: nixpkgs repository, run Successful execution of <!-- 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.