Skip to content

Can't install nightly-2019-01-10 #57488

Description

@emilyalbini

Installing rust nightly with rustup returns this error:

info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: latest update on 2019-01-10, rust version 1.33.0-nightly (6ecad3383 2019-01-09)
info: downloading component 'rustc'
error: failed to parse url: nightly/2019-01-10/rustc-nightly-x86_64-unknown-linux-gnu.tar.xz
info: caused by: relative URL without a base

We're aware of this and a fix is pending in #57484. Sorry for the trouble!

Activity

  1. added
    P-highHigh priority
    T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.
    C-bugCategory: This is a bug.
    on Jan 10, 2019
  2. pinned this issue on Jan 10, 2019
  3. dwijnand commented on Jan 10, 2019

    @dwijnand
    Contributor

    You can mitigate this by using rustup install nightly-2019-01-09 instead of today's nightly, and then use +nightly-2019-01-09 in place of +nightly.

  4. added a commit that references this issue on Jan 10, 2019
  5. jens1o commented on Jan 10, 2019

    @jens1o
    Contributor

    Thanks for pinning this, just wanted to file a new issue. :)

  6. NathanIceSea commented on Jan 10, 2019

    @NathanIceSea

    failed to parse url again 😅😂!

  7. added a commit that references this issue on Jan 10, 2019
    c2d381d
  8. emilyalbini commented on Jan 11, 2019

    @emilyalbini
    MemberAuthor

    The issue will be fixed in the next nightly. Sorry for the trouble.

  9. dwijnand commented on Jan 11, 2019

    @dwijnand
    Contributor

    No, I think it's fixed (despite finishing 20 minutes after UTC midnight 😅)

  10. emilyalbini commented on Jan 11, 2019

    @emilyalbini
    MemberAuthor

    Oh, ok then 🎉🎉🎉

  11. unpinned this issue on Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-bugCategory: This is a bug.P-highHigh priorityT-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions