nix build fails to find Cargo.lock #822
Labels
No labels
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
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity#822
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
I use the nix
#oci-imagebuild target because it lets me build the static release binary using less disk space than using a docker Ubuntu image, and with more chances of success than directly asking cargo to build a static binary (which was always a little tricky for me).But, having rebased on the main branch, the nix build fails to find
Cargo.lock- although there is one at the root of the repo.Build details :
d78fc535It seems the issue was due to the fact that I was calling nix as
The
cranecrate apparently tries to fetch from/nix/store/...whereas it should use/path/to/my/store/nix/store/.... See this crane issue for insights. The issue was closed with a fixup but conduwuit's flake seems to bring it up again.As a workaround, I added
in
commonAttrsin/nix/pkgs/main/default.nix.I don't know what to do with this now. Is this workaround a real fix ? It possibly wouldn't harm to point to
Cargo.lockexplicitly. I could propose a MR with a proper comment to document what it addresses. I'm just really too fresh to nix to tell.I'll wait for some input before closing this issue.
Closing as this target doesn't exist anymore