[431] in athena10
Re: Automatic updates for Athena 10
daemon@ATHENA.MIT.EDU (Timothy G Abbott)
Wed Aug 13 17:37:37 2008
Date: Wed, 13 Aug 2008 17:36:52 -0400 (EDT)
From: Timothy G Abbott <tabbott@MIT.EDU>
To: Greg Hudson <ghudson@mit.edu>
cc: Kenneth Arnold <kcarnold@mit.edu>, athena10@mit.edu
In-Reply-To: <1218486101.12433.177.camel@error-messages.mit.edu>
Message-ID: <alpine.DEB.1.10.0808131713490.30521@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
On Mon, 11 Aug 2008, Greg Hudson wrote:
> The actual update process is just "aptitude update && aptitude
> full-upgrade" so most of the scripting will be the safety checks around
> it, possibly an attempt to communicate to the console that an update is
> happening, etc.. Also, /etc/sources.list.d/debathena.list will be
> updated depending on cluster info.
I would take care with this upgrade path. It is quite possible if we have
an update that is intended to replace one installed package with another,
that aptitude will not perform the upgrade (and quite possibly might
uninstall debathena-workstation in the process). We ran into this on the
6.01 laptops when the printing setup was to be switched from cupsys to
lprng (so it worked with the lab printers), but cupsys had a higher
priority than the 6.01 metapackage.
I think what you want to do is something like
aptitude install debathena-cluster
after the upgrade, but I've not tested this.
-Tim Abbott
