fix: X11 socket symlink creation #172
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
If this works, I don't see a reason not to merge it |
|
but I don't want to continuously update this. Maybe we should really just drop it and let MS handle this until it breaks again. |
SuperSandro2000
force-pushed
the
fix-x11-symlink
branch
from
6e4825c
to
631930e
Compare
The tmpfile.d rule no longer matches upstream and has higher priority, so rather than updating it now and possible in the future we delete it.
SuperSandro2000
force-pushed
the
fix-x11-symlink
branch
from
631930e
to
1861cd3
Compare
|
now the rule is deleted so that we don't need to update it in the future |
psvo
added a commit
to psvo/NixOS-WSL
that referenced
this pull request
Dec 12, 2022
* upstream/main: Fix X11 socket symlink creation (nix-community#172) Update flakes
nzbr
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
by updating the tmpfile.d rule to match the one created by upstream WSL
Or do we just want to remove this?