I envision that a script that applies a patch to an existing update
and creates a new update (that is "automated emergency method") will
be the next step in the process. This would ONLY be used where the
"revert to a known stable update" is not possible, though, due to no
good previous update to revert to. Patching updates manually = bad;
and should be avoided.
HOWEVER... I think the only thing that should be used if AT ALL
possible right now (IF ANYTHING) is the "revert to a known stable
update" method.
Makes a lot of sense, thanks.
A BIG HOWEVER THOUGH... the fix for the problem will be in tonight's
mass-check which means that it will be in tomorrow's auto-update which
will be published at approximately 11pm EDT Jun 28 (or 0400UTC Jun
29). I vote +600 that we just leave things be and let the auto-update
do it's job. There's always the chance of screwing up the manual
update making things worse than they are (and things aren't really
that bad... it's been 25 hours another 23 should be OK).
I agree 100% and leaving the issue be and going to the swim meet was my
vote on the matter. A brand new morning in my timezone and 1140483
appears to have resolved the issue and been published. All that is left
is the remnants for reuse:
72_active.cf:reuse T_URIBL_SEM_FRESH
72_active.cf:reuse T_URIBL_SEM_FRESH_10
72_active.cf:reuse T_URIBL_SEM_FRESH_15
Ticket already open about that.
Regards,
KAM
