Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Complicated installation #921

Closed
LuckyFrost opened this issue Nov 3, 2023 · 2 comments
Closed

Complicated installation #921

LuckyFrost opened this issue Nov 3, 2023 · 2 comments
Labels
S-triage Status: Waiting for a maintainer to triage this issue/PR

Comments

@LuckyFrost
Copy link

Installing rustic is not the most trivial task.
rhel 9
1)

wget https://github.com/rustic-rs/rustic/releases/download/v0.5.4/rustic-v0.5.4-x86_64-unknown-linux-gnu.tar.gz
tar xvzf rustic-v0.5.4-x86_64-unknown-linux-gnu.tar.gz
./rustic
./rustic: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by ./rustic)
cargo --version
cargo 1.73.0 (9c4383fb5 2023-08-26)

cargo-binstall -V
1.4.4

/root/.cargo/bin/cargo-binstall rustic-rs
 WARN Failed to read git credential file /root/.git-credentials err=Os { code: 2, kind: NotFound, message: "No such file or directory" }
 WARN Failed to retrieve token from `gh auth token` err=Os { code: 2, kind: NotFound, message: "No such file or directory" }
 INFO resolve: Resolving package: 'rustic-rs'
ERROR Fatal error:
  × For crate rustic-rs: Failed to parse cargo manifest: TOML parse error at line 44, column 11
  │    |
  │ 44 | pkg-fmt = "tar.gz"
  │    |           ^^^^^^^^
  │ unknown variant `tar.gz`, expected one of `tar`, `tbz2`, `tgz`, `txz`, `tzstd`, `zip`, `bin`
  │
  ├─▶ Failed to parse cargo manifest: TOML parse error at line 44, column 11
  │      |
  │   44 | pkg-fmt = "tar.gz"
  │      |           ^^^^^^^^
  │   unknown variant `tar.gz`, expected one of `tar`, `tbz2`, `tgz`, `txz`, `tzstd`, `zip`, `bin`
  │
  ├─▶ TOML parse error at line 44, column 11
  │      |
  │   44 | pkg-fmt = "tar.gz"
  │      |           ^^^^^^^^
  │   unknown variant `tar.gz`, expected one of `tar`, `tbz2`, `tgz`, `txz`, `tzstd`, `zip`, `bin`
  │
  ╰─▶ TOML parse error at line 44, column 11
         |
      44 | pkg-fmt = "tar.gz"
         |           ^^^^^^^^
      unknown variant `tar.gz`, expected one of `tar`, `tbz2`, `tgz`, `txz`, `tzstd`, `zip`, `bin`

  1. And even cargo install is not the most trivial for those who have not touched rust. At the beginning I did this
dnf install cargo
cargo install rustic-rs
    Updating crates.io index
  Installing rustic-rs v0.6.0
error: failed to compile `rustic-rs v0.6.0`, intermediate artifacts can be found at `/tmp/cargo-installLmGHaW`

Caused by:
  package `clap_builder v4.4.7` cannot be built because it requires rustc 1.70.0 or newer, while the currently active rustc version is 1.66.1

Yes, of course, I spent a some time getting more recent versions of cargo and was able to install using the third method, but it is too complicated compared to restic.

@github-actions github-actions bot added the S-triage Status: Waiting for a maintainer to triage this issue/PR label Nov 3, 2023
@aawsome
Copy link
Member

aawsome commented Nov 3, 2023

Thanks for opening this issue!

About 1): did you try the musl Versions? Those should work without glibc requirements. But have a look at the nightly builds!

About 2): I think this should be fixed by #919 in the next release.

@LuckyFrost
Copy link
Author

Thanks, I just checked musl - at first glance it works.
I also tried using self-update on it - is this how it should be?

./rustic self-update
using no config file (./rustic.toml doesn't exist)
Checking target-arch... x86_64-unknown-linux-musl
Checking current version... v0.5.4
Checking latest released version... v0.6.0
New release found! v0.5.4 --> v0.6.0
New release is *NOT* compatible
Error: ReleaseError: No asset found for target: `x86_64-unknown-linux-musl`

@rustic-rs rustic-rs locked and limited conversation to collaborators Nov 4, 2023
@simonsan simonsan converted this issue into discussion #923 Nov 4, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
S-triage Status: Waiting for a maintainer to triage this issue/PR
Projects
None yet
Development

No branches or pull requests

2 participants