On 3/21/2011 5:29 PM, Daryl C. W. O'Shea wrote:
On 21/03/2011 11:08 PM, Karsten Bräckelmann wrote:
On Mon, 2011-03-21 at 20:01 -0700, John Hardin wrote:
On Mon, 21 Mar 2011, Daryl C. W. O'Shea wrote:
Actually... I can't find any sign of PILL_PRICE in the latest
update. Are you
sure there's still an issue with it?
Here's what I did:
[...]
If I did that wrong I'll be happy to say "d'oh!".
Nope, already confirmed myself.
The __PILL_PRICE_x rules are still there, with the tflags multiple.
OK, I've added the three (0) metas to the bottom of 72_active.cf and
rolled and pushed an update. I didn't test it, because, well, I'm going
to bed. Hopefully I didn't screw it up.
I've disabled stable branch updates for now. If they are re-enabled
there's a chance that the fix will be clobbered and the bad version will
be published again. I'll confirm things are OK later in the week before
re-enabling.
I think my first step to resolving this "fix a broken update" issue is
to write a script to just roll-back to a given (manually chosen) update
revision number, by having it copied and published as a new (higher)
revision number. It doesn't fix things like the Y2K10 issue we had, but
it would resolve issues like we just had now.
Daryl
Hi Daryl,
I am afraid we already need another emergency rule update for 3.3.
Please take a look at Bug #6220 and #6560. In the short-term we need to
push another emergency rule update to disable all six of those network
rules. Then we need to figure out how it managed to ignore the
"#testrules" mark within the sandbox file.
Warren Togami
[email protected]
