Indeed, when I try to build the latest rye binary within nixpkgs, it fails with:
Compiling monotrail-utils v0.0.1 (https://github.com/konstin/poc-monotrail#9d3892a5)
error: couldn't read /build/cargo-vendor-dir/monotrail-utils-0.0.1/src/../../../resources/python_build_standalone_known_good_release.json.zst: No such file or directory (os error 2)
--> /build/cargo-vendor-dir/monotrail-utils-0.0.1/src/standalone_python.rs:32:5
|
32 | include_bytes!("../../../resources/python_build_standalone_known_good_release.json.zst");
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: this error originates in the macro `include_bytes` (in Nightly builds, run with -Z macro-backtrace for more info)
Compiling age v0.9.2
error: could not compile `monotrail-utils` (lib) due to previous error
warning: build failed, waiting for other jobs to finish...
Would it be possible to move this file back where it was previously ? It was working fine in this sense.
Hello,
It seems that having the
resources/python_build_standalone_known_good_release.json.zst
file outside from themonotrail-utils
crate is not completely supported by cargo.Indeed, when I try to build the latest rye binary within nixpkgs, it fails with:
Would it be possible to move this file back where it was previously ? It was working fine in this sense.