[432] in athena10
Re: Automatic updates for Athena 10
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Aug 13 17:48:04 2008
From: Greg Hudson <ghudson@MIT.EDU>
To: Timothy G Abbott <tabbott@mit.edu>
Cc: Kenneth Arnold <kcarnold@mit.edu>, athena10@mit.edu
In-Reply-To: <alpine.DEB.1.10.0808131713490.30521@vinegar-pot.mit.edu>
Content-Type: text/plain
Date: Wed, 13 Aug 2008 17:47:19 -0400
Message-Id: <1218664039.12433.203.camel@error-messages.mit.edu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
On Wed, 2008-08-13 at 17:36 -0400, Timothy G Abbott wrote:
> 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).
jdreed ran into a case like this recently, although he wasn't able to
preserve the output to see why it happened, unfortunately.
> I think what you want to do is something like
>
> aptitude install debathena-cluster
>
> after the upgrade, but I've not tested this.
Well, can't hurt.
It would also be helpful if we could get aptitude to balk at solutions
with a negative score, but I don't see a command-line option to do that.
I'm tempted to go a level deeper and write the update using python or
perl apt bindings for better control (e.g. for progress notifications to
the X server) but I don't know if that's feasible.
