-
Notifications
You must be signed in to change notification settings - Fork 1
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
cargo supposedly not installed while being installed #11
Comments
Unfortunately https://github.com/dionysius/vaultwarden-deb/blob/main/debian/control#L4 looks for a cargo package installed. You have 3 options:
|
…e buildpackage option -d to ignore all build-depends #11
Updated and explained the first option (using |
After that you will run into #12. Just tested the building locally |
I'll try that. But actually, rustup has been introduced to Debian, although it's only to be included in Trixie. That's how I installed it, as the first time I tried to run it, it complained that some dependency needs rustc 1.64, while stable only has 1.63 without any backports. On Testing it then claimed another dependency needed rustc 1.78, so I installed rustup there and tried again with that, running into this issue. |
true |
You are right, it's currently in testing: https://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=names&keywords=rustup. So I will have options in the future to make this a bit smarter once it hits stable. For now, this issue is solved and the package works as intended. The important bits have been documented in the readme. Lets head over to #12, I'll look into it. |
Actually, installing cargo won't be an option anymore in Testing/Trixie once it hits stable. cargo has a fixed dependency on rustc, which in turn will mark rustup to be removed:
Just as a FYI. |
Thank you, will keep in mind. Will be fun when ubuntu and debian are out of sync again package wise. I can use the or operator |
Yep as hoped and expected |
Yes, that does help. |
I've installed the rust toolchain 1.78 with rustup. But gdb buildpackage for some reason refuses to find cargo:
But
So what exactly is it complaining about?
The text was updated successfully, but these errors were encountered: