2016-05-31 vs. 2016-05-13

I noticed:
https://rcn-ee.com/rootfs/bb.org/testing/2016-05-31/lxqt-4gb/bone-debian-8.4-lxqt-4gb-armhf-2016-05-31-4gb.img.xz
is out and that:

https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz
is now “current”.

Will apt-get update & apt-get upgrade get me from 2016-05-13 to 2016-05-31? or should I start with a fresh image. Just looking to redo my “newbie” tests this weekend.

In theory upgrading should do it, but in practice, some packages get added and thus aren’t there to be upgraded.

If nobody answers I’ll try both ways if I have time over the weekend – but more storms are expected here, so power outages are very possible.

I noticed:

https://rcn-ee.com/rootfs/bb.org/testing/2016-05-31/lxqt-4gb/bone-debian-8.4-lxqt-4gb-armhf-2016-05-31-4gb.img.xz
is out and that:

https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz
is now "current".

Will apt-get update & apt-get upgrade get me from 2016-05-13 to 2016-05-31?
or should I start with a fresh image. Just looking to redo my "newbie"
tests this weekend.

Consider to do a 'apt-get dist-upgrade' or a 'apt full-upgrade'
Google will tell u the difference between upgrade, dist-upgrade and
full-upgrade;)

In theory upgrading should do it, but in practice, some packages get added
and thus aren't there to be upgraded.

Note: all packages installed with apt will be upgraded. But, there
might be other differences between 2016-05-13 and 2016-05-31, namely
other packages installed...

As far as my “newbie tests” go 2016-05-31 has the same issues as does 2016-05-13.