jiebi/CodeConvo huggingface dataset:
Change:
python = python2; buildType = "release"; # Manually sha256sum the extensionPack file, must be hex! <del> extpack = "13n6d6wca3bnvqc1q0bapgwfjmfqm19nxn9c0vbzd28c4l88j991"; </del> <ins> # Thus do not use `nix-prefetch-url` but instead plain old `sha256sum`. extpack = "21258910250c89f6d7062cd96e53a8d855e9f8bb6a011c18de760dc5b869c68e"; </ins> extpackRev = "120294"; main = "0agjldjn01p4x54m53db50xwamrphl7iqcrika3wa04rvlb36f40"; version = "5.1.32";

Discussion:
VirtualBox build crashes with error on extension pack SHA checksum mismatch. Extension pack file was prefetched using a link provided by license message and its checksum matches with . have this in your run (has done it with key)system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Same problem here system: host os: multi-user?: sandbox: version: channels(root): channels(markus): nixpkgs:
I also have the same problem. I tried patching in virtualboxn (and the 4.1.15 kernel) from unstable in an overlay, but now I sadly get this error: Is there any other way I can override this so I can rebuild my system?
I think the hash needs to be changed here to as mentioned above.
Yes. I'd make it by myself, but have no idea what to do here so nothing would be broken.
I guess this issue can be closed now.
Yes, now VirtualBox builds well. // btw, though has to stay on this channel version, as got new issues, such as audio jitter and big lags (a Spectre core patch?!). that's a different story to tell.
Change:
}; config = lib.mkIf cfg.enable { <ins> virtualisation.containers.containersConf.settings = { network.cni_plugin_dirs = [ "${pkgs.cni-plugins}/bin/" ]; engine = { init_path = "${pkgs.catatonit}/bin/catatonit"; } // lib.optionalAttrs cfg.ociSeccompBpfHook.enable { hooks_dir = [ config.boot.kernelPackages.oci-seccomp-bpf-hook ]; }; }; </ins> <del> environment.etc."containers/containers.conf".text = '' [network] cni_plugin_dirs = ["${pkgs.cni-plugins}/bin/"] [engine] init_path = "${pkgs.catatonit}/bin/catatonit" ${lib.optionalString (cfg.ociSeccompBpfHook.enable) '' hooks_dir = [ "${config.boot.kernelPackages.oci-seccomp-bpf-hook}", ] ''} '' + cfg.containersConf.extraConfig; </del> <ins> environment.etc."containers/containers.conf".source = toml.generate "containers.conf" cfg.containersConf.settings; </ins> <del> environment.etc."containers/registries.conf".source = toTOML "registries.conf" { </del> <ins> environment.etc."containers/registries.conf".source = toml.generate "registries.conf" { </ins> registries = lib.mapAttrs (n: v: { registries = v; }) cfg.registries; };

Discussion:
Describe the bug creates a defect as the block is defined two times. To Reproduce Steps to reproduce the behavior: Enable and Expected behavior and should be merged to one block. Additional context I'm on zfs. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(plumps): channels(root): nixpkgs: Maintainer information:
I have a PR up to fix this
Change:
nativeBuildInputs = [ makeWrapper ]; <ins> seshat = callPackage ./seshat {}; keytar = callPackage ./keytar {}; </ins> buildPhase = '' runHook preBuild export HOME=$(mktemp -d)

Discussion:
Describe the bug Riot-Desktop -Security & Privacy Under the "Message search" heading, observe: Riot is missing some components required for securely caching encrypted messages locally. If you'd like to experiment with this feature, build a custom Riot Desktop with search components . it links to here: Notify maintainers cc: Metadata Maintainer information:
Would be fantastic to have built with . I tried building it myself but couldn't do it. :cry:
Just stumbled across this myself. What's the current state on this? What needs to be done before this can be fixed?
So, element seems to use its own build system to build these native dependencies. It tries to download and build those itself with cargo and stuff. Seems quite complicated to package.
I would like to add that support for desktop notifications would be also appreciated. (They showed up on Arch's version, at least) Edit: This problem has been resolved since
I made some progress. This solves the issue of downloading the hakDependencies. Unfortunately they are not locked in any way, so we need to lock them at packaging-time (is that even a term?) by adding them to and Since yarn2nix always runs yarn with , we can safely ignore the upstream reasoning for fetching them outside of yarn dependencies. I'm now at the point where it tries to build seshat in the element-desktop derivation, but unfortunately they don't provide a Cargo lockfile. I'm working on resolving this problem upstream: <details</details
It turns out to be much more complicated, because the cargo build of seshat-node-native calls , so we have multiple layers of npm calling yarn calling cargo calling npm. With lots of things being downloaded and executed. It's a huge shitshow.
Is there anything we could do to help fix building with encrypted chat search working on NixOS?
I poured some (many) more hours into this today. I can build the two native modules, matrix-seshat and keytar, both in a seperate derivation and as part of the element-desktop build. However, I can not build them correctly against electron's node lib, so when starting the compiled thing, it refuses to load the module. Attempting to build against electron gives a mystic error.

Or the second approach, with everything in one derivation using the hak tool: <details</details<rantHonestly it's just a horrible build system. hak and neon and so on don't give any consideration to users who want to build the libraries in an environment without an internet connection. </rant If you can find a fix for the error, there shouldn't be much work left.
I think I found the solution to that error: Upstream is using Electron 12.x while we are using Electron 13.x.
! PR incoming :sparkles:
Change:
{ stdenv, fetchurl, fetchFromGitHub, cmake, pkgconfig, ncurses, zlib, xz, lzo, lz4, bzip2, snappy <del> , libiconv, openssl, pcre, boost, judy, bison, libxml2 </del> <ins> , libiconv, openssl, pcre, boost, judy, bison, libxml2, libkrb5 </ins> , libaio, libevent, jemalloc, cracklib, systemd, numactl, perl , fixDarwinDylibNames, cctools, CoreServices , asio, buildEnv, check, scons

Discussion:
mysqlupgrade requires availability of mysqlcheck, which is in the package In other operating systems they are separated - mysqlupgrade -, mysqlcheck - And when the server is installed the client is automatically installed.
Hmm, is there a reason not to make the client a dependency of the server? The only dependencies the client has that the server doesn't are and which any server should have (via openssh). How much space is saved by removing the client binaries?
So it seems the mysql_upgrade binary is hardcoded to expect the other binaries in the same directory: Probably the splitting works on other distros because the binaries all end up in /usr/bin anyway.
Need to build the package with server+client and only client? Is this variant bad?
I'm not sure what you mean. Can you check to see if the project cmake allows you to configure a different install PREFIX for the client/server?
Should I change the build of MariaDB, so that one package includes files for both server and client, and the other package only includes client files? I don't know how to configure this
19.09 milestone? If this and aren't resolved by then we will have to add the client binaries back into the server package.
- this variant optimal?
update MariaDB configuration, please check this variant.
Fixed, mariadb package includes server and client binaries.
Change:
expat fftw fftwFloat <del> gtkmm2  # Could be build with gtk3 but proper UI theme is missing and therefore not very usable with gtk3 # See: https://discuss.pixls.us/t/help-needed-for-gtk3-theme/5803 </del> <ins> gtkmm2 # Could be build with gtk3 but proper UI theme is missing and therefore not very usable with gtk3 # See: https://discuss.pixls.us/t/help-needed-for-gtk3-theme/5803 </ins> lcms2 lensfun libexif

Discussion:
Steps to reproduce the behavior: Adding fixes the issue. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.
Change:
krename-qt5 = krename; # added 2017-02-18 keymon = throw "keymon has been removed from nixpkgs, as it's abandoned and archived."; # 2019-12-10 kvm = qemu_kvm; # added 2018-04-25 <ins> latinmodern-math = lmmath; </ins> letsencrypt = certbot; # added 2016-05-16 libaudit = audit; # added 2018-04-25 libcanberra_gtk2 = libcanberra-gtk2; # added 2018-02-25

Discussion:
A grep of : The latest version is 1.959 per I'd say that the texlive and fonts/lm-math versions can stay as they have different paths ( vs ), although ideally just the texlive version would stay, but the others are not helping anything at all.
cc for comments
– has meta, unpacks only the needed files – resides in the same directory with , tries to provide texmf So, perhaps, we should keep the implementation of under the name and make an alias. The satysfi needs to be fixed to use existing packages (also implements a duplicate of ).
Well, for texmf one would presumably use the TexLive package, as it has separated and outputs unlike the other packages. And it auto-updates along with the rest of TexLive. The only issue with using it as the sole package is that it's not a multiple output derivation so using it in the fonts list looks like rather than just . It shouldn't be that hard to set up TexLive to have attributes usable directly, by setting and so forth. Nix doesn't support multiple outputs for fixed-output derivations, so it'd be a bit of a hack.
The "packages" in are set up to be used with . They were not intended to be used in any other way.
Change:
}: let <del> systems = [ "/run/current-system/kernel-modules" "/run/booted-system/kernel-modules" "" ]; </del> <ins> systems = [ "/run/booted-system/kernel-modules" "/run/current-system/kernel-modules" "" ]; </ins> modulesDirs = lib.concatMapStringsSep ":" (x: "${x}/lib/modules") systems; in stdenv.mkDerivation rec {

Discussion:
After update can't properly reload zram module. Reproducible only with . journalctl -eu zram-reloader.service Steps to reproduce the behavior: zram and switch to ; ; switch to ; the logs. Successful module reload. None. None. Maintainer information:
i assume a reboot fixed this? its probably because the booted kernel and the updated kernel versions mismatched i suspect that this line may be causing it it was in this pr but it states that extra info at
Yes, after reboot everything works fine.
is different from what it was in nix-info ?
No. The system has already been rebooted after the update.
I can't find in paths: It is there where the kernel is:
find doesn't work with symlinks fd with -L does
i got this same issue and before rebooting i tested changing the path order in kmod expr and it worked
Progress of the pr can be tracked at
Change:
<ins> { stdenv , lib , rustPlatform , fetchpatch , fetchFromGitHub , pkg-config , dbus , openssl }: rustPlatform.buildRustPackage rec { pname = "tiny"; version = "0.5.1"; src = fetchFromGitHub { owner = "osa1"; repo = pname; rev = "v${version}"; sha256 = "1m57xsrc7lzkrm8k1wh3yx3in5bhd0qjzygxdwr8lvigpsiy5caa"; }; cargoSha256 = "1vj6whnx8gd5r66zric9163ddlqc4al4azj0dvhv5sq0r33871kv"; RUSTC_BOOTSTRAP = 1; nativeBuildInputs = lib.optional stdenv.isLinux pkg-config; buildInputs = lib.optionals stdenv.isLinux [ dbus openssl ]; meta = with lib; { description = "A console IRC client"; homepage = "https://github.com/osa1/tiny"; license = licenses.mit; maintainers = with maintainers; [ filalex77 ]; }; } </ins>

Discussion:
Project description A tiny IRC client Metadata homepage URL: source URL: license: mit platforms: linux
Change:
installPhase = '' runHook preInstall <del> mkdir -p $out/bin $out/share/${pname}/ mv resources/app.asar* $out/share/${pname}/ </del> <ins> mkdir -p $out/bin $out/share/${finalAttrs.pname}/ mv resources/app.asar* $out/share/${finalAttrs.pname}/ </ins> mkdir -p $out/share/applications <del> ln -s ${desktopItem}/share/applications/* $out/share/applications/ </del> <ins> ln -s ${finalAttrs.desktopItem}/share/applications/* $out/share/applications/ </ins> <del> makeWrapper ${electron}/bin/electron $out/bin/${pname}  --add-flags $out/share/${pname}/app.asar </del> <ins> makeWrapper ${electron}/bin/electron $out/bin/${finalAttrs.pname}  --add-flags $out/share/${finalAttrs.pname}/app.asar </ins> runHook postInstall '';

Discussion:
Package name: Stretchly Latest released version: 1.15.1 <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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:
<del> { stdenv, fetchurl, perlPackages, iproute }: </del> <ins> { stdenv, fetchurl, perlPackages, iproute, perl }: </ins> perlPackages.buildPerlPackage rec { name = "ddclient-${version}";

Discussion:
Right now if you update the unstable tree and install ddclient the shebang patch is not applied properly and the first line of the script starts with: This reference doesn't exist so the actual binary cannot be started. ) Install ddclient ) Attempt to start ddclient
Change:
, substituteAll , nix-update-script # To include additional plugins, pass them here as an overlay. <del> , packageOverrides ? self: super: {} </del> <ins> , packageOverrides ? self: super: { } </ins> }: let mkOverride = attrname: version: sha256: <del> self: super: { ${attrname} = super.${attrname}.overridePythonAttrs ( oldAttrs: { inherit version; src = oldAttrs.src.override { inherit version sha256; }; } ); }; </del> <ins> self: super: { ${attrname} = super.${attrname}.overridePythonAttrs ( oldAttrs: { inherit version; src = oldAttrs.src.override { inherit version sha256; }; } ); }; </ins> py = python3.override { self = py; <del> packageOverrides = lib.foldr lib.composeExtensions (self: super: {}) ( </del> <ins> packageOverrides = lib.foldr lib.composeExtensions (self: super: { }) ( </ins> [ # the following dependencies are non trivial to update since later versions introduce backwards incompatible # changes that might affect plugins, or due to other observed problems

Discussion:
The recent nixos-unstable update () breaks octoprint. Last known good commit is . Steps to reproduce the behavior: result: This is probably because the derivation of octoprint has an override for . Werkzeug changed its API in version 2, which lead to a similar . When v1.0.1 , it fails with the old Werkzeug version due to an incorrect redirect. This is also why builds without issues, but fails to build, when its needed for octoprint. I'm not a 100% sure its the werkzeug override. Octoprint has a lot of Python overrides.. build sucessfully. Please run and paste the result.
Feel free to open a PR overriding the pytest-httpbin version for octoprint.
it seems it wasn't just (at least not in aarch64). Anyway, I submitted a PR which should fix the build issues introduced by recent Python upgrades.
Change:
<ins> { stdenv, fetchurl, pkgconfig, libnl, popt, gnugrep }: stdenv.mkDerivation rec { name = "ipvsadm-${version}"; version = "1.29"; src = fetchurl { url = "mirror://kernel/linux/utils/kernel/ipvsadm/${name}.tar.xz"; sha256 = "c3de4a21d90a02c621f0c72ee36a7aa27374b6f29fd4178f33fbf71b4c66c149"; }; postPatch = '' substituteInPlace Makefile --replace "-lnl" "$(pkg-config --libs libnl-genl-3.0)" ''; nativeBuildInputs = [ pkgconfig ]; buildInputs = [ libnl popt ]; preBuild = '' makeFlagsArray+=( INCLUDE=$(pkg-config --cflags libnl-genl-3.0) BUILD_ROOT=$out MANDIR=share/man ) ''; postInstall = '' sed -i -e "s|^PATH=.*|PATH=$out/bin:${gnugrep}/bin|" $out/sbin/ipvsadm-{restore,save} ''; meta = with stdenv.lib; { description = "Linux Virtual Server support programs"; homepage = http://www.linuxvirtualserver.org/software/ipvs.html; license = licenses.gpl2; platforms = platforms.linux; }; } </ins>

Discussion:
The program described by this man page is not available in master. ag ipvsadm
Poked at this, looks like it needs which because it was old and krufty even back then (note the patches required). That seems like a bit of a show-stopper, unfortunately.
Thanks! Is there a replacement for that I am missing? is still a part of the Linux kernel.
Enjoy! LMK if you're able to actual test it or know how to employ the tools :+1:.
I plan to do that tomorrow. I hope the tools will tell me the crucial information I need to make it work.
This works great and should be merged. It told me something unexpected, but that's good.
Change:
if pkgs.stdenv.hostPlatform != pkgs.stdenv.buildPlatform then '' echo "Ignoring validation for cross-compilation" '' <del> else '' </del> <ins> else let showCommand = if isNixAtLeast "2.20pre" then "config show" else "show-config"; in '' </ins> echo "Validating generated nix.conf" ln -s $out ./nix.conf set -e set +o pipefail NIX_CONF_DIR=$PWD  <del> ${cfg.package}/bin/nix show-config ${optionalString (isNixAtLeast "2.3pre") "--no-net"}  </del> <ins> ${cfg.package}/bin/nix ${showCommand} ${optionalString (isNixAtLeast "2.3pre") "--no-net"}  </ins> ${optionalString (isNixAtLeast "2.4pre") "--option experimental-features nix-command"}  |& sed -e 's/^warning:/error:/'  | (! grep '${if cfg.checkAllErrors then "^error:" else "^error: unknown setting"}')

Discussion:
When building the system configuration, there is a check for the generated nix config, which seems to use internally. This check fails when using with a drv from nix master, as there creates a hard error and exits with a non zero exit code. The message suggests to use instead Steps to reproduce the behavior: to a nix from master. Seems to happen since 2023-11-28 on my CI the system it fail, similar to The build of the system suceeds Please see the linked build logs instead nixos/nix seems to be the PR that introduced the behaviour on the side. (only person touching relevant module) (author of the nix PR) This is the last known to build version: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Uh, I though deprecated aliases were only throwing a warning, not a hard error. is that really the behaviour we want?
Oh, but it's not an error from the Nix side, it's the NixOS module code that rewrites warnings into hard errors :grimacing:
Yeah I have my fingerprints all over the module... The reason it escalates warnings to errors is Maybe we could make the activation script print warnings instead, so we don't have to do this kind of thing. Anyway, the simplest fix is to use the new syntax. could you try ?
Would the new syntax also work for users that still use nix 2.3? I will test the PR later today nevertheless.
Okay, just checked the changes in the PR. You do indeed a version based switch of the actual command to use :+1: I will give it a try in a couple of hours, need to be back at PC first.
Yeah, I guessed that would be something like that. I suppose it could make sense to have a way to have these triggered as hard errors (although that would be a bit tricky to implement because that would mean having a setting that influences how the settings parser works :upsidedown_face: )
I was finally able to check, and the PR seems to work for me. Just took ages as I had to build qemu from scratch…
Change:
<ins> { lib , stdenv , rustPlatform , fetchFromGitHub , fetchpatch , pkg-config , openssl , Security }: rustPlatform.buildRustPackage rec { pname = "replibyte"; version = "0.9.7"; src = fetchFromGitHub { owner = "Qovery"; repo = pname; rev = "v${version}"; sha256 = "02bdz0464d6gbkgbvn67sgn6cc6p6pjqacblh8nimy0r8b13x2ki"; }; # Lockfile was updated in a commit after the release cargoPatches = [ (fetchpatch { url = "https://github.com/Qovery/Replibyte/commit/15f122cc83fff03ae410be705779ab964fa7b375.patch"; sha256 = "sha256-v95V4pl/2WN2do2SLVTJIO+5J7esqhC2BZaGBEtDhe0="; }) ]; cargoSha256 = "sha256-Y9CXpJTY/uszAVAbafa2+FumWKWFGaOLhK1FY+Nc+EU="; nativeBuildInputs = [ pkg-config ]; buildInputs = [ openssl ] ++ lib.optionals stdenv.isDarwin [ Security ]; cargoBuildFlags = [ "--all-features" ]; doCheck = false; # requires multiple dbs to be installed meta = with lib; { description = "Seed your development database with real data"; homepage = "https://github.com/Qovery/replibyte"; license = licenses.gpl3Only; maintainers = with maintainers; [ dit7ya ]; }; } </ins>

Discussion:
Project description Helps you seed your development database with real data Metadata homepage URL: source URL: license: gpl3 platforms: unix, linux, darwin
Hey can you please test the linked PR? I had to skip the internal package tests because of a lot of complexity.
Change:
<del> { callPackage, fetchurl, ... } @ args: </del> <ins> { callPackage, ... } @ args: </ins> callPackage ./generic.nix (args // rec { version = "${branch}.2"; branch = "1.5"; <del> src = fetchurl { url = "mirror://gentoo/distfiles/openjpeg-${version}.tar.gz"; sha256 = "11waq9w215zvzxrpv40afyd18qf79mxc28fda80bm3ax98cpppqm"; }; </del> <ins> sha256 = "11waq9w215zvzxrpv40afyd18qf79mxc28fda80bm3ax98cpppqm"; </ins> })

Discussion:
I tried building openjpeg as a dependency when using on Mac OS X, and it failed on trying to run javac. Nevertheless, its derivation seemed to define (long line follows). The package built successfully after I installed an external JDK. It seems that for some strange reason the build script is ignoring the option.
Should fix this. JPIP builds a java component, but the cmake script does not require for
Thanks for the quick reaction! I will try the fix soon!
Change:
[ kernelPatches.bridge_stp_helper kernelPatches.cpu-cgroup-v2."4.4" kernelPatches.modinst_arg_list_too_long <ins> # https://github.com/NixOS/nixpkgs/issues/42755 # Remove these xen-netfront patches once they're included in # upstream! Fixes https://github.com/NixOS/nixpkgs/issues/42755 kernelPatches.xen-netfront_fix_mismatched_rtnl_unlock kernelPatches.xen-netfront_update_features_after_registering_netdev </ins> ]; };

Discussion:
Network access works well on a new instance booted from the stable AMIs listed on the website, but after running and rebooting the instance, it is broken. More specifically, the host can no longer send packets with an MSS larger than 3836. two EC2 instances from one of the 18.03 AMIs in the same VPC one of them latest stable with and reboot the security group to allow internal VPC communication on the host without the updates and on the updated one As I was writing this, I dug a bit deeper and found out that this is a bug introduced in the 4.14.37 release of the kernel. It is fixed in master (commit and possibly .) Applying those patches to the 4.14.51 kernel in stable fixes this issue for me.
Fix is now backported to 18.03.
Change:
runHook postInstall ''; <ins> passthru.updateScript = writeScript "update-redux" '' #!/usr/bin/env nix-shell #!nix-shell -I nixpkgs=./. -i bash -p curl htmlq common-updater-scripts set -euo pipefail new_version="$( curl 'https://files.renoise.com/demo/'  | htmlq a --text  | grep -E '^Renoise_Redux_([0-9]+_?)+_Demo_Linux_x86_64.tar.gz$'  | grep -Eo '[0-9]+(_[0-9]+)*'  | head -n1  | tr _ . )" update-source-version redux "$new_version" --system="x86_64-linux" ''; </ins> meta = with lib; { description = "Sample-based instrument, with a powerful phrase sequencer"; homepage = "https://www.renoise.com/products/redux";

Discussion:
404 when trying to install. Version is out of date on both stable / unstable. Current version is 1.3.5 aka <

<] Trying to install this and get failure due to bad URL. Probably due to a stale version number, this should target the most recent version or redux