jiebi/CodeConvo huggingface dataset:
Code change:
}; }; }) <ins> (mkIf (cfg.enable && cfg.prompt.enable) { environment.interactiveShellInit = '' source ${cfg.package}/share/bash-completion/completions/git-prompt.sh ''; }) </ins> ]; meta.maintainers = with maintainers; [ figsoda ];

Related discussion:
text: git package includes which defines functions for shell prompt customization like . Even though the file is included it's not sourced by default and doesn't make the functions available. Steps to reproduce the behavior: package system-wide. one of the functions provided: the file manually: function becomes available: shell function being available out of the box when package installed. Making the prompt functions available when bash completions are enabled seem to have been the original intention of . However one might also argue that the functions should not be sourced by default if someone doesn't use git prompt customisations provided. It could be placed behind an option but I'm not sure it's worth the hassle. cc
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I'm not a maintainer or expert, but I read your linked Discourse thread and your ticket because it sounded interesting. Great analysis and writeup. My interpretation is that was never intended to be sourced automatically when completions are enabled, for two reasons. First, inside of : which is an instruction to source it explicitly. Second, the for says: which leads me to believe that was created so that it can be used independently from bash completion. Prior to its creation, it might have been available automatically as a consequence of completion scripts being loaded eagerly, but that was accidental.
Thanks for digging deeper into this, Theodore! I agree with your conclusion: it does look like the prompt script wasn't intended to be sourced automatically. I think the best way to approach this in NixOS would be to have a option that would enable sourcing of the file.
I think something like this sounds reasonable. I'm sorry I can't help with it right now, because I haven't set up NixOS yet. (I'm just using nix on my Mac right now.)
No worries, thanks for your help so far :) I might eventually give it a shot myself.
Code change:
with lib; <del> # The Magewell Pro Capture drivers are not supported for kernels older than 3.2 assert versionAtLeast kernel.version "3.2.0"; </del> let bits = if stdenv.is64bit then "64"

Related discussion:
text: I'm trying to use the mwprocapture nixos module (which uses the mwprocapture kernel package) on 20.09 (linuxPackageslatest), and I get the following: Is this known and/or already fixed somewhere? (Also, is it safe to use it anyways?) I'd love to try and fix it further myself, but I don't know how to splice in a local/development nix file into my for development purposes :sweatsmile: (also CC
Looks like upgrading the package version resolved things. Will create a PR soon.
Thanks for the heads up.
Code change:
typst = callPackage ../tools/typesetting/typst { }; <ins> typst-fmt = callPackage ../tools/typesetting/typst-fmt { }; </ins> tz = callPackage ../tools/misc/tz { }; u9fs = callPackage ../servers/u9fs { };

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:
makeCacheWritable = true; npmWorkspace = "apps/desktop"; <del> npmDepsHash = "sha256-KN8C9Y0tfhHVagk+CUMpI/bIRChhzxC9M27HkU4aTEc="; </del> <ins> npmDepsHash = "sha256-bnYpvHO9Pnob+MbrSshv03mSwXCADH/2xw33nLVKMdg="; </ins> cargoDeps = rustPlatform.fetchCargoTarball { name = "${pname}-${version}"; inherit patches src; patchFlags = [ "-p4" ]; sourceRoot = "${src.name}/${cargoRoot}"; <del> hash = "sha256-AmtdmOR3aZJTZiFbkwRXjeTOJdcN40bTmWx4Ss3JNJ8="; </del> <ins> hash = "sha256-pCy3hGhI3mXm4uTOaFMykOzJqK2PC0t0hE8MrJKtA/k="; </ins> }; cargoRoot = "apps/desktop/desktop_native";

Related discussion:
text: Steps to reproduce the behavior: bitwarden Please run and paste the result.
Will be fixed by
Code change:
orgmode-parse = dontCheck super.orgmode-parse; os-release = dontCheck super.os-release; persistent-redis = dontCheck super.persistent-redis; <ins> pure-zlib = dontCheck super.pure-zlib; # https://github.com/NixOS/nixpkgs/issues/37499 </ins> pipes-extra = dontCheck super.pipes-extra; pipes-websockets = dontCheck super.pipes-websockets; postgresql-binary = dontCheck super.postgresql-binary; # needs a running postgresql server

Related discussion:
text: The package fails to build because of missing test dependencies: system: host os: multi-user?: sandbox: version: channels(z0028sn): nixpkgs:
I jailbroke it and the the tests fail anyway. So it should be set to . succeeds.
The problem is that the release tarball on Hackage is incomplete, i.e. the required file appears to be missing. This should be reported upstream () so that they can release a fixed version. Ping:
This should be fixed in 0.6.1, which I just uploaded to Hackage. Please tell me (probably on a pure-zlib ticket?) if you have any further problems.
Code change:
inherit (pkgs) stdenv fetchurl unzip; }; <ins> sources = import ./sources.nix { inherit (pkgs) stdenv fetchurl unzip; }; </ins> androidsdk = import ./androidsdk.nix { inherit (pkgs) stdenv fetchurl unzip makeWrapper; inherit (pkgs) zlib glxinfo freetype fontconfig glib gtk2 atk mesa file alsaLib jdk coreutils libpulseaudio dbus; inherit (pkgs.xorg) libX11 libXext libXrender libxcb libXau libXdmcp libXtst xkeyboardconfig; <del> inherit platformTools buildTools support supportRepository platforms sysimages addons; </del> <ins> inherit platformTools buildTools support supportRepository platforms sysimages addons sources includeSources; </ins> stdenv_32bit = pkgs_i686.stdenv; };

Related discussion:
text: Currently, our Android SDK derivations contain only binary files. This is unfortunate during development, when one wants to jump to a definition of a particular symbol in the SDK and it is not found. For comparison, ArchLinux is doing this in their packages, e.g. System: 16.09pre-git (Flounder) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: "16.09beta335." /cc
Created PR .
Code change:
stdenv.mkDerivation { pname = "mmc-utils"; <del> version = "2018-12-14"; </del> <ins> version = "2019-10-04"; </ins> src = fetchgit { url = "git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc-utils.git"; <del> rev = "aef913e31b659462fe6b9320d241676cba97f67b"; sha256 = "1mak9rqjp6yvqk2h5hfil5a9gfx138h62n3cryckfbhr6fmaylm7"; </del> <ins> rev = "73d6c59af8d1bcedf5de4aa1f5d5b7f765f545f5"; sha256 = "18a7qm86gavg15gv4h6xfnapgq24v4dyvhwfp53lkssxyhjbli0z"; </ins> }; makeFlags = [ "CC=${stdenv.cc.targetPrefix}cc" ];

Related discussion:
text: Describe the bug While Nixpkgs provides version 2018-12-14, there are some fixes landed since then. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
can please check using with a local chekout of nixpkgs?
Yes, I will. Thank you for your prompt response!
I did and tried some commands. It seems to work fine and the store size does not grow significantly. Is there anything else to test?
Code change:
<ins> { lib, rustPlatform, fetchFromGitHub, libdrm }: rustPlatform.buildRustPackage rec { pname = "amdgpu_top"; version = "0.1.7"; src = fetchFromGitHub { owner = "Umio-Yasuno"; repo = pname; rev = "v${version}-stable"; hash = "sha256-cdKUj0pUlXxMNx0jypuov4hX3CISTDaSQh+KFB5R8ys="; }; cargoLock.lockFile = ./Cargo.lock; buildInputs = [ libdrm ]; meta = with lib; { description = "Tool to display AMDGPU usage"; homepage = "https://github.com/Umio-Yasuno/amdgpu_top"; changelog = "https://github.com/Umio-Yasuno/amdgpu_top/releases"; license = licenses.mit; maintainers = with maintainers; [ geri1701 ]; }; } </ins>

Related discussion:
text: Project description amdgputop is tool that display AMD GPU utilization, like or . The tool displays information gathered from performance counters (GRBM, GRBM2, CPSTAT), sensors, fdinfo, and AMDGPU driver. Presumably it wouldn't depend on as does, and it's written in that one language. :lobster: Metadata homepage URL: source URL: license: mit platforms: linux
Code change:
runHook postInstall ''; <ins> checkPhase = attrs.checkPhase or '' runHook preCheck $LUAROCKS test runHook postCheck ''; </ins> passthru = { inherit lua; # The lua interpreter inherit externalDeps;

Related discussion:
text: Describe the bug neovim fails to build with missing , similar to , on . To Reproduce Steps to reproduce the behavior: to from master () Expected behavior The package should successfully build. Metadata On master () Maintainer information:
via in
so you could do until a proper fix.
Reverting the luarocks bump doesn't work for me. That fix is also very surprising to me, since neovim broke (for me) after the latest nixos-unstable channel update.
Interesting. It worked fine for me. Running the above revert command and then (inside my local nixpkgs with it reverted) let me build neovim properly. I don't think it's particularly surprising if updating a channel that happens to include the luarocks bump causes it to break, unless I'm misunderstanding you.
I updated from a channel where the luarocks bump had already happened, and neovim worked on that channel. In fact, I reverted to the previous hydra evaluation to make my system evaluate again.
This was actually before and it was working without problems and then suddenly the problem appeared again. I can also report that I cam getting this in the same way described (updated latest nixos-unstable channel and then neovim stopped building again).
I confirm this fixed by on master (channels may take a while). For now I'll assume that charvp's failure to resolve the issue with that revert was some kind of mistake; we can re-open otherwise, perhaps separately if it's a different kind of error.
Does anyone know why updating the luarocks dependency is so brittle? Is it possible to at least add a test so we don't regress again in the future?
the tool exists (nixpkgs-review) but it takes CPU and disk space to run plus some reviewer time (and was not run in this case). Also for this specific case, the luarocks update broke in subtle ways the build so I wouldn't call it . It is called unstable for a reason. The good thing about nixpkgs is you can pin neovim to an older version while keeping your system on unstable.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Are we sure this is fixed on Darwin? still shows failing with logs of: Or is this a different issue?
Code change:
runHook postInstall ''; <ins> checkPhase = attrs.checkPhase or '' runHook preCheck $LUAROCKS test runHook postCheck ''; </ins> passthru = { inherit lua; # The lua interpreter inherit externalDeps;

Related discussion:
text: I think the root problem here is that luarocks has a poor implementation of "move". Combined with the build's behavior being affected by filesystem ordering the result is essentially random. The [implementation of move][] calls out to the operating system commands [][] and [][]. Building with will contain a sequence of , and . I've extracted the [relevant part of the log][]. The critical aspect here is that by default, unix will dereference symlinks and copy their contents. [implementation of move]: []: []: [relevant part of the log]: My theory: luarocks scans the directory for external libraries in filesystem order and attempts to move all shared libraries from to . At which point one of 3! things will happen, but the two main ones are: is copied and deleted and , now broken symlinks, fail to copy and are copied by dereferencing, and deleted is copied and deleted Either way is wrong to some degree, but one of them happens to work well enough for downstream packages to build. If I build locally, the filesystem order I get seems to work, so we can inspect the two results: I've been focusing on this for darwin since the failure case happens to be cached, but I believe it applies equally to linux.
is that sthg you have already witnessed ?
What LuaRocks version is this happening with? I have pushed fixes related to the file deployment stage in 3.3.1.
I've tested 3.2.1 (current nixpkgs master) and 3.3.1 (hasty upgrade locally), they both have similar results, except on 3.3.1 the errors now propagate correctly. I've uploaded a [log of a failed build][] with 3.3.1. [log of a failed build]:
I was hoping to find time to write a proper issue report and a test lua package for this, but haven't yet. My test case would have a directory structure made with , that looks like: In order to succeed the deployment stage would have to produce both the file and its symlink.
Code change:
runHook postInstall ''; <ins> checkPhase = attrs.checkPhase or '' runHook preCheck $LUAROCKS test runHook postCheck ''; </ins> passthru = { inherit lua; # The lua interpreter inherit externalDeps;

Related discussion:
text: Describe the bug I have neovim in my systemPackages, I did and today and it stuck at building luajit: To Reproduce Steps to reproduce the behavior: to Expected behavior The system should upgrade properly. Additional context Output: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(kj): nixpkgs: Maintainer information:
Possible fix is in . There was already an open issue about it () but from an unclear reason people have reached the conclusion it was fixed on latest master.
Oh I meant , not .
Well, I agree with that conclusion. For me, on the build is broken with the error above and on current master it isn't. EDIT: note that the channels lag behind, usually less than a couple days, but sometimes we get a week or two due to some harder regression.
Yea right. For me on NixOS I tried with the nixpkgs-unstable channel and could install successfully. The nixos-unstable still fails though.
Code change:
license = stdenv.lib.licenses.gpl3Plus; maintainers = with stdenv.lib.maintainers; [raskin]; description = "Scientific Pragramming Language"; <ins> # https://savannah.gnu.org/bugs/?func=detailitem&item_id=56425 is the best attempt to fix JIT broken = enableJIT; </ins> platforms = if overridePlatforms == null then (with stdenv.lib.platforms; linux ++ darwin) else overridePlatforms;

Related discussion:
text: I'm trying to build octave with QT5 and with GUI (of course, when I try to build it with GUI, right?). Unfortunately, after the build: Apply this patch: and then system: host os: multi-user?: sandbox: version: channels(m): nixpkgs:
I just noticed that I do not even get the GUI feature when building octave from nixpkgs (neither nor has a GUI).
Pinging: touched the package recently, is the maintainer of the package.
I’ll try to have a look when I have some time. I’ll let you know what I can achieve.
Here is what the configure script says:
yes, I got that and I fixed it. See for my attempt to build with Qt5 (which succeeds, but starting octave with gui fails - see PR).
Code change:
exit 1 fi <del> VERSION=$1 </del> <ins> VERSION="$1" </ins> declare -A SYSTEMS HASHES SYSTEMS=(

Related discussion:
text: Element v1.11.0 updated to Electron 19, so we need this packaged in Nixpkgs: <!-- 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: <!-- 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: 18.1.0 desired version: 19.0.7 <!-- 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.
When I run the script tries to download which does not exist. Do you know where to get the electron headers?
PR that brings electron19 but does not provide electron19 headers:
I believe that states that they migrated storage. So, I think the new url would be
Great find, thanks! Updated PR to include this change and electron_19 now provides the headers.
electrum_19 to master via - feel free to update your package
Code change:
<del> { lib, buildPythonPackage, fetchPypi }: </del> <ins> { lib , buildPythonPackage , fetchFromGitHub , pytestCheckHook }: </ins> buildPythonPackage rec { pname = "sarge"; version = "0.1.7"; <ins> format = "setuptools"; </ins> <del> src = fetchPypi { inherit pname version; sha256 = "3b810d396a75a5a2805272f64f4316f6dcc086e0a744b042cdb0effc85c0f21b"; </del> <ins> src = fetchFromGitHub { owner = "vsajip"; repo = pname; rev = version; sha256 = "sha256-E1alSDXj0oeyB6dN5PAtN62FPpMsCKb4R9DpfWdFtn0="; </ins> }; <del> # No tests in PyPI tarball doCheck = false; </del> <ins> checkInputs = [ pytestCheckHook ]; pythonImportsCheck = [ "sarge" ]; </ins> meta = with lib; { <ins> description = "Python wrapper for subprocess which provides command pipeline functionality"; </ins> homepage = "https://sarge.readthedocs.org/"; <del> description = "A wrapper for subprocess which provides command pipeline functionality"; </del> license = licenses.bsd3; maintainers = with maintainers; [ abbradar ]; };

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:
fribidi p11-kit <ins> gmp </ins> # libraries not on the upstream include list, but nevertheless expected # by at least one appimage libtool.lib # for Synfigstudio

Related discussion:
text: Describe the bug AppImages assume that the gmp library is present on the system, but appimage-run does not include gmp. To Reproduce Steps to reproduce the behavior: +x the appimage Expected behavior The app should run. Additional context I believe it is because of this commit: I fixed it on my end with: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
I marked this as stale due to inactivity. &rarr;
not stale
Also affected:
as pointed out by t-paul, appimage specifically assumes GMP is provided by the system
Code change:
ogre = ogre1_10; }; <del> certbot = callPackage ../tools/admin/certbot { }; </del> <ins> certbot = python3Packages.callPackage ../tools/admin/certbot { }; </ins> caf = callPackage ../development/libraries/caf {};

Related discussion:
text: Update certbot Current packaged version is 0.39.0, upstream version is 1.2.0.
Fix in
Code change:
rustPlatform.buildRustPackage rec { pname = "racer"; <del> version = "2.1.22"; </del> <ins> version = "2.1.27"; </ins> src = fetchFromGitHub { owner = "racer-rust"; repo = "racer"; rev = "v${version}"; <del> sha256 = "1n808h4jqxkvpjwmj8jgi4y5is5zvr8vn42mwb3yi13mix32cysa"; </del> <ins> sha256 = "1ajj515ck5n0mzig77xnq1qgb2s4gf6ahgd5mab91406jvij9qf3"; </ins> }; <del> cargoSha256 = "0njaa9vk2i9g1c6sq20b7ls97nl532rfv3is7d8dwz51nrwk6jxs"; </del> <ins> cargoSha256 = "0ki5j5gh59c92a0w43kzljpiamv2jvyk4m2w8qldfyl5kaa40dxb"; </ins> buildInputs = [ makeWrapper ] ++ stdenv.lib.optional stdenv.isDarwin Security;

Related discussion:
text: Current version of rustracer 2.1.22 does not build with latest stable rust (see ). Please update rustracer to the newest version 2.1.27
Code change:
]; checkInputs = [ pytestCheckHook ]; <del> disabledTests = [ # Steam runtime is hard-coded with steam-run.patch and can't be configured "test_run_steam_runtime_not_found" "test_unknown_steam_runtime_detected" # Steam runtime 2 currently isn't supported # See https://github.com/NixOS/nixpkgs/issues/100655 "test_run_winetricks_steam_runtime_v2" ]; </del> <ins> pythonImportsCheck = [ "protontricks" ]; </ins> meta = with lib; { description = "A simple wrapper for running Winetricks commands for Proton-enabled games";

Related discussion:
text: This issue is mainly a note to myself since the upgrade won't be trivial and will need a lot of testing. Protontricks is now using the Pressure Vessel runtime, so I have to refactor my patches with steam-run to account for this. <!-- 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 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: protontricks <!-- The current version can be found easily with the same process than 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.4.4 desired version: 1.5.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: myself
Code change:
<ins> { lib, rustPlatform, fetchFromGitHub }: rustPlatform.buildRustPackage rec { pname = "gobang"; version = "0.1.0-alpha.5"; src = fetchFromGitHub { owner = "tako8ki"; repo = pname; rev = "v${version}"; sha256 = "02glb3hlprpdc72ji0248a7g0vr36yxr0gfbbms2m25v251dyaa6"; }; cargoSha256 = "sha256-Tiefet5gLpiuYY6Scg5fjnaPiZfVl5Gy2oZFdhgNRxY="; meta = with lib; { description = "A cross-platform TUI database management tool written in Rust"; homepage = "https://github.com/tako8ki/gobang"; license = licenses.mit; maintainers = with maintainers; [ figsoda ]; }; } </ins>

Related discussion:
text: Project description A cross-platform TUI database management tool written in Rust Metadata homepage URL: source URL: license: mit platforms: unix