On Fri, Dec 10, 2010 at 11:04 +0000, Tom Furie wrote: > On 10/12/2010 10:04, Jesús M. Navarro wrote: > >On Thursday 09 December 2010 21:05:00 Tom Furie wrote:
[…]
>>> you could change from 'testing' to 'squeeze' now as they are
>>> currently the same thing. Then when squeeze goes stable you could
>>> change to 'stable', this will allow you to track the stable
>>> distribution and it will upgrade to the next stable 'wheezy', when
>>> that is released.
>> I wouldn't suggest that as it can deal to unexpected surprises.
>> Of course, you can do as you see, but in order to track Stable, I
>> always suggest doing it by tracking codename changes, so stay with,
>> say, squeeze till you know wheezy has come Stable and you are ready
>> for the upgrade, then change the codename on your sources and do it.
> Why? What's the difference between having stable in the source list
> and automatically upgrading when the new stable is released - all
> upgrade issues *should* be worked out by then - versus switching the
> codename once the new version becomes stable?
Upgrading between releases is typically not just a simple
apt-get/aptitude upgrade (dist-,full-) run. The upgrade process and
things you have to consider when you upgrade are documented in the
release notes and it is a good idea to follow them, as there might be
substantial changes to the system that have to be taken care of.
The release notes for Squeeze [1] break the update down into a couple of
steps:
1. Checking system status
update packages, verify enough space is available, disable
pinning/backports, …
2. Upgrading packages
- Use apt-get and *not* aptitude for this
- Minimal system upgrade
- Upgrading the kernel and udev
This step is very important, because you have to make sure
that you upgrade the kernel *and* udev together and
- *Reboot the system*
- Only now can you upgrade the rest of the system with a
"apt-get dist-upgrade" run.
This a, of course, a highly simplified view of the upgrade process, but
it exemplifies that you definitely don't want to plunge into the process
without preparation by running "aptitude full-upgrade" before you had
your coffee.
I would therefore *strongly* recommend to use the actual names in your
sources.list and upgrade once you are ready and have read the release
notes.
--
.''`. Wolodja Wentland <wolodja.wentl...@ed.ac.uk>
: :' :
`. `'` 4096R/CAF14EFC
`- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
signature.asc
Description: Digital signature
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
