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

Remove git reference for sev #334

Merged
merged 1 commit into from
Aug 29, 2023

Conversation

emanuellima1
Copy link
Contributor

Having the sev dependency come from GitHub instead of crates.io was causing errors when vendoring. This change fixes it, as it makes Cargo look for sev on crates.io.

Fixes issue 333.

Having the sev dependency come from GitHub instead of crates.io was
causing errors when vendoring. This change fixes it, as it makes Cargo
look for sev on crates.io.

Fixes [issue 333](#333).

Signed-off-by: Emanuel Lima <[email protected]>
@emanuellima1 emanuellima1 requested a review from jialez0 as a code owner August 29, 2023 20:10
@beraldoleal
Copy link
Member

@fitzthum any reason for using the virtee/sev here?

Copy link
Member

@fitzthum fitzthum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is probably just a remnant from the switch to the virtee repo. Should be fine to change.

@fitzthum fitzthum merged commit f4b58ce into confidential-containers:main Aug 29, 2023
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

Successfully merging this pull request may close these issues.

Cargo Vendor fails due to duplicate version of sev
3 participants