jiebi/CodeConvo huggingface dataset:
Change:
keybase-go = keybase;  # added 2016-08-24 kinetic-cpp-client = throw "kinetic-cpp-client has been removed from nixpkgs, as it's abandoned."; # 2020-04-28 kicad-with-packages3d = kicad; # added 2019-11-25 <ins> kindlegen = throw "kindlegen has been removed from nixpkgs, as it's abandoned and no longer available for download."; # 2021-03-09 </ins> krename-qt5 = krename; # added 2017-02-18 keymon = throw "keymon has been removed from nixpkgs, as it's abandoned and archived."; # 2019-12-10 kvm = qemu_kvm; # added 2018-04-25

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:
, autoconf , automake , libtool <del> , faad2 , mp4v2 </del> }: <del> stdenv.mkDerivation rec { </del> <ins> stdenv.mkDerivation { </ins> pname = "aacgain"; <del> version = "2.0.0"; </del> <ins> version = "2.0.0-unstable-2022-07-12"; </ins> src = fetchFromGitHub { owner = "dgilman"; <del> repo = pname; rev = version; sha256 = "sha256-9Y23Zh7q3oB4ha17Fpm1Hu2+wtQOA1llj6WDUAO2ARU="; </del> <ins> repo = "aacgain"; rev = "9f9ae95a20197d1072994dbd89672bba2904bdb5"; hash = "sha256-WqL9rKY4lQD7wQSZizoM3sHNzLIG0E9xZtjw8y7fgmE="; fetchSubmodules = true; </ins> }; <del> postPatch = '' cp -R ${faad2.src}/* 3rdparty/faad2 cp -R ${mp4v2.src}/* 3rdparty/mp4v2 chmod -R +w 3rdparty ''; </del> nativeBuildInputs = [ cmake autoconf

Discussion:
Steps to reproduce the behavior: I believe this is the most important bit from the logs: Please run and paste the result.
The build log linked above does not seem to be complete. This should be a more complete log:
Oops, thanks I've fixed the gist. For the record, the permissions on your pastebin seem to be wrong, I get this error when I try to view it: "This page is no longer available. It has either expired, been removed by its creator, or removed by one of the Pastebin staff."
Hmm not sure what happened there but now that you've updated the gist I don't think that I need to fix the pastebin link.
Happens here too. Can't upgrade beets due to the build failure.
Same issue here: output of nix-shell -p nix-info --run "nix-info -m" : Using following input in my = "";
Apparently this issue was mentioned 3 days ago:
Is there even any more reason for beets to depend on aacgain (nor mp3gain for that matter) since AFAIK the default replaygain backend was changed to ffmpeg?
Adding (beets) and (aacgain) and (aacgain)
Here is the failed build report from Hydra:
By observing the aacgain's Nix expression, I think it'd be ideal to make it link to the "system"'s and libraries. Regarding beets, it still supports using aacgain, both in the unstable and stable flavors. If you won't be able to fix the issue and you'd mark it as broken or something, we'll get along without it, I'd only ask you to notify us so we could propose something in the same PR marking it as broken.

The default replaygain backend looks to still be mp3gain/aacgain (depending on which is available):
error: getting status of /nix/var/nix/daemon-socket/socket: Permission denied i got these
error: … <borkedat «none»:0: (source not available) … while calling the 'import' builtin at «string»:1:18: 1| {...} with import <nixpkgsargs; (pkgs.runCommandCCr pkgs.runCommand) "shell" { buildInputs = [ (nix-info) ]; } "" | ^ (stack trace truncated; use '--show-trace' to show the full trace) error: file 'nixpkgs' was not found in the Nix search path (add itsing $NIX_PATH or -I) at «none»:0: (source not available)
, this issue was closed about half a year ago. Could you please open a new issue and provide a bit more context? I just tried building on , and everything worked out fine. Also, has been updated recently and works fine here!
Change:
system.build.installBootLoader = pkgs.writeScript "install-lxd-sbin-init.sh" '' #!${pkgs.runtimeShell} <del> ln -fs "$1/init" /sbin/init </del> <ins> ${pkgs.coreutils}/bin/ln -fs "$1/init" /sbin/init </ins> ''; systemd.additionalUpstreamSystemUnits = lib.mkIf cfg.nestedContainer ["systemd-udev-trigger.service"];

Discussion:
A recent change introduced () which runs by using systemd-run. This brings with it better isolation of the new system/ a cleaner execution environment, although the new environment appears to be lacking most/all of from the currently running system. This means that the command in  cannot be found when the script is run inside of systemd-run. This has been breaking my NixOS install within OrbStack. I've been able to fix the problem by including the absolute path to (ie ); PR coming shortly. Steps to reproduce the behavior: LXD container: run Error message: Should switch to new system configuration without errors If applicable, add screenshots to help explain your problem. Content of Command producing error: <!-- 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.
Change:
<del> --- sbsigntools/configure.ac	2018-09-25 10:30:00.878766256 -0500 +++ configure.ac.new	2018-09-25 10:34:56.231277375 -0500 @@ -71,15 +71,16 @@ </del> <ins> diff --git a/configure.ac b/configure.ac index 4ffb68f..d8a8265 100644 --- a/configure.ac +++ b/configure.ac @@ -71,15 +71,16 @@ AM_CONDITIONAL(TEST_BINARY_FORMAT, [ test "$EFI_ARCH" = "arm" -o "$EFI_ARCH" = " </ins> # no consistent view of where gnu-efi should dump the efi stuff, so find it ## <del> for path in /lib /lib64 /usr/lib /usr/lib64 /usr/lib32 /lib/efi /lib64/efi /usr/lib/efi /usr/lib64/efi; do </del> <ins> for path in /lib /lib64 /usr/lib /usr/lib64 /usr/lib32 /lib/efi /lib64/efi /usr/lib/efi /usr/lib64/efi /usr/lib/gnuefi /usr/lib64/gnuefi ; do </ins> -    if test -e $path/crt0-efi-$EFI_ARCH.o; then -       CRTPATH=$path +    if test -e @@NIX_GNUEFI@@/$path/crt0-efi-$EFI_ARCH.o; then

Discussion:
The systemd-boot image built in nixpkgs has gaps in the section table. This leads to signature verification failure with some UEFI Secure Boot implementations (e.g. Dell XPS 13 9310) Using NixOS 22.05 @ Using some old version from NixOS 21.11 that I still have in the store: N/A Allegedly something like this was fixed in systemd upstream and the commit is present in v250.4 but for some reason it still appears and Secure Boot fails. <!-- 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:
Relevant:
This commit might be the culprit: I will try confirm this, but since it requires rebuilding systemd, it'll take a while.
It's more likely a problem of sbsigntools:
Does your hardware still correctly validate the signature with this patch applied?
Yes, signature verification works with this patch (and only with this patch). Hardware is Dell XPS 13 9310. See also
Change:
<ins> { rustPlatform, lib, fetchFromGitHub, pkg-config, glib, pango, gdk-pixbuf, graphene, gtk4, copyDesktopItems, makeDesktopItem, wrapGAppsHook4, }: rustPlatform.buildRustPackage rec { pname = "airgorah"; version = "0.7.3"; src = fetchFromGitHub { owner = "martin-olivier"; repo = "airgorah"; rev = "refs/tags/v${version}"; hash = "sha256-cIb40TKkk3gfy4dTP8WyZqQkRGj5nItaQ3NSfexCUOA="; }; cargoHash = "sha256-sJFOpxBW6Z8ewfyhJuxZByJNgaEmezw15OQt9KjFaec="; nativeBuildInputs = [ pkg-config copyDesktopItems wrapGAppsHook4 ]; buildInputs = [ glib pango gdk-pixbuf graphene gtk4 ]; postInstall = '' install -Dm644 icons/app_icon.png $out/share/icons/hicolor/1024x1024/apps/airgorah.png ''; dessktopItems = [ (makeDesktopItem { name = "airgorah"; comment = "A WiFi auditing software that can perform deauth attacks and passwords cracking"; desktopName = "airgorah"; exec = "pkexec airgorah"; icon = "airgorah"; categories = [ "Network" "Monitor" "Utility" "GTK" ]; type = "Application"; terminal = false; }) ]; meta = { description = "WiFi security auditing software mainly based on aircrack-ng tools suite"; homepage = "https://github.com/martin-olivier/airgorah"; changelog = "https://github.com/martin-olivier/airgorah/releases/tag/v${version}"; license = lib.licenses.mit; mainProgram = "airgorah"; maintainers = with lib.maintainers; [ bot-wxt1221 ]; platforms = lib.platforms.linux; }; } </ins>

Discussion:
Project description A WiFi security auditing software mainly based on aircrack-ng tools suite. Metadata homepage URL: source URL: license: mit platforms: linux
Change:
sed '1i#include <ctime>' -i include/openbabel/obutil.h # gcc12 ''; <del> buildInputs = [ perl zlib libxml2 eigen python cairo pcre swig rapidjson ]; </del> <ins> buildInputs = [ perl zlib libxml2 eigen python cairo pcre swig rapidjson boost maeparser coordgenlibs ]; </ins> nativeBuildInputs = [ cmake pkg-config ]; <del> pythonMajorMinor = "${python.sourceVersion.major}.${python.sourceVersion.minor}"; cmakeFlags = [ "-DRUN_SWIG=ON" "-DPYTHON_BINDINGS=ON" ]; </del> <ins> preConfigure = '' cmakeFlagsArray+=( "-DRUN_SWIG=ON" "-DPYTHON_BINDINGS=ON" "-DPYTHON_INSTDIR=$out/${python.sitePackages}" ) ''; </ins> # Setuptools only accepts PEP 440 version strings. The "unstable" identifier # can not be used. Instead we pretend to be the 3.2 beta release. postFixup = '' <del> cat <<EOF > $out/lib/python$pythonMajorMinor/site-packages/setup.py from distutils.core import setup </del> <ins> cat << EOF > $out/${python.sitePackages}/setup.py from setuptools import setup </ins> setup( name = 'pyopenbabel',

Discussion:
Steps to reproduce the behavior: openbabel or any package that depends on it, i.e Kalzium The issue seems to have appeared in the most recent push to nixos-unstable, it seems to be an issue with the openbabel dependency <!-- 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]:
Actually after properly inspecting this issue I realize that it is rather an issue with it's dependency, openbabel that fails to build
The problem is exactly this line and Python 3.12, which removed distutils: We can work around it by setting in CMake , but I didn't manage to get the Python bindings to build again, as the nix expression also crafts a custom like that:
Change:
drvName = drv: discard (substring 33 (stringLength (builtins.baseNameOf drv)) (builtins.baseNameOf drv)); <del> rewriteHashes = drv: hashes: runCommand (drvName drv) { nixStore = "${nix.out}/bin/nix-store"; } '' </del> <ins> rewriteHashes = drv: hashes: runCommandLocal (drvName drv) { nixStore = "${nix.out}/bin/nix-store"; } '' </ins> $nixStore --dump ${drv} | sed 's|${baseNameOf drv}|'$(basename $out)'|g' | sed -e ${ concatStringsSep " -e " (mapAttrsToList (name: value: "'s|${baseNameOf name}|${baseNameOf value}|g'"

Discussion:
Currently when distributed builds enabled each derivation is uploaded to the remote server to have their hashes rewritten. Within pkgs/build-support/replace- the 'replaceHashes; derivation should be marked in such a way so that the replacement is done locally for those people who have enabled distributed builds. I believe there is a simple way to do this, but I need to look up how it is done. I've assigned myself this issue, but you might also be interested in fixing it.
, I suppose.
(triage) , any update on this ? Have you fixed it ?
Are there any updates to this issue, please?
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
Change:
description = "Decode traffic from devices that broadcast on 433.9 MHz, 868 MHz, 315 MHz, 345 MHz and 915 MHz"; homepage = "https://github.com/merbanan/rtl_433"; license = licenses.gpl2Plus; <del> maintainers = with maintainers; [ earldouglas ]; </del> <ins> maintainers = with maintainers; [ earldouglas markuskowa ]; </ins> platforms = platforms.all; };

Discussion:
, CVSSv3=5.5 (nixos-unstable) rtl433 21.12 was discovered to contain a stack overflow in the function acurite00275rm_decode at /devices/acurite.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted file. Scanned versions: nixos-unstable: . Cc
See also:
Change:
<ins> { lib, stdenvNoCC, fetchFromGitHub, makeWrapper, git, fzf, }: stdenvNoCC.mkDerivation (finalAttrs: { pname = "git-toolbelt"; version = "1.9.1"; src = fetchFromGitHub { owner = "nvie"; repo = "git-toolbelt"; rev = "v${finalAttrs.version}"; hash = "sha256-lrVMSItA0Eo7DgB+QjOLPPxwMLaC9+6FNPrhw6pkpKA="; }; nativeBuildInputs = [ makeWrapper ]; buildInputs = [ git fzf # needed by git-fixup-with ]; installPhase = '' runHook preInstall install -Dm755 git-* -t "$out"/bin for exe in "$out"/bin/*; do wrapProgram "$exe"  --prefix PATH : "$out"/bin:${lib.makeBinPath finalAttrs.buildInputs} done runHook postInstall ''; meta = { changelog = "https://github.com/nvie/git-toolbelt/blob/${finalAttrs.src.rev}/CHANGELOG.md"; description = "A suite of useful Git commands that aid with scripting or every day command line usage"; homepage = "https://github.com/nvie/git-toolbelt"; license = lib.licenses.bsd3; maintainers = with lib.maintainers; [ tomasajt ]; platforms = lib.platforms.all; }; }) </ins>

Discussion:
Project description "A suite of useful Git commands" Metadata homepage URL: N/A source URL: license: BSD 3-Clause platforms: All, I think? (I'd like it for linux, please!) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
# dropDot :: String -> String inherit dropDot; } // formatCapabilities { <del> cudaCapabilities = config.cudaCapabilities or supportedCapabilities; </del> <ins> cudaCapabilities = config.cudaCapabilities or defaultCapabilities; </ins> enableForwardCompat = config.cudaForwardCompat or true; }

Discussion:
Steps to reproduce the behavior: magma From : Also may be interested.
Is this related to the race condition error you saw before?
can you tell me more about what hardware you're using, and what your looks like? For reference, runs without issue for me with using a 4090 and an i9 13900k: EDIT: Would you also try building with I made some changes there that moved the CUDA runtime stub and NVCC into . I'm curious if that helps at all.
I don't think so -- closest I can remember to this was the linking error AMD HIP had with 2.7.x (which is why its stuck on magma 2.6.x), but that was a different inscrutable error from .
CPU is a Xeon Gold 5218 with Quadro RTX 8000 GPUs. I haven't set any configuration other than and .
I don't know why this issue isn't affecting your builds but most likely the fix is to set :
Haven't tried yet either, sorry.
Any idea when this failure started occurring?
magma 2.6.2 I believe works but 2.7.1 fails. I can try to bisect at some point if needed.
What channel were you building from by the way? I'm gonna try to find a way to match your setup but I need to know exactly which version of nixpkgs you're using to build.
Okay, I was able to reproduce it. It happened while a Nixpkgs-review for that magma PR I linked earlier. I suspect it has something to do with either my disabling or restricting . Time to investigate ‍
Something for me to look at later tonight; if it is the case that the increased number of cuda capabilities being targeted is causing the binary to bloat, check that we're using , like PyTorch : IIRC Magma doesn't set that flag. Also, I remember being unable to find specifically in the NVCC docs. Since PyTorch also ships binaries targeting a bunch of different CUDA capabilities, their configs are a goldmine of flags we might need to look into. EDIT: Haven't built with it yet, but it seems like it should fix it.

Apache MXNet had the same issue: EDIT2: Reminder to self: if that is the fix, add here: and here:
I know it's still a draft but can you try building again with I think it should fix your issue. Unrelated, but if you're building anything from source and you want faster builds I highly recommend specifying the single compute capability you need to build for (like I do here ) because it results in massively faster builds. HEAD right now builds for 14 different capabilities and that PR gets it down to 8, but it's much faster to build for just one.
is building for me from that branch (without any configuring compute capabilities yet), thanks.
Change:
}; }; <ins> ImagePNGLibpng = buildPerlPackage { pname = "Image-PNG-Libpng"; version = "0.56"; src = fetchurl { url = "mirror://cpan/authors/id/B/BK/BKB/Image-PNG-Libpng-0.56.tar.gz"; sha256 = "1nf7qcql7b2w98i859f76q1vb4b2zd0k0ypjbsw7ngs2zzmvzyzs"; }; buildInputs = [ pkgs.libpng ]; meta = { description = "Perl interface to the C library "libpng""; license = with lib.licenses; [ artistic1 gpl1Plus ]; }; }; </ins> Imager = buildPerlPackage { pname = "Imager"; version = "1.012";

Discussion:
Describe the bug in seems to be broken, in a way (I think) related to how other things have broken in the past, e.g. . From looking at examples of fixes, e.g. , it looks like it might be necessary to patch the Perl source in , but I don't really understand what's going on so I don't know how. To Reproduce Steps to reproduce the behavior: to for this package so that the tests actually run, as in my PR tests fail Expected behavior I tried making a package that depends on , and got the following error at runtime: Maintainer information:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
Change:
<del> Origin: https://build.opensuse.org/package/view_file/X11:XOrg/tigervnc/u_xorg-server-1.20.7-ddxInputThreadInit.patch diff -u -p -r tigervnc-1.10.0.old/unix/xserver/hw/vnc/xvnc.c tigervnc-1.10.0/unix/xserver/hw/vnc/xvnc.c --- tigervnc-1.10.0.old/unix/xserver/hw/vnc/xvnc.c	2020-01-15 11:19:19.486731848 +0000 +++ tigervnc-1.10.0/unix/xserver/hw/vnc/xvnc.c	2020-01-15 11:37:33.275445409 +0000 @@ -295,6 +295,15 @@ void ddxBeforeReset(void) } #endif +#if INPUTTHREAD +/** This function is called in Xserver/os/inputthread.c when starting +    the input thread. */ +void +ddxInputThreadInit(void) +{ +} +#endif + void ddxUseMsg(void) { vncPrintBanner(); </del>

Discussion:
, CVSSv3=7.5 (nixos-20.03, nixos-20.09, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-20.09: ; nixos-unstable: . Cc
Fixed on master as , on 20.09 as .
Change:
systemd.services.strongswan = { description = "strongSwan IPSec Service"; wantedBy = [ "multi-user.target" ]; <del> path = with pkgs; [ kmod iproute iptables utillinux ]; # XXX Linux </del> <ins> path = with pkgs; [ config.system.sbin.modprobe iproute iptables utillinux ]; # XXX Linux </ins> wants = [ "keys.target" ]; after = [ "network.target" "keys.target" ]; environment = {

Discussion:
As described in , NixOS's module needs to use so it in the . I noticed errors in the journal saying that certain kernel modules weren't loaded. When I replaced with the errors disappeared.
Why did errors disappear?
I believe the errors disappeared because doesn't look in the right modules directory and does.
Change:
postPatch = '' substituteInPlace src/main.cpp --replace "/sbin/modprobe" "modprobe" substituteInPlace src/calibrate/calibrate.cpp --replace "/usr/bin/xset" "xset" <ins> substituteInPlace src/tuning/bluetooth.cpp --replace "/usr/bin/hcitool" "hcitool" </ins> ''; meta = with stdenv.lib; {

Discussion:
Describe the bug powertop executes hcitool in an FHS location: Metadata system: host os: multi-user?: sandbox: warning: unknown setting 'experimental-features' version: warning: unknown setting 'experimental-features' channels(root): warning: unknown setting 'experimental-features' channels(grahamc): warning: unknown setting 'experimental-features' nixpkgs: cc
Change:
dontPatchELF = true; meta = with lib; { <del> homepage = "http://ultrastardx.sourceforge.net/"; </del> <ins> homepage = "https://usdx.eu/"; </ins> description = "Free and open source karaoke game"; license = licenses.gpl2Plus; maintainers = with maintainers; [ Profpatsch ];

Discussion:
Package name: ultrastardx Latest released version: Current version on the unstable channel: 2021-04-03 Current version on the stable/release channel: 2021-04-03 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:
# Revert of the attempt: https://github.com/NixOS/nixpkgs/pull/147609 # More details: https://github.com/NixOS/nixpkgs/issues/74899#issuecomment-981142430 } else { <del> my %unitInfo = $newUnitInfo ? %{$newUnitInfo} : parseUnit($newUnitFile); </del> <ins> my %unitInfo = $newUnitInfo ? %{$newUnitInfo} : parse_unit($newUnitFile); </ins> if (parseSystemdBool(%unitInfo, "Service", "X-ReloadIfChanged", 0) and not $unitsToRestart->{$unit} and not $unitsToStop->{$unit}) { $unitsToReload->{$unit} = 1; recordUnit($reloadListFile, $unit);

Discussion:
Switching NIxOS configurations when using produces the following warning: Steps to reproduce the behavior: (current master) file in the directory with the following content: test fails and produces the warning should not produce warnings. It looks like currently can't handle service file names containing a . I tracked the first failing commit down to . The warning seems to not create any problems for me at the moment and all services are running.
Great… I'll take a look
Change:
<ins> import ./make-test-python.nix ({ pkgs, ... }: let testPort = 8108; in { name = "typesense"; meta.maintainers = with pkgs.lib.maintainers; [ oddlama ]; nodes.machine = { ... }: { services.typesense = { enable = true; apiKeyFile = pkgs.writeText "typesense-api-key" "dummy"; settings.server = { api-port = testPort; api-address = "0.0.0.0"; }; }; }; testScript = '' machine.wait_for_unit("typesense.service") machine.wait_for_open_port(${toString testPort}) assert machine.succeed("curl --fail http://localhost:${toString testPort}/health") == '{"ok":true}' ''; }) </ins>

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