jiebi/CodeConvo huggingface dataset:
Change:
url = "mirror://gnome/sources/libsigc++/${ver_maj}/${name}.tar.xz"; sha256 = "f843d6346260bfcb4426259e314512b99e296e8ca241d771d21ac64f28298d81"; }; <del> patches = [(fetchpatch { url = "https://anonscm.debian.org/cgit/collab-maint/libsigc++-2.0.git/plain" + "/debian/patches/0002-Enforce-c-11-via-pkg-config.patch?id=d451a4d195b1"; sha256 = "19g19473syp2z3kg8vdrli89lm9kcvaqajkqfmdig1vfpkbq0nci"; })]; </del> nativeBuildInputs = [ pkgconfig gnum4 ];

Discussion:
Currently, the derivation for libsigc++ includes a patch that appends to . As a result a C++ project that uses libsigc++-2.0 may be interpreted according to a different standard than expected. For instance, and using libsigc++ via pkg-config effectively downgrades this to C++11. The patch responsible seems to originate from the Debian project . As a side note, I feel pkg-config files are not the place to force a certain c++ standard. a c++ file that conforms to C++14 and higher (but not lower) a nix expression, e.g. that lists gcc, pkgconfig and libsigcxx as buildInputs the following command
Change:
homepage = "https://www.graalvm.org/"; description = "High-Performance Polyglot VM"; license = with licenses; [ upl gpl2Classpath bsd3 ]; <del> maintainers = with maintainers; [ bandresen volth hlolli glittershark ]; </del> <ins> maintainers = with maintainers; [ bandresen volth hlolli glittershark babariviere ]; </ins> platforms = [ "x86_64-linux" "x86_64-darwin" ]; }; };

Discussion:
Describe the bug When running I get the following error message: Looking at the executable the first line is: In fish does not return the name of the current executed file. It appear to work when running this using . Also as comparison look at the file generated via package manager: To Reproduce Steps to reproduce the behavior: Expected behavior should start the server Additional context So with . Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(yogsototh): nixpkgs: Maintainer information:
Hey this version is pretty outdated, could you try latest which is using graalvm binary?
Also the brew forumla you saw is outdated as well, the updated is
You are probably using the stable channel 20.09 channel, that should explain why you're still using the with JVM instead of GraalVM compiled binary. Switch to the unstable channel instead. I am not sure if it will work though since this package was never tested with macOS (and the fact that this package is broken in Hydra: ).
I just tested with latest master commit And if failed to build: I think the main bug is probably fixed. This is just another one :). This is late for me. I'll probably give it a look another day. Thanks for checking!
I think all GraalVM's packages build with Clojure are broken in macOS simply by the lack of people that has macOS systems to test/fix them. If you can fix this, a PR would be welcome :slightlysmilingface: .
Agreed If you have mac, using the homebrew official clojure-lsp formula should work as well: https://clojure-
Change:
{ description = "WireGuard Peer - ${interfaceName} - ${peer.publicKey}"; requires = [ "wireguard-${interfaceName}.service" ]; <del> after = [ "wireguard-${interfaceName}.service" ]; wantedBy = [ "multi-user.target" "wireguard-${interfaceName}.service" ]; </del> <ins> wants = [ "network-online.target" ]; after = [ "wireguard-${interfaceName}.service" "network-online.target" ]; wantedBy = [ "wireguard-${interfaceName}.service" ]; </ins> environment.DEVICE = interfaceName; environment.WG_ENDPOINT_RESOLUTION_RETRIES = "infinity"; path = with pkgs; [ iproute2 wireguard-tools ];

Discussion:
Hello, Current wireguard-wgXX.service dependencies are as follows: Now it depends on network- which I believe is wrong. The following is correct: These settings allow wgXX interface to be brought up just like others. The other services that depend on or network- can now use wgXX interfaces. Similarly the following in the PeerUnit can be altered by the following. evrim.
I have the same issue. My workaround is let the service using wireguard interface depend on the wireguard service.
Right, but then we'll have network-, network-, network- ...
Opened . You may be interested.
Change:
nativeBuildInputs = [ wrapQtAppsHook wrapGAppsHook asciidoc docbook_xml_dtd_45 docbook_xsl libxml2 libxslt <del> ]; </del> <ins> ] ++ lib.optional isQt6 python3Packages.pygments; </ins> propagatedBuildInputs = with python3Packages; ([ pyyaml backendPackage jinja2 pygments

Discussion:
This error occurs when trying to open the help page. ! Steps to reproduce the behavior: Launch qutebrowser-qt6 Run :help Loads help page (since qt6 build, although not a maintainer) Note this doesn't happen for the qt5 build.
I probably should have myself as a maintainer. Seems it is not all urls since I can still load , the help is gone. Perhaps it needs to be explicitly built like the man page.
Change:
, jackSupport ? false , fetchpatch , removeReferencesTo <ins> , chromecastSupport ? true, protobuf, libmicrodns </ins> }: <ins> # chromecastSupport requires TCP port 8010 to be open for it to work. # If your firewall is enabled, make sure to have something like: #   networking.firewall.allowedTCPPorts = [ 8010 ]; </ins> with stdenv.lib; assert (withQt5 -> qtbase != null && qtsvg != null && qtx11extras != null);

Discussion:
The current vlc derivation does not include chromecast support. I believe we need to add the flags during the configuration step to enable it by default, which I think is a reasonable thing to do. I tried to do the minimal change myself, but looks like we need some new dependencies that don't exist in nixpkg yet: I'm still fairly new so it will take some learning to figure out what needs to be done to package protobuf-lite (not sure I'll get around to it anytime soon). If anyone else is into making these changes, it would be much appreciated. Or please let me know if I'm off-track here and there's a better way to do this.
You're on the right track. This should work:
Ah, now it builds, and I can see the relevant chromecast features, but it's still not finding the chromecast. Thank you! Sounds like that happens when microdns is not available. I tried adding nssmdns to the derivation but that didn't do the trick. is enabled. Hmmmm.
FWIW (mostly because I like linking things together), but sounds like you're past what is useful from that :). I frequently find chromecast programs on NixOS don't work... especially scanning support... with the firewall enabled. . Should only need mdns support for discovery/scanning, I think :).
Yea I did see that. I don't think it's the firewall, as google-chrome chromecasts fine. Even VLC via flatpak manages to connect to the chromecast (but fails to encode due to some other error). I believe mdns is used to find the chromecast automagically.
Make sure avahi is running and that mdns is set in resolvconf
Avahi is running and nssmdns is enabled, if that's what you mean. Is it working for you? Reading an older VLC PR: Sounds like we need VLC's own libmicrodns packaged before this will work: Edit: Indeed building with :
I managed to package up libmicrodns and it's working now! I'll clean up and send a PR. :) Thanks for the help everyone.
Change:
name = "libnl-${version}"; src = fetchFromGitHub { <del> sha256 = "1078sbfgcb6ijal9af6lv26sy233wq14afyrc4bkdbnfl0zgsbwi"; rev = "libnl3_2_23"; </del> <ins> sha256 = "0y8fcb1bfbdvxgckq5p6l4jzx0kvv3g11svy6d5v3i6zy9kkq8wh"; rev = "libnl3_2_29"; </ins> repo = "libnl"; owner = "thom311"; };

Discussion:
cc:
I think this started failing when we updated to (/cc In 3.2.28, was defined here: Also (potentially) suspect:
Looks like the nl update was accidentally a downgrade.
I'll prepare a patch for libnl.
Yeah, just noticed, hehe. Thanks!
Oops, ignore the first PR, picked the wrong branch.
Sorry, y'all...! :o
I can't blame you for a typo, we're all human
Change:
cmakeFlags = [ (lib.cmakeBool "USE_SYSTEM_OPENXR" true) (lib.cmakeBool "USE_SYSTEM_GLM" true) <del> (lib.cmakeFeature "CMAKE_CXX_FLAGS" "-DGLM_ENABLE_EXPERIMENTAL") # debug logging macros cause format-security warnings (lib.cmakeFeature "CMAKE_CXX_FLAGS" "-Wno-error=format-security") </del> ]; <ins> # NOTE: `cmakeFlags` will get later tokenized by bash and there is no way # of inserting a flag value with a space in it (inserting `"` or `'` won't help). # https://discourse.nixos.org/t/cmakeflags-and-spaces-in-option-values/20170/2 preConfigure = '' cmakeFlagsArray+=( "-DCMAKE_CXX_FLAGS=-DGLM_ENABLE_EXPERIMENTAL -Wno-error=format-security" ) ''; </ins> installPhase = '' runHook preInstall mkdir -p $out/lib/opencomposite

Discussion:
Hiii :) Steps to reproduce the behavior: opencomposite Full log: Add any other context about the problem here. Stuff like this shows up many times on the log, for many different extensions. Seems to be the cause: Package was updated on <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
{ stdenv, lib, fetchFromGitHub <del> , qmake, qtwebsockets, qtwebengine, wrapQtAppsHook, openconnect </del> <ins> , cmake, qtwebsockets, qtwebengine, wrapQtAppsHook, openconnect </ins> }: stdenv.mkDerivation rec {

Discussion:
globalprotect-openconnect has latest version 1.3.4 on but when I try to install it I got version 1.2.5 Steps to reproduce the behavior: nix-env -iA nixos.globalprotect-openconnect Install latest version ! Please run and paste the result. That my first time reporting issues, so please tell me if any additional info need to be provided.
This is because of from It didn't actually update the git commit hash, it just changed the hash away from base32 encoding. :(
This is the second time I've seen do this ( was the first). CC who merged , as an FYI.
is the upstream issue report for the false updates from
Change:
''; })) <ins> (patchExtension "gtk4-ding@smedius.gitlab.com" (old: { patches = [ (substituteAll { inherit gjs util-linux xdg-utils; util_linux = util-linux; xdg_utils = xdg-utils; src = ./extensionOverridesPatches/gtk4-ding_at_smedius.gitlab.com.patch; nautilus_gsettings_path = "${glib.getSchemaPath gnome.nautilus}"; }) ]; })) </ins> (patchExtension "pano@elhan.io" (old: { patches = [ (substituteAll {

Discussion:
No GNOME Shell Extension can enable desktop icons. . to enable desktop icons. Should be able to enable desktop icons in GNOME Shell, one way or another. About the time of NixOS 20.03, i was still able to have desktop icons using some old version of extension. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
I can confirm this. The systemd journal shows (once every second):
This probably requires patching all paths referencing other libraries or binaries. Which of those extensions shall I have a look at first?
, maybe the one that is easier to fix? I did not have an opportunity to test , so i cannot decide between the two. Thanks!
Haven't had the opportunity to check out any of them so I also cannot decide. Any one of them would be fine for me, so I guess start with the one that is easier to fix (if there is a difference). If I can be of any help let me know.
WIP: I have the following override and the following patch: But I somehow can't get it to find nautilus. It will always end with a null exception while trying to access nautilus stuff (can't copy the stack trace out of the testing VM, sorry).
still not solved :
Made a PR for , a similar technique can be used on the other desktop icon extensions. Would like if someone could test that everything's working. Note the schema path bit, that was causing . For any path you cannot directly list with you most likely need to do the thing (or otherwise find a way to make it find the schema source).
Change:
postInstall = '' substituteInPlace $out/lib/pkgconfig/${pname}.pc  <del> --replace "''${prefix}" "" </del> <ins> --replace "''${prefix}/" "" </ins> ''; meta = with lib; {

Discussion:
tblite is unusable in python at the moment, failing with I think this is due to incorrect pkgconfig setups - look at which is correct and outputs vs which is missing the trailing Which results in a pkgconfig of Steps to reproduce the behavior: a nix environment with the python interpreter, run failure A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Please run and paste the result.
i'm having the exact same issue as well :'(
Change:
install -m644 -Dt $out/${pname} plugin.yaml cp -r scripts/* $out/${pname}/scripts wrapProgram $out/${pname}/scripts/run.sh  <del> --prefix PATH : ${lib.makeBinPath [ coreutils findutils getopt gnugrep gnused sops vault ]} </del> <ins> --prefix PATH : ${lib.makeBinPath [ coreutils findutils getopt gnugrep gnused sops ]} </ins> runHook postInstall '';

Discussion:
Updating my falke to latest nixpkgs unstable gives an error that vault is non-free. But my package doesn't use or need vault. My package at has: This gives the error: If I comment out the it works. Steps to reproduce the behavior: to use nixpkgs-unstable instead of nixpkgs 23.11 Should build without errors. As above. ` Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
helm-secrets depends on vault
What happened to vault? It use to be open source I thought. Did the license change?
Does helm-secrets really depend on vault? From the it says: Which seems to indicate that it should be able to use any secret manager, not just vault.
the vault license change, which sparked quite the outrage. you ask a question and follow with the answer, that's both rare and impressive ^^'' You can see it here: I suggest you follow the recommendation and accept the new license for vault. If you dont need it, you can remove support for it as well from helm-secrets (but will require some nix skills though you can search the web for plenty of examples)
How about switching the dependency from vault to OpenBAO - would that be possible?
Heh, I didn't realize LF forked Vault too. :popcorn: It's certainly possible, but might have unintended side effects for Nix users. (I realize how annoying that might sound, given your recent experience.) By default, helm-secrets supports and . After a quick glance, it looks like both sops and vals use the Vault Go library, so maybe we don't even need at runtime anyway... I wonder if sops and vals will have to alter their licenses... Edit: It seems the is still .
I've just tried a modified helm-secrets derivation, removing all references to , against a repo that uses helm-secrets (with AWS KMS backend) and it worked fine. I then switched the config to point use a Vault backend, and that also worked. Note that I used to get a token, but assuming exists or the env var is set somehow, it seems doesn't need a binary at runtime at all. So, I suggest we drop the dependency.

might you be able to test It Works on my Machine, and I'm fairly confident, but I'd love some additional verification.
It seems to work OK on my system, so far. Don't have a good test case for vault though. Will think about additional ways to test this.
Change:
, dpkg , glib , gtk3 <ins> , wrapGAppsHook </ins> , libkrb5 , libsecret , nss

Discussion:
crashes when attempting to open any file dialog, such as saving an attachment. mailspring the menu bar select Edit Install Theme... Expected behavior A "Choose Directory" file dialog should open Actual Behaviour Mailspring crashes with the following output: Adding to resolves the issue: I have mailspring to in my system's file. Notify maintainers Metadata Results of : system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
I tried installing from unstable but to no avail.
This package is missing in . See the gnome section of the nixpkgs manual
Change:
url = "https://www.antigrain.com/${pname}-${version}.tar.gz"; sha256 = "07wii4i824vy9qsvjsgqxppgqmfdxq0xa87i5yk53fijriadq7mb"; }; <del> nativeBuildInputs = [ pkg-config ]; buildInputs = [ autoconf automake libtool freetype SDL libX11 ]; </del> <ins> nativeBuildInputs = [ pkg-config autoconf automake libtool ]; buildInputs = [ freetype SDL ] ++ lib.optionals stdenv.isLinux [ libX11 ]; </ins> postPatch = '' substituteInPlace include/agg_renderer_outline_aa.h 

Discussion:
Project description Superset of package , which isnt actively developed now. Metadata homepage URL: https://lite- source URL: license: mit platforms: linux, darwin
Change:
buildPythonApplication rec { pname = "legendary-gl"; # Name in pypi <del> version = "0.20.33"; </del> <ins> version = "unstable-2023-10-14"; </ins> src = fetchFromGitHub { owner = "derrod"; repo = "legendary"; <del> rev = "refs/tags/${version}"; sha256 = "sha256-fEQUChkxrKV2IkFGORUolZE2qTzA10Xxogjl5Va4TcE="; </del> <ins> rev = "450784283dd49152dda6322db2fb2ef33e7c382e"; sha256 = "sha256-iwIaxD35tkOX6NX1SVNmN2OQACwaX/C4xnfgT5YcUvg="; </ins> }; propagatedBuildInputs = [

Discussion:
Heroic Launcher while trying to install a game from gog will download it, but won't install it. You can see downloaded installer inside your directory. After "installation", launcher will say on the game's details screen that It should install. ! You can't just use the gog installer like in a normal linux distribution: So you need to use steam-run to install it. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --heroic-launcher: 2.9.2 - unstable nixpkgs
This sounds exactly like a bug I encountered in a previous version of Heroic, but they have since fixed it, and I have not run into it on 2.9.2. Could you please attach the Heroic log file from right after trying to install the game? It's accessible via the sidebar Settings-Log.
<details</details
It looks like it successfully installs, going by that log. I seem to vaguely recall now having some issues with my GOG library in Heroic 2.9.2, and I eventually removed (with Heroic closed) and logged in to GOG through Heroic again, and it's been behaving since. You might try that, otherwise I don't see anything indicating this would be an issue specific to the Heroic package, so I think it would be appropriate to go to upstream's support channel, which is .
I will try moving to nixpkgs unstable and see if it was an issue of using stable and unstable in the same time. It should not, but maybe it is. Thank you for your help PS. I tried different game and the situation is still the same.
I found that heroic needs unzip to be installed to extract the gog linux installers. When I have somewhere in my installed packages (home or system), it just works. Probably it will have to be to the heroic wrapper.
Could you please try changing in your Nix config to the following and see if that fixes your problem?
By using: Everything started to work.
Change:
stdenv.mkDerivation rec { pname = "jetty"; <del> version = "9.4.35.v20201120"; </del> <ins> version = "9.4.36.v20210114"; </ins> src = fetchurl { url = "https://repo1.maven.org/maven2/org/eclipse/jetty/jetty-distribution/${version}/jetty-distribution-${version}.tar.gz"; <del> name = "jetty-distribution-${version}.tar.gz"; sha256 = "1cpdrqz6wi7fd228lh4ijs82jq51qr5aym6vff464w3y2sd0jbav"; </del> <ins> sha256 = "1bsqxzjcdgdg2qdgc64pvrimkn9j2di2s3prlgdpbwi566744q54"; </ins> }; <del> phases = [ "unpackPhase" "installPhase" ]; </del> <ins> dontBuild = true; </ins> installPhase = '' mkdir -p $out

Discussion:
, CVSSv3=7.8 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: .
Change:
<del> { lib , buildGoModule , fetchFromGitHub }: buildGoModule rec { pname = "kubei"; version = "1.0.12"; src = fetchFromGitHub { owner = "Portshift"; repo = pname; rev = version; sha256 = "sha256-QUPRw8fQ6ahBLZox6m4+feYIrcgDnCTe72nMF8iAV+Y="; }; vendorSha256 = "sha256-uWDQf0zcTTPBthK60bmGJBP/m+yUu5PvYAbwyd0dcWE="; meta = with lib; { description = "Kubernetes runtime scanner"; longDescription = '' Kubei is a vulnerabilities scanning and CIS Docker benchmark tool that allows users to get an accurate and immediate risk assessment of their kubernetes clusters. Kubei scans all images that are being used in a Kubernetes cluster, including images of application pods and system pods. ''; homepage = "https://github.com/Portshift/kubei"; license = with licenses; [ asl20 ]; maintainers = with maintainers; [ fab ]; }; } </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: kubei <!-- 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: 1.0.12 desired version: 2.9.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:
, curl , coreutils , cacert <ins> , libjpeg </ins> , useChineseVersion ? false }: let

Discussion:
can not use export to pdf function Steps to reproduce the behavior: a doc/docx file to pdf successfully export to pdf ! There might be a explain: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Reproducible on my side. Will try to investigate and push a pr if feasible
pretty sure we already handle the dependency: as mentioned in the thread, can you try running followed by (or applicable command) to confirm thi actual cause?
I have tried to run with , here is the log: Seems like there is nothing to do about , maybe something else is broken in otherwise.
Never mind. When I tried to create link to on somewhere and running with , PDF export working like a charm. Maybe the workaround is not working as expected.
Can you try this pr and see whether this pr fix the issue for you?
crash
Fixed in latest push Feel free to drop a message if further issues appear.
ok, it works fine for me
Change:
<ins> { lib , rustPlatform , fetchFromGitHub , pkg-config , wayland , ffmpeg }: rustPlatform.buildRustPackage rec { pname = "wl-screenrec"; version = "unstable-2023-05-31"; src = fetchFromGitHub { owner = "russelltg"; repo = pname; rev = "fc918f7898900c1882c6f64c96ed2de8cb9a6300"; hash = "sha256-P/JELiw0qGcwLFgNPccN/uetNy8CNCJdlCLhgq0h4sc="; }; cargoHash = "sha256-r9zmAiLiAntHcb5W/WKmKbVP9c9+15ElIWtHkks0wig="; nativeBuildInputs = [ pkg-config rustPlatform.bindgenHook ]; buildInputs = [ wayland ffmpeg ]; meta = with lib; { description = "High performance wlroots screen recording, featuring hardware encoding"; homepage = "https://github.com/russelltg/wl-screenrec"; license = licenses.asl20; platforms = platforms.linux; maintainers = with maintainers; [ colemickens ]; }; } </ins>

Discussion:
Project description offers high performance wlroots screen recording, featuring hardware encoding. Metadata homepage URL: source URL: license: gpl2+ platforms: linux
made this a couple weeks ago, not sure if it works well, but here if anyone wants to work on top of this
that's pretty cool, I'll try when I have some time
Here's the correct way of packaging this:
Oh bindgen hook is a thing?
do you want to PR it? I don't want to just yoink and submit it if you want to.
I can but I don't care if you do it, it was basically all automated anyway. Would you like me to add you as maintainer?
sure, that's fine, I'm going to put it in nixpkgs-wayland so I can keep an eye on it anyway.