Re: Aptitude updating Sarge to Etch?
- To: dcorking <lists@dcorking.com>
- Cc: debian-user@lists.debian.org
- Subject: Re: Aptitude updating Sarge to Etch?
- From: Daniel Burrows <dburrows@debian.org>
- Date: Tue, 29 May 2007 07:35:54 -0700
- Message-id: <[🔎] 20070529143553.GA5184@alpaca>
- In-reply-to: <listhandler=2&site=www.debianhelp.org&nid=6559&pid=22387&cid=26820&uid=4308&tid=79&872d334a4e1854ce04235fae0707e3fc@www.debianhelp.org>
- References: <20070426135100.GB5743@jeeves.burrows.local> <listhandler=2&site=www.debianhelp.org&nid=6559&pid=22387&cid=26820&uid=4308&tid=79&872d334a4e1854ce04235fae0707e3fc@www.debianhelp.org>
On Mon, May 28, 2007 at 11:21:10PM +0200, dcorking <lists@dcorking.com> was heard to say:
> Since "Etch" became "stable" on April 8, is it possible that aptitude
> updated many packages from Sarge to Etch for Jan?
It's possible.
> The first time I read /usr/share/doc/packages/aptitude/README, I understood
> (probably incorrectly) that aptitude should not do this.
aptitude will do what you tell it to do. It reads
/etc/apt/sources.list to decide where it should look for packages and
upgrades. If you have a deb line like:
deb http://ftp.us.debian.org/debian/ stable main
then aptitude will always upgrade you to the current "stable" release,
whatever it is; when a new release is put out, aptitude will see a whole
bunch of new versions of packages and try to get you in sync with them.
In general, you should use the name of the release instead, e.g.
deb http://ftp.us.debian.org/debian/ sarge main
Daniel
Reply to: