jiebi/CodeConvo huggingface dataset:
Change:
gtksourceview = throw "xfce.gtksourceview has been removed, use gtksourceview instead"; # added 2022-05-24 dconf = throw "xfce.dconf has been removed, use dconf instead"; # added 2022-05-24 vte = throw "xfce.vte has been removed, use vte instead"; # added 2022-05-24 <del> xinitrc = xfce4-session.xinitrc; # added 2019-11-04 thunar-bare = thunar.override { thunarPlugins = []; };  # added 2019-11-04 }) </del> <ins> } </ins>

Discussion:
Trying to rebuild my system with current master () fails with the error: `error: has been removed, use dconf instead" This stems from PR from Obviously I don't use anywhere in my config. Running my deployment with yields: Looking at the source of just shows the correct usage of as far as I can tell. Steps to reproduce the behavior: nixpkgs locally to the given commit -rebuild with local nixpkgs Rebuild without issues. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Please run and paste the result.
I guess it is due to the removal of because on another machine I have the same issue with
A simpler way to test it to checkout current master and try to build which fails with the above error
Change:
]; postPatch = '' <del> for file in $(find src/ -type f ( -iname configure -o -iname *.sh  ) ); do </del> <ins> for file in $(find src/ -type f ( -iname configure -o -iname *.sh ) ); do </ins> substituteInPlace "$file" --replace "/bin/bash" "${stdenv.shell}" done '';

Discussion:
Describe the bug Latest MEGAsync app fails to start (Segmentation fault), probably because of . Not sure if it is NixOS related or just a MEGAsync bug. To Reproduce Steps to reproduce the behavior: it fault Expected behavior No crash Additional context Crash dump: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Maintainer information:
Yep I have this too. Actually the most recent commit version doesn't open at all, just dumps core - but the previous commit before that () does open and reopens on startup and everything fine, despite giving me the segmentation fault when I open it manually. <details<summaryCrashdump</summary
Same for me. Reported upstream: Bumping the version to does not help. It is still usable for me on 20.09 stable with this overlay:
Does anyone know how to specify an older version of cryptopp, as a stopgap until this is fixed upstream? I'm in desperate need of getting Megasync to work again. The overlay above isn't working for me on Unstable.
can't you just use michojel's overlay above, or an older version of the megasync package entirely? The latter is what I'm doing rn, just stick this in your : Which pins commit (which still uses megasync 4.3.5.0)
Looks like 4.4.0.0 addressed the issues. Works for me at least. See
Change:
easyabc = callPackage ../applications/audio/easyabc { }; <ins> easyaudiosync = qt6Packages.callPackage ../applications/audio/easyaudiosync {}; </ins> easycrypt = callPackage ../applications/science/logic/easycrypt { why3 = pkgs.why3.override { ideSupport = false; }; };

Discussion:
Project description From the project GitHub: Easy Audio Sync is an audio library syncing and conversion utility. The intended use is syncing an audio library with many lossless files to a mobile device with limited storage. The program's design is inspired by the utility. It supports folder-based source to destination syncing, with audio transcoding capability, and is GUI-based instead of CLI-based. Metadata homepage URL: source URL: license: Public Domain (Unlicense) platforms: Linux, Windows, and macOS Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
makeWrapper "${vim-customized}/bin/vim" "$out/bin/spacevim"  --add-flags "-u $out/SpaceVim/vimrc" --set SPACEVIMDIR "${spacevimdir}/"  --prefix PATH : ${lib.makeBinPath [ fzf git ripgrep]} <ins> runHook postInstall </ins> ''; meta = with lib; {

Discussion:
Describe the bug Each time spacevim is started, the "startify" onboarding prompt is displayed, followed by an error message. To Reproduce Steps to reproduce the behavior: prompt (or or ) fails to proceed ( ) over to confirm the bug persists Expected behavior The prompt should be shown at most once at first startup. Upstream behavior would be to show it once and save in the user's home directory, nixified behavior would be to never show this and get customized configuration information from the derivation. Screenshots If applicable, add screenshots to help explain your problem. ! ! Additional context Inspection reveals that the sets to point to the generated toml file instead of a directory containing it. One approach would be to synthesize that directory with a small derivation. AFAICT does not host anything else but I could be mistaken. That being said, it gets to () so this could be used to symlink plugins maybe...? The error message is Also last month. Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(louis): nixpkgs: Maintainer information:
Change:
install -Dt ${coreDir} ${coreFilename} makeWrapper ${retroarch}/bin/retroarch $out/bin/${mainProgram}  <del> --add-flags "-L ${coreDir}/${coreFilename} $@" </del> <ins> --add-flags "-L ${coreDir}/${coreFilename}" </ins> runHook postInstall '';

Discussion:
Seems like the wrapper in the installPhase is broken. When I build an individual core, like e.g. , the wrapper contains an additional argument that is always "installPhase". This is interpreted by retroarch as if you want to open a rom file called "installPhase", so you effectively are unable to supply a rom file via the arguments. Steps to reproduce the behavior: Results in retroarch trying to load a content file called "installPhase". Should run retroarch with core bsnes-mercury-accuracy loading the given rom file. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
]; propagatedBuildInputs = [ <del> aiohttp click </del> importlib-metadata <del> linkify-it-py </del> markdown-it-py <del> mdit-py-plugins mkdocs-exclude msgpack </del> rich <del> ] ++ lib.optionals (pythonOlder "3.11") [ </del> typing-extensions <del> ]; </del> <ins> ] ++ markdown-it-py.optional-dependencies.plugins ++ markdown-it-py.optional-dependencies.linkify; passthru.optional-dependencies = { syntax = [ tree-sitter # tree-sitter-languages ]; }; </ins> nativeCheckInputs = [ jinja2

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.37.1 Current version on the stable/release channel: 0.24.1 <!-- 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:
plugins = lib.mkOption { type = lib.types.listOf lib.types.package; <del> default = with pkgs.wayfirePlugins; [ wcm wf-shell ]; </del> <ins> default = with pkgs.wayfirePlugins; [ wcm wf-shell ]; </ins> defaultText = lib.literalExpression "with pkgs.wayfirePlugins; [ wcm wf-shell ]"; example = lib.literalExpression '' with pkgs.wayfirePlugins; [

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: wayfire with wayfire from the terminal (it doesn't need a display manager, and I couldn't get one to work but that's irrelevant here) Wayfire launches It gives the following error However, if I also enable sway: Then wayfire launches as intended. Clearly sway installs some dependencies (e.g. wlroots or something) that are required by wayfire that the package does not. It would be cleaner to allow only installing wayfire and not have to also install sway. <!-- 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]:
This seems not to be a bug in the wayfire package, but with the nixos wayfire module. It seems is the relevant maintainer for programs.wayfire. wayfire does not import wayland-, that sets up required services like graphics and xdg, but sway does. See for a quick fix
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
then pkgs.writeText "throttled.conf" cfg.extraConfig else "${pkgs.throttled}/etc/throttled.conf"; <ins> hardware.cpu.x86.msr.enable = true; </ins> # Kernel 5.9 spams warnings whenever userspace writes to CPU MSRs. # See https://github.com/erpalma/throttled/issues/215 hardware.cpu.x86.msr.settings.allow-writes =

Discussion:
works if started manually, but the daemon is failing to start on boot (NixOS unstable). Steps to reproduce the behavior: to your to unstable channel and run 's daemon should fail to initialize systemctl status throttled.service and check the error info Throttled's daemon should fail to initialize on boot with this 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.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
PR to
Change:
cp contrib/matrix_decrypt.py $out/bin/matrix_decrypt cp contrib/matrix_sso_helper.py $out/bin/matrix_sso_helper substituteInPlace $out/bin/matrix_upload  <del> --replace '/usr/bin/env -S python3' '${scriptPython}/bin/python' </del> <ins> --replace-fail '/usr/bin/env -S python3' '${scriptPython}/bin/python' </ins> substituteInPlace $out/bin/matrix_sso_helper  <del> --replace '/usr/bin/env -S python3' '${scriptPython}/bin/python' </del> <ins> --replace-fail '/usr/bin/env -S python3' '${scriptPython}/bin/python' </ins> substituteInPlace $out/bin/matrix_decrypt  <del> --replace '/usr/bin/env python3' '${scriptPython}/bin/python' </del> <ins> --replace-fail '/usr/bin/env python3' '${scriptPython}/bin/python' </ins> mkdir -p $out/${python.sitePackages} cp -r matrix $out/${python.sitePackages}/matrix

Discussion:
With the script, errors with: I'm not sure, but it could be because Steps to reproduce the behavior: to a channel, and try I expected it to properly upload the file. N/A This is how I setup in my dots. <!-- 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]:
fixed, I can't PR myself though
Change:
meta = with stdenv.lib; { description = "Print, scan and fax HP drivers for Linux"; homepage = https://developers.hp.com/hp-linux-imaging-and-printing; <ins> downloadPage = https://sourceforge.net/projects/hplip/files/hplip/; </ins> license = if withPlugin then licenses.unfree else with licenses; [ mit bsd2 gpl2Plus ];

Discussion:
Printing with a HP Color LaserJet printer fails due to a crash in the filter when using the driver "hpcups 3.19.1" With the "CUPS+Gutenprint v5.2.14" driver printing works. Try to print anything, a test page would do Please run and paste the results. oops.. let's try again:
I'm having the same problem, and made some observations: hplip 3.18.5 (used in release-18.09) works, even if compiled with pkgs from release-19.03 Here's a bug report with a proposed patch: is probably here: I didn't come around to test any of those patches thoug as I have only very limited access to my HP printer.
Change:
<del> { lib, buildPythonPackage, fetchdarcs, zope_interface, isPy3k }: </del> <ins> { lib, buildPythonPackage, fetchFromGitHub, zope_interface, isPy3k }: </ins> buildPythonPackage rec { pname = "python-application"; <del> version = "2.7.0"; </del> <ins> version = "2.8.0"; </ins> disabled = isPy3k; <del> src = fetchdarcs { url = "http://devel.ag-projects.com/repositories/${pname}"; </del> <ins> src = fetchFromGitHub { owner = "AGProjects"; repo = pname; </ins> rev = "release-${version}"; <del> sha256 = "1xpyk2v3naxkjhpyris58dxg1lxbraxgjd6f7w1sah5j0sk7psla"; </del> <ins> sha256 = "1xd2gbpmx2ghap9cnr1h6sxjai9419bdp3y9qp5lh67977m0qg30"; </ins> }; buildInputs = [ zope_interface ]; <ins> # No tests upstream to run doCheck = false; </ins> meta = with lib; { description = "Basic building blocks for python applications"; <del> homepage = https://github.com/AGProjects/python-application; </del> <ins> homepage = "https://github.com/AGProjects/python-application"; changelog = "https://github.com/AGProjects/python-application/blob/master/ChangeLog"; </ins> license = licenses.lgpl2Plus; }; }

Discussion:
This impacts any fixed-output derivation using that is not already in the binary cache. Packages relying on should be inspected to make sure that the canonical source location still actually uses in the first place; many of them have migrated to GitHub or similar places over the years.
It appears that is now fixed.
Change:
<del> { lib, stdenv, fetchFromGitHub, cmake, scdoc, util-linux, xorg }: stdenv.mkDerivation rec { pname = "ydotool"; version = "1.0.4"; src = fetchFromGitHub { owner = "ReimuNotMoe"; repo = "ydotool"; rev = "v${version}"; hash = "sha256-MtanR+cxz6FsbNBngqLE+ITKPZFHmWGsD1mBDk0OVng="; }; postPatch = '' substituteInPlace Daemon/ydotoold.c  --replace "/usr/bin/xinput" "${xorg.xinput}/bin/xinput" substituteInPlace Daemon/ydotool.service.in  --replace "/usr/bin/kill" "${util-linux}/bin/kill" ''; strictDeps = true; nativeBuildInputs = [ cmake scdoc ]; meta = with lib; { homepage = "https://github.com/ReimuNotMoe/ydotool"; description = "Generic Linux command-line automation tool"; license = licenses.agpl3Plus; maintainers = with maintainers; [ willibutz kraem ]; platforms = with platforms; linux; }; } </del>

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:
stdenv.mkDerivation rec { pname = "gnome-boxes"; <del> version = "44.2"; </del> <ins> version = "44.3"; </ins> src = fetchurl { url = "mirror://gnome/sources/${pname}/${lib.versions.major version}/${pname}-${version}.tar.xz"; <del> sha256 = "ndOJwUnQwPpXRW7DY9UaiCVflFVY+530KJTOeO+F34k="; </del> <ins> sha256 = "ZIpBuODIdfBOOnh+pnA2vJIehYo25jQ6Q9tyQu5z4XE="; </ins> }; patches = [

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 44.3 Current version on the stable/release channel: 44.2 <!-- 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:
''; enableParallelBuilding = true; <ins> env.NIX_CFLAGS_COMPILE = lib.optionalString stdenv.cc.isClang "-Wno-error=c++11-narrowing"; </ins> <del> setupHook = ./setup-hook.sh; </del> <ins> makeFlags = [ "DEST_BIN=${placeholder "out"}/bin" "DEST_SHARE=${placeholder "lib"}/lib/p7zip" "DEST_MAN=${placeholder "man"}/share/man" "DEST_SHARE_DOC=${placeholder "doc"}/share/doc/p7zip" ]; </ins> <del> env.NIX_CFLAGS_COMPILE = lib.optionalString stdenv.cc.isClang "-Wno-error=c++11-narrowing"; </del> <ins> outputs = [ "out" "lib" "doc" "man" ]; setupHook = ./setup-hook.sh; </ins> passthru.updateScript = ./update.sh; meta = with lib; { <del> homepage = "https://github.com/jinfeihan57/p7zip"; </del> <ins> homepage = "https://github.com/p7zip-project/p7zip"; </ins> description = "A new p7zip fork with additional codecs and improvements (forked from https://sourceforge.net/projects/p7zip/)"; license = with licenses; # p7zip code is largely lgpl2Plus

Discussion:
p7zip source is gone try to build without substituters cc
What commit are you having the issue from? it works for me at
Current master, that is sets to . There is no such tag at
Maybe the fork cleared the tags by force pushing?
Hmm, I wonder if all the changes got merged into with the fork then rebasing and force-pushing…
Yeah, looks like it. A bunch of jinfeihan57's commits are now in the commit history I'll change it to point back to p7zip-project's copy now
Change:
, buildPythonApplication , fetchPypi , gdb <del> , flask-socketio </del> <ins> , eventlet </ins> , flask-compress <ins> , flask-socketio </ins> , pygdbmi , pygments , }:

Discussion:
gdbgui fails to start (dump_stack) nixpkgs similar
Same issue for me :cry: Looks related to this cs01/gdbgui/issues/425
Change:
<ins> { lib, stdenv, buildGoModule, fetchFromGitHub, installShellFiles, }: buildGoModule rec { pname = "mangal"; version = "4.0.6"; src = fetchFromGitHub { owner = "metafates"; repo = pname; rev = "v${version}"; hash = "sha256-nbJdePlzZFM2ihbvFIMKyYZ9C0uKjU3TE5VLduLvtKE="; }; proxyVendor = true; vendorHash = null; ldflags = [ "-s" "-w" ]; nativeBuildInputs = [ installShellFiles ]; postInstall = lib.optionalString (stdenv.hostPlatform == stdenv.buildPlatform) '' # Mangal creates a config file in the folder ~/.config/mangal and fails if not possible export HOME=$(mktemp -d) installShellCompletion --cmd mangal  --bash <($out/bin/mangal completion bash)  --zsh <($out/bin/mangal completion zsh)  --fish <($out/bin/mangal completion fish) ''; doCheck = false; # test fail because of sandbox meta = with lib; { description = "CLI app written in Go which scrapes, downloads and packs manga into different formats"; homepage = "https://github.com/metafates/mangal"; license = licenses.mit; maintainers = [ maintainers.bertof ]; mainProgram = "mangal"; }; } </ins>

Discussion:
Steps to reproduce the behavior: mangal Add any other context about the problem here. <!-- 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:
, systemd, libgudev, libnl, libuuid, polkit, gnutls, ppp, dhcp, iptables , libgcrypt, dnsmasq, bluez5, readline , gobjectIntrospection, modemmanager, openresolv, libndp, newt, libsoup <del> , ethtool, gnused, coreutils, file, inetutils, kmod }: </del> <ins> , ethtool, iputils, gnused, coreutils, file, inetutils, kmod, jansson, libxslt , python3Packages, docbook_xsl, fetchpatch }: </ins> stdenv.mkDerivation rec { name    = "network-manager-${version}"; pname   = "NetworkManager"; <del> major   = "1.4"; version = "${major}.4"; </del> <ins> major   = "1.6"; version = "${major}.2"; </ins> src = fetchurl { url    = "mirror://gnome/sources/${pname}/${major}/${pname}-${version}.tar.xz"; <del> sha256 = "029k2f1arx1m5hppmr778i9yg34jj68nmji3i89qs06c33rpi4w2"; </del> <ins> sha256 = "1y96k82rav8if334jl500zc024d210c4pgprh94yqyz3rmanyaxj"; </ins> }; outputs = [ "out" "dev" ]; <ins> postPatch = '' patchShebangs ./tools ''; </ins> preConfigure = '' substituteInPlace configure --replace /usr/bin/uname ${coreutils}/bin/uname substituteInPlace configure --replace /usr/bin/file ${file}/bin/file <del> substituteInPlace src/devices/nm-device.c --replace /usr/bin/ping ${inetutils}/bin/ping </del> <ins> substituteInPlace src/devices/nm-device.c  --replace /usr/bin/ping ${inetutils}/bin/ping  --replace /usr/bin/ping6 ${inetutils}/bin/ping substituteInPlace src/devices/nm-arping-manager.c  --replace '("arping", NULL, NULL);' '("arping", "${inetutils}/bin/arping", NULL);' </ins> substituteInPlace src/NetworkManagerUtils.c --replace /sbin/modprobe ${kmod}/bin/modprobe substituteInPlace data/84-nm-drivers.rules  --replace /bin/sh ${stdenv.shell}

Discussion:
After nixos-rebuild switch, the network-manager service goes down and immediately segfaults every time it tries to come up again. journalctl for the segfault message or something, anyway, at this point I don't have working network anymore. nixos 17.09pre104870.
Specifically it segfaults because returns a non-zero exit status (saying "No for interface NetworkManager"); the segfault itself appears fixes in their HEAD. I haven't checked whether that makes it actually work, yet, but maybe we could arrange for it to have a in the meantime, whatever that means.
In which commit it was fixed?
Does this also happen in 17.03?
Happens with both the 17.03 tag and the 17.03 channel. Looks like cherry-picking the above commit as a patch for our network-manager lets it work correctly, btw.
also fixed in 17.03:
Change:
# https://github.com/NixOS/nixpkgs/issues/83885 patches = [ ./dependency-paths.patch ]; <del> inherit mlt mediainfo; </del> <ins> inherit mediainfo; </ins> ffmpeg = ffmpeg-full; <ins> mlt = mlt-full; </ins> postPatch = # Module Qt5::Concurrent must be included in `find_package` before it is used.

Discussion:
kdenlive can't encode to AV1 due to missing access to libaom-av1 Steps to reproduce the behavior: a new project. → Render → Ultra-High Definition (4K) WebM-AV1/Opus (libre) is available. instead it is disabled. ! This is strange because the package appears to try an use the : I also have ffmpeg installed in my PATH with libaom-av1 support: <details<summary<code% ffmpeg -help encoder=libaom-av1</code</summary</details The exact package I am using is which is available in system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Can reproduce.
Is this related to ?
I'm not sure, but it might be that the encoding libraries are actually not limited by the that uses, but by , which uses and not .
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Yes, this seems to be the issue.
Hi there :) I updated my channels and then rebuild, and still haven't gotten this fix. It still shows the same error, as in the original screenshot. I even libaom by hand, still the same.
Which channels have you updated, and to which versions?
11 and with nix-channel --update
Ah ok, as you see the issue was reported after release of 23.11, so it is fixed only in (and the next release).
I am on NixOS unstable () and Kdenlive 24.02.2 still reports "Unsupported video codec: libaom-av1".
Yes, it seems to have regressed for me as well.
I can't easily bisect the kdenlive derivation itself as it fails to load pipewire shared libraries probably due to skew between my base system and the built kdenlive. However I ran a bisection on with the override and found to be the culprit. At first glance this seems like it should be unrelated. <details<summarybisect script</summary</details
So before this change depends on both ffmpeg 4 and 6. After this change only 6 is in the dependency graph. Maybe 4 was somehow being used and that is needed for to work?
does have libaom-av1.

So presumably something isn't working with ffmpeg 6. Reverting to 4 for now is a possible solution but likely has a lot of downsides as well.
It is worth noting that ffmpeg 6 does have libaom support. So it is possibly an incompatibility between mlt and ffmpeg.
I do see that we are linking two versions of ffmpeg. -full and non-full. So possibly what is happening is that when the other version was 4 it wasn't getting used, so full was. But now that both are 6 the wrong one happens to get used.
This fixes the issue. Maybe the best solution is updating to use the same as . However this makes me think that this isn't the best solution in general.
Created to propagate the ffmpeg version through . I don't know if this fix is the most maintainable solution, but it solves this problem and doesn't harm maintainability.