George Borisov wrote:
Søren Christensen wrote:
Change /etc/apt/sources.list to point to etch instead of sarge
and update, upgrade anything else?
I would create an /etc/apt/preferences file like this:
---
Package: *
Pin: release a=stable
Pin-Priority: 650
Package: *
Pin: release a=testing
Pin-Priority: 1001
Package: *
Pin: release a=unstable
Pin-Priority: 600
---
Then:
# apt-get update
# apt-get dist-upgrade
This is probably not a very clever idea. One day after etch becomes
stable your preferences will point to the 'new' testing. In the
following days and weeks you should expect that your system will upgrade
all those packages that didn't make it into etch (because of bugs etc.)
when it was frozen during the time before the release and now rush into
testing once the ban is lifted due to the release of etch. This will
quite likely break quite a few packages.
I would recommend to avoid mixing different releases as long as you are
not 100% sure what you are doing and to set up your sources.list file to
point to release names (sarge instead of stable; etch instead of
testing). Ie. use either 'sarge', 'etch' or 'sid'.
This way nothing get's mixed up and you will always be knowing which
version of debian you are running (independent of release cycles)
Johannes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
