Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cargo install failed on 0.37.0 #1603

Closed
ykomatsu opened this issue Feb 20, 2023 · 1 comment · Fixed by #1606
Closed

cargo install failed on 0.37.0 #1603

ykomatsu opened this issue Feb 20, 2023 · 1 comment · Fixed by #1606
Labels
topic: build Anything relating to the build system. type: bug Something isn't working

Comments

@ykomatsu
Copy link

cargo install failed on 0.37.0.

> cargo install --version 0.37.0 fj-app
... snip ...
error: couldn't read /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/../../../assets/navigation_cube/cube.obj: No such file or directory (os error 2)
  --> /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/assets.rs:15:13
   |
15 |             include_bytes!("../../../assets/navigation_cube/cube.obj");
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `include_bytes` (in Nightly builds, run with -Z macro-backtrace for more info)

error: couldn't read /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/../../../assets/navigation_cube/cube.mtl: No such file or directory (os error 2)
  --> /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/assets.rs:17:13
   |
17 |             include_bytes!("../../../assets/navigation_cube/cube.mtl");
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `include_bytes` (in Nightly builds, run with -Z macro-backtrace for more info)

error: couldn't read /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/../../../assets/navigation_cube/front.png: No such file or directory (os error 2)
  --> /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/assets.rs:19:13
   |
19 |             include_bytes!("../../../assets/navigation_cube/front.png");
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `include_bytes` (in Nightly builds, run with -Z macro-backtrace for more info)

error: couldn't read /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/../../../assets/navigation_cube/right.png: No such file or directory (os error 2)
  --> /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/assets.rs:21:13
   |
21 |             include_bytes!("../../../assets/navigation_cube/right.png");
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `include_bytes` (in Nightly builds, run with -Z macro-backtrace for more info)

error: couldn't read /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/../../../assets/navigation_cube/rear.png: No such file or directory (os error 2)
  --> /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/assets.rs:23:13
   |
23 |             include_bytes!("../../../assets/navigation_cube/rear.png");
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `include_bytes` (in Nightly builds, run with -Z macro-backtrace for more info)

error: couldn't read /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/../../../assets/navigation_cube/left.png: No such file or directory (os error 2)
  --> /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/assets.rs:25:13
   |
25 |             include_bytes!("../../../assets/navigation_cube/left.png");
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `include_bytes` (in Nightly builds, run with -Z macro-backtrace for more info)

error: couldn't read /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/../../../assets/navigation_cube/top.png: No such file or directory (os error 2)
  --> /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/assets.rs:27:13
   |
27 |             include_bytes!("../../../assets/navigation_cube/top.png");
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `include_bytes` (in Nightly builds, run with -Z macro-backtrace for more info)

error: couldn't read /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/../../../assets/navigation_cube/bottom.png: No such file or directory (os error 2)
  --> /Users/ykoma/.cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/fj-viewer-0.37.0/src/assets.rs:29:13
   |
29 |             include_bytes!("../../../assets/navigation_cube/bottom.png");
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `include_bytes` (in Nightly builds, run with -Z macro-backtrace for more info)

   Compiling futures v0.3.26
error: could not compile `fj-viewer` due to 8 previous errors
warning: build failed, waiting for other jobs to finish...
error: failed to compile `fj-app v0.37.0`, intermediate artifacts can be found at `/var/folders/dj/2r8nstk968s9t2cfzf38_7v40000gn/T/cargo-install3o1uAk`

I think that /assets/navigation_cube directory is not accessible in .cargo directory.

@hannobraun
Copy link
Owner

Thank you for opening this issue, @ykomatsu!

This was introduced in #1573. I should have caught this in review. Oh well 😄

This is also the second bug of this kind that made it into a release in the recent months. We are currently running cargo publish with the --no-verify option to save time and CI resources, but I think this was a mistake, as it would catch issues like this.

I will fix this issue and look into removing --no-verify in the next few days.

@hannobraun hannobraun added type: bug Something isn't working topic: build Anything relating to the build system. labels Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: build Anything relating to the build system. type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants