Justin Mason wrote:
Daryl C. W. O'Shea writes:
Justin Mason wrote:
Daryl C. W. O'Shea writes:
Justin Mason wrote:
Daryl C. W. O'Shea writes:
At a minimum I'd disable the 3.2 updates until we figure out exactly
what we want to do (actually that's what I intended).
OK, sounds fine.
So, to do so, I'd just create an update that contains an identical
ruleset to the one being released with 3.2.0, using say 533971 as the
update number and then add the appropriate txt record to the zone file:
0.2.3.updates.spamassassin.org. 3600 IN TXT "533971"
Actually, the cron jobs run as "updatesd" on the zone would quickly
move on and create another update tomorrow, so that wouldn't help. ;)
I assumed (good start eh) that there was a *.2.3 wildcard like 3.1 has,
so a 0.2.3 record would have worked.
oh -- actually, you may be right. That way of doing it hadn't occurred
to me, at all!
I've edited the 'build/mkupdates/run_part2' script, which is run by
cron, and set it to write the updates to a different dir (
http://buildbot.spamassassin.org/updatedev/ ) and to a different
record in the DNS zone ( 0.2.3.updates.dev.spamassassin.org ).
The existing files/records will remain the same until we edit the
script again and uncomment the "live" lines; in the meantime, we'll
be able to see what *would* be going into the updates by checking
those locations.
I'm not sure if you intended the "updates.dev.spamassassin.org." channel
to be usable or not (I guess you did since you created it), but it needs
its own MIRRORED.BY file since you're putting the updates in a different
directory (and effectively a different server since Theo doesn't rsync
your new directory). As it is now it won't work.
To make it usable we need to either:
- create a new MIRRORED.BY file pointing at the zone server and update
mirrors.updates.dev.spamassassin.org. accordingly
- create a new MIRRORED.BY file pointing at the new directory on Theo's
server, have Theo rsync that directory and update DNS accordingly
- revert the changes from this morning, change the update script to use
a wild card *.2.3 entry and set a fixed 0.2.3 record (and update)
Daryl
