-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
loaOf deprecation warnings or errors #77189
Comments
transmission is using the users.users and users.groups configuration, so also needs to be patched. |
I'm seeing the last bit of warnings at https://hydra.nixos.org/jobset/nixos/trunk-combined#tabs-errors |
It seems to just be tests, these remain to be fixed in |
The last warnings are just in tests. |
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them. Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel. |
can this be closed now? |
Describe the bug
The type
loaOf
was deprecated and its use will spring up evaluation warnings likeThis was done in #63103, but because the scope of the change
it wasn't feasible to get them all in one go and there was a few syntax related errors #77177.
rg "loaOf"
returned this for me at the time of writingand it appears some modules were probably added while the PR was opened used the old format.
What to do if encountered
Duplicate such changes like in:
Here's the PR that added the release note, with details about the change #77109.
The text was updated successfully, but these errors were encountered: