Closed matwey closed 2 years ago
That would be a problem in the crate itself, not a problem in cargo vendor as a service here.
Try checking out the flux project and doing "cargo update; cargo build".
cargo build
works fine.
It says:
Compiling anyhow v1.0.56
and as far as I understand 1.0.56
also satisfies requirement 1
.
What OBS project are you seeing this in?
I see the issue. It's because your cargo dir is a child of flux, specific flux/libflux. Because of that, when it unpacks, it can't find the vendor dir, since it expects you to run cargo in the root, not the child dir.
So I think you need to change your specfile to have the %setup for vendor.tar extract into libflux.
Thank you. I'll try you advice. However, I wounder how does it work here: https://build.opensuse.org/package/show/server:database/flux I've just updated version.
The difference appears to be the presence of the Cargo.lock in the vendor.tar, which is needed for when an "update" is run. Otherwise I can't see any other differences ....
@matwey I'm assuming that worked for you?
Yes, thank you!
Hi,
I am running
obs-service-cargo_vendor-0.4.3~5-1.1.noarch
(openSUSE Tumbleweed). I am tring to package this https://github.com/influxdata/flux/tree/v0.170.1 project, as the following:And see the following:
I suppose this is due to controversial version requirements.
libflux
crate consists of two members:flux
requiringanyhow = "1"
, andflux-core
requiringanyhow = "1.0.56"
.Can you reproduce this issue?