jiebi/CodeConvo huggingface dataset:
Code change:
libnotify libxfce4ui libxfce4util <ins> pcre </ins> xfconf ];

Related discussion:
text: Describe the bug The Thunar bulk-rename dialog doesn't support regular expressions. To Reproduce Steps to reproduce the behavior: multiple files. -Click → Rename. "Search & Replace" Expected behavior The "Regular Expression" option can be checked. Screenshots ! Additional context This appears to be because it is not using PCRE or PCRE doesn't support UTF-8. I support it isn't being built with PCRE at all. Notify maintainers No maintainers, touched it last. Metadata system: host os: multi-user?: sandbox: version: channels(kevincox): channels(root): nixpkgs: Maintainer information:
Code change:
"colorlog" "emoji" "immutabledict" <ins> "sarge" </ins> "sentry-sdk" "watchdog" "wrapt"

Related discussion:
text: Octoprint can't build on unstable due to a conflict of the required version for . octoprint , while the dependency requires (due to ) . Octoprint builds successfully I ran a between and (known good) , the first bad commit was I suspect that it's necessary to pin the additional dependencies (and maybe some more), too, but I'm not that experienced with packaging python packages. made the first bad commit Octoprint maintainers: system: host os: multi-user?: sandbox: version: channels(root): channels(richard): nixpkgs: Maintainer information:
Code change:
<ins> { lib, rustPlatform, fetchFromGitHub }: rustPlatform.buildRustPackage rec { pname = "typst-fmt"; version = "unstable-2023-04-16"; src = fetchFromGitHub { owner = "astrale-sharp"; repo = pname; rev = "9ed1fd1656f8e776b6c8d9d326c488f5ba1091eb"; hash = "sha256-yHR13n5yx5Yl2atteGQq+qqz21zsy37ZJfGllbvSZcQ="; }; cargoLock = { lockFile = ./Cargo.lock; outputHashes = { "typst-0.2.0" = "sha256-+YHyxZTzMG9zpzLV9NgJsMtrXG+/ymPQo5b26HDYJaQ="; }; }; postPatch = '' cp ${./Cargo.lock} Cargo.lock ''; checkFlags = [ # test_eof is ignored upstream "--skip=rules::tests_typst_format::test_eof" ]; meta = with lib; { description = "A formatter for the Typst language"; homepage = "https://github.com/astrale-sharp/typst-fmt"; license = licenses.mit; maintainers = with maintainers; [ geri1701 ]; }; } </ins>

Related discussion:
text: Project description Formatter for typst. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...
There is no CLI:
Looks like the author use .
looks like it is still a WIP in
what do you mean wrong default branch? Hi there, I wasn't sure there was interest for a cli, I'll merge the cli in a few days, want a ping then?
I merged my change, it should be good to package!
has renamed the project from typst-fmt to typstfmt in
Code change:
<ins> { lib , buildPythonApplication , fetchFromGitHub , gitMinimal , arrow , click , sh , wheel }: buildPythonApplication rec { pname = "gitlint"; version = "0.15.1"; src = fetchFromGitHub { owner = "jorisroovers"; repo = "gitlint"; rev = "v${version}"; sha256 = "sha256-CqmE4V+svSuQAsoX0I3NpUqPU5CQf3fyCHJPrjUjHF4="; }; nativeBuildInputs = [ wheel ]; propagatedBuildInputs = [ arrow click sh ]; preCheck = '' export PATH="$out/bin:$PATH" ''; checkInputs = [ gitMinimal ]; meta = { description = "Linting for your git commit messages"; homepage = "http://jorisroovers.github.io/gitlint"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ ethancedwards8 ]; }; } </ins>

Related discussion:
text: Gitlint CLI tool and pre-commit hook plugin to lint commit messages with presets Metadata homepage URL: source URL: license: MIT platforms: linux, unix, darwin (python3)
This isn't my library, I simply requested for this package. should i still be included as maintainer?
Also, do I make a PR with the code above? Or is there already a PR
There is no PR yet. New packages need a maintainer and I don't want to maintain this.
I'll do it. I'll send in a PR now.
Code change:
nativeBuildInputs = [ autoconf cargo <del> dump_syms </del> llvmPackages.llvm # llvm-objdump makeWrapper nodejs

Related discussion:
text: Steps to reproduce the behavior: librewolf from nixpkgs master Add any other context about the problem here. Please run and paste the result.
I have the exact same issue but my machine is a little slower :|. Also this means (not just Git ) is now broken.
I also reproduced this on master.
I think it's related to . I'm guessing the crash reporter symbols aren't generated because we disable the crash reporter. Running some tests to confirm.
is the first broken commit on master.
I'm going to close this. The PR by fixes the problem.
Code change:
<del> { lib, stdenv, fetchFromGitHub, rustPlatform, Security, installShellFiles }: </del> <ins> { lib , stdenv , fetchFromGitHub , rustPlatform , Security , SystemConfiguration , installShellFiles }: </ins> rustPlatform.buildRustPackage rec { pname = "ferium";

Related discussion:
text: Steps to reproduce the behavior: ferium cc thanks! <!-- 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]:
Code change:
./darwin-mutexes-4.8.patch ]; <ins> drvArgs.configureFlags = lib.optional (targetPlatform.useLLVM or false) "--with-mutex=POSIX/pthreads"; </ins> drvArgs.hardeningDisable = [ "format" ]; drvArgs.doCheck = false; })

Related discussion:
text: Steps to reproduce the behavior: 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. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
openai = with python3Packages; toPythonApplication openai; <ins> openai-whisper = with python3.pkgs; toPythonApplication openai-whisper; </ins> opengrok = callPackage ../development/tools/misc/opengrok { }; openocd = callPackage ../development/embedded/openocd { };

Related discussion:
text: Project description Whisper is a general-purpose speech recognition model. It is trained on a large dataset of diverse audio and is also a multi-task model that can perform multilingual speech recognition as well as speech translation and language identification. Metadata homepage URL: source URL: license: mit platforms: all
PTAL.
Code change:
if (ipc) { const generator = (stdout: any, res: any) => { <del> diff --git a/src/floating_exceptions/src/main.ts b/src/floating_exceptions/src/main.ts index f298ec7..87a6bc4 100644 --- a/src/floating_exceptions/src/main.ts +++ b/src/floating_exceptions/src/main.ts @@ -1,4 +1,4 @@ -#!/usr/bin/gjs +#!/usr/bin/env gjs imports.gi.versions.Gtk = '3.0' @@ -329,4 +329,4 @@ function main() { Gtk.main() } -main()  No newline at end of file +main() </del> diff --git a/src/panel_settings.ts b/src/panel_settings.ts index 83ff56c..1bc1e98 100644 --- a/src/panel_settings.ts

Related discussion:
text: In 's tray menu the options "Floating Window Exceptions" & "Active Hint Color" don't work. Steps to reproduce the behavior: & enable pop-shell in GNOME (Wayland). pop-shell's tray menu and try clicking the mentioned options. Further dialogs should open for the respective features.
I found the problem: the compiled (g)js are not executible in filesystem. I do not know a solution yet. Most beautiful solution, fix chmod in pop-shell (but how ...). Or after compiling with an workaround in nix. Other solutions are set path to gjs during patching. Till fixing, you can run this features in your in, with calling it per gjs ...
Code change:
, zlib , zstd <ins> # Dependencies of overridden Python dependencies, hopefully we can remove these soon. , rustPlatform </ins> # Optional Dependencies , curl ? null , expat ? null

Related discussion:
text: Steps to reproduce the behavior:  nixos-unstable Noticed when setting and rebuilding &lt;!-- 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]:
You won't get a reply if you leave that empty.
I'm having the same issue I didn't notice when it happened, but I also have sambaFull
Same error whit the package .
This seems related to
That turned out not to be the issue. The actual error: In colour so that one can actually make sense of C++ error messages: ! One potential problem here: This is because of having: Switching to : Builds Removing entirely (which swiches to ): Fails on new related errors (see below) Removing and : Fails because Ceph requires lua = 5.3 and nixpkgs's default is still 5.2: CMake saysCould NOT find Lua (missing: LUAINCLUDEDIR) (Required is at least version "5.3")` Build failure with : <details</detailsI noticed Arch . But we can just use to fix the build.
PR for the
Code change:
|| cfg.openssh.authorizedKeys.keyFiles != []) ) cfg.users) ++ [ config.security.googleOsLogin.enable <del> ]); </del> <ins> ]; </ins> message = '' Neither the root account nor any wheel user has a password or SSH authorized key. <del> You must set one to prevent being locked out of your system.''; </del> <ins> You must set one to prevent being locked out of your system. If you really want to be locked out of your system, set users.allowNoPasswordLogin = true; However you are most probably better off by setting users.mutableUsers = true; and manually running passwd root to set the root password. ''; </ins> } ] ++ flatten (flip mapAttrsToList cfg.users (name: user: [

Related discussion:
text: Describe the bug There are reasons to want a system, that has no user that can log in by SSH or with their password, for example in a declarative container To Reproduce Steps to reproduce the behavior: up a minimal declarative container asserts that I will be locked out from the system and refuses to build the configuration with Expected behavior nix generates me a container that I can log in with , or maybe I don't want to log into it at all (because it's a disposable VM or something of the like). I think there should be a check whether the generated system is a container and an additional "I know what I'm doing" override for other cases. I'll create a PR once we agreed on what's best. Maintainer information: Code causing the problem: mentioning since you the check.
Is it an option to set a randomly-generated (the hash itself would be generated, not obtained by honestly hashing a password)? Recovering the password from such a hash is probably harder than a lot of other attack vectors. But an override «doLockOutEveryone» sounds fine.
Setting a password would certainly be a possibility, but somewhat (for lack of a better word) really lame. Having slept a night over it, I propose , that disables all the assertions at the bottom. I can see scenarios where two users with the same uid could be wanted. I want my unixoid to always give me enough rope to shoot myself in the leg.
What about not enabling ssh and disabling the getty? It should completely lock anyone out, unless I am missing something. Take a look at the profile.
In case of a nixos declaratively defined nixos container, you are not logged out because the root system(d) can generate a root shell without any authentication, which is why I consider this a bug. Having to "fool" the assertion to actually lock oneself out is another matter, I could live with that but I don't think it's nice behavior.
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this.
Code change:
|| cfg.openssh.authorizedKeys.keyFiles != []) ) cfg.users) ++ [ config.security.googleOsLogin.enable <del> ]); </del> <ins> ]; </ins> message = '' Neither the root account nor any wheel user has a password or SSH authorized key. <del> You must set one to prevent being locked out of your system.''; </del> <ins> You must set one to prevent being locked out of your system. If you really want to be locked out of your system, set users.allowNoPasswordLogin = true; However you are most probably better off by setting users.mutableUsers = true; and manually running passwd root to set the root password. ''; </ins> } ] ++ flatten (flip mapAttrsToList cfg.users (name: user: [

Related discussion:
text: Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
This is still an issue.
I marked this as stale due to inactivity. &rarr;
Fixed via
Code change:
# Splicer will pull out correct variations libDeps = platform: [ ncurses ] ++ stdenv.lib.optional (!enableIntegerSimple) gmp <del> ++ stdenv.lib.optional (platform.libc != "glibc") libiconv ++ stdenv.lib.optional enableDwarf elfutils; </del> <ins> ++ stdenv.lib.optional (platform.libc != "glibc") libiconv; </ins> toolsForTarget = [ pkgsBuildTarget.targetPackages.stdenv.cc

Related discussion:
text: Our can no longer link executables. For example: This issue is present in current versions of . Compiling and linking works fine with an older revision, say . It looks like this might be related to some change in binutils, maybe?
This is probably from
Yes, it is. came to the same conclusion.
This probably is GHC bug though. Things like gmp and libiconv get their paths hardcoded so this isn't a problem. I would expect the same treatment for elfutils. should provide a arg.
/cc
I guess now I know why there's a patch in branch.
I'll reopen the PR fixing the linking issues.
I opened while we wait on upstream fix.
Which one, from
Yes, although it doesn't help. See
Yes, it would have surprised me a bit if it helped against that symptom -- my patch fixes that DWARF-enabling is skipped completely.
I'm surprised this worked for you back then and now there are linking errors.
Code change:
${pkgs.remarshal}/bin/json2yaml -i ${lovelaceConfigJSON} -o $out ''; <del> availableComponents = pkgs.home-assistant.availableComponents; </del> <ins> availableComponents = cfg.package.availableComponents; </ins> # Given component "parentConfig.platform", returns whether config.parentConfig # is a list containing a set with set.platform == "platform".

Related discussion:
text: Nixos build error when using a MQTT sensor, following . being the channel. The corresponding line seems to have been removed in : which is the commit for the update to . Maybe the code has changed and the python script no longer recognises sensors correctly ? system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
The configuration you listed above does not yield an evaluation error. I have verified that by building it myself. You must have specified somewhere else.
I don't have any other mention of in my config, although I have also configured an external mqtt brocker with which might change the evaluation. I can confirm that when I remove the sensor config, the evaluation error goes away, which is why I didn't think I needed to include the brocker config. Those are the only mention of in my config I promise! Still it's strange that the line was removed from no ?
I've just noticed now that I have forgotten in my config... Here is the actual pieces of relevant config:
That's the default. No need to include it. After all, I was able to reproduce your error by building NixOS from the stable channel. My bad. It's caused by the following line: which will use the from the stable package. However, if I set I get which I still have to investigate.
I really have no idea what's going on. The way I test this is by having a file with the following content: and a checkout of the branch with the following diff at : When building the configuration I get What's strange is that there is no error when points to the branch with the diff applied. Maybe or have a clue.
I am happy you could reproduce this! Still, I don't see any line for in the (but I see it in the ), which I think it will lead to problems when it will be merged, no ? What I still find strange, is that the referred file in my original error is from ... Is this making any sense ?
Yes, this makes sense: The module is taking the list of from the stable channel and passing those used in your config to the package from the unstable channel, which obviously can't find the component since it's no longer in .
Ok, thank you for your explanations, I understand where the error comes from now !
Code change:
${pkgs.remarshal}/bin/json2yaml -i ${lovelaceConfigJSON} -o $out ''; <del> availableComponents = pkgs.home-assistant.availableComponents; </del> <ins> availableComponents = cfg.package.availableComponents; </ins> # Given component "parentConfig.platform", returns whether config.parentConfig # is a list containing a set with set.platform == "platform".

Related discussion:
text: I did some digging around to know why the line has disappeared from the with the update. This is what I found out: on the home-assistant repository, the code for the mqtt sensor was moved from the to between and this means that the is now in the When I define a mqtt sensor in my nixos config, will the nixos module be able to do the conversion from to (I don't fully understand the code in the nixos module, especially the code) ?
Not yet. I will implement that once I was able to solve the stack overflow issue.
The problem should be solved once you upgrade your system since is now in the channel. Can you please try again?
I can confirm that I don't have the build error anymore, thank you ! However, the home-assistant environment is missing component dependencies. Same as stated previously, home-assistant code has been refactored, but config is the same, which means that dependencies are not found. For example, I have declared in config, but dependencies are at the key.
Adjusting the code for is on my TODO list. For now, please override the package's .
Ok, at the moment, I am using manual config because I am testing home-assistant, using and the automation editor, so I have manually set the . Do you think we could add a package (something like ) which would have all possible dependencies (the idea being that I would also be built by hydra) - a little like the docker/distro image that distributes ?
Sure, no problem. However, I suscpect that will often not build due to some Python packages not building. Do you want to make a PR or should I do it?
I can surely try, but I am not sure how I should proceed : I define a new option for package that populates to all packages referenced in should I call the package with all packages referenced in (in a new file next to ), and call it in a new in . Which option do you think is best ?
I guess the first option comes close to the best one. However, please don't use for that but directly add the packages to . Maybe we could also add a few lines to to add a list of all packages to so that we don't go through all components to generate that list.
Code change:
configureFlags = [ "--with-gtk" "--with--board3d" ]; <ins> desktopItems = makeDesktopItem { desktopName = "GNU Backgammon"; name = pname; genericName = "Backgammon"; comment = meta.description; exec = pname; icon = pname; categories = [ "Game" "GTK" "StrategyGame" ]; }; </ins> meta = with lib; { description = "World class backgammon application"; homepage = "https://www.gnu.org/software/gnubg/";

Related discussion:
text: Package name: gnubg Latest released version: 1.07.001 <!-- Search your package here: --- Current version on the unstable channel: 1.06.002 Current version on the stable/release channel: 1.06.002 <!-- 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.
I packaged this in 2015 and I have no idea why.
Code change:
fsck = handleTest ./fsck.nix {}; fwupd = handleTestOn ["x86_64-linux"] ./fwupd.nix {}; # libsmbios is unsupported on aarch64 gdk-pixbuf = handleTest ./gdk-pixbuf.nix {}; <ins> gotify-server = handleTest ./gotify-server.nix {}; </ins> gitea = handleTest ./gitea.nix {}; gitlab = handleTest ./gitlab.nix {}; gitolite = handleTest ./gitolite.nix {};

Related discussion:
text: Project description A simple server for sending and receiving messages in real-time per WebSocket. Includes a web UI, also has an Android client for receiving notifications and an optional CLI program (distributed separately) for sending notifications. Metadata homepage URL: source URL: license: MIT platforms: anything Go runs on
I started an attempt locally, however it failed due to some timeouts while fetching Go dependencies... will retry during this week :)
I think the main difficulty is the UI, which needs to be compiled with NPM. In essence, I think the build is three-staged: fetch UI dependencies, fetch Go dependencies, do the actual build.
You may want to take a look at .
Code change:
<ins> { lib, stdenv, fetchFromGitHub, cmake, libminc }: stdenv.mkDerivation { pname = "ebtks"; version  = "unstable-2017-09-23"; src = fetchFromGitHub { owner  = "BIC-MNI"; repo   = "EBTKS"; rev    = "67e4e197d8a32d6462c9bdc7af44d64ebde4fb5c"; sha256 = "1a1qw6i47fs1izx60l1ysabpmyx9j5sjnbdv8b47wi2xcc9i3hpq"; }; # error: use of undeclared identifier 'finite'; did you mean 'isfinite'? postPatch = '' substituteInPlace templates/EBTKS/SimpleArray.h  --replace "#define FINITE(x) finite(x)" "#define FINITE(x) isfinite(x)" '' # error: ISO C++17 does not allow 'register' storage class specifier + '' find . -type f -exec sed -i -e 's/register //g' {} + ''; nativeBuildInputs = [ cmake ]; buildInputs = [ libminc ]; cmakeFlags = [ "-DLIBMINC_DIR=${libminc}/lib/cmake" ]; meta = with lib; { homepage = "https://github.com/BIC-MNI/EBTKS"; description = "Library for working with MINC files"; maintainers = with maintainers; [ bcdarwin ]; platforms = platforms.unix; license   = licenses.free; }; } </ins>

Related discussion:
text: For x8664-darwin, aarch64-darwin: build .#EBTKS x8664-darwin: aarch64-darwin:
Code change:
openapi-core = callPackage ../development/python-modules/openapi-core { }; <ins> openusd = callPackage ../development/python-modules/openusd { alembic = pkgs.alembic; }; </ins> overly = callPackage ../development/python-modules/overly { }; overpy = callPackage ../development/python-modules/overpy { };

Related discussion:
text: Project description Universal Scene Description (USD) is an efficient, scalable system for authoring, reading, and streaming time-sampled scene description for interchange between graphics applications. OpenUSD is AFAIK the library to work with the USD format. Metadata homepage URL: source URL: license: Modified Apache 2.0 License platforms: unix, linux, darwin
I've got a working derivation, but I'm not sure if this is already in a state that is good enough for a PR. In particular, packaging the pyside tools properly didn't seem straightforward to me. AFAICT, it just copies some binaries from other QT parts and wraps them with extra arguments, so that's what I'm doing here. While the python package seems to be working properly, I ran into an issue before when trying to include the headers into a C++ project, and I believe it failed to find some python headers? Maybe that needs some extra buildInput? I haven't investigated more. Locally, I've just been using a version compiled with for that. The binaries, such as , are working by my testing, besides requiring on wayland. I'd be happy to make a PR for this if this is a good-enough state.