Maui Forums

Full Version: [Solved] - Upgrade question
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
Hi Starbuck. Congratulations on your new baby. I would like to ask for upgrade clarification pls. Do you remember this interchange we recently had [https://mauilinux.org/updating-maui-2-maui-backports/]?

Quote:Starbuck2001

Hi, since Maui is based on neon and that on ubuntu xenial LTS,all Maui's are on the same platform, and therefore share all backports. So it is easy to upgrade, as there is no path needed, one of the advantages of partitially rolling distros. Only LTS to LTS in 2 years would need a true update path.


I thought you were meaning that we could upgrade Maui 1 to 2 simply via the normal Upgrade Manager, but now i read in your https://mauilinux.org/maui-2-blue-tang-released/ that "You can get the new version fresh from our download site ( https://mauilinux.org/download/ )" --> that sounds like we do after all need to download a new ISO, & thus do another total installation...?

If that is correct, then i have a subsidiary question. To my frustration David has not replied to clarify the pretty astonishing statement he made, "Plausible, the encryption scheme even changed between the two releases", https://forums.mauilinux.org/showthread....5#pid39965. IF i need to d/l then fresh-install Maui 2 ISO, then given David's possible meaning, do you think i should now not only format my / with the Maui 2 install, but ALSO this time format & re-encrypt my /home, to avoid any possible conflicts of any old Mint 17 KDE config files buried in /home that might be conflicting with Maui?
Quote:I thought you were meaning that we could upgrade Maui 1 to 2 simply via the normal Upgrade Manager, but now i read in your https://mauilinux.org/maui-2-blue-tang-released/ that "You can get the new version fresh from our download site ( https://mauilinux.org/download/ )" --> that sounds like we do after all need to download a new ISO, & thus do another total installation...?

Thats only for new users.
Existing users are already on Maui 2 for several weeks since we did the last big update Smile

Quote:If that is correct, then i have a subsidiary question. To my frustration David has not replied to clarify the pretty astonishing statement he made, "Plausible, the encryption scheme even changed between the two releases", https://forums.mauilinux.org/showthread....5#pid39965. IF i need to d/l then fresh-install Maui 2 ISO, then given David's possible meaning, do you think i should now not only format my / with the Maui 2 install, but ALSO this time format & re-encrypt my /home, to avoid any possible conflicts of any old Mint 17 KDE config files buried in /home that might be conflicting with Maui?
Please lets discuss this matter on the thread already created. I am afraid I cannot help here as I don't know exactly what changed in kwallet in terms of encryption.
NO, If you update your system via the cli or synaptic you are up to date, no need to reinstall.
Re-installation or Upgrade path would only be needed from LTS base to LTS base, every two years.
Thank you both. Maybe i'm just being too frivolous; if the important code in my installation is now already same as Maui 2 then possibly that's the only thing that really matters... but it'd be kinda nice if it actually told me it's Maui 2:
[attachment=1061]
If you install the base-files package 99 from our repo it should tell you Maui 2 then Smile
Imo I'd even rather prefer if it didnt tell you "Maui 2" if you upgraded, so we still would know if its an original Maui 1 or 2 in the beginning IF some problems occur.
(28th October 2016, 15:27)leszek Wrote: [ -> ]If you install the base-files package 99 from our repo it should tell you Maui 2 then Smile

And how to do that ? Confused
It should be offered as an update in the update manager that you need to tick.
(28th October 2016, 15:58)leszek Wrote: [ -> ]It should be offered as an update in the update manager that you need to tick.

Not seen, after sudo apt-get update, no update package available.
Then maybe you have it installed already? Check with apt-cache policy
Pages: 1 2 3