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

ztunnel build fails because of "Unable to update https://github.com/howardjohn/boring/?branch=hyper-boring/adopt-hyper-1.0.0#5185311a" #732

Closed
clairelz-zhang opened this issue Nov 20, 2023 · 9 comments

Comments

@clairelz-zhang
Copy link

I want to build ztunnel 1.19.4 binary with cargo build --release but it failed with below errors.

cargo build --release

Updating git repository `https://github.com/howardjohn/boring/`

error: failed to get boring as a dependency of package ztunnel v0.0.0 (/root/ztunnel)

Caused by:
failed to load source for dependency boring

Caused by:
Unable to update https://github.com/howardjohn/boring/?branch=hyper-boring/adopt-hyper-1.0.0#5185311a

Caused by:
object not found - no match for id (5185311af8addc6851a48bd5747ec634dbb72811); class=Odb (9); code=NotFound (-3)

@hzxuzhonghu
Copy link
Member

Cannot reproduce, do you need to clean cache?

@clairelz-zhang
Copy link
Author

@hzxuzhonghu
Did you try to reproduce in version 1.19.4. Because I tried in the 1.20.0, it works.
This commit id 5185311af8addc6851a48bd5747ec634dbb72811 really doesn't exist in the branch "hyper-boring/adopt-hyper-1.0.0"

@hzxuzhonghu
Copy link
Member

Yes, on 1.19

@clairelz-zhang
Copy link
Author

Do I need to modify the Cargo.lock file?

@ZarrianShi
Copy link
Contributor

ZarrianShi commented Nov 23, 2023

I got the same error while trying to build tag 1.19.4, the commit 5185311a is indeed not exist @howardjohn

@ZarrianShi
Copy link
Contributor

ZarrianShi commented Nov 23, 2023

Do I need to modify the Cargo.lock file?

I had tried to use the newest commit of the branch hyper-boring/adopt-hyper-1.0.0 which full SHA is 423c260d87b69a926594ded0dd693b5cf1220452(also change version to 5.0.0), then a dependency conflict error appears:

$ BUILD_WITH_CONTAINER=1 make build
cargo build
    Updating git repository `https://github.com/howardjohn/boring/`
    Updating git submodule `https://github.com/google/boringssl.git`
    Updating git submodule `https://github.com/google/boringssl.git`
    Updating git repository `https://github.com/howardjohn/hyper-util`
    Updating crates.io index
error: failed to select a version for `hyper`.
    ... required by package `hyper-boring v5.0.0 (https://github.com/howardjohn/boring/?branch=hyper-boring/adopt-hyper-1.0.0#423c260d)`
    ... which satisfies git dependency `hyper-boring` (locked to 5.0.0) of package `ztunnel v0.0.0 (/work)`
versions that meet the requirements `^1.0` are: 1.0.1, 1.0.0

all possible versions conflict with previously selected packages.

  previously selected package `hyper v1.0.0-rc.3`
    ... which satisfies dependency `hyper = "=1.0.0-rc.3"` (locked to 1.0.0-rc.3) of package `hyper-util v0.0.0 (https://github.com/howardjohn/hyper-util?branch=h2-timer-expose-exec#b9eaeca8)`
    ... which satisfies git dependency `hyper-util` (locked to 0.0.0) of package `ztunnel v0.0.0 (/work)`

failed to select a version for `hyper` which could resolve this conflict
make[1]: *** [Makefile.core.mk:11: build] Error 101
make: *** [build] Error 2

seems the hyper is also needed by another dependency but they referenced different version.

@ZarrianShi
Copy link
Contributor

ZarrianShi commented Nov 23, 2023

Cannot reproduce, do you need to clean cache?

maybe the '5185311af8addc6851a48bd5747ec634dbb72811' exists in your local cache?

@howardjohn
Copy link
Member

should be fixed now, sorry about that. We will be off of my forks soon

@GregHanson
Copy link
Member

related to #726

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

5 participants