http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5147
------- Additional Comments From [EMAIL PROTECTED] 2006-11-06 08:35 ------- The more I think about this, the more I feel that I must veto any change to the channel/sa-update/M::SA/etc. This issue only exists for development versions, and IMO it's really a problem with the update being out of sync with the code. ie: if there's a code change which removes a certain EvalTest from the code, then an update should be created that includes the needed change. >From JM: > - 1. user downloads a dev, prerelease tarball of 3.2.0, installs it > - 2. runs sa-update, gets rules version N > - 3. next day, 3.2.0 is released, containing rules version N+1 > - 4. on that same day, user downloads, installs it > - 5. /var/lib/spamassassin/3.002000/updates_spamassassin_org (version N) is > used, instead of /usr/share/spamassassin (version N+1) Same problem here -- there should be a step 2.5 which is "release a new update w/ rules version N+1". ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
