How did these nopublish rules get into the sa-update channel? This seems
to be a bug. These rules will cause network lookups to that provider who
is unprepared for the 3.3.0 release onslaught. He's currently working on
moving the zone to a separate address with public mirrors and round robin
DNS.
Warren Togami
[email protected]
They got in the tarball/update channel because they shouldn't have. It's a
bug but this confirms the belief that the relevant bug 6297 should be a
blocker for 3.3.0.
However, I don't know for sure that it ever went out to the sa-update
channel. It's in the proposed 3.3.0 release rules tarball (and therefore
the proposed 3.3.0 channel).
Regards,
KAM
