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

Update to v0.5.0 using cargo fails #778

Closed
lukehsiao opened this issue Jun 7, 2021 · 5 comments
Closed

Update to v0.5.0 using cargo fails #778

lukehsiao opened this issue Jun 7, 2021 · 5 comments

Comments

@lukehsiao
Copy link

lukehsiao commented Jun 7, 2021

I'm excited for the new release! I notice when I try to update tectonic using cargo, I see the following failure.

error: failed to run custom build command for `tectonic_bridge_harfbuzz v0.2.0`

Caused by:
  process didn't exit successfully: `/tmp/cargo-installskpdaR/release/build/tectonic_bridge_harfbuzz-e75182cb6c8217ab/build-script-build` (exit code: 1)
  --- stderr
  error: no such file /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/tectonic_bridge_harfbuzz-0.2.0/harfbuzz/src/harfbuzz.cc
     if you have checked out from Git, you probably need to fetch submodules:
         git submodule update --init
     This is needed because we are attempting to compile a local copy of Harfbuzz.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `tectonic v0.5.0`, intermediate artifacts can be found at `/tmp/cargo-installskpdaR`

Caused by:
  build failed


Updated 0 packages.
Failed to update tectonic.
@pkgw
Copy link
Collaborator

pkgw commented Jun 7, 2021

Yup, there was a packaging error in the tectonic_bridge_harfbuzz crate. I think that I should have it resolved once #781 goes through.

@pkgw
Copy link
Collaborator

pkgw commented Jun 7, 2021

OK, hopefully version 0.2.2 of tectonic_bridge_harfbuzz should fix this issue. Is anyone able to confirm?

@soruh
Copy link

soruh commented Jun 7, 2021

It works for me.

@roland-5
Copy link

roland-5 commented Jun 7, 2021

Yup, cargo install tectonic working flawless.

@lukehsiao
Copy link
Author

I can also confirm that I was able to update to tectonic v0.5.1 just fine with the fix. I'd consider this issue resolved, and am closing the issue as a result. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants