[7558] in Release_7.7_team
Re: Permission to use update hook?
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Tue Jul 26 21:16:16 2011
Message-Id: <201107270116.p6R1G9FA016919@outgoing.mit.edu>
To: Jonathan Reed <jdreed@mit.edu>
cc: release-team@mit.edu
In-reply-to: <DE478C18-19DF-49CE-9FA9-E79FF1E1CF4A@mit.edu>
Date: Tue, 26 Jul 2011 21:16:09 -0400
From: Jonathon Weiss <jweiss@MIT.EDU>
Is it worth coding this to explicitly only run on natty machines? I
realize that the suggested fix should be a no-op everywhere else, but
the paranoid in me says that scripts like this should touch as little as
possible.
Jonathon
Jonathan Reed <jdreed@MIT.EDU> 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
