Skip to content
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

rustup tries to sync channel updates for non-updatable channels #756

Closed
brson opened this Issue Oct 12, 2016 · 4 comments

Comments

Projects
None yet
4 participants
@brson
Copy link
Contributor

brson commented Oct 12, 2016

@alexcrichton says it's trying to sync channel updates for old versions when it shouldn't.

@Diggsey Diggsey added this to Components & extensions in Issue Categorisation May 3, 2017

@brson

This comment has been minimized.

Copy link
Contributor Author

brson commented May 12, 2017

I continue to see this error:

brian@ip-10-145-43-250:/mnt2/dev/quandl⟫ rustup update
info: syncing channel updates for 'stable-i686-unknown-linux-gnu'
info: syncing channel updates for 'stable-x86_64-pc-windows-gnu'
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'beta-x86_64-unknown-linux-gnu'
info: downloading component 'rustc'
info: downloading component 'rust-std'
info: downloading component 'cargo'
info: downloading component 'rust-docs'
info: installing component 'rustc'
info: installing component 'rust-std'
info: installing component 'cargo'
info: installing component 'rust-docs'
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: downloading component 'rustc'
info: downloading component 'rust-std'
info: downloading component 'cargo'
info: downloading component 'rust-docs'
info: installing component 'rustc'
info: installing component 'rust-std'
info: installing component 'cargo'
info: installing component 'rust-docs'
info: syncing channel updates for '1.14.0-x86_64-unknown-linux-gnu'
info: syncing channel updates for '1.15.0-x86_64-unknown-linux-gnu'
info: syncing channel updates for '1.16.0-x86_64-unknown-linux-gnu'
info: checking for self-updates

    stable-i686-unknown-linux-gnu unchanged - rustc 1.17.0 (56124baa9 2017-04-24)
     stable-x86_64-pc-windows-gnu unchanged - (rustc does not exist)
  stable-x86_64-unknown-linux-gnu unchanged - rustc 1.17.0 (56124baa9 2017-04-24)
      beta-x86_64-unknown-linux-gnu updated - rustc 1.18.0-beta.2 (f4e8e81c3 2017-05-11)
   nightly-x86_64-unknown-linux-gnu updated - rustc 1.19.0-nightly (e40beb3af 2017-05-11)
  1.14.0-x86_64-unknown-linux-gnu unchanged - rustc 1.14.0 (e8a012324 2016-12-16)
  1.15.0-x86_64-unknown-linux-gnu unchanged - rustc 1.15.0 (10893a9a3 2017-01-19)
  1.16.0-x86_64-unknown-linux-gnu unchanged - rustc 1.16.0 (30cf806ef 2017-03-10)

Note the info: syncing channel updates for '1.16.0-x86_64-unknown-linux-gnu'.

There's a flag associated with toolchains (tracking) that indicates whether they can be updated or not, and it is incorrect:

    pub fn is_tracking(&self) -> bool {
        self.date.is_none()
    }

The logic here should be more like, if the channel is nightly/beta/stable, and the date is none, then it's a tracking toolchain.

@mikhail-m1

This comment has been minimized.

Copy link
Contributor

mikhail-m1 commented May 15, 2017

I'll fix it.

bors added a commit that referenced this issue May 19, 2017

Auto merge of #1121 - mikhail-m1:is_tracking, r=Diggsey
fix ToolchainDesc is_tracking

issue #756.

I wonder, why is not ToolchainDesc.channel a enum?
@kichristensen

This comment has been minimized.

Copy link
Contributor

kichristensen commented May 29, 2017

Is this fixed with the PR from @mikhail-m1 ?

@Diggsey

This comment has been minimized.

Copy link
Contributor

Diggsey commented May 29, 2017

Should be, yes.

@Diggsey Diggsey closed this May 29, 2017

@Diggsey Diggsey removed this from Toolchains & components in Issue Categorisation May 29, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.