fix: fallback rev to empty string #1949
No reviewers
Labels
No labels
Abandoned
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
bob the builder
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity!1949
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Henry-Hiles/continuwuity:quad/fix/flake-compat"
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?
This pull request... fixes flake-compat support by falling rev back to null.
Pull request checklist:
mainbranch, and the branch is named something other thanmain.myself, if applicable. This includes ensuring code compiles.
5d96e72352ee1940eba2ee1940eba27bcde96d53WIP: fix: fallback rev to nullto WIP: fix: fallback rev to empty stringWIP: fix: fallback rev to empty stringto fix: fallback rev to empty stringJust a small note; as a regression test for this we might as well add a little
nix-instantiate -A defaultto the workflows, this way we can see if the derivation evaluates. It is then safe to assume that the flake-compat build is identical to the flake build.@bart wrote in #1949 (comment):
Good idea, I can add that.
@Henry-Hiles wrote in #1949 (comment):
Actually, that doesn't work. Even if I don't do this change,
nix-instantiate -A defaultstill works.