jiebi/CodeConvo huggingface dataset:
Change:
{src = pkgs.writeText "sudoers-in" cfg.configFile; } # Make sure that the sudoers file is syntactically valid. # (currently disabled - NIXOS-66) <del> "${pkgs.sudoWithVisudo}/sbin/visudo -f $src -c && </del> <ins> "${pkgs.sudo}/sbin/visudo -f $src -c && </ins> cp $src $out"; target = "sudoers"; mode = "0440";

Discussion:
The installer test was broken by the change mentioned below, along with the change which adds a keepVisudo option to the package build of sudo. The installer tests do not have network connectivity, therefore requiring that all packages be located on the iso from which they are being installed. The problem is that this patch forces one of the installed sudo derivations to differ from the default, forcing nix to attempt a rebuild of the derivation and subsequently failing to download the sudo sources. We need to either bundle both versions of the sudo derivation or simply remove the keepVisudo option and always keep it Is it a problem to keep visudo around for the default sudo derivation? Broken in:
Change:
criu = callPackage ../os-specific/linux/criu { }; <ins> cryptomator = callPackage ../tools/security/cryptomator { }; </ins> cryptsetup = callPackage ../os-specific/linux/cryptsetup { }; cramfsprogs = callPackage ../os-specific/linux/cramfsprogs { };

Discussion:
Project description Cryptomator is an application providing client-side encryption for cloud storage. Metadata homepage URL: source URL: license: GPLv3 platforms: linux, darwin
Source URL:
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 .
This is still relevant to me. There is currently no way to get transparent encryption on any cloud-drive.
guys, whoever is interested in cryptomator testing/reviewing are welcome: we absolutely need it for darwin platform as well?
Let's first get it merged for linux, we can then base on that and check if we can get darwin working too.
Change:
]; postInstall = '' <del> install -Dm444 psst-gui/assets/logo_512.png $out/share/icons/${pname}.png </del> <ins> mkdir -pv $out/share/icons/hicolor/512x512/apps install -Dm444 psst-gui/assets/logo_512.png $out/share/icons/hicolor/512x512/apps/${pname}.png mkdir -pv $out/share/applications ln -s ${desktopItem}/share/applications/* $out/share/applications </ins> ''; meta = with lib; {

Discussion:
I'm unable to launch from my application launcher due to it missing the  entry & Please run and paste the result.
Change:
tqdm ]; <ins> preCheck = '' export HOME=$(mktemp -d) ''; pythonRelaxDeps = [ "protobuf" ]; </ins> disabledTestPaths = [ # Tests that try to get chatty over sockets or spin up servers, not possible in the nix build environment. "tests/unit_tests/integrations/test_keras.py"

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags: -
fixed in
Change:
sha256 = "sha256-uVFuwtsmR/9epoqot3lJ/5v5OuJjuRjL7FJF7oXNDzU="; }; <ins> nativeBuildInputs = [ wrapGAppsNoGuiHook gobject-introspection ]; </ins> propagatedBuildInputs = with python3Packages; [ dbus-python pygobject3 ]; checkInputs = with python3Packages; [ dbus-python ];

Discussion:
Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
version = "0.1.1"; }; oxidized = { <del> dependencies = ["asetus" "net-ssh" "net-telnet" "rugged" "slop"]; </del> <ins> dependencies = ["asetus" "git" "net-ssh" "net-telnet" "rugged" "slop"]; </ins> groups = ["default"]; platforms = []; source = {

Discussion:
Describe the bug Oxidized crashes on startup when using gitcrypt as output method. It works with any other output method (including git). I think this is because there is a missing dependency (gem git). This is not triggered when using output git because it relies on rugged (which is in the ) rather than git. To Reproduce Steps to reproduce the behavior: oxidized to use gitcrypt, e.g.: oxidized Crash file says: Expected behavior Oxidized should start normally. Additional context Metadata
Change:
tlc = callPackage ../development/coq-modules/tlc {}; topology = callPackage ../development/coq-modules/topology {}; trakt = callPackage ../development/coq-modules/trakt {}; <ins> vcfloat = callPackage ../development/coq-modules/vcfloat {}; </ins> Velisarios = callPackage ../development/coq-modules/Velisarios {}; Verdi = callPackage ../development/coq-modules/Verdi {}; VST = callPackage ../development/coq-modules/VST ((lib.optionalAttrs

Discussion:
Project description VCFloat: A Unified Coq Framework for Verifying C Programs with Floating-Point Computations Metadata homepage URL: source URL: license: LGPL platforms: <uncertain limitations here
Change:
{ lib , stdenv , fetchFromGitHub <del> , makeWrapper </del> <ins> , wrapGAppsHook </ins> , makeDesktopItem , copyDesktopItems , unzip , xdg-utils <ins> , gtk3 </ins> , jdk , gradle , perl

Discussion:
File open dialog results in crash due to missing GSettings schema path. This seems similar to Steps to reproduce the behavior: on "Open library" icon File open dialog opens. Please run and paste the result.
I can't reproduce it on a clean NixOS VM.
to reproduce these issues do to empty XDGDATADIRS
Great! Now I can reproduce it without a VM.
Please test
Thanks for the quick fix, works for me.
Would be nice if this could be backported (let's try with issue label on the PR again after it is merged, if you would be so kind to 22.05 as well.
I'll add the label. :ok_hand:
I am not sure whether this label should only be applied after the PR is successfully merged, i.e. only then does the action trigger, but let's see about that assumption.
Unfornately there is confilctions so the auto backport failed.
Thanks, yes, already saw it. Will open a manual backport PR.
Change:
Enabled Fcitx5 addons. ''; }; <ins> waylandFrontend = mkOption { type = types.bool; default = false; description = lib.mdDoc '' Use the Wayland input method frontend. See [Using Fcitx 5 on Wayland](https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland). ''; }; </ins> quickPhrase = mkOption { type = with types; attrsOf str; default = { };

Discussion:
Upon login, Fcitx5 presents a popup notification telling me to unset and . This is specifically in the Plasma 6 (alpha) Wayland session. The environment variables appear to be set in the Fcitx5 NixOS module. also for ibus. I'm not sure if the other IMEs are supposed to work on Wayland at all. (nixos-unstable with Plasma 6 alpha from nix-community/kde2nix)
It's mostly impossible to detect if the user is currently using the plasma wayland session (unless with some custom profile scripts). Maybe we should add an option allowing disabling the automatic configuration of these environment variables.
FWIW Plasma 6 defaults the "plasma" session to wayland. The X11 session is renamed to "plasmax11". At least Plasma has some startup script generated by nix, I think at that point it might be known whether it is Wayland or not?
But users can still choose the session to use upon login right? However the current fcitx5 nixos module unconditionally sets these variables, without a runtime detection mechanism.
Is that possible to detect that at runtime, with something like ?
Well that's the part. But I'd rather let the users decide than trying to act smart. There are both pros and cons of using the immodules or not.
That's why I pointed out the startup script from the plasma module.
I mean it's not a must (or even should, IMO) that you unset and for the wayland session. The input method story is very complicated, with different applications/compositors/input methods supporting different protocols of varying compatibility and functionality. Setting these variables by default in most cases, won't worsen the situation. You may read https://fcitx- for some background.
Hmm, I see. Maybe they could be set with so users or other modules can easily override them?
Reasonable, but empty string and unset do have different meaning regarding these variables. So I think a blanket option to unset then entirely is more desirable.
Is there any temporary workaround? I can't find out how to unset it, I don't think there is way besides making it blank which might work?

I am confused as to how to get IME to work on Hyprland or Wayland at all though, if I can't get Japanese IME to work it's a complete deal breaker for me personally Edit, this worked for me personally. Using Fcitx on GTK crashes my Hyprland, but seems the QT one works fine? I am super confused now. But glad to see that IME support seems to be baked into Wayland itself somewhat I just hope it makes it work just as well as Windows in the far future: Also you will need this at the top of your file where you set it
If hyprland crashes, that's a hyprland issue, the fcitx5 gtk immodule works fine on most other platforms, such as sway.
Change:
manages Xen and LXC (linux containers). ''; license = licenses.gpl2; <ins> # exclude Darwin since libvirt-glib currently doesn't build there platforms = platforms.linux; </ins> maintainers = with maintainers; [ qknight offline fpletz ]; }; }

Discussion:
Since , virtmanager no longer depends on pygtk; it is still listed in the dependencies though. Actually, most of the propagated dependencies are not mentioned anywhere in the virt-manager source code.
Change:
net-telnet (0.1.1) oxidized (0.26.3) asetus (~> 0.1) <ins> git (~> 1) </ins> net-ssh (~> 5) net-telnet (~> 0.1.1) rugged (~> 0.21, >= 0.21.4)

Discussion:
Describe the bug Oxidized crashes on startup when using gitcrypt as output method. It works with any other output method (including git). I think this is because there is a missing dependency (gem git). This is not triggered when using output git because it relies on rugged (which is in the ) rather than git. To Reproduce Steps to reproduce the behavior: oxidized to use gitcrypt, e.g.: oxidized Crash file says: Expected behavior Oxidized should start normally. Additional context Metadata
Change:
run jobs as if they were running on the hosted CirleCI application. ''; maintainers = with maintainers; [ synthetica ]; <del> platforms = platforms.unix; </del> license = licenses.mit; homepage = https://circleci.com/; };

Discussion:
The package appears to be quite out of date. I could use some help in updating it. Here is the version in nixpkgs: Here is my attempt at updating it: And here is the error message I get when I try to build: Any advice?
Relaying what I said on IRC: If you want to update it in nixpkgs you should edit the expression in nixpkgs directly And it seems that the package didn't have any dependencies before, so updating just the source won't work, you also need to make its dependencies available If the package has a file, check out kalbasit's blog on how to use buildGoModule for this: Otherwise check
Thank you so much,
Change:
sed -i "s:${gnustep.make}:$out:g" $out/share/GNUstep/GNUstep.conf # Link in GNUstep base <del> ${lndir}/bin/lndir ${gnustep.base}/lib/GNUstep/ $out/lib/GNUstep/ </del> <ins> ${lndir}/bin/lndir ${lib.getLib gnustep.base}/lib/GNUstep/ $out/lib/GNUstep/ </ins> # Link in sope ${lndir}/bin/lndir ${sope}/ $out/

Discussion:
As the subject says on latest unstable.
I marked this as stale due to inactivity. &rarr;
These dependencies are also creeping into , so for example , a simple CLI pulls in 1.4 gigs of dependencies.
Preemptive anti stale-bot strike. Pinging people contributing to gnustep-base package:
I was about to report the same bug; the application also pulls in unnecessary stuff via and :
It's not unar as such, but instead that pulls in a bunch of stuff that doesn't belong there. I'm wondering if maybe or have some insights?
Fix in
Change:
stdenv.mkDerivation rec { pname = "ncnn"; <del> version = "20231027"; </del> <ins> version = "20240102"; </ins> src = fetchFromGitHub { owner = "Tencent"; repo = pname; rev = version; <del> sha256 = "sha256-ak/5QTOptg5M2I+3olnrBK6JZ01haIE6oh+sagEboAc="; </del> <ins> hash = "sha256-kk70oLY+2QJOkyYq10whLRMxBuibQMWMOBA9dcbKf/I="; </ins> }; patches = [

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: build and upgrade successfully. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
failed to build, may be maintaining this dependency
You can exclude this package until the build is fixed
Thanks a lot for getting back to me so quickly and for your helpful suggestion!
Change:
npmRebuildFlags = [ "|| true" ]; makeCacheWritable = true; <del> npmDepsHash = "sha256-JeJjjrCfJMuxP9sVVkKJQ7bRCGu0jbGfiw78jS0r2Sg="; </del> <ins> npmDepsHash = "sha256-H2f6xdAa7fNETbQhIv+InCB7+O4nq0bx+RILjGjqXdY="; </ins> npmFlags = [ "--legacy-peer-deps" ]; npmBuildScript = if buildWebExtension then "buildWeb" else "build"; npmBuildFlags = [ "--" "--standalone" "--disable-updater" ];

Discussion:
Vesktop opens up to a white screen. It cannot update from tray to latest version. I tried completely removing config files from Vencord but it doesn't change anything. Running Vesktop with flag --disable-gpu makes the Vesktop stuck at loading Steps to reproduce the behavior: Vesktop Launching Vesktop should open up the app normally ! Kernel: 6.5.7-xanmod1 Gpu: AMD (mesa 23.1.7)
vencorddesktop command doesn't output any logs. When doing update from the gui, it doesn't show anything. Only time it shows something is when i try updating from tray icon. The output is the following:
This is a problem with Vencord. It is currently broken with the curren versions of Discord (including the web app) We have to wait for upstream to fix these issues and release a new version of vencord
Alright, thank you for the fast response! Cheers
I encountered the same issue, and can confirm it is fixed when the system version of vencord is 1.6.0.
Change:
type = types.bool; }; <ins> enableLsColors = mkOption { default = true; description = '' Enable extra colors in directory listings. ''; type = types.bool; }; </ins> }; };

Discussion:
As in the title. At the moment ls colors orphaned symbolic links just as normal symbolic links per default. As symbolic links are really ubiquitous in nix or nixos, is it a good a idea to change that default setting? (From reading the comments in the source, the idea is not following symbolic links, if it isn't really necessary, to avoid the work. Coloring orphaned links different per default, all the effort not to follow symbolic links, wouldn't be used usually.) It's a one line change, I could happily provide a pr (or is it mr) for. In a directory without the files and . ln -s a b LS_COLORS="" ls --color=always
I like this idea. After playing with it a little bit I went ahead and created a PR, since I think it deserves more than a 1-liner. There are bound to be those who want it toggleable.
Change:
# Hardcode paths used by Flatpak itself. (substituteAll { src = ./fix-paths.patch; <del> p11kit = "${p11-kit.dev}/bin/p11-kit"; </del> <ins> p11kit = "${p11-kit.bin}/bin/p11-kit"; </ins> }) # Adapt paths exposed to sandbox for NixOS.

Discussion:
Describe the bug does not provide the binary, while I would expect it to. To Reproduce Steps to reproduce the behavior: in Expected behavior (and ) are installed for operator usage of p11-kit. Screenshots See step 3. Additional context It turns out the binaries are present when I do . Debian ships the binaries as part of the base non-dev package. RHEL/CentOS ship the binary as part of and have separated out into . Notify maintainers (based on git history, there is no meta.maintainers for p11-kit) Metadata Please run and paste the result. Maintainer information:
p11-kit is a library as well, so it makes sense to have headers, library, and binaries in separate outputs. I think we can fixed this by setting: in the derivation.
If we do this we need to fix it in flatpak's patch to hardcode the path to the p11-kit binary.
I marked this as stale due to inactivity. &rarr;
Any updates on this?
I marked this as stale due to inactivity. &rarr;
Change:
# Inject custom settings machine.succeed("mkdir -p /root/.config/MuseScore/") machine.succeed( <del> "cp ${customMuseScoreConfig} /root/.config/MuseScore/MuseScore3.ini" </del> <ins> "cp ${customMuseScoreConfig} /root/.config/MuseScore/MuseScore4.ini" </ins> ) # Start MuseScore window machine.execute("DISPLAY=:0.0 mscore >&2 &") # Wait until MuseScore has launched <del> machine.wait_for_window("MuseScore") </del> <ins> machine.wait_for_window("MuseScore 4") </ins> # Wait until the window has completely initialised <del> machine.wait_for_text("MuseScore") </del> <ins> machine.wait_for_text("MuseScore 4") machine.screenshot("MuseScore0") # Create a new score machine.send_key("ctrl-n") # Wait until the creation wizard appears machine.wait_for_window("New score") machine.screenshot("MuseScore1") machine.send_key("tab") machine.send_key("tab") machine.send_key("tab") machine.send_key("tab") machine.send_key("right") machine.send_key("right") machine.send_key("ret") machine.sleep(1) </ins> <del> # Start entering notes machine.send_key("n") </del> # Type the beginning of https://de.wikipedia.org/wiki/Alle_meine_Entchen machine.send_chars("cdef6gg5aaaa7g") <del> # Make sure the VM catches up with all the keys </del> machine.sleep(1) <del> machine.screenshot("MuseScore0") </del> <ins> machine.screenshot("MuseScore2") </ins> # Go to the export dialogue and create a PDF machine.send_key("alt-f")

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:
} { name = "imap"; <del> buildInputs = [ uwimap openssl pam pcre2 ]; configureFlags = [ "--with-imap=${uwimap}" "--with-imap-ssl" ]; # uwimap doesn't build on darwin. enable = (!stdenv.isDarwin); </del> <ins> buildInputs = [ uwimap openssl pam pcre2 libkrb5 ]; configureFlags = [ "--with-imap=${uwimap}" "--with-imap-ssl" "--with-kerberos" ]; </ins> } { name = "intl";

Discussion:
this package () is not available for any platforms. When I try to install the package from the shell To be available for popular platform like x86/amd64. arm64 If applicable, add screenshots to help explain your problem. Add any other context about the problem here. : Answered me by email. Merci :) <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
For the context: I use the wrapper layer of Nix Package Manager and docker with
The extension is a core PHP extension and therefore, it is already available. On my side, I succeeded to test with my own project (loophp/nix-shell) by doing: a random file containing: in or . : in the same directory The thing is that is not in NixOS, if you want to enable it, you have to add it explicitly. The syntax to use is: Hope this helps.
Dear , I guess we can now close this issue ?
any idea why ?
No, but this is a good question, I guess or might help here.
So I did some digging into this, because it's a very good question. The reason for it not being enabled by default on darwin is because it wasn't enabled by default before we migrated to our modular build of PHP. The latest release branch before the modular build was 19.09 and here's the PHP definition from that time, where I have highlighted the line that we emulated by leaving it disabled after that big refactoring: -- so in 19.09 it was disabled on darwin. Inspecting that line further, the last time it was changed before that I linked it as of 19.09 was as part of a refactoring in July 2018: -- however, this commit actually didn't change the fact if it was enabled or not. So looking back ever further I found this, the commit authored in June 2016: That made a bunch of changes to the PHP definition, in which, one of the changes was to disable the imap extension on darwin. So I would assume that at that time, in June 2016, either as a dependency or the PHP extension itself actually didn't build on darwin, hence it was disabled to make PHP build at all on darwin.

Digging deeper: Here's the PR for that latest commit to fix the build back in 2016: And the corresponding issue: In the issue we can conclude that didn't build on darwin at that time. So it was a reasonable desicsion back then to disable that extension. Of course... now... 6 years later... this may not be a problem anymore and maybe we should revisit this :wink:
So now we have the PR merged to build on darwin, which sholud be a good first step to enable the imap extension:
Change:
autoreconfHook = buildPackages.autoreconfHook269; }; <del> # TODO: we should probably merge these 2 musescore = if stdenv.isDarwin then callPackage ../applications/audio/musescore/darwin.nix { } else libsForQt5.callPackage ../applications/audio/musescore { }; </del> <ins> musescore = libsForQt5.callPackage ../applications/audio/musescore { }; </ins> music-player = callPackage ../applications/audio/music-player { };

Discussion:
Package name: MuseScore Latest released version: 4.1 Current version on the unstable channel: 4.0.2 Current version on the stable/release channel: 4.0.2 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Thanks for the notification! Your review is welcome at .