jiebi/CodeConvo huggingface dataset:
Change:
}: mkDerivation rec { <del> pname = "krita"; </del> <ins> pname = "krita-unwrapped"; </ins> inherit version; src = fetchurl {

Discussion:
Krita 5 complains that it cannot find the G'Mic plugin. Steps to reproduce the behavior: Krita and the G'Mic plugin by adding and to in Krita a new image the menu item Filter→Start G'MIC-Qt will complain, via a modal dialog, that it cannot load the plugin. the menu item Settings→Configure Krita… should be a "G’Mic plugin" section in the left-hand sidebar, but there is not. For there to be a Krita setting to specify the path to the G'Mic plugin. The explains the correct behaviour.
Starting from the package won't work with Krita. Krita team forked and Krita will only work with that fork: It would take some effort to implement the build process mentioned in the README since cmake and make need to be invoked multiple times. (Probably need to manually write the whole and )
Is it possible to maintain a separate krita-gmic package like arch linux does?
It is possible but making it a separate package probably wouldn't make it easier to implement. We just need someone to implement the build process I linked above in nix (sorry I don't have time to do it)
Making some minor changes to you can build the krita plugin: I've not yet been able to have krita load the plugin though. I've tried creating a symlinkJoin'ed version with the plugin, that does not work :confused: Krita is not logging enough information about where it tried to load the plugin for me to be able to deduce what is going wrong.
Do you think the Krita fork of gmic-qt should be integrated in the definition at ? I was originally afraid modifying it now would not be worth it because the two versions might deviate too much from one another.
If you want to remove the original gmic-qt and change it to krita's fork, I believe it will conflict with the previous one, and I would therefore vote against it If you want to keep the fork along with the original, it's fine! You can use overrideAttrs magic in order to reuse the previous expression. Look at as an example for inspiration.
Option 1 is terrible, I'd never ask for that :smiley:.

I was asking if krita's gmic-qt should be included as a "variant" in , effectively does the same as option 2 <details<summaryLike this</summary</detailsI think it's best to keep it as a completely separate package, because both packages will never have matching versions.
So close! I got the "Q'MIC-qt for Krita" window to open by manipulating : ! Unfortunately it segfaults the moment I try to use any of the filters: Progress at
Change:
hash = "sha256-2DqEfTXD3W6MxfBb6aHaKH+zpxLc2tHaGuWGQuncySo="; }; <ins> patches = [ # Fix SQLite db lockup (fetchpatch { url = "https://github.com/matrix-org/dendrite/commit/c08c7405dbe9d88c1364f6f1f2466db5045506cc.patch"; hash = "sha256-gTF9jK5Ihfe1v49gPCK68BLeiUZa2Syo+7D9r62iEXQ="; }) ]; </ins> vendorHash = "sha256-dc0zpKh7J+fi2b5GD/0BQ120UXbBvJLUF74RmYMSOMw="; subPackages = [

Discussion:
A clear and concise description of what the bug is. Matrix server dendrite does not start after upgrade to 0.13.1 This is fixed in - Prepare statement on an existing transaction Steps to reproduce the behavior: dendrite < 0.13.1 running as a service with sqlite as database backend which upgrades dendrite to 0.13.1 as per Matrix server dendrite not crashing fixed in Please run and paste the result.
Sorry for that, it seems like the issue slipped through the test suite, because it starts up an empty dendrite instance. I'll make a PR to apply the commit provided above.
I've proposed PR to address this issue. Let me know if the issue still occurs after applying the commit.
Works :partying_face: thanks a lot for the quick fix !! :hugs:
Change:
--set GDK_PIXBUF_MODULE_FILE "$GDK_PIXBUF_MODULE_FILE"  --suffix XDG_DATA_DIRS : "${gnome_themes_standard}/share:$out/share:$XDG_ICON_DIRS:$GSETTINGS_SCHEMAS_PATH" <ins> wrapProgram "$out/bin/gnome-shell-extension-tool"  --prefix PYTHONPATH : "${python3Packages.pygobject3}/lib/python3.4/site-packages:$PYTHONPATH" </ins> wrapProgram "$out/libexec/gnome-shell-calendar-server"  --prefix XDG_DATA_DIRS : "${evolution_data_server}/share:$out/share:$XDG_ICON_DIRS:$GSETTINGS_SCHEMAS_PATH"

Discussion:
System: NixOS: (Flounder) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version:
Change:
check_return=False, check_output=False, ) <del> self.wait_for_console_text(r"systemd[1]:.*Switching root.") </del> self.connected = False self.connect()

Discussion:
I'm using the initrd backdoor to write tests for a nixos module that installs a systemd stage1 addition; it uses the backdoor to wait for a condition on host alice, and then when that condition occurs, uses to continue booting into the proper system. That mostly works, except just now, a test failure happened where switchroot() didn't detect the console output: (my apologies for the several thousand log lines). If you download those referenced build logs above and run it will show all the logs and console messages; those aren't showing the message "Switching root." What's more, they're not showing the service "Switch Root" being started either. But the system "alice" does reach , as the log messages say. should always work and be able to detect that it worked. Further, it should allow setting a timeout or set a timeout itself, to avoid running indefinitely, like the test run above did. This test run is happening on this change: Looking at without much familiarity with the test driver itself, I'd suspect a race condition: Since several log messages are missing (e.g. about starting the root-switching service), I'm wondering if there's a race condition happening with the backdoored system? Please run and paste the result. (that output isn't too useful; here's the nixpkgs rev I'm running with: ) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I have logs here with systemd LogLevel=debug turned on: - same issue as above, and it seems to reproduce more reliably with systemd debug logging.
Change:
cp --no-preserve=mode -r "${contribSrc}/modules" "$NIX_BUILD_TOP/source/opencv_contrib" ''; <ins> patches = [ (fetchpatch { url = "https://github.com/opencv/opencv/commit/5691d998ead1d9b0542bcfced36c2dceb3a59023.patch"; name = "CVE-2019-14493.patch"; sha256 = "14qva9f5z10apz5q0skdyiclr9sgkhab4fzksy1w3b6j6hg4wm7m"; }) ]; </ins> # This prevents cmake from using libraries in impure paths (which # causes build failure on non NixOS) # Also, work around https://github.com/NixOS/nixpkgs/issues/26304 with

Discussion:
, (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.
` will take some effort.
Change:
wtype = callPackage ../tools/wayland/wtype { }; <del> ydotool = callPackage ../tools/wayland/ydotool { }; </del> cambalache = callPackage ../development/tools/cambalache { }; cambrinary = python3Packages.callPackage ../applications/misc/cambrinary { };

Discussion:
requires to be running in order to be used otherwise it aborts and crashes (see ). It would make sense to have a NixOS configuration option in order to automatically configure to run. Some NixOS module option (perhaps ) that automatically configures and runs as a systemd service in the background.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
{ <ins> # allow overriding electron electron, </ins> webcord, substituteAll, lib,

Discussion:
Under Wayland on Hyprland, trying to launch Webcord results in a frozen window and then a crash on startup. It doesn't matter if I launch using Ozone flags or not. Vanilla Discord package launches without issue. I did not test if Webcord launches under Xorg. Steps to reproduce the behavior: launcher or shell to launch Webcord it crash instead of starting properly. Webcord launches and works fine. I am using Hyprland's upstream flake. However, I don't see why that might be relevant, but it might be worth mentioning. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Please test with an alternative Wayland compositor, e.g., sway or river.
Unfortunately, same behavior on Sway.
Then it's safe to assume it's an electron problem. We may consider overriding the electron version. is webcord working for you two?
Works for me
I've never run into such an issue on sway. did you ensure to disable hyprland when testing sway? Also, can you try with to rule out any electron issues?
It's probably the vencord patch
Seems to be the vencord patch. Logs of are as follows, but unlike the app actually starts. Perhaps would help?
On nixos-unstable webcord-vencord launches on Xorg but does not have anything relating to vencord working on master everything works properly on Xorg
I updated to vencord 1.8.4. It's still not working. I'm running out of ideas on what the cause could be.
seems to be caused by and it's still broken on . I was able to prevent the segfault by using electron 29:
Change:
(fetchNuGet { pname = "Microsoft.Testing.Extensions.VSTestBridge"; version = "1.0.2"; sha256 = "0c65fsc23xxw648xh83sjcmrn9hvs9q58l5lb36wflvaajbsjf2r"; }) (fetchNuGet { pname = "Microsoft.Testing.Platform"; version = "1.0.2"; sha256 = "0bq46f4v2r4nzwly7g0dsakyc1lcql9nh85sp59d1fwzaknf1n94"; }) (fetchNuGet { pname = "Microsoft.Testing.Platform.MSBuild"; version = "1.0.2"; sha256 = "1vjqrpqjx3z1irqgy0ckmkgyvrzqqqcikxs36q6gadyj643ra1c5"; }) <ins> (fetchNuGet { pname = "Microsoft.TestPlatform.ObjectModel"; version = "17.10.0"; sha256 = "07j69cw8r39533w4p39mnj00kahazz38760in3jfc45kmlcdb26x"; }) </ins> (fetchNuGet { pname = "Microsoft.TestPlatform.ObjectModel"; version = "17.5.0"; sha256 = "0qkjyf3ky6xpjg5is2sdsawm99ka7fzgid2bvpglwmmawqgm8gls"; }) <del> (fetchNuGet { pname = "Microsoft.TestPlatform.ObjectModel"; version = "17.9.0"; sha256 = "1kgsl9w9fganbm9wvlkqgk0ag9hfi58z88rkfybc6kvg78bx89ca"; }) (fetchNuGet { pname = "Microsoft.TestPlatform.TestHost"; version = "17.9.0"; sha256 = "19ffh31a1jxzn8j69m1vnk5hyfz3dbxmflq77b8x82zybiilh5nl"; }) </del> <ins> (fetchNuGet { pname = "Microsoft.TestPlatform.TestHost"; version = "17.10.0"; sha256 = "1bl471s7fx9jycr0cc8rylwf34mrvlg9qn1an6l86nisavfcyb7v"; }) </ins> (fetchNuGet { pname = "Microsoft.VisualStudio.Threading"; version = "17.7.35"; sha256 = "1sr2ydgl6clnpf7axjhnffx3z2jz1zhnxfiizsv1prl26r3y52f9"; }) (fetchNuGet { pname = "Microsoft.VisualStudio.Threading.Analyzers"; version = "17.10.48"; sha256 = "00p3ywq4ppfl14l9yzxl5id5zmay8fv42b4w3ppr1b3d5ipldxhj"; }) (fetchNuGet { pname = "Microsoft.VisualStudio.Validation"; version = "17.6.11"; sha256 = "0qx4nzsx28galgzzjkgf541254d433dgxcaf7y2y1qyyxgsfjj1f"; })

Discussion:
update script errors when executed as: Logs: -shell --argstr package bicep logs at: Update script should not error. It should update package. An update for bicep 0.28.1 is available. CC
Error looks like a red herring, I see it during successful updates. Seems like a problem with a dependency version in that release. I was able to run it on a newer commit after they bump dependencies. When you run the fetch-deps I see this on that release:
Change:
<ins> { stdenv , fetchFromGitHub , lib , gnome-themes-extra , gtk-engine-murrine , gtk_engines }: stdenv.mkDerivation rec { pname = "rose-pine-gtk-theme"; version = "unstable-2021-02-22"; src = fetchFromGitHub { owner = "rose-pine"; repo = "gtk"; rev = "9cd2dd449f911973ec549231a57a070d256da9fd"; sha256 = "0lqx8dmv754ix3xbg7h440x964n0bg4lb06vbzvsydnbx79h7lvy"; }; buildInputs = [ gnome-themes-extra # adwaita engine for Gtk2 gtk_engines # pixmap engine for Gtk2 ]; propagatedUserEnvPkgs = [ gtk-engine-murrine # murrine engine for Gtk2 ]; installPhase = '' runHook preInstall mkdir -p $out/share/themes cp -a Rose-Pine $out/share/themes rm $out/share/themes/*/LICENSE runHook postInstall ''; meta = with lib; { description = "Rosé Pine theme for GTK"; homepage = "https://github.com/rose-pine/gtk"; license = licenses.gpl3Only; platforms = platforms.linux; maintainers = [ maintainers.romildo ]; }; } </ins>

Discussion:
Project description It's a colourscheme that has an implementation for gtk, it's pretty! We have gtk themes like on here, but wasn't sure if the process is any different when it comes to packaging this instead. Metadata homepage URL: source URL:
Change:
# These values will be replaced with actual values during the package build EFI_SYS_MOUNT_POINT = "@efiSysMountPoint@" TIMEOUT = "@timeout@" <del> EDITOR = bool("@editor@") </del> <ins> EDITOR = "@editor@" == "1" </ins> CONSOLE_MODE = "@consoleMode@" BOOTSPEC_TOOLS = "@bootspecTools@" DISTRO_NAME = "@distroName@"

Discussion:
See title. nixos-unstable (), set is missing from . is present in . n/a Regression caused by (which I verified by reverting the commit, and the expected behaviour is restored). <!-- 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]:
Change:
, libxfce4util , libxklavier , pam <ins> , python3 </ins> , systemd , xfconf , lib }: <ins> let # For xfce4-screensaver-configure pythonEnv = python3.withPackages (pp: [ pp.pygobject3 ]); in </ins> mkXfceDerivation { category = "apps"; pname = "xfce4-screensaver";

Discussion:
Apparently there's a problem with wrapped command. When try to configure my screensaver (e.g. slideshow), it won't open. Opening it via terminal returns nothing. The command itself points to /nix/store/hash-xfce4-screensaver-version/bin/.xfce4-screensaver-configure-wrapped. Its a python script, but interpreter is set as #!/usr/bin/python3, which is obviously not available on nixos. Steps to reproduce the behavior: Configuration program should open ! strace output:
Does help?
Thanks, now it works. Shall i close the issue or wait for PR?
Change:
inherit (darwin.apple_sdk.frameworks) AGL Carbon Cocoa Kernel QTKit; }; <del> wxGTK31 = callPackage ../development/libraries/wxwidgets/3.1 {}; </del> <ins> wxGTK31 = callPackage ../development/libraries/wxwidgets/3.1 { inherit (gnome2) GConf; inherit (darwin.stubs) setfile; inherit (darwin.apple_sdk.frameworks) AGL Carbon Cocoa Kernel QTKit; }; </ins> wxmac = callPackage ../development/libraries/wxwidgets/3.0/mac.nix { inherit (darwin.apple_sdk.frameworks) AGL Cocoa Kernel;

Discussion:
I am trying to package -13.0.0, which depends on wxWidgets 3.1 or later. I am putting the following in : But it does not work: Currently  is defined using cc system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Related to this, we should make wxGTK31 the default wxGTK & make it a real derivation instead of an override (related to ).
Change:
darwin.apple_sdk.frameworks.Foundation ]; <ins> # Disable cwd support on darwin, because it requires macOS>=10.15 preConfigure = lib.optionalString stdenv.isDarwin '' for file in 3rd/bee.lua/bee/subprocess/subprocess_posix.cpp 3rd/luamake/3rd/bee.lua/bee/subprocess/subprocess_posix.cpp; do substituteInPlace $file --replace '#define SUPPORT_CWD 1' "" done ''; </ins> preBuild = '' cd 3rd/luamake ''

Discussion:
Building the most recent version breaks under darwin Full log: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- the last version bump broke darwin builds Please run and paste the result.
1 is the last version that successfully builds under darwin. Everything above (currently 3.0.2 and 3.1.0) breaks during build.
2 has the same build problem:
Change:
<del> diff --git a/libmariadb/mariadb_config/mariadb_config.c.in b/libmariadb/mariadb_config/mariadb_config.c.in index 45d2f4e..e5666db 100644 --- a/libmariadb/mariadb_config/mariadb_config.c.in +++ b/libmariadb/mariadb_config/mariadb_config.c.in @@ -5,7 +5,7 @@ static char *mariadb_progname; -#define INCLUDE "-I@CMAKE_INSTALL_PREFIX@/@INSTALL_INCLUDEDIR@ -I@CMAKE_INSTALL_PREFIX@/@INSTALL_INCLUDEDIR@/mysql" +#define INCLUDE "-I@INSTALL_INCLUDEDIR@ -I@INSTALL_INCLUDEDIR@/mysql" #define LIBS    "-L@CMAKE_INSTALL_PREFIX@/@INSTALL_LIBDIR@/ -lmariadb @extra_dynamic_LDFLAGS@" #define LIBS_SYS "@extra_dynamic_LDFLAGS@" #define CFLAGS  INCLUDE </del>

Discussion:
mysqlupgrade requires availability of mysqlcheck, which is in the package In other operating systems they are separated - mysqlupgrade -, mysqlcheck - And when the server is installed the client is automatically installed.
Hmm, is there a reason not to make the client a dependency of the server? The only dependencies the client has that the server doesn't are and which any server should have (via openssh). How much space is saved by removing the client binaries?
So it seems the mysql_upgrade binary is hardcoded to expect the other binaries in the same directory: Probably the splitting works on other distros because the binaries all end up in /usr/bin anyway.
Need to build the package with server+client and only client? Is this variant bad?
I'm not sure what you mean. Can you check to see if the project cmake allows you to configure a different install PREFIX for the client/server?
Should I change the build of MariaDB, so that one package includes files for both server and client, and the other package only includes client files? I don't know how to configure this
19.09 milestone? If this and aren't resolved by then we will have to add the client binaries back into the server package.
- this variant optimal?
update MariaDB configuration, please check this variant.
Fixed, mariadb package includes server and client binaries.
Change:
buildPythonPackage rec { pname = "betterproto"; <del> version = "2.0.0b5"; </del> <ins> version = "2.0.0b6"; </ins> format = "pyproject"; disabled = pythonOlder "3.7"; src = fetchFromGitHub { owner = "danielgtaylor"; repo = "python-betterproto"; <del> rev = "v${version}"; hash = "sha256-XyXdpo3Yo4aO1favMWC7i9utz4fNDbKbsnYXJW0b7Gc="; </del> <ins> rev = "v.${version}"; hash = "sha256-ZuVq4WERXsRFUPNNTNp/eisWX1MyI7UtwqEI8X93wYI="; </ins> }; nativeBuildInputs = [ poetry-core ];

Discussion:
Python package betterproto is missing setuptools as a run time dependency This is my fixing the issue Give me some feedback if this is not properly reported, I'm a newbie when it comes to reporting issues
see
Change:
stdenv.mkDerivation (finalAttrs: { pname = "srb2"; <del> version = "2.2.11"; </del> <ins> version = "2.2.13"; </ins> src = fetchFromGitHub { owner = "STJr"; repo = "SRB2"; rev = "SRB2_release_${finalAttrs.version}"; <del> hash = "sha256-tyiXivJWjNnL+4YynUV6k6iaMs8o9HkHrp+qFj2+qvQ="; </del> <ins> hash = "sha256-OSkkjCz7ZW5+0vh6l7+TpnHLzXmd/5QvTidRQSHJYX8="; </ins> }; nativeBuildInputs = [

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:
, pythonOlder , rply , testers <del> , toPythonApplication , hyDefinedPythonPackages ? python-packages: [ ] /* Packages like with python.withPackages */ </del> }: buildPythonPackage rec { pname = "hy"; <del> version = "1.0a4"; </del> <ins> version = "0.24.0"; </ins> format = "setuptools"; disabled = pythonOlder "3.7";

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: desired version: <!-- 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:
# also make sure to update the udev rules in ./10-dygma.rules; most recently # taken from <del> # https://github.com/Dygmalab/Bazecor/blob/v1.3.8/src/main/utils/udev.ts#L6 </del> <ins> # https://github.com/Dygmalab/Bazecor/blob/v1.3.9/src/main/utils/udev.ts#L6 </ins> extraPkgs = p: (appimageTools.defaultFhsEnvArgs.multiPkgs p) ++ [ p.glib

Discussion:
The package is missing a entry for application launchers. It should have a entry for application launchers. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks, fix is in
Change:
jump = callPackage ../tools/system/jump {}; <del> kindlegen = callPackage ../tools/typesetting/kindlegen { }; </del> latex2html = callPackage ../tools/misc/latex2html { }; latexrun = callPackage ../tools/typesetting/tex/latexrun { };

Discussion:
. Consequently, the is broken. I suppose we need to choose whether to remove the package or find a mirror? CC maintainer: Side notes: Sadly, its replacement, , has no Linux support. But on a more positive note, there are other programs that can produce mobi files, some mentioned in .
I suggest we just drop it. Considering that kindlegen was under an unfree license, we're probably not allowed to distribute it, so let's just blow it away with a release note entry that mentions some alternatives.
I marked this as stale due to inactivity. &rarr;
My current recommendation for NixOS is to use calibre for conversion. It also has commandline tools for scripting.
Change:
name = "debian-9.8-stretch-i386"; fullName = "Debian 9.8 Stretch (i386)"; packagesList = fetchurl { <del> url = http://snapshot.debian.org/archive/debian/20190503T090946Z/dists/stretch/main/binary-i386/Packages.xz; sha256 = "1dr3skl35iyj85qlc33lq4whippbqf327vnbcyfqqrv6h86k68mw"; </del> <ins> url = http://snapshot.debian.org/archive/debian/20200301T030401Z/dists/stretch/main/binary-i386/Packages.xz; sha256 = "1jglr1d1jys3xddp8f7w9j05db39fah8xy4gfkpqbd1b5d2caslz"; </ins> }; urlPrefix = mirror://debian; packages = commonDebianPackages;

Discussion:
Describe the bug See This is because vmTools.diskImageFuns.debian9i386 doesn't build
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
Closing since indicates that it fixed this.