| 6 Nov 2023 |
K900 | This makes zero sense | 20:51:51 |
K900 | You're adding an empty list | 20:51:56 |
matthewcroughan - nix.how | ah.. I copied from some template code | 20:52:10 |
matthewcroughan - nix.how | and I didn't notice that | 20:52:16 |
matthewcroughan - nix.how | Wait, re-reading it again even, that's not supposed to be an empty list | 20:53:17 |
matthewcroughan - nix.how | old.nativeBuildInputs is supposed to be :
nativeBuildInputs = [
hatchling
hatch-requirements-txt
hatch-fancy-pypi-readme
];
| 20:53:31 |
matthewcroughan - nix.how | * old.nativeBuildInputs is supposed to be :
nativeBuildInputs = [
hatchling
hatch-requirements-txt
hatch-fancy-pypi-readme
];
https://github.com/NixOS/nixpkgs/blob/nixos-unstable/pkgs/development/python-modules/gradio/client.nix#L62C1-L66C5
| 20:53:47 |
matthewcroughan - nix.how | and then if not, it will be an empty list, and then my deps, am I misreading something? | 20:54:08 |
K900 | Are you sure you're using a recent enough nixpkgs? | 20:54:33 |
K900 | That package does not exist in 23.05 | 20:54:40 |
K900 | And is two months old in unstable | 20:54:44 |
matthewcroughan - nix.how | 85f1ba3e51676fa8cc604a3d863d729026a6b8eb | 20:55:08 |
matthewcroughan - nix.how | nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
poetry2nix = {
url = "github:pegasust/poetry2nix/orjson";
inputs.nixpkgs.follows = "nixpkgs";
};
| 20:55:22 |
K900 | What is that poetry2nix branch | 20:55:32 |
matthewcroughan - nix.how | something new to fix orjson that I was just trying out | 20:55:42 |
matthewcroughan - nix.how | https://github.com/nix-community/poetry2nix/pull/1398 | 20:55:48 |
matthewcroughan - nix.how | it's based on poetry2nix 2553decbc032504e968312cf0cb76964ca602035 so I think it's okay | 20:56:13 |
matthewcroughan - nix.how | And with that, private gpt is finally packaged.. | 20:58:09 |
matthewcroughan - nix.how | that took me forever. | 20:58:12 |
K900 | nix-repl> map (x: x.name) packages.x86_64-linux.chinatsu.passthru.python.pkgs.gradio-client.nativeBui
[ "python3-3.11.5" "wrap-python-hook" "ensure-newer-sources-hook" "python-remove-tests-dir-hook" "python-catch-conflicts-hook" "python-remove-bin-bytecode-hook" "pypa-build-hook.sh" "pypa-install-hook" "python-imports-check-hook.sh" "python-namespaces-hook.sh" "python-output-dist-hook" "python3.11-hatchling-1.18.0" "python3.11-hatch-requirements-txt-0.4.0" "python3.11-hatch-fancy-pypi-readme-23.1.0" "python3.11-hatchling-1.18.0" "python3.11-setuptools-68.2.2" ]
| 20:58:37 |
K900 | Can't reproduce here | 20:58:41 |
K900 | This is just a random poetry2nix package that definitely does not touch gradio | 20:58:50 |
K900 | As you can see, all the inputs are there | 20:59:06 |
matthewcroughan - nix.how | in poetry2nix defaultPoetryOverrides.extend (self: super: {}) does super use Nixpkgs ? | 20:59:55 |
matthewcroughan - nix.how | or is that before the overlay is applied? | 21:00:10 |
matthewcroughan - nix.how | because if so, I've been using super, assuming it means before and after in the context of extended | 21:00:50 |
matthewcroughan - nix.how | * because if so, I've been using super, assuming it means before and after in the context of just the extended ovelray | 21:01:08 |
matthewcroughan - nix.how | * because if so, I've been using super, assuming it means before and after in the context of just the extended overlay | 21:01:11 |
matthewcroughan - nix.how | * because if not, I've been using super, assuming it means before and after in the context of just the extended overlay | 21:01:23 |
K900 | super uses the entire overlay stack | 21:01:25 |