Closed aghecenco closed 2 months ago
@aghecenco looking at the CI failures, and it seems virtio-queue
contains unpublished changes (we bump the version when we make a new release). So unfortunately this might not be possible as long as the crates are developed in the same repository.
Can you give more info re: Cargo.lock and duplicates? perhaps there's another solution to your problem.
Summary of the PR
Use the published virtio-queue to prevent unwanted duplicates in Cargo.lock when consuming both am unpublished device and a released virtio-queue.
Requirements
Before submitting your PR, please make sure you addressed the following requirements:
git commit -s
), and the commit message has max 60 characters for the summary and max 75 characters for each description line.unsafe
code is properly documented.