# Seeking beta testers for Rustup v1.27.1 **URL:** \ **Category:** community\ **Created:** [April 28, 2024, 12:11am UTC](https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-v1-27-1/20730 "2024-04-28T00:11:31Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rami3l](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/rami3l/32/9835_2.png) [@rami3l](https://internals.rust-lang.org/u/rami3l)\ **Post date:** [April 28, 2024, 12:11am UTC](https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-v1-27-1/20730/1 "2024-04-28T00:11:32Z")
Hi everyone! Following [dist: bump `rustup` version to `1.27.1` by rami3l · Pull Request #3773 · rust-lang/rustup · GitHub](https://github.com/rust-lang/rustup/pull/3773), I'd like to announce on behalf of the Rustup team that Rustup v1.27.1 beta is now available for testing and we are currently looking for beta testers to ensure that this update does deliver the improvements that we would like it to include. We would be happy to receive regression/breakage reports of any kind, especially regarding the following use cases: - `rustup component (add|remove)` with a fully qualified component name: Commands like `rustup component remove rust-std-wasm32-unknown-unknown` should no longer fail ([rustup component remove component-NOT-TOOLCHAIN-TARGET errors · Issue #3166 · rust-lang/rustup · GitHub](https://github.com/rust-lang/rustup/issues/3166)); - GitHub Codespaces: The installation should no longer fail with an error ([Rustup-init fails when `fish` is installed but without config files generated · Issue #3706 · rust-lang/rustup · GitHub](https://github.com/rust-lang/rustup/issues/3706)); - Windows: The update to v1.27.1 should update Rustup’s `DisplayVersion` in your “Programs” panel as well ([rustup self update doesn't update DisplayVersion · Issue #3739 · rust-lang/rustup · GitHub](https://github.com/rust-lang/rustup/issues/3739)); - Old macOS versions (10.12+): The precompiled build should work normally again ([Rustup 1.27.0 incompatible with older macOS · Issue #3708 · rust-lang/rustup · GitHub](https://github.com/rust-lang/rustup/issues/3708)); - Where `~/.rustup/(downloads|tmp)` are symlinks: `rustup update` should no longer fail ([Regression when ~/.rustup/downloads and/or tmp are symlinks · Issue #3344 · rust-lang/rustup · GitHub](https://github.com/rust-lang/rustup/issues/3344)). To begin, all you need to do is simply switching to the dev environment by setting the `RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup` environment variable and update (or install) rustup. \[1\] Many thanks in advance! * * * 1. To switch out of the dev environment, just remove that environment variable and do a `rustup self update`. Also, if you want to be sure you’re using the right environment, we have added a debug message for `RUSTUP_UPDATE_ROOT` which will appear after setting the `RUSTUP_DEBUG` flag ([feat: log `RUSTUP_UPDATE_ROOT`, `RUSTUP_DIST_SERVER` or `RUSTUP_DIST_ROOT` on `RUSTUP_DEBUG` by rami3l · Pull Request #3722 · rust-lang/rustup · GitHub](https://github.com/rust-lang/rustup/issues/3722)). ---
**Author:** ![correabuscar](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/correabuscar/32/11958_2.png) [@correabuscar](https://internals.rust-lang.org/u/correabuscar)\ **Post date:** [April 28, 2024, 9:12am UTC](https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-v1-27-1/20730/2 "2024-04-28T09:12:52Z")
**tl;dr:** it works for me (the #3708 case): ```rust RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup rustup self update ``` or ```rust export RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup rustup self update ``` or ```rust curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup sh ``` or ```rust export RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh ``` > **** > > > [@rami3l](#): > > > > RUSTUP\_UPDATE\_ROOT=[https://dev-static.rust-lang.org/rustup](https://dev-static.rust-lang.org/rustup) > > That url seems to be 404(hmm, only on safari, not on firefox/gentoo, odd), but anyway I tried this: > > ```rust > users-iMac:45 user$ RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup > users-iMac:45 user$ rustup self update > info: checking for self-update > rustup unchanged - 1.27.0 > > ``` > > What should I replace the below url with, to get it to install? because I've uninstalled it and #3708 is in effect. > > ```rust > users-iMac:45 user$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh > > ``` > > ok, nevermind, it seems to work if I prepend `export` to the env. var. setting! ie. `export RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup` instead of just `RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup` it makes sense in retrospect. > > **EDIT:** For both commands it's required to have `export`-ed one. (that is, for both: `rustup self update` and the `curl` one) > > **EDIT2:** I didn't know there was a difference between these 2 ways to pass the env. var., the one on cmdline does an implicit `export`, it seems, had no idea until now: > > ```rust > users-iMac:45 user$ RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup rustup self update > debug: `RUSTUP_UPDATE_ROOT` has been set to `https://dev-static.rust-lang.org/rustup` > info: checking for self-update > debug: `RUSTUP_UPDATE_ROOT` has been set to `https://dev-static.rust-lang.org/rustup` > rustup unchanged - 1.27.1 > > users-iMac:45 user$ RUSTUP_UPDATE_ROOT=https://dev-static.rust-lang.org/rustup > users-iMac:45 user$ rustup self update > info: checking for self-update > info: downloading self-update > rustup updated - (unknown) (from 1.27.1) > > dyld: cannot load 'rustup-init' (load command 0x80000034 is unknown) > error: self-updated failed to replace rustup executable > > ``` ---
**Author:** ![malachid](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/malachid/32/12125_2.png) [@malachid](https://internals.rust-lang.org/u/malachid)\ **Post date:** [May 4, 2024, 7:28pm UTC](https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-v1-27-1/20730/4 "2024-05-04T19:28:53Z")
From Ubuntu 22.04, the update worked without error. Trying multiple projects, I am not seeing any issues with both stable and nightly installed. I also don't see any issues with VSCode or RustRover after updating. `rustup doc` doesn't work; but that's because it is trying to open them in the default snap version of Firefox. Opening the page in Chrome works. Also verified the completions generations is working. ---
**Author:** ![rami3l](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/rami3l/32/9835_2.png) [@rami3l](https://internals.rust-lang.org/u/rami3l)\ **Post date:** [May 5, 2024, 2:03am UTC](https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-v1-27-1/20730/5 "2024-05-05T02:03:59Z")
Thanks a lot for your detailed report! I'm not quite sure why `rustup doc` part didn't work on your side, but I do know that we depend on [GitHub - Seeker14491/opener: Open a file or link in the system default program.](https://github.com/Seeker14491/opener) for this feature, and detecting the default browser is harder than it seems... Setting the `BROWSER` environment variable to your default browser should help in general. It would be particularly helpful if you file a GitHub issue on this one, and then we can decide whether it should be forwarded upstream. ---
**Author:** ![malachid](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/malachid/32/12125_2.png) [@malachid](https://internals.rust-lang.org/u/malachid)\ **Post date:** [May 5, 2024, 3:24am UTC](https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-v1-27-1/20730/6 "2024-05-05T03:24:15Z")
Hi @rami3l . I took a look at that repo. `rustup doc` does successfully launch Firefox, it's just not allowed to access documentation generated by rustup. There are multiple tickets filed for it. I had commented on this one in 2022. > > > \### Problem > > Running \`rustup doc\` or \`rustup doc --book\` in \[Fedora Silverblue…\](https://silverblue.fedoraproject.org/) opens the web browser with temporary directories that in turn opens a broken HTML page. These pages are broken in the sense that CSS appears to missing, and clicking on a link will result in a \`File not found\` error: > > \`\`\` > file:///run/user/1000/doc/a80e7c5e/index.html > \`\`\` > > These directories only seem to contain \`index.html\` too: > > \`\`\` > $ find /run/user/1000/doc/a80e7c5e > /run/user/1000/doc/a80e7c5e > /run/user/1000/doc/a80e7c5e/index.html > \`\`\` > > This behavior persists regardless of whether it opens in the Firefox RPM or in the \[Firefox flatpak\](https://flathub.org/apps/details/org.mozilla.firefox). > > The pages themselves are actually intact, as they can be browsed from within rustup's install location: > > \`\`\` > file:///var/home/jstone/.rustup/toolchains/stable-x86\_64-unknown-linux-gnu/share/doc/rust/html/book/index.html > \`\`\` > > \### Steps > > 1. \[Install Fedora Silverblue\](https://silverblue.fedoraproject.org/) > 2. \[Install rustup from the official instructions\](https://rustup.rs/) > 3. Run \`rustup doc\` or \`rustup doc --book\` > 4. Observe page URL in browser window > > \### Possible Solution(s) > > \_No response\_ > > \### Notes > > \`\`\` > $ distro > Name: Fedora Linux 36.20220510.0 (Silverblue) > Version: 36 > Codename: > $ uname -a > Linux fedora 5.17.5-300.fc36.x86\_64 #1 SMP PREEMPT Thu Apr 28 15:51:30 UTC 2022 x86\_64 x86\_64 x86\_64 GNU/Linux > \`\`\` > > \### Rustup version > > \`\`\`console > rustup 1.24.3 (ce5817a94 2021-05-31) > info: This is the version for the rustup toolchain manager, not the rustc compiler. > info: The currently active \`rustc\` version is \`rustc 1.60.0 (7737e0b5c 2022-04-04)\` > \`\`\` > > > \### Installed toolchains > > \`\`\`console > Default host: x86\_64-unknown-linux-gnu > rustup home: /var/home/jstone/.rustup > > installed toolchains > \-------------------- > > stable-x86\_64-unknown-linux-gnu (default) > nightly-x86\_64-unknown-linux-gnu > > installed targets for active toolchain > \-------------------------------------- > > x86\_64-unknown-linux-gnu > x86\_64-unknown-linux-musl > > active toolchain > \---------------- > > stable-x86\_64-unknown-linux-gnu (default) > rustc 1.60.0 (7737e0b5c 2022-04-04) > \`\`\` A couple other places that it was mentioned: > > > This appears in Firefox when I run \`rustup docs\`: > > \`\`\` > Access to the file was… denied > > The file at /home/ken/.rustup/toolchains/nightly-x86\_64-unknown-linux-gnu/share/doc/rust/html/index.html is not readable. > > It may have been removed, moved, or file permissions may be preventing access. > \`\`\` > > I had tried a bunch of stuff to give myself permission, but running \`cat /home/ken/blahblah/index.html\` works. There is a record of some troubleshooting \[here\](https://stackoverflow.com/questions/55961953/access-denied-when-i-run-rustup-doc?noredirect=1#comment98647187\_55961953), but to no avail. > > Hope we can find a solution, thanks in advance for your time. > > > version info: > \`\`\` > rustc 1.37.0-nightly (2887008e0 2019-06-12) > binary: rustc > commit-hash: 2887008e0ce0824be4e0e9562c22ea397b165c97 > commit-date: 2019-06-12 > host: x86\_64-unknown-linux-gnu > release: 1.37.0-nightly > LLVM version: 8.0 > \`\`\` > > > \- I have searched open and closed issues and pull requests for duplicates, using… these search terms: > - doc > - access > - denied > \- I have checked the latest \`main\` branch to see if this has already been fixed, in this file: > - I believe this is a packaging bug rather than a software bug > > URL to the section(s) of the book with this problem: > The issue is that the local version of the book (or any of the docs cannot load) > > Description of the problem: > When running \`rustup doc\` (or any variant) on Ubuntu since Firefox since it became a snap, I get a browser error > !\[Screenshot from 2022-11-12 10-46-05\](https://user-images.githubusercontent.com/146764/201482542-d2e30515-74ab-4641-a80e-40ddb911966f.png) > > Suggested fix: > Place the contents of the docs elsewhere than in a hidden directory. In general, `rustup doc` does not work on a default install of Ubuntu. You'd have to uninstall the default Firefox browser and reinstall it as a .deb since both the snap and flatpak are broken with respect to rust documentation. Or switch to a different default browser. ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/system/32/14092_2.png) [@system](https://internals.rust-lang.org/u/system)\ **Post date:** [August 3, 2024, 3:24am UTC](https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-v1-27-1/20730/7 "2024-08-03T03:24:22Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.