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

0.5.2: lock file is not updated #728

Closed
dvzrv opened this issue Jun 4, 2024 · 2 comments · Fixed by #729
Closed

0.5.2: lock file is not updated #728

dvzrv opened this issue Jun 4, 2024 · 2 comments · Fixed by #729

Comments

@dvzrv
Copy link

dvzrv commented Jun 4, 2024

Hi! 👋

I package this project for Arch Linux. When trying to upgrade to 0.5.2 I noticed that the lock file has not been updated:

version = "0.5.1"

For packaging purposes we want to fetch the locked sources, but this is unfortunately not possible:

$ cargo fetch --locked --target "$(rustc -vV | sed -n 's/host: //p')"
warning: profiles for the non root package will be ignored, specify profiles at the workspace root:
package:   /home/user/Downloads/cyclonedx-rust-cargo/cargo-cyclonedx/Cargo.toml
workspace: /home/user/Downloads/cyclonedx-rust-cargo/Cargo.toml
    Updating crates.io index
error: the lock file /home/user/Downloads/cyclonedx-rust-cargo/Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.
@Shnatsel
Copy link
Contributor

Shnatsel commented Jun 4, 2024

Right, I see. I'll make a 0.5.3 point release soon with this change and also support for cargo binstall. Thanks for letting me know.

@lfrancke
Copy link
Contributor

lfrancke commented Jun 7, 2024

@dvzrv Thank you very much for your packaging work! And thanks @Shnatsel for taking care of the release.

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 a pull request may close this issue.

3 participants