lix-project/nixos-module
15
7
Fork 14
Code Issues 3 Pull requests Packages Projects Releases Wiki Activity

fix: add nixd and its dependency to overridelist #46

Closed
gepbird wants to merge 0 commits from gepbird:fix-nixd into main
pull from: gepbird:fix-nixd
merge into: lix-project:main
Conversation 3 Commits - Files changed -
gepbird commented 2024-11-20 11:50:25 +00:00
First-time contributor
Copy link

Closes #45

Closes #45
gepbird added 1 commit 2024-11-20 11:50:30 +00:00
gepbird force-pushed fix-nixd from 9a54da0fe6 to d36f053070 2024-11-20 11:51:22 +00:00 Compare
gepbird requested review from jade 2024-11-20 11:54:10 +00:00
jade referenced this pull request from a commit 2024-11-26 06:48:47 +00:00
Merge commit '60edaab' into HEAD
jade commented 2024-11-26 06:48:52 +00:00
Owner
Copy link

merged :)

merged :)
jade closed this pull request 2024-11-26 06:48:57 +00:00
gepbird deleted branch fix-nixd 2024-11-26 07:08:29 +00:00
gepbird commented 2024-11-26 07:15:02 +00:00
Author
First-time contributor
Copy link

Thanks @jade! May I ask if it can be backported to stable or which branch should a home user use? In the docs I see the latest hardcoded release recommended, but I'd like to not have to update my flake.nix whenever there's a new major lix update. And by using the main branch I was getting some lix version mismatch error so thought it's a bad idea.

Thanks @jade! May I ask if it can be backported to stable or which branch should a home user use? In the docs I see the latest hardcoded release recommended, but I'd like to not have to update my flake.nix whenever there's a new major lix update. And by using the main branch I was getting some lix version mismatch error so thought it's a bad idea.
jade commented 2024-11-26 07:19:54 +00:00
Owner
Copy link

Yeah, currently there is not a real stable branch. There is a branch called stable which we might occasionally remember to update, but it is definitely not automated properly and thus cannot be trusted.

If you want to get the non-tagged versions of the module for Lix 2.91 (which will introduce basically no instabilities at all), use release-2.91. main is intended to be used with Lix main and has no guarantees it will work with anything else. This PR should be backported to release-2.91, let me take 5 seconds to do that.

edit: done and released

Yeah, currently there is not a real stable branch. There is a branch called `stable` which we might occasionally remember to update, but it is definitely not automated properly and thus cannot be trusted. If you want to get the non-tagged versions of the module for Lix 2.91 (which will introduce basically no instabilities at all), use `release-2.91`. `main` is intended to be used with Lix main and has no guarantees it will work with anything else. This PR should be backported to release-2.91, let me take 5 seconds to do that. edit: done and released
👍 1

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
jade
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/nixos-module#46
No description provided.
Delete branch "gepbird:fix-nixd"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?