-
Notifications
You must be signed in to change notification settings - Fork 139
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
Debian package? #897
Comments
What errors did you get when you tried to build Topgrade with that version of Rust toolchain?🤔
Packaging for Linux is hard, so I won't do this. But I am willing to help if someone wants to get this done. |
It fails on one of the dependencies, because the provided version of
I might take a look at this when I have time, then. I've never built a Debian package before, but I've built packages for other OSes (like FreeBSD), so I imagine I'll be able to figure it out somehow and get something set up as a GitHub action. |
Looks like Topgrade's MSRV is 1.70.
Appreciate it, feel free to ask me for help if needed! |
#898 adds the
For more information, see the discussion there. |
This is incorrect, Topgrade needs Rust 1.76.0 or higher, I just pinned the toolchain to the MSRV in #900. |
Ah, nice. That'll help identify when it need to be updated in the documentation. |
I want to suggest some general feature
It would be nice if there were a Debian package available for this (even if it requires adding another repo). Currently, Debian stable doesn't have a new enough version of rust in its packaging system to build the project (and, given their focus is on stability rather than the newest versions of things, I wouldn't expect that to change), so installing it requires installing binaries the package manager doesn't know about. Even installing
cargo-binstall
doesn't work, as it requires a newer version ofrustc
than Debian offers.It'd be much easier if there were a package that could just install the binary on its own, rather than having to build it on a host and then copy it over to other hosts every time there's an update.
The text was updated successfully, but these errors were encountered: