[GH-ISSUE #477] Cargo install is broken #300

Closed
opened 2026-02-27 19:29:53 +03:00 by kerem · 4 comments
Owner

Originally created by @ashthespy on GitHub (May 11, 2020).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/477

Thanks to a breaking change in protobuf-pure, our current master will not build with cargo install.
A workaround is to pass the --locked flag i,e cargo install --locked as per https://github.com/rust-lang/cargo/issues/7169

cc #473 #460

@awiouy @sashahilton00 Could you make a patch release with 6ee2dbaad4 in the meantime?

Originally created by @ashthespy on GitHub (May 11, 2020). Original GitHub issue: https://github.com/librespot-org/librespot/issues/477 Thanks to a breaking change in `protobuf-pure`, our current master will not build with `cargo install`. A workaround is to pass the `--locked` flag i,e `cargo install --locked` as per https://github.com/rust-lang/cargo/issues/7169 cc #473 #460 @awiouy @sashahilton00 Could you make a patch release with 6ee2dbaad4406628f77cd59adebb2ed3ed70fcaa in the meantime?
kerem closed this issue 2026-02-27 19:29:53 +03:00
Author
Owner

@awiouy commented on GitHub (May 13, 2020):

What about vendoring the required crates and using only the vendored crates at build time? This way, the source code would be complete and consistent.
https://doc.rust-lang.org/cargo/commands/cargo-vendor.html

<!-- gh-comment-id:627755974 --> @awiouy commented on GitHub (May 13, 2020): What about vendoring the required crates and using only the vendored crates at build time? This way, the source code would be complete and consistent. https://doc.rust-lang.org/cargo/commands/cargo-vendor.html
Author
Owner

@ashthespy commented on GitHub (May 15, 2020):

Doesn't vendoring requiring you to clone the repo first?
You might as well just build it with --locked if you already cloned it right?

<!-- gh-comment-id:629501114 --> @ashthespy commented on GitHub (May 15, 2020): Doesn't vendoring requiring you to clone the repo first? You might as well just build it with `--locked` if you already cloned it right?
Author
Owner

@TooLazyToMakeAName commented on GitHub (May 21, 2020):

What about vendoring the required crates and using only the vendored crates at build time? This way, the source code would be complete and consistent.
https://doc.rust-lang.org/cargo/commands/cargo-vendor.html

could you not do that commit ( 6ee2dba ) to master then rebase dev onto master ? A none compiling master seems the greater evil.

<!-- gh-comment-id:632404017 --> @TooLazyToMakeAName commented on GitHub (May 21, 2020): > What about vendoring the required crates and using only the vendored crates at build time? This way, the source code would be complete and consistent. > https://doc.rust-lang.org/cargo/commands/cargo-vendor.html could you not do that commit ( 6ee2dba ) to master then rebase dev onto master ? A none compiling master seems the greater evil.
Author
Owner

@EdoardoLaGreca commented on GitHub (Jul 21, 2020):

If you're trying to compile it on a Raspberry Pi (as I did, expect 40m+ of compiling time) I'd suggest you to try this command: cargo install --features alsa-backend -- librespot.

HMU if it solves the problem

<!-- gh-comment-id:661824163 --> @EdoardoLaGreca commented on GitHub (Jul 21, 2020): If you're trying to compile it on a Raspberry Pi (as I did, expect 40m+ of compiling time) I'd suggest you to try this command: `cargo install --features alsa-backend -- librespot`. HMU if it solves the problem
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/librespot#300
No description provided.