jiebi/CodeConvo huggingface dataset:
Change:
path=${prefetch[1]} echo "vivaldi: $vivaldi_version_old -> $vivaldi_version" <ins> echo "$path" </ins> (cd "$root" && update-source-version vivaldi "$vivaldi_version" "$hash") # Check vivaldi-ffmpeg-codecs version. chromium_version_old=$(version vivaldi-ffmpeg-codecs) <del> chromium_version=$(bsdtar xOf "$path" data.tar.xz | bsdtar xOf - ./opt/vivaldi/vivaldi-bin | strings | grep -A2 -i '^chrome/' | grep '^[0-9]+.[0-9]+.[1-9][0-9]+.[0-9]+') </del> <ins> chromium_version=$(bsdtar xOf "$path" data.tar.xz | bsdtar xOf - ./opt/vivaldi/vivaldi-bin | strings | grep '^[0-9]{2,}.[0-9]+.[0-9]{4,}+.[0-9]+$') </ins> if [[ "$chromium_version" != "$chromium_version_old" ]]; then echo "vivaldi-ffmpeg-codecs: $chromium_version_old -> $chromium_version"

Discussion:
This probably isn't a strictly NixOS issue, but nevertheless should be mentioned. The hash for vivaldi-stable2.1.1337.51-1 has changed. The old one in nixpkgs is 08x6abyz65vx4ycj8ys8sib9z1adb8ybmnrqjck69b30kbz78rj2, while nix-env reports 00rxp6rardxjg17g2b28y2rj8szqlainp4ga6c58z981zkxvdlls. to unstable channels. -env -i vivaldi system: host os: multi-user?: sandbox: version: channels(void): channels(root): nixpkgs:
unfortunately, sometimes software projects update different package sources with different sha256sums on their website, which will then error during build, until it gets fixed again Can you add a Pull Request, updating the hash in
Change:
, gettext , fetchFromGitLab , python3Packages <del> , libpwquality </del> , wrapGAppsHook4 , gtk4 , glib

Discussion:
When trying to start gnome-secrets it fails with the message: Steps to reproduce the behavior: -shell -p gnome-secrets --run "secrets" Please run and paste the result.
Also gnome-secrets 6.4 is available. Updating it to the latest version doesn't solve the issue :(
Fixed by
Thank you for your work!
Change:
{ lib <del> , substituteAll , buildPythonApplication , fetchFromGitHub , distutils_extra , setuptools-git </del> <ins> , fetchFromGitLab # native </ins> , intltool <del> , pygtk , libX11 , libXtst </del> , wrapGAppsHook <del> , gnome3 </del> <ins> , file # not native , xorg , gobject-introspection , gtk3 , python3 </ins> }: <del> buildPythonApplication rec { </del> <ins> python3.pkgs.buildPythonApplication rec { </ins> pname = "screenkey"; <del> version = "0.9"; </del> <ins> version = "1.2"; </ins> <del> src = fetchFromGitHub { owner = "wavexx"; </del> <ins> src = fetchFromGitLab { owner = "screenkey"; </ins> repo = "screenkey"; <del> rev = "screenkey-${version}"; sha256 = "14g7fiv9n7m03djwz1pp5034pffi87ssvss9bc1q8vq0ksn23vrw"; </del> <ins> rev = "v${version}"; sha256 = "1x13n57iy2pg3h3r994q3g5nbmh2gwk3qidmmcv0g7qa89n2gwbj"; </ins> }; <del> patches = [ (substituteAll { src = ./paths.patch; inherit libX11 libXtst; }) ]; </del> nativeBuildInputs = [ <del> distutils_extra setuptools-git </del> <ins> python3.pkgs.distutils_extra # Shouldn't be needed once https://gitlab.com/screenkey/screenkey/-/issues/122 is fixed. </ins> intltool <ins> # We are not sure why is this needed, but without it we get "file: command # not found" errors during build. file </ins> wrapGAppsHook <ins> # for setup hook gobject-introspection </ins> ]; buildInputs = [ <del> gnome3.adwaita-icon-theme </del> <ins> gtk3 </ins> ]; <del> propagatedBuildInputs = [ pygtk </del> <ins> propagatedBuildInputs = with python3.pkgs; [ pycairo pygobject3 </ins> ]; <ins> # Prevent double wrapping because of wrapGAppsHook dontWrapGApps = true; # https://github.com/NixOS/nixpkgs/issues/56943 strictDeps = false; preFixup = '' makeWrapperArgs+=("''${gappsWrapperArgs[@]}") ''; </ins> # screenkey does not have any tests doCheck = false; <ins> # Fix CDLL python calls for non absolute paths of xorg libraries postPatch = '' substituteInPlace Screenkey/xlib.py  --replace libX11.so.6 ${lib.getLib xorg.libX11}/lib/libX11.so.6  --replace libXtst.so.6 ${lib.getLib xorg.libXtst}/lib/libXtst.so.6 ''; </ins> meta = with lib; { homepage = "https://www.thregr.org/~wavexx/software/screenkey/"; description = "A screencast tool to display your keys inspired by Screenflick";

Discussion:
Project description Screenkey is currently in version 0.9. The latest version is currently 1.1. Major changes: The repository was migrated from github to gitlab Version 1.0 switched to Python 3 and GTK 3 Metadata homepage URL: source URL: changelog URL: Nix source URL:
Change:
cp -r ${fundamental-source} plugins/Fundamental/ chmod -R +rw plugins/Fundamental # will be used as build dir substituteInPlace plugin.mk --replace ":= all" ":= dist" <ins> substituteInPlace plugins/Fundamental/src/Logic.cpp  --replace  "LightButton<VCVBezelBig, VCVBezelLightBig<WhiteLight>>"  "struct rack::componentlibrary::LightButton<VCVBezelBig, VCVBezelLightBig<WhiteLight>>" </ins> # Fix reference to zenity substituteInPlace dep/osdialog/osdialog_zenity.c 

Discussion:
Package name: vcv-rack Latest released version: 2.4.1 Current version on the unstable channel: 2.4.0 Current version on the stable/release channel: 2.3.0 Notify maintainers Note for maintainers: Please tag this issue in your PR. Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
may be trying something with so I'll wait a bit
Honestly I have no idea what vcv-rack is, I just looked for a package I can update to test out a new feature for `nix-update. If you can, take this from from, feel free to update it.
Not sure if I'll have time in the next few weeks, so this is free to pick
Change:
<ins> import ./make-test-python.nix ({ lib, ... }: with lib; { name = "libreddit"; meta.maintainers = with maintainers; [ fab ]; nodes.machine = { pkgs, ... }: { services.libreddit.enable = true; }; testScript = '' machine.wait_for_unit("libreddit.service") machine.wait_for_open_port("8080") # The service wants to get data from https://www.reddit.com machine.succeed("curl http://localhost:8080/") ''; }) </ins>

Discussion:
Project description 10 second pitch: Libreddit is a portmanteau of "libre" (meaning freedom) and "Reddit". It is a private front-end like Invidious but for Reddit. Browse the coldest takes of r/unpopularopinion without being tracked. Demo: Metadata homepage URL: source URL: license: agpl3 platforms: unix, linux, darwin, ...
could you please give a try? Thanks
That's just the package, but not a service (like ) right?
Yes, it's only the package for the moment.
There seems to be a bug present in the latest release. I opened a feature request () which could improve the service. Sorry, it will take some time till we can finish this.
Change:
hash = "sha256-2ZUD+RBsl35QV3250JOPCIoJb4sJcBsiRE4SZaS6ROs="; }; <del> nativeBuildInputs = [ cmake python3 jq which pkg-config ]; </del> <ins> nativeBuildInputs = [ cmake python3 jq which pkg-config libsForQt5.qt5.wrapQtAppsHook ]; </ins> buildInputs = [ expat

Discussion:
Add vulkan-tools-lunarg to a devshell and see that the only executable it provides is vkvia. It should also at least build and provice vkconfig Steps to reproduce the behavior: vulkan-tools-lunarg to a devshell to execute vkconfig to debug your vulkan application that it is not found in your path I expected vkconfig to be built and included in the vulkan-tools-lunarg derivation
Change:
<ins> { lib }: { meta = with lib; { description = "Comprehensive, professional-quality productivity suite, a variant of openoffice.org"; homepage = "https://libreoffice.org/"; license = licenses.lgpl3; maintainers = with maintainers; [ raskin tricktron ]; platforms = platforms.linux ++ [ "x86_64-darwin" "aarch64-darwin" ]; }; } </ins>

Discussion:
Apparently the DMG download is 404'ing - see below. Perhaps a different mirror should be used:
Apparently they remove older versions. Maintainer:
Maybe we can use to avoid 404's.
Good input. I'll update the version and have a look at it tomorrow.
is 404'ing again: . Should we re-open this issue?
I can't see version 7.2.5 in any supported nixpkgs branch anymore. If you're using an old commit, you'll be getting old bugs, of course.
Change:
python-dotenv python-frontmatter requests <ins> setuptools </ins> tinydb validators werkzeug

Discussion:
Looks like it is missing python3Packages.setuptools...
works for me - please provide output from
fixes that, but then you will be running into
I have informed the author of archivy, and he's looking into it.
This is because in the version requirements are loosened and an incompatible new version of flask is used to run archivy. Removing this change to the version constraints for flask would fix the problem.
Change:
, enableQt ? true , callPackage , qtwayland <ins> , fetchPypi </ins> }: let <del> version = "4.5.3"; </del> <ins> version = "4.5.4"; python = python3.override { self = python; packageOverrides = self: super: { # Pin ledger-bitcoin to 0.2.1 ledger-bitcoin = super.ledger-bitcoin.overridePythonAttrs (oldAttrs: rec { version = "0.2.1"; format = "pyproject"; src = fetchPypi { pname = "ledger_bitcoin"; inherit version; hash = "sha256-AWl/q2MzzspNIo6yf30S92PgM/Ygsb+1lJsg7Asztso="; }; }); }; }; </ins> libsecp256k1_name = if stdenv.isLinux then "libsecp256k1.so.{v}"

Discussion:
Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
for component in src gmic_stdlib; do # The script will not perform an update when the version attribute is up to date from previous platform run # We need to clear it before each run <del> update-source-version "--source-key=$component" "gmic" 0 "$(printf '0%.0s' {1..64})" </del> <ins> update-source-version "--source-key=$component" "gmic" 0 "${lib.fakeHash}" </ins> update-source-version "--source-key=$component" "gmic" $latestVersion done '';

Discussion:
Steps to reproduce the behavior: gmic from There are more of those function arity errors, but just a small sample since they're the same. I'm going to assume pull in today has something to do with it. no maintainer? merged and it shows failures for gmic. gmic is used for me in GIMP and darktable. Please run and paste the result.
I will revert this preventively. There are many strange bugs happening.
Change:
false fi rm -f $AUTH_KEYS <ins> SSH_HOST_KEYS_DIR=$(${mktemp} -d) ${wget} -O $SSH_HOST_KEYS_DIR/ssh_host_ed25519_key http://metadata.google.internal/computeMetadata/v1/instance/attributes/ssh_host_ed25519_key ${wget} -O $SSH_HOST_KEYS_DIR/ssh_host_ed25519_key.pub http://metadata.google.internal/computeMetadata/v1/instance/attributes/ssh_host_ed25519_key_pub if [ -s $SSH_HOST_KEYS_DIR/ssh_host_ed25519_key -a -s $SSH_HOST_KEYS_DIR/ssh_host_ed25519_key.pub ]; then mv -f $SSH_HOST_KEYS_DIR/ssh_host_ed25519_key* /etc/ssh/ chmod 600 /etc/ssh/ssh_host_ed25519_key chmod 644 /etc/ssh/ssh_host_ed25519_key.pub else echo "Setup of ssh host keys from http://metadata.google.internal/computeMetadata/v1/instance/attributes/ failed." false fi rm -f $SSH_HOST_KEYS_DIR </ins> ''; serviceConfig.Type = "oneshot"; serviceConfig.RemainAfterExit = true;

Discussion:
Unable to download the public google cloud image, Can confirm the other very outdated images are downloadable. The bucket object is not world readable.
Would really appreciate a fix to this, combined with I can't create a working vm. edit: worked around.
Having the same issue
Where did you get the link from? I think the URI should be: gs://nixos-cloud-images/nixos-image-18.03..-x86_64-
This page There is definitely a new image someone too. The bucket url you listed is not public either. To be honest, I didn't trust those images and built my own. I made this issue to benefit other people.
I have removed that image, as the nixos-images bucket is an old bucket. Probably got upload accidentally, when the creation script referred to it still. I tried generating a new image, however, that has issues connecting via ssh (nixops), as some code was removed from nixpkgs that downloads SSH host key from metadata in . I might have time to look into that next week. Not sure yet what the correct way forward is.
I'll have look at the issue in nixops this weekend.
Is there a new 18.03 image now ? I can't seem to find a link to it in the nixpkgs repo.
I think the issue preventing the image generation was fixed now. Otherwise, afaik takes care of updating the images, so better ask him if there is anything else pending ?
(25 days ago) mentions an image from May 29 currently being present, after these comments, but still quite old, and for 18.03, 18.09 is still missing. Closing this issue in favour of .
Change:
${optionalString (cfg.pubkeyAcceptedKeyTypes != []) "PubkeyAcceptedKeyTypes ${concatStringsSep "," cfg.pubkeyAcceptedKeyTypes}"} ${optionalString (cfg.hostKeyAlgorithms != []) "HostKeyAlgorithms ${concatStringsSep "," cfg.hostKeyAlgorithms}"} <del> ${cfg.extraConfig} </del> ''; environment.etc."ssh/ssh_known_hosts".text = knownHostsText;

Discussion:
The following setting has no effect: This is because the is set globally depending on whether the host is IPv6 capable . This line should be set after , otherwise it is not possible to override it for a specific host (first match wins). Perhaps the other options should be moved as well? Alternatively, the line could only be set if it is not , as that is the default. However, I don't think that is the right solution. Insert the above snippet into , and try to connect to an IPv4 only server from an IPv6-capable client. Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): channels(kai): nixpkgs:
This server is probably a bit weird in that it has both IPv6/4 DNS entries, but only accepts SSH connections over IPv4, so it's an odd edge case.
Change:
meta.maintainers = with lib.maintainers; [ eperuffo jtojnar rhoriguchi ]; })) <ins> (patchExtension "ddterm@amezin.github.com" (old: { # Requires gjs, zenity & vte via the typelib nativeBuildInputs = [ gobject-introspection wrapGAppsHook ]; buildInputs = [ vte ]; postPatch = '' for file in *.js com.github.amezin.ddterm; do substituteInPlace $file --replace "gjs" "${gjs}/bin/gjs" substituteInPlace $file --replace "zenity" "${gnome.zenity}/bin/zenity" done ''; postFixup = '' wrapGApp "$out/share/gnome-shell/extensions/ddterm@amezin.github.com/com.github.amezin.ddterm" ''; })) </ins> (patchExtension "display-brightness-ddcutil@themightydeity.github.com" (old: { # Has a hard-coded path to a run-time dependency # https://github.com/NixOS/nixpkgs/issues/136111

Discussion:
Describe the bug The "ddterm" extension does not work, because it lacks some NixOS-specific packaging magic having to do with , typelibs etc (I don't understand anything about it, just keyword-googled ) To Reproduce Steps to reproduce the behavior: to into Gnome F12 visible happens. "/run/current-system/sw/share/gnome- line 5: exec: gjs: not found" appears in the user journal Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(cmm): channels(root): nixpkgs: Maintainer information:
Would need patching to hardcode the GJS path.
note that adding to does not serve as a workaround, because then it fails due to not finding typelibs. so I'm not sure just patching in the path to will solve this.
Yeah, will need at least in and , , and in .
You can try
still cannot find the Vte typelib, whatever that is. I'll have to let the experts sort it out :)
If vte is used by the extension itself, not just by the program it executes, it will need something like
still broken on 21.11
As far as I can tell, VTE is not used by the extension itself. They do the required modules at runtime. My patch currently looks like this:
that's an improvement, but with it I still get (in a nice Zenity window this time):
only applies to stuff in and by default so will not actually get wrapped.
if I'm reading the of correctly, "by default" actually means "hard-coded, nothing you can do short of changing itself", right?
You can still use in .
After processing, the script looks like this: does not appear anywhere in this (although I think it should), and consequentially the error does not go away.
thanks for the hints folks! this overlay finally results in working ddterm here:
That's great to hear. Is the still needed though? Also, would you like to open a pull request fixing this? (Start in )
I thought you need to have in the build inputs so that the shell function is available?
You probably also need in the so that is picked up into automatically.
yup, that also works, pull amended
Change:
postFetch = '' rm $out/tests/demo/doc/ma*ana.txt ''; <del> hash = "sha256-i8HqMW36YtRxu/DLJWNiCfw6+ce3Gw8r8VBBo9l9aDI="; </del> <ins> hash = "sha256-PxyXlmEZ9cqZgDWcdeNznEC4F1J4NFMiwy0D7g+YZUs="; </ins> }; POETRY_DYNAMIC_VERSIONING_BYPASS = version;

Discussion:
Package name: copier Latest released version: 8.1.0 <!-- Search your package here: --- Current version on the unstable channel: 7.0.1 Current version on the stable/release channel: 7.0.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:
funding from the DOE. It is an open-source code, distributed freely under the terms of the GNU Public License (GPL). ''; <del> homepage = "https://lammps.sandia.gov"; license = licenses.gpl2Plus; </del> <ins> homepage = "https://www.lammps.org"; license = licenses.gpl2Only; </ins> platforms = platforms.linux; # compiling lammps with 64 bit support blas and lapack might cause runtime # segfaults. In anycase both blas and lapack should have the same #bits

Discussion:
With reference to please consider the following updates: The LAMMPS homepages is at The LAMMPS license is GPL-2.0 not GPL-2.0 or later.
Please feel free to submit a PR :)
Change:
streamScript = writePython3 "stream" {} ./stream_layered_image.py; baseJson = writeText "${name}-base.json" (builtins.toJSON { inherit config; <del> architecture = getArch system; </del> <ins> architecture = defaultArch; </ins> os = "linux"; });

Discussion:
Describe the bug It seems generates images with the wrong architecture set. ( began setting these values, but the values before were also wrong) To Reproduce Compared to the current version of : If you actually run the image on arm, Docker complains. Expected behavior Architectures embedded in the image configuration should match those generated by Docker. Additional context The warning message printed by Docker if the running platform doesn't match the image's platform. The operating system, architecture, and variant are determined by and . (If the image's architecture is "arm" and the variant is empty, as it almost always is, it is normalized to "v7", see ) Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(terin): nixpkgs: Maintainer information:
The specification is a bit loose, but the examples given all follow and . If we take a look at the specification, the fields should be and . Every officiall and semi-official image I've looked at, included the pre-multiarch manifest "legacy" images referenced at follow this pattern.
Change:
configureFlags = [ "--enable-simplexml" ]; <del> patches = lib.optionals (lib.versions.majorMinor php.version == "8.2" && lib.versionOlder php.version "8.2.22") [ </del> <ins> patches = lib.optionals (lib.versions.majorMinor php.version == "8.1") [ # Fix tests with libxml2 2.12 (fetchpatch { url = "https://github.com/php/php-src/commit/061058a9b1bbd90d27d97d79aebcf2b5029767b0.patch"; hash = "sha256-0hOlAG+pOYp/gUU0MUMZvzWpgr0ncJi5GB8IeNxxyEU="; excludes = [ "NEWS" ]; }) # Backport of PHP_LIBXML_IGNORE_DEPRECATIONS_START and PHP_LIBXML_IGNORE_DEPRECATIONS_END # Required for libxml2 2.13 compatibility patch. ../development/interpreters/php/php81-fix-libxml2-2.13-compatibility.patch # Fix build with libxml2 2.13+. Has to be applied after libxml2 2.12 patch. (fetchpatch { url = "https://github.com/php/php-src/commit/9b4f6b09d58a4e54ee60443bf9a8b166852c03e0.patch"; hash = "sha256-YC3I0BQi3o3+VmRu/UqpqPpaSC+ekPqzbORTHftbPvY="; }) ] ++ lib.optionals (lib.versions.majorMinor php.version == "8.2" && lib.versionOlder php.version "8.2.22") [ </ins> # Fixes compatibility with libxml2 2.13. Part of 8.3.10RC1+, 8.2.22RC1+ (fetchpatch { url = "https://github.com/php/php-src/commit/4fe821311cafb18ca8bdf20b9d796c48a13ba552.diff?full_index=1";

Discussion:
Steps to reproduce the behavior: php-simplexml-8.1.2 This happen after latest flake update Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hydra build : and seem fine: Probably related: (fixes for 8.2 and 8.3 with same error) 1 is out of active support, so there was no backport for from upstream PS you did not ping any maintainers for that package, so they would need to notice this issue (which is unlikely)
Also causes an lsp-plugins build failure. Gonna ping maintainers.
this is fixed in master
forgive my ignorance, but what needs to happen for the fix on master to make its way to the unstable channel? I would love to be able to rebuild my system soon
fixed "lsp-plugins build failure" (it does not depend on php 8.1 version now) If your system update depends on in some other way it won't help. does not build on current master as of (2024-07-30T19:50:23Z)
Well if you only need to rebuild your system again and you don't necessarily care about the updates you're missing out on, you can try using a previous version of your file
Change:
, fetchFromGitHub , autoreconfHook , fuse <del> , unrar </del> <ins> , unrar_6 </ins> }: stdenv.mkDerivation rec {

Discussion:
Package name: unrar Latest released version: 7.00 beta 3 Current version on the unstable channel: 6.2.12 Current version on the stable/release channel: 6.2.12 I receive more and more RAR files which are created with Unrar 7.00 beta versions / require a more recent version tan 6.2.12 I would appreciated if the existing unrar package can be updated or a new unrar-beta package be proposed .. Changelog : Notify maintainers
There was an automatic update in that I marked as draft, exactly because it's in beta. I'd much rather add a new package. what do you think?
I don't think we should update to the beta either. Sometimes I think about adding beta and release candidate versions to package , but that would be a nixpkgs policy discussion.
If people are still creating new RAR files then I don't want to be maintainer of this package. Stop using RAR.
Change:
firewall-nftables = handleTest ./firewall.nix { nftables = true; }; fish = handleTest ./fish.nix {}; flannel = handleTestOn ["x86_64-linux"] ./flannel.nix {}; <ins> floorp = handleTest ./firefox.nix { firefoxPackage = pkgs.floorp; }; </ins> fluentd = handleTest ./fluentd.nix {}; fluidd = handleTest ./fluidd.nix {}; fontconfig-default-fonts = handleTest ./fontconfig-default-fonts.nix {};

Discussion:
Project description Floorp is a firefox fork. Metadata homepage URL: source URL: license: MPLv2.0 platforms: windows, macos, linux