[7434] in Release_7.7_team
Re: machines logging " can't configure unconfigured packages"
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Tue Mar 29 11:42:29 2011
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Jonathan Reed <jdreed@MIT.EDU>
In-Reply-To: <201103291524.p2TFO37l027424@wax-lion.mit.edu>
Date: Tue, 29 Mar 2011 11:42:19 -0400
Cc: release-team@mit.edu
Message-Id: <EA0EC90F-C79A-4383-9629-FE1F9A4A3C7F@mit.edu>
To: Jonathon Weiss <jweiss@mit.edu>
Content-Transfer-Encoding: 8bit
> quickstation-50-1 is suffering from something that post-dates the
> atpocalypse, and should eitehr be investigated by someone on
> release-team, or re-installed.
I totally fixed quickstation-50-1 after the atpocalypse. It subsequently exploded because, as usual, someone power-cycled the machine in the middle of an update when they couldn't log in because GNOME is more focused on shiny things than functionality, and is too incompetent to handle /etc/nologin correctly.
I have tested deabthena-gdm-config on two machines, and I'm going to decide that that's good enough to go to proposed, because we REALLY need to push it, like, now so that it will correctly tell users that an update is in progress and to come back later.
> The following machines appear to be suffering from the atpocalypse
> (and while they are not official cluster machines, they are all
> running debathena-cluster, and it's probably a good idea for hotline
> to assist in fixing them):
> caes-sun-2
> caes-sun-6
> cardparkathena
> dew-ref-2
> dke-athena-1
> jupiter
> medfd1
> quickstation-w35-2
These can be fixed with the procedure I previously sent to hotline. If the procedure fails, re-installation should work.
> saturn is running debathena-cluster on jaunty.
Anything running debathena-cluster was supposed to upgrade. I... have no idea why it didn't. A re-install is the right answer at this point.
-Jon
