jiebi/CodeConvo huggingface dataset:
Change:
vendorSha256 = null; <ins> ldflags = [ "-s" "-w" "-X github.com/cilium/hubble/pkg.GitBranch=none" "-X github.com/cilium/hubble/pkg.GitHash=none" "-X github.com/cilium/hubble/pkg.Version=${version}" ]; # Test fails at Test_getFlowsRequestWithInvalidRawFilters in github.com/cilium/hubble/cmd/observe # https://github.com/NixOS/nixpkgs/issues/178976 # https://github.com/cilium/hubble/pull/656 # https://github.com/cilium/hubble/pull/655 doCheck = false; doInstallCheck = true; installCheckPhase = '' $out/bin/hubble version | grep ${version} > /dev/null ''; nativeBuildInputs = [ installShellFiles ]; postInstall = '' installShellCompletion --cmd hubble  --bash <($out/bin/hubble completion bash)  --fish <($out/bin/hubble completion fish)  --zsh <($out/bin/hubble completion zsh) ''; </ins> meta = with lib; { broken = (stdenv.isLinux && stdenv.isAarch64) || stdenv.isDarwin; description = "Network, Service & Security Observability for Kubernetes using eBPF"; license = licenses.asl20; homepage = "https://github.com/cilium/hubble/"; <del> maintainers = with maintainers; [ humancalico ]; </del> <ins> maintainers = with maintainers; [ humancalico bryanasdev000 ]; </ins> }; }

Discussion:
Steps to reproduce the behavior: hubble Maybe related to and I've tried to build with Go 1.18 inside nix expression and get the same error, a nix-shell with cmake and go118 can build it OK. <!-- 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:
{ lib , fetchFromGitHub , python3 <del> , qt6 </del> <ins> , qtbase , qtsvg , qtwayland </ins> , nixosTests <ins> , wrapQtAppsHook </ins> }: python3.pkgs.buildPythonApplication rec {

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: on crash (coredump) The behaviour is very similar to a previous bug: Doesn't crash on startup.
Change:
, withGssapiPatches ? false , kerberos , libfido2 <del> , withFIDO ? stdenv.hostPlatform.isUnix </del> <ins> , withFIDO ? stdenv.hostPlatform.isUnix && !stdenv.hostPlatform.isMusl </ins> , linkOpenssl? true }:

Discussion:
Describe the bug After the PR is merged, as , fails to evaluate on . This is quite annoying because is a dependency of , which makes a sizable chunk of fail to evaluate on . I encountered this issue when trying to build . To Reproduce Steps to reproduce the behavior: Expected behavior , therefore to evaluate and run successfully on . cc
I believe should change the error message, but not fix the problem. Now the trace should go like hidapi -systemd, instead of hidapi -libusb -systemd. I don't really know where the infinite recursion comes from as that doesn't happen with nixos-19.09, however even if that didn't happen it wouldn't matter because systemd doesn't work with musl. If you want to fix this you'd have to look into getting the systemd dependency out of the hidapi nix expression. I'm not really sure why it's there in the first place, glancing at the hidapi , it seems like it depends on udev, which depends on util-linux which depends on systemd, but not on systemd directly and util-linux can be build without systemd. The utillinux nix expression already accounts for that possibility, you'd just have to make it actually do that for pkgsMusl. You could take the libusb nix expression as a template on how to achieve this. Disclaimer: I have virtually no experience with these low-level things, so I may be wrong.
Change:
<ins> #! /usr/bin/env nix-shell #! nix-shell -i bash -p gnused nix nodejs prefetch-npm-deps wget set -euo pipefail pushd "$(dirname "${BASH_SOURCE[0]}")" version=$(npm view @withgraphite/graphite-cli version) tarball="graphite-cli-$version.tgz" url="https://registry.npmjs.org/@withgraphite/graphite-cli/-/$tarball" if [[ "$UPDATE_NIX_OLD_VERSION" == "$version" ]]; then echo "Already up to date!" exit 0 fi sed -i 's#version = "[^"]*"#version = "'"$version"'"#' package.nix sha256=$(nix-prefetch-url "$url") src_hash=$(nix-hash --to-sri --type sha256 "$sha256") sed -i 's#hash = "[^"]*"#hash = "'"$src_hash"'"#' package.nix rm -f package-lock.json package.json *.tgz wget "$url" tar xf "$tarball" --strip-components=1 package/package.json npm i --package-lock-only npm_hash=$(prefetch-npm-deps package-lock.json) sed -i 's#npmDepsHash = "[^"]*"#npmDepsHash = "'"$npm_hash"'"#' package.nix rm -f package.json *.tgz popd </ins>

Discussion:
Package name: Grahpite-cli Latest released version: 1.1.1 <!-- Search your package here: --- Current version on the unstable channel: 1.0.9 Current version on the stable/release channel: 1.0.9 <!-- 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. This package has no maintainer because it is a NPM package. might be related? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hello thanks for the request, I will try to go from node2nix to build from source as the issue linked suggestes
Giving a quick check to the graphite-cli repo linked in the npm package it is archived and "moved to your mono-repo" and also it is built with yarn so nor it can migrated to buildNpmPackage nor to building from source, so my guess is that it will need to still in node2nix
Please make a PR marking the package as unfree since their monorepo isn't publicly available.
As of right now graphite-cli is already unfree
Change:
libsoup_3 pygobject3 pyopenssl <ins> setuptools </ins> ]; nativeCheckInputs = [

Discussion:
Package name: gajim Latest released version: 1.7.3 <!-- Search your package here: --- Current version on the unstable channel: 1.5.4 Current version on the stable/release channel: 1.6.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 Note for maintainers: Please tag this issue in your PR.
New sha256 hash, but it doesn’t just work with a version bump because they changed something with the build setup.
Change:
that it configures the NixOS boot process, not the Nix daemon. </para> </listitem> <ins> <listitem> <para> Deprecated <literal>xlibsWrapper</literal> transitional package has been removed in favour of direct use of its constitutents: <literal>xorg.libX11</literal>, <literal>freetype</literal> and others. </para> </listitem> </ins> </itemizedlist> </section> <section xml:id="sec-release-23.05-notable-changes">

Discussion:
In I noticed unusual behaviour of when is overridden. That PR handles override part. But I think should just disappear. Where should be no reason (for example) for to depend on at build time. is just the wrapper around a few libraries. Quoting : Mechanically we can replace with the list of packages it provides. Even better would be to audit needed libraries for each user and use only a subset of them. Example fix: [x] perlPackages.X11Protocol: [x] pulseaudio: More packages to fix: [x] Xaw3d: [x] emacs: [x] fox16: [x] geant4: [x] [x] gtk2: [x] [x] haskellPackages.greenclip: [x] [x] lesstif: [x] monotoneViz: [x] motif: [x] mythtv: [x] ocaml- [x] [x] [x] pypy2, pypy3: [x] qgis: [x] qgis-ltr: [x] [x] qt6Packages.qtwayland: [x] rPackages.Cairo: [x] rPackages.devEMF: [x] [x] rPackages,rgl: [x] tightvnc: [x] weston: Fixed packages: [x] astromenace: [x] catclock: [x] clanlib: [x] conky: [x] elinks: [x] fox: [x] freeglut: [x] ghostscript, ghostscriptX: [x] gnome2.libgnomeui: [x] glbinding: [x] glew, glew-egl: [x] glew110: [x] imhex: [x] imlib2,

imlib2Full: [x] ion3: [x] libagar: [x] libstroke: [x] lirc: [x] mitschemeX11: [x] ncview: [x] nedit: [x] notion: [x] oneko: [x] openrw: [x] pasystray: [x] pcb: [x] povray: [x] pythonFull: [x] qemacs: [x] qmmp: [x] rss-glx: [x] scrot: [x] soxt: [x] survex: [x] synergy: [x] ted: [x] unclutter: [x] unclutter-xfixes: [x] vlc: [x] voxelands: [x] wordnet: [x] xautolock: [x] xfe: [x] x11sshaskpass: [x] xfig: [x] xidlehook: [x] xine-ui: [x] xinputcalibrator: [x] xmountains: [x] xspim: [x] xtrlock-pam: [x] xwinwrap: [x] xxgdb: [x] zoom:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
{ stdenv, lib, fetchFromGitHub , rustPlatform, pkgconfig, openssl <ins> # testing packages , cargo-insta </ins> # darwin dependencies , Security, CoreFoundation, libiconv }: rustPlatform.buildRustPackage rec { pname = "cargo-geiger"; <del> version = "0.9.1"; </del> <ins> version = "0.10.2"; </ins> src = fetchFromGitHub { owner = "rust-secure-code"; repo = pname; rev = "${pname}-${version}"; <del> sha256 = "0kvmjahyx5dcjhry2hkvcshi0lbgipfj0as74a3h3bllfvdfkkg0"; </del> <ins> sha256 = "1z920p8i3gkjadyd6bqjk4i5yr5ds3m3sbcnf7plcqr69dsjr4b8"; </ins> }; <del> cargoSha256 = "0v50fkyf0a77l7whxalwnfqfi8lxy82z2gpd0fa0ib80qjla2n5z"; cargoPatches = [ ./cargo-lock.patch ]; </del> <ins> cargoSha256 = "1zh6fjfynkn4kgk1chigzd0sh4x1bagizyn7x6qyxgzc57a49bp7"; </ins> <del> # Multiple tests require internet connectivity, so they are disabled here. # If we ever get cargo-insta (https://crates.io/crates/insta) in tree, # we might be able to run these with something like # `cargo insta review` in the `preCheck` phase. </del> checkPhase = '' <del> cd cargo-geiger/tests/snapshots for file in * do mv $file r#$file done cd - cargo test --  --skip test_package::case_2  --skip test_package::case_3  --skip test_package::case_6 </del> <ins> ${cargo-insta}/bin/cargo-insta test </ins> ''; buildInputs = [ openssl ] ++ lib.optionals stdenv.isDarwin [ Security libiconv ];

Discussion:
Describe the bug The package cargo-geiger () fails its check phase: <details<summarycargo-geiger build log</summary</detailsNotify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Change:
vulkan-memory-allocator ]; <del> configurePhase = '' </del> <ins> configurePhase = let cpu = { "x86_64" = "x64"; "i686" = "x86"; "arm" = "arm"; "aarch64" = "arm64"; }.${stdenv.hostPlatform.parsed.cpu.name}; in '' </ins> runHook preConfigure gn gen build --args='${toString ([ # Build in release mode

Discussion:
N/A Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<del> --- a/main/CMakeLists.txt +++ b/main/CMakeLists.txt @@ -220,16 +219,0 @@ else (MINGW) -      ## install qwebengine core -      if (NOT APPLE AND USE_WEBENGINE) -         install(PROGRAMS -            ${QT_INSTALL_LIBEXECS}/QtWebEngineProcess -            DESTINATION bin -            ) -         install(DIRECTORY -            ${QT_INSTALL_DATA}/resources -            DESTINATION lib/qt5 -            ) -         install(DIRECTORY -            ${QT_INSTALL_TRANSLATIONS}/qtwebengine_locales -            DESTINATION lib/qt5/translations -            ) -      endif(NOT APPLE AND USE_WEBENGINE) - </del>

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 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: musescore <!-- The current version can be found easily with the same process as 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: 3.6.2 desired version: 4.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Change:
else true; in <del> assert licenseAllowed attrs; </del> lib.addPassthru (derivation ( (removeAttrs attrs ["meta" "passthru" "crossAttrs" "pos"

Discussion:
I have the following in my : And yet, despite setting , I still get the following error: I'm positive that my overrides are taking place, and that this isn't user error.
This is a bug in Nix/Nixpkgs: is too strict. See also
I filed to fix this. Did GitHub notify anybody here?
The first attempt from had to be reverted ().
Fixed by .
unfortunately, this change had the undesired side-effect of re-enabling the builds of all kinds of broken packages on Hydra, so now I get hundreds of evaluation errors where there used to be none, i.e.: How am I supposed to remedy that issue?
I'm a little confused by the fact/statement that there used to be none, but I think we can get rid of all, as there's now a lot of flexibility in handling the errors.
Note that this is the jobset -- not . That jobset always had zero evaluation errors until the behavior changed. I suppose I can fix most of them by changing the generator to set at the same time as . This used to be implicit before ...
I noticed but I didn't know you managed to clear all of them in haskell packages. I'll try to get rid of all (incl. trunk), as I expect that to be relatively easy now, but I can't promise it will be during this weekend already.
Change:
<ins> { fetchFromGitHub , fetchurl , lz4 ? null , lz4Support ? false , lzma , lzo , stdenv , xz , zlib }: assert lz4Support -> (lz4 != null); let patch = fetchFromGitHub { owner = "devttys0"; repo = "sasquatch"; rev = "3e0cc40fc6dbe32bd3a5e6c553b3320d5d91ceed"; sha256 = "19lhndjv7v9w6nmszry63zh5rqii9v7wvsbpc2n6q606hyz955g2"; } + "/patches/patch0.txt"; in stdenv.mkDerivation rec { pname = "sasquatch"; version = "4.3"; src = fetchurl { url = mirror://sourceforge/squashfs/squashfs4.3.tar.gz; sha256 = "1xpklm0y43nd9i6jw43y2xh5zvlmj9ar2rvknh0bh7kv8c95aq0d"; }; buildInputs = [ lzma lzo xz zlib ] ++ stdenv.lib.optional lz4Support lz4; patches = [ patch ]; patchFlags = [ "-p0" ]; postPatch = '' cd squashfs-tools ''; installFlags = "INSTALL_DIR=${out}/bin"; makeFlags = [ "XZ_SUPPORT=1" ] ++ stdenv.lib.optional lz4Support "LZ4_SUPPORT=1"; meta = with stdenv.lib; { homepage = "https://github.com/devttys0/sasquatch"; description = "Set of patches to the standard unsquashfs utility (part of squashfs-tools) that attempts to add support for as many hacked-up vendor-specific SquashFS implementations as possible"; license = licenses.gpl2Plus; maintainers = [ maintainers.pamplemousse ]; platforms = platforms.linux; }; } </ins>

Discussion:
Project description sasquatch is a varation of the unsquashfs utilty that can unpack a much larger amount of vendor specific flavours of squashfs that the regular unsquashfs utility cannot unpack. It is distributed as a patch to the regular squashfs-tools package (so might need some extra work to work with the squashfs-tools package already in nixpkgs). Metadata homepage URL: source URL: license: gpl2+ platforms: linux
Change:
vaapi = null; libva = null; libwebp = null; <ins> xwayland = null; </ins> }; weston = callPackage ../applications/window-managers/weston {

Discussion:
A in the xwayland package output causes nixos-rebuild to fail due to permission issues, since /var/tmp contains private directories (mode 700) System: NixOS 16.09 Nix version: 1.11.4 Nixpkgs version: 16.09.901.
Essentially the same problem as in vanilla X server:
found some more info on the problem the issue, is that both wayland and xorg have the same "fix" for packages wanting to write to the store, at the same place /nix/store/dd65ni8yzibvq2aj5jdylnv557i3hcd1-xwayland-1.18.4/share/X11/xkb/compiled and /nix/store/v82zrx8dnm5j8lq4a2fc5g0rcx2jx04k-xorg-server-1.18.4/share/X11/xkb/compiled are "conflicting" so buildEnv tries to cd into both, find every file within, and then create a compiled directory with symlinks to merge the 2 except, both versions of compiled are symlinks to /var/tmp in this case, there is no need to merge the contents of "compiled" since its 2 identical symlinks that are conflicting, so id say buildEnv should be patched and i have a simple testcase:
I'm guessing that this works OK when built in a sandbox?
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 .
As both the referenced packages build now, I guess it's safe to close this.
Change:
<del> { stdenv, fetchurl, libiconv }: </del> <ins> { stdenv, fetchurl, libiconv, fetchpatch }: </ins> stdenv.mkDerivation rec { name = "wavpack-${version}";

Discussion:
, (nixos-unstable) (nixos-unstable) (nixos-unstable) (nixos-unstable) (nixos-unstable) (nixos-unstable) (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.
I can't see this reported for 19.03, but the version is the same, so I cherry-picked that PR anyway.
Change:
./services/misc/gammu-smsd.nix ./services/misc/geoipupdate.nix ./services/misc/gitea.nix <del> # ./services/misc/gitit.nix </del> ./services/misc/gitlab.nix ./services/misc/gitolite.nix ./services/misc/gitweb.nix

Discussion:
This is essentially a repost of : We have a NixOS module for gitit in nixpkgs which due to its impact on evaluation performance. It continued to be shipped, so that one could include it manually, but it has bitrotted since then. One thing I noticed is that it makes an incorrect assumption where gitit's data files would be located, but there may be more issues. It would be great if we could either find someone willing to fix the module up or drop it altogether.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
if someone wants to fix it then the options should be converted to freeform and
At this time, I don't see anymore, neither in 22.11, neither in unstable. I am closing.
I still see on master. It was however excluded from evaluation in Edit: wrong commit, that just a space. . So it hasn't been evaluated since 2015… There's also some comments on that commit.
Oh thank you for correcting me. I used I am in favor of dropping it, I guess. It's not easy to discover and someone else can revive it at some point.
see IMO if nobody has stepped up in the years since, it hasn't been a priority to anyone. We can wait a few days for comments on . Then again, if someone still needs it, they can always revert/take it from the history.
Change:
''; }; <ins> generatePeerUnit = { interfaceName, interfaceCfg, peer }: let keyToUnitName = replaceChars [ "/" "-"    " "     "+"     "="      ] [ "-" "x2d" "x20" "x2b" "x3d" ]; unitName = keyToUnitName peer.publicKey; psk = if peer.presharedKey != null then pkgs.writeText "wg-psk" peer.presharedKey else peer.presharedKeyFile; in nameValuePair "wireguard-${interfaceName}-peer-${unitName}" { description = "WireGuard Peer - ${interfaceName} - ${peer.publicKey}"; requires = [ "wireguard-${interfaceName}.service" ]; after = [ "wireguard-${interfaceName}.service" ]; wantedBy = [ "multi-user.target" ]; environment.DEVICE = interfaceName; environment.WG_ENDPOINT_RESOLUTION_RETRIES = "infinity"; path = with pkgs; [ iproute wireguard-tools ]; serviceConfig = { Type = "oneshot"; RemainAfterExit = true; }; script = let wg_setup = "wg set ${interfaceName} peer ${peer.publicKey}" + optionalString (psk != null) " preshared-key ${psk}" + optionalString (peer.endpoint != null) " endpoint ${peer.endpoint}" + optionalString (peer.persistentKeepalive != null) " persistent-keepalive ${toString peer.persistentKeepalive}" + optionalString (peer.allowedIPs != []) " allowed-ips ${concatStringsSep "," peer.allowedIPs}"; route_setup = optionalString (interfaceCfg.allowedIPsAsRoutes != false) (concatMapStringsSep "n" (allowedIP: "ip route replace ${allowedIP} dev ${interfaceName} table ${interfaceCfg.table}" ) peer.allowedIPs); in '' ${wg_setup} ${route_setup} ''; </ins> <del> generateSetupServiceUnit = name: values: </del> <ins> postStop = let route_destroy = optionalString (interfaceCfg.allowedIPsAsRoutes != false) (concatMapStringsSep "n" (allowedIP: "ip route delete ${allowedIP} dev ${interfaceName} table ${interfaceCfg.table}" ) peer.allowedIPs); in '' wg set ${interfaceName} peer ${peer.publicKey} remove ${route_destroy} ''; }; generateInterfaceUnit = name: values: </ins> # exactly one way to specify the private key must be set #assert (values.privateKey != null) != (values.privateKeyFile != null); let privKey = if values.privateKeyFile != null then values.privateKeyFile else pkgs.writeText "wg-key" values.privateKey;

Discussion:
In there was an option introduced that indefinitely tries to restart the wireguard service until all peer hostnames are resolved. Instead it should use as introduced by instead. This feature will be available in the next snapshot release of wireguard. cc
Alright 0.0. has been released for the purpose of this disaster being fixed. care to cleanup the mess?
I fail to see what mess/disaster you're refering to.
Change:
xlib ]; <del> makeWrapperArgs = [ "--prefix PYTHONPATH : $PYTHONPATH" "--prefix GI_TYPELIB_PATH : $GI_TYPELIB_PATH" ]; </del> # the -cli symlink is just to maintain compabilility with older versions where # there was a difference between the GUI and CLI versions. postInstall = ''

Discussion:
Describe the bug Solaar crashes with the following error: Notify maintainers
thanks for report, I can reproduce it. I'll try to find some time to investigate, it looks like it cannot find an icon?
can you elaborate how you run this? I was able to reproduce the issue with , but when I install in the system with it works. It's something with xdg and icons discovery and I wasn't able to fix this, probably some specific XDG variable or desktop environment variable must be set to properly discover icons.
Yes, it seems like it was indeed the problem with icons. Installing KDE fixes the issue even without using it.
The wiki has a small section on this: But on a side note The package is out of date
thanks. Locally I updated to latest version and it didn't change much. If I have a sec I'll try debug little more.
Same error, here's the output i get when running I'm running i3 as my desktop environment
same problem with + . how you investigation progress?