-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Question about Crouton updates #1039
Comments
Essentially, yes. The new installer is indirect: it downloads the latest version of crouton before running the command. Recently, we've had a number of cases where old installers were used for updates, leading to problems not getting fixed. This update should fix this kind of issue in the future. |
I see. So theres no need for me to do croutonversion -u anymore? |
croutonversion -u will download and store the latest direct installer for the branch your chroot was made in (i.e., if you're running the desktops branch, it'll be sure to get the right one). The indirect installer (the goo.gl link) will always grab (and temporarily cache) the latest master branch installer, or whatever branch you manually specify with CROUTON_BRANCH. So yeah, if you're on the main branch, then if you download the current direct installer you can keep using it without redownloading it. If you're on a separate branch, you may want to use croutonversion -u to avoid accidentally switching back to the main branch. |
Hi :D
So I updated crouton via croutonversion -u -d -c
I then proceeded to update my chroot via sudo sh ~/Downloads/crouton -u -n trusty
I noticed that the first thing it did was to download "Crouton Installer".
Is that the same thing as croutonversion -u ?
The text was updated successfully, but these errors were encountered: