Since "Etch" became "stable" on April 8, is it possible that aptitude updated
many packages from Sarge to Etch for Jan?
The first time I read /usr/share/doc/packages/aptitude/README, I understood
(probably incorrectly) that aptitude should not do this.
Indeed up to today, sarge security updates were found for me quickly and simply
(I only have one debian server.)
However, today I was looking for the php4 security update in aptitude - sure enough it was there, but aptitude told me to hit 'U' begore 'g' 'g'. Now it suprised me with a long list of packages to remove (ok - I don't need them), and a long list of upgrades - even a very surprising apache2.0 to apache2.2 I looked at the apache2 changelog, and saw the update marked as Urgent, but no mention of the change from sarge to etch.
This certainly sounds like a distribution upgrade.
I wonder if Jan was surprised by the same event. Is he perhaps now caught in a
no man's land between sarge and etch? Can he reasonably expect to use
automated tools to complete it the distribution upgrade without installing etch
from scratch?
David
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
