libutil: Fix error message #12758
Merged
libutil: Fix error message #12758
+1
−1
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
I encountered this with a misconfigured libutil. I doubt that a non-lutimes config is viable, because tests were failing.
|
Was this intended to be a draft? |
|
I marked it as draft by mistake because I didn't solve my root cause yet, but this PR only fixes a technically unrelated problem anyway. A possible outcome is that we remove this code, but other than that, this trivial PR is ready for review. |
Ericson2314
added
backport 2.24-maintenance
This was referenced Mar 28, 2025
mergify bot
added a commit
that referenced
this pull request
Mar 28, 2025
…2758 libutil: Fix error message (backport #12758)
mergify bot
added a commit
that referenced
this pull request
Mar 28, 2025
…2758 libutil: Fix error message (backport #12758)
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.
I encountered this with a misconfigured libutil. I doubt that a non-lutimes config is viable, because tests were failing.
EDIT: I get the misconfiguration reproducibly with
.#native-clangStdenv; need to look into why it happensEDIT:
nix build .#nix-everything-clangStdenvpasses with this PRMotivation
Context
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.