jiebi/CodeConvo huggingface dataset:
Change:
flashplayer-standalone = throw "flashplayer-standalone has been removed as Adobe Flash Player is now deprecated"; # Added 2021-02-07 flashplayer = throw "flashplayer has been removed as Adobe Flash Player is now deprecated"; # Added 2021-02-07 flashtool = throw "flashtool was removed from nixpkgs, because the download is down for copyright reasons and the site looks very fishy"; # Added 2021-06-31 <ins> flatbuffers_1_12 = throw "FlatBuffers version 1.12 has been removed, because upstream no longer maintains it"; # Added 2022-05-12 flatbuffers_2_0 = flatbuffers; # Added 2022-05-12 </ins> flink_1_5 = throw "flink_1_5 was removed, use flink instead"; # Added 2021-01-25 flutter-beta = throw "Non-stable versions of Flutter have been removed. You can use flutterPackages.mkFlutter to generate a package for other Flutter versions"; # Added 2020-01-15 flutter-dev = throw "Non-stable versions of Flutter have been removed. You can use flutterPackages.mkFlutter to generate a package for other Flutter versions"; # Added 2020-01-15

Discussion:
We define two packages, one for version 1.12 and one for version 2.0. The package for version 1.12 . Upstream has the fixes needed but only for version 2.0. The version 1.12 branch does not appear maintained, and there to it since March of 2020. We can continue to maintain this (e.g. we can disable warnings, or we can adapt those fixes to 1.12 and patch them), but perhaps we could drop support for the old version altogether? ZHF: /cc
Disabling -Werror is always reasonable, but if there's no users left in nixpkgs I think it's ok to drop it. Unless the maintainer or someone else still has a use for this (do a scream test by removing it, I guess)
is unused and can be safely removed.
Change:
, pytest-mock , pytest-xdist , pythonAtLeast <ins> , darwin </ins> }: buildPythonPackage rec {

Discussion:
Steps to reproduce the behavior: poetry on macOS ARM64 from current master (so that is fixed) with fails It boils down to: Building works on Linux ARM64. Don't know about macOS x64. ? Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
~duplicate~ Sorry, I misread.
Change:
<p align="center"> <del> <a href="https://nixos.org#gh-light-mode-only"> <img src="https://raw.githubusercontent.com/NixOS/nixos-homepage/master/logo/nixos-hires.png" width="500px" alt="NixOS logo"/> </a> <a href="https://nixos.org#gh-dark-mode-only"> <img src="https://raw.githubusercontent.com/NixOS/nixos-artwork/master/logo/nixos-white.png" width="500px" alt="NixOS logo"/> </del> <ins> <a href="https://nixos.org"> <picture> <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/NixOS/nixos-homepage/master/logo/nixos-hires.png"> <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/NixOS/nixos-artwork/master/logo/nixos-white.png"> <img src="https://raw.githubusercontent.com/NixOS/nixos-homepage/master/logo/nixos-hires.png" width="500px" alt="NixOS logo"> </picture> </ins> </a> </p>

Discussion:
<!-- describe your problem --The logo at the top of the README is currently using a now deprecated method for using different logo's depending on the user's theme From: <!-- propose a solution (optional) --This is fixed by switching to the recommended method. I believe it should be something like <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<ins> { appimageTools, lib, fetchurl, }: let pname = "rquickshare"; version = "0.7.1"; src = fetchurl { url = "https://github.com/Martichou/rquickshare/releases/download/v${version}/r-quick-share_${version}_amd64.AppImage"; hash = "sha256-716d7T4nbs/dDS4KVGTADCpLO31U8iq6hDVD+c7Ks1I="; }; appimageContents = appimageTools.extractType2 { inherit pname version src; }; in appimageTools.wrapType2 { inherit pname version src; extraInstallCommands = '' install -Dm444 ${appimageContents}/r-quick-share.desktop -t $out/share/applications substituteInPlace $out/share/applications/r-quick-share.desktop  --replace-fail 'Exec=r-quick-share' 'Exec=rquickshare %u' cp -r ${appimageContents}/usr/share/icons $out/share ''; meta = { description = "Rust implementation of NearbyShare/QuickShare from Android for Linux"; homepage = "https://github.com/Martichou/rquickshare"; changelog = "https://github.com/Martichou/rquickshare/blob/v${version}/CHANGELOG.md"; license = lib.licenses.gpl3Plus; maintainers = [ lib.maintainers.luftmensch-luftmensch ]; platforms = [ "x86_64-linux" ]; sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ]; mainProgram = "rquickshare"; }; } </ins>

Discussion:
Project description is implementation of QuickShare (NearbyShare) About QuickShare: Metadata homepage URL: source URL: license: gpl3 platforms: linux It might also work on macOS. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
makeWrapper gettext python3.pkgs.wrapPython <ins> wrapGAppsNoGuiHook </ins> python3.pkgs.setuptools-scm ]; buildInputs = [ librsync <ins> # For Gio typelib glib </ins> ]; pythonPath = with python3.pkgs; [

Discussion:
Upon attempting to start the backup process, the following error is shown, resulting in the backup failing to start: Steps to reproduce the behavior: deja-dup (Backups) to create a backup Backup run properly without issues ! Similar to , but with a different Python library (Gio) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I have located the derivation files for both the working and non-working version. working: non-working:
Thanks for reporting. probably needs I opened , could you please test it?
The fix works!
Change:
{ lib , stdenv , fetchFromGitHub <ins> , fetchpatch </ins> , SDL2 , cmake , curl , discord-rpc , duktape <ins> , expat </ins> , flac , fontconfig , freetype

Discussion:
Package name: openrct2 Latest released version: 0.4.6 Current version on the unstable channel: 0.4.5 Current version on the stable/release channel: 0.4.4 Notify maintainers Note for maintainers: Please tag this issue in your PR.
I attempted this one, and even though all the new title-sequences files are in the same place as the old ones, it fails to load those. And it fails to load the park files from the original games, that reads without any issues in 0.4.5. Failure logs: Note that object conflict also happens in 0.4.5. Bump commit: Use SRI-hash field: Use "srcs" (solves ):
I experienced the same when I tried 0.4.6 with an overlay. Also could not connect to multiplayer games because he could not load the map. Hoped that somebody more knowledgeable in NixOS could solve this.
Please excuse the late reply. When 0.4.6 came out, I tried bumping the versions as I did before and ran in the same buggy behavior as and did. Since then I procrastinated debugging it. I'm hoping that I'll find time this week. If someone else beats me with that, I would also be happy.
Change:
currentConfigPath = "$STATE_DIRECTORY/.nixos-current-config.json"; runnerRegistrationConfig = getAttrs [ "name" "tokenFile" "url" "runnerGroup" "extraLabels" ] cfg; newConfigPath = builtins.toFile "${svcName}-config.json" (builtins.toJSON runnerRegistrationConfig); <del> currentConfigTokenFilename = ".current-token"; </del> newConfigTokenFilename = ".new-token"; runnerCredFiles = [ ".credentials" ".credentials_rsaparams" ".runner" ]; <del> ownConfigTokens = writeScript "own-config-tokens" '' # Copy current and new token file to runtime dir and make it accessible to the service user cp ${escapeShellArg cfg.tokenFile} "$RUNTIME_DIRECTORY/${newConfigTokenFilename}" chmod 600 "$RUNTIME_DIRECTORY/${newConfigTokenFilename}" chown "$USER" "$RUNTIME_DIRECTORY/${newConfigTokenFilename}" if [[ -e "$STATE_DIRECTORY/${currentConfigTokenFilename}" ]]; then cp "$STATE_DIRECTORY/${currentConfigTokenFilename}" "$RUNTIME_DIRECTORY/${currentConfigTokenFilename}" chmod 600 "$RUNTIME_DIRECTORY/${currentConfigTokenFilename}" chown "$USER" "$RUNTIME_DIRECTORY/${currentConfigTokenFilename}" fi ''; disownConfigTokens = writeScript "disown-config-tokens" '' # Make the token inaccessible to the runner service user chmod 600 "$STATE_DIRECTORY/${currentConfigTokenFilename}" chown root:root "$STATE_DIRECTORY/${currentConfigTokenFilename}" ''; </del> unconfigureRunner = writeScript "unconfigure" '' differs= # Set `differs = 1` if current and new runner config differ or if `currentConfigPath` does not exist ${pkgs.diffutils}/bin/diff -q '${newConfigPath}' "${currentConfigPath}" >/dev/null 2>&1 || differs=1 # Also trigger a registration if the token content changed ${pkgs.diffutils}/bin/diff -q  <del> "$RUNTIME_DIRECTORY"/{${currentConfigTokenFilename},${newConfigTokenFilename}}  </del> <ins> "$STATE_DIRECTORY"/${currentConfigTokenFilename}  ${escapeShellArg cfg.tokenFile}  </ins> >/dev/null 2>&1 || differs=1 if [[ -n "$differs" ]]; then

Discussion:
After rebooting the machine, the systemd service fails to start due to an "invalid user: ‘github-runner’" Steps to reproduce the behavior: The systemd service enters the state : It does not happen after every reboot. I have not found the circumstances that make the systemd service fail. One workaround to bring the service back to the running state is to manually restart . Please run and paste the result. Maintainer information:
Thanks for raising this. I guess I ran into this as well already but didn't give it too much thought. Now, after reading systemd.service(5) again, I believe we should prefix with instead of : I'm not sure that's really the issue but it seems like the user/group () is not always set up when systemd runs . It appears would make sure they exist. I'm going to open a PR. Regardless of fixing this issue (which I hope it does), it makes sense to use instead of .
Wow, thanks for the quick response! I will check out your PR soon.
Change:
export LC_ALL=C.UTF-8 ''; <del> multiPkgs = extraPkgs; extraPkgs = pkgs: (appimageTools.defaultFhsEnvArgs.multiPkgs pkgs) ++ ([ udev wooting-udev-rules xorg.libxkbfile ]); </del> <ins> extraPkgs = pkgs: with pkgs; ([ xorg.libxkbfile ]); </ins> <del> meta = with lib; { </del> <ins> meta = { </ins> homepage = "https://wooting.io/wootility"; description = "Customization and management software for Wooting keyboards"; <del> platforms = [ "x86_64-linux" ]; license = licenses.unfree; maintainers = with maintainers; [ davidtwco sodiboo ]; </del> <ins> platforms = lib.platforms.linux; license = lib.licenses.unfree; maintainers = with lib.maintainers; [ davidtwco sodiboo ]; </ins> mainProgram = "wootility"; }; }

Discussion:
It would be nice if the packages provided a icon. the following in your : up a graphical application launcher and search for Wootility. Please run and paste the result. <pre<samp- system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: </samp</pre
PR submitted that, among other things, adds a desktop-entry file.
Change:
overrideSDK = platform: version: <del> platform // lib.optionalAttrs (platform ? darwinMinVersion) { darwinMinVersion = version; }; </del> <ins> platform // lib.optionalAttrs (platform ? darwinMinVersion) { darwinMinVersion = version; }; </ins> stdenv' = if swiftSupport && stdenv.isDarwin && stdenv.isx86_64 then stdenv.override (old: { <del> buildPlatform = overrideSDK old.buildPlatform "10.15"; hostPlatform = overrideSDK old.hostPlatform "10.15"; targetPlatform = overrideSDK old.targetPlatform "10.15"; </del> <ins> buildPlatform = overrideSDK old.buildPlatform "11.0"; hostPlatform = overrideSDK old.hostPlatform "11.0"; targetPlatform = overrideSDK old.targetPlatform "11.0"; </ins> }) else stdenv;

Discussion:
Steps to reproduce the behavior: mpv-unwrapped on x86_64-darwin Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Unless I got confused this is still a problem on nixos-unstable, but according to the fix was merged there
It looks like not a same error?
You're right. This one seems like it's originating in swift.
I was also confused because I have the same error when building mpv, but yeah looks like a swift error. Any solutions?
The build-failure reported in this issue seems to be unrelated to the recent swift breakage on Darwin. Where swift-dependent packages like mpv are currently broken on Darwin. I suggest opening a separate issue to track mpv's build-failure due to swift on Darwin. There is an open-issue for the swift build failure at .
Change:
<del> { lib, stdenv </del> <ins> { lib , stdenv </ins> , fetchFromGitHub <del> , autoconf-archive , appstream-glib </del> <ins> , substituteAll , fetchpatch , meson , ninja </ins> , pkg-config , wrapGAppsHook <ins> , desktop-file-utils </ins> , libcanberra , gst_all_1 , vala

Discussion:
Enabling the gnome-shell extension provided by fails, as can be seen in the output below. It specifically results in an error that I found in the Extensions app (). See screenshot below. Launching the standalone app also produces the same error, but sends it to the user as a desktop notification. Steps to reproduce the behavior: to in . to in for debugging. . the machine (logging out of the current GNOME session and logging back in should also work). to enable the extension by executing that the GNOME Pomodoro icon is not displayed in the topbar. that the output of includes . the Extensions application, click the dropdown beside Pomodoro, and notice the error message displayed (). the Pomodoro application for the first time in a GNOME session, and notice that it sends a notification to the user with the same error message (). GNOME Pomodoro would be displayed in the topbar as an item on the right. The output of should include rather than after enabling the extension Opening the standalone GNOME Pomodoro application would not result in an error notification being sent to the user. Opening the Extensions app, this is the error we're presented with. ! This is the topbar item we expect to get (screenshot from an older version of GNOME, not mine): ! This appears to be a NixOS-specific bug. It has been reported in the project's repository also () for NixOS 20.05, but I could not find a corresponding issue in this tracker. I can confirm that this package works as expected on at least one other distribution which officially packages it (Fedora 34). They appear to be tracking upstream without adding any patches (see: ) There doesn't appear to be a maintainer specified; pinging the person who co-committed the last change to bump version. My system is built using flakes; providing the output of both in my nixfiles directory, as well as the output requested. Maintainer information:
Change:
<del> diff -ur RetroFE.1/RetroFE/Source/CMakeLists.txt RetroFE.2/RetroFE/Source/CMakeLists.txt --- RetroFE.1/RetroFE/Source/CMakeLists.txt	2016-02-21 14:52:36.726070602 +0100 +++ RetroFE.2/RetroFE/Source/CMakeLists.txt	2016-02-21 14:38:43.036249029 +0100 @@ -59,6 +59,7 @@ set(RETROFE_INCLUDE_DIRS "${GLIB2_INCLUDE_DIRS}" "${GSTREAMER_INCLUDE_DIRS}" +	"${GSTREAMER_BASE_INCLUDE_DIRS}" "${SDL2_INCLUDE_DIRS}" "${SDL2_IMAGE_INCLUDE_DIRS}" "${SDL2_MIXER_INCLUDE_DIRS}" </del>

Discussion:
Looks like it lives and now. in nixpkgs hasn't been touched in 6 years. <!-- 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: 0.6.169 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:
configureFlags = ["--enable-shared" "--enable-pthread" "--with-soname=ruby-${version}"] ++ op useRailsExpress "--with-baseruby=${baseruby}/bin/ruby" <ins> ++ op (!jitSupport) "--disable-jit-support" </ins> ++ op (!docSupport) "--disable-install-doc" ++ ops stdenv.isDarwin [ # on darwin, we have /usr/include/tk.h -- so the configure script detects

Discussion:
Describe the bug I'm hunting down packages that reference gcc. One of them is (maintainers: & ). Here's why: The fault is the fact that the build flag doesn't remove all references, as one might expect (EDIT, see: ). I'm up to including this feature, but I was wondering perhaps it'd be legit to disable this feature for the derivation? I opened a PR at (EDIT).
But that would mean gems that require a compiler would no longer work.
The suggestion is for , not . Isn't the derivation that's used to build the gems? According to:
It still has support for gems, so some will fail with gcc. What exactly is the use case for ?
Technically it's not used anywhere, according to .
I'd like to make my - with an overlay. The goal is to make the 1 or 2 pure ruby scripts I have on my system not pull , as they do today.
But what is the reason? You're likely to have a version of ruby that includes gcc on your system anyway, so you don't really save any space. And the use-case would be plain ruby scripts with only the gems that don't require system libraries. We have no users in nixpkgs of presumably because it's rather pointless. And while of course we can strip gcc from rubyMinimal (there's no harm), I'd rather say drop instead.
Not If I'll apply and this overlay: This allows me to not need GCC for for example - which is the only ruby gem I use. For example, run with this PR and that overlay applied: And you should get: And without , (and without the overlay because it would fail) you should get: is the only derivation that needs ruby that I actually use. I've updated the 1st comment in to exemplify this overlay as a possible usecase. Well I tend to agree - even for asciidoctor which should be pretty much a pure ruby gem, it still required and which aren't enabled in current . Hence I tend to agree. OK so I've updated to include a drop to , including release notes and an alias. Waiting for your review :crossed_fingers: .
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
] ++ cfg.extraOptions ); <del> path = [ cfg.qemu.package ] # libvirtd requires qemu-img to manage disk images </del> <ins> path = [ cfg.qemu.package pkgs.netcat ] # libvirtd requires qemu-img to manage disk images </ins> ++ optional vswitch.enable vswitch.package ++ optional cfg.qemu.swtpm.enable cfg.qemu.swtpm.package;

Discussion:
Virt-manager requires netcat version with support for arguments. version available by default does not. Steps to reproduce the behavior: virt-manager into a profile connecting to remote machine Connection successful virt-manager complains about not supporting flag. ! <!-- 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. (this is probably mostly irrelevant as I'm using flakes to manage my profile)
Both and do support -U but does not. Since this needs to be available on the remote machine, we should add this to the module.
Change:
}: assert cloog != null -> stdenv.lib.versionOlder version "5"; <del> assert langJava -> stdenv.lib.versionOlder version "6"; </del> <ins> assert langJava -> stdenv.lib.versionOlder version "7"; </ins> let inherit (stdenv)

Discussion:
Describe the bug On release-19.09, or later, I cannot eval pdftk, which uses gcj: Things are fine on the previous commit, To Reproduce Steps to reproduce the behavior: ~/code/nixpkgs && git fetch checkout origin/release-19.09 -env --show-trace --builders '' -f ~/code/nixpkgs -iA pdftk Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: Maintainer information: cc related
Change:
, gettext , makeDesktopItem , copyDesktopItems <ins> , wrapGAppsHook </ins> }: python3.pkgs.buildPythonApplication rec {

Discussion:
re , the package crashes with when a file dialog is opened (eg. file -open). The rest of the program seems to work. I tried adding wrapGAppsHook, gsettings-desktop-schemas, and glib, but none of those fixed it. I'm running awesome wm, nixos 21.11 cc
Some resources i found related to the error message: timeline sources does not have schemas files. maybe is not set correctly on your system do you know how to fix this issue?
That might be a issue (since it defaults to true for ). See similar issue with
other gnome stuff seems to work though
You need to use . Global intentionally will not contain schemas.
I did try wrapGAppsHook, but that didn't fix it. maybe I did it wrong?
As mentioned above, for Python packages, you might also need to disable .
I tried using and , and it still errors out
Change:
<ins> From 5c158213fc3afe39ee96be84e255c12d5886ca18 Mon Sep 17 00:00:00 2001 From: Pavel Sobolev <paveloom@riseup.net> Date: Sat, 1 Apr 2023 17:38:37 +0300 Subject: [PATCH] Add a hash to the `googletest` binary. --- CMakeLists.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/CMakeLists.txt b/CMakeLists.txt index 0a06e6f..a614025 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -434,6 +434,7 @@ include(FetchContent) FetchContent_Declare( googletest URL https://github.com/google/googletest/archive/609281088cfefc76f9d0ce82e1ff6c30cc3591e5.zip +  URL_HASH SHA256=5cf189eb6847b4f8fc603a3ffff3b0771c08eec7dd4bd961bfd45477dd13eb73 ) # For Windows: Prevent overriding the parent project's compiler/linker settings set(gtest_force_shared_crt ON CACHE BOOL "" FORCE) -- 2.39.2 </ins>

Discussion:
Project description Codon is a high-performance Python compiler that compiles Python code to native machine code without any runtime overhead. Typical speedups over Python are on the order of 10-100x or more, on a single thread. Codon's performance is typically on par with (and sometimes better than) that of C/C++. Unlike Python, Codon supports native multithreading, which can lead to speedups many times higher still. Codon grew out of the . Metadata homepage URL: source URL: license: Business Source License 1.1 platforms: unix, linux, darwin
I didn't compile it properly, but if you want to run the official binaries on NixOS, this does the job: