| 7 Nov 2023 |
 K900 | That's probably just broken with latest poetry | 20:27:05 |
 @fractivore:cyberia.club | It looks similar, but fails with exit code 1 rather than 2, and it appears to be the main project builder | 20:27:13 |
| @fractivore:cyberia.club | In reply to @k900:0upti.me
That's probably just broken with latest poetry Should I pin to an earlier poetry version then? Can I do that with the flake? | 20:27:47 |
| K900 | I'd probably try to get rid of the dependency | 20:27:59 |
| K900 | Yep | 20:28:40 |
| K900 | https://github.com/mtkennerly/poetry-dynamic-versioning/releases | 20:28:40 |
| K900 | poetry-dynamic-versioning 0.21.5 is broken with latest poetry | 20:28:49 |
| K900 | You should try and track down where it comes form | 20:29:01 |
| K900 | * You should try and track down where it comes from | 20:29:09 |
| K900 | And see if you can patch it out | 20:29:12 |
| K900 | Actually it's a direct dependency | 20:29:28 |
| K900 | So you can try just poetry-dynamic-versioning = null; | 20:29:36 |
| K900 | So it just doesn't get built at all | 20:29:41 |
| @fractivore:cyberia.club | In reply to @k900:0upti.me
So you can try just poetry-dynamic-versioning = null; Where would I put that line? I tried
overrides = defaultPoetryOverrides.extend
(self: super: {
poetry-dynamic-versioning = null;
| 20:36:29 |
| K900 | Yes, there | 20:36:38 |
| @fractivore:cyberia.club | But now I just get
last 10 log lines:
> File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
> File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
> File "<frozen importlib._bootstrap>", line 1126, in _find_and_load_unlocked
> File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
> File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
> File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
> File "<frozen importlib._bootstrap>", line 1140, in _find_and_load_unlocked
> ModuleNotFoundError: No module named 'poetry_dynamic_versioning'
>
> ERROR Backend 'poetry_dynamic_versioning.backend' is not available.
| 20:36:54 |
| K900 | Oh | 20:37:47 |
| K900 | In pyproject.toml replace
[build-system]
requires = ["poetry-core>=1.0.0", "poetry-dynamic-versioning"]
build-backend = "poetry_dynamic_versioning.backend"
with
[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"
| 20:38:14 |
| @fractivore:cyberia.club | It's building! I collected garbage after I edited the pyproject.toml file, maybe I didn't really need to do that. I'm gonna munch some more pasta while it builds. | 20:44:52 |
| @fractivore:cyberia.club | yay it built! My first real derivation! 😄 | 20:51:07 |
| @fractivore:cyberia.club | Now what do I do lol | 20:51:18 |
| K900 | I dunno | 20:51:46 |
| K900 | Run it? | 20:51:49 |
| K900 | Whatever you were trying to do in the first place | 20:51:56 |
| @fractivore:cyberia.club | Should I contribute it to nixpkgs or something? poetry2nix said something about pushing changes upstream | 20:52:49 |
| @fractivore:cyberia.club | I'm pretty new to making open source contributions | 20:52:57 |
| K900 | You should contribute the overrides that worked for you | 20:54:51 |
| K900 | But putting the whole thing into nixpkgs will require a different build process | 20:55:03 |
| K900 | The current policy with Python packages in nixpkgs is to not use tools like poetry2nix, but use nixpkgs packages directly | 20:55:32 |
| @fractivore:cyberia.club | Oh, okay, I guess I'll just pull the build-systems.json file where it says to put the overrides in the edgecases.md file | 20:57:15 |
