jiebi/CodeConvo huggingface dataset:
Change:
libvorbis libxml2 movit <del> opencv4 </del> rtaudio rubberband sox

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.
Change:
, pkg-config , sphinx <ins> , lerc </ins> , libdeflate , libjpeg , xz

Discussion:
, and , but doesn't include LERC in the option list. Am I looking at the wrong thing, or is this dependency missing in the end result? The same seems to apply to WEBP. Related: Cc Steps to reproduce the behavior: the Python console (Ctrl-Alt-p) Alternatively, one level down: The strings and should appear in the option names. system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs:
, I just checked GDAL build messages, and it looks like GDAL is correctly built with LERC. If I try driver, I can see LERC in the list of available compressions:
HI do you see it compiled in for the Geotiff driver? That Victor needs it.
No, I don't see LERC compression available for GTiff driver, but I see it present for mrf (as I said above). I don't have any idea why.
Implemented in
Change:
with python3Packages; buildPythonApplication rec { pname = "kitty"; <del> version = "0.31.0"; </del> <ins> version = "0.32.0"; </ins> format = "other"; src = fetchFromGitHub { owner = "kovidgoyal"; repo = "kitty"; rev = "refs/tags/v${version}"; <del> hash = "sha256-VWWuC4T0pyTgqPNm0gNL1j3FShU5b8S157C1dKLon1g="; </del> <ins> hash = "sha256-untfXvBAn39C+s1BxVjXoLpPvnw7TM/uPFB+zZHH8w8="; </ins> }; goModules = (buildGoModule { pname = "kitty-go-modules"; inherit src version; <del> vendorHash = "sha256-OyZAWefSIiLQO0icxMIHWH3BKgNas8HIxLcse/qWKcU="; </del> <ins> vendorHash = "sha256-WRDP3Uyttz/kWm07tjv7wNguF/a1YgZqutbvFEOHuE0="; </ins> }).goModules; buildInputs = [

Discussion:
Package name: kitty Latest released version: 0.32.0 () <!-- Search your package here: --- Current version on the unstable channel: 0.31.0 Current version on the stable/release channel: 0.31.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<ins> library IEEE; use IEEE.STD_LOGIC_1164.all; use IEEE.NUMERIC_STD.ALL; use IEEE.STD_LOGIC_MISC.or_reduce; entity simple is port ( CLK, RESET : in std_ulogic; DATA_OUT : out std_ulogic_vector(7 downto 0); DONE_OUT : out std_ulogic ); end simple; architecture beh of simple is signal data : std_ulogic_vector(7 downto 0); signal done: std_ulogic; begin proc_ctr : process(CLK) begin if (CLK = '1' and CLK'event) then if (RESET = '1') then data <= "01011111"; done <= '0'; else case data is when "00100000" =>  data <= "01001110"; when "01001110" =>  data <= "01101001"; when "01101001" =>  data <= "01111000"; when "01111000" =>  data <= "01001111"; when "01001111" =>  data <= "01010011"; when others =>  data <= "00100000"; end case; done <= not or_reduce(data xor "01010011"); end if; end if; end process; DATA_OUT <= data; DONE_OUT <= done; end beh; </ins>

Discussion:
Describe the bug To Reproduce -env -i ghdl-llvm # or nix run ... -a Expected behavior ghdl compiles and runs the code Additional context uses LLVM as a backend to compile VHDL to a simulator executable for RTL simulation. It finally links its outputs using (via a call to gcc). The problem is, that in this linking step it also wants to link , which the linker can not find. However, in a everything works as intended. Even a and appending to NIX_LDPATH suffices. I tried various (combinations) of and friends and also , but never got this to work. I suspect that there is something in the setup hook of the nix-shell, but inspecting and comparing s didn't get me any further. Maybe someone could look into this or introduce me to the dark magic of and packaging compilers. (Looking at other compiler's .nix files also was a dead end for me.)
I marked this as stale due to inactivity. &rarr;
Change:
exporterConfig = { enable = true; url = "http://localhost"; <del> configFile = pkgs.writeText "json-exporter-conf.json" (builtins.toJSON [{ name = "json_test_metric"; path = "$.test"; }]); </del> <ins> configFile = pkgs.writeText "json-exporter-conf.json" (builtins.toJSON { metrics = [ { name = "json_test_metric"; path = "$.test"; } ]; }); </ins> }; metricProvider = { systemd.services.prometheus-json-exporter.after = [ "nginx.service" ];

Discussion:
current version: unstable-2017-10-06 desired version: 0.2.0 maintainers:
An option in the service definition to overwrite the package would be nice, too! :smile:
Why is this needed? -options are usually implemented if modifying the package in question with an overlay is a bad idea because it would mean that a lot of leaf-packages would require a rebuild as well. An example for that would be .
Ah, okay.
could you please update this package?
Oh sure, thank you for the ping :)
Change:
, lib ? pkgs.lib , elpaDevelPackages ? mkElpaDevelPackages { inherit pkgs lib; } self , elpaPackages ? mkElpaPackages { inherit pkgs lib; } self <ins> , nongnuDevelPackages ? mkNongnuDevelPackages { inherit pkgs lib; } self </ins> , nongnuPackages ? mkNongnuPackages { inherit pkgs lib; } self , melpaStablePackages ? melpaGeneric { inherit pkgs lib; } "stable" self , melpaPackages ? melpaGeneric { inherit pkgs lib; } "unstable" self

Discussion:
Project description NonGNU-devel ELPA Packages; i.e., development versions of the already packaged Metadata homepage URL: source URL: license: probably (guessed by looking at ) platforms: probably all (guessed by looking at ) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This feels like something that should only live in the emacs-overlay, not in Nixpkgs.
Consider that the other two supported ELPAs have both their stable/unstable versions supported in nixpkgs: elpa/elpaDevel; melpaStable/melpa (see to quickly fact-check). What's the reason for this feeling; why should nongnu be an exception?
I think the same about the others.
Change:
stdenv.mkDerivation rec { pname = "pyside2"; <del> version = "5.12.3"; </del> <ins> version = "5.12.6"; </ins> src = fetchurl { url = "https://download.qt.io/official_releases/QtForPython/pyside2/PySide2-${version}-src/pyside-setup-everywhere-src-${version}.tar.xz"; <del> sha256 = "0hk89jm8pa0q6kifask5rrffa3bvx02dg2f97ibv7wds9dysnyjg"; </del> <ins> sha256 = "1n45l6xxyxs6cfp2l4rp8qs1c2fyfwyrdxa4qcpwfsqsi51rydsk"; </ins> }; patches = [

Discussion:
Describe the bug , a package which requires PySide2, fails to install, either system-wide, nix-env local, nix-env global, or with home-manager. To Reproduce Results Running the above command: Expected behavior Syncplay installs correctly without error. Notify maintainers pyside2: syncplay: Metadata Please run and paste the result.
This not only affects syncplay. Many other dependencies are broken as well. Freecad for instance does not build either.
looks like updating pyside2 to 5.12.6 fixed this issue on my fork:
Your fix looks good to me. Could you PR it?
done,
Change:
] ); in <del> mkDerivation rec { </del> <ins> stdenv.mkDerivation (finalAttrs: { </ins> pname = "scribus"; <del> version = "1.5.8"; </del> <ins> version = "1.6.0"; </ins> src = fetchurl { <del> url = "mirror://sourceforge/${pname}/${pname}-devel/${pname}-${version}.tar.xz"; hash = "sha256-R4Fuj89tBXiP8WqkSZ+X/yJDHHd6d4kUmwqItFHha3Q="; </del> <ins> url = "mirror://sourceforge/scribus/scribus-devel/scribus-${finalAttrs.version}.tar.xz"; hash = "sha256-lLl0kOzhcoaNxPBMeqLulQtBtfL/QoXfN9YV8ETQOOU="; </ins> }; <del> patches = [ # For Poppler 22.02 (fetchpatch { url = "https://github.com/scribusproject/scribus/commit/85c0dff3422fa3c26fbc2e8d8561f597ec24bd92.patch"; sha256 = "YR0ii09EVU8Qazz6b8KAIWsUMTwPIwO8JuQPymAWKdw="; }) (fetchpatch { url = "https://github.com/scribusproject/scribus/commit/f75c1613db67f4067643d0218a2db3235e42ec9f.patch"; sha256 = "vJU8HsKHE3oXlhcXQk9uCYINPYVPF5IGmrWYFQ6Py5c="; }) # For Poppler 22.03 (fetchpatch { url = "https://github.com/scribusproject/scribus/commit/f19410ac3b27e33dd62105746784e61e85b90a1d.patch"; sha256 = "JHdgntYcioYatPeqpmym3c9dORahj0CinGOzbGtA4ds="; }) # For Poppler 22.04 (fetchpatch { url = "https://github.com/scribusproject/scribus/commit/f2237b8f0b5cf7690e864a22ef7a63a6d769fa36.patch"; sha256 = "FXpLoX/a2Jy3GcfzrUUyVUfEAp5wAy2UfzfVA5lhwJw="; }) # For Poppler 22.09 (fetchpatch { url = "https://github.com/archlinux/svntogit-community/raw/ea402a588c65d11973b148cf203b3463213431cf/trunk/scribus-1.5.8-poppler-22.09.0.patch"; sha256 = "IRQ6rSzH6ZWln6F13Ayk8k7ADj8l3lIJlGm/zjEURQM="; }) ]; </del> nativeBuildInputs = [ cmake pkg-config <ins> qt5.wrapQtAppsHook </ins> ]; buildInputs = [

Discussion:
Package name: scribus Latest released version: 1.6.0 Current version on the unstable channel: 1.5.8 Current version on the stable/release channel: 1.4.8 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The version on the stable channel is also 1.5.8, 1.4 existed only on the old NixOS 23.05 release and got removed since.
Change:
<ins> diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt index e7befae..8689f13 100644 --- a/src/CMakeLists.txt +++ b/src/CMakeLists.txt @@ -43,11 +43,14 @@ configure_file("${PROJECT_SOURCE_DIR}/translations/languages.hpp.in" "${PROJECT_ # Make lupdate target for Qt 6 if (${QT_VERSION} VERSION_GREATER_EQUAL "6") -  qt_add_lupdate(${EXECUTABLE_NAME} +  qt_add_lupdate( TS_FILES ${TS_FILES} "${PROJECT_SOURCE_DIR}/translations/source.ts" +    SOURCE_TARGETS ${EXECUTABLE_NAME} ) endif () -qt_add_translation(QM_FILES "${TS_FILES}") +qt_add_translations( +  ${EXECUTABLE_NAME} +) foreach (FILE ${QM_FILES}) get_filename_component(BASENAME ${FILE} NAME) string(APPEND TRANSLATION_FILES "    <file>${BASENAME}</file>n") </ins>

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:
libcec_platform = callPackage ../development/libraries/libcec/platform.nix { }; <del> libcef = callPackage ../development/libraries/libcef { inherit (gnome2) GConf; }; </del> <ins> libcef = callPackage ../development/libraries/libcef {}; </ins> libcello = callPackage ../development/libraries/libcello {};

Discussion:
(Upstream bug, autoclosed due to NixOS not being supported: ) I get the following segv on start: This behavior was not present pre-v27.
Not sure what the issue is but removing a scene that had a browser embed in it stopped the crash. (I tried it because libcef is chrome).
Okay, I can confirm that adding a Browser scene (then quitting OBS, then opening it again) will cause a segfault. Actually adding the scene does not cause any problems, although I was unable to get it to render anything.
This is probably due to our CEF version being out of date. Currently building with a newer copy…
It was indeed our CEF version being out of date. It's practically ancient, from 2019-07-27. Building against latest gives me an OBS that doesn't crash on startup & shows stuff in the Browser source. See for the fix.
Change:
homepage = "https://peazip.github.io"; platforms = platforms.linux; maintainers = with maintainers; [ annaaurora ]; <ins> mainProgram = "peazip"; </ins> }; }

Discussion:
Steps to reproduce the behavior: <!-- 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:
#  supportedGpuTargets: List String # } <del> { blas </del> <ins> { autoPatchelfHook , blas </ins> , cmake , cudaPackages , cudaSupport ? config.cudaSupport

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . python3Packages.torchvision maintainers cc: magma maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags:
This is also breaking atm
This shows that fortran name mangling is using the underscore ``. (See ) Magma should have the flag "-DADD" set during compilation to fix this
And, in fact, clmagma already sets :
Both of the following overlays fixed the problem: Specify the fortran name mangling convention To explain this, in , we see that if USEFORTRAN=off then the FORTRANCONVENTIONS flag is set and also copied to CFLAGS and CXXFLAGS. FORTRANCONVENTIONS is copied outside of this block into the NVCCFLAGS, and DEVCCFLAGS (which can't otherwise be set), so all three flags are necessary if we use the default of USE_FORTRAN=on. Disable fortran in magma
Nice! Would you be interested in turning that into a PR? It'd be great to fix on master!
Change:
stdenv.mkDerivation rec { pname = "planify"; <del> version = "4.1"; </del> <ins> version = "4.1.1"; </ins> src = fetchFromGitHub { owner = "alainm23"; repo = "planify"; <del> rev = version; sha256 = "sha256-H8TPuqKRwbcB+2NTC5ZIK7y6uiYbTT4svtx21FbTzME="; </del> <ins> # The commit is named as "Release 4.1.1", published to Flathub, but not tags # https://github.com/flathub/io.github.alainm23.planify/commit/2a353ccfcf3379add6778d569f49da37f40accfa # https://github.com/alainm23/planify/issues/1002 rev = "adf3629bcacfc9978f6dde5b87eff0278533ab3e"; hash = "sha256-xqklvSYmqBQ+IQ3lRjMbV4W4vD/rLCln7rBVCbYiBGo="; </ins> }; nativeBuildInputs = [

Discussion:
Package name: planify Latest released version: 4.1.1 <!-- Search your package here: --- Current version on the unstable channel: 4.1 Current version on the stable/release channel: none <!-- 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. Trivial update, fixes an issue where some modifier-less hotkeys were active even when editing a text field (namely that typing 'a' in a task would pop up a new blank task). Alas while there is an obvious release commit, there is no github release or tag.
Change:
, qtlocation, qtquickcontrols2, qtwebchannel , qtwebengine, qtx11extras, qtxmlpatterns , monero, unbound, readline, boost, libunwind <del> , pcsclite, zeromq, cppzmq, pkgconfig </del> <ins> , libsodium, pcsclite, zeromq, cppzmq, pkgconfig </ins> }: with stdenv.lib; stdenv.mkDerivation rec { name = "monero-gui-${version}"; <del> version = "0.12.3.0"; </del> <ins> version = "0.13.0.2"; </ins> src = fetchFromGitHub { owner  = "monero-project"; repo   = "monero-gui"; rev    = "v${version}"; <del> sha256 = "1ry0455cgirkc6n46qnlv5p49axjllil78xmx6469nbp3a2r3z7i"; </del> <ins> sha256 = "02419rqi3zfy6yjyw3b3gvkbxh2ypdfpijiiklc7lyblb9nnjr68"; </ins> }; nativeBuildInputs = [ qmake pkgconfig ];

Discussion:
Monero is hardforking and changing the proof of work. xmr-stak must be upgraded to v2.5.0 before the 18th of Oct (Thu), or it will stop working Thanks
Thanks & .. When can we expect this to land ? Thanks
It should be ready to merge already.
Change:
<del> { pkgs , buildPythonPackage , fetchPypi , python , azure-common , futures , python-dateutil , requests , isPy3k }: buildPythonPackage rec { version = "0.20.3"; pname = "azure-storage"; src = fetchPypi { inherit pname version; extension = "zip"; sha256 = "06bmw6k2000kln5jwk5r9bgcalqbyvqirmdh9gq4s6nb4fv3c0jb"; }; propagatedBuildInputs = [ azure-common python-dateutil requests ] ++ pkgs.lib.optionals (!isPy3k) [ futures ]; postInstall = '' echo "__import__('pkg_resources').declare_namespace(__name__)" >> "$out/lib/${python.libPrefix}"/site-packages/azure/__init__.py ''; meta = with pkgs.lib; { description = "Microsoft Azure SDK for Python"; homepage = "https://azure.microsoft.com/en-us/develop/python/"; license = licenses.asl20; maintainers = with maintainers; [ olcai ]; }; } </del>

Discussion:
After in nixops, we can remove the locally pinned version in nixpkgs.
Not yet, I would like to keep those for building nixops v1.6.1 for any users of the Azure backend.
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:
source-han-serif-korean = source-han-serif; source-han-serif-simplified-chinese = source-han-serif; source-han-serif-traditional-chinese = source-han-serif; <del> source-sans-pro = source-sans; # Added 2021-10-20 source-serif-pro = source-serif; # Added 2021-10-20 </del> spaceOrbit = throw "'spaceOrbit' has been renamed to/replaced by 'space-orbit'"; # Converted to throw 2022-02-22 spectral = neochat; # Added 2020-12-27

Discussion:
The font as installed by the package, is now called . This breaks all references to the font in documents, but also in web pages, etc. The font Open this webpage: The logo uses the Source Sans Pro font and it should look correct when the package is installed. Instead, it shows an alternative font with serif. The font should be called and not , keeping all references. If this was not desirable (because the font is just too different) then a package should be provided to install the old version with the old name. Please run and paste the result.
The upstream name change was intentional (adobe-fonts/source-serif).
Thank you andersk that explains a lot! I guess then it makes sense to also install the older version? Edit: or provide it as a separate package.
We should be able to deal with this through fontconfig.
If I understand correctly, it's not only the name that has been changed, but the renamed font has also different metrics. This means that if we just configure fontconfig to replace "Source Sans Pro" with "Source Sans 3", the layout of existing documents might change. So I think, it would make sense to either reintroduce Pro fonts as a separate package, or include the older (Pro) version together with the new one (which is what ). If is interested, I can turn , which does the former, to a PR.
I agree. Either of these two solutions would be satisfying to me.
I wasn't aware of the metrics changes. I think adding the older version back as a new package makes perfect sense, thank you!
Change:
{ lib , buildPythonPackage <del> , dnspython </del> , deprecat <ins> , dnspython </ins> , fetchFromGitHub , loguru , passlib , poetry-core , pytestCheckHook , pythonOlder <ins> , pythonRelaxDepsHook </ins> , toml }:

Discussion:
Package name: loguru Latest released version: 0.7.0 <!-- Search your package here: --- Current version on the unstable channel: 2023-01-20 Current version on the stable/release channel: 2023-01-20 <!-- 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:
url = "https://github.com/WebAssembly/binaryen/commit/93b8849d9f98ef7ed812938ff0b3219819c2be77.patch"; sha256 = "sha256-Duan/B9A+occ5Lj2SbRX793xIfhzHbdYPI5PyTNCZoU="; }) <ins> # https://github.com/WebAssembly/binaryen/pull/4913 (fetchpatch { url = "https://github.com/WebAssembly/binaryen/commit/b70fe755aa4c90727edfd91dc0a9a51febf0239d.patch"; sha256 = "sha256-kjPLbdiMVQepSJ7J1gK6dRSMI/2SsH39k7W5AMOIrkM="; }) </ins> ]; nativeBuildInputs = [ cmake python3 ];

Discussion:
Emscripten 3.1.17 is now the default in nixpkgs but it has been failing to build for a few days and isn't in the binary cache (, ). The failure is actually in , which is a build input for . The same build failure happens to me locally when the build is triggered by a cache miss (e.g. with ). It looks to me with a shallow search on the internet that maybe Node 18 is the problem, and should depend on explicitly (or something). I don't know how to do that, so I'm opening an issue. If I figure it out, maybe I'll send a PR.
This seems to work locally (as ):