[7555] in Release_7.7_team
Permission to use update hook?
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Tue Jul 26 19:47:39 2011
From: Jonathan Reed <jdreed@MIT.EDU>
Content-Type: text/plain; charset=us-ascii
Date: Tue, 26 Jul 2011 19:47:31 -0400
Message-Id: <DE478C18-19DF-49CE-9FA9-E79FF1E1CF4A@mit.edu>
To: release-team@mit.edu
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Transfer-Encoding: 8bit
Due to #987, there are now a number (3) of -development machines which can't take an update. This would be an ideal time to test out our update hook in real life, rather than waiting for a last resort. I propose trying out the following update hook:
"""
#!/bin/sh
aptitude install debathena-auto-update
"""
This should be a no-op on production machines, and should pull in the new debathena-auto-update on -dev machines.
Thoughts? We can also decide that the update hook should really truly only be reserved for the end of the world.
-Jon
