Untitled attachment

Notices where this attachment appears

1. Embed this notice
   silverpill (silverpill@mitra.social)'s status on Friday, 16-May-2025 06:34:22 JST silverpill

   Rust is 10 years old, but they still ask people to do this:

   curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
2. Embed this notice
   Jonathan ‘theJPster’ Pallant (thejpster@hachyderm.io)'s status on Thursday, 25-Apr-2024 20:44:05 JST Jonathan ‘theJPster’ Pallant

   Hey @bagder, I was wondering about the default Rust install command:

   curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

   Is the restriction on --proto to =https strictly required? Will curl switch to http even given an https URL?

   Is the restriction to TLSv1.2 strictly required? Will curl downgrade to TLSv1.1 or SSLv3 if the server suggests it?

   The -s and -S are fine, but I'd probably live with the stderr output for the sake of command brevity. The -f seems reasonable though.

3. Embed this notice
   かみま :turube: 巣 (kamima_iruka@su.kurotanesou.online)'s status on Monday, 19-Feb-2024 09:00:10 JST かみま :turube: 巣

   @dev
   朝早くから失礼いたします（返信は急がなくても結構です）

   Firefishのアップデートを試みたところ、エラーが起きてサーバが起動しなくなる事象がおきています。
   他の鯖缶さん同様Rustのバージョンが問題かと考えたのですが、別の事象でしょうか…？

   ＝＝＝＝＝＝＝＝＝＝＝＝＝＝
   ＜経緯＞
   ```
   sudo apt purge --remove rust-all
   curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
   ```
   した後に、SSH再接続

   ```
   $ rustc --version
   rustc 1.76.0 (07dca489a 2024-02-04)
   ```
   を確認した後に、`sudo ./update.sh`

   ＜エラー＞
   ```
   error: package `clap_lex v0.7.0` cannot be built because it requires rustc 1.74 or newer, while the currently active rustc version is 1.73.0
   Either upgrade to rustc 1.74 or newer, or use
   cargo update -p clap_lex@0.7.0 --precise ver
   where `ver` is the latest version of `clap_lex` supporting rustc 1.73.0
   Internal Error: Command failed: cargo build --release
   at genericNodeError (node:internal/errors:956:15)
   at wrappedFn (node:internal/errors:510:14)
   at checkExecSyncError (node:child_process:890:11)
   at Object.execSync (node:child_process:962:15)
   at BuildCommand.<anonymous> (/home/firefish/firefish/node_modules/.pnpm/@napi-rs+cli@2.18.0/node_modules/@napi-rs/cli/scripts/index.js:11527:30)
   at Generator.next (<anonymous>)
   at /home/firefish/firefish/node_modules/.pnpm/@napi-rs+cli@2.18.0/node_modules/@napi-rs/cli/scripts/index.js:3540:69
   at new Promise (<anonymous>)
   at __awaiter$1 (/home/firefish/firefish/node_modules/.pnpm/@napi-rs+cli@2.18.0/node_modules/@napi-rs/cli/scripts/index.js:3536:10)
   at BuildCommand.execute (/home/firefish/firefish/node_modules/.pnpm/@napi-rs+cli@2.18.0/node_modules/@napi-rs/cli/scripts/index.js:11297:16)
   /home/firefish/firefish/packages/backend-rs:
    ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  backend-rs@0.0.0 build: `napi build --platform --release ./built/`
   Exit status 1
    ELIFECYCLE  Command failed with exit code 1.
    ELIFECYCLE  Command failed with exit code 1.
   ```

4. Embed this notice
   naskya::dev (dev@post.naskya.net)'s status on Saturday, 17-Feb-2024 20:40:12 JST naskya::dev

   in reply to

   @ddquino@misskey.yukineko.me sudo apt purge --remove rust-all curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

5. Embed this notice
   Jarkko Sakkinen (jarkko@social.kernel.org)'s status on Friday, 17-Nov-2023 01:37:14 JST Jarkko Sakkinen

   Installing #rustup:

   alias rustup="curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | bash -s --"

   E.g.

   rustup --no-modify-path

   Just though that good to write this up since I see some distributions packaging rustup, which makes no sense (for #rustc and #cargo it does for obvious reasons).

   It is also totally safe to run rustup this way kudos to the amazing #TLS 1.2.

   #rustlang