[7556] in Release_7.7_team
Re: Permission to use update hook?
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Tue Jul 26 19:53:28 2011
Date: Tue, 26 Jul 2011 19:53:21 -0400 (EDT)
From: Geoffrey Thomas <geofft@MIT.EDU>
To: Jonathan Reed <jdreed@mit.edu>
cc: release-team@mit.edu
In-Reply-To: <DE478C18-19DF-49CE-9FA9-E79FF1E1CF4A@mit.edu>
Message-ID: <alpine.DEB.2.00.1107261950260.4814@tyger.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sounds like a great idea to test it once before the end of the world. I'll
be on campus (although distracted) until a little past 10, so I can pay
attention if something massively breaks. Or we can do this tomorrow.
Should that also include "aptitude update"?
Should that also desync?
--
Geoffrey Thomas
geofft@mit.edu
On Tue, 26 Jul 2011, Jonathan Reed wrote:
> 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
