Closed Artim96 closed 5 months ago
Unfortunately https://github.com/dionysius/vaultwarden-deb/blob/main/debian/control#L4 looks for a cargo package installed. e.g. dpkg -l | grep cargo
should list it. I haven't figured out a way to make this optional as there is no rustup
package in debian.
You have 3 options:
gbp buildpackage -d ...
to ignore build-dependscargo
from your apt sources but still use rustup toolchain install <version>
as described in the readme. It should pick your rustup version when buildingcargo
from build-depends in said file and make a temporary git commit before buildingUpdated and explained the first option (using -d
) in the readme
After that you will run into #12. Just tested the building locally
Unfortunately https://github.com/dionysius/vaultwarden-deb/blob/main/debian/control#L4 looks for a cargo package installed.
e.g. dpkg -l | grep cargo
should list it. I haven't figured out a way to make this optional as there is norustup
package in debian.You have 3 options:
- use
gbp buildpackage -d ...
to ignore build-depends- install
cargo
from your apt sources but still userustup toolchain install <version>
as described in the readme. It should pick your rustup version when building- remove
cargo
from build-depends in said file and make a temporary git commit before building
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.
After that you will run into #12. Just tested the building locally
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:
Error: Conflict: -> cargo:amd64=1.74.1+dfsg1-1 but rustup:amd64 -> rustup:amd64=1.26.0-6 -> not cargo:amd64=1.74.1+dfsg1-1
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 |
in build-depends which might suffice. For now i this source package must run for debian stable or ubuntu lts at least.
Yep as hoped and expected Build-Depends: rustup | cargo
works like a charm. Now you don't need -d
anymore in buildpackage. Tested on trixie
and booworm
. See/use branch main
or tag debian/1.30.5-3
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?