Conversation
a134877 to
38d7eef
Compare
|
Result of 2 packages failed to build:
2 packages built:
logs |
|
it build the second time :-) Result of 4 packages built:
|
|
I just had the same issue when running on GitHub actions, it was fine the second time I ran it? I'll look into it, but it's a bit difficult since it doesn't happen locally or even consistently. Some quick research makes me think it is something to do with |
2c60700 to
ec195a2
Compare
|
I've been using the package for the past week or so without running in to the issue. setuptools had been updated in nixpkgs since creating this PR, so I updated the branch. I believe there was an issue with that specific version of setuptools that has since been fixed. I think this PR is ready to merge! |
There was a problem hiding this comment.
https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#package-naming
The pname attribute should be identical to the upstream package name.
There was a problem hiding this comment.
Since both versions of gdtoolkit may be in use, I followed what was chosen for Godot 3 and 4. There may be a better way to do this that I am missing, so please let me know if that is the case!
There was a problem hiding this comment.
version will be appended, so you can have both installed name=godot-3.3.1 and name=godot-4.4.2
I am not aware of any issues or reasons for changing pname
There was a problem hiding this comment.
Hmm, I originally thought that as well, but wanted to keep it similar to Godot. I'll check to see if I can find an issue/PR where that was discussed to see why that was chosen.
There was a problem hiding this comment.
It seems the names should be without an _ then? That's what godot itself is doing, and seems nice to have it consistent.
The docs do indeed say The pname attribute should be identical to the upstream package name. (as linked above) but should is key here, and this feels like a valid reason for the extra number.
pkgs/top-level/aliases.nix
Outdated
There was a problem hiding this comment.
whats the justification for now having this toplevel attribute ?
There was a problem hiding this comment.
Like with the package name, I followed how this was implemented for Godot 3 and 4.
nixpkgs/pkgs/top-level/aliases.nix
Line 327 in 614b461
TheOddler
left a comment
There was a problem hiding this comment.
Tested and works for me. Code seems good. Do see my comment below about the naming, I'm happy to approve already and leave it up to your best judgement with the name.
There was a problem hiding this comment.
It seems the names should be without an _ then? That's what godot itself is doing, and seems nice to have it consistent.
The docs do indeed say The pname attribute should be identical to the upstream package name. (as linked above) but should is key here, and this feels like a valid reason for the extra number.
|
That's fair, I can get that updated! The whole naming scheme with Godot is a bit odd, |
|
Yea, I got confused looking into the naming too, the Godot packages don't seem consistent, and they changed it for godot 3 but not for godot 4 at some point, idk. A bit messy, so I guess best you can do is not add to the mess? |
|
Result of 2 packages failed to build:
2 packages built:
|
|
Oh, I only tested by actually running it as part of my system (actually using it). Also tried nixpkgs-review now, and it fails some tests: |
I've been using this locally and worked around this by just disabling tests for these. + disabledTestPaths = [
+ "tests/generated/test_expression_parsing.py"
+ "tests/gdradon/test_executable.py"
+ ];What I find odd though is that if I do multiple rebuilds these tests sometimes don't fail and sometimes do, quite odd, also not quite sure why |
This is what I've been doing as well, and it works well so far, no problems.
I did not have to disable any tests. I'm not sure what your setup is, but I added |
It seems to be working for me, but the inconsistency makes it difficult to tell. Hopefully everything is good now, but if anyone still has issues, let me know! |
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/how-to-introduce-a-breaking-version-bump/46746/2 |
|
Hello, this seemed to break my system upgrade, on unstable-small, even though i don't use godot... it spits out on the upgrade: this host is a media server, running jellyfin, radarr, deluge... nothing with godot or games, or game dev... not even a gui. here is the config: https://github.com/Thiago-Assis-T/.nixos and the hostname is |
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
That's very strange. I have a bit of time this morning, I'll look into it and see if I can find anything! My first complete guess would be something like nvim or similar using it as a formatter, but it doesn't make much sense that you would have the gdtoolkit formatter in your config. |
|
AAAAA yess, i'm using nixvim, with all ts grammars... perhaps thats it? i dont have as formatter or as linter though, never messed with godot, so never added it... |
|
Wow, guess seems to have been correct! It looks like it is an issue with nixvim |
Yep 😄 |
|
thank you @squarepear |
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
addressing: NixOS/nixpkgs#291040
Description of changes
Rename gdtoolkit to gdtoolkit_3
Init gdtoolkit_4 at v4.2.2
Update gdtoolkit_3 to v3.5.0
Tested and seems to be working fine.
Resolves #267249
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.