jiebi/CodeConvo huggingface dataset:
Change:
# # I've chosen to import Alpine Linux, because its image is turbo-tiny and, # generally, sufficient for our tests. alpine-meta = pkgs.fetchurl { <del> url = "https://uk.images.linuxcontainers.org/images/alpine/3.11/i386/default/20200608_13:00/lxd.tar.xz"; sha256 = "1hkvaj3rr333zmx1759njy435lps33gl4ks8zfm7m4nqvipm26a0"; </del> <ins> url = "https://tarballs.nixos.org/alpine/3.12/lxd.tar.xz"; hash = "sha256-1tcKaO9lOkvqfmG/7FMbfAEToAuFy2YMewS8ysBKuLA="; </ins> }; alpine-rootfs = pkgs.fetchurl { <del> url = "https://uk.images.linuxcontainers.org/images/alpine/3.11/i386/default/20200608_13:00/rootfs.tar.xz"; sha256 = "1v82zdra4j5xwsff09qlp7h5vbsg54s0j7rdg4rynichfid3r347"; </del> <ins> url = "https://tarballs.nixos.org/alpine/3.12/rootfs.tar.xz"; hash = "sha256-Tba9sSoaiMtQLY45u7p5DMqXTSDgs/763L/SQp0bkCA="; </ins> }; lxd-config = pkgs.writeText "config.yaml" ''

Discussion:
Please find stable urls for the lxd container tests these fail to download now and are causing test failures: cc
Thanks for pinging - I will fix it later today :-)
Change:
nativeBuildInputs = [ lua  # for lua.h wrapLua <del> luarocks </del> <ins> luarocks_bootstrap </ins> ]; inherit doCheck extraConfig rockspecFilename knownRockspec externalDeps nativeCheckInputs;

Discussion:
luarocks exists that other luarocks packages can depend on. When trying to build a rockspec that depends on luarocks with , it fails. The entry in the generated luarocks config contains an entry for luarocks, but luarocks doesn't recognise it and tries to download the package instead. I have created a repository to reproduce it with: Run A workaround is to use to generate a expression for luarocks (), and to add that package to the 's instead of the package from nixpkgs. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
thanks for creating the test repo, it's helpful. I've looked at the generated LUAROCKSCONFIG and all looks good and I think luarocks just doesn't recognize the installed luarocks because of My first thought would have been to rename the current luarocks into a luarocksbootstrap and add a generated derivation, for which we could run the tests without the cyclic dependency luarocks -busted -luarocks. While this might be the best outcome longterm, I am looking into the quickfix which would be to generate the manifest for the current luarocks
Change:
../modules/testing/test-instrumentation.nix ../modules/profiles/qemu-guest.nix ]; <del> }).config.system.build.openstackImage; </del> <ins> }).config.system.build.openstackImage + "/nixos.qcow2"; </ins> sshKeys = import ./ssh-keys.nix pkgs; snakeOilPrivateKey = sshKeys.snakeOilPrivateKey.text;

Discussion:
Describe the bug On current master (), the ec2 tests don't work: Expected behavior They should work in order to be portable to python, see CCing contributors who wrote/touched this code:
Change:
free = false; }; <ins> ncbiPd = { spdxId = "NCBI-PD"; fullname = "NCBI Public Domain Notice"; # Due to United States copyright law, anything with this "license" does not have a copyright in the # jurisdiction of the United States. However, other jurisdictions may assign the United States # government copyright to the work, and the license explicitly states that in such a case, no license # is granted. This is nonfree and nonredistributable in most jurisdictions other than the United States. free = false; redistributable = false; }; </ins> ncsa = { spdxId = "NCSA"; fullName = "University of Illinois/NCSA Open Source License";

Discussion:
See
Same question a in . We could add the license if there is a need for it.
That would be for , which is not public domain worldwide.
Please open a PR that adds the license to and adjust the license of .
I'd do that, except I can't find any documentation as to what format the commit message should be.
Change:
src = ./fix-paths.patch; inherit asciidoc; }) <ins> ] ++ lib.optionals (stdenv.hostPlatform.isi686) [ # Upstream: https://gitlab.gnome.org/GNOME/tracker/-/issues/332 (fetchpatch { name = "i686-test.patch"; url = "https://gitlab.gnome.org/GNOME/tracker/-/commit/af707181a2c492a794daec7ce3f3062d67ffd9dc.patch"; sha256 = "sha256-KOdkTy79w3oiQILrPG00UVrv+VBjAk4Y868I8jtifqk="; }) </ins> ]; nativeBuildInputs = [

Discussion:
Not sure if this needs to be reported or going to be caught by automation anyway. Still, trying to install steam from unstable repo fails. Steps to reproduce the behavior: to install steam from unstable ... ... Please run and paste the result. Maintainer information:
Seems like reported already, thx , closing this one.
I think we should still keep this issue open. Not only was that comment in a merged merge request (rather than an issue) but Steam affects all desktop environments including non-gnome ones such as i3 (which I am running).
Upstream report:
This doesn't affect just Steam but also (but not limited to) Lutris and Wine.
I have stumbled upon this build failure tonight; with a command inside the unstable-small channel. Is the fix still in the production pipeline?
Change:
{ stdenv, fetchurl, pkgconfig, intltool, gtk, libxfce4util, libxfce4ui , libxfce4ui_gtk3, libwnck, exo, garcon, xfconf, libstartup_notification , makeWrapper, xfce4mixer, hicolor_icon_theme <del> , withGtk3 ? false, gtk3 </del> <ins> , withGtk3 ? false, gtk3, gettext </ins> }: let inherit (stdenv.lib) optional;

Discussion:
System: 18.03pre116572. (Impala) Nix version: nix-env (Nix) 1.11.15 Nixpkgs version: "18.03pre116572." Sandboxing enabled: false
Change:
rev = "v${version}"; sha256 = "1453qkd9s4z4r0xzmv8ym7qfg33szf6gizfkb5zxj590fcbsgnd7"; }; <del> vendorSha256 = null; </del> <ins> vendorSha256 = "0j25m56cwzjd9b75v7xlb26q81bsmln77k23h9n8v2f2gqwwpkrl"; </ins> subPackages = [ "cmd/helm" ]; buildFlagsArray = [ "-ldflags=-w -s -X helm.sh/helm/v3/internal/version.version=v${version}" ];

Discussion:
Describe the bug When I attempt to use from or , I get the following error: To Reproduce Steps to reproduce the behavior: Expected behavior Either is downloaded from cache or builds successfully. Additional context I had originally thought this was due to the recent , but it appears that there may be some upstream issues with Helm. For example, the say this: That having been said, I'm not totally convinced this is the root cause. I tried to confirm the fix with 3.2.2 by overriding the helm derivation to use the new version: No matter which of 3.2.2, 3.2.3, or 3.2.4 I choose, I get the same set of errors (see collapsed element below). <details<summary<strongBuild log for 3.2.4</strong</summary</detailsNotify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(gustavderdrache): nixpkgs: Maintainer information:
Update: it looks like caused the issue. If I pin nixpkgs to 's parent commit (), I can both fetch helm from the nix cache and build it locally:
Change:
inherit ruby; inherit dontBuild; inherit dontStrip; <ins> inherit suffix; </ins> gemType = type; nativeBuildInputs = [

Discussion:
Describe the bug fails to build when the gem configured in the is pointing to a git repository. <details<summaryGemfile</summary</details<details</summary</details<details</summary</details<details<summarynix-build output</summary</detailsTo Reproduce Run with the configuration posted above. Expected behavior The package should build like it does when the gem is pointed to a released version. Metadata Maintainer information:
Can confirm this, I have the same issue trying to package
I ran into this issue today. Both in my scenario and the recipe above the issue happens bundlerApp tries to of the gem. The directory find is call with doesn't exist. While I don't know the proper way to fix bundlerApp, a work around is to set the installManpages attributes to false. ej.
I'm having issue as well, is there any temporal fix atleast? Its annoying, and making my setup not-so-reproducible, I'm bundling puppet and it says: Its actually been created with rev: at and haven't been copied over.
Seems like you're right not installing manpages did somehow fix it, but not sure how you figured out... What I find post trying that is that the problem resides exactly in these lines:
I figured out the workaround by reading the error from nix log . Seeing the call to find being the error and looking for the expression responsible for making the call. Found it was the the installManpages option as you linked above. However I'm not familiar enough with the process to know what is the proper way to fix this. It seems the reason it fails is because in only has the dependencies of the gem we are building, not the gem itself. Should the man page installation happen in a latter phase? Should it look for the gem man pages in a different place? In what phase it is running?
I started a PR for the fix, can you please try building packages from this PR branch?
Change:
zscroll = callPackage ../applications/misc/zscroll {}; <del> zynaddsubfx = callPackage ../applications/audio/zynaddsubfx { }; </del> <ins> zynaddsubfx = zyn-fusion; zynaddsubfx-fltk = callPackage ../applications/audio/zynaddsubfx { guiModule = "fltk"; }; zynaddsubfx-ntk = callPackage ../applications/audio/zynaddsubfx { guiModule = "ntk"; }; zyn-fusion = callPackage ../applications/audio/zynaddsubfx { guiModule = "zest"; }; </ins> ### BLOCKCHAINS / CRYPTOCURRENCIES / WALLETS

Discussion:
Project description ! Zyn-Fusion is the new GUI front-end for . I tried to modify zynaddsubfx to use the package from (which is said to have included zyn-fusion) with no avail. Metadata homepage URL: source URL: license: platforms: linux cc zynaddsubfx maintainers
I marked this as stale due to inactivity. &rarr;
Change:
"--linux-cpu ${constants.alt-arch}" ] ++ lib.optional (!isOptimized) "--unoptimized" <del> ++ lib.optional (runtimeMode == "debug") "--no-stripped"; </del> <ins> ++ lib.optional (runtimeMode == "debug") "--no-stripped" ++ lib.optional finalAttrs.doCheck "--enable-unittests" ++ lib.optional (!finalAttrs.doCheck) "--no-enable-unittests"; </ins> # NOTE: Once https://github.com/flutter/flutter/issues/127606 is fixed, use "--no-prebuilt-dart-sdk" configurePhase =

Discussion:
Package name: flutter Latest released version: 3.24.1 <!-- Search your package here: --- Current version on the unstable channel: 3.22.2 Current version on the stable/release channel: 3.22.2 <!-- 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]:
CC
Already being done

Package name: flutter (stable, but also beta) Latest released version: 3.24.0 <!-- Search your package here: --- Current version on the unstable channel: 3.22.2 (beta version: 3.23.0) Current version on the stable/release channel: 3.22.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
CC has been a blocker for updates since it affects the update script but it is close to being ready.
Hmm, hopefully this can be resolved soon, as it's quite critical for my work.
Yeah, I hope to have it done soon. It's close. Unfortunately, I just don't always have enough time.
Yeah, of course! Take your time :)
Hey, since the blocker is merged, how is it looking with updating the flutter version? :) No worries, if you're too busy right now
I plan on doing that on my next day off work which will be Thursday.
Change:
assertion = !config.networking.useDHCP; message = "You can not use services.connman with networking.useDHCP"; }{ <del> assertion = config.networking.wireless.enable; message = "You must use services.connman with networking.wireless"; }{ </del> assertion = !config.networking.networkmanager.enable; message = "You can not use services.connman with networking.networkmanager"; }];

Discussion:
connman built with iwd: But module contains assertion that returns error when wpasupplicant is disabled (enabling iwd disables wpasupplicant):
In , the only supported way to use is to use it as a standalone wireless daemon. Even if you assertion was disabled, it wouldn't make a difference, since the configurations don't allow for to connect to . The default is setup for which differs from the one that is required [1]. Though it does look like it's relatively easy to enable integration with the addition of two services, for now it might be better to just override the module manually on your local configuration. [1]
If someone ends up putting together the needed bits, please share (probably as a PR)! Ive kludged network-manager into using iwd (kludge is needed for similar assertion and to not run iwd standalone, IIRC) but I'm keen to give connman a try :).
FYI guys, ConnMan doesn't really keep up to date with iwd and integration between the two might lead to frustration. See and The best bet for now is to use network manager with iwd ()
NetworkManager is ugly and buggy
I've been also using iwd without network manager or connman just fine.
I'm thinking of writing a GUI for iwd - to use iwd + dhcpcd
Heads up for anyone interested iwd 1.0 was released with breaking changes, refs:
Change:
<del> { lib, python3Packages, stdenv, writeTextDir, substituteAll, targetPackages }: </del> <ins> { lib , python3Packages , fetchpatch , stdenv , writeTextDir , substituteAll , targetPackages }: </ins> let # See https://mesonbuild.com/Reference-tables.html#cpu-families

Discussion:
Describe the bug The channel is currently blocked on the i686-linux minimal ISO not building. It's both failing at and Both of these packages use the meson build system and produce a similar output on failure cc It's another topic entirely if i686-linux should be able to block channels. In my opinion, it's not at the same tier of support to be able to have a channel blocking job like this.
Re channel dependency:
Git bisect said this was at fault ??
I got , damn the merge commits. Neither seems particularly suspect. Edit: I was using wrong bad tag, now I get the same.
That is just weird. On () I see the following in logs: Comparing the two does not show anything suspicious: /nix/store/d915ffl08q1yckm2laqwvjj55ykjq6vd-gcc-wrapper-8.3.0/bin/cc /nix/store/38rh09iclvs97fisbgy8fg6wxr33ijr1-gcc-wrapper-8.3.0/bin/cc
Applying the following to Meson revealed The error pointed me to  method and the empty argument to: The hash contains so it matches some obscure compiler!
Ewwwww :rofl: This is actually rather funny. I can assume what the folllow-up PR to this will be doing to meson...
Change:
<ins> { lib , fetchbzr , mkDerivation , qmake , qtserialport , qtmultimedia , qttools , qtscript }: let version = "0.4.15"; release = "SR10"; branch = "simulide_0.4.14"; # the branch name does not mach the version for some reason rev = "291"; sha256 = "sha256-BBoZr/S2pif0Jft5wrem8y00dXl08jq3kFiIUtOr3LM="; in mkDerivation { pname = "simulide"; version = "${version}-${release}"; src = fetchbzr { url = "https://code.launchpad.net/~arcachofo/simulide/${branch}"; inherit rev sha256; }; postPatch = '' # GCC 13 needs this header explicitly included sed -i src/gpsim/value.h -e '1i #include <cstdint>' sed -i src/gpsim/modules/watchdog.h -e '1i #include <cstdint>' sed -i resources/simulide.desktop  -e "s|^Exec=.*$|Exec=simulide|"  -e "s|^Icon=.*$|Icon=simulide|" sed -i SimulIDE.pro  -e "s|^VERSION = .*$|VERSION = ${version}|"  -e "s|^RELEASE = .*$|RELEASE = -${release}|"  -e "s|^REV_NO = .*$|REV_NO = ${rev}|"  -e "s|^BUILD_DATE = .*$|BUILD_DATE = ??-??-??|" ''; preConfigure = '' cd build_XX ''; nativeBuildInputs = [ qmake ]; buildInputs = [ qtserialport qtmultimedia qttools qtscript ]; installPhase = '' runHook preInstall install -Dm644 ../resources/simulide.desktop $out/share/applications/simulide.desktop install -Dm644 ../resources/icons/hicolor/256x256/simulide.png $out/share/icons/hicolor/256x256/apps/simulide.png mkdir -p $out/share/simulide $out/bin pushd executables/SimulIDE_* cp -r share/simulide/* $out/share/simulide cp bin/simulide $out/bin/simulide popd runHook postInstall ''; meta = with lib; { description = "A simple real time electronic circuit simulator"; longDescription = '' SimulIDE is a simple real time electronic circuit simulator, intended for hobbyist or students to learn and experiment with analog and digital electronic circuits and microcontrollers. It supports PIC, AVR, Arduino and other MCUs and MPUs. ''; homepage = "https://simulide.com/"; license = licenses.gpl3Only; mainProgram = "simulide"; maintainers = with maintainers; [ carloscraveiro tomasajt ]; platforms = ["x86_64-linux"]; }; } </ins>

Discussion:
Project description SimulIDE Circuit Simulator is a simple real time electronic circuit simulator, intended for hobbyist or students to learn and experiment with analog and digital electronic circuits and microcontrollers. It supports PIC, AVR , Arduino and other MCUs and MPUs. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
nativeBuildInputs = [ hatchling ]; nativeCheckInputs = [ <del> chainer </del> jupyter nbconvert numpy

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: python311Packages.chainer maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags: -
fixed in master
Change:
postPatch = '' substituteInPlace OpenBoard.pro  <del> --replace '/usr/include/quazip5' '${quazip}/include/QuaZip-Qt5-${quazip.version}/quazip'  </del> <ins> --replace '/usr/include/quazip5' '${lib.getDev quazip}/include/QuaZip-Qt5-${quazip.version}/quazip'  </ins> --replace '-lquazip5' '-lquazip1-qt5'  <del> --replace '/usr/include/poppler' '${poppler.dev}/include/poppler' </del> <ins> --replace '/usr/include/poppler' '${lib.getDev poppler}/include/poppler' </ins> ''; nativeBuildInputs = [ qmake copyDesktopItems wrapQtAppsHook ];

Discussion:
This means nearly all qt6 packages depend on gdb which is 641M on its own. Why is that the case? I can't imagine needing Valgrind for "production" qt6 builds but I have no knowledge in this domain. cc
valgrind was not in my qt6 draft in valgrind was in but valgrind or gdb dont show up in the closure of <details </summaryto compare, </detailsso ... no problem? edit: <details </summary</details
The inputs are only propagated in the output and that's what other packages use. I only came across this because I found gdb in my system closure. showed <the package-quazip -qtbase -valgrind -gdb why did you add valgrind to qt6's propagatedBuildInputs?
It should have been a build time dependency for qtbase. And as it is only referenced in dev output, it should normally not be referenced in system closures, except for issues like Edit, quazip wasn't fixed by that, let me look into it tomorrow.
... so should not be there &rarr; /nix/store/y1m61ayisqmp29ckzi0qq4fp640qfl3l-qtbase-6.4.1-dev/include/QtTest/qtestmouse.h &rarr; /nix/store/y1m61ayisqmp29ckzi0qq4fp640qfl3l-qtbase-6.4.1-dev/include/QtTest/qtestmouse.h &rarr; propagatedBuildInputs &rarr; propagatedBuildInputs also may be relevant: in , are copied to
For the , they should have been in dev output, but and do not have dev output, adding it back should be enough. For , it should be of the same problem as in , maybe we should add that in the hooks of qtbase, or we can fix this ad-hoc.
Change:
replay-sorcery = callPackage ../tools/video/replay-sorcery { }; <ins> recyclarr = callPackage ../tools/video/recyclarr { }; </ins> tsduck = callPackage ../tools/video/tsduck { }; ripasso-cursive = callPackage ../tools/security/ripasso/cursive.nix {

Discussion:
Project description A command-line application that will automatically synchronize recommended settings from the to your Sonarr/Radarr instances. Metadata homepage URL: source URL: license: mit platforms: linux
Change:
swaycons = callPackage ../applications/window-managers/sway/swaycons.nix { }; <ins> swayfx = callPackage ../applications/window-managers/sway/fx.nix { }; </ins> swaylock-fancy = callPackage ../applications/window-managers/sway/lock-fancy.nix { }; swaylock-effects = callPackage ../applications/window-managers/sway/lock-effects.nix { };

Discussion:
Project description SwayFX is a fork of the Sway window manager that includes popular eye-candy features including rounded corners, shadows, dimming (and a WIP blur). Metadata homepage URL: source URL: license: mit platforms: linux, bsd
We already have a working nix flake: , but I am unsure how maintainers would prefer to have SwayFX packaged.
Change:
nativeBuildInputs = kernel.moduleBuildDependencies; hardeningDisable = [ "pic" ]; <del> KERNEL_DIR = "${kernel.dev}/lib/modules/${kernel.modDirVersion}/build"; INSTALL_MOD_PATH = "${out}"; prefix = "${out}"; </del> <ins> makeFlags = kernel.makeFlags ++ [ "KERNEL_DIR=${kernel.dev}/lib/modules/${kernel.modDirVersion}/build" "INSTALL_MOD_PATH=$(out)" "prefix=$(out)" ]; </ins> meta = { description = "Device that allows access to Linux kernel cryptographic drivers";

Discussion:
On an machine with nixpkgs at : I'm trying to bisect this, but I haven't yet found a commit where cross-compilation works. It also fails at these commits: () <!-- 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:
, nodejs , prefetch-yarn-deps , yarn <ins> , testers </ins> }: stdenv.mkDerivation (finalAttrs: {

Discussion:
gitmoji broken. Steps to reproduce the behavior: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --~
I'm not a gitmoji-cli maintainer. Buils fine on master. There's a reason we ask you to run .
Sorry to disturb you. I copy wrong name :cry:
Does help?
Still cannot:
I think be packaged to NixOS to make gitmoji work.
No, the dependency is already installed: exists.
Change:
requirements-parser = callPackage ../development/python-modules/requirements-parser { }; <ins> reretry = callPackage ../development/python-modules/reretry { }; </ins> resampy = callPackage ../development/python-modules/resampy { }; resolvelib = callPackage ../development/python-modules/resolvelib { };

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: a simple Snakefile such as shown below command fails with (truncated) exception message as shown below The command does not fail with an exception This is a known issue that has been fixed in the recent versions of Snakemake Please run and paste the result.