jiebi/CodeConvo huggingface dataset:
Change:
<del> { lib, stdenv, fetchFromGitHub, python3Packages, x11vnc, xrandr, libGL }: </del> <ins> { lib , stdenv , fetchFromGitHub , python3Packages , x11vnc , xrandr , libGL , qt5 }: </ins> python3Packages.buildPythonApplication rec { pname = "virtscreen";

Discussion:
Describe the bug Related to , virtscreen needs to be updated to work with . I've tried to do it myself based on the qutebrowser derivation but haven't been able to figure it out. To Reproduce Steps to reproduce the behavior: I've attempted to fix it like so: with the above patch applied it seems to get further but still doesn't quite work: along with those messages I get a dialog box that says "Failed to load QML": ! I must be missing something here; can someone help me out?
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
I didn't test virtscreen but I have some tips: a look at . That's most of the definition of . You can see, e.g., that is already in . is appropriate here, because Python executables get already wrapped if using . using manually then is probably mainly for controlling exactly when something is wrapped. Python apps are already wrapped, and you probably don't want to wrap the wrapper. You rather amend them by adding to . Have a look at the reference for in the of the manual and at the of simultaneous gnome, qt and python wrappers. An example is . global nipkgs scope uses qt-5.15 by default while python3Packages use qt-5.14. Therefore you either need to use , or you use and use / as a package input.

The second method ensures that you always get the same the current are using. If you then still have problems, feel free to ask again.
I marked this as stale due to inactivity. &rarr;
Bump: virtscreen seems quite useful and currently broken.
Change:
drv="$(runCmd nix "${flakeFlags[@]}" eval --raw "${attr}.drvPath" "${evalArgs[@]}" "${extraBuildFlags[@]}")" if [ -a "$drv" ]; then logVerbose "Running nix with these NIX_SSHOPTS: $SSHOPTS" <del> NIX_SSHOPTS=$SSHOPTS runCmd nix "${flakeFlags[@]}" copy --derivation --to "ssh://$buildHost" "$drv" </del> <ins> NIX_SSHOPTS=$SSHOPTS runCmd nix "${flakeFlags[@]}" copy "${copyFlags[@]}" --derivation --to "ssh://$buildHost" "$drv" </ins> buildHostCmd nix-store -r "$drv" "${buildArgs[@]}" else log "nix eval failed"

Discussion:
says but in flake mode, it uses , not , and the flag has no effect. I guess this is technically as documented, but a bit surprising. Should it pass to as well?
Is there any workaround for now?
Change:
ethtool = callPackage ../tools/misc/ethtool { }; <ins> ets = callPackage ../tools/misc/ets { }; </ins> ettercap = callPackage ../applications/networking/sniffers/ettercap { }; eventstat = callPackage ../os-specific/linux/eventstat { };

Discussion:
Project description is a command output timestamper similar to in moreutils. Primary advantages over are the non-conflicting command name and its handling of progress bars. See "Comparison to moreutils ts" section in source repo for more complete comparison. Metadata homepage URL: source URL: license: mit platforms: linux, darwin
Change:
}) ]; <ins> # PDAL is disabled until https://github.com/qgis/QGIS/pull/54940 # is backported. </ins> cmakeFlags = [ "-DWITH_3D=True" <del> "-DWITH_PDAL=TRUE" </del> <ins> "-DWITH_PDAL=False"  # TODO: re-enable PDAL </ins> "-DENABLE_TESTS=False" ] ++ lib.optional (!withWebKit) "-DWITH_QTWEBKIT=OFF" ++ lib.optional withGrass (let

Discussion:
Steps to reproduce the behavior: with latest master branch is building with the older version of (2.5), because it can't build with the latest version (see: ). Build of started to fail after recent update to version . Notify Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
{ stdenv, lib, fetchFromGitHub, pkgconfig, cmake <del> , dbus, networkmanager, spidermonkey_1_8_5 }: </del> <ins> , dbus, networkmanager, webkitgtk214x, pcre, python2 }: </ins> stdenv.mkDerivation rec { name = "libproxy-${version}";

Discussion:
After nixos-rebuild switch, the network-manager service goes down and immediately segfaults every time it tries to come up again. journalctl for the segfault message or something, anyway, at this point I don't have working network anymore. nixos 17.09pre104870.
Specifically it segfaults because returns a non-zero exit status (saying "No for interface NetworkManager"); the segfault itself appears fixes in their HEAD. I haven't checked whether that makes it actually work, yet, but maybe we could arrange for it to have a in the meantime, whatever that means.
In which commit it was fixed?
Does this also happen in 17.03?
Happens with both the 17.03 tag and the 17.03 channel. Looks like cherry-picking the above commit as a patch for our network-manager lets it work correctly, btw.
also fixed in 17.03:
Change:
{ stdenv, fetchFromGitHub, fetchpatch, makeWrapper <del> , which, nodejs, mkYarnPackage, python2 }: </del> <ins> , which, nodejs, mkYarnPackage, python2, nixosTests }: </ins> mkYarnPackage rec { name = "codimd";

Discussion:
Describe the bug Using sqlite as backend yields the following error How should sqlite be ? Should yarn be ran again? To Reproduce Notify maintainers Metadata Maintainer information:
I did some digging into why this does not work anymore and it seems that this probably did not work for a long time without anyone noticing (including me), even though this should have been caught by the test. The node module is built with using , but on startup I could see that node looks for the module with . Also according to node version 10 does not seem to be officially supported by . Adding.. ..directly after calling for does work, but I am pretty sure that this hack could have weird consequences during runtime :) Building codimd with node version 12, which is officially supported by sqlite3, is probably our best option here and I just successfully ran the test with it. I'll open a PR with the update later this evening. /cc
Working well now, thanks!
Change:
m17n = callPackage ../tools/inputmethods/fcitx-engines/fcitx-m17n { }; mozc = callPackage ../tools/inputmethods/fcitx-engines/fcitx-mozc { <del> inherit (pythonPackages) gyp; protobuf = protobuf.override { stdenv = clangStdenv; }; </del> <ins> python = python2; inherit (python2Packages) gyp; protobuf = protobuf3_2.override { stdenv = clangStdenv; }; </ins> }; table-other = callPackage ../tools/inputmethods/fcitx-engines/fcitx-table-other { };

Discussion:
after a , fcitx cannot switch to mozc only in chromium. journalctl gives me System: (NixOS: , Ubuntu/Fedora: , ...) 09pre106117. (Hummingbird) Nix version: (run ) nix-env (Nix) 1.11.8 Nixpkgs version: (run ) "17.09pre106117." fcitx version: 4.2.9.1 Chromium 57.0.2987.133
Thanks for reporting! Will look into this.
Change:
<ins> { lib , rustPlatform , fetchFromGitHub , pkg-config , wrapGAppsHook , atk , cairo , gdk-pixbuf , glib , gtk3 , pango , gtk-layer-shell }: rustPlatform.buildRustPackage rec { pname = "sway-easyfocus"; version = "unstable-2023-11-05"; src = fetchFromGitHub { owner = "edzdez"; repo = "sway-easyfocus"; rev = "4c70f6728dbfc859e60505f0a7fd82f5a90ed42c"; hash = "sha256-WvYXhf13ZCoa+JAF4bYgi5mI22i9pZLtbIhF1odqaTU="; }; cargoHash = "sha256-9cN0ervcU8JojwG7J250fprbCD2rB9kh9TbRU+wCE/Y="; nativeBuildInputs = [ pkg-config wrapGAppsHook ]; buildInputs = [ atk cairo gdk-pixbuf glib gtk3 gtk-layer-shell pango ]; meta = { description = "A tool to help efficiently focus windows in Sway, inspired by i3-easyfocus"; homepage = "https://github.com/edzdez/sway-easyfocus"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ eclairevoyant ]; mainProgram = "sway-easyfocus"; }; } </ins>

Discussion:
Project description A tool to help efficiently focus windows in Sway inspired by i3-easyfocus: basically you press a key and hints ("q", "w", ...) popup on the titlebars, you can then press "q" to focus the window matching the "q" key. Metadata homepage URL: source URL: license: mit platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
[[package]] name = "rust-ini" <del> version = "0.21.0" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "0d625ed57d8f49af6cfa514c42e1a71fadcff60eb0b1c517ff82fe41aa025b41" </del> <ins> version = "0.21.1" source = "git+https://github.com/zonyitoo/rust-ini?rev=5748ae57a178216a920b88dfac1296618e967447#5748ae57a178216a920b88dfac1296618e967447" </ins> dependencies = [ "cfg-if", "ordered-multimap",

Discussion:
See title. It also may fail to correctly parse comments within such blocks as well, but unsure. a systemd unit in config e.g. to switch configuration (though this might only happen on the second switch, trying to parse existing config?) with Per , this is valid syntax: The value of should thus be parsed to (I may have gotten the spaces wrong there) If applicable, add screenshots to help explain your problem. Patch for failing example test case (may not be perfect): also due to authoring Please run and paste the result. I was running dry-activate to a config using nixpkgs @ Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
thanks for the report! I've looked a little into this so far and switch-to-configuration doesn't actually use that much of the unit file contents, which could be fine considering that systemd's DBus interface exposes almost all of their unit properties as DBus properties. However, since NixOS uses some custom unit properties (think ), these aren't exposed as DBus properties. So instead I've gone the route of adding support for multi-line values in the INI parser used for switch-to-configuration-ng, with the eventual goal of upstreaming this support to that crate. This isn't going to be something that's immediately ready though, I should have a PR for review within the coming days. For now, I would recommend opting out of the switch-to-configuration-ng implementation with the following config until it's fixed:
The problem with INI in general is that there is no standard. The systemd syntax, after all, “is inspired by XDG Desktop Entry Specification .desktop files, which are in turn inspired by Microsoft Windows .ini files”.
Change:
<ins> { lib , stdenv , fetchFromGitLab , docbook-xsl-nons , gtk-doc , meson , ninja , pkg-config , sassc , vala , gobject-introspection , gtk4 , xvfb_run }: stdenv.mkDerivation rec { pname = "libadwaita"; version = "unstable-2021-05-01"; outputs = [ "out" "dev" "devdoc" ]; outputBin = "dev"; src = fetchFromGitLab { domain = "gitlab.gnome.org"; owner = "GNOME"; repo = "libadwaita"; rev = "8d66b987a19979d9d7b85dacc6bad5ce0c8743fe"; sha256 = "0i3wav6jsyi4w4i2r1rad769m5y5s9djj4zqb7dfyh0bad24ba3q"; }; nativeBuildInputs = [ docbook-xsl-nons gtk-doc meson ninja pkg-config sassc vala ]; mesonFlags = [ "-Dgtk_doc=true" ]; buildInputs = [ gobject-introspection gtk4 ]; checkInputs = [ xvfb_run ]; doCheck = true; checkPhase = '' xvfb-run meson test ''; meta = with lib; { description = "Library to help with developing UI for mobile devices using GTK/GNOME"; homepage = "https://gitlab.gnome.org/GNOME/libadwaita"; license = licenses.lgpl21Plus; maintainers = with maintainers; [ dotlambda ]; platforms = platforms.linux; }; } </ins>

Discussion:
Project description Library to help with developing UI for mobile devices using GTK/GNOME Metadata homepage URL: source URL: license: lgpl21Plus platforms: linux cc This is needed for e.g.
Added it to GNOME 41 to do list. Currently, there are no releases.
Change:
mapAliases { "@antora/cli" = pkgs.antora; # Added 2023-05-06 <ins> "@bitwarden/cli" = pkgs.bitwarden-cli; # added 2023-07-25 </ins> "@githubnext/github-copilot-cli" = pkgs.github-copilot-cli; # Added 2023-05-02 "@google/clasp" = pkgs.google-clasp; # Added 2023-05-07 "@nestjs/cli" = pkgs.nest-cli; # Added 2023-05-06 <ins> bitwarden-cli = pkgs.bitwarden-cli; # added 2023-07-25 </ins> eslint_d = pkgs.eslint_d; # Added 2023-05-26 manta = pkgs.node-manta; # Added 2023-05-06 readability-cli = pkgs.readability-cli; # Added 2023-06-12

Discussion:
Steps to reproduce the behavior: Seems like the bitwarden-cli entry disappeared so now I have to use: Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc this is on master
It still exists for me, is there some way I can reproduce this? that aside, this works I'm not submiting this as a PR since we probably shouldn't do this if bitwarden-cli is still intended to be used
Use rather than .
Change:
cmakeFlags = [ "-DGPERF_PRG=${gperf}/bin/gperf" <del> "-DLIBLUV_LIBRARY=${lua.pkgs.luv}/lib/lua/${lua.luaversion}/luv.so" </del> "-DLUA_PRG=${neovimLuaEnv.interpreter}" ] <ins> # FIXME: this is verry messy and strange. ++ optional (!stdenv.isDarwin) "-DLIBLUV_LIBRARY=${lua.pkgs.luv}/lib/lua/${lua.luaversion}/luv.so" ++ optional (stdenv.isDarwin) "-DLIBLUV_LIBRARY=${lua.pkgs.luv.libluv}/lib/lua/${lua.luaversion}/libluv.dylib" </ins> ++ optional doCheck "-DBUSTED_PRG=${neovimLuaEnv}/bin/busted" ++ optional (!lua.pkgs.isLuaJIT) "-DPREFER_LUA=ON" ;

Discussion:
Describe the bug In PR , was as a build input for Neovim. This PR is now live on the channel. On macOS 10.14.6 Neovim now fails to build for me. As best I can tell this is because is failing to build. I'm not certain whether getting building on Darwin will lead to Neovim building successfully on Darwin, but it seems like it's at least a necessary step. ( might also be relevant here.) To Reproduce Steps to reproduce the behavior: Expected behavior builds successfully. Additional context <details<summaryOutput of :</summary<p</p</detailsMetadata Maintainer information:
CCing some relevant folks,
CC
Change:
hash = "sha256-+C/4dDg6WTLpBgkpNyxjthSdqYdaTLC8vG6jG1LNJ7w="; }; <ins> # Remove when this is fixed upstream: # https://gitlab.freedesktop.org/upower/upower/-/issues/214 patches = lib.optional (stdenv.hostPlatform.system == "i686-linux") ./i686-test-remove-battery-check.patch; </ins> strictDeps = true; depsBuildBuild = [

Discussion:
Steps to reproduce the behavior: building KDE on i686 machine. I've been struggling with building KDE for a few recent NixOS versions. I've managed to get it running recently and made 2 MRs that fix it: and . The first one was merged, while the other one wasn't. Creating this as an issue to add as a 22.11 blocker to hopefully get KDE running on i686 in 22.11. Whether it is really a blocker and whether should be merged is up to the dev team to decide of course. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
I think it is time to let go of i686-linux. Keeping it around for wine/steam is fine, but we haven't even been able to build firefox for i686-linux since 2020.
Note we also have an RFC covering this. i686-linux is a tier 3 platform. Tier 3 platforms are non-blocking.
The build log in OP is misleading, as that's from 22.05 and doesn't apply anymore. Here's a link that should work all the time:
The build log I've provided as an example of what's going on there in 22.05, the last stable version, trunk may or may not have some other issues on top of the ones present in 22.05, since it obviously changes all the time. Since I'm commenting on this issue again, can someone elaborate on the existence of binary cache for i686? From what I could gather, even if we get Hydra jobs working correctly, the binary cache still wouldn't exist as it was disabled for the entire i686 architecture?
has everything that's built on Immediately.
I'm sorry, but I keep getting conflicting information on this and all of it got me somewhat confused. What about Nix? If a binary cache for i686 should exist and I'm rebuilding Nixos from a local nixpkgs repo copy set to a revision already built Hydra, for example the latest 22.05 revision from , it should not be building Nix from scratch, right? It should get it from the binary cache?
Yes, you do get it (just tried).
Did you try it on i686? For some reason it's trying to build it from scratch for me.

I got i686-linux version of the attribute on the latest channel. You can download e.g. by
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Now upower fails to build. Personally I don't think we need to support i686 beyond wine and steam because 4GB RAM is to little to run nix comfortable anyway and more and more upstream projects done support it. I would vote for closing this.
. Seems like some kind of Python integer precision issue, I'll make an MR to fix it.
A month ago with no reaction so far. Doesn't look promising. We could patch that test downstream, or disable the specific test, if the test runner supports that.
Change:
patches = [(substituteAll { src = ./0001-Fix-some-paths-for-Nix-build.patch; libipasir = "${libipasir}/lib/${libipasir.libname}"; <del> openssl = openssl.out; </del> <ins> libssl = "${openssl.out}/lib/libssl${stdenv.hostPlatform.extensions.sharedLibrary}"; libcrypto = "${openssl.out}/lib/libcrypto${stdenv.hostPlatform.extensions.sharedLibrary}"; </ins> })]; buildInputs = [

Discussion:
The output from building the target on macOS: Note that if I hack the patch file associated with the derivation to use a extension, it builds fine.
The should be changed to a placeholder and then the placeholder should be replaced with
Change:
sha256 = "1g093g0difnkjmnm91p20issdsxn9ri4c56zzddj5wfrbmhwdfag"; }; <ins> nativeBuildInputs = [ wrapGAppsHook ]; </ins> buildInputs = [ <del> wrapGAppsHook gobject-introspection gnome-desktop libnotify libgnome-keyring pango </del> <ins> gobject-introspection glib-networking gnome-desktop libnotify libgnome-keyring pango </ins> gdk-pixbuf atk webkitgtk ] ++ gstDeps;

Discussion:
Describe the bug Trying to install a GOG game yields just the following window: ! To Reproduce Steps to reproduce the behavior: a GOG game to your library (eg. via the website) -click it in the Lutris interface the "Install" button for GOG "Install" in the installation directory window Expected behavior Presumably, some sort of login popup is supposed to appear, that enables the integration. Screenshots See above. Additional context I'm using due to an unrelated installation issue with Steam, but I suspect that the main attribute suffers from the same issue. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: (Note: Lutris installed from ) Maintainer information:
I believe you can fix this by adding to . will take care of the additional wrapping needed for it.
Having very similar issues with the 'lutris' package on nixos 19.09 I'm trying to use from blizzard and getting the following error: edit: this issue is unrelated and resolved through
Adding to in doesn't seem to have any effect. GOG import still complains about the missing lib.
Change:
}; }; serviceOpts.serviceConfig.ExecStart = '' <del> ${pkgs.prometheus-json-exporter}/bin/prometheus-json-exporter  --port ${toString cfg.port}  ${cfg.url} ${prettyJSON (generateConfig cfg.extraLabels)}  </del> <ins> ${pkgs.prometheus-json-exporter}/bin/json_exporter  --config.file ${prettyJSON (generateConfig cfg.extraLabels)}  --web.listen-address "${cfg.listenAddress}:${toString cfg.port}"  </ins> ${concatStringsSep " n  " cfg.extraFlags} ''; <ins> imports = [ (mkRemovedOptionModule [ "url" ] '' This option was removed. The URL of the rspamd metrics endpoint must now be provided to the exporter by prometheus via the url parameter `target'. In prometheus a scrape URL would look like this: http://some.rspamd-exporter.host:7980/probe?target=http://some.rspamd.host:11334/stat For more information, take a look at the official documentation (https://github.com/prometheus-community/json_exporter) of the json_exporter. '') ({ options.warnings = options.warnings; options.assertions = options.assertions; }) ]; </ins> }

Discussion:
current version: unstable-2017-10-06 desired version: 0.2.0 maintainers:
An option in the service definition to overwrite the package would be nice, too! :smile:
Why is this needed? -options are usually implemented if modifying the package in question with an overlay is a bad idea because it would mean that a lot of leaf-packages would require a rebuild as well. An example for that would be .
Ah, okay.
could you please update this package?
Oh sure, thank you for the ping :)
Change:
sha256 = "0wkyzkhshlax9rvdmn441gv87n9abfr0qqmgs8bkg9kbcjb4bhad"; }; <del> propagatedBuildInputs = [ pyyaml fonttools fontforge ]; </del> <ins> propagatedBuildInputs = [ pyyaml fonttools fontforge setuptools ]; </ins> installPhase = '' runHook preInstall

Discussion:
Steps to reproduce the behavior: on current master, system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Error in logs from : Upstream maintenance status for this is quite questionable, current repo for is archived since 2018: It is a 20 min build on hydra for resulting fonts that are unlikely to ever change. Fix for is pretty easy - just patching distutils part and add to dependencies (or even remove that check altogether because fonttools version in nixpkgs has been over 2.5 for years): But considering it is archived it may be better to either drop both (as nothing else seem to depend on ) or switch to release tarball similar to :
I wouldn't remind emojione being removed if there's a useful alternative. I don't know of a good way to get complete coverage over emojis, and so far I've installed emojione, nerdfonts, noto-fonts, stix-two, and twemoji-color-font, none of which seem to cover any of the other emoji code points completely.
Potentially related: and Potential fix: or
Change:
''; nativeBuildInputs = [ <del> docutils makeWrapper perl pkgconfig python3 which </del> <ins> addOpenGLRunpath docutils makeWrapper perl pkgconfig python3 which </ins> ]; buildInputs = [

Discussion:
Describe the bug In mpv, CUDA-accelerated playback worked a few months ago after landed, but now no longer does. To Reproduce Steps to reproduce the behavior: NixOS master with an NVIDIA card and and observe: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(at): nixpkgs: Maintainer information:
I will see if doing helps