jiebi/CodeConvo huggingface dataset:
Change:
MOUSE_PS2_VMMOUSE  = yes; MTRR_SANITIZER     = yes; NET_FC             = yes; # Fibre Channel driver support <ins> # Needed for touchpads to work on some AMD laptops PINCTRL_AMD        = whenAtLeast "5.19" yes; </ins> # GPIO on Intel Bay Trail, for some Chromebook internal eMMC disks PINCTRL_BAYTRAIL   = yes; # GPIO for Braswell and Cherryview devices

Discussion:
Putting this out here in case anybody else is seeing this. On am Acer Swift SF314-43, the touchpad goes missing with kernel 5.19. Works again with kernel 5.18 and no other changes. Steps to reproduce the behavior: to kernel 5.19 that it's broken With kernel 5.18: With kernel 5.19:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This happended to me as well, on a Tuxedo Aura Gen 1 with an ElanTech clickpad and NixOS 22.05. Comparing the output of between kernel 5.18 and 5.19 I found three modules, which haven't been loaded on 5.19: , and . ~I them to , ran and after rebooting the touchpad is working again.~ Adding them to in my NixOS configuration did not help. Edit: Was on the wrong kernel version, when testing if manually adding the modules would help.
Ah, on 5.19: Kernel rebuilding time. Haven't done that in a while...
So that did it. I didn't need to specify the list of modules, only add the kernel option.
That fixed it on my Tuxedo as well.
Change:
, python3 , fetchFromGitHub , wrapQtAppsHook <ins> , packageOverrides ? self: super: {} </ins> }: let

Discussion:
Steps to reproduce the behavior: (as of ) <details<summaryBuild Log</summary<preerror: builder for '/nix/store/8r1frbwzxwncagff57r7zz86zl2nsxbm-python3.10-jsonschema-' failed with exit code 1; last 10 log lines: For full logs, run 'nix log /nix/store/8r1frbwzxwncagff57r7zz86zl2nsxbm-python3.10-jsonschema-'. error: 1 dependencies of derivation '/nix/store/2413pkb4n4z1bj0rywpcfbi8s1yisvkg-python3.10-bravado-core-' failed to build error: 1 dependencies of derivation '/nix/store/x9h491ipp10gpp771jzfr3qyn3y6pbf9-powerdns-admin-' failed to build </pre</detailsLooks like json schema got updated to 4.13 which requires adding a patch. When , we're not patching (please excuse the pun), so it tries to apply to new patch against 3.2.0 which, of course, fails. Seems like we probably just need to override the to remove the offending patch? <!-- 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.
, and are also broken in similar fashion.
I'll take a look later today.
I opened .
Change:
nativeBuildInputs = [ makeWrapper installShellFiles ]; buildInputs = [ bash ]; installPhase = '' <del> installManPage contrib/grimshot.1 </del> <ins> installManPage grimshot.1 </ins> <del> install -Dm 0755 contrib/grimshot $out/bin/grimshot </del> <ins> install -Dm 0755 grimshot $out/bin/grimshot </ins> wrapProgram $out/bin/grimshot --set PATH  "${lib.makeBinPath [ sway-unwrapped

Discussion:
User-contributed scripts are being moved over to this repository: I just adopted the use of and couldn't build grimshot: I could build my nixosconfiguration before when I was using . I guess nixpkgs-wayland is slightly ahead, and we'll have this problem when nixos-unstable updates sway.
i don't think github notifies issue subscribers of linked PRs so: i've opened to fix this
Yes, that's a nixpkgs-wayland problem/regression/bug. Nixpkgs is still fine. We just have to update the package before the next Sway update but it might indeed be best to do this in advance.
Change:
<ins> { lib, buildKodiAddon, fetchFromGitHub, addonUpdateScript }: buildKodiAddon rec { pname = "infotagger"; namespace = "script.module.infotagger"; version = "0.0.7"; src = fetchFromGitHub { owner = "jurialmunkey"; repo = namespace; rev = "v${version}"; hash = "sha256-Us7ud0QORGn+ALB4uyISekp0kUYY8nN8uFNg8MlxEB0="; }; passthru = { # Unusual Python path. pythonPath = "resources/modules"; updateScript = addonUpdateScript { attrPath = "kodi.packages.infotagger"; }; }; meta = with lib; { homepage = "https://github.com/jurialmunkey/script.module.infotagger"; description = "Wrapper for new Nexus InfoTagVideo ListItem methods to maintain backwards compatibility"; license = licenses.gpl3Plus; maintainers = teams.kodi.members; }; } </ins>

Discussion:
When using Kodi with the YouTube plugin , I get the following error: Steps to reproduce the behavior: The YouTube plugin used to work perfectly. shows that the dependency was but that the dependency is an old one. The wrapper is here:
Thanks for catching this. Looks like a pretty straight forward addon to package. Is this something you'd be interested in tackling
I can, if I find the time! One thing I do not understand is that the dependency is an old one. I could see that the YouTube plugin is failing because the new dependency is missing, but it seems to fail because of (which is also not provided by Nixpkgs, but why didn't it fail before?).
I have tested this and it works for me. Thanks
Change:
Packages inside nixpkgs are written by hand. However many tools exist in community to help save time. No tool is preferred at the moment. <del> - [pypi2nix](https://github.com/nix-community/pypi2nix): Generate Nix expressions for your Python project. Note that [sharing derivations from pypi2nix with nixpkgs is possible but not encouraged](https://github.com/nix-community/pypi2nix/issues/222#issuecomment-443497376). </del> - [nixpkgs-pytools](https://github.com/nix-community/nixpkgs-pytools) - [poetry2nix](https://github.com/nix-community/poetry2nix)

Discussion:
Steps to reproduce the behavior: Command should execute without an error None? Please run and paste the result.
Change:
version = "2.2.14"; sha256 = "1b2x3q1ach44qg07sh8wr7d8a10n36w5522drd3p35djbiwa3d9q"; generation = "2_2"; <ins> extraMeta.knownVulnerabilities = [ # Fixed in 3.* but 2.* hasn't been released since "CVE-2020-17516" ]; </ins> })

Discussion:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
See also , ,
Change:
meta = with lib; { description = "Practical and minimal image viewer"; homepage = "https://interversehq.com/qview/"; <del> license = licenses.gpl3; </del> <ins> license = licenses.gpl3Plus; </ins> maintainers = with maintainers; [ acowley ]; platforms = platforms.all; };

Discussion:
qview support a list of images format, including webp: However, if you try opening a webp image in nixos, you get "unsupported image format". This format is listed as "optional", so it might just be a matter of activating it somehow. Steps to reproduce the behavior: qview with nex "qview " error message Image should be opened. Not needed Add any other context about the problem here.
I wonder if this is something we’d need to add in the nix Qt build itself.
Change:
buildPythonPackage rec { pname = "python-openems"; <del> version = "unstable-2020-02-15"; </del> <ins> version = openems.version; </ins> <del> src = fetchFromGitHub { owner = "thliebig"; repo = "openEMS"; rev = "ba793ac84e2f78f254d6d690bb5a4c626326bbfd"; sha256 = "1dca6b6ccy771irxzsj075zvpa3dlzv4mjb8xyg9d889dqlgyl45"; }; </del> <ins> src = openems.src; </ins> sourceRoot = "${src.name}/python";

Discussion:
Package name: OpenEMS Latest released version: 0.0.36 <!-- Search your package here: --- Current version on the unstable channel: 2020-02-15 Current version on the stable/release channel: 2020-02-15 <!-- 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:
platforms = []; source = { remotes = ["https://rubygems.org"]; <del> sha256 = "08ximcyfjy94pm1rhcx04ny1vx2sk0x4y185gzn86yfsbzwkng53"; </del> <ins> sha256 = "05i8518ay14kjbma550mv0jm8a6di8yp5phzrd8rj44z9qnrlrp0"; </ins> type = "gem"; }; <del> version = "3.2.5"; </del> <ins> version = "3.2.6"; </ins> }; ruby-dbus = { dependencies = ["rexml"];

Discussion:
The fusuma program in the package of the same name crashes when trying to run it. The breaking change causing this issue was made somewhere in the last 56 days: That's when I last updated this particular host, after which everything was still working fine. Steps to reproduce the behavior: "fusuma" package to run fusuma I expected fusuma to start running and be available for use. N/A Instead of displaying the expected behavior, the program crashes: In addition, if I clone the repo, then open a and run the cloned project in that nix-shell, that runs successfully unmodified on the same host. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks especially for the celerity of the fix!
Is there supposed to be a delay between this merge and availability updating? I can clearly see this PR is merged, but when I update my system the new version isn't in there.
Yes, see
One month later, I don't see the updated package. How long can this take ?
The update is already on master, but I don't think it's been backported yet. Are you on NixOS 23.11 instead of unstable?
Yes.
Backported in , should take a few days to land.
Many thanks for the commit !
Change:
<ins> diff --git a/Tools/CMake/Libraries.cmake b/Tools/CMake/Libraries.cmake index cc4681a..f484013 100644 --- a/Tools/CMake/Libraries.cmake +++ b/Tools/CMake/Libraries.cmake @@ -67,7 +67,7 @@ if((NOT LibArchive_FOUND) AND (NOT WIN32)) endif() endif() -set(Boost_USE_STATIC_LIBS ON) +add_definitions(-DBOOST_LOG_DYN_LINK) find_package( Boost 1.78 REQUIRED COMPONENTS filesystem @@ -178,10 +178,10 @@ if(LINUX) set(LIBREADSTAT_INCLUDE_DIRS /app/include) set(LIBREADSTAT_LIBRARY_DIRS /app/lib) else() -    set(LIBREADSTAT_INCLUDE_DIRS /usr/local/include /usr/include) +    set(LIBREADSTAT_INCLUDE_DIRS @readstat@/include /usr/include) # The last two library paths handle the two most common multiarch cases. # Other multiarch-compliant paths may come up but should be rare. -    set(LIBREADSTAT_LIBRARY_DIRS /usr/local/lib /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/aarch64-linux-gnu) +    set(LIBREADSTAT_LIBRARY_DIRS @readstat@/lib /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/aarch64-linux-gnu) endif() message(CHECK_START "Looking for libreadstat.so") diff --git a/Tools/CMake/Programs.cmake b/Tools/CMake/Programs.cmake index dbd089d..ef6857a 100644 --- a/Tools/CMake/Programs.cmake +++ b/Tools/CMake/Programs.cmake @@ -39,6 +39,7 @@ endif() # ------ Linux Tools/Programs +#[[ if(LINUX) message(CHECK_START "Looking for 'gfortran'") @@ -81,6 +82,7 @@ if(LINUX) endif() endif() +]]# # ---------------------- </ins>

Discussion:
Project description <!-- JASP aims to be a complete statistical package for both Bayesian and Frequentist statistical methods, that is easy to use and familiar to users of SPSS --Metadata homepage URL:https://jasp- source license: agpl3 platforms: window, linux, darwin
PR:
thank you but I had a error when building source
Yes, I get the same error. Unfortunately I could not figure out where the file is supposed to come from. That's why the PR is in draft mode (waiting for someone who knows how to fix the build).
hash = "sha256-h/jFzR5XE+dmETENaBPQ0bCTLJYanpvtJTsMnAwoi9g="; #sha256-h/jFzR5XE+dmETENaBPQ0bCTLJYanpvtJTsMnAwoi9g= sha256-1m0URudMF50pnR7xYuu/d5817ouybaNLTG/h2d1J7rY= fetchSubmodules = true; After changed above, I got error
Change:
in stdenv // { mkDerivation = { nativeBuildInputs ? [] <del> , selfNativeBuildInput ? args.crossAttrs.selfNativeBuildInput or false </del> , ... } @ args: <del> let # *BuildInputs exists temporarily as another name for # *HostInputs. # The base stdenv already knows that nativeBuildInputs and # buildInputs should be built with the usual gcc-wrapper # And the same for propagatedBuildInputs. nativeDrv = stdenv.mkDerivation args; in </del> stdenv.mkDerivation (args // { nativeBuildInputs = nativeBuildInputs <del> ++ stdenv.lib.optional selfNativeBuildInput nativeDrv </del> # without proper `file` command, libtool sometimes fails # to recognize 64-bit DLLs ++ stdenv.lib.optional (hostPlatform.config == "x86_64-w64-mingw32") pkgs.file

Discussion:
I noticed in the derivation, but do not see it defined anywhere.
Pinging What is the status of this attribute? Should it be used? What purpose does it serve? It seems to me like it would be simpler if we just explicitly to .
It is defined in the cross adapter in . Yeah, I want to get rid of , like (). It's pointless.
Will be closed automatically when staging is merged.
Change:
"~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/)".extraConfig = '' return 404; ''; <del> "~ ^/(?:.|autotest|occ|issue|indie|db_|console)".extraConfig = '' </del> <ins> "~ ^/(?:.(?!well-known)|autotest|occ|issue|indie|db_|console)".extraConfig = '' </ins> return 404; ''; "~ ^/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|updater/.+|oc[ms]-provider/.+|.+/richdocumentscode/proxy).php(?:$|/)" = {

Discussion:
Describe the bug I have a nextcloud installation in the vhost root: which would redirect to for the NextCloud login. Also I enabled in the nginx settings that a SSL certifcate with the acme service should be used. However, no certificate can be issued - acme claims that it gets 404. To Reproduce Steps to reproduce the behavior: nextcloud and acme configuration to your configuration nix. E.g. will generate a nginx config that contains: first part of that configuration snippet also matches for the folder and hence a 404 is returned. Expected behavior Having SSL cert issued by Let's Encrypt. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Opened with a fix.
Thanks for the quick fix :)
can you confirm that this fixes the issue for you? If so, I'd merge+backport. Just in case you didn't know - you can do
I did manually edit the nginx config in the nix store: Then run the acme command as standalone: So it works.
Change:
paths = [ cudaPackages.cudatoolkit cudaPackages.cuda_cudart <ins> cudaPackages.cuda_cudart.static </ins> ]; postBuild = '' rm "$out/lib64"

Discussion:
Steps to reproduce the behavior: 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]:
Blender with cuda is also broekn maybe it is linked ? I enabled cuda with this <details<summarybuild log</summary</details
I've tried your config change with no luck unfortunately I get the same error, but I can confirm that it was working as of yesterday nix-info:
Here are my modifications and I just don't have cuda detected in blender using this
I created pr , which seems to get ollama to compile correctly. However, I don't know if it works correctly and uses cuda at runtime. Any testing of my branch with enabled is much appreciated!
Change:
<del> { lib, stdenv, fetchurl, cmake, imagemagick }: </del> <ins> { lib, stdenv, fetchurl, cmake, imagemagick, testers }: </ins> <del> stdenv.mkDerivation { </del> <ins> stdenv.mkDerivation (finalAttrs: { </ins> pname = "cuneiform"; version = "1.1.0";

Discussion:
Running cuneiform results in a shared-library load error Steps to reproduce the behavior: 23.11 or nixpkgs unstable Will get error: The program will run
PR should fix this. can you verify that the change works for you? or
Change:
nativeBuildInputs = [ cmake ]; <del> propagatedBuildInputs = [ openssl ]; # s2n-config has find_dependency(LibCrypto). </del> <ins> outputs = [ "out" "dev"]; buildInputs = [ openssl ]; # s2n-config has find_dependency(LibCrypto). </ins> cmakeFlags = [ "-DBUILD_SHARED_LIBS=ON" <ins> "-DCMAKE_SKIP_BUILD_RPATH=OFF" </ins> ]; <ins> propagatedBuildInputs = [ openssl ]; # s2n-config has find_dependency(LibCrypto). postInstall = '' substituteInPlace $out/lib/s2n/cmake/shared/s2n-targets.cmake  --replace 'INTERFACE_INCLUDE_DIRECTORIES "''${_IMPORT_PREFIX}/include"' 'INTERFACE_INCLUDE_DIRECTORIES ""' ''; </ins> meta = with lib; { description = "C99 implementation of the TLS/SSL protocols"; homepage = "https://github.com/aws/s2n-tls";

Discussion:
Describe the bug depends on which bloats the closure size of Nix among other things. To Reproduce Expected behavior Not see -bin in the dependencies of openssl. Notify maintainers I believe this was introduce in Metadata Please run and paste the result. Maintainer information:
That's by design.
This should fix it (untested)
Hm, yeah, maybe dev depending on bin is intended, but somewhere along the line something must be wrong - I don't think it's intended for Nix to depend on
I don't think it is intended. It's just the default which was not changed here. In fact, when I inspected I did not find any other reference to than in . So I think it should be safe to remove from like in the above patch. Unfortunately, properly testing this would trigger a rebuild of pretty much all of nixpkgs.
Change:
inherit (callPackages ../servers/unifi { }) unifiLTS unifi5 <del> unifi6; </del> <ins> unifi6 unifi7; </ins> unifi = unifi6; unifi-video = callPackage ../servers/unifi-video { };

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the 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: unifi, unifi7 <!-- The current version can be found easily with the same process than 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: 6.5.55 desired version: 7.0.20 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers:
Thanks for reporting, I'll prepare the patch in a moment
Change:
, libtirpc , nfs-utils , gawk, gnugrep, gnused, systemd <del> , smartmontools, sysstat, sudo , pkg-config </del> <ins> , smartmontools, enableMail ? false , sysstat, sudo, pkg-config </ins> # Kernel dependencies , kernel ? null

Discussion:
Describe the bug On a ZFS-enabled 20.03 system: IMHO zed does not need the ability to send email by default. Also mariadb-connector should have a separate -dev output so that its doesn't end up in the system closure.
cc
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
Seems still important: And: And:
Adjusted to milestone 21.03. BTW, If someone wants to backport the fix it shouldn't cause any issues.
Took a stab at this in
Change:
https://github.com/coc-extensions/coc-svelte/,, https://github.com/iamcco/coc-tailwindcss/,, https://github.com/neoclide/coc.nvim/,release, <ins> https://github.com/manicmaniac/coconut.vim/,HEAD, </ins> https://github.com/metakirby5/codi.vim/,, https://github.com/tjdevries/colorbuddy.nvim/,, https://github.com/lilydjwg/colorizer/,,

Discussion:
Project description Vim syntax highlight and indent definition for Coconut Metadata homepage URL: source URL: license: none platforms: vim
Blocked by
there shouldn't be any blocking anymore
Change:
''; nativeBuildInputs = [ autoPatchelfHook makeWrapper wrapQtAppsHook ]; <del> buildInputs = [ qtbase qtwebengine qtx11extras qtquickcontrols2 icu63 ]; </del> <ins> buildInputs = [ qtbase qtwebengine qtx11extras qtquickcontrols2 qtgraphicaleffects icu63 ]; </ins> installPhase = '' mkdir -p $out/share/teamviewer $out/bin $out/share/applications

Discussion:
After installing the update for TeamViewer 15.49.2 (introduced in ) I can no longer connect to remote hosts. The connection is established, but the window does not appear. If i try to connect to the same host again, I receive the message that I already have a connection open. Looking at the logs, this might be the issue: TeamViewer was working as expected on another system that was running version 15.38. After the update of that system, the same problem appears. TeamViewer to any host new window appears to the same host again "you are already connected" appears Please run and paste the result.
I'm still facing the same issue using
Please add more information and reopen a new issue. Thanks
Change:
stdenv.mkDerivation rec { pname = "drush"; <del> version = "6.1.0"; </del> <ins> version = "8.4.10"; </ins> <del> meta = with lib; { description = "Command-line shell and Unix scripting interface for Drupal"; homepage    = "https://github.com/drush-ops/drush"; license     = licenses.gpl2; maintainers = with maintainers; [ lovek323 ]; platforms   = platforms.all; </del> <ins> src = fetchurl { url = "https://github.com/drush-ops/drush/releases/download/${version}/drush.phar"; sha256 = "sha256-yXSoTDFLsjDiYkRfrIxv2WTVdHzgxZRvtn3Pht5XF4k="; </ins> }; <del> src = fetchFromGitHub { owner = "drush-ops"; repo  = pname; rev = version; sha256 = "sha256-0nf/m+xJmfHsFLuordiMp8UyrGGXuS70+zFHkIxLWhU="; }; consoleTable = fetchurl { url    = "http://download.pear.php.net/package/Console_Table-1.1.3.tgz"; sha256 = "07gbjd7m1fj5dmavr0z20vkqwx1cz2522sj9022p257jifj1yl76"; }; </del> <ins> dontUnpack = true; </ins> nativeBuildInputs = [ makeWrapper ]; installPhase = '' <del> # install libraries cd lib tar -xf ${consoleTable} cd .. mkdir -p "$out" cp -r . "$out/src" mkdir "$out/bin" wrapProgram "$out/src/drush" --prefix PATH : "${lib.makeBinPath [ which php bash coreutils ncurses ]}" ln -s "$out/src/drush" "$out/bin/drush" </del> <ins> mkdir -p $out/bin install -D $src $out/libexec/drush/drush.phar makeWrapper ${php}/bin/php $out/bin/drush  --add-flags "$out/libexec/drush/drush.phar"  --prefix PATH : "${lib.makeBinPath [ which php bash coreutils ncurses ]}" </ins> ''; <ins> meta = with lib; { description = "Command-line shell and Unix scripting interface for Drupal"; homepage = "https://github.com/drush-ops/drush"; license = licenses.gpl2; maintainers = with maintainers; [ lovek323 ]; platforms = platforms.all; }; </ins> }

Discussion:
I tried running in a Drupal website. It returned the following error: This seems to have changed since PHP 7.4, and php73 has been dropped from nixpkgs due to the lack of upstream maintenance. It seems our in nixpkgs also is heavily outdated. We might want to switch to Drush 8, which still is supported and should work with D6, D7, D8, according to their docs.