Re: [PLUG] Linux Mint 17.3

[JP Vossen <jp@jpsdomain.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

FWIW I've done 3 now via the `sed` method at bottom and all were quick
and easy.  One didn't automatically re-connect to wireless right away
but has since behaved, and one reset the screen resolution to default,
both are trivial fixes at the console.

On 12/09/2015 06:55 PM, Thomas Delrue wrote:
> You get the usual wizard and you have to then explicitly check a box
> that says "Do It!" before it will actually do the upgrade. You can look
> at release notes and changelogs in that wizard.
> 
> I just completed the process in about 9min (includes 2 reboots one of
> which was because of the installation of a new kernel [3.19])
> Very painless and straightforward!
> 
> On 12/09/2015 06:15 PM, Eugene Smiley wrote:
>> Nice. Thanks for the heads up.
> 
>> When you click Upgrade does it give any warnings about what actions
>> it is about to take or does it just go straight into the upgrade
>> process?
> 
>> On Wed, Dec 9, 2015 at 1:35 PM, Thomas Delrue
>> <delrue.thomas@gmail.com> wrote:
> 
>> And speaking of which, look what just popped up after 
>> mint-upgrade-info was apt-get upgraded to 1.0.4 (see attached: mint 
>> 17.3.png)
> 
>> On 12/03/2015 10:26 AM, Thomas Delrue wrote:
>>>>> On 12/02/2015 04:06 PM, JP Vossen wrote:
>>>>>> I just learned that my assumption that if I was running
>>>>>> Linux Mint 17 that I'd automatically get 17.1, 17.2, 17.3,
>>>>>> etc. is wrong.  That *is* how Debian and Redhat work, so to
>>>>>> my mind this violates the principle of least surprise, which
>>>>>> Mint also violates by manually editing LSB files thus causing
>>>>>> perpetual file conflicts on updates.  But I digress...
>>>>>
>>>>>> So you have to do something like this to jump from 17.0 to
>>>>>> 17.3: `for list in $(grep -lR 'qiana' /etc/apt/*list*); do
>>>>>> echo sed -i 's/qiana/rosa/' $list; done`
>>>>>
>>>>> You can also just open the Update Manager and go to the Edit
>>>>> menu and select "Update to 17.[1-2] (codename)". It's pretty
>>>>> much as painless as it can be made. For more information about
>>>>> why Mint doesn't behave like Debian or Redhat (partially
>>>>> because it *isn't* Debian nor RedHat): you can check out 
>>>>> http://blog.linuxmint.com/?p=2725
>>>>>
>>>>> It boils down to "If it ain't broke, don't fix it; upgrade
>>>>> because *you* want to, not because the Distro-Team has decided
>>>>> you should". I especially like that last part of the sentence:
>>>>> "because *you* want to."
>>>>>
>>>>> That being said: the instructions above are for when you want
>>>>> to use 17.3 /BEFORE/ it has been released. You won't find
>>>>> "Update to 17.3" in the update manager yet as it hasn't been
>>>>> released yet! (but you will find 'Update to .2 or .1' if you're
>>>>> still on an older version) As soon as 17.3 reaches GA, it'll
>>>>> pop up in the Edit menu and you can upgrade to it from there.
>>>>>
>>>>> As for the site being down, that still appears to be the case
>>>>> as of this moment :(

Later,
JP
- --  -------------------------------------------------------------------
JP Vossen, CISSP | http://www.jpsdomain.org/ | http://bashcookbook.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlZo4WcACgkQDaVauSnw1lxdZQCeM20Fw6aruIQzQNHwHlfgiJC0
o/4Anj2UTJ6XavR8nKGaDUNffsGZCbCx
=4gWz
-----END PGP SIGNATURE-----
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug