Re: Upgrading to etch.

To: Luis Matos <gass@otiliamatos.ath.cx>
Cc: Rob Epping <R.Epping@meteo.nl>, backports-users@lists.backports.org
Subject: Re: Upgrading to etch.
From: Alexander Wirt <formorer@formorer.de>
Date: Wed, 11 Apr 2007 17:28:01 +0200
Message-id: <[🔎] 20070411152801.GW5654@ned.snow-crash.org>
In-reply-to: <[🔎] 1176308580.3570.1.camel@portatel>
References: <[🔎] 74B5FF293A1F764FA7D48708BFECD2A85452B3@fohn.nl.meteogroup.net> <[🔎] 1176308580.3570.1.camel@portatel>

Luis Matos schrieb am Mittwoch, den 11. April 2007:

> Putting etch in sources.list and removing backports always works.
> 
> (using dist-upgrade)
> 
> versions in backports are always smaller than testing, wich makes the
> transition easier.
I have a BIG BIG BIG disclaimer here, as we don't stop sarge-bpo it can
happen that versions in sarge-bpo can be greater than in etch which can lead
to broken upgrade paths from sarge -> etch. 

Just to let you know

Your friendly ftp-master

Alex

Reply to:

Follow-Ups:
- Re: Upgrading to etch.
  - From: Luis Matos <gass@otiliamatos.ath.cx>

References:
- Upgrading to etch.
  - From: "Rob Epping" <R.Epping@meteo.nl>
- Re: Upgrading to etch.
  - From: Luis Matos <gass@otiliamatos.ath.cx>

Prev by Date: Re: Upgrading to etch.
Next by Date: Re: Upgrading to etch.
Previous by thread: Re: Upgrading to etch.
Next by thread: Re: Upgrading to etch.
Index(es):
- Date
- Thread